>> At that time, I really, really, really cursed lilypond and its
>> frequent syntax changes.
>
> I think that's Graham's point: syntax changes are bad, so if we have
> to make them (and apparently we still have to), let's do it once and
> for all. Or at most 1-2 times per decade.
I think that R
On Thu, Sep 6, 2012 at 12:15 AM, Reinhold Kainhofer
wrote:
> [1] Note, however, that ANY change, even a very small, subtle change, is a
> really grave argument for a music publisher against using lilypond.
> I wrote a huge piece (~95 pages full score, 23 orchestra instruments, choir,
> etc) a few
> - -dno-point-and-click was exactly what I was looking for;
> lilypond --help had not revealed that wisdom.
Indeed, it is missing for `lilypond -dhelp'. Looks like a bug...
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.
On 2012-09-05 18:15, David Kastrup wrote:
Karim Haddad writes:
Apparently, in the new stable version 2.16, the "\override Stem #'flag
= #modern-straight-flag" is broken. , i.e this has no effect, the
flags stay traditional. or maybe i missed something.
Anyhow, Thank you a lot to all developers
2012/9/4 Trevor Daniels
> Some time ago, around Nov 2011, David folded $(set-time-signature ..)
> into the \time command, see
> a512132fed73a94068b91fb0bab473319e477b6e.
>
> This change also provides an alternative to \set Timing.beatStructure,
> one which seems preferable to me. The use of the
Hello,
2012/9/4 Rutger Hofman
> in 2.16, if the accidentalStyle is set to "modern-cautionary", notes
> adorned with a '!' (forced accidental) have their accidental in
> parentheses. For forced accidentals, that shouldn't be. Isn't this a
> regression?
>
> Thank you for the report. It has been ad
Hello,
2012/9/4 Neil Sands
> Hello
>
> I hope this is the right place to point out some errors in the LilyPond
> Learning
> Manual. I'm a beginner to LilyPond so I may have got the wrong end of the
> stick
> about some things. If so, please tell me!
>
> Thank you for the report, I have added it
Karim Haddad writes:
> Dear list,
>
> I hope this is not already reported. (i didn't find the way to check
> it out, since i don't read all reports).
>
> Apparently, in the new stable version 2.16, the "\override Stem #'flag
> = #modern-straight-flag" is broken. , i.e this has no effect, the
> f
Karim Haddad writes:
> Dear list,
>
> I hope this is not already reported. (i didn't find the way to check
> it out, since i don't read all reports).
Or all documentation.
> Apparently, in the new stable version 2.16, the "\override Stem #'flag
> = #modern-straight-flag" is broken. , i.e this
Dear list,
I hope this is not already reported. (i didn't find the way to check it out,
since i don't read all reports).
Apparently, in the new stable version 2.16, the "\override Stem #'flag =
#modern-straight-flag" is broken. , i.e this has no effect, the flags stay
traditional. or maybe i
10 matches
Mail list logo
