In response to Elaine and Urs
1) I already thought about the way to automatically feedback the
modifications to the original .ly file, instead of the alert() string.
Again, it will be 100% JS + SVG. Just have a little patience ;-)
Basically, Lilypond will have to import the original .ly code as t
-- Forwarded message --
> From: Urs Liska
> To: lilypond-devel@gnu.org
> Date: Mon, 16 Dec 2019 10:18:36 +0100
> Subject: Re: A snippet for editing curves using the mouse and reporting
> changes to the .ly file
> Hi Paolo,
>
> I have followed the discussion but didn't have the time
From: nine.fierce.ball...@gmail.com
> To: lemzw...@googlemail.com
> Cc: lilypond-devel@gnu.org, re...@codereview-hr.appspotmail.com
> Bcc:
> Date: Mon, 16 Dec 2019 08:51:59 -0800
> Subject: Re: Issue 5621: Improve rehearsal mark position at beginning of
> staff (issue 547340043 by nine.fierce.ball.
Hi Urs,
of course the points you listed must be fixed. I was already aware about
them.
I'm following a specific workflow, and those points will be fixed at a
later time. Meanwhile, it's a good idea to keep track of them.
The workflow is as follows:
1) prepare an * usable *, even if limited, snip
On 2019/12/16 16:51:59, Dan Eble wrote:
On 2019/12/15 06:29:59, lemzwerg wrote:
> Well, the cis–trans pairing is IMHO only understandable for people
who have a
> Latin background (or come from Austria, since it was divided into
> »Cisleithanien« and »Transleithanien« in the K. und K. era)... A
On 2019/12/15 06:29:59, lemzwerg wrote:
Well, the cis–trans pairing is IMHO only understandable for people who
have a
Latin background (or come from Austria, since it was divided into
»Cisleithanien« and »Transleithanien« in the K. und K. era)... As
nice as it
is, I suggest that you find nam
On 2019/12/16 15:18:50, Dan Eble wrote:
remove/revise some regtests
Details:
revise pedal-bracket.ly
The mark is obviously intended to test the extent of the pedal
bracket.
It is not clear whether it matters that the mark extends to the left
as
well as to the right, but to be s
Hi folks
As I'm working on building a flatpak of Frescobaldi, I must compile
from source all dependencies and bundled applications, including
LilyPond (without the documentation).
I have two questions:
1. Ghostscript is not a requirement for building, but it is a
requirement for running lily
Dan,
I would certainly not want that such a typo is not corrected at all.
You may take the decision, whether you push it to staging just alone (which I
should prefer) or you keep it in the patchset attached to Issue 5639
> -Oorspronkelijk bericht-
> Van: d...@gnu.org
> Verzonden: Monday
Am 16.12.19 um 10:18 schrieb Urs Liska:
* For integration in LilyPond the functionality should be wrapped into
a single file that can be included. Including the file should
automatically activate the functionality.
Maybe there should be a second includable file that does *not*
auto
10 matches
Mail list logo
