where Babel looks for binaries?

where Babel looks for binaries?

[Steven Arntson]

I'm using org-babel to enter lilypond code for music typesetting. I had
an old version of lilypond from the Ubuntu repos installed in
/usr/bin. This worked, but the version was getting old. I installed the
latest stable version from the lilypond.org website, and it ended up in
/usr/local. I removed (apt-get remove) the repo version. Now when I do
ly-tangle, I get:

ly-compile-lilyfile: Searching for program: no such file or directory,
/usr/bin/lilypond

I tried to "customize-variable" on "ly-compile-lilyfile" but there's no match.

How do I change where org looks for this program?

Thank you!
Steven Arntson

Re: where Babel looks for binaries?

[Thorsten Jolitz]

Steven Arntson <steven@stevenarntson.com> writes:

> I'm using org-babel to enter lilypond code for music typesetting. I had
> an old version of lilypond from the Ubuntu repos installed in
> /usr/bin. This worked, but the version was getting old. I installed the
> latest stable version from the lilypond.org website, and it ended up in
> /usr/local. I removed (apt-get remove) the repo version. Now when I do
> ly-tangle, I get:
>
> ly-compile-lilyfile: Searching for program: no such file or directory,
> /usr/bin/lilypond
>
> I tried to "customize-variable" on "ly-compile-lilyfile" but there's
> no match.
>
> How do I change where org looks for this program?

Maybe

,----[ C-h v ly-nix-ly-path RET ]
| ly-nix-ly-path is a variable defined in `ob-lilypond.el'.
| Its value is "/usr/bin/lilypond"
| 
| Documentation:
| Not documented as a variable.
| 
| [back]
`----

?

-- 
cheers,
Thorsten

Re: where Babel looks for binaries?

[Steven Arntson]

Thorsten Jolitz <tjolitz@gmail.com> writes:

> Steven Arntson <steven@stevenarntson.com> writes:
>
>> I'm using org-babel to enter lilypond code for music typesetting. I had
>> an old version of lilypond from the Ubuntu repos installed in
>> /usr/bin. This worked, but the version was getting old. I installed the
>> latest stable version from the lilypond.org website, and it ended up in
>> /usr/local. I removed (apt-get remove) the repo version. Now when I do
>> ly-tangle, I get:
>>
>> ly-compile-lilyfile: Searching for program: no such file or directory,
>> /usr/bin/lilypond
>>
>> I tried to "customize-variable" on "ly-compile-lilyfile" but there's
>> no match.
>>
>> How do I change where org looks for this program?
>
> Maybe
>
> ,----[ C-h v ly-nix-ly-path RET ]
> | ly-nix-ly-path is a variable defined in `ob-lilypond.el'.
> | Its value is "/usr/bin/lilypond"
> | 
> | Documentation:
> | Not documented as a variable.
> | 
> | [back]
> `----
>
> ?

I changed ly-nix-ly-path in ob-lilypond.el to "/usr/local/lilypond". I
restarted emacs, ran "ly-tangle" and again got the message of "no such
file or directory, /usr/bin/lilypond." But my change is still there in
the file, so it must be looking somewhere else, too?

I also wonder: is it a good idea for me to be meddling in a file like
"ob-lilypond"? Will any changes I make be reverted when I get an update
from the emacs package manager?

I am a beginner here, so thank you for your help!
-steven

Re: where Babel looks for binaries?

[Thorsten Jolitz]

Steven Arntson <steven@stevenarntson.com> writes:

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> Steven Arntson <steven@stevenarntson.com> writes:
>>
>>> I'm using org-babel to enter lilypond code for music typesetting. I had
>>> an old version of lilypond from the Ubuntu repos installed in
>>> /usr/bin. This worked, but the version was getting old. I installed the
>>> latest stable version from the lilypond.org website, and it ended up in
>>> /usr/local. I removed (apt-get remove) the repo version. Now when I do
>>> ly-tangle, I get:
>>>
>>> ly-compile-lilyfile: Searching for program: no such file or directory,
>>> /usr/bin/lilypond
>>>
>>> I tried to "customize-variable" on "ly-compile-lilyfile" but there's
>>> no match.
>>>
>>> How do I change where org looks for this program?
>>
>> Maybe
>>
>> ,----[ C-h v ly-nix-ly-path RET ]
>> | ly-nix-ly-path is a variable defined in `ob-lilypond.el'.
>> | Its value is "/usr/bin/lilypond"
>> | 
>> | Documentation:
>> | Not documented as a variable.
>> | 
>> | [back]
>> `----
>>
>> ?
>
> I changed ly-nix-ly-path in ob-lilypond.el to "/usr/local/lilypond". I
> restarted emacs, ran "ly-tangle" and again got the message of "no such
> file or directory, /usr/bin/lilypond." But my change is still there in
> the file, so it must be looking somewhere else, too?

