Hello, all. As previously noted, I just got hitched. I've also got a
bunch of pictures, now (good ones, too!), and I'd like to munge 'em down
small with convert or mogrify or somesuch. However, I've got spaces
in the filenames. While it would be moderately trivial to s/ /_/g; I
would prefer
You acn specify to many of the utils like find and xargs
that they only consider a NULL to terminate a pathname.
Example:
find . -print0 | xargs --null ls -ladF
*
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
On Fri, 17 May 2002, at 7:55am, Ken Ambrose wrote:
Unfortunately, it takes each seperate word as a different paramater. I
-know- I've done this before, but I just can't remember how. Suggestions?
Place variables which may contain shell special characters in double
quotes, i.e.,
In a message dated: Fri, 17 May 2002 07:55:40 PDT
Ken Ambrose said:
for i in *
do
mogrify -geometry 30%x30% $i
echo Done with $i
done
Unfortunately, it takes each seperate word as a different paramater. I
-know- I've done this before, but I just can't remember how. Suggestions?
Place the $i
On Fri, 17 May 2002, Ken Ambrose wrote:
for i in *
do
mogrify -geometry 30%x30% $i
echo Done with $i
done
Unfortunately, it takes each seperate word as a different paramater. I
-know- I've done this before, but I just can't remember how. Suggestions?
The easiest way I can think to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Ken Ambrose hath spake thusly:
Hello, all. As previously noted, I just got hitched. I've also got a
bunch of pictures, now (good ones, too!)
You should post a link to them when you're done!
, and I'd like to munge 'em
On Fri, 17 May 2002, at 4:08pm, Derek D. Martin wrote:
Some (like me) would argue that the right way *is* to remove the spaces
from your filenames.
Computers are a tool to be used by people, not the other way around. :-)
--
Ben Scott [EMAIL PROTECTED]
| The opinions expressed in this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Benjamin Scott hath spake thusly:
On Fri, 17 May 2002, at 4:08pm, Derek D. Martin wrote:
Some (like me) would argue that the right way *is* to remove the spaces
from your filenames.
Computers are a tool to be used by
On Fri, May 17, 2002 at 04:14:33PM -0400, Benjamin Scott wrote:
On Fri, 17 May 2002, at 4:08pm, Derek D. Martin wrote:
Some (like me) would argue that the right way *is* to remove the spaces
from your filenames.
Computers are a tool to be used by people, not the other way around. :-)
Especially in the Unix/Linux environment, I think that creating files or
directories with spaces is ill advised, but there is a reality. Many
Windows users are migrating to Linux, and are bringing their habits with
them. Additionally, we tend to share file systems with Windows by importing
or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Jerry Feldman hath spake thusly:
Especially in the Unix/Linux environment, I think that creating files or
directories with spaces is ill advised, but there is a reality. Many
Windows users are migrating to Linux, and are
Derek D. Martin [EMAIL PROTECTED] writes:
Personally, I wish operating systems would limit the characters that
can be used in filenames to [A-Za-z0-9.:_=+-]+ or something very
similar. There's no good reason why other characters NEED to be
allowed, The only reason I included as much
12 matches
Mail list logo
