piano-pedal-{performer,engraver} bug

[EMAIL PROTECTED] writes: > Since SustainEvent and friends are symbols (not strings), we should > be comparing them to symbols instead of strings. Thanks. Applied. Did this cause any errors, BTW? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~

More unfolded tremolo problems

[EMAIL PROTECTED] writes: > If the tremolo is dotted, the individual unfolded notes are dotted. > > Example: fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing li

Re: Lily 2.2.0 is out

[EMAIL PROTECTED] writes: > Hans Forbrich writes: > > > Tarball download still points to 2.1 directory. > > URL please? i already fixed this. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen __

Re: Devnull

[EMAIL PROTECTED] writes: > I don't know Scheme, so I'm following blindly here. I tried it and got: > yes, it's for .37, not earlier versions. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___

Devnull

ress skip (ly:music-length mus)) skip )) \score { \notes \relative c' \new GrandStaff << \new Staff { \cadenza c4 \bar "|." } \new Staff { #(ly:export (mmrest-of-length cadenza)) c4

Re: using the devel version

tutorial? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Re: \partcombine terribly broken

rt. ( suggests that the upper voice plays the c, while < \\ c''>> suggests that the lower voice plays the c) > > I.e., I suggest an additional rule saying that polyphony notation should be > used instead of chord notation if the pitch of the second part is > high

Re: \partcombine terribly broken

ort), > and maybe rewrite the section: I should be grateful if you could try to rewrite the complete section of the manual. I've just added a few updates, but surely the manual can be still more clear. > -- Han-Wen Nienhuys | [EMAIL PROT

Another part combine bug

r e e g g a2 } > } I added a remark to the manual. \partcombine can't be inside \relative. Use \partcombine \relative .. \relative .. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list

partcombine brokenness

[EMAIL PROTECTED] writes: > hi! > > I've been able to isolate the partcombine brokenness. Here's a score > demonstrating it: can you verify that this is fixed in CVS? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http:/

Re: \partcombine terribly broken

ythmically? Hi! maybe you can look at input/regression/part-combine*.ly for better examples. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

\partcombine terribly broken

uldn't be. Why? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

RE: Homepage: windows error reporting guidelines

we could use lily-wins.py to provide more debugging information -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

cannot find Voice

t; > \lyricsto A \new Lyrics \lyrics { a a a a } > >>} > > The following code gives the same output without warnings. IMHO, both ways > should be allowed: If the first version would not give a warning, how would you catch typing errors in the Voice names? -- Han-W

Re: another convert-ly problem

There are 318 pieces of music on Mutopia only, which were typeset with v1.8 > and earlier. In most cases, the "balanced parenthesis expressions" > consist of > [..] Very good ideas, indeed! I would welcome a patch that implements this. -- Han-Wen Nienhuys | [

Re: another convert-ly problem

was due to laziness that you > left out some nontrivial conversions.. Almost correct: I limit myself to regexps _because_ I am lazy :-) -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mai

Re: another convert-ly problem

[EMAIL PROTECTED] writes: > On Friday 26 March 2004 01.47, Han-Wen Nienhuys wrote: > > [EMAIL PROTECTED] writes: > > > It might be too much to demand that convert-ly should upgrade > > > #'(italic "Simile") > > > to > > > \markup {\it

Lack of clarity over mensural time signatures

free, a. already paid for (Peyton Jones) > > > ___________ > Bug-lilypond mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Homepage: windows error reporting guidelines

to [EMAIL PROTECTED]" > > Because I think many of the problems can easily be solved by looking at the > generated log file. do you want only test.log or both bug.txt and test.log? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen __

Another similar convert-ly bug..

y Voice.Stem \set #'stroke-style = #'( c4)} > } > > (after fixing this error manually, the file is converted correctly to 2.1.32) Can you verify that the convert-ly.py in CVS does handle this correctly? thanks! -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://w

RE: Ottava clef "8" shouldn't be counted

ent of the 8. (And as I can see it is equal now > between all staves.) I fixed this in cvs. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org

another convert-ly problem

nfortunately, I don't see good way to fix this. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

