Werner LEMBERG wrote:
Thanks for the report. It's a texinfo 6.8 bug, see
https://gitlab.com/lilypond/lilypond/-/issues/6778
Thanks for the update.
But does this also currently cover the index muddle?
https://lists.gnu.org/archive/html/bug-lilypond/2025-01/msg6.html
Cheers,
Robin
.
Cheers,
Robin
<>
Robin Bannister wrote:
This seems to happen for only the following grobs:
Beam Dots Flag Footnote InstrumentName Rest Slur Stem Tie
And I can see the same sort of corruption with the
'Internals (split HTML)' link on the docs page at
http://lilypond.org/development.html
Robin
'beam' in section 3.4
The same error at the bottom of section 3.2.15 breaks the link loop.
This seems to happen for only the following grobs:
Beam Dots Flag Footnote InstrumentName Rest Slur Stem Tie
The docs for v2.24.4 don't have this problem.
Cheers,
Robin
hrough ten-year-old lilydev mails.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
org domain changed hands last year.
[1]
http://lilypond.org/doc/v2.23/Documentation/contributor/further-git-documentation-resources
[2] http://git-scm.com/book
[3] http://git-scm.com/book/en/v2
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypo
s reading it is incomplete.
So it is too early to judge accuracy.
Changing this will be painful ...
Which was why I didn't ask for that.
Your 'Better ...' would certainly be better!
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond
's value, the
end of scoreA starts moving at 7 and scoreE bit later. I ought to be
able to align the 3 fragments of line 4 in a clean LilyPond way.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
mechanisms are very narrowminded in this
respect.
The most practicable method at the moment is to use two contexts
as in
https://lists.gnu.org/archive/html/lilypond-user/2021-03/msg00297.html
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond
aside:
in LSR1098 https://lsr.di.unimi.it/LSR/Item?id=1098
I had to include a workaround for a 2.19.16 change,
probably related.
HTH,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
about
the order being guaranteed.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hallo there
I noticed this while trying to make an MWE for a different problem.
Maybe it counts as a limitation rather than a bug?
Cheers,
Robin
% MWE for post-event ordering via event-function and wrapper
\markup #(lilypond-version)
ts-first-second =
#(define-event-function
(cons 0 base) radius)
(cons 0 base) )))
delta = \markup \delta-bhr #120 #130 #10 % customised for "sans-serif"
%%%
Just my two cents. Or three in this case.
Cheers,
Robin
___
bug-lilypo
we should
expect:
> new command, as robust replacement for unicode Delta/Triangle.
Cheers,
Robin
quadratic.pdf
Description: Adobe PDF document
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Come on, just do it ;-)
Werner Lemberg has just done it.
This thread was never assigned an issue corresponding to its subject.
This code is now riding piggyback on his Issue 5468.
https://sourceforge.net/p/testlilyissues/issues/5468/
Thanks, Werner.
Cheers,
Robin
op.
The attached yyout2g_robin_B.py replaces version _A:
- halts correctly (with both bison versions)
- is tidier re PEP8
Cheers,
Robin
#!@PYTHON@
#
# yyout2grammar.py
# This file is part of LilyPond, the GNU music typesetter.
#
# Copyright
plines finds these two ly files and their es/fr counterparts.
[1]
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=4cc11ce36f01076b3b5e6bc93b865c612ea68036
[2] http://lists.gnu.org/archive/html/lilypond-user/2008-10/msg00135.html
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
triggers suicide rather than transparency.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t some kind of binary-search regression if nobody
else has the setup for it.
See
http://sourceforge.net/p/testlilyissues/issues/4448/#c45f
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
g
- I chose 'Allow'
- but nothing happens when I click (not even a browser activity)
So it would seem so.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
r block.
http://www.lilypond.org/doc/v2.19/Documentation/notation/the-layout-block
mentions "\paper variables that affect score layout"
but doesn't seem to provide a list.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://list
will probably need to make the code
cater for these differences anyway.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
to do that?
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 14.02.2014 20:05, Pierre Perol-Schneider wrote:
[...] ask him how
he would see his snippet upgraded ?
http://lsr.dsi.unimi.it/LSR/Item?id=651
If you are referring to the horizontal distortion,
this is cured by prefixing the extra-spacing-width
override with "Staff.".
Che
Colin Hall wrote:
However there is no documentation that describes common errors for new
users and their solutions
For common errors, see
http://lilypond.org/doc/v2.14/Documentation/usage/common-errors
Cheers,
Robin
___
bug-lilypond mailing
Reinhold Kainhofer wrote:
The example had both \larger and \smaller in the same markup.
Maybe a copy/paste typo?
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=07f53dbc18c8a8903fc8796029faa3ec3c0e707f
Cheers,
Robin
___
bug
like this.)
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
9) "offset"
\markup \line {
"concat with empty-markup:" \box \concat { \empty-markup \offset }
" concat with null markup: "\box \concat { \null \offset }
}
%%
Cheers,
Robin
___
bu
signature.
This override was corrupted by convert.ly for 2.11.23.
It is still incorrect despite the update reported today on lilypond-user.
http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00196.html
Cheers,
Robin
%example of use:
\score{ \relative c'{ \set Score.timin
,
ensure the LSR377 demo contains a linebreak+leftBracket combination.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
**lost**
Only lower case because a very peripheral concern.
But this reminder has had NO RESPONSE.
(Should I have done something differently?)
http://lists.gnu.org/archive/html/bug-lilypond/2011-01/msg00480.html
Cheers,
Robin
___
bug-lilypond
nd in issue 601.
http://code.google.com/p/lilypond/issues/detail?id=601
The hint there by Valentin regarding #'infinite-spacing-height is outdated
and would now read like
\override PianoStaff.Arpeggio #'extra-spacing-height = #'(-inf.0
the right hand:
\once \override BreathingSign #'transparent = ##t \breathe
Cheers,
Robin
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Neil Puttock wrote:
Works fine here
Thanks a lot! This is very easy to apply.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
in a simple workaround to get from new to old as
illustrated in the original bug report.
http://lists.gnu.org/archive/html/bug-lilypond/2011-02/msg00541.html
I want this for the use case on the lilypond-user link there:
a workaround for issue 758.
Cheers,
/2011-02/msg00581.html
bareSnippet =
{
e'1
\break \bar ":"
\set Score.skipTypesetting = ##t
d'1
\break \bar "||"
\set Score.skipTypesetting = ##f
c'1
}
\paper { line-width = 60\mm }
{
\set Staff.instrumentName = #(lilypond-version)
devel/2008-08/msg00392.html
The custos hack should read as in
http://lists.gnu.org/archive/html/lilypond-user/2008-01/msg00580.html
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Patrick McCarty wrote:
I will try to see what's going on.
See here for an overview
http://lists.gnu.org/archive/html/bug-lilypond/2010-02/msg00124.html
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/ma
ve an 'origin property saying
'position unknown', which results in a link with invalid position.
With the workaround propagateOrigins (cf attachment), the chordmode
note events are given the position info of their containing chord,
and the resulting links are valid.
Cheers,
Robin
Robin Bannister wrote:
This of course also applies to the issue(s) I referenced in my followup
http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00294.html
I am unsuccessful again. I will just spell out the main point:
The collision snippet which is registered as issue 821
http
\paper { ragged-right = ##t }
{% seen with versions 2.12.1, 2.10.33, 2.8.8
<< b'1 \\ s1 \\ 1 \arpeggio >> % arpeggio collides with voice1
}% unless there is an accidental (in any voice)
Cheers,
Robin
___
bug-lilypond mailing
the collision avoidance is positioning the second note
as if the first notehead was the same size as the second notehead.
Issue 428 has a related title but is concerned with articulations.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gn
collisions are produced when this snippet is run with 2.8.8 or 2.10.33.
The priority should therefore be not Medium but Regression.
This of course also applies to the issue(s) I referenced in my followup
http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00294.html
Cheers,
Robin
P.S
note aspect didn't make it into the title of issue 880.
But it is this distinguishing characteristic which can help disentangle
the multiple issues, as my followup did with 601c2 and 821.
Cheers,
Robin
___
bug-lilypond mailing list
bu
- stretch
http://lists.gnu.org/archive/html/lilypond-user/2009-09/msg00271.html
Cheers,
Robin
P.S. Apologies if this already exists.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo
b 16 % collision
\dense a 16 % collision
\dense g 16
\dense f 16
}
\layout {
indent = 0
line-width = 120
ragged-right = ##f
}
}
Cheers,
Robin
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
/lilypond/issues/detail?id=821
LSR 410
http://lsr.dsi.unimi.it/LSR/Item?id=410
NR 2.2 keyboard headword (Ravel)
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Keyboard-and-other-multi_002dstaff-instruments
Cheers,
Robin
___
bug-lilypond
mark "sometimes"
\laissezVibrer \arpeggio
\laissezVibrer \arpeggio
\bar "||"
\laissezVibrer \arpeggio
\laissezVibrer \arpeggio \mark "always"
\laissezVibrer \arpeggio
\laissezVibrer \arpeggio
}
Cheers,
Robin
___
> Nice :-)
I think this deserves a NEWS entry.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
gt; no heads for arpeggio found?
and kills the arpeggio.
There is another demo and a proposed workaround on the user list at
http://lists.gnu.org/archive/html/lilypond-user/2009-09/msg00735.html
Cheers,
Robin
___
The corresponding override currently in the LSR is ineffective.
http://lsr.dsi.unimi.it/LSR/Item?id=377
Cheers,
Robin
(2.11.23 fixed issue 97)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
e \override Staff.TimeSignature #'X-extent = #'(0 . 3)
But the same problem exists with clefs and barlines, etc.
If a measure starts with such an arpeggio, you could try inserting
\cadenzaOn s8 \cadenzaOff
Cheers,
Robin
___
bug-lily
ifferently now w.r.t. pdf refresh,
but commenting out the delete never gave me any trouble (on XP).
And note that W_OK only tells you about the (static) read-only attribute.
So Lilypond always tries to delete, whether the file is locked or not.
>
\version "2.12.1"
\paper { ragged-right = ##t }
{
4. s8 \small 4. s8 4. s8 4. s8
}
% The augmentation dots are not shifted away from some chords
% when the notehead size is reduced
% this is a regression error (2.10.33 is ok)
too long for one wiggle
}
It looks like ly:arpeggio::print is careless at heads[dir] -=
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
y form a
single pile and so offer no possibility for Tetris-like packing.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
The assertion "Objects specified first are closest to the note."
is false for unfold values greater than 1.
This report was prompted by
http://lists.gnu.org/archive/html/lilypond-user/2009-03/msg00735.html
which may not be quite the same thing.
Cheers,
Robin
_
decimal code for the character required
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
e hexadecimal code for the character required
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
outine is mentioned at the bottom of IR 4,
and is similar to the end of ConvertUTF32toUTF8 in
http://www.unicode.org/Public/PROGRAMS/CVTUTF/ConvertUTF.c
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
But base 16 and the codespace slicing went hand in hand.)
So lets say
> The following example shows Unicode code points being used
And further up, lets use this same term instead of
"Unicode escape sequence" and "Unicode hexadecimal code"
Cheers,
Robin
h code points.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
ere a (private) vertical alignment, which has
changed from #DOWN to #CENTER.
See also
http://lists.gnu.org/archive/html/lilypond-user/2009-02/msg00130.html
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mail
> 148 millimeters, the height of a6 paper in landscape orientation
says v2.12 NR 4.6.1.
Readers are not told what size a point is;
they have to work it out from the example given.
So it is important to get this right: 105 mm
Cheers,
Ro
by automagic.
If you do not (yet) recognise such situations, Lilypond can be frustrating.
.
This case is mentioned at the start of Learning Manual 2.3.2.
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Multiple-
staves
Cheers,
Robin
___
In the (latest) docs (both online and download)
I see no navigation menu bars.
These were present in 2.11.60.
And you can see them at kainhofer.com (pre 2.11.62).
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
fer action on B rather than on C.
(*Slurs* warn when unterminated.)
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Mats,
Windows 98 SE and it is 2.8.0-5
I hope this gets to the list.
Robin
Mats Bengtsson wrote:
Could you please send information on which Windows version you use and
the exact version number of the LilyPond package
(if you downloaded it today, it was 2.8.0-5). Send the information to
b6 45 df a8 08 74 40 4f 78 49 8b 4d c4
Stack dump:
012c27a0 0dfe 012c0ec4 01c0e1fc 012c0ea4 012c27a0 012c0e90
00b0 012c0ec4 0dfa 0dfa 01ebf43c 00ebf2d8 007ba61a
Like to know what's wrong & what I'm doing
Greetings,
When I start Lilypond, I get a DOS screen, and after a while, a message with
the
following details
LILYPOND-WINDOWS caused an invalid page fault in
module LIBFREETYPE-6.DLL at 024f:007bbeb1.
Registers:
EAX=0001 CS=024f EIP=007bbeb1 EFLGS=00010207
EBX=0001 SS=0257 ESP=00ebf280
71 matches
Mail list logo