This looks like another instance of the infamous and intractable bug 34:
https://gitlab.com/lilypond/lilypond/-/issues/34
The work-round is to add a corresponding grace spacer note in the other staff:
https://lists.gnu.org/archive/html/bug-lilypond/2012-08/msg00084.html
> On 4 Nov 2021, at 17:15
I think you're right. I reported this about a year ago, but I think it was a
really busy time for the developers and it fell through the cracks. There's a
little more detail at
https://lists.gnu.org/archive/html/bug-lilypond/2019-10/msg00031.html
-- Graham
> On 28 Oct 2020, at 15:20, Johanne
The fact that I still don't understand this aspect of lilypond is no doubt a
bug in me, but I'm pretty sure that the example in this section of the NR has
its own problem: I cannot see any material difference between the two bars of
the output, but the text below it refers to collisions between
On 9 Nov 2018, at 14:07, Andrew Bernard wrote:
> I do not know
> how to get the lilypond command for compiling out of Frescobaldi to examine.
...but you might be able to get it out of the process table by using the Linux
command "ps" with a suitable flag (see "man ps" on your distro). This ne
meanwhile, Harm has kindly shown me a work-round. It is in the first
two bars of this example, which also serves to illustrate the partial
effect of \omit.
\version "2.19.40"
resetBounds =
\temporary \override Hairpin.after-line-breaking =
#(lambda (
The Notation Reference says [1]: " omit [music] - item (symbol list or
music): Set item's "stencil" property to #f, effectively omitting it
without taking up space. "
However, when applied to dynamics, space is taken up. This is
inconvenient, as one has to resort to \tag #'pdf {...} and \tag #'mi
First, an apology to the developers, and in particular to Harm, for my
previous, hasty, attempt to report this in March, which must have
appeared selfishly peremptory. Fortunately the message seems not to
have reached this list and, now that there's a gap in the rest of life I
can have another go:
(bug-lilypond: a regression with note-spacing in proximity to dynamic
text.)
On Wed, 2016-03-23 at 11:38 +0100, Thomas Morley wrote:
> a minimal example would have been:
>
> \version "2.19.38"
>
> music = { g'8(\p f'!) s2. }
> \new StaffGroup \new Staff \music
Wow. To get to that, I thin
www.lilypond.org is not responding this morning. I can ping it at
82.94.241.173 so, unless there's a problem with DNS, it looks like the
webserver has a problem.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bu
On Wed, 2015-10-14 at 17:24 +0100, Phil Holmes wrote:
> "David Kastrup" wrote in message
> news:87twpt4rx3@fencepost.gnu.org...
>
> > The LSR version of vspace (when was this ever a good idea?) by now has
> > markedly diverged from the built-in variant, so it really should get
> > removed a
On Sun, 2014-08-24 at 00:03 +0200, Janek WarchoĊ wrote:
> Btw, "bn" would also help people who have to switch between german and
> dutch/english naming often (e.g. me).
Janek makes a good point, but I'm not sure whether the problem to which
he refers is caused by the existence of different natio
Is there a policy about the persistence of snippet numbering? I suspect
I'm not alone in adding to my scores comments such as: "% see snippet
999"
I suppose a more neutral question is: "What is the recommended long-term
way to refer to a snippet?"
thanks
-- Graham
On Sun, 2014-02-16 at 23:26 +0
On Fri, 2013-11-29 at 06:59 +0100, David Kastrup wrote:
> Graham King writes:
> > %tempoWholesPerMinute = #(ly:make-moment 180 4)
> Keith answered the principal question already. So I have a side
> question: why would you want to do that?
Short version of a long story:
Thanks Keith,
apologies for cluttering the list - I must be gettig tired!
On Thu, 2013-11-28 at 23:18 +, Keith OHara wrote:
> Graham King tremagi.org.uk> writes:
>
> > If I adjust the comments in the following code, \tempo works fine but
> > tempoWholesPerMinut
If I adjust the comments in the following code, \tempo works fine but
tempoWholesPerMinute has no effect. Has anyone else seen this?
\version "2.17.95"
\score {
\relative c' { c d e f }
\layout {}
\midi {
%tempoWholesPerMinute = #(ly:make-moment 180 4)
\tempo 4 = 180
Confirmed. Lilypond 2.16.2 on OSX 10.6.8. Output attached.
On Wed, 2013-10-09 at 22:50 +0200, Marek Klein wrote:
> I have different result with GNU/Linux x86: LilyPond 2.16.2-1. Could
> someone on Mac OS confirm this behaviour?
>
> Marek
> bug squad member
<>
Keith,
many thanks. Your analysis is spot on and your example is much better
than mine.
-- Graham
On Tue, 2013-09-17 at 04:48 +, Keith OHara wrote:
> Keith OHara oco.net> writes:
>
> > Graham King googlemail.com> writes:
> >
> > > Adjust the comments at
> I'm not top posting.
In trying to create a modern edition of a piece of renaissance polyphony,
I've found a problem in the interaction between \scaleDurations and the
Completion_heads_engraver. I've left 3 lines of comments at the top of the
code to give some idea why I want to do this crazy th
() sets the
cursor position to column 1.
I'm a first-time lilypond user, and looking forward to learning the
program. Thanks for a first class piece of software.
kind regards,
-- Graham King
___
bug-lilypond mailing list
bug-lilypond@gnu.org
19 matches
Mail list logo
