Re: Trivial patch for define-markup-commands.scm

> btw, your fix for (larger ) was erroneous. You can only add > docstrings to function bodies. Ok, I was not aware of that. Erlend > > -- > > Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen > > ___ lilypond-devel mail

Re: lilypond ./ChangeLog Documentation/user/changin...

Quoting Graham Percival <[EMAIL PROTECTED]>: > Index: lilypond/Documentation/user/changing-defaults.itely > diff -u lilypond/Documentation/user/changing-defaults.itely:1.104 > lilypond/Documentation/user/changing-defaults.itely:1.105 > --- lilypond/Documentation/user/changing-defaults.itely:1.104

Trivial patch for define-markup-commands.scm

[EMAIL PROTECTED] writes: > Hi, > > I noticed the comment "TODO: each markup function should have a doc > string ..." in define-markup-commands.scm, so I documented the two > missing functions and made newline use more consistent. Ok? applied. > > Erlend -- Han-Wen Nienhuys | [EMAIL PRO

Trivial patch for define-markup-commands.scm

[EMAIL PROTECTED] writes: > Hi, > > I noticed the comment "TODO: each markup function should have a doc > string ..." in define-markup-commands.scm, so I documented the two > missing functions and made newline use more consistent. Ok? btw, your fix for (larger ) was erroneous. You can only add

node names in Documentation/user/notation.itely ?

[EMAIL PROTECTED] writes: > What's the new naming convention for nodes? For example, I see: > > @node Harmonic notes, , Other instrument specific notation, Other > instrument specific notation > @node Popular music, Orchestral music, Tablatures, Notation manual > @node Chord names, Chords mode,

Lilypond 2.5.8 crashes with any input

[EMAIL PROTECTED] writes: > I'm getting a segmentation fault for any input file I process (e.g. > simple.ly). This seems to be a very similar bug as I got in 2.5.7, > ecept that the offending string is now at 0x0 instead of 0x22 > > Let me know if there is anything more I can do diagnostically.

Re: CFF font sets

[EMAIL PROTECTED] writes: > > > No, you're wrong ly:font-sub-fonts is a kludge to keep TeX working. > > It returns (feta20 parmesan20 feta-alphabet20) for the emmentaler > > font. > > OK. > > Anyway, there's something fishy. All emmentaler*.cff files use > `emmentaler' for /FontName. Why? Thi

example question

X-Mailer: VM 7.14 under Emacs 21.3.1 Reply-To: [EMAIL PROTECTED] FCC: ~/persoonlijk/Mail/sent in SATB vocal score and piano reduction why are you doing \new PianoStaff << \new Staff << \context Lyrics = tenors \lyricsto tenors \tenorWords \context Lyrics = basses \lyricsto bas