2007/8/14, Graham Percival <[EMAIL PROTECTED]>:
> Thanks,
> http://code.google.com/p/lilypond/issues/detail?id=409
Thank you for adding it.
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Thanks,
http://code.google.com/p/lilypond/issues/detail?id=409
Cheers,
- Graham
Valentin Villenave wrote:
Hello everybody,
I assume this is a known bug, but I wasn't able to find it in the
archives nor on google tracker.
I've always seen such collisions occur, since my very first lilypond
ins
Thanks, this has been entered as
http://code.google.com/p/lilypond/issues/detail?id=408
Cheers,
- Graham
Peter Budny wrote:
When a word at the end of a line would run off the page, it is normally shifted
left to avoid this. However, when that word also is extended with a melisma,
Lilypond fol
Thanks, I've added this to the 2.11 docs.
Cheers,
- Graham
Zack Charter wrote:
There is a LilyPond bundle for the OS X editor TextMate. I thought you might
like to add it to the supported editors page.
(http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Editor-
support#Editor-support
I'm happy to report that issues 1 and 3 have been fixed in 2.11.29 (and
quite possible 2.10.29, although I'm not certain). As Joe mentioned,
the second problem is currently issue 143.
Once I've finished processing the current bugs, I'm going to check the
old bugs in the tracker and bring unan
Sorry, I use .29 (osx-intel), and the bug is still there. I just
double-checked.
Cheers,
- Graham
Han-Wen Nienhuys wrote:
should be fixed in 29
2007/8/14, Graham Percival <[EMAIL PROTECTED]>:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=406
Cheers,
- Graham
_
2007/8/14, Graham Percival <[EMAIL PROTECTED]>:
> If you're really, really, really bored, go ahead and browse the -bug
> list for old bugs, test them, then send them in again. It took me about
> three months to add all the old bugs that I had listed (after testing
> them and producing minimal exa
should be fixed in 29
2007/8/14, Graham Percival <[EMAIL PROTECTED]>:
> Thanks, added as
> http://code.google.com/p/lilypond/issues/detail?id=406
>
> Cheers,
> - Graham
>
>
> Rune Zedeler wrote:
> > When using a feathered kneed beam, the stems on the "upside down" part
> > of the beam are too long
Graham Percival wrote:
Hi Philippe,
Yes, please send a complete example -- complete, yet still small. We
have some guidelines here:
http://lilypond.org/web/devel/participating/bugs
(you may also want to check that this bug has not already been reported)
Also, don't forget to tell what Lil
Han-Wen Nienhuys wrote:
2007/7/19, Rune Zedeler <[EMAIL PROTECTED]>:
Manual says "thirds are added to the root until it reaches the specified
number" which would be the correct thing to do.
But when specifying :13, the 11 is left out, so that the chord name
printed is "9/add13" instead of "13"
Issue 407: tabStaff cannot handle \partcombine
http://code.google.com/p/lilypond/issues/detail?id=407
New issue report by gpermus:
An empty tabstaff is created, and a new normal staff is created under the
tabstaff. The notes are placed on the normal staff, not the tabstaff.
\version "2.10.1"
me
Hi Philippe,
Yes, please send a complete example -- complete, yet still small. We
have some guidelines here:
http://lilypond.org/web/devel/participating/bugs
(you may also want to check that this bug has not already been reported)
Cheers,
- Graham
Philippe Raynaud wrote:
Hello,
I am typin
Thanks for the report; this has been added as
http://code.google.com/p/lilypond/issues/detail?id=407
Cheers,
- Graham
hernan wrote:
just to convince the clever php guy at http://post.gmane.org/post.php that im
not top posting...
--
Issue 333: lyrics delayed by one note with \partial and \override
VerticalAxisGroup
http://code.google.com/p/lilypond/issues/detail?id=333
Comment #2 by gpermus:
Mats reports that this which was introduced somewhere between version 2.8 and
2.10.
--
You received this message because you are
Issue 406: Feathered beams do not work with knees
http://code.google.com/p/lilypond/issues/detail?id=406
New issue report by gpermus:
When using a feathered kneed beam, the stems on the "upside down" part of
the beam are too long, because they do not know that the beam is feathered
and therefore e
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=406
Cheers,
- Graham
Rune Zedeler wrote:
When using a feathered kneed beam, the stems on the "upside down" part
of the beam are too long, because they do not know that the beam is
feathered and therefore extend all the way to
Thanks, I've added this info to 369.
Cheers,
- Graham
Neil Puttock wrote:
Hello,
I'm getting some strange behaviour with cross-staff beams when they are
combine with a slur which stays on one staff:
\version "2.11.29"
\paper{ ragged-right=##t }
\score {
\new PianoStaff <<
\context St
Issue 369: \change Staff=foo affects beam too early
http://code.google.com/p/lilypond/issues/detail?id=369
Comment #1 by gpermus:
This also affects slurred notes:
\version "2.11.29"
\paper{ ragged-right=##t }
\score {
\new PianoStaff <<
\context Staff = rh \relative { c'8([ d) \change St
Valentin Villenave wrote:
I've just posted another very familiar bug that I can't find on the
tracker. Are we sure that every known bug is listed on the tracker, or
could it be useful to browse the -bug list archives looking for
unresolved bugs?
Every officially acknowledge bug is listed on th
Thanks to both of you; this has been added as
http://code.google.com/p/lilypond/issues/detail?id=405
Cheers,
- Graham
Trevor Bača wrote:
On 8/1/07, Graham Percival <[EMAIL PROTECTED]> wrote:
Thanks for this report.
Trevor, is there any special tuplet property to say "always print a
bracket?"
Issue 405: tupletBracket not printed despite #'bracket-visibility=##t
http://code.google.com/p/lilypond/issues/detail?id=405
New issue report by gpermus:
\version "2.11.29"
% If ragged-right = ##f, the music is spaced more broadly and the bug
% doesn't occur.
\paper {
ragged-right = ##t
Issue 404: request: setting the output filename
http://code.google.com/p/lilypond/issues/detail?id=404
New issue report by gpermus:
This is particularly a problem for me when I have multiple \book-s in a
single .ly file -- the default file naming (file-1.pdf, file-2.pdf) is not
very helpful. I wou
Thanks.
I've added your first example to the bug report. In 2.11.29, I don't
see any dashes at all in the second example, so haven't added it as a
separate issue. Clearly this code is broken; let's wait until somebody
takes a look at it. If this second issue reappears, please report it agai
Issue 401: misplaced textSpanner when Bar_engraver is removed
http://code.google.com/p/lilypond/issues/detail?id=401
Comment #1 by gpermus:
Shorter example:
\version "2.11.29"
%{ when the Bar_engraver is removed and textSpanner text happens to span
over a line break the text on the first line
Thanks, this is a known issue, but it only affects the GUI, not the
actual processing part. I've collected some links here
http://code.google.com/p/lilypond/issues/detail?id=402
The creation date issue is interesting; I've added it to the tracker:
http://code.google.com/p/lilypond/issues/detai
Issue 403: osx builds report creation date of March 23, 2006
http://code.google.com/p/lilypond/issues/detail?id=403
New issue report by gpermus:
Lilypond.app -> Get Info.
Not at all important, but listed here for completeness.
Issue attributes:
Status: Accepted
Owner: gpermus
Issue 402: osx intel app lists itself as "ppc"
http://code.google.com/p/lilypond/issues/detail?id=402
New issue report by gpermus:
The graphical frontend is a PPC binary, but the part of lilypond that does
all the processing is a native intel binary. See
http://lists.gnu.org/archive/html/lilypon
27 matches
Mail list logo
