On Wed, Jun 22, 2011 at 06:52:43PM -0600, Colin Campbell wrote:
> On 11-06-22 05:47 AM, Dmytro O. Redchuk wrote:
> >I would start with this:
Looks great; Colin, could you add that to the CG in the Issues
chapter?
> >Do we need more options? For trimming "in place" or something else?
I don't think so. As long as it's clear that the bug squad should
uploade the bug-trim.png file, that's fine.
> After a bit of testing, it seems that settings in \included files,
> however the include is done (very smooth trick, that, David!), are
> overridden if the tag exists in the destination file.
So if you run the script on
\header { tagline="foo" }
\relative c' { c4}
you'll still get a tagline? IMO that's an (accidental) feature,
not a bug! Most bug reports are short and don't have a tagline
defined, so you want to trim the existing one. If a bug report
explicitly adds a tagline="abcd", then it would be good to not
trim that one. (if the tagline= is not relevant to the bug, then
the bug report should be rejected because it's not Tiny)
> Where a .ly file already has the tagline set, it cancels the
> imported one. To do this from a script will, after all, take
> some sed or perhaps python magic. I'll keep at it, as much for
> education as for the satisfaction!
Well, go ahead for your own satisfaction, but I'd reject any patch
that changes the script to do this. :)
Cheers,
- Graham
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
