Behavior on Errors; Separate Run Output

. Some sort of a separator (even if it's just hyphens) should be put between compilings. --- Christopher Heckman ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated

As Gus Baird once said, when something goes wrong in a program, you should inform a user in the least surprising way. --- Christopher Heckman -- View this message in context: http://lilypond.1069038.n5.nabble.com/Issue-2214-in-lilypond-fatal-error-reported-when-version-is-too-old-but-correct

Mark / Barcheck Bug (#1626) Appearing Again

This was mentioned about five years ago, but I re-discovered it. Does the so-called patch fix this? The bug is as follows: Placing the \mark can have an effect on the bar check. If you run Lilypond with the following code, the barcheck will fail exactly once. --- CCH \new Staff { \mark | c4 c c

Re: Mark / Barcheck Bug (#1626) Appearing Again

After playing around with Lilypond for a while, I found out that \mark appears to "gobble up" the next token in the list. For example, \new Staff { c \mark | c c c | } and \new Staff { c c c c | c c c \mark | c | c c c c | } should give barcheck errors but don't. That's because

midi2ly: Fraction Reduction + 2 minor issues

(1) When midi2ly is run, it will print fractions with large numerators and denominators, like r4*361/120 e4*29/120 r4*31/120 e4*59/120 r4*361/120 e4*29/120 when the actual durations are more likely to be r2. e4*1/4 r4*1/4 e4*1/2 r2. e4*1/4 r4*1/4 e4*1/2 r2. e4*1/4 I have written a patch to fix

Re: bug-lilypond Digest, Vol 173, Issue 17

On Mon, Apr 17, 2017 at 9:00 AM, <bug-lilypond-requ...@gnu.org> wrote: > > On Sun, Apr 16, 2017 at 9:00 AM, Martin Tarenskeen > <m.tarensk...@zonnet.nl> wrote: > > On Sun, 16 Apr 2017, Christopher Heckman wrote: > >>> I like the idea and really apprecia

[no subject]

> From: Dan Eble > Subject: Default repeat type > > It would be convenient if both of these did the same thing: > > A. \lyricmode { Ah __ \repeat unfold 7 _ } > B. \lyricmode { Ah __ \repeat 7 _ } Maybe the user should be able to set the default repeat type? After all,

Re: bug-lilypond Digest, Vol 189, Issue 17

On Sun, Aug 26, 2018 at 7:04 AM, wrote: > > Message: 3 > Date: Sun, 26 Aug 2018 11:43:44 +0200 > From: Thomas Morley > To: Pierre Perol-Schneider > Cc: bug-lilypond > Subject: Re: Doc 2.4.2: Indicating harmonics and dampened notes > Message-ID: > > Content-Type: text/plain;

Request: Print actual number of pages after compiling

Obviously, in this situation, I want to know the exact number of pages without re-opening the .pdf file. Could someone add a one-line statement to print out the actual number of pages, near the "Success: compilation successfully completed" message? ---

Bug: q doesn't keep fingerings in TabStaff context

I searched for this at the archives, but maybe I didn't look in the right place. The title is pretty self-expanatory. If the pitch e is normally played on the 5th string of a guitar (after transposition), then \new TabStaff { q } will show e played on the 6th string and then on the 5th string,

Re: bug-lilypond Digest, Vol 197, Issue 11

On Thu, Apr 25, 2019 at 9:05 AM wrote: > > Am Mi., 24. Apr. 2019 um 23:24 Uhr schrieb Christopher Heckman > : > > > > I searched for this at the archives, but maybe I didn't look in the right > > place. > > > > The title is pretty self-expanatory. If the pi

Re: polyphony and TabStaff: don’t put two voices on the same string (Malte Meyn)

On Sat, Oct 19, 2019 at 9:00 AM wrote: > > Date: Sat, 19 Oct 2019 10:06:10 +0200 > From: Malte Meyn > To: bug-lilypond > Subject: polyphony and TabStaff: don’t put two voices on the same > string > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi list, > >

"Library not loaded" error on MacOS version

g the same problem, and if so, what was your workaround? --- Christopher Heckman ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Polychord Support

> Message: 2 > Date: Sat, 29 Jan 2022 21:30:36 +0100 > From: skoop...@web.de > To: bug-lilypond@gnu.org > Subject: Polychord support > Message-ID: > > > > Content-Type: text/plain; charset=UTF-8 > > Hello, > > is there meanwhile an easy way to write polychords as a chord name? I found a