Simon Albrecht <simon.albre...@mail.de> writes:
> I currently try out the consequences of issue 3648
> <http://code.google.com/p/lilypond/issues/detail?id=3648>, namely the
> possibility to use isolated durations as frequently as has been normal
> for isolated pitches. It certainly means a change to the habits of
> entering music in LilyPond language, but I can imagine that it
> considerably simplifies typing in the long run.
I'd keep away from it unless entering predominantly rhythmic patterns.
That includes a lot of drum music, of course. That is: you should focus
on those use cases which simplify _reading_ music rather than _writing_
it.
> This way, the following music (verbose version)
>
> \version "2.19"
> \relative { d4 c4 c2 }
>
> becomes
>
> \relative { d4 c 2 }
Turn it into \relative { d4 c4 2 } which is d followed by a c pattern of
4 and 2. When you are thinking of patterns, leaving out the
no-longer-redundant duration does not make much sense. Indeed,
something like
rhythm =
#(define-music-function (parser location p) (ly:pitch?)
"Make the rhythm in Mars (the Planets) at the given pitch"
#{ \tuplet 3/2 { $p 8 $p $p } $p 4 $p $p 8 $p $p 4 #})
from
<URL:http://www.lilypond.org/doc/v2.19/Documentation/snippets/pitches#pitches-creating-a-sequence-of-notes-on-various-pitches>
can be turned into the much more readable
rhythm =
#(define-music-function (parser location p) (ly:pitch?)
"Make the rhythm in Mars (the Planets) at the given pitch"
#{ \tuplet 3/2 { $p 8 8 8 } 4 4 8 8 4 #})
which has the side effect of working fine in \relative mode without the
need to employ make-relative. You don't want spaces to have an effect
here. It's not clear what they would even mean here when they did.
> However, it would be great for consistency and automatisation of
> writing music if it could work. Which would mean to forbid any spaces
> or line breaks between pitch and duration, if they belong to the same
> note, and interpret them as two notes if there is any space or line
> break inbetween.
> I don’t see any problem in that with normal input, whereas in other
> cases like music functions the space might be necessary.
> What do you think?
We don't want space to be significant between separate syntactical
entities. Particularly not for automatisation of writing music which
becomes awfully tricky if you have to keep track of writing spaces.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
