On 2023-12-10 9:33 pm, Stefano Antonelli wrote:
On Sun, 2023-12-10 at 08:46 -0500, Michael Werner wrote:
I'm not at all familiar with ly2video, so I really have no idea if
this'll be directly useful to you. But for getting the headers from
an included file, this is how I do it with nearly all th
Phishing website reported to Google Safe Browsing.
--
Karlin High
Missouri, USA
> Is there any way to produce png output without --png in the command?
No, sorry.
signature.asc
Description: This is a digitally signed message part
> We need a copy so we can introduce the space time dumper code which
> boils down to a simple /include statement at the very top of the file.
You can do that via the `-dinclude-settings` option instead.
> It looks like ly2video also removes any \break, \noBreak, and
> \pageBreak it finds in t
On Mon, 2023-12-11 at 03:49 -0800, Aaron Hill wrote:
> Why should ly2video need any such smarts at all? Since there are
> myriad
> ways an end user can structure their input files, let LilyPond do its
> job and have ly2video ask it for all the information needed. It
> sounds
> like ly2video is al
On Mon, 2023-12-11 at 17:22 +0100, Jean Abou Samra wrote:
> > We need a copy so we can introduce the space time dumper code which
> > boils down to a simple /include statement at the very top of the
> > file.
>
> You can do that via the -dinclude-settings option instead.
Good to know, thanks.
>
> There is a case where I want to create a narrower page for a narrower
> screen. I can easily append a /paper {} block to the original file to
> do this. However, any manual breaks will probably not work at this
> newer width. How would you recommend dealing with this?
Put
```
break = {}
pag
On Mon, 2023-12-11 at 19:41 +0100, Jean Abou Samra wrote:
> Put
>
> break = {}
> pageBreak = {}
> in the -dinclude-settings file?
Wow. That's deceptively simple!
> You can put
>
> #(set! toplevel-music-functions (cons unfoldRepeats toplevel-music-
> functions))
> in -dinclude-settings.
This i
On Mon, 2023-12-11 at 17:22 +0100, Jean Abou Samra wrote:
> ly2video or not, you need to unfold repeats as soon as you want
> correct MIDI output. I agree that requiring to do it explicitly is
> not very user-friendly, but auto-adding \unfoldRepeats sounds like
> solving the problem at the wrong l
