Author Topic: Funny File Names that confuse Slickedit.  (Read 1450 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1901
  • Hero Points: 184
  • Text
Funny File Names that confuse Slickedit.
« on: September 16, 2016, 06:40:48 pm »
I've ended up with some files on my system with filenames with weird characters.
Its amazingly hard to pin down exactly *what* some of these filenames are.
I can access them from CMD with more, type and copy (using filename completion or wildcards).

Attached is a CPP program to create a file with a name that Slick cannot handle. This is just one example I was able to make happen from CPP, I've got more but I'm not sure how to create them. A bunch showed up in a folder that I expanded from a ZIP archive, but I cannot create a zip from them, others are from Cygwin.

Slick cannot open this file - though using the Windows File Open dialog, slick "opens" it, but doesn't show any contents.
When slick tries to save it, it fails with "File not found".
Autosave is really annoyed by this thing.
Slick managed to create a backup of the file in vsdelta, but sgrep cannot open it.
When I do a FiF, sgrep will complain about these files with "Failed to open: ...."

Sometimes, Slick will come up with "Reload modified files" when it has the file open - but when I choose "Close selected buffers", it doesn't actually close it.

In VisualStudio, the character is displayed as a box with a ? in it.
Slick displays it as "fi"
Windows displays it as a dot.
CMD shows it as a box.



Autosave:
   ---------------------------
   SlickEdit Pro
   ---------------------------
   AutoSave has failed to save the file C:\Users\josepo03\Documents\Visual Studio 2015\Projects\DirUnicode\DirUnicode\File?.txt.  Do you wish to disable AutoSave?
   ---------------------------
   Cancel   &Yes   &No   
   ---------------------------
   ---------------------------
   SlickEdit Pro
   ---------------------------
   File not found
   ---------------------------
   OK   
   ---------------------------


Ordinary save:
   ---------------------------
   SlickEdit Pro
   ---------------------------
   Unable to save C:\Users\josepo03\Documents\Visual Studio 2015\Projects\DirUnicode\DirUnicode\File?.txt
   File not found
   ---------------------------
   OK   
   ---------------------------

(Kudos: A "File not found" error dialog *with* the filename!)


Backup History:
   ---------------------------
   SlickEdit Pro
   ---------------------------
   Could not open 'C:\Users\joe\Documents\Slickedit\21.0.0\vsdelta\C\cygwin64\home\joe\FILE?.txt.vsdelta', it may be damaged.

   Would you like to try to repair it now?
   ---------------------------
   &Yes   &No   
   ---------------------------


Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5146
  • Hero Points: 425
Re: Funny File Names that confuse Slickedit.
« Reply #1 on: September 17, 2016, 12:31:00 am »
Nice catch!

There's a bug in the Utf16 to Utf-8 converter. Problem is between 0xDC00 - 0xFBFF. Conversion from Utf-8 to Utf-16 is fine.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5146
  • Hero Points: 425
Re: Funny File Names that confuse Slickedit.
« Reply #2 on: September 17, 2016, 03:45:16 am »
Fixed in RC 2