From: Ryan Johnson <ryanjohn@ece.cmu.edu>
To: Eric Blake <eblake@redhat.com>
Cc: cygwin@cygwin.com
Subject: Re: Re: Spurious warnings about MS-DOS paths
Date: Sat, 16 Apr 2011 07:27:00 -0000 [thread overview]
Message-ID: <4DA8D6D6.9090601@ece.cmu.edu> (raw)
In-Reply-To: <4DA70298.3040601@redhat.com>
On 2:59 PM, Eric Blake wrote:
> On 04/13/2011 09:10 PM, Ryan Johnson wrote:
>> Hi all,
>>
>> A recent cygwin update has started spewing warnings such as the
>> following when I do tab completion on a path containing spaces:
>>> $ cd ~/Home/Documents/Pcygwin warning:
>>> MS-DOS style path detected: ~/Home/Documents/PC\ reviews\ 2011
>>> Preferred POSIX equivalent is: ~/Home/Documents/PC/ reviews/ 2011
>>> CYGWIN environment variable option "nodosfilewarning" turns off this
>>> warning.
>>> Consult the user's guide for more details about POSIX paths:
>>> http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
>> Would it be possible to make the check exclude common character escapes?
> No, but it probably is an upstream bug the bash-completion package worth
> reporting and fixing. Can you use 'set -vx' just before typing the
> command that triggers the message, so I can see which command in the
> completion function is insufficiently quoting the pathname such that a
> glob completion is being inappropriately attempted on escape characters?
I don't have bash-completion(s) installed.
If set -vx would be useful with vanilla bash, I'm happy to try it, though.
Regards,
Ryan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2011-04-15 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 9:09 Ryan Johnson
2011-04-14 12:05 ` Christopher Faylor
2011-04-14 18:07 ` Eric Blake
2011-04-16 7:27 ` Ryan Johnson [this message]
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=4DA8D6D6.9090601@ece.cmu.edu \
--to=ryanjohn@ece.cmu.edu \
--cc=cygwin@cygwin.com \
--cc=eblake@redhat.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).