On Wed, Oct 6, 2010 at 1:26 AM, Mark Polesky wrote:
> Well, so many extensive replies to respond to! It's great,
> but it makes for a long post, and I do hope the thread
> participants read to the end; there's a lot of relevant
> stuff for everyone here. Thanks.
>
> * * * * * * * * * *
>
> Joe
Mark Polesky wrote Wednesday, October 06, 2010 4:46 PM
I also think the name 'space is misleading; I propose
'default-distance. Opinions?
I'd be happy with that change too.
Mark
Trevor
___
lilypond-devel mailing list
lilypond-devel
On Wed, Oct 06, 2010 at 08:50:20AM +0100, Trevor Daniels wrote:
>
> Further to my suggestion to leave the renaming to GLISS,
> so far there have been only comments supporting the
> renaming, even from Joe. Since no discussion seems
> to be necessary, do you think it might be better to
> change th
Mark Polesky:
>> Personally, I think we should add a new variable to
>> control the spacing between a markup and the bottom
>> margin. We could call it bottom-markup-spacing for now,
>> but see this post for my proposed variable renaming:
Joe Neeman:
>
> This is easy enough to add (and the naming
On 10/6/10 10:55 AM, "percival.music...@gmail.com"
wrote:
> Reviewers: ,
>
> Message:
> Here's two patches (confusingly merged together by git cl :(
To avoid that problem in the future, you'll want to have two separate
branches (a pain, I know, but it's doable).
As for the patch, LGTM.
Th
On 10/6/10 9:46 AM, "Mark Polesky" wrote:
> I also think the name 'space is misleading; I propose
> 'default-distance. Opinions?
So then we'd have, for each item-item-spacing entry
default-distance -- the non-stretched distance between the upper item
reference point and the lower item refer
Reviewers: ,
Message:
Here's two patches (confusingly merged together by git cl :( that
complete the "make fixcc.py produce compilable files" task.
Description:
Style: disable removal of "gratuitous" blocks.
This rule removed any {} which were around a single statment, but
this removal broke a
I also think the name 'space is misleading; I propose
'default-distance. Opinions?
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Arno Waschk wrote Wednesday, October 06, 2010 1:27 PM
why does the following:
[snip>
give a small piano part (which i expected) but a normal sized
bassPart Staff?
It does give a small bassPart here (2.13.34).
What do you have in bassPart?
Trevor
__
dear list,
why does the following:
<<
\new Staff \with {
fontSize = #-8
\override StaffSymbol #'staff-space = #(magstep -8)
\override StaffSymbol #'thickness = #(magstep -8)
}
{\bassPart}
\new PianoStaff \with {
fontSize = #-8
\override StaffSymbol #'staff-space = #(m
Marc Hohl schrieb:
Hello all,
here is a small patch that provides proper support for text spanners
in combination with \tabFullNotation.
... or is anything wrong with it?
(I know, tablature is not important for most users, but still ... :-)
Marc
Greetings,
Marc
--
Well, so many extensive replies to respond to! It's great,
but it makes for a long post, and I do hope the thread
participants read to the end; there's a lot of relevant
stuff for everyone here. Thanks.
* * * * * * * * * *
Joe Neeman wrote:
> I would argue that the baseline is more natural then
Mark Polesky wrote Tuesday, October 05, 2010 7:09 PM
http://lists.gnu.org/archive/html/lilypond-devel/2010-10/msg00070.html
Let me know what you guys think; it would be nice to achieve
consensus on this one.
I'm with Carl on this. I agree with all his comments.
Further to my suggestion to
13 matches
Mail list logo
