Achim Gratz 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"
>
> T
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 l
Steven Arntson writes:
> Achim Gratz 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
Achim Gratz 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 woul
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
Steven Arntson writes:
> Thorsten Jolitz writes:
>
>> Steven Arntson 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
o
Thorsten Jolitz writes:
> Steven Arntson 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 rec
Steven Arntson 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 f
Thorsten Jolitz writes:
> Steven Arntson writes:
>
>> Thorsten Jolitz writes:
>>
>>> Steven Arntson 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 t
Steven Arntson writes:
> Thorsten Jolitz writes:
>
>> Steven Arntson 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 t
Thorsten Jolitz writes:
> Steven Arntson 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
Steven Arntson 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
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
13 matches
Mail list logo