From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: edit Aux.pm under GNU emacs hangs
Date: Tue, 07 Apr 2009 15:07:00 -0000 [thread overview]
Message-ID: <20090407150714.GE22338@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20090407100659.GB12558@trikaliotis.net>
On Tue, Apr 07, 2009 at 12:06:59PM +0200, Spiro Trikaliotis wrote:
>Hello,
>
>* On Mon, Apr 06, 2009 at 06:20:26PM +0200 Corinna Vinschen wrote:
>> On Apr 6 18:12, Spiro Trikaliotis wrote:
>
>> > * On Mon, Apr 06, 2009 at 03:00:21PM +0100 Phil Betts wrote:
>> > > Marc Girod wrote:
>[...]
>> > > http://cygwin.com/faq/faq-nochunks.html#faq.using.dos-filenames
>
>> > Is this still true for Cygwin 1.7? I mean, Win 9x support has been
>> > dropped, there is no reason not to use the \\.\... path specifiers,
>> > which would make this problem vanish.
>>
>> Apart from the fact that you should use slashes instead of backslashes,
>> there isn't any need to use //./ in Cygwin 1.7. Just open Aux.pm.
>
>I was asking if 1.7 supports the access to such files. As I was assuming
>that you would use the Win32 API, I asked why *Cygwin* does not use the
>\\.\... paths.
>
>
>> http://cygwin.com/1.7/cygwin-ug-net/using-specialnames.html
>
>Ok, so this is not an issue for 1.7 anymore. Good to know.
So, to summarize:
Message 1: "I can't create Aux.pm"
Message 2: "Windows limitation"
Message 3: "What about 1.7?"
Message 4: "Fixed in 1.7"
Message 5: "You didn't answer the question"
Message 6: "Yes I did"
Message 7: minor correction to 6
Message 8: "Oh. I misinterpreted the question"
Message 9: "No problem"
Message 10: Pedantic responses/questions to nits in Message 3
Message 11: Polite response to pedantry
Message 12: "Thanks for message #3"
Seems like we were seven or eight messages over the limit.
cgf
next parent reply other threads:[~2009-04-07 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22909185.post@talk.nabble.com>
[not found] ` <5E25AF06EFB9EA4A87C19BC98F5C875302FBD5C5@core-email.int.ascribe.com>
[not found] ` <20090406161239.GA12558@trikaliotis.net>
[not found] ` <20090406162026.GA8063@calimero.vinschen.de>
[not found] ` <20090407100659.GB12558@trikaliotis.net>
2009-04-07 15:07 ` Christopher Faylor [this message]
2009-04-08 8:34 ` Dave Korn
2009-04-08 16:42 ` Christopher Faylor
2009-04-08 17:04 ` Warren Young
2009-04-08 17:30 ` Corinna Vinschen
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=20090407150714.GE22338@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-talk@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).