Greetings Kevin,

I think the easiest thing to do would be to put someting into the dir
file that you cited above. Most likely, you will have to do this as
root. In my file, I have the following:

LilyPond
* LilyPond Changes: (lilypond-changes). New features in 2.19.46 since 2.18
* LilyPond Contributor's Guide: (lilypond-contributor).
* LilyPond Essay: (lilypond-essay).
* LilyPond Extending: (lilypond-extending).
* LilyPond Internals Reference: (lilypond-internals).
* LilyPond Learning Manual: (lilypond-learning).
* LilyPond Music Glossary: (music-glossary).
* LilyPond Notation Reference: (lilypond-notation).
* LilyPond Snippets: (lilypond-snippets).
* LilyPond Usage: (lilypond-usage).
* LilyPond Web: (lilypond-web).

Of course, you may adjust things as you please (for example, adding
more annotations after each location given in parentheses), though
take care that the general format, including punctuation, remains as
above.

Hwaen Ch'uqi


On 9/9/16, Kevin Barry <barr...@gmail.com> wrote:
> Hi all,
>
> I have installed the lilypond-doc package on my system (Fedora), but
> it didn't add anything to the main info directory. In the LilyPond
> menu in emacs two of the info buttons work (Internals and Glossary)
> and the other two (LilyPond and index search) both give errors. I
> tried adding the directory including them to the emacs path with
> (add-to-list 'Info-default-directory-list
> "/usr/share/doc/lilypond-doc/share/info")
> but it didn't make any difference (which isn't surprising since the
> `dir' file is empty).
>
> Before I start trying all kinds of hackery to make the manuals appear
> in my directory or make them accessible through lilypond-mode, is
> there a proper way to do it?
>
> Best wishes,
> Kevin
>
> _______________________________________________
> 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

Reply via email to