Re: (doc help) internal lilypond file locations on non-OSX

2006-05-03 Thread Graham Percival
On 3-May-06, at 3:29 AM, Geoff Horton wrote: > @item Windows: # > C:/PRogram Files/LilyPond/usr/share/lilypond/current/ Only if Lilypond was installed to the C drive. Wouldn't it be better to make this relative to the installation directory? I suppose we could write "INSTDIR" instead.

Re: (doc help) internal lilypond file locations on non-OSX

2006-05-03 Thread Geoff Horton
> To access this, either @code{cd} into this directory from > the Terminal, or control-click on the LilyPond application > and select "Show Package Contents". > > @item Windows: # > C:/PRogram Files/LilyPond/usr/share/lilypond/current/ Only if Lilypond was installed to the C drive. Wouldn'

Re: (doc help) internal lilypond file locations on non-OSX

2006-05-03 Thread Han-Wen Nienhuys
Graham Percival schreef: Quote from upcoming docs; please fill in the . Cheers, - Graham Some default settings (such as the definitions for @code{\header{}s) are stored as @code{.ly} files. Other settings (such as the definitions of markup commands) are stored as @code{.scm} (Scheme)

(doc help) internal lilypond file locations on non-OSX

2006-05-02 Thread Graham Percival
Quote from upcoming docs; please fill in the . Cheers, - Graham Some default settings (such as the definitions for @code{\header{}s) are stored as @code{.ly} files. Other settings (such as the definitions of markup commands) are stored as @code{.scm} (Scheme) files. Further explanatio