Jim Long writes:
> On Wed, Jan 09, 2013 at 03:33:27AM -0800, Eluze wrote:
>> thanks, Jim
>>
>> added to the tracker as
>> https://code.google.com/p/lilypond/issues/detail?id=3092&thanks=3092&ts=1357730898
>>
>> another - not perfect - workaround is using less chordnames than there are
>> notes:
69038.n5.nabble.com/Layout-behaviour-arising-from-set-chordChanges-t-tp138934p139116.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
uze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Layout-behaviour-arising-from-set-chordChanges-t-tp138934p139082.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-use
Kieren's request for a ! shortcut in chordMode brought a slightly
related issue to my forebrain which I have been dealing with
quietly in the past.
Based on the example below, it appears that the net result of
\set chordChanges = ##t
is that repeated chordnames are made invisible, but space is
s
