Re: ver. 2.11.56 problems

[Carl Sorensen]

Tom Cloyd <tomcloyd <at> comcast.net> writes:

> 
> This isn't a path problem, I think. "lilypond -h" may not be quite
> right, but I should have gotten something other than what I got, if the
> "lilypond" script that IS in the dir executed. Here's the script -
> 

Tom,

You can tell if it's a path problem by typing

which lilypond

It will tell you the directory from which lilypond is run.

If it's not ~/bin, then you will want to apply James's solution, but
with one change -- you need to put /home/tomc/bin *before* $PATH

PATH=/home/tomc/bin:$PATH
export PATH

You can try doing it from the command line before you edit ~/.bashrc.
Just type 

export PATH=~/bin:$PATH 

before you execute lilypond.

If /home/tomc/bin or ~/bin is already in your PATH, you'll need to get it
at the start of your path string.

HTH, 

Carl