Renaming proposals, round 4:
CURRENT NAME PROPOSED NAME
-
next-staff staff-staff
default-next-staff default-staff-staff
inter-staffnonstaff-relatedstaff
inter-loose-line nonstaff-nonstaff
non-affinity nonstaff-unrelatedstaff
This patch has revised the callbacks in scm/tablature.scm. It appears
to work properly.
The tab-tie-follow-engraver is still using SCM calls to analyze the
grobs. I will get that worked out soon, I hope (although I seem to have
gone backward, not forward, today).
In this patch, the glissando,
Keith E OHara wrote Sunday, November 07, 2010 2:54 AM
On Sat, 06 Nov 2010 18:20:08 -0700,
lilypond-devel-requ...@gnu.org wrote:
[...]
And lastly, I still think reference/opposite is better than
related/unrelated:
nonstaff-referencestaff
nonstaff-oppositestaff
But I won't protest. Any last
Mark Polesky wrote Sunday, November 07, 2010 12:46 AM
Carl Sorensen wrote:
9) initial-separation
* longer but describes the meaning more accurately now
we have an item-item-spacing format
I vote for 8 or 9.
9.
Does this entail changing 'minimum-distance to
'minimum-separation?
On Sat, 06 Nov 2010 20:08:06 -0700, Mark Polesky markpole...@yahoo.com wrote:
Keith E OHara wrote:
I had imagined you would simultaneously change
staff-affinity (UP / DOWN / CENTER)
toreference-direction (UP / DOWN / CENTER)
so we can remember that this direction tells us which
Trevor Daniels wrote:
relatedstaff/unrelatedstaff
Okay, I think enough votes are in to finalize the most
recent proposal:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00137.html
So relatedstaff/unrelatedstaff it will be. I'll have more
time to start making this change later
Keith E OHara wrote Sunday, November 07, 2010 1:19 AM
On Wed, 27 Oct 2010 00:24:33 -0700, Graham Percival
gra...@percival-music.ca wrote:
On Tue, 26 Oct 2010 00:47:01 -0700, Graham wrote:
This is directed at people saying I can't do anything to
help...
I need a committing, not
After polling some of you individually, the clear winner is
to change the 'space key to 'basic-distance. Joe, can you
take it from here?
Thanks all.
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hello Carl,
I didn't test the patch, but the general logic behind it
seems to be the right way to do.
Regards,
Marc
http://codereview.appspot.com/2723043/diff/57001/scm/define-grob-properties.scm
File scm/define-grob-properties.scm (right):
Am 07.11.2010 08:47, schrieb carl.d.soren...@gmail.com:
This patch has revised the callbacks in scm/tablature.scm. It appears
to work properly.
The tab-tie-follow-engraver is still using SCM calls to analyze the
grobs. I will get that worked out soon, I hope (although I seem to have
gone
Mark, since you were the only one to vote for
this openly and Carl, Alexander and I didn't
(well, Carl did initially, then changed his mind)
perhaps you need to be a little more open about
the voting process or you'll have Valentin after
you :) Since you chose to have an open vote it
should
On Sun, Nov 7, 2010 at 11:09 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Mark, since you were the only one to vote for
this openly and Carl, Alexander and I didn't
(well, Carl did initially, then changed his mind)
perhaps you need to be a little more open about
the voting process or
Greetings everybody, here's a patch that (hopefully) addresses the
low-priority issue 1365.
I'm not sure if we've ever used convert-ly to insert comments in .ly
files, but I do think we should in this specific case: the
piano-centered dynamics template has been used by a *lot* of people in
the
On 6 November 2010 17:49, Werner LEMBERG w...@gnu.org wrote:
The whole issue is VERY problematic. Today, many fonts already
contain glyphs for small caps, however, lilypond isn't able to access
them! Reason is that lilypond currently misses an interface to
OpenType layout tables.
[...]
Valentin Villenave wrote Sunday, November 07, 2010 10:35 AM
Greetings everybody, here's a patch that (hopefully) addresses the
low-priority issue 1365.
I'm not sure if we've ever used convert-ly to insert comments in
.ly
files, but I do think we should in this specific case: the
Valentin Villenave valen...@villenave.net writes:
On Sat, Nov 6, 2010 at 4:48 AM, Joe Neeman joenee...@gmail.com wrote:
If the archives were public, it might deter people from speaking frankly.
I understand; however having public archives is also something
important for the project's
On Sun, Nov 07, 2010 at 12:26:59PM -, Trevor Daniels wrote:
Valentin Villenave wrote Sunday, November 07, 2010 10:35 AM
I'm not sure if we've ever used convert-ly to insert comments in
.ly
files, but I do think we should in this specific case: the
piano-centered dynamics template has
On Sun, Nov 07, 2010 at 12:50:20PM +, Graham Percival wrote:
The normal method would be for convert-ly to print a warning
message to the console. Why is this Dynamics thing so different
from previous changes?
Another option is to argue that in-file comments are much more
noticeable than
On 11/7/10 6:50 AM, Graham Percival gra...@percival-music.ca wrote:
On Sun, Nov 07, 2010 at 12:26:59PM -, Trevor Daniels wrote:
Valentin Villenave wrote Sunday, November 07, 2010 10:35 AM
I'm not sure if we've ever used convert-ly to insert comments in
.ly
files, but I do think we
On 11/7/10 7:07 AM, Graham Percival gra...@percival-music.ca wrote:
On Sun, Nov 07, 2010 at 12:50:20PM +, Graham Percival wrote:
The normal method would be for convert-ly to print a warning
message to the console. Why is this Dynamics thing so different
from previous changes?
Another
Trevor Daniels wrote:
Mark, since you were the only one to vote for this openly
and Carl, Alexander and I didn't (well, Carl did
initially, then changed his mind) perhaps you need to be a
little more open about the voting process or you'll have
Valentin after you :) Since you chose to have
On Sun, Nov 7, 2010 at 2:58 PM, Carl Sorensen c_soren...@byu.edu wrote:
If we could collect all the NOT_SMART output and put it as comments at the
top of the file, I'd be OK with that. But I don't like having them
scattered throughout the file.
Interesting. That's what Frescobaldi already
On Sun, Nov 7, 2010 at 4:30 PM, Mark Polesky markpole...@yahoo.com wrote:
But you're right; I was wrong to resort to backroom
politics.
Backroom politics? And here I was, thinking private discussions were
a normal and legitimate part of a project's life... :)
Here's your list with my humble
On Sun, Nov 7, 2010 at 7:30 AM, Mark Polesky markpole...@yahoo.com wrote:
All right, hopefully everyone here won't mind one last vote,
so please state your preference among the following:
SPACE MINIMUM-DISTANCE
-- --
1) basic-distance
Alexander:
Carl:
David: 1
Joe:
Mark: 1
Trevor:
Valentin: 2
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Mark Polesky markpole...@yahoo.com writes:
Mark Polesky wrote:
Okay, I think enough votes are in to finalize the most
recent proposal:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00137.html
I almost forgot... Can we have one last vote among these
two choices?
1)
Mark Polesky wrote Sunday, November 07, 2010 4:40 PM
Mark Polesky wrote:
Okay, I think enough votes are in to finalize the most
recent proposal:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00137.html
I almost forgot... Can we have one last vote among these
two choices?
1)
Mark Polesky wrote Sunday, November 07, 2010 3:30 PM
All right, hopefully everyone here won't mind one last vote,
so please state your preference among the following:
SPACE MINIMUM-DISTANCE
-- --
1) basic-distanceminimum-distance
2)
On 11/7/10 1:03 PM, Patrick McCarty pnor...@gmail.com wrote:
On Sun, Nov 7, 2010 at 7:30 AM, Mark Polesky markpole...@yahoo.com wrote:
All right, hopefully everyone here won't mind one last vote,
so please state your preference among the following:
SPACE MINIMUM-DISTANCE
Graham Percival wrote Sunday, November 07, 2010 12:50 PM
On Sun, Nov 07, 2010 at 12:26:59PM -, Trevor Daniels wrote:
Valentin Villenave wrote Sunday, November 07, 2010 10:35 AM
I'm not sure if we've ever used convert-ly to insert comments in
.ly
files, but I do think we should in this
Graham Percival wrote Sunday, November 07, 2010 1:07 PM
On Sun, Nov 07, 2010 at 12:50:20PM +, Graham Percival wrote:
The normal method would be for convert-ly to print a warning
message to the console. Why is this Dynamics thing so different
from previous changes?
Another option is to
Mark, I wanted to flag a bit of cleanup, and this reasonably-related
patch still shows as 'open'.
http://codereview.appspot.com/2758042/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
On Sun, 07 Nov 2010 01:58:58 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
Keith E OHara wrote Sunday, November 07, 2010 1:19 AM
2a) Lyrics get less space in the new system, but all the
choral-music folk seem to want is a but a touch more padding from
Lyrics to any non-associated grobs
On Sun, 07 Nov 2010 07:57:33 -0800, Mark Polesky wrote:
Can we have one last vote among these
two choices?
1) within-group-staff-staff-spacing
2) withingroup-staff-staff-spacing
Keith: either
Both are usable.
We will use this in context that makes that first qualifier almost redundant :
1) within-group-staff-staff-spacing
2) withingroup-staff-staff-spacing
Werner: 2
I think option 2 is more consistent, but I don't really care.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Oops, forgot to actually *add* Joe to this!
* * * * * * * * * * * *
Mark Polesky wrote:
Okay, I think enough votes are in to finalize the most
recent proposal:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00137.html
I almost forgot... Can we have one last vote among these
two
On 11/7/10 9:52 AM, Mark Polesky markpole...@yahoo.com wrote:
Mark Polesky wrote:
Okay, I think enough votes are in to finalize the most
recent proposal:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00137.html
I almost forgot... Can we have one last vote among these
two
On Sun, Nov 7, 2010 at 4:52 PM, Mark Polesky markpole...@yahoo.com wrote:
Carl:
David:
James:
Jan:
Jean-Charles:
Keith:
Mark: 1
Trevor:
Valentin: 1
Werner: 2
This is fun, kinda :-)
Cheers,
Valentin.
___
lilypond-devel mailing list
On Sun, Nov 7, 2010 at 5:40 PM, Mark Polesky markpole...@yahoo.com wrote:
Valentin: 1*
*was 2, then changed it to 1? Which one is it?
Er, is it the same vote we're talking about? I voted 2 in the other
thread about the 'space alist:
2) initial-distanceminimum-distance
But I thought here
On Thu, Nov 4, 2010 at 9:38 AM, Marc Hohl m...@hohlart.de wrote:
I came up with the idea to parenthesize the Harmonic brackets instead of the
TabNoteHead and thus provide the possibility to left-parenthesize or
right-parenthesize an item, but your approach sounds more consistent.
[...]
But I
On Sat, Nov 6, 2010 at 3:33 AM, Erich Enke erich.e...@gmail.com wrote:
Anyway, I hope you found that brief survey to be interesting, at
least, and I look forward to what advice you might have to offer.
Thanks for this detailed description, it looks quite interesting!
Although I don't have any
On 6 Nov 2010, at 03:33, Erich Enke wrote:
I just happened across a Sept 2010 post on lilypond-devel regarding
microtones. It reminded me how I've been wanting to work on Byzantine
notation support for lilypond. I would love to have a tool that could
actually transcribe between western and
Am Sonntag, 7. November 2010, um 20:46:54 schrieb Trevor Daniels:
I think this would be an improvement, but I don't think it's
essential. The file will be left in an erroneous state so
the user will be forced into further investigation anyway,
and the usual LilyPond error messages will
You guys are going to *hate* me for doing this, but I just
thought of a way to keep the StaffGrouper grobs consistent
with each other.
Instead of these two:
withingroup-staff-staff-spacing
staffgroup-staff-spacing
we could have these:
within-group-staff-staff-spacing
On 11/7/10 7:24 PM, Mark Polesky markpole...@yahoo.com wrote:
You guys are going to *hate* me for doing this, but I just
thought of a way to keep the StaffGrouper grobs consistent
with each other.
Instead of these two:
withingroup-staff-staff-spacing
staffgroup-staff-spacing
Keep
45 matches
Mail list logo
