[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: adding \lyricmode to \lyricsto triggers an error

From: Eluze
Subject: Re: adding \lyricmode to \lyricsto triggers an error
Date: Mon, 17 Feb 2014 06:17:10 -0800 (PST)

Janek Warchoł wrote
> 2014-02-16 23:58 GMT+01:00 Eluze <

> eluzew@

> >:
>> \version "2.18.0"
>> % this doesn't work since 2.19.2
>> <<
>>   \new Voice=A \relative c'{ c d e f g a }
>>   \new Lyrics \lyricsto A \lyricmode { ahh b c d e f }
>> the doc says: *The lyrics themselves follow the \lyricsto command. The
>> \lyricsto command invokes lyric mode automatically, so the \lyricmode
>> keyword may be omitted."
>> and indeed, omitting \lyricmode works and also putting braces after
>> /\lyricsto A/ works - but I don't think this is an improvement in
>> user-friendliness...
> I don't have an opinion about the change, but i have one suggestion:
> it would be much better if objections like this were raised during
> patch review.  So, please look at the review issue of this commit and
> tell us what would make it easier for you to comment on it during
> review instead of now.  I believe that we should adjust our policies
> to encourage people like you (i.e. people who aren't core developers)
> to review patches (for example from the User Interface point of view).

the main problem with this suggestion is that usually I only look at
solutions when the new version has been released and I download it (that's
also the time for verifying issues).

and very often I only get fully aware of what has been done when I use the
new or fixed function.

now I wouldn't change the policies because of just this single case - if
there are many complaints about new behavior new issues should take care of
these. for the actual case I think it would be good to change the doc
according to David's proposal.

the actual process - create a new (test-) version with issues fixed and new
features, verify it and collect the feedback seems quite natural and makes
corrections possible (if needed ).


View this message in context: 
Sent from the Bugs mailing list archive at Nabble.com.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]