[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: path to lilypond executable
From: |
Johan Vromans |
Subject: |
Re: path to lilypond executable |
Date: |
Thu, 12 Mar 2015 14:49:02 +0100 |
On Thu, 12 Mar 2015 10:38:20 +0100
Urs Liska <address@hidden> wrote:
> OK, this means if the result points to "in the current dir" then I
> should prepend it with the current dir (which is easily possible with
> the tools I already have).
To be more precise: when the result is not an absolute path name (i.e.,
does not start with a / ) then it must be resolved from the perspective of
the current directory. I assume python has a function abspath or similar.
> I get
> => /home/uliska/lilypond/usr/bin/lilypond
> with each of the following:
>
> cd ~
> lilypond test-script.ly
> cd ~/bin
> lilypond test-script.ly
> cd ~/lilypond/usr/bin
> lilypond test-script.ly
You probably do not have "." in your PATH, or it does not precede
"/home/uliska/lilypond/usr/bin/". Try e.g.
env PATH=.:$PATH lilypond test-script.ly
-- Johan
- path to lilypond executable, Urs Liska, 2015/03/11
- Re: path to lilypond executable, Mattes, 2015/03/11
- Re: path to lilypond executable, Urs Liska, 2015/03/12
- Re: path to lilypond executable, Johan Vromans, 2015/03/12
- Re: path to lilypond executable, Urs Liska, 2015/03/12
- Re: path to lilypond executable, Noeck, 2015/03/12
- Re: path to lilypond executable, Urs Liska, 2015/03/12
- Re: path to lilypond executable,
Johan Vromans <=
- Re: path to lilypond executable, Noeck, 2015/03/12
- Re: path to lilypond executable, Urs Liska, 2015/03/12
- Re: path to lilypond executable, Wilbert Berendsen, 2015/03/12
- Re: path to lilypond executable, Urs Liska, 2015/03/12
- Re: path to lilypond executable, Johan Vromans, 2015/03/12