From: Baho Utot on
Sidney Lambe wrote:

[putolin]

> mv $(locate gfortran.pdf) <destination directory>
>
> The $() tells bash to feed the results of the enclosed command
> to mv.
>

No it doesn't
From: Sidney Lambe on
On comp.os.linux.misc, Harald Meyer <meyersharald(a)googlemail.com> wrote:
> Sidney Lambe wrote:
>
>> Filenames with whitespaces is a Windows idiocy.
>
> Yes. But sometimes one has to exchange files with Windows users,

Then you run them through a filter that changes the white spaces
to underscores. Just like you run them through a filter to
remove the CR/LFs.

> or a Linux box is a fileserver for Windows clients,

No one has to do that.

> so every script hould be able to handle filenames with spaces.

None of mine will except by accident. And they never will.

>> (Another technocrat trying to turn Linux into Windows.)
>
> No, just somebody who takes care.

Takes care to make Linux cater to Windows instead of the
other way around.

Someone who is more interested in money than they are
in Linux.

Sid

From: Keith Keller on
On 2010-04-11, Harald Meyer <meyersharald(a)googlemail.com> wrote:
> Chris F.A. Johnson wrote:
>> On 2010-04-11, unruh wrote:
>
>>> function rm () { cp $* /tmp; /bin/rm $* ;}
> ^
>> rm() { cp "$@" /tmp; /bin/rm "$@"; }
> ^
> May I suggest to use "&&" instead of ";" ?

Wouldn't mv be slightly better than cp && rm, since that's basically
what mv does (across filesystems, anyway)? (And if this happens to be
on the same fs then mv will be even better.)

--keith


--
kkeller-usenet(a)wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

From: Keith Keller on
On 2010-04-11, Sidney Lambe <sidneylambe(a)nospam.invalid> wrote:
>
> Filenames with whitespaces is a Windows idiocy.

Not all of us are fortunate enough not to work with Windows idiots.

> I don't allow them on my box.

What, you have a badly-written shell script that scans every filename as
it's written? Either that or you have no friends and therefore don't
need any way of enforcing no spaces in filenames.

> (Another technocrat trying to turn Linux into Windows.)

FWIW, some silly programs for Linux come with files with spaces. (Most,
if not all, of these programs I've seen are cross-platform, primarily
written for Windows and ported to linux/OS X, where the vendor didn't
bother to use sensible file names.)

--keith



--
kkeller-usenet(a)wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

From: Sidney Lambe on
On comp.os.linux.misc, Keith Keller
<kkeller-usenet(a)wombat.san-francisco.ca.us> wrote:

> On 2010-04-11, Sidney Lambe <sidneylambe(a)nospam.invalid> wrote:
>
>> Filenames with whitespaces is a Windows idiocy.
>
> Not all of us are fortunate enough not to work with Windows
> idiots.
>
>> I don't allow them on my box.
>
> What, you have a badly-written shell script that scans every
> filename as it's written? Either that or you have no friends
> and therefore don't need any way of enforcing no spaces in
> filenames.

Another dickless punk who takes cheap shots at people while
he hides behind the Internet.

In the real world this loser would call me "sir" when he
was finished mowing my lawn.

<plonk>

[delete]

Sid