On Thu, Dec 07, 2006 at 06:34:39AM -0600, Martin McCormick wrote:
[..]
You are responding to a thread in name only. You should list reply to a
previous message in the thread. Sorry for being picky, but when I saw
Re: I wondered why my threaded mail reader was 'playing up'.
The MUA should put
I finally fixed the problem I was having with the shell
variable in double quotes and my face is a bit red, but not too
red.
It appears that the output of the cdda2wav file had a tab
preceeding each song title to make it print nice and pretty. I
successfully removed all the extra
Just to make this question a little simpler and filter
out the distracters, the problem appears to be that placing
double quotes around a variable name in a Bourne shell script causes
a horizontal tab to be prepended to the rest of the string.
In the case I described in earlier pos
Bill Marcum writes:
> Try this:
> echo "$songfilename" | od -to1z
It suddenly hit me that you suggested I put the "'s
around the variable name when I did the test so I did and I think
we've got the culprit though I am not sure what to do to fix it.
This time I tried
echo "$songfilename"
Hmm.
Bill Marcum writes:
> How does your script create the file names?
It initially gets it from the index number of the audio file
that cdda2wav generates plus the Tracktitle= line that appears in
one of the audio_NN.inf files. In this case, audio_01.inf which
contains many information
On Wed, Dec 06, 2006 at 12:05:52PM -0600, Martin McCormick wrote:
> I am working on a shell script that generates file names
> to use with bladeenc. Everything works right except that every
> single music file the script creates via bladeenc has a ? or
> question mark preceding the words of
6 matches
Mail list logo
