On Sun, Aug 30, 2020 at 10:34 PM Werner LEMBERG wrote:
>
>
> >> > \alternative {
> >> > { c1 }
> >> > 1
> >> > { d1 }
> >> > 1
> >> >}
> >> >
> >> > Which would be interpretted as: the 1st, 2nd, and 4th endings are c,
> >> > and the 3nd ending is d.
> >>
> >> That is already valid
>> > \alternative {
>> > { c1 }
>> > 1
>> > { d1 }
>> > 1
>> >}
>> >
>> > Which would be interpretted as: the 1st, 2nd, and 4th endings are c,
>> > and the 3nd ending is d.
>>
>> That is already valid syntax and makes the first and second
>> alternative c1 and the third and fourth
On Sun, Aug 30, 2020 at 11:59 AM David Kastrup wrote:
>
> Christopher Heckman writes:
>
> > How about allowing modifying the syntax of \alternative to include the
> > possibility of a number, which means to repeat that ending? This would
> > look like
> >
> > \alternative {
> > { c1 }
> > 1
Am Sonntag, den 30.08.2020, 22:12 +0200 schrieb Jean Abou Samra:
> > What if we kept a legacy convert.ly that went from the origin to, say
> > 2.12.0 that was still Python 2 based? And then had the new, Python 3-based
> > convert.ly start from 2.12.0?
> >
> > This would provide a way for anybody
Am Sonntag, den 30.08.2020, 21:36 +0200 schrieb Joram Noeck:
> Hi Jonas,
>
> some comments to that:
>
> 1. I (hopefully) fixed all the escaping issues like #6024 in my merge
> request: https://gitlab.com/lilypond/lilypond/-/merge_requests/363
>
> The python re syntax is clear, it just requires
Greetings everybody,
Le 30/08/2020 à 21:06, David Kastrup a écrit :
Jonas Hahnfeld writes:
For https://gitlab.com/lilypond/lilypond/-/issues/6024, I've been
looking at python/convertrules.py and wonder if we really need all
ancient rules starting from version 0.1.9. Right now, a majority of
Hello,
Here is the current patch countdown list. The next countdown will be on
September 1st.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!353 Fix input/regression/page-label.ly - Jonas Hahnfeld
> The python re syntax is clear, it just requires the right amout of
> backslashes or r-prefixes
I definitely overlooked how often there are *too many* backslashes in
the code. So there are a lot more changes requried than what is in merge
request 363:
Hi Jonas,
some comments to that:
1. I (hopefully) fixed all the escaping issues like #6024 in my merge
request: https://gitlab.com/lilypond/lilypond/-/merge_requests/363
The python re syntax is clear, it just requires the right amout of
backslashes or r-prefixes;
re.sub(r'\\command',
Jonas Hahnfeld writes:
> For https://gitlab.com/lilypond/lilypond/-/issues/6024, I've been
> looking at python/convertrules.py and wonder if we really need all
> ancient rules starting from version 0.1.9. Right now, a majority of
> these won't even apply because Python 3 is much pickier about
Christopher Heckman writes:
> How about allowing modifying the syntax of \alternative to include the
> possibility of a number, which means to repeat that ending? This would
> look like
>
> \alternative {
> { c1 }
> 1
> { d1 }
> 1
>}
>
> Which would be interpretted as: the 1st, 2nd,
Dan Eble writes:
> After further thought, I believe we can do this, but using \volta
> where you have \alternative. These are my current thoughts (some
> informed by experiment).
>
> \volta i,j,k can be used anywhere and is semantically similar to tags.
> During unfolding, music is kept which
On Aug 29, 2020, at 15:50, Dan Eble wrote:
>
> On Aug 29, 2020, at 14:52, David Kastrup wrote:
>>
>> \repeat volta 40 {
>> ...
>> \alternative { ... }
>> \alternative { ... }
>> \alternative { ... }
>> }
>>
>> since that would avoid several syntactical problems and would allow to
>> produce
Hi Jonas,
Le 30/08/2020 à 15:38, Jonas Hahnfeld a écrit :
For https://gitlab.com/lilypond/lilypond/-/issues/6024, I've been
looking at python/convertrules.py and wonder if we really need all
ancient rules starting from version 0.1.9. Right now, a majority of
these won't even apply because
On Sun, Aug 30, 2020 at 9:02 AM Jonas Hahnfeld wrote:
> For https://gitlab.com/lilypond/lilypond/-/issues/6024, I've been
> looking at python/convertrules.py and wonder if we really need all
> ancient rules starting from version 0.1.9. Right now, a majority of
> these won't even apply because
FWIW, I ran a grep on my files, and the oldest version is 2.4.4; there
are also several 2.9, 2.10 and 2.11 ones. I admit I rarely touch old
files, but sometimes that happens.
James Lowe ezt írta (időpont: 2020. aug. 30., V, 16:32):
>
> On 30/08/2020 14:38, Jonas Hahnfeld wrote:
> > To make the
On 30/08/2020 14:38, Jonas Hahnfeld wrote:
To make the story short: Can we maybe instead drop any rules older than
2.12.0? Its last minor release 2.12.3 is more than 10 years ago.
I don't know.
While it is more than 10 years ago, I seem to recall a lot of stuff on
Mutopia where there are LP
For https://gitlab.com/lilypond/lilypond/-/issues/6024, I've been
looking at python/convertrules.py and wonder if we really need all
ancient rules starting from version 0.1.9. Right now, a majority of
these won't even apply because Python 3 is much pickier about bad
escape codes in the regular
18 matches
Mail list logo
