Fedora 22 bug lilypond 2.19.21

the bug. Andrew Bernard Log level set to 287 GNU LilyPond 2.19.21 Relocation: is absolute: argv0=/home/andro/lilypond/usr/bin/lilypond PATH=/home/andro/lilypond/usr/bin (prepend) Setting PATH to /home/andro/lilypond/usr/bin:/opt/anaconda/bin:/opt/anaconda/bin :/usr/local/bin:/usr/local/sbin:/usr

Another parenthesize issue

In the following MWE, when a slur is used, the two articulations overlap. I believe they should be stacked, as in the case shown with no slur. \version 2.19.25 { \slurDown c''16^!-\parenthesize ^ d''-\parenthesize ^ ^!( ees'') fis''-\parenthesize ^ ^! } Andrew

Vertical alignment - programming error

Using a grace note set that spans two staves, reduced from a vastly more complex real score to a more minimal example, if I use a hairpin between the sfz and the p indications, I get a programming error related to vertical alignment that I am unable to understand, or eliminate. Can folks

Assertion failed

Using 2.19.30, hoping to avoid the core dumps from 2.19.29, I get the following error on my moderately large score: Preprocessing graphical objects...lilypond: /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:227: T

Re: Assertion failed

Debugger backtrace attached. This is from 2.19.30. Andrew backtrace Description: Binary data ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: crash with gs-error

At least on Ubuntu 15,04, it's the page number -1 that does it. Zero or positive numbers work. Andrew On 12 July 2015 at 07:06, Thomas Morley thomasmorle...@gmail.com wrote: The following crashes with released 2.19.22 %% snippet-start \version 2.19.22 \paper { first-page-number = #-1 }

Re: Grace notes and staff miss-alignment

Works fine on Ubuntu 15.04, 64 bit, lilypond 2.19.27. Andrew ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Fontmap entry for Fontmap.local ends prematurely!

Hi Karl, As mentioned before, I tried this out on a fresh install of Centos 7 and there is no issue. Are you rigidly committed to Centos 6? I am not sure how many trailing releases behind the lilypond developers generally support, but this is a viable solution if it does not break other

Re: Cannot locate libffi.so.6 on openSUSE Leap 42.1

Confirming this is fixed on a pristine install of openSUSE Leap 42.1, with lilypond 2.19.33. Andrew ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: PNG output cannot be created with Mac OS X version of Lilipond 2.18.2-1

Hi Jun, What version of Mac OS X are you on? Current version 10.11.2 provides libgs.9.16.dylib. Andrew ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Slur inside tuplet bracket causing crash

When I attempt to move the following slur inside the the tuplet bracket relese 2.19.34 crashes with an assertion failure. Excerpting the code to isolate the issue results in incorrect output and error messages, but no assertion failure. What is going on here? In the context of my very large

Re: crescendo & decrescendo marks not end correctly

Hi Fan, Without wishing to sound annoying, this piece is written for harpsichord, and crescendo and diminuendo marks do not apply in that context, and Bach never used them for harpsichord music. The example you link to is an erroneous modern edition. Engraving it as Bach intended would be a

Cannot locate libffi.so.6 on openSUSE Leap 42.1

The downloadable version of lilypond 2.19.32 will not run on openSUSE Leap 42.1 as it is unable to find libffi.so.6, which is not installed on this OS. The lilypond distribution includes this shared library in its usr/lib64 directory. But the installer script only creates a lilypond wrapper

Re: Parenthesized accent

Hi Malte, Thanks so much. But don’t you think this is a defect in lilypond? Of all the workarounds I have seen ever in lilypond, this is the most horrifying complex and most unsatisfying. Can we raise this as an issue? Andrew ___ bug-lilypond mailing

Re: Lilypond 2.19.43 font issue

Hi Hans, On 13 June 2016 at 02:11, Hans Åberg wrote: > The solution: the UTF-8 locale has not been set as it wishes [1]. OS X > 10.11.6 has no leading language “en”, only > LC_CTYPE=UTF-8 > > It suffices with any single one of: > export LC_CTYPE=en.UTF-8 > export LC_CTYPE=en_US.UTF-8 >

Re: Lilypond 2.19.43 font issue

Hi Hans, Mac 10.11.6? Are you on a beta release? All bets are off in that case. Just asking. Andrew On 12 June 2016 at 7:55:48 AM, Hans Åberg (haber...@telia.com) wrote: The code below produces, using lilypond-2.19.43-1.darwin-x86 on OS X 10.11.6, the diagnostic: Finding the ideal number of

Re: Beaming and slurs across staves

