Phil Holmes mail at philholmes.net writes:
I'm unable to reproduce on either Windows or Linux
Interesting. I can, with Ubuntu 14.04 and Lily 2.18.2. What else might
make a difference?
Oops, I can see the problem as well on 2.18.2.
I didn't notice the version number in the report, and saw
Simon Albrecht simon.albrecht at mail.de writes:
Am 12.07.2015 um 13:20 schrieb Greg:
I'm not top posting.
This may be related to issue 3299 but I don't have the technical knowledge
to confirm this.
I think this is issue 1861
https://code.google.com/p/lilypond/issues/detail?id=1861,
Colin Campbell cpkc at shaw.ca writes:
Both pieces of code compile without error and produce reasonable output
for me, using Frescobaldi, LilyPond 2.19.22 and KXStudio (Ubuntu 15.04).
I could reproduce it, on Windows, so I added
https://code.google.com/p/lilypond/issues/detail?id=4447
Thomas Morley thomasmorley65 at gmail.com writes:
Example #1 gives a warning in 2.18.2, aborting in 2.19.21
EXAMPLE #1 (see http://lists.gnu.org/archive/html/lilypond-user/2015-06/
msg00278.html)
I added https://code.google.com/p/lilypond/issues/detail?id=4447
Example #2 gives no error or
I have trouble replying to cross-posts, but the bug from this thread is now
https://code.google.com/p/lilypond/issues/detail?id=4310
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
There is variant \key\default that re-prints the current key-signature, but
using it with midi causes an error and early exit from the Scheme interpreter.
\score {
{\key g\major g' b' d'' b' \key\default g'1 }
\layout{}
\midi{}
}
___
David Kastrup dak at gnu.org writes:
What should be the desired behavior? The easiest implementation would
likely be just ignoring the \key\default in Midi.
Good point. I should have made some indication of desired behavior.
I think either ignoring or repeating in MIDI should be fine.
On Sun, 04 Jan 2015 11:38:28 -0800, Dan Eble d...@faithful.be wrote:
Aha! Overriding Rest.stencil and changing the style there was insufficient
because ly::rest::width and other callbacks *bypass* the stencil property, so
my change of style had not yet been applied when the X-extent was
Federico Bruni fedelogy at gmail.com writes:
Il giorno ven 26 dic 2014 alle 23:32, Trevor Daniels
t.daniels at treda.co.uk ha scritto:
Was this regtest never executed before being committed?!
Well, at least by the automatic doc build:
Dan Eble nine.fierce.ballads at gmail.com writes:
% This input caused a segfault on OS X Yosemite with Lilypond 2.19.15.
\version 2.19.0
\new Staff {
\relative d' {
\time 8/1024 d128 |
\time 9/1 d1
}
}
David Kastrup writes:
You are both omitting
David Kastrup dak at gnu.org writes:
Keith OHara k-ohara5a5a at oco.net writes:
It seems that we knew about these problems, bug then added the
regression tests anyway.
We have bug-reports, so it seems we lose no information
Bug reports or an actual issue in the tracker?
Well
Trevor Daniels t.daniels at treda.co.uk writes:
You could revert commit 586a6d331e22d0e1a255068f07c534d219c7c902 locally
I've boldly reverted the commit, removing those two regtests from staging
so we don't have build errors.
I suspect it is actually issue 4231 that caused the problem, because
Added as
http://code.google.com/p/lilypond/issues/detail?id=4227
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Dan Eble dan at faithful.be writes:
What do you think of renaming the current “voice” style to something like
The name voice has a simple relation to the simple thing it does.
and adding new styles “voice” and “voice-cautionary”
These styles would be very similar to modern-voice-* except
Knute Snortum ksnortum at gmail.com writes:
Way back in Lilypond 2.14 if you wrote c:9^7 you would get Cadd9, but now
you get C9. This makes it indistinguishable from c:9.
Thanks, Knute
I thought I remembered the change that caused this, so I added
Dan Eble dan at faithful.be writes:
Is it expected that these two ways of changing the appearance of
a rest yield different spacing between the rest and the dot?
I would not think so.
The dot is placed a standard distance right of the x-extent of the rest
glyph, which should be the same in
Is it because NullVoice is has now been moved in terms of its context
'position' (if that is the right word)?
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=fc8c2d680464130af497c386ed5f0033d3fd7470
Yes. But we can revert that.
The commit just before that one fixed the bugs in
David Nalesnik david.nalesnik at gmail.com writes:
In the US, I hear people calling c-sharp c often enough. This usage is
certainly not good practice in music theory classes (where I correct it
whenever I can). I can't say anything about informal usage.
The original question here was about
David Winfrey dlw at patriot.net writes:
A new accidental for entering natural notes would be useful.
In English, this would be 'n', as in 'bn4' or 'gn2'.
This is in the bug tracker as
http://code.google.com/p/lilypond/issues/detail?id=4076
It is easy to add an alternate name for a pitch,
Simon Albrecht simon.albrecht at mail.de writes:
By default, OttavaBracket has a minimum-length of 1 and the text is
right-aligned to the first note in the range of the ottavation. Thus,
it's sometimes impossible to discern from which note on the ottava is
supposed to be applied. In
Phil Holmes mail at philholmes.net writes:
David Winfrey dlw at patriot.net wrote in message
news:loom.20140822T182826-365 at post.gmane.org...
A new accidental for entering natural notes would be useful.
In English, this would be 'n', as in 'bn4' or 'gn2'.
These would have exactly
Simon Albrecht simon.albrecht at mail.de writes:
By default, OttavaBracket has a minimum-length of 1 and the text is
right-aligned to the first note in the range of the ottavation. Thus,
it's sometimes impossible to discern from which note on the ottava is
supposed to be applied.
It is
Karol Majewski karolm2 at wp.pl writes:
This is an excerpt from random piece. If you add \noBreak command at the
end of measure 9 and 11, than the whole
spacing becomes distorted! Bug?
Is the 'distorted' spacing better or worse than in the first case?
If we want different behavior, we would
Not a bug, but probably of interest here.
For some reason I compared the regression tests between 2.16 and 2.18, up
through lyrics-tenor-clef.ly before I got tired. Many look a bit nicer. For
most changes I recognized the cause.
Some non-obvious changes:
‘ambitus-with-ligature.ly’ lost
Trevor Daniels t.daniels at treda.co.uk writes:
The description of \defineBarLine in NR 1.2.5 does
not make it clear that the parameter called bartype
doubles as both the name of the barline being defined
and the definition of the bar line to be used in
the middle of the line (i.e. not at
Helge Hafting helge.hafting at ntebb.no writes:
\new PianoStaff
\new Staff = up \relative a' {
a2 e2
\mark \default
Due to issue 34, we need here: \grace s8
}
\new Staff = down \relative f' {
a2 e2
\acciaccatura e8 a1
Timothy Lanfear lanfear at costamagna.demon.co.uk writes:
As suggested in
http://www.lilypond.org/doc/v2.17/Documentation/notation/writing-
parts#formatting-cue-notes,
I tried using instrumentSwitch to label cue voices. The instrument names are
printed twice in different size fonts.
Oops.
Timothy Lanfear lanfear at costamagna.demon.co.uk writes:
Keith OHara k-ohara5a5a at oco.net writes:
The double printing from an \instrumentSwitch is issue 2835.
\instrumentSwitch has been called into service for two jobs
Thanks. you gave me enough hints to construct my preferred
Kieren MacMillan kieren_macmillan at sympatico.ca writes:
For the last few [development] versions, I’ve found random checkmarks
appearing in my scores:
Random guesses.
The editing environment called Frescobaldi has a new preview-mode, that
marks up the output including things that might
Eluze eluzew at gmail.com writes:
with the code
\new GrandStaff
\new StaffGroup
\new Staff { c'1 }
\new Staff { d'1 }
\new Staff { \set Staff.instrumentName = last f'1 }
the staff named last is engraved /above/ the StaffGroup
because the StaffGroup is not
Karol Majewski karol.majewsky at gmail.com writes:
{
eis' b' d''4 ^1 eis' b' d''8 ^1 eis' b'8 r2
}
Vertical position of the numerals should be the same.
It is intentional that the fingering on the beamed chords is above
the beam, so that when more than one chord has fingering, those
karol karolm2 at wp.pl writes:
My question is: how can I improve the code
to have this TextScript closer to the staff?
Ask on the lilypond-user mailing list.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
karol karolm2 at wp.pl writes:
{
e'' f'' cis'''1 ^1^2^5
}
Unfortunately this is a different bug -- or two -- so it will
not be fixed at the same time as collisions between Fingerings.
(1) LilyPond has never looked at Accidentals when placing Fingering;
until recently that caused only
Colin Campbell cpkc at shaw.ca writes:
So, you can do the same as we did when using version 2.12: rearrange
the order of pitches in the chord so a main-column note comes first.
Would it be worth making a note of a Known Issue, in NR 1.7.1?
Yes. Either bug-report or known issue would be
Karol Majewski karol.majewsky at gmail.com writes:
\version 2.17.96
{
\set fingeringOrientations = #'(up) dis''-1 a''-4 b''-51
}
PS. I want to have all numerals in one column.
Karol,
To have one column, put the fingering on the chords as a whole
{
\set fingeringOrientations = #'(up)
David Kastrup dak at gnu.org writes:
3312ca325600af8adf1fbad1a9546aa1566fab66 is the first bad commit
commit 3312ca325600af8adf1fbad1a9546aa1566fab66
Author: Keith OHara k-ohara5a5a at oco.net
Date: Wed Aug 21 13:51:49 2013 -0700
side-position-interface: do not recursively add
Graham King lilypond at tremagi.org.uk writes:
If I adjust the comments in the following code, \tempo works fine but
tempoWholesPerMinute has no effect. Has anyone else seen this?
You needed to change the variable in the Score 'context'
\midi {
\context {\Score
tempoWholesPerMinute
Ryan McClure ryanmichaelmcclure at gmail.com writes:
Can a discussion be moved? I've never seen that done before on a mailing
list, at least not to my knowledge. It started out as a bug--what I
thought was a bug, anyway--in how the accidental was aligned to the stem.
There is no a bug in
On Wed, 27 Nov 2013 06:35:48 -0800, Hans Aberg haber...@telia.com wrote:
On 27 Nov 2013, at 04:37, Keith OHara k-ohara5...@oco.net wrote:
Philippe Ploquin philippeploquin at neuf.fr writes:
The accidental called eksik bakiye is missing in lilypond.
Can anyone give a link to a reference image
Philippe Ploquin philippeploquin at neuf.fr writes:
The accidental called eksik bakiye is missing in lilypond.
On Wed, 27 Nov 2013 12:08:02 -0800, Hans Aberg haber...@telia.com wrote:
In the Ph.D. thesis by Ozan Yarman, 79-tone tuning theory for Turkish maqam music, p.
90 (PDF 106), he
Philippe Ploquin philippeploquin at neuf.fr writes:
The accidental called eksik bakiye is missing in lilypond.
Can anyone give a link to a reference image showing this accidental in use?
If and when someone edits the font, we should be careful to associate the
glyph with the correct
ryanmichaelmcclure ryanmichaelmcclure at gmail.com writes:
Here is the exact sample of what I am trying to do, except I am writing out
the repeats. I want the eighth notes to have the stems down and the solo
note stem up.
We should discuss this on -user
Mario Bolognani mabol at fastwebnet.it writes:
staffs are are not separated as specified.
When you ask LilyPond to make the tuplet number transparent
terzinesenza = \override TupletNumber #'transparent = ##t
she gives the number the usual space.
To understand the space between the staves
Eluze eluzew at gmail.com writes:
If you put A at the bottom of your list, the lyrics become spaced close
to the staves.
not sure what you mean with this - example?
staff=\new Staff = staff \new Voice = voice { a'1 a'1 }
lyric=\context Lyrics = lyric \lyricsto voice { oh oh }
A =
Eluze eluzew at gmail.com writes:
staff=\new Staff = staff \new Voice = voice { a'1 a'1 }
lyric=\context Lyrics = lyric \lyricsto voice { oh oh }
A = \staff \lyric
B= \staff \new Lyrics = lyric \with { alignAboveContext = staff } \lyric
C= \new Lyrics = lyric \staff \lyric
Gilberto Agostinho gilbertohasnofb at gmail.com writes:
1) Some ugly positioning when using \pitchedTrill:
This was from an intentional change to place things as close as they fit
http://code.google.com/p/lilypond/issues/detail?id=2527
but it should have come with padding.
I added
Keith OHara k-ohara5a5a at oco.net writes:
Graham King kayakfreelunch at googlemail.com writes:
Adjust the comments at lines 10 and 13 below, to trigger the bug
or not, and observe the length of the two notes that cross barlines.
If I understand you ...
Graham emailed to confirm my
Graham King kayakfreelunch at googlemail.com writes:
Adjust the comments at lines 10 and 13 below, to trigger the bug
or not, and observe the length of the two notes that cross barlines.
The time signature in the example confuses me.
If I understand you, the problem is that the notes
Jean-Charles Malahieude lilyfan at orange.fr writes:
1- unfoldRepeats doesn't work, neither on pdf nor in midi, [on Quotes]
You can
\addQuote echo { \singer }
before the printed score, and
\addQuote echo { \unfoldRepeats \singer }
before the midi score with \unfoldRepeats
I'll add a
Federico Bruni fedelogy at gmail.com writes:
convert-ly can't update these \paper options:
\version 2.14.2
after-title-spacing markup-system-spacing
between-system-spacing system-system-spacing
The conversion rules think this change happened with version 2.13.36,
so they do not
Jean-Charles Malahieude lilyfan at orange.fr writes:
When using *quoteDuring*, I would expect the third staff not to
displayed at normal size, not as a *cueVoice*.
I could not find this in the bug list, so added
http://code.google.com/p/lilypond/issues/detail?id=3489
You can avoid the
Another case that eats memory on Windows came up in the verification test
for issue 2910. There was no problem on Linux, and small changes avoid
the problem on Windows.
I have not been able to minimize smaller than:
{a'^This text is placed very close to the note
c^This text is padded away
Phil Holmes mail at philholmes.net writes:
Thanks for the report. On my Windows box, the even-much-more-tiny example
below has the same effect:
I tried to reduce today's bugs a little further, and opened issue 3432:
skylined text alongside a staff consumes all memory under Windows
Thomas Morley thomasmorley65 at gmail.com writes:
2013/6/25 Eluze eluzew at gmail.com:
but lilypond raises a programming error: cyclic dependency:
calculation-in-progress encountered for #'control-points (Slur).
This might be related to Issue 2589.
sorry - I can't reproduce this! (I'm
Jean-Charles Malahieude lilyfan at orange.fr writes:
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
I think I've narrowed the problem to a particular score which, when
alone, compile fine.
LilyPond asks for more memory than your computer has.
David Kastrup dak at gnu.org writes:
Thomas Morley thomasmorley65 at gmail.com writes:
As a work-around you could add:
\override Staff.Clef #'Y-extent = #'(0 . 0)
I am actually rather appalled that there seems to be no easier way to
keep instrumentName from getting centered with
Keith OHara k-ohara5a5a at oco.net writes:
The bug report remains, though, that someone expected a (generalized)
InstrumentName to be aligned on its baseline, whereas it is centered.
The primary use of InstrumentName is to print the instrument name, and
we would rather have the text
Phil Holmes email at philholmes.net writes:
Compare
http://lilypond.org/doc/v2.17/Documentation/learning/outside_002dstaff-
objects#grob-sizing
I added issue 3407 with an explanation of the change that caused the
difference in this example.
___
Timothy Lanfear lanfear at costamagna.demon.co.uk writes:
f'8 \change Staff=R f'( \change Staff=L f'_. f')
Thanks. I added issue 3363. A similar bug was recently fixed,
but that fix does not solve this case.
Workaround: \override Script #'avoid-slur = #'around
On Sat, 04 May 2013 22:14:52 -0700, Jay Anderson horndud...@gmail.com wrote:
I figured out where this was coming from. I was using something like
\score { label #'a } { ... music ...}
Quite likely your original example will go back to fitting on one page with
version 2.17.18.
The fix to
On Sat, 04 May 2013 22:14:52 -0700, Jay Anderson horndud...@gmail.com wrote:
On Sat, May 4, 2013 at 7:21 PM, Keith OHara k-ohara5...@oco.net wrote:
I cannot reproduce the full problem. Has anyone seen LilyPond print
'annotate-spacing' output where both the limits for the top staff
On Wed, 01 May 2013 21:34:46 -0700, wrote:
On Wed, 01 May 2013 21:07:52 -0700, Jay Anderson horndud...@gmail.com wrote:
On Wed, May 1, 2013 at 12:15 AM, Keith OHara k-ohara5...@oco.net wrote:
Nothing was intended to change page-breaking between those versions.
However, almost anything
On Wed, 01 May 2013 21:34:46 -0700, wrote:
On Wed, 01 May 2013 21:07:52 -0700, Jay Anderson horndud...@gmail.com wrote:
On Wed, May 1, 2013 at 12:15 AM, Keith OHara k-ohara5...@oco.net wrote:
Nothing was intended to change page-breaking between those versions.
However, almost anything
David Kastrup dak at gnu.org writes:
I think that our current code balks at setting paper sizes like A4
rather than a4. Can someone check with older versions?
At least since 2.12, LilyPond has responded
warning: Unknown paper size: A4
but continued to process the input.
On Wed, 01 May 2013 21:07:52 -0700, Jay Anderson horndud...@gmail.com wrote:
On Wed, May 1, 2013 at 12:15 AM, Keith OHara k-ohara5...@oco.net wrote:
If one of these things puts the page-breaking back to the old way
[...]
then something in my change to give space to tempo marks has caused
On Sun, 21 Apr 2013 01:26:21 -0700, Janek Warchoł janek.lilyp...@gmail.com
wrote:
Indeed, i've arrived at a similar conclusion: we need padding both
inwards and outwards, but they need different values. I think it
would be a reasonable thing to do.
There are two parameters
Another minimal example from
http://code.google.com/p/lilypond/issues/detail?id=2795#c16
\paper { indent = 0\mm
line-width = 41\mm
ragged-right = ##f }
\score { \new Staff { g1_retaliate }
\new Staff { e''4 e''' r2 } \\ e'1 }
Workaround
\override DynamicTextSpanner
Trevor Daniels t.daniels at treda.co.uk writes:
% The tie between the g's is misplaced
c e g b~ c e g
I get a correct ties from this, with 2.16 and 2.17.2.
The tie between the Gs curves up, but is in a good place.
Maybe add directly to whichever of issue 904 or 962 is closer?
This example
Another minimal example from
http://code.google.com/p/lilypond/issues/detail?id=2795#c16
\paper { indent = 0\mm
line-width = 41\mm
ragged-right = ##f }
\score { \new Staff { g1_retaliate }
\new Staff { e''4 e''' r2 } \\ e'1 }
Workaround
\override DynamicTextSpanner
mike at mikesolomon.org mike at mikesolomon.org writes:
This just hit the French list, which is an old bug already talked about
in 2010:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00057.html
It may be worth it to add a report.
The forwarded French email reports random
Jean-Charles Malahieude lilyfan at orange.fr writes:
I've got a problem when combining \include \tag and \quoteDuring :
where should I put the addQuote statement?
Where you have it is fine.
You have tagged segments in sequence, and all the tagged segments go into
\addQuote, creating 5 bars
David Kastrup dak at gnu.org writes:
So the 2010 problem is still around, it is just that the error
tracebacks moved to Mike's code in 2.16 and have now moved on or back.
The report of a Scheme crash ostensibly from version 2.17.16 is here
On Wed, 20 Mar 2013 16:11:38 -0700, Colin Hall colingh...@gmail.com wrote:
On 19 mars 2013, at 06:10, Keith OHara k-ohara5...@oco.net wrote:
I request that the 2.16 behavior be the default, letting people who want the
close spacing apply an override.
I could create a tracker Fix text
David Kastrup dak at gnu.org writes:
I suspect
markup.scm: use stencil extents when stacking; issue 732
though from the patch itself, it appears plausible that this might be a
_desired_ effect of the change as a consequence of the brace metrics.
I can confirm that that patch caused
Starting with 2.17.2 or so, text is placed as closely as the detailed shapes
will allow. There is a regression test ‘text-script-vertical-skylines.ly’
checking for this behavior but I have seen no example where we want text so
closely spaced to other objects.
{\tempo Adagio r4 b'4^sadly r2 }
Federico Bruni fedelogy at gmail.com writes:
I'm a bit confused about the use of minimumFret and restrainOpenString.
Maybe adding a warning in the documentation could be a good idea.
It seems that restrainOpenString = #t causes LilyPond to check if you can
reach a finger to fret zero, within
Colin Hall colinghall at gmail.com writes:
I'm going to post a link to this on the dev forum and see if we can
identify what the bug is, and then I can create a tracker.
I don't see any bug; reasoning is on -devel.
___
bug-lilypond mailing list
Eluze eluzew at gmail.com writes:
ledger lines of full notes touch the stem of the next note (with half notes
a reasonable distance is kept)
I'm not sure this is related to issue 1262
Issue 1262 was fixed (accidentally, as part of some code cleanup) so I marked
1262 fixed and entered this
Ben Rudiak-Gould benrudiak at gmail.com writes:
The 2.16 documentation says that \set Staff.whichBar = |: will create a
start-repeat bar in this staff only.
I suppose desired behavior is to have at least one way to change one bar-line
in one staff, preferably the way it was done in version
On Sat, 24 Nov 2012 16:44:15 -0800, Thomas Morley
thomasmorle...@googlemail.com wrote:
2012/11/25 Keith OHara k-ohara5...@oco.net:
Ben Rudiak-Gould benrudiak at gmail.com writes:
The 2.16 documentation says that \set Staff.whichBar = |: will create a
start-repeat bar in this staff only.
I
Eluze eluzew at gmail.com writes:
now coming back to the original topic where Phil wanted to make a correction
to the distance of the text after the \circle:
he had to do this because overriding the circle-padding also increases the
distance of the following object:
\markup
Werner LEMBERG wl at gnu.org writes:
This time I tried with current git (commit 436824b8):
../flower/include/interval.hh:226:
T Interval_tT::center() const [with T = double]:
Assertion `!is_empty ()' failed.
I'm on a GNU/Linux box, running `autogen.sh' with
Eluze eluzew at gmail.com writes:
with negative values for \hspace
since 2.15.7 this has no effect!
I couldn't find why this change happened or where it is documented.
It changed as part of the fix for this bug
http://code.google.com/p/lilypond/issues/detail?id=732
Does the
On Tue, 20 Nov 2012 22:55:21 -0800, Werner LEMBERG w...@gnu.org wrote:
BTW, here is a full backtrace (of the first 32 frames).
#0 Interval_tdouble::center (this=0xbfff96ec)
at ../flower/include/interval.hh:226
#1 0x082d9cdd in Note_head::get_stem_attachment (fm=0x8602ec8, key=...)
David Kastrup dak at gnu.org writes:
Keith OHara k-ohara5a5a at oco.net writes:
One can reverse the change, but possibly re-introduce issue 732, with :
scm/markup.scm
@@ -72,3 +72,3 @@ Example:
(head (car stencils))
- (xoff (+ space (interval
Eluze eluzew at gmail.com writes:
when I (re-)read the passage about modifying alists in NR (chapter 5.3.6)
I'm getting a bit confused: there is an example how to set all values to
zero and it lists every available parameter and sets it to zero:
\new PianoStaff \with {
\override
Eluze eluzew at gmail.com writes:
maybe the same bug!?
\paper {
system-system-spacing = #'((stretchability . 666))
score-system-spacing = #'((stretchability . 666))
}
\new Staff { f1 \break g1 }
\new Staff { f1 \break g1 }
That's not a bug; that's parody of a horrible user
Eluze eluzew at gmail.com writes:
just discovered a thread on the German LilyPond Forum
(http://www.lilypondforum.de/index.php?topic=1254.0) which can be summarized
as follows: [ ... ]
I think it can be reduced to
\paper { markup-system-spacing #'minimum-distance = 100 }
\score { { g'1
Trevor Daniels t.daniels at treda.co.uk writes:
While browsing the Learning Manual I
noticed the last example in Section 3.4.4
displays a fault. It is intended to show the
use of 'padding to displace TextScript, but
the script is not displaced. The example is
still incorrect in the
Rutger Hofman rutger at cs.vu.nl writes:
The bug is that the is not terminated, it flows until the end or some
other [text].
As a workaround you could place a hidden note at the end of the hairpin
e2. { s4\ s4\ \once\hideNotes e4\!_poco cresc.}
The bug might go away naturally as
Karim Haddad Karim.Haddad at ircam.fr writes:
I hope this was not yet reported.
Apparently in the stable and dev version 2.16, and 2.17 this kind of
line break don't work anymore. It used to in the old stable version (2.14).
I tried as indicated in the documentation these overrides
mike at mikesolomon.org writes:
I stumbled upon behavior in LilyPond that is non-deterministic.
If you mean that the order (in which LilyPond determines the sizes and
locations of things) changes from run-to-run, I do not think that is a
problem.
For purposes of regression testing, `make
eluze eluzew at gmail.com writes:
ArnoldTheresius wrote
old, ugly problem, same behavior since 2.12.3
{ \time 2/2
s2.. d'8 ~ \break
d' g'' s2. \break
}
what's wrong with it, or what are the special conditions? for me it looks
fine with standard settings!
We see the
On Sat, 25 Aug 2012 16:55:48 -0700, Xavier Scheuer x.sche...@gmail.com wrote:
Dear LilyPond developers and users,
This rude spam is now
http://code.google.com/p/lilypond/issues/detail?id=2779thanks=2779
___
bug-lilypond mailing list
Better workaround at http://code.google.com/p/lilypond/issues/detail?id=2746
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Looks like an unpleasant bug. The only workaround I see is the commented
override in the example below.
{ b1
% \once\override Score.BarLine #'space-alist #'clef = #'(minimum-space . 2.5)
\once \override Score.BreakAlignment #'break-align-orders = #(make-vector 3
'( staff-bar clef ))
Mark Brophy mark at brophyworld.com writes:
% This bug is a tiny example because nothing can be removed; the bug
% is a consequence of a dense set of eighth and sixteenth notes placed
% in guitar tablature using tabFullNotation.
Thanks. Tiny enough to unambiguously show the problem is
Jay Anderson horndude77 at gmail.com writes:
This example works in 2.14.2 with dash bars being between the staves.
In 2.15.41 the dashes are missing. Taking out the alignAboveContext
make dashed bars show, but the staff is below x.
I added
On Fri, 01 Jun 2012 14:49:33 -0700, Keith OHara k-ohara5...@oco.net wrote:
Part-combining [...] LilyPond starts two slurs and lets one continue too long.
Thank you, this has been entered as
http://code.google.com/p/lilypond/issues/detail?id=2584
Bug Squad,
Would you take a look at this?
Part-combining has always had warnings and awkwardness when combining parts
slurs, tuplets, crescendos, etc. Version 2.14 would warn about trying to start
two slurs on the first beat, but probably since the fix for issue 1967,
LilyPond starts two
1 - 100 of 224 matches
Mail list logo