Thats because there is probably a compiled ob-lilypond.elc that wasn't
updated and is loaded instead - right?

> I also wonder: is it a good idea for me to be meddling in a file like
> "ob-lilypond"? Will any changes I make be reverted when I get an update
> from the emacs package manager?

Not such a good idea, you should rather put 

,----
| (setq ly-nix-ly-path "/usr/local/lilypond")
`----

or whatever in your init file and revert the changes in
ob-lilypond.el. If you want to hack the library, better clone its git
repo and create your own branch for experimenting.

> I am a beginner here, so thank you for your help!

I would say try the above, i.e. restore ob-lilypond.el and set the
variable in you init file. Alternatively you could delete the
ob-lilypond.elc and the do M-x byte-compile-file on the modified
ob-lilypond.el, but I would not recommend mess around in libraries for
customizations. 

-- 
cheers,
Thorsten

Re: where Babel looks for binaries?

[Steven Arntson]

Thorsten Jolitz <tjolitz@gmail.com> writes:

> Steven Arntson <steven@stevenarntson.com> writes:
>
>> Thorsten Jolitz <tjolitz@gmail.com> writes:
>>
>>> Steven Arntson <steven@stevenarntson.com> writes:
>>>
>>>> I'm using org-babel to enter lilypond code for music
>>>> typesetting. I had
>>>> an old version of lilypond from the Ubuntu repos installed in
>>>> /usr/bin. This worked, but the version was getting old. I
>>>> installed the
>>>> latest stable version from the lilypond.org website, and it ended
>>>> up in
>>>> /usr/local. I removed (apt-get remove) the repo version. Now when I do
>>>> ly-tangle, I get:
>>>>
>>>> ly-compile-lilyfile: Searching for program: no such file or directory,
>>>> /usr/bin/lilypond
>>>>
>>>> I tried to "customize-variable" on "ly-compile-lilyfile" but there's
>>>> no match.
>>>>
>>>> How do I change where org looks for this program?
>>>
>>> Maybe
>>>
>>> ,----[ C-h v ly-nix-ly-path RET ]
>>> | ly-nix-ly-path is a variable defined in `ob-lilypond.el'.
>>> | Its value is "/usr/bin/lilypond"
>>> | 
>>> | Documentation:
>>> | Not documented as a variable.
>>> | 
>>> | [back]
>>> `----
>>>
>>> ?
>>
>> I changed ly-nix-ly-path in ob-lilypond.el to "/usr/local/lilypond". I
>> restarted emacs, ran "ly-tangle" and again got the message of "no such
>> file or directory, /usr/bin/lilypond." But my change is still there in
>> the file, so it must be looking somewhere else, too?
>
> Thats because there is probably a compiled ob-lilypond.elc that wasn't
> updated and is loaded instead - right?
>
>> I also wonder: is it a good idea for me to be meddling in a file like
>> "ob-lilypond"? Will any changes I make be reverted when I get an update
>> from the emacs package manager?
>
> Not such a good idea, you should rather put 
>
> ,----
> | (setq ly-nix-ly-path "/usr/local/lilypond")
> `----
>
> or whatever in your init file and revert the changes in
> ob-lilypond.el. If you want to hack the library, better clone its git
> repo and create your own branch for experimenting.
>
>> I am a beginner here, so thank you for your help!
>
> I would say try the above, i.e. restore ob-lilypond.el and set the
> variable in you init file. Alternatively you could delete the
> ob-lilypond.elc and the do M-x byte-compile-file on the modified
> ob-lilypond.el, but I would not recommend mess around in libraries for
> customizations. 

I reverted the change to ob-lilypond.el and did as you suggested, adding

(setq ly-nix-ly-path "/usr/local/lilypond")

It's now looking in the right place, but still won't tangle the file
when I run ly-tangle. The message in the minibuffer is:

ly-compile-lilyfile: Searching for program: resource temporarily
unavailable, /usr/local/lilypond

The use of "temporarily" is certainly intriguing! I quit out of emacs
and restarted, but am still getting the message.

Thank you for all of your help. I feel like I'm inching forward here
... !

Re: where Babel looks for binaries?

[Thorsten Jolitz]

Steven Arntson <steven@stevenarntson.com> writes:

>> I would say try the above, i.e. restore ob-lilypond.el and set the
>> variable in you init file. Alternatively you could delete the
>> ob-lilypond.elc and the do M-x byte-compile-file on the modified
>> ob-lilypond.el, but I would not recommend mess around in libraries for
>> customizations. 
>
> I reverted the change to ob-lilypond.el and did as you suggested, adding
>
> (setq ly-nix-ly-path "/usr/local/lilypond")
>
> It's now looking in the right place, but still won't tangle the file
> when I run ly-tangle. The message in the minibuffer is:
>
> ly-compile-lilyfile: Searching for program: resource temporarily
> unavailable, /usr/local/lilypond
>
> The use of "temporarily" is certainly intriguing! I quit out of emacs
> and restarted, but am still getting the message.

