Richard Lyons <[EMAIL PROTECTED]>:
> On Thu, Nov 01, 2007 at 01:49:03PM -0700, Mike Bird wrote:
> > On Thursday 01 November 2007 13:07, Wei Chen wrote:
> > > I would like to write a bash script like the following one:
> > >
> > > for i in `some program that outputs a word list`
> > > do
> > > ec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Bird wrote:
> On Thursday 01 November 2007 13:07, Wei Chen wrote:
>> I would like to write a bash script like the following one:
>>
>> for i in `some program that outputs a word list`
>> do
>> echo $i
>> done
>>
>> where the word list can be ver
On 11/01/07 15:07, Wei Chen wrote:
> Hi,
>
> I would like to write a bash script like the following one:
>
> for i in `some program that outputs a word list`
> do
> echo $i
> done
>
> where the word list can be very very long. I wonder what is the upper bound
> limit of the length of word list
On Thu, Nov 01, 2007 at 01:49:03PM -0700, Mike Bird wrote:
> On Thursday 01 November 2007 13:07, Wei Chen wrote:
> > I would like to write a bash script like the following one:
> >
> > for i in `some program that outputs a word list`
> > do
> > echo $i
> > done
> >
> > where the word list can be
On Thursday 01 November 2007 13:07, Wei Chen wrote:
> I would like to write a bash script like the following one:
>
> for i in `some program that outputs a word list`
> do
> echo $i
> done
>
> where the word list can be very very long. I wonder what is the upper bound
> limit of the length of wor
Hi,
I would like to write a bash script like the following one:
for i in `some program that outputs a word list`
do
echo $i
done
where the word list can be very very long. I wonder what is the upper bound
limit of the length of word lists in "for" loop of a bash script, or
does it only
depend
>
> Are we trying to optimize the thrown together? How about one (1) line
> for both ???
>
> echo $file | sed 's!^.*/!!;s!\..*$!!'
>
sed is powerful but I prefer the simplest way:
basename $file .mp3
Romuald DELAVERGNE wrote:
>
> On 2001.11.08 23:44 Michael D. Schleif wrote:
>
> You can use 'basename' command to remove complete path.
Are we trying to optimize the thrown together? How about one (1) line
for both ???
echo $file | sed 's!^.*/!!;s!\..*$!!'
--
Best Regards,
mds
mds
On 2001.11.08 23:44 Michael D. Schleif wrote:
You can use 'basename' command to remove complete path.
On Thu, Nov 08, 2001 at 04:44:15PM -0600, Michael D. Schleif wrote:
| Stephen Gran wrote:
[ specification ]
| How about this?
|
|
| #!/bin/sh
| DIR=/home/mds
| for dir in `find $DIR -type d | sort`
| do
| echo $dir
| echo
| for file in `find $dir -maxdepth 1 -type f | so
On Thu, Nov 08, 2001 at 17:24, Stephen Gran wrote:
> Hello all,
> What I'd like to end up with is a short script that will scan my music
> directories and output to a file. I'd like this to strip off the full
> path and any ending extension, and ideally leave a blany\k line in
> between directorie
Thus spake Michael D. Schleif:
>
> Stephen Gran wrote:
> >
> > Hello all,
> > What I'd like to end up with is a short script that will scan my music
> > directories and output to a file. I'd like this to strip off the full
> > path and any ending extension, and ideally leave a blany\k line in
>
Stephen Gran wrote:
>
> Hello all,
> What I'd like to end up with is a short script that will scan my music
> directories and output to a file. I'd like this to strip off the full
> path and any ending extension, and ideally leave a blany\k line in
> between directories. The best I can do so fa
Hello all,
What I'd like to end up with is a short script that will scan my music
directories and output to a file. I'd like this to strip off the full
path and any ending extension, and ideally leave a blany\k line in
between directories. The best I can do so far is :
ls -R /home/mp3 | (read fil
14 matches
Mail list logo
