bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)


From: Dmytro O. Redchuk
Subject: Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
Date: Wed, 22 Jun 2011 10:05:51 +0300
User-agent: Mutt/1.5.20 (2009-06-14)

On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
> On Tue, Jun 21, 2011 at 12:52:01PM +0300, Dmytro O. Redchuk wrote:
> > In such cases I add
> >   \header { tagline = "" }
> > to a source file and then:
> > 
> >   lilypond --png test.ly
> >   convert test.png -trim test-trim.png
> 
> Excellent!
> 
> Could you write a short shell script to do this?  i.e. using
>   lilypond -e ...
> to remove the tagline (maybe that's already in LSR),
> and then call convert automatically?  I'd really like to add this
> to the CG so that we have a simple way to generate images.
> (at least on non-windows machines)
As far as I can see, Phil asked how to remove the tagline from the comand
line*, but the answer was "it's impossible".

Another option, proposed by Valentin, was to use external file
(-dinclude-settings=...), but i would find this "inconvenient" for the build
system?

And... I'd be happy to appear wrong -- so, please, is this really possible
with scheme?  I will search more if "yes" .)

> This would allow us to standardize on 1-page pngs (automatically
> trimmed) and multi-page pdfs, and avoid -dpreview entirely.

_______________________
 * http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00080.html

-- 
  Dmytro O. Redchuk
  Bug Squad



reply via email to

[Prev in Thread] Current Thread [Next in Thread]