public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: cygpath
Date: Fri, 10 Feb 2017 23:17:00 -0000	[thread overview]
Message-ID: <e84da808-cba0-589d-d1ec-58f64d8eb351@cs.umass.edu> (raw)
In-Reply-To: <91DCAC3CB99C724EB365BB64677FBE7B139AF9@MX204CL04.corp.emc.com>

On 2/10/2017 3:03 PM, Gluszczak, Glenn wrote:
> * is a legal character for ls but perhaps not cygpath?  I don't know.
> No files or directories are using * in the name.
>
> Not sure about incorrect terminal settings as I never touched any.
> It shows up in mintty and ssh equally. The characters that appear vary.
>
> Some non-existent paths do *not* produce the gibberish.
>
> %%%cygpath -w /aaa/bbb/*
> C:\cygwin\aaa\bbb\

Yes, but I found something interesting when I did this:

echo "$(cygpath -w /usr/non-existent/*)" > mytemp

od -c mytemp

revealed that there is a three-byte sequence after the
output of

C:\cygwin\usr\non-existent\

and before the newline added by echo.  I guess it's
some representation of * that does not show up on the
terminal, but it did strike me as a little strange ...

Regards - EM

--
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-10 23:17 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 19:07 cygpath Gluszczak, Glenn
2017-02-10 19:50 ` cygpath Andrey Repin
2017-02-10 20:04   ` cygpath Gluszczak, Glenn
2017-02-10 20:31     ` cygpath Gluszczak, Glenn
2017-02-10 20:42       ` cygpath Michael Enright
2017-02-10 20:47         ` cygpath Michael Enright
2017-02-10 20:52         ` cygpath Gluszczak, Glenn
2017-02-10 21:35     ` cygpath Andrey Repin
2017-02-10 21:47       ` cygpath Gluszczak, Glenn
2017-02-10 21:54         ` cygpath Michael Enright
2017-02-10 21:55       ` cygpath Michael Enright
2017-02-10 23:17     ` Eliot Moss [this message]
2017-02-10 23:50       ` cygpath Sam Edge
2017-02-11  0:05         ` cygpath Eliot Moss
2017-02-11  0:45           ` cygpath Sam Edge
2017-02-10 20:37   ` cygpath Michael Enright
2017-02-13 17:29   ` cygpath Nellis, Kenneth (Conduent)
2017-02-14  8:47     ` cygpath Corinna Vinschen
2017-02-15 14:41       ` cygpath Nellis, Kenneth (Conduent)
2017-02-15 15:29         ` cygpath Corinna Vinschen
2017-02-11 18:19 ` cygpath Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2011-03-02 14:10 cygpath Jim P
2011-03-02 14:16 ` cygpath Edward Lam
2011-03-02 14:19 ` cygpath Roger K. Wells
     [not found] <pdy988306100538bcc77a8d4986@[209.128.98.50]>
2004-05-12 16:32 ` cygpath Joshua Daniel Franklin
2004-05-12 17:58   ` cygpath Dave Korn
2004-05-12 19:00   ` cygpath Christopher Faylor
2004-05-12 19:30   ` cygpath Igor Pechtchanski
     [not found] <19981114183901.22135.rocketmail@send104.yahoomail.com>
1998-11-17 12:51 ` cygpath Laurent Charles
1998-11-12 16:07 cygpath Earnie Boyd
1998-11-12 17:30 ` cygpath Rick Rankin
     [not found] <36484B31.A6089DF.cygnus.gnu-win32@st.com>
1998-11-11  8:01 ` cygpath DJ Delorie
1998-11-11  4:22 cygpath Earnie Boyd
1998-11-12  3:32 ` cygpath Rick Rankin
1998-11-10  6:18 cygpath Laurent Charles
1998-11-12  3:32 ` cygpath Rick Rankin
1998-11-13  2:57 ` cygpath Laurent Charles

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=e84da808-cba0-589d-d1ec-58f64d8eb351@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).