Re: tuplet number on cross-staff kneed-beam

Hi, again -- I've also attached a pared-down version of the file which should work in either release, as is. It distills the problem a little more -- at the expense of centering the number directly on the beam . . . My last email included an image produced with 2.12.3. Attached is the

Re: tuplet number on cross-staff kneed-beam

Hi, Colin -- On 7/5/11, Colin Campbell c...@shaw.ca wrote: This will probably require an issue, David, but could you send the code you used to produce the 2.12.3 version, please? I can't reproduce the previous stable example, in order to confirm the regression, because your Scheme-ing gives

Re: Center a number above a measure

Hi, 2012/3/28 Colin Hall colingh...@gmail.com On Wed, Mar 28, 2012 at 05:02:49PM +0100, James wrote: hello, 2012/3/28 Clément Ryder themu...@gmail.com: ...etc. So it seems that this is really the enhancement request stated before

Re: Center a number above a measure

Hi, 2012/3/28 Colin Hall colingh...@gmail.com On Wed, Mar 28, 2012 at 05:02:49PM +0100, James wrote: hello, 2012/3/28 Clément Ryder themu...@gmail.com: ...etc. So it seems that this is really the enhancement request stated before

Re: Center a number above a measure

Hi Colin, Thanks very much for that, David. I've updated the issue tracker with your post and your engraver. http://code.google.com/p/lilypond/issues/detail?id=2445 Thank you! ___ bug-lilypond mailing list bug-lilypond@gnu.org

lower portion of image cut off in NR examples

Hi, Part of the beam and the leftmost stem is cut off in the lower staff of each of the examples here: http://www.lilypond.org/doc/v2.15/Documentation/notation/displaying-pitches#automatic-accidentals (I notice the same problem in the 2.14.2 documentation --

Re: lower portion of image cut off in NR examples

Keith, On Mon, Apr 16, 2012 at 12:10 AM, Keith OHara k-ohara5...@oco.net wrote: David Nalesnik david.nalesnik at gmail.com writes: Part of the beam and the leftmost stem is cut off in the lower staff of each of the examples here: http://www.lilypond.org/doc/v2.15/Documentation/notation

Re: Feature request: Display bezier control-points

Hi Urs, It would be a really valuable feature if one could let LilyPond display the control-points of a bezier curve. I would imagine something like a cross or a point at the middle two control-points. I think this would be very helpful, so that you can visualize exactly what these

Re: Feature request: Display bezier control-points

On Thu, May 3, 2012 at 7:08 PM, David Nalesnik david.nales...@gmail.comwrote: Hi Urs, It would be a really valuable feature if one could let LilyPond display the control-points of a bezier curve. I would imagine something like a cross or a point at the middle two control-points. I

Re: Feature request: Display bezier control-points

Hi Urs, But this really _is_ helping to find suitable values for the control-points. I'm very glad to hear this! * Although I know bezier curves from vector graphics software, I also was convinced that the 'control-points' were four points on the curve that define its shape.

Re: Feature request: Display bezier control-points

Hi Harm, how about: \version 2.14.2 #(define (make-cross-stencil coords) (ly:stencil-add (make-line-stencil 0.1 (- (car coords) 0.2) (- (cdr coords) 0.2) (+ (car coords) 0.2) (+ (cdr coords) 0.2)) (make-line-stencil 0.1 (- (car coords) 0.2) (+ (cdr coords) 0.2) (+ (car coords)

Re: Staccato alignment on stem side

Hi Urs, On Wed, May 16, 2012 at 4:02 AM, Urs Liska lilyli...@googlemail.com wrote: Am 16.05.2012 10:50, schrieb Colin Hall: Urs Liskalilyliskaat googlemail.com writes: The following example shows that staccato points are aligned differently from other articulations when on the stem

Re: Staccato alignment on stem side