RE: Rehearsal mark disappears

"@ref{Staff_collecting_engraver} must move along, otherwise all marks" "end up on the same Y-location" , iow.: add \consists Staff_collecting_engraver to Staff context. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | htt

SuSE fixes for Lilypond

t;{} >{}~ > if ! cmp -s {} {}~ ; then cat {}~ >{} ; fi ; rm {}~ > ' \; I'm missing the patch itself? BTW, you might want to have a look at packaging Lily 2.1 ; we're very close to a 2.2 release. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~ha

Re: bugs.ly

m just curious: Does this book say that \chords c^3 and \chords c should be > typeset identically? (in that case i'll just do a dirty workaround in my > music). c^3 is just a plain fifth. Since that doesn't have a traditional harmonic function, I suppose it doesn't qual

vocNam?

ll. thanks, fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Re: bugs.ly

[EMAIL PROTECTED] writes: > Thanks for trying. daveA And *you* are saying this to *me*? You can also throw out your computer with the trash, and write parts by hand, you know. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~han

Homepage: windows error reporting guidelines

to [EMAIL PROTECTED]" > > Because I think many of the problems can easily be solved by looking at the > generated log file. where do users get the test.log file from? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___

RE: Rehearsal mark disappears

[EMAIL PROTECTED] writes: > Attached. > > Thanks, > > Bert > > Subject: Rehearsal mark disappears I get four fermatas over here? What's wrong according to you? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | ht

Ottava clef "8" shouldn't be counted

ateEight #'Y-extent-callback = ##f \override Staff.OctavateEight #'padding = #2 -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Re: Crash 11

t make anything of it, because the binary has been stripped of its debugging information. Can you send the .ly causing the crash? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROT

Choral example for documentation; Cygwin comments

[EMAIL PROTECTED] writes: > makes intensive use of the new text features and adjusts the spacing in > a number of important ways. The file is public domain. Are you sure? (Ira Bishop Wilson died in 1950) -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~

bugs.ly

ode support for it. Han-Wen (Getting very tired of yet another chord name request) -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

tuplet bracket skewers numbers

[EMAIL PROTECTED] writes: > In this example the tuplet bracket sticks into the tuplet numbers. > Should this be taken care of automatically, or is the user expected to > adjust it? fixed in cvs. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.n

papersize

, the old way (as described in the doc for 2.0) > papersize = "letter" > works fine. This is a bug in the documentation. You should use #(set-paper-size "letter") outside of \paper { }, i.e. \header { .. } #(set-paper-size "letter") \score { ..

Rehearsal mark disappears

[EMAIL PROTECTED] writes: > See this fragment: can you post a full .ly? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/

the future of \addlyrics

d it. For the moment, \addlyrics is an undocumented feature. If it is disappears all byitself, there is no need for fuss. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://

midi lyrics broken after slur

[EMAIL PROTECTED] writes: > hi, > > It seems that any syllables after a slurred syllable are not output to midi. should be fixed in cVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypon

Re: Lilypond 2.1.32 released

[EMAIL PROTECTED] writes: > > Not quite.. 2.1.33 makes normal text only in the first movement, and smallcaps > in the second movement: > whoops, fixed that too. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4al

Re: spelling corrections

Where? > Should smallcaps really be small caps? Yes, unless it refers to the command \smallcaps > ascii=ASCII; What file is the license documented at to change it? Documentation/user/fdl.itexi > Are there any times that backend and frontend should not be hyphenated > (excluding wit

Too many clashing notecolumns

[EMAIL PROTECTED] writes: > hi, > > the following code results in the below warning, & incorrect output. > fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mai

Feta diagram broken 2.1.32

[EMAIL PROTECTED] writes: > The second diagramm at > http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/The-Feta-font.html#The%20Feta%20font > doesn't have any feta symbols on it. fixed. > http://mail.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nien

squished rests demo

[EMAIL PROTECTED] writes: > Ok, here's a demo of the squished rests. I've moved this to > bug-lilypond because this is quite obviously a bug. Thanks for the report. This was a tricky bug, tickled by the new break-alignment code. I have fixed this in CVS. -- Han-Wen Nienh

Confusing titles in docu

[EMAIL PROTECTED] writes: > hi, > > Under "Changing defaults", there are two subtopics "Fonts" and "Font size". > Under "Fonts" there is a topic "Selecting font sizes": This chapter is still under construction. Stay tun

spelling corrections

Thanks, patch looks OK, integrated it. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Re: key signatures

ion = ##f) -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Re: truncated math mode in Staff.instrument

ks the > string into several strings. I consider that a bug. This is a hack to make early -fps postscript output work. I've removed it. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailin

Re: Lilypond 2.1.32 released

[EMAIL PROTECTED] writes: > Han-Wen Nienhuys wrote: > > >>5. Repeat barlines are engraved to the left of the key signature. My feeling > >>is that it should be the other way around. Am I wrong? > >>\score { \notes {\key f\major a1 \break \repeat "volta

Documentation bug in 2.1 tutorial

[EMAIL PROTECTED] writes: > On this page: > > http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Music-expressions-explained.html#Music%20expressions%20explained Thanks for the report. I fixed this. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.n

make web troubles

eedback to help lead me along the right path for troubleshooting these > problems would be greatly appreciated. I suspect a GS bug. What version of Ghostscript do you run? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen _

Re: Lilypond 2.1.32 released

b16} \\ {b8 b b16}>> r b b b % <-- these notes should be beamed > } This is a documented deficiency of the autobeamer: autobeams are not created when terminating a context. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Odd artifact using 2.1.32

e the tagline in the score for more info. > > It's possible I'm doing something wrong here -- however, there was no > problem in 2.1.31, so I'm assuming that this is a new bug. I've fixed this in CVS. -- Han-Wen Nienhuys | [EM

Odd artifact using 2.1.32

e the tagline in the score for more info. > > It's possible I'm doing something wrong here -- however, there was no > problem in 2.1.31, so I'm assuming that this is a new bug. I've seen these problems before, but only in the direct PostScript output. I guess I have

crash: with {\consists Mark_engraver}

; } > > (2.1.31) > > Greetings, > > Bert Can you send a full .ly file ? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Global auto-beam settings? Was: convert-ly crash

BeamSettings > globally within the \paper{} section? Of course, I could do a I dislike the way that \override misused for transporting property settings, but I still haven't figured out what the alternative should be. The old syntax is still functional. -- Han-Wen Nienhuys

Re: Odd Crash

Removing the forced beam fixed everything. Perhaps > this should have a greater status than just a warning? this doesn't help me; can you send me a complete example file that causes a crash? I can't duplicate your problem. -- Han-Wen Nienhuys | [EMAIL P

lilypond 2.1.31 \harmonic bug (inhibit accidentals)

{ } > } > > Please see png attached... I was explained by Werner Lemberg that harmonics never get accidentals. Werner? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PR

Re: staff lines problem in professional printing

blems with > stems and beams? Yes, the errors are in the order of points. That's pretty brutal rather than subtle. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED

Odd Crash

rewed with tonight is one part, which compiled fine by > itself. When included in the main score, BOOM! > > If you need any more info, buzz me privately as well, as I normally > don't subscribe to this list. Can you send either the .ly or a backtrace of the crash from GDB? priv

lilypond crash

fContext > % \accepts Dynamics > } > } > } -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

