[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nedit-develop
Subject:    [ nedit-Bugs-1616278 ] Windows/Cygwin file name compatibility
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2006-12-18 10:11:49
Message-ID: E1GwFTJ-000388-64 () sc8-sf-web5 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1616278, was opened at 2006-12-15 11:37
Message generated for change (Comment added) made by ajbj
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111005&aid=1616278&group_id=11005

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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joerg Fischer (jf505)
Assigned to: Nobody/Anonymous (nobody)
Summary: Windows/Cygwin file name compatibility

Initial Comment:
When running on MS Windows (using Cygwin), NEdit should not distinguish between cases \
in filenames, otherwise it opens the same file twice, eg as file.txt and File.TXT.

Notice that the hack attached is only meant as demonstration and also is not \
complete.  It is still possible to open the same file twice because of Cygwin mount \
points, i.e., if the Cygwin root is on say C:\cygwin, then /home/user/file.txt points \
to the same file as /cygdrive/c/cygwin/home/user/file.txt.

(Notice that with the /cygdrive/ prefix you can reach all areas of all the drives \
under MS Windows regardless of mount points.)

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

Comment By: Tony Balinski (ajbj)
Date: 2006-12-18 11:11

Message:
Logged In: YES 
user_id=618141
Originator: NO

Good idea. I think there might be some NT stuff (Cygwin stuff too?)
telling you whether the file system has case significance or not (imagine
going to a Samba share from your Windows box). Hmmm. In fact, it would be
nice to have NEdit respect the case of the file path elements as they
appear in the directory entries rather than as as supplied by the user, or
converted arbitrarily to upper or lower case.

Isn't VMS also case insensitive, or has that changed since I last used it
(circa 1999)?

BTW there's the problem with spaces in paths/names - I had a crack at a
fix for the bug I entered as #1565125 - No spaces in paths for "Open
Selected", which also probably needs some work.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111005&aid=1616278&group_id=11005
-- 
NEdit Develop mailing list - Develop@nedit.org
http://www.nedit.org/mailman/listinfo/develop


[prev in list] [next in list] [prev in thread] [next in thread]