hmm ... does it work without emacs?
did you try to use lilypond from the commandline?

-- 
cheers,
Thorsten

Re: where Babel looks for binaries?

[Steven Arntson]

Thorsten Jolitz <tjolitz@gmail.com> writes:

> Steven Arntson <steven@stevenarntson.com> writes:
>
>>> I would say try the above, i.e. restore ob-lilypond.el and set the
>>> variable in you init file. Alternatively you could delete the
>>> ob-lilypond.elc and the do M-x byte-compile-file on the modified
>>> ob-lilypond.el, but I would not recommend mess around in libraries for
>>> customizations. 
>>
>> I reverted the change to ob-lilypond.el and did as you suggested, adding
>>
>> (setq ly-nix-ly-path "/usr/local/lilypond")
>>
>> It's now looking in the right place, but still won't tangle the file
>> when I run ly-tangle. The message in the minibuffer is:
>>
>> ly-compile-lilyfile: Searching for program: resource temporarily
>> unavailable, /usr/local/lilypond
>>
>> The use of "temporarily" is certainly intriguing! I quit out of emacs
>> and restarted, but am still getting the message.
>
> hmm ... does it work without emacs?
> did you try to use lilypond from the commandline?

Yes, it's working from there. I'm befuddled. I tried changing the path
to "/usr/local/lilypond/bin" and also "/usr/local/lilypond/usr/bin"
thinking maybe the system needed a little more guidance, but neither of
these worked.

Re: where Babel looks for binaries?

[Thorsten Jolitz]

Steven Arntson <steven@stevenarntson.com> writes:

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> Steven Arntson <steven@stevenarntson.com> writes:
>>
>>>> I would say try the above, i.e. restore ob-lilypond.el and set the
>>>> variable in you init file. Alternatively you could delete the
>>>> ob-lilypond.elc and the do M-x byte-compile-file on the modified
>>>> ob-lilypond.el, but I would not recommend mess around in libraries for
>>>> customizations. 
>>>
>>> I reverted the change to ob-lilypond.el and did as you suggested, adding
>>>
>>> (setq ly-nix-ly-path "/usr/local/lilypond")
>>>
>>> It's now looking in the right place, but still won't tangle the file
>>> when I run ly-tangle. The message in the minibuffer is:
>>>
>>> ly-compile-lilyfile: Searching for program: resource temporarily
>>> unavailable, /usr/local/lilypond
>>>
>>> The use of "temporarily" is certainly intriguing! I quit out of emacs
>>> and restarted, but am still getting the message.
>>
>> hmm ... does it work without emacs?
>> did you try to use lilypond from the commandline?
>
> Yes, it's working from there. I'm befuddled. I tried changing the path
> to "/usr/local/lilypond/bin" and also "/usr/local/lilypond/usr/bin"
> thinking maybe the system needed a little more guidance, but neither of
> these worked.

what if you simply move the liliypond binary to where ob-lilypond
expects it or set a symlink to "/usr/bin/lilypond"?

-- 
cheers,
Thorsten

Re: where Babel looks for binaries?

[Achim Gratz]

Steven Arntson writes:
> I reverted the change to ob-lilypond.el and did as you suggested, adding
>
> (setq ly-nix-ly-path "/usr/local/lilypond")

I don't think that path points to an actual lilypond executable, but is
rather an installation directory.  Since it would seem you have lilypond
in PATH on your system, you might rather try just "lilypond" (or check
which lilypond you're actually using by doing a "which lilypond" on the
command line).

> It's now looking in the right place, but still won't tangle the file
> when I run ly-tangle. The message in the minibuffer is:
>
> ly-compile-lilyfile: Searching for program: resource temporarily
> unavailable, /usr/local/lilypond

That message comes from callproc.c / fileio.c in Emacs although in the
current version of Emacs the order of output would be different.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: where Babel looks for binaries?

[Steven Arntson]

Achim Gratz <Stromeko@nexgo.de> writes:

> Steven Arntson writes:
>> I reverted the change to ob-lilypond.el and did as you suggested, adding
>>
>> (setq ly-nix-ly-path "/usr/local/lilypond")
>
> I don't think that path points to an actual lilypond executable, but is
> rather an installation directory.  Since it would seem you have lilypond
> in PATH on your system, you might rather try just "lilypond" (or check
> which lilypond you're actually using by doing a "which lilypond" on the
> command line).
>
> Regards,
> Achim.