RE: staff lines problem in professional printing

hat easily can be the > scanner's error). Curious - I suspect that the problem is caused by TeX's \vrule (which are only used for staff lines) in combination with improper scaling somewhere. Stay tuned. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanw

Slurs broken 2.1.27 DrumStaff

[EMAIL PROTECTED] writes: > Hi. > > Inside a DrumStaff or a DrumVoice, both Slurs and PhrasingSlurs don't > work: they result in "Junking event" warnings. > > This also means that appoggiaturas die too. Drummers use these alot > (we call them flams or ru

staff lines problem in professional printing

d-book, v2.1.26). How did you make the .ps file? Also, can you check (maybe you could use printout from a printer?) whether it is the staff lines that are too long, or the bar is shifted left. -- Han-Wen Nienhuys | [EMAIL PROTECTED] |

tuplet fraction bug

[EMAIL PROTECTED] writes: > In short, shouldn't \times x/y {notes} produce y:x over the {notes} in > the output? I think you're right. Fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen

PianoStaff display problems

[EMAIL PROTECTED] writes: > I tried just putting in spacer rests, but that didn't work either. If > that's all there is in the lower cleff, it won't display. example please. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://

Re: Lilypond 2.1.27 and MIDI output

rly with midi output? I had the following > included in a file with no luck and had gone back through with rosegarden to > resolve the output problems: This is fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen __

