That worked! Thanks for walking me through it.
Keizen
they/them
On Tue, Nov 13, 2018 at 6:38 AM David Bowen <dmb0...@gmail.com> 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 $PATH at the beginning means everything in the current
> PATH will be searched before /usr/share, which means the old lilypond will
> be found first. Try PATH=/usr/share:$HOME/bin:$HOME/local/bin:$PATH
>
> David Bowen
>
> On Mon, Nov 12, 2018 at 11:28 PM Keizen Li Qian <keizen....@gmail.com>
> wrote:
>
>> Okay, I tried the following. Is something wrong with the syntax? I'm
>> pointing it to /usr/share/lilypond/2.18.2/ but it is still looking in home.
>>
>> # set PATH so it includes user's private bin directories
>> PATH="${PATH}:/usr/share/:$HOME/bin:$HOME/.local/bin:$PATH"
>>
>>
>> Keizen
>> they/them
>>
>>
>> On Mon, Nov 12, 2018 at 7:11 PM Keizen Li Qian <keizen....@gmail.com>
>> wrote:
>>
>>> Hi David,
>>>
>>> I found this line in bash.profile (just .profile in my system):
>>>
>>> # if running bash
>>> if [ -n "$BASH_VERSION" ]; then
>>> # include .bashrc if it exists
>>> if [ -f "$HOME/.bashrc" ]; then
>>> . "$HOME/.bashrc"
>>> fi
>>> fi
>>>
>>> PATH="$HOME/bin:$HOME/.local/bin:$PATH"
>>>
>>>
>>> But there is no bin directory:
>>>
>>> $ ls .local/
>>> share
>>>
>>>
>>> Please let me know your ideas. Thank you.
>>>
>>> Keizen
>>> they/them
>>>
>>>
>>> On Mon, Nov 12, 2018 at 6:30 PM David Bowen <dmb0...@gmail.com> wrote:
>>>
>>>> It's going to depend on the shell you are using. I use bash and for me
>>>> the initial setting of $PATH happens in .bash_profile and then I have
>>>> additions in .bash_login and .bashrc. All of these files are in my home
>>>> directory. If you wanted to change the $PATH for all users, look at the man
>>>> page for your shell. Most shells have a global script that gets called for
>>>> all users on login and that file (or files) will be mentioned in the man
>>>> page.
>>>>
>>>> David Bowen
>>>>
>>>> On Mon, Nov 12, 2018 at 8:18 PM Keizen Li Qian <keizen....@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks, David. I'm using Ubuntu. How do I navigate to the relevant
>>>>> one? Thanks again.
>>>>>
>>>>> Keizen
>>>>> they/them
>>>>>
>>>>>
>>>>> On Mon, Nov 12, 2018 at 6:11 PM David Bowen <dmb0...@gmail.com> wrote:
>>>>>
>>>>>> 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 <keizen....@gmail.com>
>>>>>> 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 still grabbed an old version in home/bin.
>>>>>>> After
>>>>>>> renaming the old directory, I get bash: /home/bin/lilypond: No such
>>>>>>> file or
>>>>>>> directory
>>>>>>>
>>>>>>> I'd appreciate any detailed suggestions for updating this path and
>>>>>>> finding information like this. Thank you!
>>>>>>>
>>>>>>> Keizen
>>>>>>> _______________________________________________
>>>>>>> lilypond-user mailing list
>>>>>>> lilypond-user@gnu.org
>>>>>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>>>>>>
>>>>>>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