Hi Janek, \layout { \context { \Staff \consists #stacc-corrector } } i wanted to include your engraver in Fried Songs project, but there's an error. Unfortunately i don't have time to debug this problem at the moment, but maybe the error message will give you an idea

Re: Staccato alignment on stem side

Hi Janek, On Tue, May 22, 2012 at 1:01 PM, Janek Warchoł janek.lilyp...@gmail.comwrote: Hi David, On Tue, May 22, 2012 at 7:51 PM, David Nalesnik david.nales...@gmail.com wrote: In procedure string= in expression (string= (ly:prob-property # #) staccato): Wrong type argument

Re: Staccato alignment on stem side

David, script-interface: This grob interface is used in the following graphical object(s): *note AccidentalSuggestion::, *note DynamicText:: and *note Script::. Quite a lot of stuff created without an articulation-type, so you should be using eqv? rather than string= ... Ah, I get

\balloonGrobText does not work properly with slurs

The image shows what happens when \balloonGrobText is used with a slur. Uncommenting the \override demonstrates a possible workaround. I tried this code in 2.14.2 with the same result. \version 2.15.39 \new Voice \with { \consists Balloon_engraver } \relative c'' { % uncommenting the

problem with 'outside-staff-padding

Hi, In the example in the documentation of 2.17.4 relating to 'outside-staff-padding, the last line of text ought to be close to the previous text. Compare: 2.16 - http://www.lilypond.org/doc/v2.16/Documentation/notation/vertical-collision-avoidance 2.17.4 -

Re: \alterBroken doesn't work for properties accessed before line breaking

On Thu, Feb 21, 2013 at 3:02 AM, Colin Hall colingh...@gmail.com wrote: m...@mikesolomon.org writes: If \alterBroken tries to set a property consulted before line breaking, it results in the property having an incorrect value: For example... \relative c'' { \alterBroken

Re: \alterBroken doesn't work for properties accessed before line breaking

Mike, On Thu, Feb 21, 2013 at 7:38 AM, David Nalesnik david.nales...@gmail.comwrote: m...@mikesolomon.org writes: If \alterBroken tries to set a property consulted before line breaking, it results in the property having an incorrect value: For example... \relative c

Re: [Spam??] repeated time signatures

On Mon, Apr 29, 2013 at 11:10 AM, Urs Liska lilyli...@googlemail.comwrote: Am 29.04.2013 17:46, schrieb Trevor Daniels: Urs Liska wrote Monday, April 29, 2013 3:50 PM Am 29.04.2013 16:46, schrieb Trevor Daniels: Urs Liska wrote Monday, April 29, 2013 3:02 PM The NR (1.2.3

Re: repeated time signatures

Urs, On Mon, Apr 29, 2013 at 10:32 AM, Urs Liska u...@openlilylib.org wrote: Hi David, Am 29.04.2013 16:15, schrieb David Nalesnik: Hi Urs, On Mon, Apr 29, 2013 at 9:02 AM, Urs Liska u...@openlilylib.org wrote: b) How can I achieve that the time signature is only printed

Re: [Lilypond] Incorrectly print notes with length 16*7 and 16*5

Hopefully, we're good! On Mon, Oct 28, 2013 at 11:49 AM, Trevor Daniels t.dani...@treda.co.ukwrote: Neither am I :) This output looks correct to me. In the first example you're asking for a g16 to be displayed but for its duration to be 7/16 long followed by a fis16 with duration 5/16,

Re: autochange sends voice to wrong clef

On Sat, Nov 2, 2013 at 11:36 AM, sniv...@catesby.org wrote: % here is a case where autochange weirdly sends the top note to the bass clef, using lots of ledger lines version 2.16.0 score { new PianoStaff new Staff = up { new Voice { voiceOne autochange relative c'' {

Re: beams look ugly when using \autochange

On Wed, Nov 6, 2013 at 1:32 PM, Gilberto Agostinho gilbertohasn...@gmail.com wrote: When using \autochange, the slope of the beams look ugly against the staff lines: It's not specifically a problem with \autochange. You get the same behavior with manual staff changes: up = \change Staff =

broken horizontal brackets don't clear prefatory material

In the following snippet, there is a collision between the broken analysis bracket and the clef (see image): \version 2.17.97 { c''1\startGroup \break c''1\stopGroup } \layout { ragged-right = ##t \context { \Voice \consists Horizontal_bracket_engraver } }

Re: Define custom/new \accidentalStyles (dodecaphonic minus repeated notes)

Hi Urs, On Mon, Feb 3, 2014 at 3:16 AM, Urs Liska u...@openlilylib.org wrote: Hi, searching the docs and the lilypond-user archive I couldn't find any relevant information. I am looking for a custom \accidentalStyle. Actually I think this is quite commonly used, so it would also seem

Re: [LSR-2.18] Affecting items only on the left or rigth... needs update.

Hi Pierre, On Wed, Feb 12, 2014 at 12:04 PM, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote: Hi All, Hi Harm, I'm stucked whith your snippet : http://lsr.dsi.unimi.it/LSR/Item?id=775 again (equal? (ly:music-property m 'name) 'EventChord)... I'm not sure what problem you

Re: \fill-line while respecting natural widths

Hi, On Mon, Feb 10, 2014 at 1:26 PM, James pkx1...@gmail.com wrote: Hello, Browsing through the user threads I came across the recent thread http://lilypond.1069038.n5.nabble.com/fill-line-while-respecting-natural-widths-td158967.html and created

Re: [LSR v2.18] Slashed beamed grace notes enhancement proposal

Hi Pierre, On Thu, Feb 20, 2014 at 6:51 AM, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote: Hi Bug Squad, Enhancement for the following snippet : http://lsr.di.unimi.it/LSR/Item?id=721 has been disscussed here:

Re: [LSR v2.18] Complex compound time signatures modif

Hi Pierre, On Mon, Feb 24, 2014 at 6:59 AM, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote: Dear Bug Squad, See the following snippet : http://lsr.di.unimi.it/LSR/Item?id=743 Since defining compoundMeter is not needed anymore shall I erease the definition lines ? In

Re: mark running into margin

Simon, On Sun, Mar 9, 2014 at 7:45 PM, Simon Albrecht simon.albre...@mail.dewrote: Hello, lenghty \marks which are at the beginning of a line tend to run into the margin or even out of the page. It would be nice to make the center-alignment more flexible and move the mark so that it stays

Re: example is not working

Oliver, On Tue, Apr 1, 2014 at 7:36 AM, Oliver Sanftleben oliver.sanftle...@berlin.de wrote: Hello, In LM 2.1.7 (german section: Andere rhythmische Aufteilungen), the example is not working. I think\tuplet 3/2 should be replaced by\times 2/3 What version are you running? It looks like

Re: How to catch extent of AccidentalPlacement?

Hi Harm, On Sun, Mar 16, 2014 at 7:06 AM, Thomas Morley thomasmorle...@gmail.comwrote: 2014-03-12 1:27 GMT+01:00 Thomas Morley thomasmorle...@gmail.com: Hi, for some function I need to know the extent/length of the AccidentalPlacement. With 2.16.2 I used to do something like:

Re: How to catch extent of AccidentalPlacement?

Hi Harm, On Sat, Apr 12, 2014 at 4:53 PM, Thomas Morley thomasmorle...@gmail.comwrote: One question remains: why was it changed? Instead of more or less simply calling the vallue via ly:grob-extent we now have to calculate it, looking at each Accidental separately. (via map and reduce)

Re: How to catch extent of AccidentalPlacement?

On Mon, Apr 14, 2014 at 8:53 AM, David Nalesnik david.nales...@gmail.comwrote: I can't figure out where that 1.1 comes from, though. This happens in accidental-placement.cc. It's the value of width calculated in position_apes. Looks like it doesn't factor in the offsets to the accidentals

Re: How to catch extent of AccidentalPlacement?

Harm, On Mon, Apr 14, 2014 at 12:07 PM, David Nalesnik david.nales...@gmail.comwrote: On Mon, Apr 14, 2014 at 8:53 AM, David Nalesnik david.nales...@gmail.comwrote: I can't figure out where that 1.1 comes from, though. This happens in accidental-placement.cc. It's the value of width

Re: How to catch extent of AccidentalPlacement?

Hi Harm, On Fri, Apr 18, 2014 at 8:49 AM, Thomas Morley thomasmorle...@gmail.comwrote: thanks for all your work you've put on this. I'm ashamed I didn't try it out so far. I hope I can find the time to do it the next days. No problem. If you don't get a chance to look at it, no worries!

Re: doc modification

On Wed, Jun 25, 2014 at 3:02 PM, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote: Hi, This thread : http://lilypond.1069038.n5.nabble.com/Positioning-spanner-at-different-height-after-line-break-td163618.html made me think that maybe it would be good to find another example

Re: doc modification

James, On Thu, Jun 26, 2014 at 2:23 AM, James pkx1...@gmail.com wrote: On 26/06/14 00:33, David Nalesnik wrote: On Wed, Jun 25, 2014 at 3:02 PM, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote: Hi, This thread : http://lilypond.1069038.n5.nabble.com/Positioning

Re: doc modification

On Thu, Jun 26, 2014 at 7:49 AM, David Nalesnik Not sure why. Attached is my result, where the tie is there (Win7, 64-bit). In any case, the altered code is equivalent to \alterBroken extra-offset #'((0 . 0) (-2 . 5)) Tie so I can't understand why it wouldn't work as expected. --David

Re: doc modification

Hi James, On Thu, Jun 26, 2014 at 4:14 PM, James pkx1...@gmail.com wrote: [...] What I have found is that if you use lilypond-book (which is what the documentation uses) I don't get the expected output but with lilypond in a *.ly file I do. If you are unfamiliar with how doc works in

Re: accidentalStyle dodecaphonic-no-repeat

On Sat, Jul 5, 2014 at 12:24 PM, James pkx1...@gmail.com wrote: Thanks http://code.google.com/p/lilypond/issues/detail?id=3992 James I've figured out the problem, but I'd like to revise the dodecaphonic-no-repeat code a little while I'm at it. I've added some comments and an image to the

Accidentals on repeated notes separated by rests in certain styles

Certain accidental styles suppress accidentals on immediately repeated notes. (These styles are neo-modern, neo-modern-cautionary, neo-modern-voice, neo-modern-voice-cautionary, and dodecaphonic-no-repeat.) When a pitch repetition occurs across a rest, however, the accidental is repeated: as an

accidentals on note overlaps

Hi, In the following example, the half-note F# counts as an immediate repetition and should not get an accidental in neo-modern and neo-modern-cautionary styles, This issue is seen in the documentation at

Re: accidentals on note overlaps

On Mon, Jul 14, 2014 at 7:39 PM, David Nalesnik david.nales...@gmail.com wrote: Hi, In the following example, the half-note F# counts as an immediate repetition and should not get an accidental in neo-modern and neo-modern-cautionary styles, This issue is seen in the documentation at http

Re: Accidentals on repeated notes separated by rests in certain styles

-- Forwarded message -- From: guoguocuozuoduo brian777...@hotmail.com Date: Tue, Jul 15, 2014 at 12:13 AM Subject: RE: Accidentals on repeated notes separated by rests in certain styles To: David Nalesnik david.nales...@gmail.com There should be for neo-modern, neo-modern

Re: Accidentals on repeated notes separated by rests in certain styles

On Tue, Jul 15, 2014 at 6:52 AM, David Kastrup d...@gnu.org wrote: So what about { { fis'8 r8 r4 r4 r8 fis'8 } \\ { r8 cis'8 f' r2 } } ? I think you mean { fis'8 r8 r4 r4 r8 fis'8 } \\ { r8 cis'8 f' r2 } Should neo-modern-voice really consider the second fis'8 a repetition of the

Re: Accidentals on repeated notes separated by rests in certain styles

On Tue, Jul 15, 2014 at 7:04 AM, David Nalesnik david.nales...@gmail.com wrote: On Tue, Jul 15, 2014 at 6:52 AM, David Kastrup d...@gnu.org wrote: So what about { { fis'8 r8 r4 r4 r8 fis'8 } \\ { r8 cis'8 f' r2 } } ? I think you mean { fis'8 r8 r4 r4 r8 fis'8 } \\ { r8 cis'8 f

cross-staff bug?

Hi, Attempting to put dynamics above cross-staff notes using the code below leads to some awful collisions. I've recast my example in three ways, to no avail. In the first example, besides the collisions, the final stem is reversed and I get a number of programming errors: Grob direction

self-alignment-X has negligible effects on dynamics

In the following example, the ordinary overrides of self-alignment-X appear to have no effect on the position pf the dynamics (or an effect I can't see). Large numbers are needed for an obvious shift. Is this a bug, or something I'm doing wrong? \version 2.19.10 { \override

Re: self-alignment-X has negligible effects on dynamics

On Mon, Jul 28, 2014 at 9:25 AM, Noeck noeck.marb...@gmx.de wrote: Your snippet produces a different output here with 2.19.8 (i.e. more like what I would expect) Yup--and you get the same with 2.19.9. ___ bug-lilypond mailing list

Re: self-alignment-X has negligible effects on dynamics

On Mon, Jul 28, 2014 at 3:17 PM, Janek Warchoł janek.lilyp...@gmail.com wrote: Hi, 2014-07-28 16:13 GMT+02:00 David Nalesnik david.nales...@gmail.com: In the following example, the ordinary overrides of self-alignment-X appear to have no effect on the position pf the dynamics

Re: self-alignment-X has negligible effects on dynamics

Hi Janek, On Mon, Jul 28, 2014 at 4:12 PM, Janek Warchoł janek.lilyp...@gmail.com wrote: Hi, 2014-07-28 22:51 GMT+02:00 David Nalesnik david.nales...@gmail.com: What is potentially confusing (and you see how badly I've been confused) is that the default setting of X-offset has changed

Re: New feature suggestion

On Sat, Aug 23, 2014 at 11:57 AM, David Kastrup d...@gnu.org wrote: David Winfrey d...@patriot.net writes: Keith OHara k-ohara5a5a at oco.net writes: Phil Holmes mail at philholmes.net writes: But if you enter b4 in F major, you'll get a natural typeset, so there can be no

Re: New feature suggestion

On Tue, Aug 26, 2014 at 2:11 AM, Keith OHara k-ohara5...@oco.net wrote: David Nalesnik david.nalesnik at gmail.com writes: In the US, I hear people calling c-sharp c often enough. This usage is certainly not good practice in music theory classes (where I correct it whenever I can). I

Re: New feature suggestion

On Tue, Aug 26, 2014 at 8:41 PM, Dan Eble d...@faithful.be wrote: Knute Snortum ksnortum at gmail.com writes: Just my two cent's worth: Adding an n modifier isn't saying that C Sharp is C Natural, it's an assertion. Yes, I really mean natural. No, I didn't just forget the sharp.

Broken TextSpanner does affect horizontal spacing

In the following snippet, horizontal spacing is not stretched to fit the broken spanner with long text on its second line. It may be that proper accommodation requires at least one bound of TextSpanner to be set to NoteColumn. In the snippet, one of the bounds of the sibling on either the first

Re: Broken TextSpanner does affect horizontal spacing

, NonMusicalPaperColumn for broken. The middle line has NonMusicalPaperColumn as both bounds. On Mon, Oct 20, 2014 at 11:43 AM, David Nalesnik david.nales...@gmail.com wrote: In the following snippet, horizontal spacing is not stretched to fit the broken spanner with long text on its second line

Re: empty markup causes text overlapping in lilypond 2.17

Hi Eugene, You could substitute \markup \null for \markup { } Alternatively, you could use \markup \vspace #1 (or whatever value). I'm not sure that it is a bug--the notation says to me make no markup, whatever LilyPond did in the past. Anyway, for the purposes of the bug list, you should

Re: empty markup causes text overlapping in lilypond 2.17

Eugene, On Tue, Oct 21, 2014 at 12:12 PM, Eugene Cormier eugenecorm...@gmail.com wrote: David Kastrup dak at gnu.org writes: Without anything suitable for reproducing the problem, this is sort of anecdotal knowledge which severely reduces the chances of somebody actually working on it.

Re: Bug in \offset with Fingering.font-size?

On Sat, Nov 1, 2014 at 4:34 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Should \offset work with the font-size of fingering? It doesn't seem to. The default value is -5, so offsetting by -2 should give -7, with a size as shown by the \override and \tweak, but both forms of \offset give 0.

Re: Bug in \offset with Fingering.font-size?

On Sat, Nov 1, 2014 at 4:56 PM, Trevor Daniels t.dani...@treda.co.uk wrote: David Nalesnik wrote Saturday, November 01, 2014 9:46 PM On Sat, Nov 1, 2014 at 4:34 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Should \offset work with the font-size of fingering? It doesn't seem

Re: Bug in \offset with Fingering.font-size?

On Sat, Nov 1, 2014 at 5:29 PM, Trevor Daniels t.dani...@treda.co.uk wrote: David Nalesnik wrote Saturday, November 01, 2014 9:46 PM On Sat, Nov 1, 2014 at 4:34 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Should \offset work with the font-size of fingering? It doesn't seem

Re: Bug in \offset with Fingering.font-size?

On Sat, Nov 1, 2014 at 6:21 PM, Trevor Daniels t.dani...@treda.co.uk wrote: David Nalesnik wrote Saturday, November 01, 2014 10:53 PM To work, \offset needs access to a default value--a number, number-pair, or list of number-pairs--or a default procedure to calculate these values

Re: Bug in \offset with Fingering.font-size?

On Sat, Nov 1, 2014 at 6:53 PM, David Nalesnik david.nales...@gmail.com wrote: Actually, it might not be hard to enhance \offset to deal with Script. The defaults aren't stored in define-grobs, rather they're in script.scm. I'll look into that. The defaults are available, yes, but then we

Re: Place objects by hand

Hi, On Sun, Nov 2, 2014 at 6:23 AM, Trevor Daniels t.dani...@treda.co.uk wrote: Noeck wrote Sunday, November 02, 2014 12:46 AM That would be nice, but your example puts the f on the left of the upper note and not centralized between the staves (I am using 2.19.15). You're right, Joram,

Re: Place objects by hand

On Sun, Nov 2, 2014 at 6:55 AM, Trevor Daniels t.dani...@treda.co.uk wrote: David, you wrote Sunday, November 02, 2014 12:44 PM No, it's not a problem with \offset. Substitute this for the call to \offset, and you'll see that it's actually an issue with X-offset here: \once

Re: Place objects by hand

Hi again, On Sun, Nov 2, 2014 at 7:08 AM, David Nalesnik david.nales...@gmail.com wrote: Offsetting arpeggio.positions is nice, I think. (Though not precise; there is quantization which unavoidably kicks in, I think. It's still nice for arpeggios across tiny intervals, where you don't want

Re: lyrics extender and acciaccatura

Hi Jean-Charles, On Tue, Nov 11, 2014 at 9:00 AM, Jean-Charles Malahieude lily...@orange.fr wrote: Hi all, Trying to align a syllable to acciaccaturas, I came across an extender problem: The extender should stop *before* the rest, not when encountering the next acciaccatura. The problem

Re: lyrics extender and acciaccatura

On Tue, Nov 11, 2014 at 9:53 AM, David Nalesnik david.nales...@gmail.com wrote: Hi Jean-Charles, The problem I see here is that the X-parent of the LyricText is being set to the NoteColumn of main note rather than to the grace note. (Perhaps that's desirable?) This doesn't work: \new

Re: lyrics extender and acciaccatura

On Tue, Nov 11, 2014 at 10:22 AM, David Kastrup d...@gnu.org wrote: Not much of a surprise here. \new Staff \new Voice = music { \grace c'8 } \new Lyrics \with { includeGraceNotes = ##t } \lyricsto music { hi } Ah, OK. That's the solution to Jean-Charles's problem. --David

Re: lyrics extender and acciaccatura

On Tue, Nov 11, 2014 at 10:28 AM, David Nalesnik david.nales...@gmail.com wrote: Ah, OK. That's the solution to Jean-Charles's problem. Nevertheless, it seems that what he describes is a bug. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: LSR : Dashed slurs indicating optional slurs between lyric lines

Hi Pierre, On Wed, Nov 12, 2014 at 7:57 AM, Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote: Hi Squad, In this snippet : http://lsr.di.unimi.it/LSR/Item?id=308 the slur is to low. So I'd like to slightly change it to : [...] Any objection ? Looks a lot better to me.

Re: Retrieving information about breaks

Urs, On Fri, Jan 23, 2015 at 11:17 AM, Urs Liska u...@openlilylib.org wrote: Hi David, thanks, that works great. It did *not* write to a file, but that's not the issue here. The main point is that it listens to implicit break events. The only time it doesn't write to a file for me is

Re: Retrieving information about breaks (was: Partial compilation (again))

at which positions (in terms of barnumber and measure-position) the final line breaks, page breaks and page turns have been placed in LilyPond? I'm sure this information has to be present at one point, but someone (I think it may have been David Nalesnik) expressed the opinion that engravers could

faulty interaction of line-width and minimum-length in spanners

Hi, In the following snippet, the music runs right off the page. Clearly, the setting of line-width is not respected. Probably, it should be minimum-width that is ignored or adjusted along with an error being thrown. %%% \paper { line-width = 50\mm } { \override Tie.minimum-length =

Re: Problem with enharmonic tie in partcombine (can let LilyPond crash)

Hi Urs, On Fri, Jan 16, 2015 at 6:01 AM, Urs Liska u...@openlilylib.org wrote: Hi, I encountered a strange crash that is related to enharmonic ties. I'm using an engraver that is passed a grob. One particular snippet of input code lets now crash LilyPond. I can't easily produce a

allow changes of scripts by type

Hi, It is a common request to be able to change the defaults of specific scripts globally. An example would be changing the padding and font-size of tenuto throughout a file. Currently, the user needs to tweak each instance of the right Script, a process that is tedious and error-prone. There

Re: Enhancement: command line option to transpose N halftones up or down

Hi Michael, Am 16.03.2015 um 15:02 schrieb Michael Schuerig: I've only been using LilyPond for a rather short time, so far mostly for engraving short snippets transposed into several keys for practicing. Of course, the transpose command works nicely for this. However, it made me think

Re: staffSize music function unreliable at LP v2.19.16

On Tue, Mar 3, 2015 at 4:35 PM, Simon Albrecht simon.albre...@mail.de wrote: Well, there’s reason enough to redirect this to bug-lilypond, isn’t it? Somehow, Mozilla Thunderbird messes up the code examples, so I can’t do so well. Perhaps the OP’s and Harm’s first mails in the thread,

Re: Hairpin flared + circled-tip won't work together.

Hi Karim, On Wed, Aug 19, 2015 at 11:01 AM, Karim Haddad karim.had...@ircam.fr wrote: Hello list, I hope this issue is not reported. If it is sorry to post it again : https://code.google.com/p/lilypond/issues/detail?id=3357 in this example : \version 2.19.25 { \override

Re: Patch/issue procedures (was: Randomness in layout)

David, On Sat, Aug 22, 2015 at 2:24 AM, David Kastrup d...@gnu.org wrote: David Nalesnik david.nales...@gmail.com writes: [Patch] Maybe put it up on Rietveld and post a pointer on bug-lilypond? Even when it does not make all that much sense to create a new Google issue for it, my

Re: Patch/issue procedures (was: Randomness in layout)

On Sat, Aug 22, 2015 at 6:00 PM, David Nalesnik david.nales...@gmail.com wrote: David, On Sat, Aug 22, 2015 at 2:24 AM, David Kastrup d...@gnu.org wrote: David Nalesnik david.nales...@gmail.com writes: [Patch] Maybe put it up on Rietveld and post a pointer on bug-lilypond? Even when

Re: Vertical alignment - programming error

Hi Andrew, On Mon, Oct 26, 2015 at 3:41 AM, Andrew Bernard wrote: > 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

Re: Vertical alignment - programming error

On Mon, Oct 26, 2015 at 10:23 AM, David Nalesnik <david.nales...@gmail.com> wrote: > > > A more minimal example triggers the warning with TimeSignature: > Two with TimeSignature, one with Clef. ___ bug-lilypond mailing list bug-lily

Re: Broken horizontal brackets do not avoid treble clef

Hi Mike, On Tue, Sep 8, 2015 at 11:57 PM, Mike Solomon wrote: > \version "2.19" > > % broken horizontal bracket intersects with bottom of treble clef > This has already been reported as Issue 3759: https://sourceforge.net/p/testlilyissues/issues/3759/ What about moving

Re: crescendo & decrescendo marks not end correctly

Hi, On Wed, Dec 30, 2015 at 9:54 PM, Fan Hongtao wrote: > When I write note of Bach's Minuet, I find that LilyPond do not write > crescendo & decrescendo mark the way I want. > > With beams 21~ 24, I write something like : > > a8([\< b] cis[ d] e fis | > g4)\! fis-.

Re: Make flared hairpins work with the circled-tip property

Hi, On Wed, Apr 6, 2016 at 2:47 PM, Simon Albrecht wrote: > Hi Trevor, > > that’s a known deficiency: > > < > https://sourceforge.net/p/testlilyissues/issues/search/?q=flared+%26%26+niente > > > > Best, > Simon > > Note that a workaround is attached to the issue. David

Re: alterBroken and ties

Hi Simon, On Thu, Oct 6, 2016 at 4:58 PM, Simon Albrecht wrote: > On 06.10.2016 23:46, Simon Albrecht wrote: >> >> Hello, >> >> in the following snippet >> >> %%% >> \version "2.19.47" >> { >> 1-\alterBroken color #'(black red) ~ \break >> 1 >> } You can't

Re: TupletBracket.shorten-pair with strange output

Harm, On Sun, Apr 9, 2017 at 1:53 PM, Thomas Morley wrote: > The following gives strange output, see attached. > > \version "2.19.58" > > { > \override TupletBracket.shorten-pair = #'(10 . 0) > \tuplet 1/1 { > c'1 c'1 > } > } > > I would have

Re: TupletBracket.shorten-pair with strange output

On Mon, Apr 10, 2017 at 8:39 AM, Thomas Morley <thomasmorle...@gmail.com> wrote: > 2017-04-10 15:28 GMT+02:00 David Nalesnik <david.nales...@gmail.com>: >> Harm, >> >> On Sun, Apr 9, 2017 at 5:30 PM, Thomas Morley <thomasmorle...@gmail.com> >>

Re: TupletBracket.shorten-pair with strange output

On Mon, Apr 10, 2017 at 8:39 AM, Thomas Morley <thomasmorle...@gmail.com> wrote: > 2017-04-10 15:28 GMT+02:00 David Nalesnik <david.nales...@gmail.com>: >> Harm, >> >> On Sun, Apr 9, 2017 at 5:30 PM, Thomas Morley <thomasmorle...@gmail.com> >>

Re: NR 5.3.6 The \offset command: confusion in describing the examples

On Wed, Jun 7, 2017 at 9:00 AM, Federico Bruni <f...@inventati.org> wrote: > Il giorno mer 7 giu 2017 alle 15:57, David Nalesnik > <david.nales...@gmail.com> ha scritto: >> >> Ah, OK -- that too!! (Maybe I ought to make this clearer in the >> explanation: the

Re: Tweaking Hairpin shape

Hi Stefano, On Thu, Feb 8, 2018 at 4:43 PM, Stefano Troncaro wrote: > Hello again! > > I managed to modify David's translation of ly:hairpin::print to have it use > two properties, Hairpin.rotate and Hairpin.straight-end, to achieve almost > all the results I wanted.

Re: Tweaking Hairpin shape

Hi Stefano, On Sun, Feb 11, 2018 at 3:44 PM, Stefano Troncaro wrote: > I managed to fix it. The problem was not with the calculation of the angle, > it was with the translation of the angle to the offset that the function > applies to the vertical placement of the

Re: Tweaking Hairpin shape

Hi Stefano, On Sat, Feb 10, 2018 at 11:14 AM, Stefano Troncaro wrote: > Hi David, thank you for your suggestions, this is almost done! > > I decided to pass an alist to the function instead of changing the amount of > arguments based on the procedure name, mainly