Can we please raise this as a bug in the bug tracker? I encounter this situation frequently in my scores. Andrew On 26 May 2016 at 21:16, David Kastrup <d...@gnu.org> wrote: > Andrew Bernard <andrew.bern...@gmail.com> writes: > >> Thanks. Do we raise

Beaming and slurs across staves

I keep finding situations using beamed groups across staves where adding a slur or a phrasing slur causes lilypond to fail with the following error: Processing `/home/andro/work/lilypond/fp/exp-slur-crash.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal

Re: Beaming and slurs across staves

Thanks. Do we raise a bug? The program stops and will not continue to compile after this error. Andrew ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Wrongly combined note heads

Hi Simon, What does Elaine Gould say about resolving this? There are a lot of different styles to adopt when faced with this scenario, and although the current lilypond approach is unreadable, you can fix it according to whatever style you prefer. Fixing lilypond would presumably mean adopting

Re: Wrongly combined note heads

Hi Paul, Yo can do this: \version "2.19.42" \language "english" { \clef treble << { \voiceOne g'!4 gs'4 } \new Voice { \voiceTwo gs'4 \once \override NoteColumn.force-hshift = #1 g'!4 } >> } I think the behaviour you show is normal lilypond

Tuplet numbet text

When setting the tuplet number text, in a piece that uses the full fraction throughout, when temporarily set to just the denominator on a nested tuplet, if the nested tuplet comes first the out tuplet text is also set to the inner setting. This does not occur if the inner tuplet comes later. Is

Re: Noteheads slightly too large

Hi Abraham, What unit is this particular em? In typography at least an em is a measurement equal to the currently specified point size for a font. That does not seem to fit your analysis here. Andrew On 10 February 2016 at 02:12:48, tisimst (tisimst.lilyp...@gmail.com) wrote: Relative to a

Re: Noteheads slightly too large

Hi Abraham, Thanks for this explanation. Now that I have read up on this, for TrueType at least, I see that FUnits, or font units are used, and that there are a given number of units-per-em for a specific design, say 1000 or 2048 and so on. I can’t find much reference to em-units - to me that

Re: Default font for the web site

Hi Simon, No. In my experience doing typography for people, for every typeface that one person likes, another loathes it. Taste in type is very personal and very emotive – you can never win and satisfy all. Everybody now has their own expert opinion, even though typography is a very refined

Re: Default font for the web site

Hi Simon, There are a lot of people who strongly dislike Garamond, I know from experience with typesetting. [This goes to the point of my previous email.] And a modified Garamond is/was the Apple corporate font since 1984, so the whole family looks terribly tired and overused. I am probably

Re: fondu fails on newer OS X versions

Hi Thomas et al., While I was helping Mats look into this I noticed the same point. The defect means you can’t even use a basic system font like Times in a font name override in markup on the Mac. Given that fondu is moribund, does this topic need to go the development list for discussion?

Re: fondu fails on newer OS X versions

Hi Mats, This may be a half baked answer, since it is a long time since I ever did any Mac programming. But here are some thoughts. The designers of the file system for Apple invented the idea of a data fork and a resource fork to store everything that they deemed to be not ‘data’, that is,

Cross staff dynamics

I am having difficulties with cross staff dynamics throwing errors and causing collisions in 2.19.44 (at least). The issues are the same as reported here: https://lists.gnu.org/archive/html/bug-lilypond/2014-07/msg00104.html Has there been any work on this issue and topic? Andrew

Re: Major Minor Chord

Hi Craig, Not at all. This is not a bug. If you want this to express the chord construct you are describing, explicitly put in the accidentals. Lilypond has no notion of standard chords in various periods of music, unless you are using a chord mode. This is plain note entry. Andrew On 10

Font cache issues on Windows 10

Where are we at with the font caching issue on Windows 10? There does not appear to be much discussion on the bug list presently, but I certainly experience the slow down. After being advised to remove the font cache directory, things speed up after that, when using Frescobaldi. But now I am

Re: #4975 [Windows] Grace notes cause staff to protrude into the margin

Hi Ralph, On Windows 10 under 2.19.49 I get: Parsing... Interpreting music... Preprocessing graphical objects... programming error: mis-predicted force, 108.120472 ~= 108.221141 continuing, cross fingers programming error: mis-predicted force, 108.120472 ~= 108.221141 continuing, cross

RE: easyHeads size

Hello Tanner, Don't be so quick to assign a bug! :-) The \huge command only applies to text in markups, not noteheads. To change the notehead size you can increase the global staff size, or you can adjust the size of the notehead grob itself. For example: \override NoteHead.font-size = #3

RE: easyHeads size

Hi Simon, So it is a bug actually? Andrew -Original Message- From: bug-lilypond [mailto:bug-lilypond-bounces+andrew.bernard=gmail@gnu.org] On Behalf Of Simon Albrecht Sent: Saturday, 12 November 2016 10:55 AM To: Tanner Noguess ; bug-lilypond@gnu.org Subject:

RE: easyHeads size

Mea culpa. Andrew -Original Message- From: Simon Albrecht [mailto:simon.albre...@mail.de] Sent: Saturday, 12 November 2016 10:54 AM To: Andrew Bernard <andrew.bern...@gmail.com>; 'Tanner Noguess' <jtnogu...@gmail.com>; bug-lilypond@gnu.org Subject: Re: easyHeads size Hi A

RE: easyHeads size

Yes, I am completely wrong. Sorry folks. Andrew -Original Message- From: Simon Albrecht [mailto:simon.albre...@mail.de] Sent: Saturday, 12 November 2016 9:11 PM To: Andrew Bernard <andrew.bern...@gmail.com>; 'Tanner Noguess' <jtnogu...@gmail.com>; bug-lilypond@gnu.org

RE: Mark / Barcheck Bug (#1626) Appearing Again

Hi, Don't you have to provide an argument for \mark, I thought? I am not familiar with 2.18.2, but in 2.19.48 you do: Processing `/tmp/frescobaldi-pofhqya8/tmp1asznm_p/document.ly' Parsing... /tmp/frescobaldi-pofhqya8/tmp1asznm_p/document.ly:4:20: error: wrong type for argument 1.