attachment filtering

mechanism against virus forwarding. If you want to send .ly or diff files as attachments, then rename them to .txt and attach them. greetings, Han-Wen -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond

input/regression/rhythmic-staff.ly

thms > > > http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/lily-1818775889.ly > is also broken. From memory it should display a rhythm on a single line > also. thanks, fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED]

Re: Real user now!

ago where an open is closed by (in the heading > "Frequently asked questions" which makes the page render rather badly in > some browsers (because most of the text is h1 size). fixed. > > -- > http://www.mupsych.org/~rrt/ | irrevocable, a. expensive; see a

doc questions

orical notes interesting, I wonder if the Notation manual is the right place for this information. > Shouldn't 'backend' be hyphenated? yep. > 'piu' should have an accent over the 'u'; Do we try to avoid certain > characters in the docs? no, typo. > > > __

doc questions

27;? > abc2ly: mentions the program both as ABC and abc ABC is format. > musedata2ly: mentions the program both as Musedata and musedata. don't know. Check out the website to musedata. > Should 'Scheme datatypes' be corrected to 'Scheme data types' in the index?

bracketed stems are too long at small size

[EMAIL PROTECTED] writes: > At the global-staff-size of 11 and below the following code produces two > long stems for the 'c b a' sequence: Fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___

doc spelling questions

[EMAIL PROTECTED] writes: > When should LilyPond be spelled 'lilypond'? Is this debris resulting from Only if referring to the program binary itself, and then it should be spelled @code{lilypond} or @file{lilypond}. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://

(possible) doc spelling corrections

hould 'wildcards' be 'wild cards'? Not patched. No, wildcard is correct. > time related choice. Maybe I switch between them. Numerous (but probably not > all) patches. Should they be implemented? Yes, consistency is better. I thought that canceled was American, and c

Doc question: capitalization

apitalized) preferred? \applyoutput doesn't tell what the section is about, which is bad, IMO. The section title should be changed to be descriptive of its contents. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen _

Re: Real user now!

[EMAIL PROTECTED] writes: > On Thu, 19 Feb 2004, Han-Wen Nienhuys wrote: > > > [EMAIL PROTECTED] writes: > > > I'm now using Lilypond. I just installed 2.1.25, and noticed a couple of > > > small things: > > > > > > 1. The lilypond-documentati

Re: Real user now!

[EMAIL PROTECTED] writes: > On Thu, 19 Feb 2004, Han-Wen Nienhuys wrote: > > > [EMAIL PROTECTED] writes: > > > I'm now using Lilypond. I just installed 2.1.25, and noticed a couple of > > > small things: > > > > > > 1. The lilypond-documentati

re: \once broken ?

[EMAIL PROTECTED] writes: > I confirm the bug reported by Juergen about \once being broken. But my > symptoms are sightly different: in the following example, the "B" mark > is missing. It's OK without \once. fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED]

Pointless repetition in manual

[EMAIL PROTECTED] writes: > "For Lyrics, Lyrics, ChordNames and FiguredBass," > > Presumably you only want to mention Lyrics once (was one of the mentions > supposed to be something else?). fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http:/

lilypond-book and relative octave

[EMAIL PROTECTED] writes: > Something's gone wrong with relative tag, some lines are one or two > octave higher than they should, see > > > > http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Grace-n > otes.html#Grace%20notes fixed. -- Han-Wen Nienh

bug: \tiny at beginning of \times

