Re: Accidental spacing with tied note, issue 612

2022-04-16 Thread Knute Snortum
On Sat, Apr 16, 2022 at 8:04 AM Jean Abou Samra wrote: > > > > Le 16/04/2022 16:55, Knute Snortum a écrit : > > > > > > I have run into a LilyPond issue [1] where the accidental spacing is > > wrong when there is a tie to the next measure. This is my tiny > > example (and there's a good one in th

Re: Accidental spacing with tied note, issue 612

2022-04-16 Thread Jean Abou Samra
> Le 16/04/2022 16:55, Knute Snortum a écrit : > > > I have run into a LilyPond issue [1] where the accidental spacing is > wrong when there is a tie to the next measure. This is my tiny > example (and there's a good one in the issue, too): > > %%% > \version "2.22.2" > > \relative { > \clef

Re: accidental spacing (multiple signs): X-extent and ly:accidental-interface::width

2009-09-09 Thread Carl Sorensen
On 9/8/09 3:21 PM, "Torsten Anders" wrote: > Hello Lilyponders, > > I am still looking for a way to avoid collisions of accidentals > consisting of multiple signs. I searched various sources including the > Internals Reference and finally came across the accidental slot/ > property X-extent (

Re: accidental spacing (multiple signs): X-extent and ly:accidental-interface::width

2009-09-09 Thread Kieren MacMillan
Hi Torsten, - What exactly does this pair of numbers mean? Why are there two values to specify the width of a graphical object? From the grob-interface doc page: "Each grob has a reference point (a.k.a. parent): the position of a grob is stored relative to that reference point." Altho

Re: accidental spacing issue

2008-12-16 Thread Jonathan Kulp
Neil Puttock wrote: 2008/12/17 Jonathan Kulp : I still want the a-sharp to appear in the 2nd measure, but don't want the space occupied by the c-sharp. Using this "no-reset" workaround, the a-sharp disappears, too. Is there a way to apply this style using \override instead of "set"? if so th

Re: accidental spacing issue

2008-12-16 Thread Neil Puttock
2008/12/17 Jonathan Kulp : > I still want the a-sharp to appear in the 2nd measure, but don't want the > space occupied by the c-sharp. Using this "no-reset" workaround, the > a-sharp disappears, too. Is there a way to apply this style using \override > instead of "set"? if so then I could prob

Re: accidental spacing issue

2008-12-16 Thread Kieren MacMillan
Hi Jonathan, This was promising but didn't solve the problem because it also made the accidentals in the other voice disappear. Here's the context: Maybe the modified snippet (included below) will solve your problem? HTH, Kieren. %% \version "2.11.65" \new Staff \relative c'' {

Re: accidental spacing issue

2008-12-16 Thread Jonathan Kulp
Neil Puttock wrote: Hi Jon, 2008/12/16 Jonathan Kulp : Is there a way to make the invisible sharp symbol take up no space so that the whole chord moves to the left where it ought to be? There's a workaround for this mentioned in the bug tracker for issue #612. Regards, Neil This was prom

Re: accidental spacing issue

2008-12-16 Thread Neil Puttock
Hi Jon, 2008/12/16 Jonathan Kulp : > Is there a way to make the invisible sharp symbol take up no space so that > the whole chord moves to the left where it ought to be? There's a workaround for this mentioned in the bug tracker for issue #612. Regards, Neil __

Re: accidental spacing

2007-01-25 Thread yota moteuchi
sorry ;p Lilypond 2.11.13 hairpin minimum-length seems to work perfectly... thank you again, your are ... very reliable ^^ Yota On 1/25/07, Mats Bengtsson <[EMAIL PROTECTED]> wrote: Please always tell what LilyPond version you use. When I try your example with version 2.10.0, I certainly get

Re: accidental spacing

2007-01-25 Thread Mats Bengtsson
Please always tell what LilyPond version you use. When I try your example with version 2.10.0, I certainly get an added spacing between the two notes. However, if your main purpose is to get a longer hairpin, why not follow the instructions in the section on Dynamics in the manual: \override V

Re: accidental spacing/placement issue

2003-10-26 Thread David Raleigh Arnold
On Sunday 26 October 2003 07:49 am, Kieren Richard MacMillan wrote: > Hello, Graham: > > Does it look very bad to you? > > Yes, I find it stands out as looking "sloppy". > > Here's an example of what I think it *should* look like (untweaked as > engraved by Igor Engraver v1.7): I thought chromatic

Re: accidental spacing/placement issue

2003-10-26 Thread Kieren Richard MacMillan
Hello, Graham: Does it look very bad to you? Yes, I find it stands out as looking "sloppy". Here's an example of what I think it *should* look like (untweaked as engraved by Igor Engraver v1.7): <> Note how the top and bottom accidentals align (without touching), and how much "cleaner" the re

Re: accidental spacing/placement issue

2003-10-25 Thread Graham Percival
On Mon, 20 Oct 2003 21:35:56 -0400 Kieren Richard MacMillan <[EMAIL PROTECTED]> wrote: > I seem to be running into a situation where accidentals are not > spacing quite right. > > Here is the input: > r | r It looks good to me -- if you move the sharp over to be directly under the natural sig