From: Colin Peters <colin@bird.fu.is.saga-u.ac.jp>
To: "'Weiqi Gao'" <weiqigao@a.crl.com>
Cc: "'GNU-Win32'" <gnu-win32@cygnus.com>
Subject: RE: CONTINUING Elementary Problems with Find
Date: Wed, 22 Oct 1997 23:44:00 -0000 [thread overview]
Message-ID: <01BCDFCA.70BDB540@gbird0> (raw)
Weiqi Gao[SMTP:weiqigao@a.crl.com] wrote:
>Watch out for the shell, because the shell has the first stab at the
>command line. If you are using the Windows 95 COMMAND.COM shell, then
>*.c gets expanded to:
> i) a list of your .c files in the current directory; --OR--
> ii) if there are no .c files in the current directory, *.c
Sorry to pick nits, but this is not strictly true. Under Win95
the startup code of a program gets the command line unaltered
and performs "globbing" to create the argv list. Most (but not
all) Win95 programs do the globbing you describe (because
thats the kind that MS compilers' startup code does). I could
give you a program that runs under Win95 command.com and
does not perform globbing.
With all this said, your main point is correct. It's probably
the shell (or the startup code) expanding *.c that's messing
him up.
Sorry again,
Colin.
-- Colin Peters - Saga Univ. Dept. of Information Science
-- colin@bird.fu.is.saga-u.ac.jp - finger for PGP public key
-- http://www.fu.is.saga-u.ac.jp/~colin/index.html
-- http://www.geocities.com/Tokyo/Towers/6162/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-10-22 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-22 23:44 Colin Peters [this message]
1997-10-23 9:23 ` Weiqi Gao
-- strict thread matches above, loose matches on Subject: below --
1997-10-23 6:10 Earnie Boyd
1997-10-22 20:35 Robert Seeger
1997-10-22 7:51 GBradfor
1997-10-22 18:52 ` gnu-win32-request
1997-10-22 22:14 ` Weiqi Gao
1997-10-23 14:42 ` Michael Hirmke
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=01BCDFCA.70BDB540@gbird0 \
--to=colin@bird.fu.is.saga-u.ac.jp \
--cc=gnu-win32@cygnus.com \
--cc=weiqigao@a.crl.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).