Issue 22 in lilypond: collision tuplet number and staff with increased spacing

2008-01-27 Thread codesite-noreply
Issue 22: collision tuplet number and staff with increased spacing http://code.google.com/p/lilypond/issues/detail?id=22 Comment #2 by horndude77: This issue might have been fixed. At least the example seems fixed. I just tried it with 2.11.37 and the '3' is now placed in the top space between t

Re: \times -> \tuplet (was Re: Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn)

2008-01-27 Thread Hans Aberg
On 27 Jan 2008, at 15:38, John Mandereau wrote: Note the difference: \times 3/4 {...} means a quadruplet, though in music, it would be more natural to write \tuplet 4/3 {...} or \tuplet 4:3 {...} (I think this may make a difference in some more complex situations, but I do not recall

Issue 564 in lilypond: \setEasyHeads -> \beginEasyHeads. Add \endEasyHeads

2008-01-27 Thread codesite-noreply
Issue 564: \setEasyHeads -> \beginEasyHeads. Add \endEasyHeads http://code.google.com/p/lilypond/issues/detail?id=564 Comment #3 by john.mandereau: Changed to \easyHeadsOn, and added \easyHeadsOff. Issue attribute updates: Status: Fixed Labels: fixed_2_11_38 -- You received th

Issue 563 in lilypond: rename: \fatText -> \textLengthOn

2008-01-27 Thread codesite-noreply
Issue 563: rename: \fatText -> \textLengthOn http://code.google.com/p/lilypond/issues/detail?id=563 Comment #5 by john.mandereau: Changed to \textLength{On,Off}. Issue attribute updates: Status: Fixed Labels: fixed_2_11_38 -- You received this message because you are listed in

Re: Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn

2008-01-27 Thread Francisco Vila
2008/1/27, Hans Aberg <[EMAIL PROTECTED]>: > So, one possibility would be to keep \times for backwards > compatibility, adding \tuplet with the numbers reversed. IMOP this is the mos sensible and wise. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org __

Issue 564 in lilypond: \setEasyHeads -> \beginEasyHeads. Add \endEasyHeads

2008-01-27 Thread codesite-noreply
Issue 564: \setEasyHeads -> \beginEasyHeads. Add \endEasyHeads http://code.google.com/p/lilypond/issues/detail?id=564 Comment #2 by wbsoft: Yes, \easyHeadsOn and -Off are imho VERY nice, even better than \startEasyHeads and \stopEasyHeads (or \begin- , \end- ). -- You received this message

Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn

2008-01-27 Thread codesite-noreply
Issue 566: showStaffSwitch -> \staffSwitchOn http://code.google.com/p/lilypond/issues/detail?id=566 Comment #4 by wbsoft: I have no problem at all with \hideStaffSwitch and \showStaffSwitch. regarding \unhideNotes: \showNotes would also be nice. The verb (the action) is at the beginning, just li

Issue 563 in lilypond: rename: \fatText -> \textLengthOn

2008-01-27 Thread codesite-noreply
Issue 563: rename: \fatText -> \textLengthOn http://code.google.com/p/lilypond/issues/detail?id=563 Comment #4 by wbsoft: replying to self: \keepTextWidth (or \keepTextLength) is also nice. However, when really striving for a uniform command naming scheme, I could very well live with \textLengt

Issue 563 in lilypond: rename: \fatText -> \textLengthOn

2008-01-27 Thread codesite-noreply
Issue 563: rename: \fatText -> \textLengthOn http://code.google.com/p/lilypond/issues/detail?id=563 Comment #3 by wbsoft: I think the names in comment#1 are better, because there's not much in the sense of "On"/"Off" in textLength alone. \useTextLengthOn and \useTextLengthOff are more clear, b

Re: Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn

2008-01-27 Thread Hans Aberg
On 27 Jan 2008, at 12:23, Graham Percival wrote: And what about renaming \times to \tuplet? ;) I think that everybody agreed with it. Some people wanted a weird \tuplet 3:4 { } syntax as well, but after discussion it was pointed out that this wouldn't work in scheme. Certainly everybody agre

Re: Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn

2008-01-27 Thread Graham Percival
On Sun, 27 Jan 2008 02:42:26 -0800 [EMAIL PROTECTED] wrote: > And what about renaming \times to \tuplet? ;) I think that everybody agreed with it. Some people wanted a weird \tuplet 3:4 { } syntax as well, but after discussion it was pointed out that this wouldn't work in scheme. Certainly ever

Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn

2008-01-27 Thread codesite-noreply
Issue 566: showStaffSwitch -> \staffSwitchOn http://code.google.com/p/lilypond/issues/detail?id=566 Comment #3 by john.mandereau: I'm doing #563 and #564 with latest renaming proposals, as it was discussed on the list and I fully agree with them (I'm running a clean 'make web' to check, be p

Re: set associatedVoice and disappearing lyrics

2008-01-27 Thread Matti Aaltonen
Trevor Daniels treda.co.uk> writes: > > > > Date: Sat, 26 Jan 2008 12:13:38 + (UTC) > > From: Matti Aaltonen ppb.inet.fi> > > Subject: set associatedVoice and disappearing lyrics > > To: bug-lilypond gnu.org > > Message-ID: post.gmane.org> > > Content-Type: text/plain; charset=us-ascii >

Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn

2008-01-27 Thread codesite-noreply
Issue 566: showStaffSwitch -> \staffSwitchOn http://code.google.com/p/lilypond/issues/detail?id=566 Comment #2 by gpermus: I admit that this change is a bit weaker than the others. The general form of these commands is \generalDescriptionOn \generalDescriptionOff \generalDescriptionOne \genera

Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn

2008-01-27 Thread codesite-noreply
Issue 566: showStaffSwitch -> \staffSwitchOn http://code.google.com/p/lilypond/issues/detail?id=566 Comment #1 by john.mandereau: I'm not sure about this change; why not also renaming \{hide,unhide}Notes too, then? I won't do it until there is some consensus; has anybody else an opinion on this

Issue 533 in lilypond: input/regression/cluster-cross-staff.ly

2008-01-27 Thread codesite-noreply
Issue 533: input/regression/cluster-cross-staff.ly http://code.google.com/p/lilypond/issues/detail?id=533 Comment #11 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_38 -- You received this message because you ar

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

2008-01-27 Thread codesite-noreply
Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #8 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_38 -- You received this me

Issue 562 in lilypond: Vertical spacing: wrong extent-estimate with StaffGroups and hara-kiri

2008-01-27 Thread codesite-noreply
Issue 562: Vertical spacing: wrong extent-estimate with StaffGroups and hara-kiri http://code.google.com/p/lilypond/issues/detail?id=562 Comment #4 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_38 -- You recei