Feature request: Fix cascading error messages

2022-03-28 Thread Christopher Heckman
scade-level=N file.ly which, for any given line, prints the first N error messages, and after that a message saying that further error messages have been suppressed. A default value for N might be 3 or 4. What does everyone think? --- Christopher Heckman

Re: Feature request: Fix cascading error messages

2022-03-28 Thread Christopher Heckman
On Mon, Mar 28, 2022 at 4:58 PM David Kastrup wrote: > > Christopher Heckman writes: > > > I have a request concerning Lilypond that has bothered me for a while, > > but which I haven't seen any one else complain about. It is the > > cascade of error messages yo

Re: percent repeats (bug?)

2019-07-03 Thread Christopher Heckman
In a post/email sent out several months ago, Randy brought up some issues about percent repeats over more than two measures. He cited two issues, related to where the percent sign is placed and what it looks like. I would like to add a third: line breaks aren't allowed in the middle of a \repeat p

Making a Hairpin end close to the end of a Score

2016-10-30 Thread Christopher Heckman
rGrace, with an invisible grace note. \absolute { c'2\> \afterGrace d' { s16\! } | } MIDI translates this as you would expect, without an extra note at the end. However, this will not work if the hairpin starts on the last printed no

Re: Making a Hairpin end close to the end of a Score

2016-11-04 Thread Christopher Heckman
On Fri, Nov 4, 2016 at 9:36 AM, Simon Albrecht wrote: > On 04.11.2016 09:11, Christopher Heckman wrote: >> >> On Tue, Nov 1, 2016 at 3:08 PM, Simon Albrecht >> wrote: >>> >>> Hi Chris, >>> [...] >>> In that case, another opportunity t

Suggestions for the lilypond-user archive search

2024-07-27 Thread Christopher Heckman
This is a useful website to bookmark and use, but I've found over the years that it can be improved. My suggestions are: (1) Allow an option to search by thread. If X is a thread that matches the search, then most of the emails there (and in Re: X) will also match, filling up the screen. (2) The

FYI: Nested Markuplist-Score-Midi Block Behavior

2024-11-12 Thread Christopher Heckman
I don't know whether this is a bug or not, but if you put a score block inside of a markuplist, you cannot export MIDI from it. If it's not fixed, it should be documented at the website. Minimal(?) example: \markuplist { \score { { c1 } \layout { } \midi { } }

Re: FYI: Nested Markuplist-Score-Midi Block Behavior

2024-11-15 Thread Christopher Heckman
On Fri, Nov 15, 2024 at 10:58 PM Werner LEMBERG wrote: > > [Sending this e-mail again to the 'lilypond-user' list, which we > forgot to include in our conversation.] > > >> Maybe you are mixing up the the `\score` *markup* command (to be > >> used within `\markup` or `\markuplist`) with the 'norma

Re: Some things need need to be fixed on the interfaces pages

2024-12-10 Thread Christopher Heckman
On Tue, Dec 10, 2024 at 12:58 AM Werner LEMBERG wrote: > > > I went through the interfaces pages recently, and I found a couple of > > things that need to be fixed (these is from the 2.25 version). > > > > (1) The centered-spanner-interface page talks about using it with > > MultiMeasureRest,

Some things need need to be fixed on the interfaces pages

2024-12-09 Thread Christopher Heckman
I went through the interfaces pages recently, and I found a couple of things that need to be fixed (these is from the 2.25 version). (1) The centered-spanner-interface page talks about using it with MultiMeasureRest, but MultiMeasureRest isn't among the list of grobs at the bottom that use it. (Th

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Christopher Heckman
On Tue, Dec 10, 2024 at 9:38 PM Werner LEMBERG wrote: > > >> The policy of LilyPond is to avoid different property names for > >> similar functionality, which often leads to cryptic property > >> descriptions to be as generic as possible. In this particular case > >> an example is given, which is

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Christopher Heckman
On Tue, Dec 10, 2024 at 9:38 PM Werner LEMBERG wrote: > > >> The policy of LilyPond is to avoid different property names for > >> similar functionality, which often leads to cryptic property > >> descriptions to be as generic as possible. In this particular case > >> an example is given, which is

Re: Some things need need to be fixed on the interfaces pages

2024-12-12 Thread Christopher Heckman
On Thu, Dec 12, 2024 at 4:05 PM David Kastrup wrote: > > Christopher Heckman writes: > > > On Wed, Dec 11, 2024 at 10:58 PM Werner LEMBERG wrote: > >> > >> >> IIRC, a suggestion in the mentioned thread is to make the property > >> >> descri

Re: Some things need need to be fixed on the interfaces pages

2024-12-12 Thread Christopher Heckman
On Wed, Dec 11, 2024 at 10:58 PM Werner LEMBERG wrote: > > >> IIRC, a suggestion in the mentioned thread is to make the property > >> description displayed for a given grob show which interfaces it is > >> part of, for example > >> > >> ``` > >> ‘spacing-pair’ (pair) > >> interface(s): > >>