Re: [Lilypond-auto] Issue 4387 in lilypond: Patch: Let \relative work on \transpose content as if it were untransposed

[lilypond]

Comment #7 on issue 4387 by address@hidden: Patch: Let \relative work on  
\transpose content as if it were untransposed
https://code.google.com/p/lilypond/issues/detail?id=4387

> I did say that "It is a bit of an inconvenience that \relative skips over  
> \transpose," but I was only thinking of the inconvenience of remembering  
> an exception to its behavior (and of reading that point in the  
> documentation every time I forgot how \relative worked).

Well, it might be nice for clobbering together some slightly varied  
fugue-like stuff using cut&paste in \relative mode when you feel like you  
cannot work with anything but \relative.  The variation means that you need  
to use cut&paste anyway and cannot revert to music variables, but you don't  
want to write in absolute mode and you don't want to transpose in your  
head, and you are too lazy to crank up a full
\transpose x' y' \relative { } incantation, particularly because you object  
to having more than one \relative per Staff for religious reasons.

This is sort of a use case.  I mean, there must be _some_ reason this has  
been a topic sometimes.

With regard to \displayLilyMusic: it is used sometimes for sort-of music  
export or as a more readable form of \displayMusic for the sake of  
debugging.  The current rendition does not reflect the TransposedMusic  
(which _has_ effects, like on \relative).  Even if one does not transpose  
back, it might be  more accurate to tack on something like \transpose c c  
in order to arrive at source reflecting the input.

In a similar vein, I am tempted to let \displayLilyMusic \relative { c e g  
c } produce \absolute { c e g c' } rather than its current { c e g c' }.   
While it's not the input itself, it is something reproducing it.



--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings