Comment #4 on issue 1393 by pnorcks: HTML docs: @multitable uses too much
space
http://code.google.com/p/lilypond/issues/detail?id=1393
IIUC, texi2html is now part of texinfo and there has not been a stable
release since that integration.
I check the commit list
(http://lists.gnu.org/ar
On Sun, Nov 21, 2010 at 08:46:54PM +0100, Reinhold Kainhofer wrote:
> Am Sonntag, 21. November 2010, um 20:09:12 schrieben Sie:
> > Unfortunately not:
> > http://lilypond.org/doc/v2.13/Documentation/contributor/precompiled-regress
> > ion-tests "Note: The automatic comparison of the regtests checks
Updates:
Labels: Patch
Comment #2 on issue 1253 by percival.music.ca: programming error:
(de)crescendo on items with specified volume.
http://code.google.com/p/lilypond/issues/detail?id=1253
Patch looks ok to me, but let's make sure that we have the Patch label.
Comment #3 on issue 1393 by percival.music.ca: HTML docs: @multitable uses
too much space
http://code.google.com/p/lilypond/issues/detail?id=1393
Does anybody know what the status of texinfo + texi2html integration? I
remember that a few years ago, somebody said that texi2html was going to
Comment #2 on issue 1393 by pnorcks: HTML docs: @multitable uses too much
space
http://code.google.com/p/lilypond/issues/detail?id=1393
Well, texi2html may very well be "fixed" upstream, but last time I tested
CVS texinfo/texi2html, there were breakages (due to non-backward-compatible
cha
On Sun, Nov 21, 2010 at 06:52:38PM +0100, Reinhold Kainhofer wrote:
> Am Sonntag, 21. November 2010, um 13:42:21 schrieb Phil Holmes:
> > I've cast my usual eye over the regtest comparison for 13.40 - the only
> > significant change appears to be with figured-bass-continuation-forbid.log
> > where
Am Sonntag, 21. November 2010, um 13:42:21 schrieb Phil Holmes:
> I've cast my usual eye over the regtest comparison for 13.40 - the only
> significant change appears to be with figured-bass-continuation-forbid.log
> where we've lost the error message. This would appear to be expected, as a
> resu
Comment #1 on issue 1422 by markpolesky: Beam edges over rests should not
be centered
http://code.google.com/p/lilypond/issues/detail?id=1422
% according to Gardner Read (Example 6-38 on p.93) beams are
% supposed to start at the left edge of the rest and stop at
% the right edge of the rest,
Comment #2 on issue 1131 by markpolesky: Spacing bug with above lyrics
http://code.google.com/p/lilypond/issues/detail?id=1131
Lyrics above a staff attach to the staff above, not the correct
staff below.
First, a gentle reminder to always include a \version line in the
bug-tracker. Future sy
On Sat, Nov 20, 2010 at 6:48 PM, Reinhold Kainhofer
wrote:
> Actually, according to Gardner Read (Example 6-38 on p.93) the beams are
> supposed to start at the left edge of the rest and stop at the right edge of
> the rest, not in the middle as lilypond (both 2.12 and 2.13) do.
Thanks!
http://co
Status: Accepted
Owner:
Labels: Type-Defect Priority-Low engraving-nitpick
New issue 1422 by v.villenave: Beam edges over rests should not be centered
http://code.google.com/p/lilypond/issues/detail?id=1422
Reported by Reinhold:
% according to Gardner Read (Example 6-38 on p.93)
% beams ar
Comment #2 on issue 1421 by PhilEHolmes: Parenthesis arpeggio wronglt
positioned
http://code.google.com/p/lilypond/issues/detail?id=1421
The way the parenthesis arpeggio responds to \override Arpeggio #'X-extent
is also completely flawed:
\layout { ragged-right = ##t }
\relative c' {
\t
Updates:
Status: Verified
Comment #12 on issue 1382 by PhilEHolmes: Segfault when
setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
(No comment was entered for this change.)
___
bug-lilypond mailing list
b
Updates:
Status: Verified
Comment #5 on issue 1385 by PhilEHolmes: Line indents confuse vertical
spacing
http://code.google.com/p/lilypond/issues/detail?id=1385
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-li
Comment #1 on issue 1253 by markpolesky: programming error: (de)crescendo
on items with specified volume.
http://code.google.com/p/lilypond/issues/detail?id=1253
programming error: (de)crescendo on items with specified
volume.
Wouldn't it be enough simply to reword the error message? I
pr
Comment #1 on issue 1393 by markpolesky: HTML docs: @multitable uses too
much space
http://code.google.com/p/lilypond/issues/detail?id=1393
pnorcks wrote:
Unfortunately, we can't currently single out a
@multitable, since texi2html doesn't add any class
attribute to this type of table...
Is
"Valentin Villenave" wrote in message
news:aanlktimjvrizkapoiva__+2phquq4hid4fngp2og6...@mail.gmail.com...
On Sun, Nov 21, 2010 at 1:42 PM, Phil Holmes wrote:
> _However_. Shouldn't the regtest comparison for
> figured-bass-continuation-forbid.ly flag the change as well?
I'm not sure I unde
On Sun, Nov 21, 2010 at 1:42 PM, Phil Holmes wrote:
> _However_. Shouldn't the regtest comparison for
> figured-bass-continuation-forbid.ly flag the change as well?
I'm not sure I understand: do you mean that /disappearing/ errors
should be flagged?
Valentin.
__
I've cast my usual eye over the regtest comparison for 13.40 - the only
significant change appears to be with figured-bass-continuation-forbid.log
where we've lost the error message. This would appear to be expected, as a
result of the fix to the figured bass code resulting from Reinhold's repo
Comment #1 on issue 1421 by PhilEHolmes: Parenthesis arpeggio wronglt
positioned
http://code.google.com/p/lilypond/issues/detail?id=1421
Neil Puttock provided a workaraound:
As a workaround to prevent the collision you can set a tiny amount of
extra-spacing-height:
\override Arpeggio #'extr
Status: Accepted
Owner:
Labels: Type-Collision Priority-Medium
New issue 1421 by PhilEHolmes: Parenthesis arpeggio wronglt positioned
http://code.google.com/p/lilypond/issues/detail?id=1421
Drawing a parenthesis arpeggio in one voice where the notes in another
voice are short causes the a
On 2010-11-21 05:13, Joe Neeman wrote:
On Sat, Nov 20, 2010 at 5:10 AM, Alexander Kobel mailto:n...@a-kobel.de>> wrote:
See the attached example; with the increased
'nonstaff-nonstaff-spacing, the ChordNames run into the staves they
belong to.
No, it wasn't known. And now, it's fixe
Updates:
Status: Fixed
Labels: fixed_2_13_40
Comment #1 on issue 1275 by pnorcks: name+email for lily-git.tcl
http://code.google.com/p/lilypond/issues/detail?id=1275
Fixed with this commit:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=58b1bea7f7007022965b6b9
Updates:
Status: Fixed
Labels: fixed_2_13_40
Comment #4 on issue 1299 by pnorcks: ly/gregorian.ly needs minimum-Y-extent
updated
http://code.google.com/p/lilypond/issues/detail?id=1299
(No comment was entered for this change.)
___
Updates:
Status: Fixed
Labels: fixed_2_13_40
Comment #16 on issue 1298 by pnorcks: minimum-Y-extent might be obsolete?
http://code.google.com/p/lilypond/issues/detail?id=1298
(No comment was entered for this change.)
___
bug-lilypond
25 matches
Mail list logo
