If I changed \compoundMeter to work exactly like \time when just a
single fraction is provided, would that upset anyone? Right now,
they're slightly different (image attached).
```
{
\time 4/4
\repeat unfold 8 c'8
\compoundMeter #'((4 4))
\repeat unfold 8 c'8
}
```
I am currently tryi
On 2025-01-27 16:48, Stefan E. Mueller wrote:
Once I have all the changes in place, how do they eventually end up in a
review or a new version of Lilypond?
Refer to chapter 3 of the Contributor's Guide. You can find the latest
version in HTML or PDF at https://lilypond.org/development.html .
On 2025-01-19 15:38, Dan Eble wrote:
The bracket is not symmetric. I think this is a bug and I would like to
fix it, but I want to ask what the positions property is supposed to
mean. Is the positions property correct and the bracket wrong, or vice
versa, or some of both?
I found that
[sorry, adding lilypond-devel]
Forwarded Message
Subject: Non-arpeggio bracket extent
Date: Sun, 19 Jan 2025 15:38:02 -0500
From: Dan Eble
To: Werner LEMBERG
The following example shows a table of \arpeggio styles and sizes. The
sizes are forced by the setting
On 2025-01-12 06:15, David Kastrup wrote:
Personally, I would consider it a bad idea to change "duration" here.
It is used pervasively in LilyPond and is "good enough".
I hope to avoid making this another multi-dozen-response thread where
people with diverse concerns pull it off topic in mult
Saul Tobin wrote at
https://lists.gnu.org/archive/html/lilypond-devel/2024-12/msg00048.html,
> In English, I would also use the term "note value"
> ...
> to describe something like "dotted quarter."
I have been surfing the web reading about duration and I find sources
pushing me in different di
Old-timers,
For some reason, I had it in my head that a context property could not
be set to *unspecified*, but now that I have looked again, I see that
that is false. It is possible to set a property to *unspecified* and
mask the value from the enclosing context, just like setting any other
On 2024-12-31 07:40, Jan-Peter Voigt wrote:
Urs Liska, co-initiator and developer of OpenLilyLib, passed away on December
28, 2024 after a serious illness.
Urs will be remembered with respect. I will pray Christian prayers for
his family and friends.
--
Dan
Are "grid lines" used in the real world?
https://lilypond.org/doc/v2.25/Documentation/notation/grid-lines.html
As a feature, this seems... spartan. Does it meet all requirements?
--
Dan
On 2024-12-17 00:48, Werner LEMBERG wrote:
Distributing the file with LilyPond was not intended. I don't
think it would make sense either.
I agree with Trevor, and I also think it would make sense.
[...] For my part, looking at the music of the psalm (lovely, btw) I
certainly think it woul
On 2024-12-16 17:57, Trevor Bača wrote:
On Mon, Dec 16, 2024 at 5:32 PM Dan Eble <mailto:nine.fierce.ball...@gmail.com>> wrote:
I am the author of this example. I used inclusion to cut out material
that I thought was not essential to make my point. I question whether
On 2024-12-16 15:28, Trevor Bača wrote:
dit 23: NR 2.1.7: Phrase bar lines in hymn tunes: notation example 1
* Example contains \include "old-hundredth-example.ly",
which can not be found under 2.25.19
In your attachment, your suggested action is "Update location of
included file, or r
On 2024-12-10 20:13, Dan Eble wrote:
Current Name Proposed New Name
-- ---
measureLength measureLength (no change)
minimumPageTurnLength pageTurnMinimumRestLength
On 2024-12-13 13:20, Trevor Bača wrote:
On Fri, Oct 4, 2024 at 2:00 AM David Kastrup wrote:
Yup, but a duration has structural properties (there are different
durations with the same length). That is not wanted here.
The word "duration" means a length of time.
Can someone explain what
On 2024-12-12 11:16, Trevor Bača wrote:
should happen in public-facing parts of the API), then why not rename
voltaSpannerDuration to voltaSpannerMoment instead of
voltaSpannerMusicLength? In other words, what's the motivation for
further spreading around musicLength when the underlying type is
On 2024-12-11 13:26, Simon Albrecht wrote:
>
Maybe rename grob
property musical-length so users don’t get confused about musical-length
= \musicLength 4 ? Spelling it out, doesn’t seem actually confusing to
me. Don’t have time to continue thinking about that, right now.
I don't know whether i
On 2024-12-11 14:04, Trevor Bača wrote:
>
Thinking this way, proportionalNotationDuration is named correctly, because
what's being set here is a unit of time.
>
I am not sure that I made my reason for wanting to rename this clear.
Maybe this will help:
```
\version "2.24.0"
{
\set Score.v
On 2024-12-11 13:26, Simon Albrecht wrote:
Since context property voltaSpannerDuration is deprecated anyway, ...
You're right in the sense that a better alternative (the musical-length
grob property) was added in 2.25.4. I also remembered this about five
minutes after I sent my message. :)
Current NameProposed New Name
-- ---
measureLength measureLength (no change)
minimumPageTurnLength pageTurnMinimumRestLength
minimumRepeatLengthForPageTurn pageTurnMinimumRepea
On 2024-11-30 13:37, Jean-Charles Malahieude wrote:
On a fresh repo, make doc chokes on
input/regression/include-path-modification and I'm unable to resolve this.
Excerpt of the log:
```
Renaming input to: `include-path-modification-i.ly'
include-path-modification-i.ly:13:2: error: Guile signa
On 2024-11-28 03:39, Mark Knoop wrote:
Hi,
Documentation and Info pages builds are currently failing for me - anyone else
having this problem? This is on current master (6df7159). The tail of the
failing log file is attached - seems to be a font issue with NotoSerif?
The log ends with this:
On 2024-10-26 10:19, David Kastrup wrote:
I took a look at the code, and the baseMoment property in the
timeSignatureSettings alist has type rational and is autoconverted to a
Moment when it is being used for setting the property.
This is garbage, but it is in a separate garbage can.
https://g
On 2024-10-04 17:58, David Kastrup wrote:
Dan Eble writes:
Taking all the feedback into account, I plan to prepare a patch
renaming baseMoment to beatBase.
How about doing both rename and retyping to rational and keeping the old
property as a Moment-typed compatibility read/write accessor
On 2024-10-21 11:20, Luca Fascione wrote:
I might try taking new-minus-old, render that with red ink, blur it a
bit, and composite it with a pale version of the old?
Is there any other presentation that comes to that you'd like to see?
My main complaint about the status quo is low sensitivity
On 2024-10-20 13:02, Luca Fascione wrote:
Here's a zip file with a quick demo of the idea:
when you press the button in the right hand side column, the different
pixels stay put, but the text becomes very pale (so that you still have a
sense of where the diff is wrt the overall score).
The red/
On 2024-10-14 17:33, Dan Eble wrote:
How can I coax LilyPond into giving me more information about Guile errors?
...
Either of those work if you don't set warning-as-error in your test. If
you set warning-as-error, the logging code exits after the first line. 🙄
--
Dan
How can I coax LilyPond into giving me more information about Guile errors?
Attempt 1:
```
$ out/bin/lilypond -ddebug-eval
~/lilypond-src/input/regression/context-property-deprecated-scheme-get.ly
GNU LilyPond 2.25.21 (running Guile 3.0)
Processing
`/home/user/lilypond-src/input/regression/co
On 2024-10-04 19:30, David Kastrup wrote:
I'd probably bring them into existence with something like
(define-compatibility-property 'baseMoment 'beatBase
ly:moment? ly:moment-main ly:make-moment)
My battle with conversion doesn't end with the legacy property.
\set Timing.beatBase = 1/
On 2024-10-04 19:30, David Kastrup wrote
Since the compatibility properties are just for compatibility and would
not be used by LilyPond itself, access to them can be checked in the
failure paths since performance is of secondary consideration.
...> I'd probably bring them into existence with so
On 2024-10-04 17:58, David Kastrup wrote:
Dan Eble writes:
Taking all the feedback into account, I plan to prepare a patch
renaming baseMoment to beatBase.
How about doing both rename and retyping to rational and keeping the old
property as a Moment-typed compatibility read/write accessor
On 2024-10-02 19:48, Dan Eble wrote:
To follow up the replacement of make-moment by \musicLength [1], I think
it would make sense to rename baseMoment to beatBaseLength. Are there
any concerns or other suggestions?
Taking all the feedback into account, I plan to prepare a patch renaming
On 2024-10-04 03:59, David Kastrup wrote:
Saul Tobin writes:
I can see duration vs. moment becoming a source of confusion, since these
are not the same type. I would expect a property named baseDuration to take
a value of type ly:duration?.
Yup, but a duration has structural properties (ther
On 2024-10-03 07:38, Joram Noeck wrote:
You guys know much better, but I would be wondering "was it
baseBeatLength or beatBaseLenth"? A shorter name would be easier to
remember. How about
baseLength?
baseLength is vague. Is it a spatial length or a musical length?
--
Dan
On 2024-10-03 01:19, Saul Tobin wrote:
baseBeatLength? I don't have a strong opinion either way, but it seems like
another natural possibility.
I agree that that sounds more natural in English, but it sounds like the
length of a beat, which is not what it is (not necessarily).
--
Dan
To follow up the replacement of make-moment by \musicLength [1], I think
it would make sense to rename baseMoment to beatBaseLength. Are there
any concerns or other suggestions?
--
Dan
[1]
https://gitlab.com/lilypond/lilypond/-/commit/73ea27187caadc4828d99226f0be64035760fe42
On 2024-08-11 11:13, Luca Fascione wrote:> could someone explain what's
the story behind this segment, circa line 25:
>
> # Add a non-root user who can run sudo without a password.
I found it convenient. You don't have to use it.
> Also, wasn't lilypond building with Guile 3 now?
Yes. Locall
Note to composers: This thread is about software development.
Check this out!
1. Save and unzip the attached JSON file.
2. Visit https://ui.perfetto.dev/ in a browser.
3. Click "Open trace file" and choose the JSON file.
4. Explore.
What you should see is a visualization of the activity
On 2024-05-14 10:49, 周 卫星 wrote:
[HIGH] The LilyDev3 docker build is **MISSING SOME PACKAGES** and not
available for work out-of-box! To me it looks like a critical issue - why all
the bother with Docker when I need to search and install the missing packages
manually?
I believe that Federic
On 2024-04-29 17:39, Steph Phillips wrote:
Hi there!
I'm an experienced Python developer with some additional background in
C# and C++ and would be really excited to contribute to LilyPond.
It's definitely hard to decide where to begin though, so I'm hoping you
can point me at the starting l
On 2024-04-28 03:34, Werner LEMBERG wrote:
>
Independent of improving the metrics, maybe we could improve the
review workflow by adding dynamic control to the diff web page to
expand or collapse the entries based on a variable threshold.
Yes, this would be a nice feature – please submit an issu
On 2024-04-27 00:24, Werner LEMBERG wrote:
I'm working on a modification of `musicxml2ly` that will cause a
change in the result as shown by the attached images. However, our
regtest classifies this as 'below threshold' and doesn't display it.
Does anybody have an idea how to improve this? I'
x27;t?
When I test that assumption by removing the listener for articulations
from the Voice context listeners, the list of articulations is still empty.
cheers
Maurits
Op 16-04-2024 om 13:14 schreef Dan Eble:
On 2024-04-15 04:20, Maurits Lamers via Discussions on LilyPond
development wrote:
On 2024-03-13 20:09, Thomas Morley wrote:
I don't understand what you propose.
My advice was general software-design advice based on a hasty
consideration of your post, so I'm not really surprised.
To give a different example, let's look at make-dotted-bar-line (afaik
it's your code).
There
On 2024-03-13 17:35, Thomas Morley wrote:
currently I'm attempting to improve dashed/dotted bar lines wrt to
changed staff-space and span bars.
We use both definitions for BarLine _and_ SpanBar, but then SpanBar is
frequently a little off.
It would be nice to have a possibility to detect whether
On 2024-03-11 18:27, hassan.elfat...@free.fr wrote:
you delete
(define-safe-public FIVE-HALF-FLAT -5/2)
(define-safe-public SEVEN-HALF-FLAT -7/2)
(define-safe-public FIVE-HALF-SHARP 5/2
you delete (define-safe-public FIVE-HALF-FLAT -5/2)
As I understand it, this change was made after your st
On 2024-03-07 09:24, hassan.elfat...@free.fr wrote:
by trying to make hel-arabic.ly dependent on arabic.ly without consulting me,
you screwed up the hel-arabic.ly file.
Neighbor,
1. You contributed to an open-source project. Proposed
changes are posted for public review. GitLab sends
notific
On 2024-02-27 07:14, Luca Fascione wrote:
inline constexpr vsize VPOS (vsize(-1));
OK, but don't repeat the type.
inline constexpr auto VPOS = vsize (-1);
Personally, I don't like flower's aliases related to vsize,
ssize, and Real -- I'd rather just use standard names --
but I remember t
On 2024-02-23 14:10, Mike Blackstock wrote:
> just above the Bulk Barn on Bloor... cheap pints
... 90% whey protein isolate by the kilo ...
But seriously: I'm not keen to tour the 18-lane highway to Hogtown just
to socialize for an hour; however, if this idea grew into a day-long
conference,
On 2024-02-10 07:52, Werner LEMBERG wrote:
systems like macOS that neither have or use '/bin/bash'.
Apple changed the default shell for new users to zsh about 5 years ago,
but bash is still there. I don't oppose making the build scripts more
portable, but let's not misunderstand the situati
On 2024-02-02 14:29, Éric Würbel wrote:
How can submit a patch ? forking the master branch and submitting a pull
request ?
Yes.
https://lilypond.org/doc/v2.25/Documentation/contributor/summary-for-experienced-developers
--
Dan
On 2024-01-20 20:55, Carl Sorensen wrote:
File
"/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py",
line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/usr/bin/tidy', '-o',
'/dev/null', '-q', 'compare
On 2023-12-07 05:12, Saul Tobin wrote:
I’d welcome feedback and I’d be happy to submit this as a pull request for
either OLL or Lilypond itself if there is interest.
They're "merge requests" on GitLab, but they smell as sweet. You would
likely get more engagement from busy developers if you
On Oct 21, 2023, at 01:12, Werner LEMBERG wrote:
>
>
>
>>> Some debugging shows it seems to be the latter: All top-level
>>> definitions are available as paper variables within a book's paper
>>> block, together with all paper variables of the top-level paper
>>> block:
>>>
>>> Is this really
On Oct 20, 2023, at 06:29, Werner LEMBERG wrote:
>>
>> Or is this an inheritance thing? Does a `\book` block inherit all
>> top-level expressions and convert them to paper variables?
>
> Some debugging shows it seems to be the latter: All top-level
> definitions are available as paper variables
On Aug 31, 2023, at 07:38, Jean Abou Samra wrote:
>
>
>
>> Le 31 août 2023 à 13:22, Dan Eble a écrit :
>>
>> My opinion hasn't changed since we instituted the automation. The previous
>> discussion is in the archive.
>
> I couldn't find it.
On Aug 31, 2023, at 02:46, Werner LEMBERG wrote:
>
>
>
>>> Colin, something that starts with 'Draft:' in the description
>>> should be omitted from the normal review cycle. So: MR 2089 is
>>> *not* on countdown. Please adjust the tag accordingly.
>>
>> Thanks for the clarification, Werner. I
On Jul 27, 2023, at 08:22, Jean Abou Samra wrote:
>
> as Dan said, we're on C++17 now (and I think the experiment has lasted long
> enough without Guile quirks that actually using C++17 features would be fine
> by now).
Good, because I queued up a random bunch of minor improvements during my r
On Jul 26, 2023, at 14:38, Jason Yip via Discussions on LilyPond development
wrote:
>
> * ../configure
> --prefix=/home/lj/projects/internships/2023/lilypond/build/release
> --disable-debugging --disable-optimising --enable-checking
> --enable-profiling 'CC=ccache clang' 'CXX=ccache clang+
On Jul 9, 2023, at 10:39, Jean Abou Samra wrote:
>
> It definitely makes sense to keep the option to build without bytecode, since
> that is quite faster for incremental rebuilds (especially in Guile 2.2,
I think it makes sense to skip `make bytecode` when iterating on particular
tests, but I a
On Jul 8, 2023, at 13:55, David Kastrup wrote:
>
> Ok, here is the deal: I think it probably is sanest to just ditch the
> operator for ly:pitch-negate and the equivalent for Moment. That being
> said, I've also found incorrect manual conversions in some code. The
> question is whether it is be
I'm hitting this on master after (roughly) autogen.sh; make; make bytecode.
```
$ out/bin/lilypond ~/lilypond-src/input/regression/other/display-lily-tests.ly
GNU LilyPond 2.25.7 (running Guile 2.2)
Processing
`/home/user/lilypond-src/input/regression/other/display-lily-tests.ly'
[...]
/home/user
On Jun 19, 2023, at 13:21, Jason Yip wrote:
> \set minSubdivideInterval = #(ly:make-moment 1 8)
> \set maxSubdivideInterval = #(ly:make-moment 1 16)
These values could be `\musicLength 8` and `\musicLength 16`.
Also, MR 2032 (merged hours ago) adds `musical-length?` and
`positive-musical-le
On Jun 17, 2023, at 09:27, David Kastrup wrote:
>
>>
>> That sounds like it would make more sense to specify those values in the
>> form of a "duration log", like the first argument to a ly:make-duration
>> call.
>
> Or just use a duration in the first place. First iterations would
> likely on
On Jun 16, 2023, at 19:13, Jason Yip wrote:
>
> minSubdivideInterval and maxSubdivideInterval. They are both Rationals. Their
> numerator and denominator must be a power of 2. For each power of 2
> (including negative powers of 2 of course) between those two values, the beam
> can be subdivide
On Jun 16, 2023, at 04:37, Jean Abou Samra wrote:
>
> I know that 2.25.6 was planned for this weekend. Unfortunately, due to
> https://gitlab.com/lilypond/lilypond/-/issues/6620 , current master is not
> going to work on Kubuntu and possibly other distros.
>
> I will try to find time this even
On Jun 4, 2023, at 08:18, Werner LEMBERG wrote
Has anyone here ever used or seen the time-signature cancellation
sign shown in MR 2029, or anything like it?
https://gitlab.com/lilypond/lilypond/-/merge_requests/2029
>>>
>>> Never.
>>> Kieren.
>>
>> Now I'm starting to doubt that
On Jun 4, 2023, at 15:27, Flaming Hakama by Elaine
wrote:
>
> I guess I am kind of confused at the default behavior, why does lilypond
> not reprint a clef when you specify \clef ?
>
> Are people putting \clef commands in their code where they don't want a
> clef to appear?
> Is this a common p
On Jun 4, 2023, at 07:53, Kieren MacMillan wrote:
>
> Hi Dan,
>
>> Has anyone here ever used or seen the time-signature cancellation sign shown
>> in MR 2029, or anything like it?
>> https://gitlab.com/lilypond/lilypond/-/merge_requests/2029
>
> Never.
> Kieren.
Now I'm starting to doubt that
Has anyone here ever used or seen the time-signature cancellation sign shown in
MR 2029, or anything like it?
https://gitlab.com/lilypond/lilypond/-/merge_requests/2029
—
Dan
On Jun 3, 2023, at 04:09, Kevin Barry wrote:
>
> On Sat, 3 Jun 2023 at 06:06, Carl Sorensen wrote:
>
>>> I vote for adjusting the code so that it follows the documentation,
>>> probably by adding `forceTimeSignature` and `forceKeySignature`
>>> properties, both for orthogonality and a way to re
About time signatures, the Notation Reference says briefly,
> Time signatures are printed at the beginning of a piece
> and whenever the time signature changes.
That is true, but incomplete: time signatures are also printed when the time
signature hasn't changed -- and it has been that way for y
I was obliquely asked about my reaction to having another person assign an
issue to me.
The main practical effect of assigning an open issue is to deter others from
acting on it: a person interested in working on an issue ought to coordinate
with the current assignee before doing something that
On May 18, 2023, at 08:47, Valentin Petzel wrote:
>
> Essentially it checks: Do we start at the begin of a measure, and if so, does
> or repeated music take exactly one or two measures?
I've dropped the user list from this thread.
I suggest looking at Percent_repeat_iterator::create_contexts()
On May 18, 2023, at 00:29, Werner LEMBERG wrote:
>
>
>>> The snippet 'Adding volta brackets to additional staves'
>>>
>>> https://lsr.di.unimi.it/LSR/Item?id=427
>>>
>>> doesn't seem to do what the description says. Honestly, I have no
>>> idea what this snippet actually wants to demonstrate
On May 17, 2023, at 14:04, Werner LEMBERG wrote:
>
> The snippet 'Adding volta brackets to additional staves'
>
> https://lsr.di.unimi.it/LSR/Item?id=427
>
> doesn't seem to do what the description says. Honestly, I have no
> idea what this snippet actually wants to demonstrate at all...
htt
On May 10, 2023, at 16:19, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> Hi all,
>
> due to various constraints, I am kind of restricted when I will be able
> to do the next releases, so I thought I might as well let you know:
>
> LilyPond 2.25.5 will happen on the weekend
On May 5, 2023, at 06:14, Jean Abou Samra wrote:
>
> Le jeudi 04 mai 2023 à 22:51 -0400, Dan Eble a écrit :
>>
>>
>> I thought it would be nice to be able to draw a tick BarLine from a font
>> glyph in lieu of the default rounded rectangle. I have a working
I thought it would be nice to be able to draw a tick BarLine from a font glyph
in lieu of the default rounded rectangle. I have a working prototype that uses
a new property BarLine.tick-font-glyph-name to enable the behavior, but I need
some advice about font-size.
VaticanaStaff has \override
On Apr 23, 2023, at 05:22, Jean Abou Samra wrote:
>
>> {
>> \textLengthOn
>> s1-"loong"
>> \once \omit Staff.BarLine
>> \clef F
>> r1
>> }
>> with a starting spacer _and_ an omitted BarLine _and_ a clef change.
>>
>> 2.22. is ok, but output of 2.24. is bad.
>
>
> The MM r
Everything I know about 16th-Century Italian I learned from 20th-Century
Spanish. I hope that someone here is able and willing to check my guesses
about this.
The following text seems to follow an introduction to mensural rests, and it
surrounds a figure of a single bar line and a double bar l
On Apr 2, 2023, at 14:39, Kevin Barry wrote:
>
> On Sun, 2 Apr 2023 at 19:31, Jean Abou Samra wrote:
>> I can do
>>
>> (define-public grob-interpret-markup ly:grob-interpret-markup)
>>
>> like we already have for assoc-get aka ly:assoc-get, but it seems
>> clumsy.
>
> That is what I would do.
On Feb 5, 2023, at 09:28, Dan Eble wrote:
>
> 2. Attack this TODO in flower/include/real.hh.
>
>using std::abs; // TODO: replace abs (x) with std::abs (x) and remove this
https://gitlab.com/lilypond/lilypond/-/merge_requests/1834
—
Dan
Friends,
I don't have a Yosemite or El Capitan environment in which to validate changes.
There are two things I would try.
1. Does changing the few occurrences of `#include ` to `#include
` fix it? I don't know that it will, but it seems like less work than
2.
2. Attack this TODO in flower/i
On Jan 26, 2023, at 12:22, David Kastrup wrote:
>
>c'' x2
>
That looks a lot like "twice" to me.
—
Dan
On Jan 23, 2023, at 18:05, David Kastrup wrote:
>
> Dan Eble writes:
>
>> On Jan 23, 2023, at 10:11, David Kastrup wrote:
>>>
>>> I am not saying that 0 is the best choice here. It merely appears to be
>>> rather cheap. I thought of * and / but
On Jan 23, 2023, at 10:11, David Kastrup wrote:
>
> I am not saying that 0 is the best choice here. It merely appears to be
> rather cheap. I thought of * and / but the first renders sequences like
> c4*2 ambiguous and the second would at least become a mess in chord
> mode.
Can you clarify ho
On Jan 16, 2023, at 16:26, David Zelinsky wrote:
> Or try to make a merge request?
Welcome. This is the way.
—
Dan
Should slurs require Stem_engraver?
No: https://gitlab.com/lilypond/lilypond/-/issues/3760#note_339794300
Yes: https://gitlab.com/lilypond/lilypond/-/merge_requests/1800#note_1227831830
I'm looking for some input from old-timers to help decide this so I can avoid
wasting more time on broken or
On Dec 30, 2022, at 12:10, Thomas Morley wrote:
>
> Hi all,
>
> please have a look at:
>
> \version "2.25.0"
>
> {
> \override Score.BarNumber.break-visibility = ##(#f #t #t)
> % \set Score.alternativeNumberingStyle = #'whatever
> b1
> \repeat volta 2 { c' c' }
> \alternative { d' e' }
>
On Dec 3, 2022, at 08:48, Jean Abou Samra wrote:
>
> It rejects the \sectionLabel that comes at the same
> time as an implicit \codaMark.
>
> Should this be supported, or is there a reasoning that
> I am missing?
It's the same concern as from the beginning: I was reluctant to allow assigning
m
On Dec 3, 2022, at 10:25, Jean Abou Samra wrote:
>
> Le 03/12/2022 à 16:18, Dan Eble a écrit :
>> Printing "Coda" instead of a coda mark is the defining use case for
>> \sectionLabel.
>
> But judging from how \repeat segno uses it and from its break-visibility
On Dec 3, 2022, at 08:48, Jean Abou Samra wrote:
>
> It rejects the \sectionLabel that comes at the same
> time as an implicit \codaMark.
Printing "Coda" instead of a coda mark is the defining use case for
\sectionLabel. I'll try to take a closer look at the example soon.
—
Dan
On Nov 26, 2022, at 17:43, Eric Benson wrote:
>
> ton of warnings, mostly of the form "implicit conversion changes
> signedness". These seem like the sort of thing that might not be too hard
> to fix.
https://gitlab.com/lilypond/lilypond/-/merge_requests/1744 fixes warnings other
than conversio
On Nov 19, 2022, at 05:19, Werner LEMBERG wrote:
>
> Attached you can find an example that demonstrates (a), taken from the
> MR.
The sample LGTM. Beyond that, I prefer not to involve myself in the discussion.
—
Dan
On Nov 14, 2022, at 04:43, Paolo Prete wrote:
>
> I need to execute the following automated test:
> given a .ly file, I would like to check if the produced output is what I
> expect it to be.
For checking the impact of LilyPond changes on my own scores, I use a
Docker container and a bash script
On Nov 12, 2022, at 09:07, Werner LEMBERG wrote:
>> 2. Release 2.23.81 without the fix and instead review it properly.
...
> Option 2 is fine with me.
+1
—
Dan
On Oct 22, 2022, at 09:16, Jean Abou Samra wrote:
>
> We have many issues related to ties and to slurs. Would anybody mind creating
> two GitLab labels ~"Ties" and ~"Slurs" for these? It would ease searching for
> defects in those specific areas.
I don't have a problem with your creating any l
On Oct 7, 2022, at 13:51, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> On Thu, 2022-10-06 at 08:39 +0200, Jean Abou Samra wrote:
>> A factor that I was starting to forget in my enthusiasm for branching is
>> !1510 (source locations). Here I am guilty of taking forever to pr
On Oct 7, 2022, at 16:45, Jean Abou Samra wrote:
> Thus I wrote to the general GNU list server admins and proposed
> to step up for being an admin on these lists, just like I am
> already an admin on lilypond-user-fr (the French-speaking equivalent
> of lilypond-user, in case you didn't know).
>
> I'm only familiar with a subset of C++ up to C++03. Would my lack of
> knowledge of modern C++ exclude me from being a contributor?
No. Others will review your code and suggest using new features where it is
appropriate.
> I'm also not an expert on UB in C++, although I very much want to avo
1 - 100 of 865 matches
Mail list logo
