public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygpath 2.6.0: -m " C:" and garbled output
Date: Thu, 06 Oct 2016 20:47:00 -0000	[thread overview]
Message-ID: <87zimhp9df.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAFKkpzpSu7bOCKf3uAwHrEiHcs5M9RCzVV4o2V=Lpo7PrgnGJg@mail.gmail.com>	(Andre Maroneze's message of "Thu, 6 Oct 2016 14:38:41 +0200")

Andre Maroneze writes:
> I just noticed a difference in behavior between versions 2.5.2 and
> 2.6.0 of cygpath (the ones I could test): if I run
>
> cygpath -m " C:"
>
> (notice the space before the C, inside the double quotes)

A filename can legitimately start with a space and it is a relative
filename in that case.  So dropping the space just to get something that
looks like a drive letter is wrong.

> In cygpath 2.6.0, this outputs C? (C followed by the unicode character
> 0xF03A, which is a ":" (0x3A) character, but prefixed with "F0").

That's how the otherwise forbidden ":" character gets encoded into the
filename.

> In cygpath 2.5.2 (and 2.4.1, which I also could test), it outputs C:,
> as I would expect.

No, that's wrong as explained above.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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:[~2016-10-06 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 14:51 Andre Maroneze
2016-10-06 19:26 ` Ken Brown
2016-10-06 20:47 ` Achim Gratz [this message]
2016-10-06 22:57   ` Andre Maroneze

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=87zimhp9df.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).