[ jEdit-devel ] [ jedit-Bugs-1488911 ] Forward slash in path causes problems on OSX

[SourceForge.net <no...@so...>]

Bugs item #1488911, was opened at 2006-05-15 08:15
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1488911&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: editor core
Group: None
>Status: Open
>Resolution: None
Priority: 5
Submitted By: sneaker333 (sneaker333)
Assigned to: Nobody/Anonymous (nobody)
Summary: Forward slash in path causes problems on OSX

Initial Comment:
If any folder in the path to a file on OS X contains a forward slash 
character then JEdit interprets that as the start of a subfolder and not part 
of the folder name.

For  example if you have a folder called 'This/That' and a file inside called 
'test.html' then you cannot open the file within JEdit until you move that 
file outside the folder. Using the File System Browser, you cannot browse 
into that folder either.


----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2006-07-21 14:26

Message:
Logged In: YES 
user_id=935841

ok I've repoened the issue. 

If a macintosh developer thinks this is important, I'm sure
s/he will fix it. I only do linux and occasionally windows.



----------------------------------------------------------------------

Comment By: Skeeve (ngc)
Date: 2006-07-19 10:31

Message:
Logged In: YES 
user_id=864970

I just renamed a file i have to my/report.html

It was displayed in jEdit's file browser as my:report.html.
But when I opened it, the name was report.html and the path
got an /my appended.

So if it actually appears to be legal to use a "/" in
filenames (it isn't, cause it's converted to ":"), we
should, if possible, do something about it.

----------------------------------------------------------------------

Comment By: Andy Streich (andystreich)
Date: 2006-07-19 09:03

Message:
Logged In: YES 
user_id=973452

Just to add a bit of closure I thought I would add this. 
Perhaps jEdit could add a policy statement in the User Guide
for Mac users.

from http://www.westwind.com/reference/OS-X/paths.html:

"In the Mac OS tradition, colons are path separators, and
cannot appear in the names of files or folders; slashes on
the other hand are perfectly fine and are commonly used in
filenames (e.g. "Meeting Notes 12/5/2000"). In unix, the
situation is reversed: colons are fine in filenames, but
slashes are forbidden. Mac OS X handles this by changing how
filenames appear, depending on what the forbidden character
is in a given context. For example, a file named "Meeting
Notes 12/5/2000" by a Classic application will appear as
"Meeting Notes 12:5:2000" under the command line. The Mac OS
X Finder takes a middle road: it displays the names with
slashes, but also uses slashes as path separators. The only
place I've found that this actually causes a problem is that
it means you cannot use the Finder's "Go To Folder" menu
command to go to a folder with a slash (or colon if you
prefer) in its name.

"Also, in an attempt to avoid the confusion in the first
place, Mac OS X sometimes tries to prevent you from using
either colons or slashes in filenames; in some places it'll
just refuse to let you enter them; in others it turns them
all into dashes."

----------------------------------------------------------------------

Comment By: sneaker333 (sneaker333)
Date: 2006-07-19 08:34

Message:
Logged In: YES 
user_id=1522997

In OS X, a folder name containing  a forward slash is perfectly legal and every 
other tool actually accesses it fine I'm afraid ... even those apps that are not 
specifically targeted at the Mac, such as the 3D app Blender. Of course I could 
simply rename the folder but that shouldn't be necessary - it just caught be me 
out.


----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2006-07-19 08:16

Message:
Logged In: YES 
user_id=935841

How the heck were you able to create a folder with a / in
its name in the first place? I doubt you'll be able to do
much with it from most other developer tools. I recommend
renaming the folder to this_that.






----------------------------------------------------------------------

Comment By: sneaker333 (sneaker333)
Date: 2006-07-19 03:05

Message:
Logged In: YES 
user_id=1522997

Matthieu, that is correct that OS X allows a folder to be named "This/That" 
which is not a folder hierarchy of That within This.

This is actually seen to the unix side of OS X as a folder named "This:That" 
and it is shown in the FSB as such, but when you try to open the folder within 
the FSB then you get the message

/Users/paul/This/That:
Cannot list directory

In the terminal, cd /Users/paul/This:That will change to that directory with no 
problem. It would appear that the colon is becoming translated back to the 
forward slash at some point. 

Trying to escape characters in the FSB does not appear to work.


----------------------------------------------------------------------

Comment By: Matthieu Casanova (kpouer)
Date: 2006-07-19 00:06

Message:
Logged In: YES 
user_id=285591

I'm not mac user, but does it mean that the folder is named
"This/That" and it is not a folder "This" containing a
folder "That" ?
If yes, and if the file separator is /, the / must be
escaped, I don't know if the FSB can escape char in path
field, could you try ?

----------------------------------------------------------------------

Comment By: Skeeve (ngc)
Date: 2006-07-18 12:29

Message:
Logged In: YES 
user_id=864970

So where is the problem? '/' is the path seperator in OS X.
This is considered normal behaviour.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1488911&group_id=588