[EMAIL PROTECTED] writes: > Example: > > \times 2/3 { \tiny c8 \normalsize c c } > > Bug: The '3' in the tuplet bracket is typeset with small font. that's not a bug; the start of the bracket happens at the same time as the c8. -- Han-Wen Nienhuys |

convert-ly and auto-beam-setting

ECTED] > http://mail.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

postun removal of ls-R should be preun

[EMAIL PROTECTED] writes: > Otherwise the uninstall won't also remove the 2.1.xx directory (as the > directory won't be empty until after the postun script). fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.x

Re: A couple of problems in lyrics handling (in 2.1.26)

g, but shouldn't > > > give an error. > > > > Please send .ly examples. > > I attach two short files. test1.ly demonstrates problem 1 and test2.ly > demonstrates problem 2. both fixed in current CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs

Manual error: "lazyness" should be "laziness"

thanks, fixed. [EMAIL PROTECTED] writes: > This appears several times. > > > ___ > Bug-lilypond mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys | [EMAIL

A couple of problems in lyrics handling (in 2.1.26)

se send .ly examples. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

2.1.26 still crashes

[EMAIL PROTECTED] writes: > And.. sorry, I still can't create a core dump, even if lilypond-bin seems to > contain debugging symbols (compiled with -g, and the file is big): no need for a core dump, just run the binary in gdb, gdb lilypond-bin r kaboom.ly (crash) bt --

/etc/profile.d/lilypond.sh is a bad idea

tallyr reading files from old versions, esp. when people update by hand. > Perhaps best of all would simply be to install your stuff in TEXMF_LOCAL > (if it exists) and otherwise TEXMF. I'm happy to help with getting this > working if you think it's a good idea. Is t

"Cross thumbs"

[EMAIL PROTECTED] writes: > I think in English this rather endearing TeX-style warning message should > be "Cross fingers". :-) (In Dutch the word "thumb" also a verb, meaning to cross fingers.) fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | ht

chordnames 2.1.0

[EMAIL PROTECTED] writes: > Hi. > > In lilypond 2.1.0, chord suffixes print differently dependant on the root > note: > > e4:7.9- yields "E7" > ees4:7.9- yields "Eb/b9" > thanks, fixed in CVS. -- Han-Wen Nienhuys | [EMAIL P

convert-ly bug

[EMAIL PROTECTED] writes: > If paper.ly contains this: unfortunate, but fixing this is impossible. sorry. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] h

minor typo

[EMAIL PROTECTED] writes: > Look at: > out-www/lilypond/Automatic-part-combining.html > The two examples are in different octaves, for no apparent reason. > > (this is from my local lilypond-doc 2.1.25; the images are broken in the web > version) fixed. -- Han-Wen Nie

build dependencies

1.6 header files are missing. huh? Are you sure? autogen runs configure, so it will complain as much as configure. > http://mail.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___

PNGs missing from lilypond-documentation-2.1.25 RPM

[EMAIL PROTECTED] writes: > Some of the PNGs are missing from the docs RPM, e.g. lily-918677483.png. This might be a side effect of my RPM building process. To save time, I reuse results of older RPM builds, which might cause some files in the RPM to be out-of-date. -- Han-Wen Nienh

RPM postun script should rm ls-R file

e/lilypond is properly removed. fixed, hopefully. > http://mail.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu

Re: LilyPond 2.1.25 packaged for Cygwin

t; only with lilypond-book. This is fixed in CVS: you have to use --output. The command you just specified would overwrite the input file with the output. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Default "engraved by" message shouldn't contain a comma

Thanks for all the bugreports! I applied/forwarded them. [EMAIL PROTECTED] writes: > because it looks like a date. Could you make it "Engraved by LilyPond > version x.y.z"? That's ok? Or how about: Engraved by LilyPond (v2.1.92). -- Han-Wen Nienhuys | [EMAIL

final barline bug

[EMAIL PROTECTED] writes: > This file exhibits a bug in 2.1.25. The final group barline connecting > the staves is shifted to the right by its own width. > fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.n

Tie bug?

the delay; this is fixed in CVS now. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

allowbeambreak not done right

same time. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

<    5   6   7   8   9   10   11   12   13   >