public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth (Conduent)" <Kenneth.Nellis@conduent.com>
To: cyg Simple <cygsimple@gmail.com>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: cygpath (reprised)
Date: Mon, 27 Feb 2017 14:03:00 -0000	[thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A704BBEF6E6@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <a012307e-c235-8571-97e8-019719058366@gmail.com>

From: cyg Simple 
> On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote:
> > I suppose one could argue that, by using -w, that cygpath might assume that it
> > is converting *from* a POSIX path, and therefore the colon would not indicate
> > a drive letter--wouldn't that make sense?--but I’ll let someone else take up
> > that battle. ☺
> 
> I would almost agree except for the help description of the -w option.
> ...

Hmm. Not sure that I see that. From the man page:

The cygpath program is a utility that converts Windows native filenames to Cygwin 
POSIX-style pathnames and vice versa.

I read this as converting one format to the other.

--Ken Nellis

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


  parent reply	other threads:[~2017-02-27 14:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 17:22 Nellis, Kenneth (Conduent)
2017-02-21 18:05 ` Andrey Repin
2017-02-21 18:22   ` Nellis, Kenneth (Conduent)
2017-02-25 16:38     ` cyg Simple
2017-02-26  1:20       ` Andrey Repin
2017-02-28 19:56         ` cyg Simple
2017-03-01 13:20           ` Andrey Repin
2017-03-01 14:33             ` cyg Simple
2017-02-27 14:03       ` Nellis, Kenneth (Conduent) [this message]
2017-02-28 20:15         ` cyg Simple

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=0D835E9B9CD07F40A48423F80D3B5A704BBEF6E6@USA7109MB022.na.xerox.net \
    --to=kenneth.nellis@conduent.com \
    --cc=cygsimple@gmail.com \
    --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).