That did it---I changed my init.el to read:

(setq ly-nix-ly-path "lilypond")

And it works like a charm.

Thank you!
steven

Re: where Babel looks for binaries?

[Steven Arntson]

Steven Arntson <steven@stevenarntson.com> writes:

> Achim Gratz <Stromeko@nexgo.de> writes:
>
>> Steven Arntson writes:
>>> I reverted the change to ob-lilypond.el and did as you suggested,
>>> adding
>>>
>>> (setq ly-nix-ly-path "/usr/local/lilypond")
>>
>> I don't think that path points to an actual lilypond executable, but is
>> rather an installation directory.  Since it would seem you have lilypond
>> in PATH on your system, you might rather try just "lilypond" (or check
>> which lilypond you're actually using by doing a "which lilypond" on the
>> command line).
>>
>> Regards,
>> Achim.
>
> That did it---I changed my init.el to read:
>
> (setq ly-nix-ly-path "lilypond")
>
> And it works like a charm.

I've stumbled straight into another issue. ly-tangle now works, but when
I try to invoke lilypond-mode in my org document by typing C-c ' in a
code block, I now get:

Language mode `lilypond-mode' fails with: "Cannot open load file"

I did "which lilypond" in the terminal and retrieved the path
"/usr/local/bin/lilypond" and replaced that in my init.el, viz:

(setq ly-nix-ly-path "/usr/local/bin/lilypond")

After this, "ly-tangle" still works perfectly, and C-c ' still doesn't.

On a hunch, I went to look at "org-babel-load-languages," but the
customize interface here doesn't seem to offer the ability to change
where the system looks for the language.

Re: where Babel looks for binaries?

[Achim Gratz]

Steven Arntson writes:
> I've stumbled straight into another issue. ly-tangle now works, but when
> I try to invoke lilypond-mode in my org document by typing C-c ' in a
> code block, I now get:
>
> Language mode `lilypond-mode' fails with: "Cannot open load file"

This tells you that you haven't lilypond-mode installed or your Emacs
can't find it.  Lilypond is not a standard mode that gets delivered with
Emacs, you have to install it seperately.  Since you said it worked
earlier for you, do

M-x locate-library lilypond-mode

in the _old_ Emacs installation to find out where it is installed, then
copy it over to where the new Emacs is looking for it.

> I did "which lilypond" in the terminal and retrieved the path
> "/usr/local/bin/lilypond" and replaced that in my init.el, viz:
>
> (setq ly-nix-ly-path "/usr/local/bin/lilypond")
>
> After this, "ly-tangle" still works perfectly, and C-c ' still doesn't.

This doesn't have anything to do with the issue you're having.

> On a hunch, I went to look at "org-babel-load-languages," but the
> customize interface here doesn't seem to offer the ability to change
> where the system looks for the language.

You don't need to look there, either.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: where Babel looks for binaries?

[Steven Arntson]

Achim Gratz <Stromeko@nexgo.de> writes:

> Steven Arntson writes:
>> I've stumbled straight into another issue. ly-tangle now works, but when
>> I try to invoke lilypond-mode in my org document by typing C-c ' in a
>> code block, I now get:
>>
>> Language mode `lilypond-mode' fails with: "Cannot open load file"
>
> This tells you that you haven't lilypond-mode installed or your Emacs
> can't find it.  Lilypond is not a standard mode that gets delivered with
> Emacs, you have to install it seperately.  Since you said it worked
> earlier for you, do
>
> M-x locate-library lilypond-mode
>
> in the _old_ Emacs installation to find out where it is installed, then
> copy it over to where the new Emacs is looking for it.
>
>> I did "which lilypond" in the terminal and retrieved the path
>> "/usr/local/bin/lilypond" and replaced that in my init.el, viz:
>>
>> (setq ly-nix-ly-path "/usr/local/bin/lilypond")
>>
>> After this, "ly-tangle" still works perfectly, and C-c ' still doesn't.
>
> This doesn't have anything to do with the issue you're having.
>
>> On a hunch, I went to look at "org-babel-load-languages," but the
>> customize interface here doesn't seem to offer the ability to change
>> where the system looks for the language.
>
> You don't need to look there, either.
>
>
> Regards,
> Achim.

I couldn't remember how I got lilypond-mode working when I first
installed it, but I found the web page I'd used before:

http://www.geoffhorton.com/lilymacs.html

I think what I'd done was pointed emacs at the lilypond-mode files in
/usr/bin/lilypond (or somewherelike) instead of copying those files to
~/.emacs.d. So when I removed the original installation, the library
disappeared, too.

I've got it all working again now, and copied the files into my home
directory's .emacs.d, so hopefully my next upgrade will be easier.

Thank you!
steven