On Sunday 18 December 2005 18.37, Sven Axelsson wrote:
Volta brackets don't break correctly anymore. They are terminated at
the end of the system and restarted at the next system instead of kept
open. I've already reported this bug some versions ago. Any chance of
having it fixed soon? It is a
On Friday 16 December 2005 15.45, liang seng wrote:
Hi, it seems that the tie problem is still not solved in version 2.7.18
(Windows 98 version).
As Han-Wen said, the problem should be fixed in v2.7.19 and later.
BTW, if the bugs in the unstable 2.7.x series disturb you, it might be a good
On Sunday 11 December 2005 03.39, Cameron Horsburgh wrote:
I don't know if this is the same bug or not, but the behaviour seems
sufficiently different to warrant a 'me too.'
Yes, already known (reported a day ago or so.) Thanks anyways, I marked the
bug popular.
--
Erik Sandberg
Maintainer
-staff.ly. Thanks!
%important critical
%Thomas Scharkowski
\version 2.7.22
\header {
texidoc = tenuto collides with staff line. Didn't happen in 2.6
reportedin = 2.7.19
}
\layout{raggedright=##t}
{ a'4_- }
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin
appropriately.
\quote
However, this behaviour doesn't seem to apply for phrasing slurs. It seems
I have to explicitly call \phrasingSlurUp/Down to get the desired
behaviour.
This is now fixed.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond
On Monday 05 December 2005 10.45, Erik Sandberg wrote:
On Monday 05 December 2005 08.42, Frédéric Bron wrote:
Using lilypond 2.6.4 on Windows (not cygwin)
In the following example, the ties at the beginning of the second system
are not typeset correctly. It seems that the problem comes
On Tuesday 06 December 2005 13.00, Han-Wen Nienhuys wrote:
Erik Sandberg wrote:
BTW:
Shouldn't the default setting of average-spacing-wishes be #f? How often
is the #t setting useful?
virtually everywhere else? #f means: take the maximum. This messes up
all subtle spacing tweaks
On Monday 05 December 2005 08.42, Frédéric Bron wrote:
Using lilypond 2.6.4 on Windows (not cygwin)
In the following example, the ties at the beginning of the second system
are not typeset correctly. It seems that the problem comes from the
different key of the first instrument: if you remove
On Wednesday 30 November 2005 12.15, liang seng wrote:
Hi, I've tried all your suggestions and they don't seem to work either.
I've attached a GIF file which is the output of extract.ps generated by
GhostScript 8.15 (I saved the image using Paint).
The raggedright and
\lyricsto do not seem
On Saturday 03 December 2005 11.56, Cameron Horsburgh wrote:
The documentation in 6.6.1 Basic Polyphony states:
quote
The separator causes Voice contexts to be instantiated. They bear the
names 1, 2, etc. In each of these contexts, vertical direction of
slurs, stems, etc., is set
. But since the fa changes its orientation depending on the
stem direction, one of the noteheads have to disappear or be inverted to
conform to the stardard.
Then, which one of the noteheads should be placed upside down?
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http
On Tuesday 29 November 2005 11.00, liang seng wrote:
To Erik Sandberg,
Hi, the lyric extender line problem still exists on version 2.7.19 (see
attached file). The file was generated by a Mac computer since 2.7.19 for
Windows hasn't been released yet. What is going on? Why can't the CVS
}
}
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.7/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
, but it will remain in the database
until it's fixed (currently there are about 100 bugreports there).
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.7
time
after the 2.7.18 release (because this kind of bug is typically _not_
system-dependent, and I haven't tried it with a pure 2.7.18 version).
So, can you please check again when 2.7.19 has been released?
Thanks,
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http
On Friday 25 November 2005 16.48, Alard de Boer wrote:
Hello list,
When using spacer notes to move the start of a descrescendo,
I found the following:
\version 2.7.18
\score {
\new Staff {
%s1*0
c'1 { s2 s2-\ } | c'4-\! r4 r2 |
c'1 { s2 s2-\ } | c'4-\! r4
- #:general-align Y DOWN #:smaller #:smaller
+ #:general-align Y DOWN #:fontsize
+ (if (not (= alt DOUBLE-SHARP))
+ -2 2)
(alteration-text-accidental-markup alt))
#f))
--
Erik
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.7/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
On Wednesday 23 November 2005 16.09, liang seng wrote:
Here, the lyric extender line starts from bar 1 until the beginning of bar
9 and the extender line is meant to be a continous line. However, what
happened was the line only starts near the middle on bar 4 and is
completely missing on bar
at the next line.
reportedin = 2.7.17
}
\layout {raggedright=##t}
\version 2.7.17
\relative c'' {
\repeat volta 2 { a a a a }
\alternative { { a a a a \break a a a a } { a a a a } }
}
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond
\header {
texidoc = Appoggiatura slurs are placed too low in some situations.
reportedin = 2.6.3
}
\layout{raggedright=##t }
\relative { \appoggiatura ais'16 b4 }
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http
On Tuesday 15 November 2005 14.37, Gilles wrote:
Hello.
- Partial bars:
You probably don't want to use \partial in the middle of a piece. In
your example, it tends to destroy the bar numbering. I think it's a
better idea to set Timing.measureLength directly.
One thing that might
On Saturday 12 November 2005 16.33, Gilles wrote:
Hello.
I didn't receive any acknowledgment to the following posts:
Sorry for the delay, and thanks for reminding me.
http://lists.gnu.org/archive/html/bug-lilypond/2005-10/msg00169.html
On Friday 26 August 2005 04.41, Jukka Akkanen wrote:
\version 2.7.7
\layout { raggedright = ##t }
{
\mark \markup {\box X} g'1 \break
\mark \markup {\box X} g'1
}
%%% end %%%
The first rehearsal mark collides with the treble clef with 2.7.7.
There's no collision with 2.7.4, but
On Thursday 18 August 2005 05.08, Graham Percival wrote:
Dynamics do not avoid the flags/beams from a whole note tremolo, but
they
avoid the stem in a half note tremolo.
\version 2.7.5
{ b'1:32\mp \break b'2:32\mp }
This is fixed in CVS.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS
On Thursday 29 September 2005 03.19, Patrick K Welton wrote:
While the Fa notehead seems to be working fine, the
Do notehead still is not right. Notice the D in
the second messure.
Hi,
This will be fixed in 2.7.16. Can you please verify this, when that version is
released?
--
Erik
Staff
\relative c' {
\override TupletBracket
#'bracket-visibility = #'if-no-beam
\times 2/3 {d4 d d}
\times 2/3 {d8 d d}
}
}
Thanks, this is fixed now (will work in 2.7.16).
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin
On Sunday 06 November 2005 02.36, Graham Percival wrote:
The below code works correctly, but if I uncomment the \score, the
tagline and copyright no longer gets defined.
I think this is intentional: \header, \paper and \layout at global level
change the default settings, so they only affect
On Friday 04 November 2005 15.02, Jeff Grady wrote:
Hi, sorry for the late response. Here you go. The string tunings are
screwed up (and thus the tablature), I know. Let me know if you need any
more info for debugging:
I don't think this is a bug, it's just a missing feature: It seems that
On Saturday 05 November 2005 00.27, Han-Wen Nienhuys wrote:
Markian Hlynka wrote:
Hi, I'm going to repeat part of what I posted to lilypond-user because
I described it better there:
I'm inputting cyrillic text. I've noticed that if cyrillic and latin
text coincide in the same block,
Hi There! пісна } }
\new Lyrics \lyricmode { \markup { Українська Hi There! пісна } }
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6/
___
bug
On Sunday 16 October 2005 00.58, David Bobroff wrote:
In current (or very recent) CVS the following code produces odd results.
The first slur has its right end point essentially centered in the 'c'
space while the second slur has its right end point on the 'f' line.
This seems to be because
On Wednesday 26 October 2005 19.57, Raphael Manfredi wrote:
Here's a little script demonstrating the problem. Proper dynamics
printing should probably be added to the regression tests.
Thanks, added this to bug cvs, as c-script-stem.ly. You can work around it by
moving the \mp indication to
the report a bit.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
On Wednesday 26 October 2005 20.06, Raphael Manfredi wrote:
The following exerpt demonstrates that Ped and * are not properly
aligned on a same horizontal line, making te indications confusing
and hard to read.
As a workaround, perhaps you can use a text spanner, this should align each
pair
-triplet-number.ly in bug CVS.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org
}
\version 2.7.12
{ \set suggestAccidentals = ##t
\stemUp
a'8[ d''!] }
\layout{raggedright = ##t}
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6
running Lilypond 2.6.1 on MacOS 10.4.2
Should this work and I'm doing something wrong, or is this a real bug? If
so, is it easy to fix?
Hi,
Can you please send a complete (but minimal) input .ly file which reproduces
this?
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http
PianoStaff.instrument=down
\set PianoStaff.instr=d
R1\break R1 \break c'1}
\layout { \context { \RemoveEmptyStaffContext } raggedright=##t }
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6
\markup {\box X} g'1 \break
\mark \markup {\box X} g'1
}
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6/
___
bug-lilypond mailing list
bug
On Sunday 21 August 2005 04.51, Hans Forbrich wrote:
As shown in User manual, section 6.3.7 System start delimiters, the
GrandStaff context example description indicates the system should start
with a brace but the brace is missing.
Hi,
c-tie-tie.ly in bug CVS has a new bug: The uppermost tie is too short.
\layout {raggedright = ##t}
\relative c' {
f e a,8~f e a,
}
% EOF
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http
On Monday 10 October 2005 18.17, Han-Wen Nienhuys wrote:
Wiz Aus wrote:
Even if it did use pre-compiled scheme, because lilypond supports
compiling scores that contain Scheme code, it would still require
effectively interpretive processing, which is not doubt a large reason
for it's
On Tuesday 11 October 2005 18.48, Nicolas Sceaux wrote:
Erik Sandberg [EMAIL PROTECTED] writes:
To me, those property lists look like major bottlenecks (though I
haven't done any real profiling). Especially the grob property alists:
While I was debugging some time ago, I saw that
Grob
On Wednesday 05 October 2005 08.10, Wiz Aus wrote:
Managed to get all the lilypond code to at least *compile* now, although a
long way off linking and running!
All this does is ensure that member functions aren't stored directly as
standalone function pointers - it creates a thunk or proxy
On Wednesday 05 October 2005 23.55, Wiz Aus wrote:
From: Erik Sandberg [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: bug-lilypond@gnu.org
CC: Mats Bengtsson [EMAIL PROTECTED], Wiz Aus
[EMAIL PROTECTED]
Subject: Re: Spacing bug
Date: Wed, 5 Oct 2005 21:46:33 +0200
On Wednesday 05
Hi,
On Friday 30 September 2005 22.25, Werner LEMBERG wrote:
%
% [EMAIL PROTECTED]
\version 2.7.11
\header { texidoc =
It seems that contexts within contexts confuse LilyPond's lyrics engine.
Starting with the second syllable in the second context, lyrics are no
longer centered below
On Thursday 29 September 2005 03.19, Patrick K Welton wrote:
While the Fa notehead seems to be working fine, the
Do notehead still is not right. Notice the D in
the second messure.
Which lilypond version are you using?
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http
On Tuesday 27 September 2005 03.57, Kevin Nowaczyk wrote:
If I have a musical phrase that is slurred and add a
grace note, the grace note ends the slurring and
produces a warning. I saw a discussion on the
lilypond-user list from 2002 about nested slurs, and
the conclusion seemed to be that
lines seem to build one line with 16th and
make the score nearly unreadable - any suggestions or workarounds?
Did you try to print out the score on paper? PDF/PS viewers often make
rounding errors that make scores look bad on a computer screen.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS
On Tuesday 27 September 2005 23.21, Fairchild wrote:
Got it!
Still think it is a bug.
Here's the workaround.
Though your solution happens to work, it's an unsupported tweak. Don't expect
it to work with future versions of lily.
I did a quick test, and the following seems to be the right
you don't want \bar ||: ? The |. bar should normally only
exist at the end of a piece, in that case you may want to have the next line
in its own \score block.
(unfortunately, there is no |.|: barline), so if you really need it, you'll
probably need some deeper trickery.
--
Erik Sandberg
On Monday 26 September 2005 02.24, Fairchild wrote:
Eric -
Look at the second snippet, showing that the end of the first line is the
end of the piece.
Ah, ok.
I'll work on deep tricks.
Looks like scm/output-lib.scm is a good place to start at. I think you'll need
to do something like
Hi,
I think this problem was reported earlier, but it hasn't been solved. It's
pretty critical IMHO.
There is a problem with lilypond-book: When quote is used in a lilypond block,
the inserted \end{quote} is placed too early.
This happens in 2.7.10.
Example: The following .lytex file ...
Hi,
this syntax error produces a segfault:
\version 2.7.10
\book{ foo = c4 }
--
Erik
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Tuesday 20 September 2005 13.38, Trent Johnston wrote:
Hi All,
A quick update on viewing postscript files in windows... especially
gsview...
Thanks to the response by Peter Mongensen I was able to view the postscript
file he created... this was created with
Linux.
Debian Sarge+DeMuDi
On Friday 16 September 2005 20.28, Jean-Charles wrote:
On Mandriva LE2005
Being unsatisfied with the autopackaging of LilyPond (no emacs-mode, no
doc), I tried to build my rpm as usual. Building a 2.4.6 takes about 3
hours with all the fonts stuff), but my spec files did not fit the 2.6.x.
On Thursday 08 September 2005 14.38, Sacha Standen wrote:
Hi
I think this may be a bug:
If you change the alignment of a fret diagram, the top horizontal bar on
the diagram ceases to be bold, as in the 2nd bar below:
Can't reproduce. Do you still see it if you zoom in the .pdf output?
On Thursday 08 September 2005 00.23, Sven Axelsson wrote:
It seems as if I can't get \RemoveEmptyStaffContext to work properly.
In the example below it doesn't do anything at all. The
RemoveEmptyVerticalGroup override does indeed remove the first
empty system, but the other two are still
On Monday 05 September 2005 13.50, Nancho Alvarez wrote:
Hello!
I have seen a problem with ligatures, the horizontal bracket joining
notes denoted with \[ and \].
The problem is that the start and end point of the bracket seems to be
affected by the rythmic figures of other simultaneus
On Monday 05 September 2005 13.57, Nancho Alvarez wrote:
Hello!
I tried to make a VaticanaStaff larger, changing the font and the
StaffSymbol. This works well for regular Staff, but in Vaticana Staff
the stems are not scaled. Look at the virga in the second example,
it has a very small stem
Citerar Han-Wen Nienhuys [EMAIL PROTECTED]:
Graham Percival wrote:
Lilypond 2.7 no longer creates linebreaks to avoid text running off the
page.
\version 2.7.7
{
c1 c c c c c
c1^\markup{really really really long text}
}
Check out the keep-inside-line property. When switched
On Monday 29 August 2005 15.14, ludovic sardain wrote:
Hello,
When I run the following file in Lilypond 2.6.3 on Ubuntu, I get the error
message:
calculating line breaks...
programming error: adding reverse spring, setting to unit
continuing, cross fingers
several times, and in the
On Sunday 28 August 2005 13.37, Sven Axelsson wrote:
Lilypond 2.7.7 Windows
If the first note in the music is a grace note, a stem direction override
will turn the grace note and not affect the normal notes. This is wrong
since the grace notes should only be affected by using
On Friday 26 August 2005 11.13, Darius Blasband wrote:
Hello,
I have a 2.2 score, recently migrated to 2.6.3, where I have something
fairly common, such as:
\grace{a8[ b c d e f]} a4
which looked good, and which is printed as if the input was defined as a
chord a b c d e f a and the
Hi,
I saw that the part-combine-mm-rest-after-solo regression test is broken. This
bug can get a low priority, because I have mysteriously fixed it in my thesis
fork.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs
On Wednesday 24 August 2005 15.40, Jukka Akkanen wrote:
Here, I would expect the triplet bracket to be in the same position
on both lines, however, it is printed lower the second time:
%%% snip %%%
\version 2.7.4
\layout {
indent = 0.0\cm
raggedright = ##t
}
\relative c'' {
This bug is fixed, or at least much improved, in 2.7.6.
Michael, can you please verify that it is the way you expect?
On Saturday 24 April 2004 15.09, Erik Sandberg wrote:
Hi,
I added this to the bug cvs as 'clef-change'.
%
%
\header { texidoc =
The clef change in bar 1 is too far
Hi,
This bug is fixed in 2.7.6.
On Thursday 23 June 2005 19.18, Erik Sandberg wrote:
On Friday 17 June 2005 13.55, Mats Bengtsson wrote:
If you suspect a bug, please send the email to bug-lilypond instead
(which I have now done).
I'm not sure if you have noticed that the bug is visible
On Thursday 18 August 2005 05.08, Graham Percival wrote:
Dynamics do not avoid the flags/beams from a whole note tremolo, but
they
avoid the stem in a half note tremolo.
\version 2.7.5
{ b'1:32\mp \break b'2:32\mp }
Thanks, added as c-tremolo-script.ly:
%
%Graham Percival
\header {
/mailman/listinfo/bug-lilypond
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
On Tuesday 16 August 2005 11.54, Hans Aberg wrote:
On 16 Aug 2005, at 10:03, Mats Bengtsson wrote:
I figure so. But I do not know the worth of the effort of
pursuing it. One can perhaps draw a parallel to the TeX macro
package LaTeX, which in its original form was too rigid for
general
demonstrating it?
thanks,
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/bugs/v2.6/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org
On Tuesday 16 August 2005 22.54, Hans Aberg wrote:
But TeX was developed once, too. Its author got tired, putting the
lid on further development, having the copyright. It could happen
with LilyPond, too, if one arrives the point where one has the
reached limits of the current setup.
This is
On Monday 15 August 2005 17.30, Yuval Harel wrote:
On Sun, 14 Aug 2005 23:53:12 +0200, Erik Sandberg
[EMAIL PROTECTED] wrote:
You're right. I don't have working sound right now, so I relied on
midi2ly
which didn't output the dis.
In any case, the above example is also problematic
!
%
%Hans Aberg
\version 2.6.0
\header {
texidoc = Tempo markings collide with scripts.
reportedin = 2.6.0
}
\new Staff { \tempo 4=100 c'4^blablabla }
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org
On Sunday 14 August 2005 19.18, Yuval Harel wrote:
On Sat, 13 Aug 2005 16:04:16 +0200, Erik Sandberg
[EMAIL PROTECTED] wrote:
On Saturday 13 August 2005 12.58, Yuval Harel wrote:
On Fri, 12 Aug 2005 18:53:13 +0200, Erik Sandberg
Actually, this example works fine for me (on version
On Saturday 13 August 2005 12.58, Yuval Harel wrote:
On Fri, 12 Aug 2005 18:53:13 +0200, Erik Sandberg
Actually, this example works fine for me (on version 2.6.3 on Windows) -
the MIDI output plays
both notes. In any case, it seems like a different bug: the bug I reported
concerns two notes
On Saturday 13 August 2005 15.59, Nicolas Sceaux wrote:
Hi,
I'm not sure if that's a bug or if I'm just doing something badly. In
the following snippet, the lyrics are not placed below the newly added
staff.
\new Lyrics creates a new lyrics context, independently of the Staff context
(it
by midi output.
I added this to bug CVS:
%
%Yuval Harel
\header {
texidoc = If notes from two polyphonic voices inside one staff overlap, the
second one isn't output to midi.
reportedin = 2.4.0
}
\version 2.6.3
\new Staff \new Voice c \new Voice dis
--
Erik Sandberg
Maintainer
Will, Peter:
I think this bug is fixed now. Can you please verify this with 2.6.3 or 2.7.4?
Thanks,
Erik
On Wednesday 10 August 2005 00.41, Erik Sandberg wrote:
On Tuesday 14 June 2005 13.02, Peter wrote:
Hello
There seems to be a problem with the `fa' triangular shaped note head
}
\version 2.6.1
{
\set Score.currentBarNumber = #33
c'4
}
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/doc/v2.5/bugs/out/index.html
___
bug-lilypond
On Tuesday 09 August 2005 05.07, Graham Percival wrote:
On 8-Aug-05, at 1:41 AM, Klaus Rettinghaus wrote:
Now let's talk business: I noticed a little bug, if I may name it this
way.
If you got two voices in one staff and the upper has a dotted note
between two lines, while the lower is
'{
\set shapeNoteStyles = ##(fa fa fa fa fa fa fa)
f1 f2 f4 f e'1 e2 e4 e
}
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/doc/v2.5/bugs/out/index.html
note is beamed together with the
visible note, and that the beam is invisible. You probably want to add
\noBeam to the invisible notes.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/doc/v2.5/bugs
-volta.ly in CVS. I marked it popular.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/doc/v2.5/bugs/out/index.html
___
bug-lilypond mailing list
bug
On Tuesday 02 August 2005 14.10, Jan Nieuwenhuizen wrote:
Han-Wen Nienhuys writes:
(although I'm surprised that Ubuntu doesn't ship the latest GS).
Ubuntu is a snapshot of debian/unstable with extra user-experience
polish. Only since July 15th, 8.15 is in debian (fixing a whishlist
bug
On Thursday 28 July 2005 08.37, Jan Nieuwenhuizen wrote:
Guy Banay writes:
The Lilypond autopackage (version 2.6.1) will not install on systems
without Ghostscript = 8.15 despite GS being an optional runtime
dependancy and lilypond can run without it.
What does `will not install' mean?
On Wednesday 27 July 2005 11.07, John Mandereau wrote:
Hi,
Although LilyPond is generally very good at spacing, I've found
that 1/32 notes at the end of a measure are often displayed much too
close from the bar, especially if they are down-stemed.
I've had a look at some traditionally
On Wednesday 27 July 2005 17.13, Trevor Baca wrote:
Looking at the final barline in this 2.7.0 snippet ...
See the section on bar lines in the manual. You need to use
\set Staff.whichBar = |.
BTW, you might want to use ChoirStaff iso. StaffGroup, this way there will
never be a barline drawn
On Thursday 28 July 2005 11.38, Jan Nieuwenhuizen wrote:
Erik Sandberg writes:
I have the same problem (I reported it earlier), with the full package. I
get the following message when installing:
# Checking for Ghostscript ... failed
# FAILED:
# Package 'Ghostscript' was found
Hi,
While attempting to install the new autopackages as non-root on several systems
(Ubuntu 5.04, Mandrake 10.0), I got the following error:
# Checking for Ghostscript ... failed
# FAILED:
# Package 'Ghostscript' was found but was of the wrong version and the correct
version could not be
On Wednesday 20 July 2005 23.26, Roland wrote:
On Mon, 18 Jul 2005 11:30:45 +0200, Erik Sandberg
[EMAIL PROTECTED] wrote:
This is because Lilypond looks for the context where graceSettings was
set; since MIDI doesn't use graceSettings, no context is found.
A workaround is to add
\set
-property 'Voice 'Slur 'direction 1)
#(add-grace-property 'Voice 'Stem 'direction -1)
\relative c'' {a b c d e}
\\
\relative c'{a b c d e}
\midi {
}
\layout {
}
}
--
Erik Sandberg
=
\relative a'{
\voiceTwo
d,4 e \\ d f g
}
\score{
\context Staff = notes
\clef treble
\context Voice = one \upperOne
\context Voice = two \upperTwo
}
--
Erik Sandberg
Maintainer
On Monday 18 July 2005 21.12, Georges Roux wrote:
Erik Sandberg a écrit :
I can't reproduce this (the a is not overwritten by any beam if I compile
your example). If it really does, it's a bug which we would like to know
more about. Can you please send a complete example in which
c''{c1 c2 c4 c8 c16 c c4 c c c}}
\layout {
raggedright = ##t
\context {
\Staff
whichBar = #|
}}
%
- Bruce
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs
Hi,
lilypond --preview regression/balloon.ly creates a too small eps file. The
text snippets end up outside the image.
Erik
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Saturday 09 July 2005 21.48, Sebastiano Vigna wrote:
I don't want to seem iterative, but my source for K460
(http://vigna.dsi.unimi.it/music/K460.ly) does not compile still with
2.6.0. Problems start with the appoggiatura at measure 28.
I would like just to know if the answer is won't fix,
the tremolo repeat notation is used, the stem length is
sometimes too short.
reportedin = 2.6.0
}
{\repeat tremolo 8 b'32 b'4:32}
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
http://lilypond.org/doc/v2.5/bugs/out
101 - 200 of 622 matches
Mail list logo
