That worked! Thanks for walking me through it.
Keizen
they/them
On Tue, Nov 13, 2018 at 6:38 AM David Bowen wrote:
> Keizen,
>
>Having the ${PATH}: at the beginning defeats the whole point of the
> change. The directories in the PATH will be searched in the order they
> occur. So putting $
Am 13.11.18 um 10:08 schrieb J Martin Rushton:
On 13/11/18 08:31, Martin Tarenskeen wrote:
On Mon, 12 Nov 2018, Keizen Li Qian wrote:
Hello,
I installed 2.18.2 on a drive with a partitioned home directory which
had an old ~home/bin/lilypond. Somewhere the path had been set to this
directory
On 13/11/18 08:31, Martin Tarenskeen wrote:
>
>
> On Mon, 12 Nov 2018, Keizen Li Qian wrote:
>
>> Hello,
>>
>> I installed 2.18.2 on a drive with a partitioned home directory which
>> had an old ~home/bin/lilypond. Somewhere the path had been set to this
>> directory so even after convert-ly su
On Mon, 12 Nov 2018, Keizen Li Qian wrote:
Hello,
I installed 2.18.2 on a drive with a partitioned home directory which had an
old ~home/bin/lilypond. Somewhere the path had been set to this
directory so even after convert-ly successfully converted my old files to 2.18,
running lilypond st
What OS are you using? For Linux your $PATH is usually set in one of the
shell . files, for Windows it is set in ControlPanel\System.
David Bowen
On Mon, Nov 12, 2018 at 7:34 PM Keizen Li Qian wrote:
> Hello,
>
> I installed 2.18.2 on a drive with a partitioned home directory which had
> an old
Hello,
I installed 2.18.2 on a drive with a partitioned home directory which had
an old ~home/bin/lilypond. Somewhere the path had been set to this
directory so even after convert-ly successfully converted my old files to
2.18, running lilypond still grabbed an old version in home/bin. After
renam