Parenthesis issue with cross staff beaming

Hi All, Here is an MWE showing an issue I encounter regularly with the parenthesizing of accents. It only occurs when using cross staff beaming which I use a lot. The reported error is: . programming error: Improbable offset for stencil: inf staff space Setting to zero. continuing,

Re: force-hshift and dotted rhythms, 2.19.57

Hi Knute, I have often seen this. I just move the dot as well. I thought dots had a more or less independent life. The same occurs when moving dotted rests. Whether this is a big or not, I can't really say. Andrew ___ bug-lilypond mailing list

Re: Lilypond 2.19.80-1 hangs

Hi Massimo, Thanks for sending the file. It compiles fine under 2.19.18 on Ubuntu, However, your file is made up of hundreds of lines like this: %Sezione M << {\parentheAll f,,8 bes,->~ bes,2.} \\ {s4 bes,,-. bes,,-.} >> << {bes,,8 f,~ f,2.} \\ {s4 f,,-. f,,-.} >> 8 <<

Re: Lilypond 2.19.80-1 hangs

Hi David, OK, but I have seen this exact thing before with another user I was helping once and it is only triggered when the number of lines of this construct become large, past some threshold. It does not seem to happen with minimal examples. So would perhaps the file Massimo has be able to be

Re: comment bug

Isn't it simply that you can't have nested block comments? Andrew On 27 May 2018 at 01:14, bb wrote: > > \version "2.19.80" > > %{ > \score { > << > %{ > %some code > %} > >> > } > %} > > ___ bug-lilypond

Re: LilyPond Download does not work!

Hi Phil, This is what I keep exhorting people to do - use the latest version. This is probably a Frequently Issued Response :-) on the list by now! I know 2.20 has not come out yet, and when it does 2.18.2 will be obsolete, but at the risk of inflaming controversy, isn't about time we started

Re: Long compile times with many empty bars

Hi Paul, How is that code recursive? Confirming the long compile times, Simon. Andrew On 7 April 2018 at 08:52, Paul Hodges wrote: > Ah, the perils of recursion! (says an aged programmer) > ___ bug-lilypond mailing list

Re: Long compile times with many empty bars

