This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Added some interesting functionality to my cygwin sandbox
On Mon, Jun 30, 2003 at 05:01:01PM +0100, Elfyn McBratney wrote:
>On Mon, 30 Jun 2003, Christopher Faylor wrote:
>
>> On Mon, Jun 30, 2003 at 05:18:39PM +0200, Corinna Vinschen wrote:
>> >On Mon, Jun 30, 2003 at 10:47:16AM -0400, Christopher Faylor wrote:
>> >> On Mon, Jun 30, 2003 at 04:41:46PM +0200, Corinna Vinschen wrote:
>> >> >On Mon, Jun 30, 2003 at 10:29:32AM -0400, Christopher Faylor wrote:
>> >> >>Does this reference the a: drive or the a: directory? I'm assuming
>> >> >>that it should probably be the a: directory in those cases where your
>> >> >>current directory is one that has the proper bit set but this makes me
>> >> >>slightly uncomfortable since it is such a departure from the way cygwin
>> >> >>used to work.
>> >> >>
>> >> >>Any thoughts?
>> >> >
>> >> >The a: directory if the mount flag is set and the directory exists.
>> >>
>> >> If I just make this conditional on the existence of an a: file or
>> >> directory you'll never be able to create a new a: .
>> >
>> >Uh, sure. Hmm, in that case, do you have any choice? If the mount
>> >flag is set, access the directory, otherwise the drive. I don't see
>> >how you could do it different.
>>
>> The only other thing I could do is announce that [a-z]: are "special"
>> and not allow creation of those kind of directories. Probably not
>> a good idea.
>
>Maybe this is to be expected, but as soon as a Cygwin user see's this feature,
>uses it wrong, throws up on the list, everyone else catches on...it's be the
>next where is `su'!? :-)
>
>BTW, is this using URL encoding or character shifting? I'm just thinking of
>those poor setup.exe users who were frightened by the URL-encoded directories in
>their cache. I'm thinking Mutt and Maildir here...
It's the same mechanism that Robert uses. Very simple. However I don't
see why anyone would be frightened by %3a's in their filenames since
they wouldn't see them unless they were running an MS-DOS application
which inspected the directory. Unfortunately, this won't help the setup
cache people since I can't allow the %2f value in an encoded filename. So,
they'll still be confounded by the file names.
cgf