From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin@cygwin.com
Subject: Re: Release candidate 1: /etc/hosts
Date: Thu, 12 Sep 2002 15:01:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.44.0209121548220.19696-100000@slinky.cs.nyu.edu> (raw)
In-Reply-To: <3D80E193.C2242234@pajhome.org.uk>
On Thu, 12 Sep 2002, Paul Johnston wrote:
> Igor,
>
> > How exactly are you proposing to modify cygpath? cygpath translates
> > windows paths to unix-style, and back. There is nothing in the cygpath
>
> Sorry, should have been clearer about this: modifying cygpath to add a
> feature to get the correct case for a path. Perhaps we could figure a
> way to use "dir /b" - but I'm sure other people will hit this same issue
> in the future and would appreciate such a feature in cygpath. If you
> agree this is a good idea, I'm prepared to do the groundwork.
Oh, I see, add a modifier similar to '-s', so that it verifies the case of
each element in the path... Yeah, that could work, something like:
-e, --exact-case print exact case of NAME
I'm not sure how to implement this, though... If you have ideas, I'd be
interested in hearing them.
> Failing that, I think it would be ok to assume that the path will either
> be all caps or all non-caps - corresponding to FAT or NTFS. Anyone
> tweaking the case of such paths/files on NTFS quite deserves their fate!
Well, on my Win2k machine, the exact case is as follows:
C:\WINNT\system32\drivers\etc\hosts. Notice that "WINNT" is all caps. I
use NTFS, and this is apparently the default setup.
> BTW, I'm subbed to cygwin so you don't need to keep copying me on mails.
Oops, sorry, this is the default in my mailer. I'll be more careful.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
It took the computational power of three Commodore 64s to fly to the moon.
It takes a 486 to run Windows 95. Something is wrong here. -- SC sig file
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-09-12 19:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 7:28 Paul Johnston
2002-09-12 8:13 ` Gerrit P. Haase
2002-09-12 10:49 ` Igor Pechtchanski
2002-09-12 10:53 ` Nicholas Wourms
2002-09-12 11:16 ` Igor Pechtchanski
2002-09-12 11:15 ` Nicholas Wourms
2002-09-12 11:33 ` Igor Pechtchanski
2002-09-12 11:29 ` Paul Johnston
2002-09-12 11:42 ` Igor Pechtchanski
2002-09-12 11:44 ` Paul Johnston
2002-09-12 15:01 ` Igor Pechtchanski [this message]
2002-09-12 17:16 ` Finding exact case of paths Paul Johnston
2002-09-12 17:52 ` Igor Pechtchanski
2002-09-12 20:14 ` Igor Pechtchanski
2002-09-13 1:12 ` Igor Pechtchanski
2002-09-13 5:58 ` Release candidate 2: /etc/hosts Paul Johnston
2002-09-13 7:38 ` Igor Pechtchanski
2002-09-15 2:47 ` Installing cygwin-mketc.sh Paul Johnston
2002-09-15 5:53 ` John Morrison
2002-09-15 6:49 ` John Morrison
2002-09-15 7:17 ` John Morrison
2002-09-15 9:44 ` Igor Pechtchanski
2002-09-15 9:28 ` Igor Pechtchanski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.44.0209121548220.19696-100000@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).