From: John Cook <john.cook@kla-tencor.com>
To: "'gnuwin32'" <gnu-win32@cygnus.com>
Subject: bash problems: with cp with a for loop
Date: Wed, 15 Oct 1997 15:59:00 -0000 [thread overview]
Message-ID: <c=US%a=_%p=KLA_Instruments_%l=SJEXCHANGE3-971015225447Z-5357@sjexchange.kla-tencor.com> (raw)
Hi.
The following works with bash 1.14.0(5) under SCO but
not with bash-1.14.7(5) under gnuwin32 (i.e., the bash
that came with b18).
for fname in `ls`
do cp $fname /tmp; done
I get an error such as the following for each filename
`ls` spits out:
cp: Acr99.tmp: No such file or directory
Can anyone tell me what I'm doing wrong or if this is a
known problem with gnuwin32 bash?
--John
(novice shell programmer, trying to escape from CMD.EXE)
-
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-15 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-15 15:59 John Cook [this message]
1997-10-15 16:39 John Cook
1997-10-16 4:37 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='c=US%a=_%p=KLA_Instruments_%l=SJEXCHANGE3-971015225447Z-5357@sjexchange.kla-tencor.com' \
--to=john.cook@kla-tencor.com \
--cc=gnu-win32@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).