public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Waldor Michael (K3/EMW4)" <Michael.Waldor@de.bosch.com>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: B20: Bug? backslashes and stars within args of ls
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <D9DA0A516892D111B3410000F8CB2C4401403D61@si13838.si.bosch.de> (raw)
Message-ID: <19990331194500.ewE2R45ZLgsMwZLYmdPvk99MrqykPLy7xX0YVMYKv_s@z> (raw)

If one combines backslashes and stars within filenames as argument for ls,
the stars are NOT expanded if they occur next to a backslash:


(C:/temp/fdr is a directory containing some files.)

ok: ls c:/temp/fdr
ok: ls c:/temp/f*
ok: ls c:\\temp\\fdr
ok: ls c:\temp\fdr

not ok: ls c:\\temp\\f*
//i/programme/mm3/util/ls: c:\temp\f*: No such file or directory

not ok: ls c:\temp\f*
//i/programme/mm3/util/ls: c:tempf*: No such file or directory

ok: ls c:\\temp/f*


I'm running ls within cmd.exe from NT 4.0


I would like to call ls like

ls c:\temp/f*

i.e. with SINGLE backslash.


Maybe there is a environment variable to control cygwin's behaviour?



M. Waldor


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


             reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-03  0:34 Waldor Michael (K3/EMW4) [this message]
1999-03-31 19:45 ` Waldor Michael (K3/EMW4)
1999-03-03  7:52 Earnie Boyd
     [not found] ` < 19990303155126.14113.rocketmail@send1e.yahoomail.com >
1999-03-04  8:08   ` Chris Faylor
1999-03-31 19:45     ` Chris Faylor
1999-03-31 19:45 ` Earnie Boyd

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=D9DA0A516892D111B3410000F8CB2C4401403D61@si13838.si.bosch.de \
    --to=michael.waldor@de.bosch.com \
    --cc=cygwin@sourceware.cygnus.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).