Re: Suggestion: Keep original breaks

[David Kastrup]

Urs Liska <address@hidden> writes:

> Of course I can achieve the same with tags. But there will be many
> instances where  I don't "need them anyway" because I don't really
> care about the state of the original score except for this
> simplification while inputting/proofing.

So what?  Why hard code one particular special case?

> Using tags requires more munging of the input file, which for example
> might pollute diffs when versioning scores.

No, it doesn't.  It's trivial to define \originalBreak in terms of tags,
so you can of course use \originalBreak just the way you'd like.

> With the command line switch I can simply wrap the call to lilypond in
> a custom script or make it a checkbox in Frescobaldi's Layout Control
> Options.

The same is true when using tags for that mechanism, except that it
would be much more versatile.  And even if you want to get along without
any warnings and changes to LilyPond or init file, stuff like

lilypond -e "(define-public taglist '(original trumpet))" ...

will define a taglist for use in your file.

-- 
David Kastrup