Am 27.11.2013 15:01, schrieb David Kastrup:
David Kastrup <d...@gnu.org> writes:
I see nothing wrong with giving a command line option for setting
tags. That sounds useful, and it would most certainly encompass your
use case. It would also fit into LilyPond's current tool set, and
consequently into the documentation.
The way one would do that is likely to have some option
--tags xxx,yyy,zzz
and when one writes in the document
\keepWithTag \default ...
\removeWithTag \default ...
then the tags from the command line are used. I'm not sure that covers
all possible and/or use cases, but with careful use of tags, it should
be useful for a lot.
Wouldn't solve my fundamental issue (having to provide a definition in
the input files) but looks good nevertheless.
But also in this case I would come back and suggest including functions like
originalBreak =
#(define-music-function (parser location)()
( #{ \tag #'keep-original-breaks \break #} ))
in LilyPond so they are available without having to put them in private
libraries.
Urs
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
