Added.
On Monday 09 August 2004 05.15, Werner LEMBERG wrote:
> % slur-accidental.ly
> %
> % [EMAIL PROTECTED]
> %
>
> \version "2.3.11"
>
> \header { texidoc = "
> Slurs and accidentals shouldn't collide.
>
> The example also shows another buglet: The stem length of the third 16th
> note is too sho
On Saturday 14 August 2004 01.08, Werner LEMBERG wrote:
> > Where should the slur end?
> >
> > Added the bug as slur-fermata.ly.
>
> If both the slur and the fermata are above the note, the order (from
> bottom to top) is note -> slur -> fermata.
>
> This is probably not so easy to catch, since, sa
On Tuesday 03 August 2004 00.24, Stefaan wrote:
> Well at least I think it is a bug:
>
> Variable names apparently can no longer contain digits in 2.3.x
> Convert-ly does not warn or change anything about offending definitions.
>
> I have tried with the 2.3.6 package (i.e. the most recent one that
Added.
On Wednesday 28 July 2004 03.40, Werner LEMBERG wrote:
> Here a problem with bar numbers.
>
>
> Werner
>
>
> ==
>
>
> %
> % bar-number-collision.ly
> %
> % [EMAIL PROTECTED]
> %
>
> \version "2.2.5"
>
> \header { texido
On Saturday 14 August 2004 01.04, Werner LEMBERG wrote:
> > > Ottava spanners should end after the dot of a dotted note.
> >
> > Already reported as octaviation-dot.
>
> Oops, sorry, missed that.
Nothing to be sorry about. The database is not designed to be easily readable
by others than me & tho
Added as slur-text.ly.
%
%
\header {
texidoc = "Slurs collide with text."
}
\version "2.3.11"
\notes{
\clef alto
\time 3/4
a'4^"blablabla"( cis'')
}
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypo
Sorry, I don't understand. The output with lilypond 2.2.5 looks normal to me,
please specify what the unexpected behaviour is.
Erik
On Sunday 15 August 2004 12.09, Christopher Ellis wrote:
> Is this a bug? Sorry is this is a repeat.
>
> \version "2.2.0"
> #(ly:set-point-and-click 'line-column)
Added this to 2.2.5 bug branch.
%important
[EMAIL PROTECTED]
\version "2.2.5"
\header {
texinfo = "Metronome markings are not displayed."
}
\score {
\new Staff \notes \relative c' {
\tempo 2=92 f8[ f r f]
}
\paper {
raggedright = ##t
}
}
_
Seems to be fixed in CVS.
On Sunday 08 August 2004 13.39, Werner LEMBERG wrote:
> % critical
> %
> % [EMAIL PROTECTED]
> %
>
> \version "2.3.11"
>
> \header { texidoc = "
> Calling `set-global-staff-size' breaks `lilypond --format=tex ...'.
> " }
>
> #(set-global-staff-size 13)
>
> \score {
> c'
Seems to be fixed in CVS.
Erik
On Sunday 01 August 2004 05.02, Graham Percival wrote:
> In this test file, the slurs appear over the bowing marks. This is
> particularily odd, since in a piece of mine, the downbow slurs are
> wrong, but I have an upbow slur that works.
>
> In any case, with fink
Thanks, bug report added to CVS as ambitus-accent.
Erik
On Thursday 05 August 2004 21.25, Christian Hitz wrote:
> \version "2.3.11"
>
> %
> % The scripts on the first note are placed in respect to the ambitus
> symbol.
> % Only happens if the Ambitus_engraver is in the Voice context.
> %
> \book{
I added this to the bug cvs:
%crash critical
[EMAIL PROTECTED]
\version "2.3.11"
\header {
texidoc = "skip appoggiaturas make lily segfault (using debian/sarge)."
}
\notes { \appoggiatura s8 s1 }
On Tuesday 17 August 2004 03.39, Will Oram wrote:
> This reproduces the problem exactly in 2.3.11
On Tuesday 17 August 2004 08.40, Jan Nieuwenhuizen wrote:
> Erik Sandberg writes:
> > Seems to be fixed in CVS.
>
> You may want to hold-on to this one a bit more, we're going to
> implement a better fix.
Ok, added this as slur-bow.ly:
%fixed
[EMAIL PROTECTED]
\header {
Added this to cvs:
%critical
%
\header {texidoc = "Variable names can not be set to pitch names" }
\version "2.3.11"
a = {c c c c}
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Added as fermata-rest-position:
%
% [EMAIL PROTECTED]
\version "2.3.11"
\header { texidoc = "
Fermatas over multimeasure rests are positioned too high.
" }
\score {
\relative c' {
r1^\fermata \setMmRestFermata R1
}
\paper {
indent = 0.0\mm
linewidth = 70.0\mm
}
}
___
Added this as dynamic-accidental:
%
[EMAIL PROTECTED]
\header {texidoc = "the \mp is touching the sharp sign of cis"}
\score { \relative c{
\clef alto
cis4.\mp
}}
On Saturday 31 July 2004 23.28, Graham Percival wrote:
> I know that we need to do a fair amount of tweaking of #'padding to
> make
On Tuesday 17 August 2004 19.29, Bertalan Fodor wrote:
> Sorry, I just can't remember the syntax of cvs to make diffs.
try cvs diff -u
Erik
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Tuesday 17 August 2004 20.57, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Added this to cvs:
> >
> > %critical
> > %
> >
> > \header {texidoc = "Variable names can not be set to pitch names" }
> > \version "2.3.11"
> >
> > a = {c c c c}
>
> not a bug; won't fix.
ok, removed from cvs
Thanks, added as spacing-whole-rest.
(i renamed it, according some quasi notation that the initial word should
describe the main area the bug is within)
Erik
On Wednesday 18 August 2004 11.11, Werner LEMBERG wrote:
> %
> % [EMAIL PROTECTED]
>
> \version "2.3.11"
>
> \header { texidoc = "
> Whol
Lily's support for fingerings in polyphony seems to be very limited.. there
seem to be much more severe examples of this. I'll write a report soon.
(now i'll reboot my computer to WINDOWS.. I am in the middle of a terrible
nightmare related to a scanner that doesn't support linux. I am going thr
On Wednesday 18 August 2004 22.24, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > %
> > % encoding.ly
> > %
> > % critical
> > %
> > % [EMAIL PROTECTED]
> > %
> >
> > \version "2.3.11"
> > \encoding "latin1"
> >
> > \header { texidoc = "
> > The `\encoding' command doesn't set the proper e
Added this to repository.
%important
[EMAIL PROTECTED]
\header { texidoc =
"PianoStaff.instrument is not shown when the first staff starts with a grace
note"
}
\version "2.2.5"
\score { <<
\new Staff \notes {
\set Staff.instrument = "Guitar"
\grace g8 a1
}
\new PianoStaff
I added this to cvs.
%
%
\header {texidoc = "
Noteheads from voices 2, 3 and 4 collide.
"}
\version "2.3.11"
<< a''2 \\ g''2 \\ f''2 \\ e''2>>
===
begin 644 notehead-collision.png
MB5!.1PT*&@[EMAIL PROTECTED]&H```!2"`(S:M8'3TE$051XG.V;
M06C37AS'[EMAIL PROT
Added this to CVS.
%
%
\header {
texidoc = "The extender line after the dim. text in \\setTextDim
should not be shown if it becomes too short, as in the first measure."
}
\version "2.3.11"
\score { \relative c''{
\setTextDim
c4.\> c8\! c4 c
\setTextDim
c4\> c c c\!
}
\paper { raggedright = ##t
Thanks, added to bug cvs:
%important
[EMAIL PROTECTED]
\version "2.3.11"
\header {texidoc = "
The definition of \finger markup is bad. The numbers are too small and
I'm not sure if they are typeset with the correct number family.
"}
\bookpaper {
linewidth = 160 \mm - 2.0 * 9.0 \mm
indent
On Friday 20 August 2004 18.47, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Added this to repository.
>
> this is -strictly speaking- not a bug, but a new disguise of the grace
> problem. insert \grace s8 before in both PianoStaves, and it should
> work.
Ah, ok. I'll keep the bug repor
On Saturday 21 August 2004 08.45, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > On Friday 20 August 2004 18.47, Han-Wen Nienhuys wrote:
> > > [EMAIL PROTECTED] writes:
> > > > Added this to repository.
> > >
> > > this is -strictly speaking- not a bug, but a new disguise of the grace
> >
It's a lot better now. However, the digits are still placed a bit too low
compared to ^1, ^2 etc.
Here's an updated report:
%important
[EMAIL PROTECTED]
\version "2.3.11"
\header {texidoc = "
The definition of \finger markup is bad. The number is placed slightly too
low.
"}
\bookpaper {
l
Hi,
using 2.3.12, the command
lilypond -
tries to create -.ps and -.pdf, which she doesn't do correctly. Adding quotes
around command arguments somewhere would probably solve the problem.
Erik
/tmp$ echo {c4} |lilypond -
Now processing `-'
Parsing...
Interpreting music... [1]
Preprocessing gra
Also, the use of quotes in Lilypond output is inconsistent: "foo.pdf" vs.
`foo.ps' and `foo.ly'.
On Sunday 22 August 2004 17.45, Erik Sandberg wrote:
> Hi,
>
> using 2.3.12, the command
> lilypond -
> tries to create -.ps and -.pdf, which she doesn't do c
On Monday 23 August 2004 01.33, Bernard Hurley wrote:
> Hi,
>
> I have a Debian Linux system. I upgraded to version 2.2.5 (Using
> 2.2.5-1.pk.deb from Pedro Kroeger's website). I immediately found that
> metromone marks were not being rendered. Even in something as simple as:
>
On Friday 20 August 2004 11.36, Bertalan Fodor wrote:
> The definition of \finger markup is bad. The numbers are too small and
> I'm not sure if they are typeset with the number family.
The bug is fixed in 2.3.12.
Erik
___
bug-lilypond mailing list
[E
\header {texidoc = "slurs are placed above up- and downbow sometimes."}
\score { \relative c''{
\clef alto
\slurUp
c4(^\downbow b) r2
c4^\downbow( b) r2
c4(^\upbow b) r2
c4^\upbow( b) r2
}}
___
bug-lilypond mailing list
[EMAIL PROTECTED
Bug status:
- The following bugs have been fixed & are now moved to fixed/:
appoggiatura-segfault.ly
broken-small-slur.ly
encoding-ss.ly
fermata-rest-position.ly
markup-fingering.ly
setTextDim.ly
volta-repeat-grace.ly
- surviving-staff has been moved to the 'future' branch.
Erik
___
On Friday 27 August 2004 23.06, [EMAIL PROTECTED] wrote:
> In the example located here:
> http://www.lilypond.org/doc/v2.3/Documentation/user/out-www/lilypond/Repea
>t-syntax.html
>
> for repeats with a partial bar and alternative endings there is the
> following example:
>
> \context Staff
I can't reproduce it (using 2.2.5 on Debian/testing). Can you send the
complete output of lilypond --verbose ?
Also, is it possible for you to see if the problem is still there in 2.2.6 or
2.3.x as well?
Erik
On Saturday 28 August 2004 18.14, Sean Reed wrote:
> dear lilypond bug control,
>
> b
On Sunday 29 August 2004 20.53, Robinson P. Tryon 03 wrote:
> hi,
>
> I'm using lilypond 2.2.5 on a debian box, and although I've stumbled
> through the basics of lilypond, I have a few problems:
>
> -
>
> I am unable to put page breaks exactly where I want them.
>
> I'm trying to replicate a p
On Thursday 02 September 2004 13.04, Russ Ross wrote:
> This looks like a bug to me:
>
> \version "2.2.2"
> \score {
> \notes \relative c'' { \autoBeamOn c8 b \autoBeamOff a c r2 }
> \paper { raggedright = ##t }
> }
Added this to bug CVS, to both 2.2 and 2.3 branches:
%
[EMAIL PROTECTED]
\hea
Hi,
I have moved most of the content of the bugreport slur-bugs into other reports
& then I renamed the report to slur-triplet-number (since that's the only bug
left)
Erik
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman
On Wednesday 01 September 2004 03.05, Julian wrote:
> When the following file is compiled with the CVS version of lilypond
> the dynamic and the slur join up in the first bar and the markup
> is totally obliterated by the notes in the fifth bar.
>
> crescPocoAPoco = \markup{ \bold\italic {cresc p
I added this to the bug repository (both 2.2 and 2.3 branches)
%
%
\header {
reportedin="2.2.5"
texidoc = "Tuplet bracket of grace note tuplets extends to the main note."
}
\version "2.3.12"
{ \grace \times 2/3 {b16[ b b]} b8}
___
bug-lilypond mailing
On Saturday 04 September 2004 23.02, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > I added this to the bug repository (both 2.2 and 2.3 branches)
> >
> > %
> > %
> > \header {
> > reportedin="2.2.5"
> > texidoc = "Tuplet bracket of grace note tuplets extends to the main
> > note." }
> > \
Added this to bug repository as partcombine-rest.
%
[EMAIL PROTECTED]
\header {
texidoc = "the measures in which there should be a whole rest for
both instruments combined (ie, ms. 3-6) have nothing in them. They
should contan mutlimeasure rests."
reportedin = "2.3.13"
}
\version "2.3.14"
\sc
Added this to bug repository, as fermat-stemUp:
%
%Jost Schenck <[EMAIL PROTECTED]>
\header {
texidoc = "The fermata is placed too long to the left. It should be centered
over the stem."
reportedin = "2.3.14"
}
\version "2.3.14"
{\stemUp c''4^\fermata }
___
I added this to bug repository.
I think it's a bug, there should be a number over the note IMHO. Object if I'm
wrong.
%unclear
%
\version "2.3.14"
\header {
texidoc = "Single tuplets get no number above them, and no warning. They used
to produce a number in v1.6"
reportedin = "2.2.5"
}
{\time
Added this.
%important
%
\version "2.3.14"
\header {texidoc "when tupletSpannerDuration is set, tuplet numbers are
printed where there are no tuplets."
\reportedin = "2.3.14"
}
{
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\times 2/3 {c8 c c} c c c c
}
On Sunday 12 September 2004 16.52, Pedro Kroger wrote:
> Hi,
>
> The vertical space in the attached file is too tight between instruments
> and maybe too big between the staves of the piano. I also find the space
> between systems too big.
>
> You can see a pdf here:
>
> http://www.pedrokroeger.net
On Monday 13 September 2004 18.52, Christophe Papazian wrote:
> Is it a bug or a new feature ?
> phrasingslurs use all the specifications of Slur grob instead of
> PhrasingSlur grob...
> It prevents from using different visual aspects between slurs and
> phrasing slurs...
>
> some little .ly file t
On Tuesday 14 September 2004 19.56, J. Scott Amort wrote:
> Hi,
>
> Try the following ly file:
>
> \paper { raggedright = ##t}
>
> globalsettings = {
> \time 3/4
> \key c \minor
> }
>
> \score {
> \context PianoStaff \relative c' <<
> \context Staff = upper {
>
On Wednesday 15 September 2004 03.34, P Scott Horne wrote:
> In the old days of version 1.6.8, we wrote polyphony this way:
>
> <{c d e}\\{e f g}>
>
> Now the notation is
>
> <<{c d e}\\{e f g}>>
>
> There seems to be a bug in the engraving of lyrics set against a staff that
> breaks in
Added the following to bug CVS as slur-staccato.ly
%
%Antti Kaihola <[EMAIL PROTECTED]>
\header {texidoc = "
It seems that there's still room for improvement in the slur algorithm
when spacing gets tight and short slurs have to travel a large interval
and end near a staccato dot. In the example b
On Thursday 16 September 2004 10.53, Antti Kaihola wrote:
> on 2004-09-16 at 00:59 +0200, Han-Wen Nienhuys wrote:
> > That's an unfortunate side-effect of the EC fonts of TeX (they don't
> > contain normal hyphens/minuses). You can get around it by adding the
> > Latin1 hyphen, which is a hi-bit as
On Tuesday 14 September 2004 20.43, Jefferson dos Santos Felix wrote:
> The page number disappears in lily 2.3.16...
>
> jeff
This problem has now been fixed.
Thanks for the report, I have added you to the THANKS file.
Erik
___
bug-lilypond mailing li
Added to cvs.
erik
On Saturday 18 September 2004 08.06, Werner LEMBERG wrote:
> %
> % [EMAIL PROTECTED]
>
> \version "2.3.17"
>
> \header { texidoc = "
> Broken slurs must be have correct start and end points. Basically, they
> should be handled as two separate slurs, and the only connection bet
This is now fixed.
On Tuesday 17 August 2004 00.23, Erik Sandberg wrote:
> Thanks, bug report added to CVS as ambitus-accent.
> Erik
>
> On Thursday 05 August 2004 21.25, Christian Hitz wrote:
> > \version "2.3.11"
> >
> > %
> > % The scripts on the f
This is now fixed in cvs.
Erik
On Friday 09 July 2004 10.11, Erik Sandberg wrote:
> On Friday 09 July 2004 00.35, Brian Clements wrote:
> > Windows 2000 version 2.2.2
> >
> > I found that when I have chords over an 8 bar solo space with two 2 bar
> > alternate endings
This is now fixed.
On Friday 13 August 2004 21.14, Erik Sandberg wrote:
> Added.
>
> On Thursday 12 August 2004 07.59, Werner LEMBERG wrote:
> > %
> > % ottava-clef.ly
> > %
> > % [EMAIL PROTECTED]
> > %
> >
> > \version "2.3.11"
&g
This is now fixed in cvs.
On Tuesday 24 August 2004 17.06, Erik Sandberg wrote:
> \header {texidoc = "slurs are placed above up- and downbow sometimes."}
>
> \score { \relative c''{
> \clef alto
> \slurUp
> c4(^\downbow b) r2
> c4^\downbow( b) r
On Monday 13 September 2004 22.19, Pedro Kroger wrote:
> Erik Sandberg <[EMAIL PROTECTED]> writes:
> > Can you please send the .ly file also (beware that the ml strips any
> > attachemnts)?
>
> Sure (I did sent a .ly file, but it was in an attachement :-() here it
> g
Added to repository as trill-span-align.ly.
On Sunday 05 September 2004 16.05, Ed Jackson wrote:
> Hello,
>
> In the following, the "tr" trill symbol is aligned differently in
> various situations. The trill with no spanner is centered nicely
> above the note, as is the trill with the spanner cre
Added (together with the downbow collision) as slur-script.ly
erik
On Tuesday 14 September 2004 07.26, Graham Percival wrote:
> I hope I didn't cause this with my patch to scm/script.scm :(
> The slur goes right across the accent; I think the accent should get
> moved
> down.
>
> % accent touche
This seems to be fixed now.
erik
> Slurs at the start or end must not touch a stem exactly at its top.
> " }
>
>
> \score {
> \relative c' {
> a'2( f4 a | b e c a | a1\fermata) |
> }
>
> \paper {
> indent = 0.0\mm
> linewidth = 70.0\mm
> }
> }
>
> % EOF
_
Seems to be fixed in cvs.
On Friday 10 September 2004 13.17, Werner LEMBERG wrote:
> % important
> % [EMAIL PROTECTED]
> %
>
> \version "2.3.14"
>
> \header { texidoc = "
> Default slur curvature in the example below is extremely ugly. The correct
> solution is to move the start points of the slu
Added as slur-broken-tie.ly. Only the first of the two problems remains.
On Monday 13 September 2004 08.44, Werner LEMBERG wrote:
> % important
> % [EMAIL PROTECTED]
>
> \version "2.3.16"
>
> \header { texidoc = "
> This example shows two problems:
>
> . The end point of a broken slur before the
On Thursday 16 September 2004 07.46, Graham Percival wrote:
> You probably know about this one already, but I figured I'd send it
> anyway.
>
>
> \version "2.3.16"
> {
> \key g \major
> g'1
> \key c \major
> c'1
> }
>
Seems to be fixed now.. anyway I can't reproduce wiht latest cvs
erik
___
Added.
On Monday 20 September 2004 16.46, Werner LEMBERG wrote:
> % important
> % [EMAIL PROTECTED]
>
> \version "2.3.17"
>
> \header { texidoc = "
> The presence of an accidental makes the hairpin start at the wrong
> horizontal position (namely too far to the left).
> " }
>
>
> \score {
> \rela
Added.
On Monday 20 September 2004 17.31, Werner LEMBERG wrote:
> %
> % [EMAIL PROTECTED]
>
> \version "2.3.17"
>
> \header { texidoc = "
> The stem of a note produced with the \note command doesn't have the correct
> length if the font size is changed.
> " }
>
>
> \score {
> \relative c' {
>
On Tuesday 21 September 2004 19.26, Antti Kaihola wrote:
> For some reason there a gap in the pedal bracket for bars 12-21 in the
> score below although it should be continuous from the beginning to end.
> If I replace the music with a single repeating note, the pedal is ok
> too. Strange.
I did s
Added as thumb-notehead.ly.
On Tuesday 21 September 2004 06.42, Graham Percival wrote:
> From a manual example...
>
> % Lily 2.3.18, thumb articulation touches notehead
> { 8
> }
>
>
>
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.
Added as pp-ppp.ly.
Erik
On Tuesday 21 September 2004 06.57, Graham Percival wrote:
> IMO the \ff and \fff don't look so good either, but it's not as
> serious a problem.
>
>
> % Lily 2.3.18; the \ppp and \pp get overwritten by each other
> \bookpaper{raggedright = ##t }
> {
> c'\ppp c'\pp c'\ff
End of output of 'make clean;make' in lilypond-bugs/bugs/:
Now processing `lily-656219358.ly'
Parsing...
input renamed to: `__dummy.ly'
Interpreting music... [2]
Preprocessing graphical objects...
Calculating line breaks... [2]
Paper output to `lily-656219358.tex'...
FORMAT: error with call: (for
I added this bug to the bug repository as stem-dot.ly.
%
%Meixner Music <[EMAIL PROTECTED]>
\header {
texidoc = "A stem collides with an augmentation dot."
reportedin = "2.3.18"
}
\version "2.3.18"
\paper { raggedright = ##t }
\new Staff {
\key e \major \time 3/4
\relative c'' {
<< { d
On Wednesday 22 September 2004 18.22, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > The following example gives a long list of warnings and produces
> > some ugly slurs, to say the least.
>
> fixed.
The problem still persists here, can you look at it again? The assertion error
is gone t
On Wednesday 22 September 2004 23.21, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > On Wednesday 22 September 2004 18.22, Han-Wen Nienhuys wrote:
> > > [EMAIL PROTECTED] writes:
> > > > The following example gives a long list of warnings and produces
> > > > some ugly slurs, to say the le
This has now been fixed.
Erik
On Tuesday 21 September 2004 17.28, Erik Sandberg wrote:
> Added.
>
> On Monday 20 September 2004 17.31, Werner LEMBERG wrote:
> > %
> > % [EMAIL PROTECTED]
> >
> > \version "2.3.17"
> >
> > \header { tex
Hi,
Just a quick notice: ChangeLog says:
2004-09-21 Han-Wen Nienhuys <[EMAIL PROTECTED]>
* lily/slur.cc (outside_slur_callback): read #'padding for
slur-padding. Fixes: slur-script.ly
but this did _not_ fix the slur-script bug. The bug is still there. (it's not
an urgent bug
On Wednesday 22 September 2004 23.32, Wim van Dommelen wrote:
> Hi,
>
> Downloaded Lilypond 2.2.5 three days ago. Run it on W2k with cygwin. My
> first impression of the program is very good.
>
> But you will be interested in a small file generating a nice
> "programming error" message.
>
> Include
On Thursday 23 September 2004 00.22, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Han-Wen Nienhuys writes:
> > >> The problem still persists here, can you look at it again? The
> > >> assertion error is gone though.
> > >
> > > "the" problem? Please be specific.
> >
> > I don't think Eri
On Friday 24 September 2004 18.33, Wim van Dommelen wrote:
> Hi,
>
> Found another problem in Lilypond. Purpose of my file was to create a
> series of notes without the staff system underneath it. When I do that
> the stems are also shortened, they stop before touching the note heads
> themselves.
On Saturday 25 September 2004 12.11, Werner LEMBERG wrote:
> > > No. There is no means to make Lilypond handle transposition in
> > > treble clef differently to transposition in bass clef. This must
> > > be done automatically.
> >
> > try
> >
> > \override OctavateEight #'transparent = ##t
> >
On Sunday 26 September 2004 11.05, Werner LEMBERG wrote:
> Sigh. It seems that I'm not able to write what I really want.
> Another try. I know that I can tune the clefs, but this isn't my
> problem. Please concentrate on the process of transposing! All music
> I enter in LilyPond is written as
On Sunday 26 September 2004 18.28, Sean Reed wrote:
> hello,
>
> i'm getting the following message in my terminal output when running
> 2.3.18 on mac 10.3.5:
>
> programming error: No solution found for Bezier intersection.
> Continuing; crossing fingers
>
> when i run lilypond on my full .ly-file
On Monday 11 October 2004 11.17, Paul Scott wrote:
> The manual says:
>
> To change the paper size, there are two commands,
>
> #(set-default-paper-size "a4")
> \paper{
> #(set-paper-size "a4")
> }
>
>
> This gives:
>
> warning: lily-guile: Mus
Citerar Mats Bengtsson <[EMAIL PROTECTED]>:
> Of course, I should have cross-posted already the previous email to
> bug-lilypond.
>
> I just came to think of yet another possible solution, namely to
> mimic the \verb command in LaTeX and let the user himself find a
> character to use as start and
On Tuesday 12 October 2004 07.13, Jefferson dos Santos Felix wrote:
> Recently I have use the \partcombine to create SATB scores, but I have
> some problems:
I don't think \partcombine was really intended to be used for SATB. I would
guess that
<< \soprano \\ \alto >>
is really what you want.
I
On Wednesday 13 October 2004 10.22, Mats Bengtsson wrote:
> >>It just seems to me that maintaining \lilypond{} is more trouble than
> >>it's worth.
> >
> > I think it just broke because of the lilypond-book rewrite, and the
> > decision to require [fragment] explicitly.
>
> The problem with matchin
added.
On Saturday 25 September 2004 15.23, Werner LEMBERG wrote:
> % important
> % [EMAIL PROTECTED]
>
> \version "2.3.18"
>
> \header { texidoc = "
> \transpose should handle \quote fragments also. In the example below,
> both hornOne and hornTwo are input as they sound (i.e., in C) so that
> t
Added as transposition-quote.
On Saturday 25 September 2004 14.52, Werner LEMBERG wrote:
> %
> % [EMAIL PROTECTED]
>
> \version "2.3.18"
>
> \header { texidoc = "
> \transposition, positioned in a transposed voice, then used in another
> transposed voice, gives wrong results. As can be seen in th
Added separately as ottava-font-size and c-ottava-triplet-bracket.
I'm introducing a new convention now, bugs that involve collisions are called
c-*.ly (I just wanted some more structure)
On Sunday 26 September 2004 17.32, Werner LEMBERG wrote:
> %
> % [EMAIL PROTECTED]
>
> \version "2.3.18"
>
>
sorry, I don't understand. What is the problem?
On Monday 27 September 2004 16.48, Werner LEMBERG wrote:
> % important
> % [EMAIL PROTECTED]
>
> \version "2.3.18"
>
> \header { texidoc = "
> The \tag command doesn't properly skip music expressions.
> " }
>
> foo = \relative c' {
> \tag #'xxx { c
I guess both your recent reports are actually the same problem; scripts do
collide with slurs. This bug is in cvs as slur-script.
The bug is marked as wontfix, see:
http://lists.gnu.org/archive/html/bug-lilypond/2004-09/msg00201.html
Any objections are welcome.
Erik
On Monday 27 September 2004
On Tuesday 28 September 2004 10.50, Werner LEMBERG wrote:
> > sorry, I don't understand. What is the problem?
>
> foo = \relative c' {
> \tag #'xxx { c2 ges' | }
> \tag #'yyy { c2 fis | }
> a1 |
> }
>
> In the image you should get (in absolute pitches)
>
>upper staff: c' ges' a'
On Tuesday 28 September 2004 09.43, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > >> (assuming this is "wontfix" as in "delete the bug report and forget
> > >> about
> > >> the problem". If "wontfix" means "we'll have a look at it after the
> > >> next stable
> > >> release", then that's
This is temporarily fixed now, the example gives programming errors but the
output is now more reasonable.
Added it as progerror-max_h
Erik
On Wednesday 22 September 2004 11.00, Mats Bengtsson wrote:
> The following example gives a long list of warnings and produces
> some ugly slurs, to say the
Added this to cvs.
%
%
\version "2.3.19"
\header {
texidoc = "rehearsal mark collides with slur"
reportedin = "2.3.19"
}
\paper { raggedright = ##t }
\relative c'' {
f1( \mark \default f1)
}
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http:
On Sunday 03 October 2004 20.15, David Bobroff wrote:
> I just ran convert-ly on a file with \version "2.3.17" and the output
> had \version "2.3.18" rather than "2.3.20"
>
> I'm running latest CVS (ChangeLog 1.2681).
This is normal. convert-ly usually doesn't upgrade \version statements unless
t
Hi,
lilypond hangs during "Interpreting music.." on this score. Latest cvs.
\version "2.3.20"
\addquote quotedPart \relative c'' {R1 \grace g16 f4 e \grace e16 d4 c}
\relative c'' {
\grace g16 f4 e \grace e16 d4 c
| \grace { \quote quotedPart 1 } \quote quotedPart 1
}
Added this to cvs as grace-partial.ly. The issue of disappearing quoted grace
notes is a consequence of how grace note timing is handled by lilypond. You
will have to quote the grace note separately until this is fixed, using
something like:
\grace {\quote quotedPart 16} \quote quotedPart 1
(th
On Sunday 03 October 2004 21.42, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Added this to cvs as grace-partial.ly. The issue of disappearing quoted
> > grace notes is a consequence of how grace note timing is handled by
> > lilypond. You will have to quote the grace note separately unt
Added as slur-fermata.
On Sunday 03 October 2004 05.29, Werner LEMBERG wrote:
> %
> % [EMAIL PROTECTED]
>
> \version "2.3.20"
>
> \header { texidoc = "
> The stacking order of the end of a slur and a fermata is not correct
> sometimes.
> " }
>
> \score {
> \relative c'' {
> r2 c4--( e | f4
401 - 500 of 818 matches
Mail list logo
