Janek Warchoł <janek.lilyp...@gmail.com> writes:
> On Sat, Mar 9, 2013 at 7:02 AM, Nick Payne
> <nick.pa...@internode.on.net> wrote:
>> See attached graphic. Quite a number of these in the score (Brahms
>> Sextet Op
>> 18).
>
> you can use a clever function written by David K. While it results in
> different (i'd say a bit worse) spacing, it makes input code
> infinitely more readable:
>
> at =
> #(define-music-function (parser location t e m)
> (ly:duration? ly:event? ly:music?)
> #{ << #m { \skip $t <>$e } >> #})
>
> \new Voice \relative c'' {
> \at 4 \turn f4. g16-. a-.
> }
It is arguably a problem with LilyPond's spacing that one perceives
worse spacing with the above code. One can likely play around a bit,
replacing <> in the code with hidden notes and similar, but of course,
how that affects spacing exactly may well depend on future versions of
LilyPond.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
