Hi Patrick,
Thanks so much for this detailed explanation. I use bash so everything
should work fine. I have so much to learn. Thanks :)
Jon
Patrick Horgan wrote:
See the info manual for bash under 3.5.3 Shell Parameter Expansion.
You could also do:
srcfile=${1##*/}# subt
Jonathan Kulp wrote:
Nice!
Thanks for this, Patrick! It works just right. Now I have to look at
it to figure out *why* it works the way it does ;-) I haven't used
that sort of construct before...
Jonathan
Patrick Horgan wrote:
Instead of basename you could use the built
___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
--
View this message in context:
http://www.nabble.com/Lilypond---Ubuntu-Help-tp19022704p19035652.html
Sent from the Gnu -
Nice! Thanks for this, Patrick! It works just right. Now I have to
look at it to figure out *why* it works the way it does ;-) I haven't
used that sort of construct before...
Jonathan
Patrick Horgan wrote:
Instead of basename you could use the built in string manipulation stuff
this:
#
Jonathan Kulp wrote:
Ah. It never occurred to me to try to allow for anything but the
standard "lilypond filename.ly" command. That's a good idea. I don't
use anything but the standard command very often, though, so I won't
lose any sleep over it. I *was* prepared to lose sleep over the fac
Ah. It never occurred to me to try to allow for anything but the
standard "lilypond filename.ly" command. That's a good idea. I don't
use anything but the standard command very often, though, so I won't
lose any sleep over it. I *was* prepared to lose sleep over the fact
that the output fil
On Sun, Aug 17, 2008 at 7:03 PM, Jonathan Kulp <[EMAIL PROTECTED]> wrote:
> Ok I've come up with a completely different script that does what I
> *thought* the original one was supposed to do. Searching around I found a
> couple of commands that make the entire thing simpler and easier for me to
>
Ok I've come up with a completely different script that does what I
*thought* the original one was supposed to do. Searching around I found
a couple of commands that make the entire thing simpler and easier for
me to understand. I don't really understand how to use sed and only
used it b/c I
Jonathan Kulp gmail.com> writes:
>
> Well, my face is red. Just tried my script from a different directory
> and it doesn't put the output in the right place. I guess I've always
> just cd'd to the right dir before running the script. Sorry about that!
> I'll see if I can make it work rig
Well, my face is red. Just tried my script from a different directory
and it doesn't put the output in the right place. I guess I've always
just cd'd to the right dir before running the script. Sorry about that!
I'll see if I can make it work right. Just have to figure out how to
capture t
All of the output goes to your current working directory unless you
specify otherwise. So, if you cd ~/Desktop as Graham suggests, then
it'll end up there.
If you're interested, you can try this little script I wrote that
automatically places all of the output in the same directory as the
li
On Sun, 17 Aug 2008 12:44:20 -0700 (PDT)
George_ <[EMAIL PROTECTED]> wrote:
> I created a lilypond file on my Desktop, called, say, Test.ly. I go
> to the terminal and type in
>
> lilypond --pdf /home/george/Desktop/Test.ly
why not
cd ~/Desktop
lilypond Test.ly
? pdf is created by default.
>
message in context:
http://www.nabble.com/Lilypond---Ubuntu-Help-tp19022704p19022704.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
13 matches
Mail list logo
