public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Mark Hansen <cygwin@mehconsulting.com>, cygwin@cygwin.com
Subject: Re: The Cygwin User Guide on path names
Date: Fri, 26 Aug 2016 13:19:00 -0000	[thread overview]
Message-ID: <1647564591.20160826153222@yandex.ru> (raw)
In-Reply-To: <41bbca20-2b04-abba-4329-aefa7600cd13@mehconsulting.com>

Greetings, Mark Hansen!

> On 8/25/2016 7:53 PM, Andrey Repin wrote:
>> Greetings, Linda Walsh!
>>
>>> Andrey Repin wrote:
>>>> Greetings, Ken Brown!
>>>>
>>>>> The documentation also says, "The usage of Win32 paths, though possible,
>>>>> is deprecated...."  I wonder if this should be strengthened to say
>>>>> something like, "The usage of Win32 paths, though possible, is strongly
>>>>> deprecated and may be removed in a future release of Cygwin."
>>>>
>>>> That would be the day Cygwin die for me.
>>>> --
>>>> With best regards, Andrey Repin
>>>> Wednesday, August 24, 2016 12:50:55
>>>> Sorry for my terrible english...
>>> ---
>>
>>> Curious -- but why?  How do you make use of win32 pathnames
>>> ( "C:\bin" versus "/bin" or "/c/bin" or "/cygdrive/c/bin" )
>>> depending on how your cygwin is configured).
>>
>> I make use of win32 paths directly.
>> diff and grep are the most used tools.
>>
>>> I'm wondering if maybe there is a misunderstanding?
>>
>> I don't think so.
>>
>>> For the most part -- many cygwin apps may not work
>>> correctly if given a win32 path in the same place you'd
>>> put a *nix path due to the backslashes being turned into
>>> quote sequences.
>>
>> That's too bad for such poor apps.
>>
>>> I mean, you can't type:
>>
>>>> ls C:\bin
>>>   (instead of )
>>>> ls /c/bin

> Can we differrentiate between C:/bin and C:\bin?

> I've always used C:/bin. Using drive identifiers and UNIX-style path separators.

> Is the proposal that this no longer be valid under cygwin?

There's (hopefully) no such proposal. Only a warning that it may not work in
all cases.


Also, @ Linda, the string escaping is done by the shell before passing
arguments to the command, as I understand.
If I'm starting an application not from shell, the app, being a good citizen,
should not second-guess the arguments it is given.


-- 
With best regards,
Andrey Repin
Friday, August 26, 2016 15:29:53

Sorry for my terrible english...


--
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

  reply	other threads:[~2016-08-26 12:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 16:25 Ken Brown
2016-08-23 16:35 ` Corinna Vinschen
2016-08-24 15:02 ` Andrey Repin
2016-08-25 17:54   ` Linda Walsh
2016-08-26  8:05     ` Andrey Repin
2016-08-26 13:08       ` Mark Hansen
2016-08-26 13:19         ` Andrey Repin [this message]
2016-08-29  2:07           ` Linda Walsh
2016-08-29 11:00             ` Mark Hansen
2016-08-29 11:15               ` Mark Hansen
2016-08-29 16:10             ` Andrey Repin
2016-08-26 13:50         ` Mark Hansen

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=1647564591.20160826153222@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@mehconsulting.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).