Re: \parenthesize collision with dots

2013-12-17 Thread Urs Liska
Am 18.12.2013 07:15, schrieb Mike Solomon: On Dec 18, 2013, at 1:00 AM, Urs Liska wrote: If I parentesize a dotted note with { \parenthesize f'2. } the right paren collides with the dot. Urs Do you want the dot to shift to avoid the collision or the parenthesis to encompass the dot? Chee

Re: \parenthesize collision with dots

2013-12-17 Thread Mike Solomon
On Dec 18, 2013, at 1:00 AM, Urs Liska wrote: > If I parentesize a dotted note with > > { \parenthesize f'2. } > > the right paren collides with the dot. > > Urs Do you want the dot to shift to avoid the collision or the parenthesis to encompass the dot? Cheers, MS _

\parenthesize collision with dots

2013-12-17 Thread Urs Liska
If I parentesize a dotted note with { \parenthesize f'2. } the right paren collides with the dot. Urs <>___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: website: why removing lilypond distro package?

2013-12-17 Thread Ralph Palmer
On Mon, Dec 16, 2013 at 6:22 PM, Federico Bruni wrote: > http://lilypond.org/website/unix.html > Maybe we could change the sentence to: > > """ > Generic Packages or Distribution-Specific Packages? > Many distributions include LilyPond in their normal package system. These > versions are easier t

Re: Spacing/collision behaviour of NullVoice

2013-12-17 Thread Carl Peterson
On Tue, Dec 17, 2013 at 6:16 AM, David Kastrup wrote: > "Trevor Daniels" writes: > >> Urs, you wrote Tuesday, December 17, 2013 10:50 AM >> >>> What about changing that to >>> "For example, arbitrary notes in the NullVoice may arbitrarily move >>> rests or cause accidentals to appear (or disappea

Re: Spacing/collision behaviour of NullVoice

2013-12-17 Thread David Kastrup
"Trevor Daniels" writes: > Urs, you wrote Tuesday, December 17, 2013 10:50 AM > >> What about changing that to >> "For example, arbitrary notes in the NullVoice may arbitrarily move >> rests or cause accidentals to appear (or disappear) on the staff." >> ? > > I see David's already had some thou

Re: Spacing/collision behaviour of NullVoice

2013-12-17 Thread Urs Liska
Am 17.12.2013 12:09, schrieb Trevor Daniels: Urs, you wrote Tuesday, December 17, 2013 10:50 AM What about changing that to "For example, arbitrary notes in the NullVoice may arbitrarily move rests or cause accidentals to appear (or disappear) on the staff." ? I see David's already had some

Re: Spacing/collision behaviour of NullVoice

2013-12-17 Thread Trevor Daniels
Urs, you wrote Tuesday, December 17, 2013 10:50 AM > What about changing that to > "For example, arbitrary notes in the NullVoice may arbitrarily move > rests or cause accidentals to appear (or disappear) on the staff." > ? I see David's already had some thoughts about this and has raised an is

Re: Spacing/collision behaviour of NullVoice

2013-12-17 Thread Urs Liska
Am 17.12.2013 11:16, schrieb Trevor Daniels: Urs Liska wrote Tuesday, December 17, 2013 9:01 AM However I noticed a behaviour I wouldn't have expected: Try out the following snippet: soprano = \relative c' { c e g c } verse = \lyricmode { This is my song } \score { \new Staff << %\

Re: Spacing/collision behaviour of NullVoice

2013-12-17 Thread Trevor Daniels
Urs Liska wrote Tuesday, December 17, 2013 9:01 AM > However I noticed a behaviour I wouldn't have expected: > > Try out the following snippet: > > soprano = \relative c' { c e g c } > verse = \lyricmode { This is my song } > > \score { > \new Staff << > %\soprano > { \oneVoice r4.

Spacing/collision behaviour of NullVoice

2013-12-17 Thread Urs Liska
Having a look at the Changes page referenced by Federico I wanted to experiment with the example for the new NullVoice. I thought it might be useful to add a different kind of example with a different rhythm for visible notes and lyrics. However I noticed a behaviour I wouldn't have expected:

Re: Missing notes after lyrics end: bug?

2013-12-17 Thread Eluze
David Kastrup wrote > James < > pkx166h@ > > writes: > Removing \lyricsto restores the missing notes, so as a work-around, given you have just one bar, remove \lyricsto and enter the duration of each syllable explicitly. >> >> Or did this user have a problem because it wasn't