From: Scott Taylor <scott@dctchambers.com>
To: linux-admin@vger.kernel.org
Subject: Re: Stupid spaces
Date: Fri, 13 Feb 2004 08:33:33 -0800 [thread overview]
Message-ID: <5.2.1.1.0.20040213082821.00acdce8@mustang> (raw)
In-Reply-To: <Pine.LNX.4.44.0402121811240.3031-100000@deadrat.localdomai n>
At 06:15 PM 02/12/2004, rich+ml@lclogic.com wrote:
>How about:
>
> for x in *; do mv $x ${x// /_}; done
That's kinda what I was thinking, only problem with that is, the file named
"blah blah.p" will cause an error as bash/sh/ksh will think it is two files.
mv: cannot stat `blah': No such file or directory
mv: cannot stat `blah.p': No such file or directory
even tried using `ls -c1` same thing. Worse thing is I know I did this
before, so long ago, maybe I used Perl after all. Hmm...
next prev parent reply other threads:[~2004-02-13 16:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 21:08 Stupid spaces Scott Taylor
2004-02-12 21:23 ` Alok K. Dhir
2004-02-12 22:19 ` Scott Taylor
2004-02-12 21:39 ` Yu Chen
2004-02-12 22:18 ` Scott Taylor
2004-02-13 2:15 ` rich+ml
2004-02-13 4:07 ` Emiliano Castagnari
2004-02-13 16:56 ` Scott Taylor
2004-02-13 6:51 ` Agus Budy Wuysang
2004-02-13 17:15 ` Scott Taylor
[not found] ` <Pine.LNX.4.44.0402121811240.3031-100000@deadrat.localdomai n>
2004-02-13 16:33 ` Scott Taylor [this message]
2004-02-13 17:26 ` rich+ml
[not found] ` <Pine.LNX.4.44.0402130907370.3031-100000@deadrat.localdomai n>
2004-02-13 17:33 ` Scott Taylor
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 19:13 urgrue
2004-07-19 13:29 calin
2004-07-19 13:56 ` Chris DiTrani
2004-07-19 14:59 ` calin
2004-07-19 14:45 ` Scott Taylor
2004-07-19 14:52 ` Scott Taylor
2004-07-20 17:48 ` scohen
2004-07-20 18:22 ` Adam Lang
2004-07-20 17:55 ` scohen
2004-07-20 18:20 ` Chris DiTrani
2004-07-20 18:37 ` Adam Lang
2004-07-21 2:28 ` Glynn Clements
2004-07-21 7:11 ` calin
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=5.2.1.1.0.20040213082821.00acdce8@mustang \
--to=scott@dctchambers.com \
--cc=linux-admin@vger.kernel.org \
/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