This is an extremely interesting discussion. but given that when there are non-empty objects present it does not appear to arise. is it simply an 'academic' corner case of purely theoretical interest? Or perhaps it matters for engraving 4'33' by John Cage. [I believe one version of the score is

Disappearing dynamics

Hi All, I apologize for the seeming lunacy of this post! I am using lilypond 2.19.82 on Ubuntu 18.10. I am currently engraving a string quarter. Only seven or eight pages in, I have started added in the dynamics and I find they just disappear - they don't show. I am simply adding dynamics to the

Re: Disappearing dynamics

Hi k\Kevin and All, It ranks as one of the most bizarre bugs I have ever seen (and I speak as a software developer of many decades). It's only with Frescobaldi. Command line compilation is fine. It's only dynamic markings, which is puzzling - whatever is going on? Running sync of course I tried,

Re: Disappearing dynamics

Hi Carl, Have not tried that idea. The weird thing is that it's only dynamics that are affected. I thought it might be some subtle font caching issue with the font I use, but I reverted to lilypond default and the same occurs. Once the dynamic finally makes itself visible, it stays. This may

Re: Disappearing dynamics

Hi Urs, Thanks for the tip. It just happened with the first dynamic I added on about page seven. Everything fine until then. Having worked as a UNIX professional developer for a very long time, I can tell you something equally lunatic sounding. It has a whiff of being related to file system

Re: Disappearing dynamics

OK. Using a command line compile there is no sign of this issue. At least I can continue with the engraving. This looks not to be a lilypond bug now but an interaction between Frescobaldi and Ubuntu 18.10. In which case it looks like I have to abandon Frescobaldi after all these years. Not

Re: Disappearing dynamics

Hi Urs, Installed Debian 9.5 and all. The error, I am sorry to say, is in Frescobaldi, displayed in Ubuntu 18.10 and Debian 9.5. Using emacs and command line lilypond works fine on both Linux distros. Using Frescobaldi 3.0.0, the dynamics appear only intermittently, with no apparent pattern. I

Lilypond crash related to tuplets

I'm not sure if this is the right list to discuss this on. Recently in my 200 page string quartet the tuplet brackets, which always used to be fine, have started becomg too short, randomly, with no apparent obvious pattern, and only a little bit, but enough to make the score very unprofessional

Re: Lilypond crash related to tuplets

Hi Aaron, I know it would be great to see my code, but the quartet is 11,000 lines long and that's only half, and my library of which I use everything is 13,000 lines of code (for all the New Complexity stuff). I would never expect anybody to go through it, let alone set it all up for compiling.

Re: Lilypond crash related to tuplets

Here it is: Using tupletFullLengthToNote = ##t crashes it. \version "2.19.82" \paper { indent = 0 ragged-right = ##t } \layout { \set tupletFullLength = ##t \set tupletFullLengthNote = ##t } { \tuplet 1/1 { b'1 } \break 4 } That qualifies as a bug worth registering, does it not? Andrew

Re: Lilypond 2.19.82 with multiple voices seems to fail

Hello Dave, We keep seeing this a lot on the various lilypond lists. I don't think anybody really knows why, but having lots of voices coming and going like you have seems to throw errors with the compiler under poorly defined conditions. With the politest respect, can I say this? You are not

Re: Rehearsal mark interferes with TupletBracket length

Hi Mark, No, that's the strange thing. I can't duplicate it in an MWE. If's a string quartet by Chris Dench. You can imagine the density and subtlety of the scoring. There's two hundred pages - hard to give to others to have a look at for debugging! Andrew On Thu, 21 Feb 2019 at 04:22, Mark

Re: Lilypond 2.19.82 with multiple voices seems to fail

Hi Paul, I have not actually said to the OP it is 'wrong', just that it's not a good way to write, as it turns out. I knew somebody would chime in with this exact comment. Fact is, it's completely valid code, and I pointed this out. The issue is that it just causes problems for lilypond in

Re: Lilypond 2.19.82 with multiple voices seems to fail

this is not the best way to enter music. Or something. If the OP is interested, I can recast his score in what I consider a more normal way - it would be very little effort, in order to show how to do it. Andrew On Sun, 3 Mar 2019 at 18:07, James wrote: > Hello, > > On 03/03/2019 01:54, Andrew Bern

Re: Rehearsal mark interferes with TupletBracket length

Hi Harm, Thanks. Fantastic as always. Adding this: \once \override TupletBracket.full-length-to-extent = ##f before the tuplets in the affected bar in each staff works perfectly. This is a great help. Problem with bugs like this is, I always think it is something I have done wrong in my way

Rehearsal mark interferes with TupletBracket length

Using 2.19.82 on Debian 9, my string quartet displays an issue that is hard to understand, and appears to be a defect. Referring to the attached image, the mark makes the tuplet brackets too short in the violin and cello part. I can prove this by adding an X-offset to the RehearsalMark and the

Re: slashedGrace and acciaccatura missing slash for multiple notes

Hi All, To that end, based on code by David Nalesnik and my own work, I wrote some very flexible functions for making slashed stems and slashed beams. You can find i the functions in openlilylib. I have no idea if the code works with 2.18. I only use the 2.19 branch. Andrew On Tue, 19 Feb

Re: The Stem of Longa notes is short when Baroque Notehead style is used

Hi, It's meant to be. That's the baroque style. Isn't it? Andrew On Tue, 29 Jan 2019 at 11:08, Pothárn Imre wrote: > %% The stem length of the longa is very short when Baroque NoteHead style > is > used. > > ___ bug-lilypond mailing list

Re: rest + fermata

Hi Martin, R1^\fermataMarkup It's special. Refer to the NR. Andrew On Sun, 14 Apr 2019 at 21:38, Martin Tarenskeen wrote: > > Hi, > > This is strange: > > %%% start of tiny example > > \version "2.19.83" > { >r1\fermata >R1\fermata > } > > %%% end of tiny example > > r1\fermata

Re: Assertion !is_empty() failed - yet again

Hi David, The reported error was from 2.19.83. But I built 2.21.0 last night, and the error persists. Andrew On Sat, 27 Apr 2019 at 00:56, David Kastrup wrote: > Andrew Bernard writes: > > > Lilypond 2.19.83. > > That one or current master? In the latte

Re: Assertion !is_empty() failed - yet again

ing that should be reported as a bug, so as to eventually get fixed? Andrew On Fri, 26 Apr 2019 at 22:47, David Kastrup wrote: > Andrew Bernard writes: > > > Lilypond 2.19.83. Yet again I see this error: > > > > Drawing systems... > > Finding the ideal number o

Assertion !is_empty() failed - yet again

Lilypond 2.19.83. Yet again I see this error: Drawing systems... Finding the ideal number of pages... Fitting music on 15 or 16 pages... Drawing systems...lilypond: /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-test/flower/include/interval.hh:227: T

Non default tuplet error with 2.21

Using 2.21 from git, the non-default tuplet example in the NR throws an error. \relative c'' {   \once \override TupletNumber.text =     #(tuplet-number::non-default-tuplet-denominator-text 7)   \tuplet 3/2  { c4. c4. c4. c4. }   \once \override TupletNumber.text =    

Re: Fonts on Arch Linux

Hi Carl, Thank you so much for this really useful information. I do wonder what happened to the development of the font. Perhaps just abandoned after ten years or more. Biolinum was an excellent Optima replacement, and I use it a lot. All I can find nowadays is scrappy partial sets of dubious

Lilypond 2.20 and 2.21 crash on Arch Linux

Just getting back into lilypond but nowadays on Arch Linux. Sorry to say both recent versions dump core: ... elapsed time: 0.61 seconds Element count 12833 (spanners 1146) Preprocessing graphical objects... Grob count 19105Segmentation fault (core dumped) Version from Arch AUR repository and Arch

Re: Lilypond 2.20 and 2.21 crash on Arch Linux

Well, it just so happened that the first file I tried on Arch makes lilypond dump core, sheer bad luck. As per the suggestion here (which I didn't even think of, too busy rushing into worrying about this) my other files compile fine. So in fact there is no real issue. I'll binary chop the file to

Re: Fonts on Arch Linux

Thanks Aaron. I didn't give an MWE as it was a preliminary probe to see if this is a known issue. Here's the code in question: #(define fonts (set-global-fonts #:roman "Linux Libertine O" #:sans "Linux Biolinum O" #:typewriter "Linux Libertine Mono O" #:factor (/

Fonts on Arch Linux

More strangeness on Arch Linux. The /paper command set-global-fonts is having no effect, no matter what fonts are specified. I have checked and rechecked font availability. This occurs in 2.20.0 and 2.21.2. I have not tried earlier versions. If I explicitly specify a font name for a markup it

Re: LP v.2.23.13 bin has no executable rights

No criticism of Lilypond, as I trust it to behave, but for me having apps installed as root when not necessary is not a good idea. Just sayin' (lest others copy this pattern from reading this thread). Andrew On 4/10/2022 7:56 am, Jonas Hahnfeld via bug-lilypond wrote: On Mon, 2022-10-03 at

Re: LP v.2.23.13 bin has no executable rights

Oh - sorry for the noise. I thought it was an ls listing. What a dunderhead I am - I did not read carefully enough. Andrew On 4/10/2022 6:06 pm, Jean Abou Samra wrote: The output Jonas shared is from "tar tvf" (list files inside the archive without extracting), so it has nothing to do with

Re: Glitch in the documentation?

Also Catalan for me. Andrew ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Glitch in the documentation?

Not that it is any help, but I recall reporting the same thing about Catalan some years ago. Andrew ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Glitch in the documentation?

Would not appear to be a browser issue. Mine is English on English Windows 11. That page shows Catalan. Andrew ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond