Lo, on Sunday, May 20, Viktor Rosenfeld did write:
> Martin Fluch wrote:
>
> > > Of course, some people argue, that spaces in filenames is a Bad
> > > Thing(tm), but I fail to see why.
> >
> > Could exactly this be the reason, why spaces in filenames are considered
> > as a bad thing, since they
On Mon, May 21, 2001 at 01:59:18AM +0200, Viktor Rosenfeld wrote:
| D-Man wrote:
|
| > | On Sun, 20 May 2001, Viktor Rosenfeld wrote:
| > | >
And-I-have-yet-to-see-somebody-who-replaces-all-spaces-with-dashes-or-dots.
| >
| > Check the archives for python-list@python.org (aka comp.lang.python).
Hejsan!
> Okay, so what you're saying is that you prefer efficient parsing of a
> script, while I prefer the aestheticy (sp?) provided by spaces.
> Obviously, there's a trade-off between the two, and we emphasize
> different aspects. So there are some points to the arguement that
> Spaces In Fil
John Hasler wrote:
>
> Viktor Rosenfeld writes:
> > ...my suggestion of improved readability is also valid and therefore one
> > could argue that Spaces In Filenames(tm) is a Good Thing(tm).
>
> > Now, how is that for a compromise, eh? Damn, am I good. Peace brothers,
> > peace!
> Nah. Let's
Viktor Rosenfeld writes:
> ...my suggestion of improved readability is also valid and therefore one
> could argue that Spaces In Filenames(tm) is a Good Thing(tm).
> Now, how is that for a compromise, eh? Damn, am I good. Peace brothers,
> peace!
Nah. Let's argue some more. If you can't name
Aem,
D-Man wrote:
> | On Sun, 20 May 2001, Viktor Rosenfeld wrote:
> | >
> And-I-have-yet-to-see-somebody-who-replaces-all-spaces-with-dashes-or-dots.
>
> Check the archives for python-list@python.org (aka comp.lang.python).
> Tim Peters (and others) routinely close their posts with a long
> se
Bruce Sass wrote:
> > But, this trouble is easily avoided with double quotes and on the flip
> > side, spaces make things much more readable.
> > IMeanIt'SNotLikeWeDon'tUseSpacesInNormalWriting.
> > And-I-have-yet-to-see-somebody-who-replaces-all-spaces-with-dashes-or-dots.
> > See.what.I.mean?
>
| On Sun, 20 May 2001, Viktor Rosenfeld wrote:
| > And-I-have-yet-to-see-somebody-who-replaces-all-spaces-with-dashes-or-dots.
Check the archives for python-list@python.org (aka comp.lang.python).
Tim Peters (and others) routinely close their posts with a long
sentence using dashes instead of spac
On Sun, 20 May 2001, Viktor Rosenfeld wrote:
> Martin Fluch wrote:
>
> > > Of course, some people argue, that spaces in filenames is a Bad
> > > Thing(tm), but I fail to see why.
> >
> > Could exactly this be the reason, why spaces in filenames are considered
> > as a bad thing, since they easily l
Martin Fluch wrote:
> > Of course, some people argue, that spaces in filenames is a Bad
> > Thing(tm), but I fail to see why.
>
> Could exactly this be the reason, why spaces in filenames are considered
> as a bad thing, since they easily lead into trouble?
But, this trouble is easily avoided wi
s: I want to process
> >>multiple files, e.g. symlinking a bunch or converting graphics.
> >>
> >>for i in *;do 'ln -s $i /home/newdir/$i';done
> > ^^^ ^^^
> >
> >You need grave accents here.
>
> Ouch! You don&#
On Sun, 20 May 2001, Philipp Lehman <[EMAIL PROTECTED]> wrote:
>On Sun, 20 May 2001, Hans <[EMAIL PROTECTED]> wrote:
>
>>I still don't understand the proper syntax for this: I want to process
>>multiple files, e.g. symlinking a bunch or converting graphics.
On Sun, 20 May 2001, Hans <[EMAIL PROTECTED]> wrote:
>I still don't understand the proper syntax for this: I want to process
>multiple files, e.g. symlinking a bunch or converting graphics.
>
>for i in *;do 'ln -s $i /home/newdir/$i';done
^^^
> Several folks have already suggested, that you just need to get rid of
> the '' quotes. However, if some files have spaces in their file name,
> you actually do need quotes, like this.
>
> for i in *; do ln -s "$i" "/home/newdir/$i"; done
>
Hi Hans,
Hans wrote:
> I still don't understand the proper syntax for this: I want to process
> multiple files, e.g. symlinking a bunch or converting graphics.
>
> for i in *;do 'ln -s $i /home/newdir/$i';done
>
> won't work.
Several folks have alread
Hans <[EMAIL PROTECTED]> writes:
> I still don't understand the proper syntax for this: I want to process
> multiple files, e.g. symlinking a bunch or converting graphics.
>
> for i in *;do 'ln -s $i /home/newdir/$i';done
Other people have explained about the q
Hans wrote:
>
> I still don't understand the proper syntax for this: I want to process
> multiple files, e.g. symlinking a bunch or converting graphics.
>
> for i in *;do 'ln -s $i /home/newdir/$i';done
you got some responses already but here's some m
> for i in *;do 'ln -s $i /home/newdir/$i';done
> won't work.
You're close. Get rid of the quotes.
-- Kevin
Hans <[EMAIL PROTECTED]> writes:
> I still don't understand the proper syntax for this: I want to process
> multiple files, e.g. symlinking a bunch or converting graphics.
>
> for i in *;do 'ln -s $i /home/newdir/$i';done
>
> won't work.
This tr
I still don't understand the proper syntax for this: I want to process
multiple files, e.g. symlinking a bunch or converting graphics.
for i in *;do 'ln -s $i /home/newdir/$i';done
won't work.
Could someone please explain the rules for doing stuff like this, e.g. when
to
20 matches
Mail list logo
