On 9/11/10 5:47 AM, Graham Percival gra...@percival-music.ca wrote:
On Fri, Sep 10, 2010 at 11:37 PM, Carl Sorensen c_soren...@byu.edu wrote:
On 9/10/10 2:17 PM, Graham Percival gra...@percival-music.ca wrote:
But somehow I lost it. I'm sorry about breaking the doc build. It's fixed
On 9/12/10 1:41 AM, Mark Polesky markpole...@yahoo.com wrote:
Hey guys,
Here's a patch to add a link to Trevor Bača's project Abjad.
Trevor, I assume you're fine with this wording, but let me
know:
Good to have you back, Mark.
Abjad, a Python API for Formalized Score Control,
I'm trying to fix Issue 372, which has
\partial 4
\grace f16
d4 |
\repeat unfold 8 c8
fail to autobeam the 8th notes.
In running through the debugger, the problem is caused because a grace part
shows up in the measure position, so the autobeam never kicks in.
I think that the reason for this
On 9/15/10 2:09 AM, Marc Hohl m...@hohlart.de wrote:
Hello all,
IIUC, \override grob #'foo = #bar
is more or less the same as
(ly:grob-set-property! grob foo bar)
Actually, this is closer to being the equivalent of \tweak.
\override context.grob #'foo = #bar is accomplished in scheme
On 9/18/10 12:23 PM, Mark Polesky markpole...@yahoo.com wrote:
This patch should prevent the type of confusion that
leads to bug #45:
http://code.google.com/p/lilypond/issues/detail?id=45
Comments/objections? Okay to push?
I like the documentation, as it clarifies things. But I think
On 9/16/10 4:55 PM, Neil Puttock n.putt...@gmail.com wrote:
On 15 September 2010 03:40, Carl Sorensen c_soren...@byu.edu wrote:
Note that at this point, I haven't changed the value to which I am setting
'measurePosition. So, can anybody help me see why this code doesn't work?
It looks
On 9/18/10 7:59 PM, Mark Polesky markpole...@yahoo.com wrote:
Carl, it looks like you're outnumbered wrt to LM vs. NR, but
feel free to protest against us masses, we'll listen.
Well, the Notation Reference is supposed to contain all the information
necessary to understand all the notation.
On 9/21/10 3:46 AM, Joseph Wakeling joseph.wakel...@webdrake.net wrote:
On 09/20/2010 03:41 PM, Hans Aberg wrote:
A sharp is M-m and a flat m-M.
If I understand right, this is a key trick of your system, since such
representations allow you to raise or lower the pitch without affecting
the
On 9/21/10 9:28 AM, Joseph Wakeling joseph.wakel...@webdrake.net wrote:
On 09/21/2010 04:52 PM, Carl Sorensen wrote:
However, I was wrong in my assumption that something about the key signature
should determine which of the enharmonic equivalents should be used.
Instead, it appears
On 9/21/10 4:51 PM, Dénes Harmath harmathde...@gmail.com wrote:
Hi all,
when trying to build LilyPond on OSX 10.6.4, I get the following error:
/Users/thsoft/Development/lilypond/scripts/build/out/help2man
out/lilypond-invoke-editor out/lilypond-invoke-editor.1
Traceback (most recent
On 9/25/10 9:42 AM, Mark Polesky markpole...@yahoo.com wrote:
David Kastrup wrote:
+In the PDF and HTML output, variables should appear in a monospace
+font (to indicate that they are elements of program code). So
+when referring to variables in the text, use
Looks marvelous to me.
Thanks!
Carl
On 9/25/10 7:31 PM, Mark Polesky markpole...@yahoo.com wrote:
Carl Sorensen wrote:
I think David's point is that variables should appear in
@code{} format, not monospace format. We might choose to
make @code{} become monospace bold, or monospace
On 9/26/10 5:09 AM, Xavier Scheuer x.sche...@gmail.com wrote:
Hi Jan!
No, I'm *not* obsessed with Tempo indications placement
(or maybe, am I?)... ;-p
Actually this time the issue was reported on the French-speaking
mailing list, I'm just relaying it.
MetronomeMark
On 9/27/10 9:32 AM, Reinhold Kainhofer reinh...@kainhofer.com wrote:
Bass figures can be either added as a separate FiguredBass context (which has
the drawback that all figures will be shifted up if one of the notes in the
staff is very high), or directly inside a staff.
In the latter case,
On 10/1/10 9:43 AM, Phil Holmes m...@philholmes.net wrote:
I downloaded 13.35 yesterday just after it was announced. Today it seems to
have disappeared, to be replaced by 13.36.
2.13.35 is the latest development release.
2.13.36 is the version that is created when you build from git, but
On 10/1/10 2:28 PM, Xavier Scheuer x.sche...@gmail.com wrote:
On 1 October 2010 22:15, Carl Sorensen c_soren...@byu.edu wrote:
2.13.35 is the latest development release.
2.13.36 is the version that is created when you build from git, but it's not
yet released.
That's why my latest
On 10/1/10 2:44 PM, Graham Percival gra...@percival-music.ca wrote:
On Fri, Oct 1, 2010 at 9:35 PM, Carl Sorensen c_soren...@byu.edu wrote:
This is a website bug, and should be Critcal, IMO, because it prevents
downloading the latest devel.
Dude! Chill! :)
What an easy Critical bug
On 10/1/10 4:42 PM, Graham Percival gra...@percival-music.ca wrote:
On Fri, Oct 1, 2010 at 11:30 PM, Mark Polesky markpole...@yahoo.com wrote:
Graham Percival wrote:
Ok guys. I see why Carl wanted to change it, but a few points:
- CG 10.2 is pretty clear about what the numbers mean.
-
On 10/1/10 4:30 PM, Mark Polesky markpole...@yahoo.com wrote:
Graham Percival wrote:
This is a website bug, and should be Critcal, IMO,
because it prevents downloading the latest devel.
Dude! Chill! :)
I mistyped 2.13.36 instead of 2.13.35 in VERSION. The fix
has been pushed.
On 10/3/10 10:29 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
David Kastrup wrote Sunday, October 03, 2010 3:22 PM
push = -\tweak #'side-axis #X ^\markup { \musicglyph
#accordion.push }
pull = -\tweak #'side-axis #X ^\markup { \musicglyph
#accordion.pull }
\score {
\repeat
On 10/2/10 10:50 PM, Joe Neeman joenee...@gmail.com wrote:
On Sat, Oct 2, 2010 at 8:08 PM, carl.d.soren...@gmail.com wrote:
On 2010/10/03 02:49:30, Mark Polesky wrote:
On 2010/10/02 16:32:06, Carl wrote:
I don't think so. I think 'padding is added as a rigid space interval,
hence my
On 10/3/10 3:49 PM, Neil Puttock n.putt...@gmail.com wrote:
On 30 September 2010 09:57, Phil Holmes m...@philholmes.net wrote:
1) In harp-pedals-sanity-checks.ly we get:
+warning: Harp pedal diagram contains dividers at positions (4). Normally,
there is only one divider after the third
On 10/3/10 5:39 PM, Neil Puttock n.putt...@gmail.com wrote:
On 4 October 2010 00:19, Carl Sorensen c_soren...@byu.edu wrote:
Is it a bug, or just different ordering of the output? The warnings are
proper, aren't they?
Can't we just say the warnings have reversed order, so
On 10/4/10 11:21 AM, Graham Percival gra...@percival-music.ca wrote:
convert-ly complains about the woodwind diagrams in wind.itely.
- if the current material is correct, please bump the
@c \version 2.12.0
at the top of the file to 2.13.36
The current version is correct. We didn't update
On 10/4/10 11:18 AM, Graham Percival gra...@percival-music.ca wrote:
Is this a good change?
Yes. convert-ly should have made these changes automatically, I think.
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 10/5/10 12:09 PM, Mark Polesky markpole...@yahoo.com wrote:
WRT the flexible vertical spacing dimensions, the upper
attachment points for 'space and 'minimum-distance currently
align with the Y-coordinate of the origin (0,0) of the upper
item. For systems this is the middle line of the
On 10/6/10 9:46 AM, Mark Polesky markpole...@yahoo.com 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
On 10/6/10 10:55 AM, percival.music...@gmail.com
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
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 seems
On 10/7/10 1:44 AM, Alexander Kobel n...@a-kobel.de wrote:
On 2010-10-06 17:46, Mark Polesky wrote:
I also think the name 'space is misleading; I propose
'default-distance. Opinions?
I can't see why 'space should be misleading, but that might just be that
I'm accustomed to it by now.
On 10/7/10 7:51 AM, Valentin Villenave valen...@villenave.net wrote:
On Thu, Oct 7, 2010 at 3:41 PM, Carl Sorensen c_soren...@byu.edu wrote:
I think I'd prefer desired-distance to optimal-distance. optimal distance
is what the algorithms actually end up with, as a tradeoff between desired
On 10/7/10 8:59 AM, Mark Polesky markpole...@yahoo.com wrote:
Enough votes are in for 'base-distance (and you can add my
vote as well), so I think that settles it. But I still need
people to comment on
1) the patch:
http://codereview.appspot.com/2303044
The patch looks fine to me.
On 10/9/10 9:46 AM, Mark Polesky markpole...@yahoo.com wrote:
* * * * * * * * * *
before-title-spacing applies to these cases:
1) from last system in a score to top-level markup.
2) from last system of one score to scoreTitleMarkup of
another score.
Within the proposed naming scheme,
On 10/9/10 10:52 AM, Joe Neeman joenee...@gmail.com wrote:
On Sat, Oct 9, 2010 at 9:05 AM, Carl Sorensen c_soren...@byu.edu wrote:
On 10/9/10 9:46 AM, Mark Polesky markpole...@yahoo.com wrote:
* * * * * * * * * *
before-title-spacing applies to these cases:
1) from last system
On 10/10/10 12:56 PM, Mark Polesky markpole...@yahoo.com wrote:
Here's an updated patch set for review:
http://codereview.appspot.com/2303044/
It's organized into 5 commits on my local branch:
1) Rename vertical spacing dimensions.
2) Update convert-ly (vertical spacing).
3) Run
On 10/12/10 4:20 PM, Wols Lists antli...@youngman.org.uk wrote:
On 12/10/10 14:02, Kieren MacMillan wrote:
Hi James,
I still think a *user* (not programmer or code developer) is going to really
get frustrated when they don't know what a system is i.e... 'oh you mean the
stuff with the
On 10/12/10 4:27 PM, Wols Lists antli...@youngman.org.uk wrote:
On 12/10/10 22:05, Graham Percival wrote:
On Tue, Oct 12, 2010 at 02:24:37PM +0100, Trevor Daniels wrote:
I'll stop if I am really showing my ignorance (I am not a code
developer),
I'm afraid you're showing your ignorance as
On 10/12/10 9:30 PM, Graham Percival gra...@percival-music.ca wrote:
On Wed, Oct 13, 2010 at 12:30:32AM +, Pavel Sanda wrote:
please would you consider to accept the patch attached in
http://code.google.com/p/lilypond/issues/detail?id=1281
for the next release?
Unfortunately our
On 10/12/10 9:28 PM, Graham Percival gra...@percival-music.ca wrote:
On Tue, Oct 12, 2010 at 05:17:44PM +0100, Phil Holmes wrote:
percival.music...@gmail.com wrote in message
news:0016e6435382308cfc04925d9...@google.com...
On 2010/10/11 18:18:37, dak wrote:
python/convertrules.py:2992: _
David Kastrup d...@gnu.org writes:
So my fear is that the new scheme is both strictly logical, and not
useful for specifying a coherent document layout.
But the new scheme is just a restatement (renaming) of the current scheme.
Mark is not trying to *redo* the document layout algorithms;
On 10/13/10 8:29 AM, David Kastrup d...@gnu.org wrote:
Carl Sorensen c_soren...@byu.edu writes:
David Kastrup d...@gnu.org writes:
So my fear is that the new scheme is both strictly logical, and not
useful for specifying a coherent document layout.
But the new scheme is just
On 10/13/10 2:40 PM, David Kastrup d...@gnu.org wrote:
Carl Sorensen c_soren...@byu.edu writes:
On 10/13/10 8:29 AM, David Kastrup d...@gnu.org wrote:
Carl Sorensen c_soren...@byu.edu writes:
David Kastrup d...@gnu.org writes:
So my fear is that the new scheme is both strictly
On 10/18/10 9:21 AM, Werner LEMBERG w...@gnu.org wrote:
I wrote:
I've attached fontforge images of two broken glyphs; [...]
Werner,
Can you open an issue directly on the tracker and post your attachments
there?
It seems that there ought to be three issues:
1) varsegno
2)
On 10/19/10 3:48 AM, Marc Hohl m...@hohlart.de wrote:
Am 19.10.2010 11:14, schrieb Werner LEMBERG:
So the advice
---
The recommended calling sequence of mf2pt1 is
mf2pt1 --rounding=0.0001other options font
You need mf2pt1 version 2.1 or newer.
---
in README should read
Here's a patch for the accordion push symbol.
I went ahead and changed to a fill of the outline.
It would have been simpler if I had just drawn two straight lines:
draw z1
-- z2;
draw z3
-- z2;
This would seem to be allowed by the instructions in README, but I get the
sense that
On 10/19/10 11:19 AM, Marc Hohl m...@hohlart.de wrote:
Am 19.10.2010 12:06, schrieb Carl Sorensen:
Actually, it's a lot easier than this.
See the attached patch.
Um, that's what I tried before, but I still got intersections (which were
smaller than before, but still visible
On 10/19/10 11:19 AM, Marc Hohl m...@hohlart.de wrote:
Um, that's what I tried before, but I still got intersections (which were
smaller than before, but still visible in fontforge at 200%), so I had to
introduce the tensions.
When I applied and tested your patch, there were still grazing
On 10/19/10 12:52 PM, Werner LEMBERG w...@gnu.org wrote:
Um, that's what I tried before, but I still got intersections
(which were smaller than before, but still visible in fontforge at
200%), so I had to introduce the tensions.
When I applied and tested your patch, there were still grazing
On 10/19/10 5:24 PM, Werner LEMBERG w...@gnu.org wrote:
Don't use `penstroke' but `fill'.
That was my thought, when looking at the glyph. Find the
intersections, and draw the relevant paths for the entire outline
and subtract the relevant paths for the holes.
This is probably
On 10/20/10 1:59 AM, Werner LEMBERG w...@gnu.org wrote:
+ ... {dir (180 - loopangle)}z7e{dir (180 - loopangle)}
This is too much :-) The following
+ ... z7e{dir (180 - loopangle)}
is sufficient. A new patch attached (to preserve tabs for dull mail
Yes, please do. It's probably my mistake.
Thanks,
Carl
On 10/20/10 9:59 AM, Francisco Vila paconet@gmail.com wrote:
Hello.
see
Customizing fretboard fret diagrams
Documentation/snippets/customizing-fretboard-fret-diagrams.ly
lines 74 -- 81:
doctitle = Customizing fretboard fret
On 10/22/10 3:10 AM, Valentin Villenave valen...@villenave.net wrote:
The following code causes a segfault.
LilyPond 2.13.36, GNU/Linux x86_64.
toto =
#(define-music-function (parser location arg) (ly:music?)
(display (ly:event-property arg 'name))
(make-sequential-music arg))
On 10/22/10 5:08 AM, Janek Warchoł lemniskata.bernoull...@gmail.com
wrote:
Hi,
I'm from Poland and we use here a different chord naming convention: the main
difference is that minor chords are written with lowercase and major chords
are written with uppercase. I'd like to add this to
On 10/23/10 3:02 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
James Lowe wrote Saturday, October 23, 2010 8:00 PM
While scanning through NR 1.2.2 the last section I came across the
line
When a multi-measure rest immediately follows a @code{\partial}
setting, resulting bar-check
On 10/23/10 2:54 PM, Valentin Villenave v.villen...@gmail.com wrote:
On Thu, Oct 21, 2010 at 4:53 AM, carl.d.soren...@gmail.com wrote:
Hi Carl,
I like this idea as a way to get the functionality you want in the short
term. But I don't like it for the long term. I think the long-term
On 10/23/10 4:35 PM, Valentin Villenave v.villen...@gmail.com wrote:
On Sun, Oct 24, 2010 at 12:15 AM, Carl Sorensen c_soren...@byu.edu wrote:
L.G...T..M
Nice approach, Valentin! Now I have no reasonable opposition to this patch!
Well, you've just made my day :-)
On Sun
On 10/22/10 12:20 PM, Marc Hohl m...@hohlart.de wrote:
Am 20.10.2010 15:30, schrieb Werner LEMBERG:
The README also says that we shouldn't apply transformations to
fills, but instead transform the path then fill the path. The
current varsegno transforms the penstroke, which I think is
On 10/23/10 1:06 PM, James Lowe james.l...@datacore.com wrote:
Hello,
While scanning through NR 1.2.2 the last section I came across the line
in the @KNOWNISSUES section
Multi-measure rests do not take part in rest collisions.
So what are they considered as when calculating
On 10/23/10 7:43 PM, Graham Percival gra...@percival-music.ca wrote:
- perhaps we should not consider arabic.ly as a language, but rather
as an instrument (or music) style, like bagpipes.ly or gregorian.ly.
I think that is correct.
Thanks,
Carl
On 10/24/10 6:17 AM, Valentin Villenave valen...@villenave.net wrote:
Better luck next time (if there is a next time, which I doubt)...
Don't give up now!
The documentation stuff can be worked out -- if you had posted it on
Rietveld, Graham would have given you feedback.
And now you've
On 10/24/10 8:17 PM, Valentin Villenave v.villen...@gmail.com wrote:
On Mon, Oct 25, 2010 at 3:57 AM, carl.d.soren...@gmail.com wrote:
Update the \version string in all of these files!
Well, I was reluctant to put a minor version number. Do you think
putting 2.14.0 would be okay?
Then,
Copied from frogs to devel, because I don't think the frog people can
answer.
Carl
-- Forwarded Message
From: Ian Hulin i...@hulin.org.uk
Date: Wed, 27 Oct 2010 15:31:13 -0600
To: Lilypond Frogs List fr...@lilynet.net
Conversation: [frogs] display-lily.scm question
Subject: [frogs]
On 10/27/10 11:32 PM, Werner LEMBERG w...@gnu.org wrote:
However, I do have the original doc-build error, which would
presumably be the same problem as the regtest failure: [...]
c7/lily-4bb72c87.ly
The compilation of this file fails? Which snippet is that?
By looking at
On 10/28/10 7:54 AM, Carl Sorensen c_soren...@byu.edu wrote:
On 10/27/10 11:32 PM, Werner LEMBERG w...@gnu.org wrote:
However, I do have the original doc-build error, which would
presumably be the same problem as the regtest failure: [...]
c7/lily-4bb72c87.ly
The compilation
On 10/28/10 1:54 PM, Marc Hohl m...@hohlart.de wrote:
Am 28.10.2010 14:53, schrieb carl.d.soren...@gmail.com:
Currently, I view Scheme engravers as a way for users (and snippets) to
add engraver functionality, but not as an optimal way to add core
functionality.
I understand your argument,
On 10/28/10 4:00 PM, Werner LEMBERG w...@gnu.org wrote:
\sourcefilename slur-tuplet.ly
But when I manually compile this regtest, I get: [...]
success: Compilation successfully completed
Honestly, I've suspected that. The question is whether Graham has
observed a Heisenbug, or whether
On 10/28/10 4:39 PM, Werner LEMBERG w...@gnu.org wrote:
I don't think it's a Heisenburg. The make test fails for me, too.
Me too... Very, very strange. Anybody out here who knows enough
about the Scheme internals to debug it?
I'm currently seeing if I can reproduce it by a single
On 10/28/10 4:44 PM, Carl Sorensen c_soren...@byu.edu wrote:
On 10/28/10 4:39 PM, Werner LEMBERG w...@gnu.org wrote:
I don't think it's a Heisenburg. The make test fails for me, too.
Me too... Very, very strange. Anybody out here who knows enough
about the Scheme
On 10/28/10 4:50 PM, Valentin Villenave valen...@villenave.net wrote:
On Fri, Oct 29, 2010 at 12:15 AM, Carl Sorensen c_soren...@byu.edu wrote:
I would *love* to have a way to document Scheme engravers such that we could
include them in the docs, but at present I have no knowledge of how
On 10/28/10 4:52 PM, Carl Sorensen c_soren...@byu.edu wrote:
On 10/28/10 4:44 PM, Carl Sorensen c_soren...@byu.edu wrote:
On 10/28/10 4:39 PM, Werner LEMBERG w...@gnu.org wrote:
I don't think it's a Heisenburg. The make test fails for me, too.
Me too... Very, very strange. Anybody out
On 10/29/10 4:27 PM, Mark Polesky markpole...@yahoo.com wrote:
Guys,
Here are my proposals for renaming the properties related to
Vertical spacing inside systems.
* * * * * * * * * * * * * * *
I've thought about it, and I think I slightly favor the term
loose line over non-staff
On 10/30/10 3:40 PM, Marc Hohl m...@hohlart.de wrote:
Am 29.10.2010 11:05, schrieb Neil Puttock:
On 28 October 2010 23:55, Carl Sorensenc_soren...@byu.edu wrote:
Well, as far as I can see, Scheme engravers are really engravers, so they
ought to be documented in the IR along with the C++
On 10/31/10 3:00 PM, Keith E OHara k-ohara5...@oco.net wrote:
On Fri, 29 Oct 2010 21:04:06 -0700, lilypond-devel-requ...@gnu.org wrote:
Mark Polesky wrote Friday, October 29, 2010 11:27 PM
I've thought about it, and I think I slightly favor the term
loose line over non-staff line
On 11/1/10 1:53 AM, Marc Hohl m...@hohlart.de wrote:
Sorry for causing so much trouble.
No trouble, Marc. You never need to apologize for working to improve
LilyPond!
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 11/2/10 2:09 AM, Jan Nieuwenhuizen jann...@gnu.org wrote:
Using a recent LilyPond Emmentaler font on the gnome canvas or
pangocairo drawing area, some characters fail to display, such
as accidentals.flat (charcode 57626 0xE11A) which is overridden
by a euro symbol.
Since we're playing in
On 11/2/10 2:56 PM, Mark Polesky markpole...@yahoo.com wrote:
(trying to make this as painless as possible...)
Renaming proposals, round 2:
CURRENT NAME PROPOSED NAME
-
next-staff staff-staff
default-next-staff default-staff-staff
On 11/3/10 6:50 AM, Marc Hohl m...@hohlart.de wrote:
Am 02.11.2010 04:04, schrieb carl.d.soren...@gmail.com:
Updated to only acknowledge tab-note-head, not note-head.
Makes perfect sense to me.
Thanks for your work!
You're welcome.
Pushed to git.
Thanks,
Carl
On 11/3/10 12:43 PM, Neil Puttock n.putt...@gmail.com wrote:
On 3 November 2010 16:15, Marc Hohl m...@hohlart.de wrote:
Am 03.11.2010 15:10, schrieb Carl Sorensen:
On 11/3/10 6:50 AM, Marc Hohlm...@hohlart.de wrote:
Am 02.11.2010 04:04, schrieb carl.d.soren...@gmail.com
On 11/3/10 10:15 AM, Marc Hohl m...@hohlart.de wrote:
Am 03.11.2010 15:10, schrieb Carl Sorensen:
On 11/3/10 6:50 AM, Marc Hohlm...@hohlart.de wrote:
Am 02.11.2010 04:04, schrieb carl.d.soren...@gmail.com:
Updated to only acknowledge tab-note-head, not note-head
On 11/3/10 9:34 AM, Marc Hohl m...@hohlart.de wrote:
Am 03.11.2010 15:11, schrieb Carl Sorensen:
On 11/3/10 7:03 AM, Marc Hohlm...@hohlart.de wrote:
Hello list, hello Valentin (I think you are the master of the tracker),
Federico Bruni raised this issue long ago, see
http
-groupedstaff].
Trevor, after some consideration, I'm afraid I'm not so much
in favor of groupedstaff-groupedstaff (or it's shorter
cousin). They too strongly suggest the possibility of this:
[last staff of group] - [first staff of next group]
Carl Sorensen wrote:
I just thought of a c
On 11/3/10 5:52 PM, n.putt...@gmail.com n.putt...@gmail.com wrote:
On 2010/11/03 23:14:47, Carl wrote:
I think I'd probably go a bit farther.
What if we acknowledged ties, slurs, and glissandos (glissandi?) in
the
Tab_note_head_engraver and set the desired properties there.
Which
On 11/5/10 7:26 AM, Graham Percival gra...@percival-music.ca wrote:
I repeat: do you (not necessarily David, but anybody) agree
that an OSS project can, in theory, have some kind of private
mailing list?
I believe that private mailing lists for an OSS project are useful and that
LilyPond
On 11/5/10 7:49 AM, Graham Percival gra...@percival-music.ca wrote:
On Fri, Nov 05, 2010 at 07:36:42AM -0600, Carl Sorensen wrote:
I don't think it's worth delaying 2.14 in order to debate either of these
questions. Can't we just note that the debate exists, perhaps add it to our
list
On 11/5/10 8:15 AM, Valentin Villenave valen...@villenave.net wrote:
On Fri, Nov 5, 2010 at 2:56 PM, Carl Sorensen c_soren...@byu.edu wrote:
Great! Let's move on, OK? If Valentin wants to patch the documentation,
then he can propose a patch. The same applies to anyone else who wants
On 11/5/10 9:37 AM, Valentin Villenave valen...@villenave.net wrote:
On Fri, Nov 5, 2010 at 4:06 PM, Carl Sorensen c_soren...@byu.edu wrote:
As far as I know, I'm not a member of -hackers. I get a not-found error
whenever I click on any of the links.
I don't have any emails from
On 11/5/10 11:40 AM, Valentin Villenave valen...@villenave.net wrote:
On Fri, Nov 5, 2010 at 5:12 PM, Carl Sorensen c_soren...@byu.edu wrote:
2) Any description of the history may be irrelevant to the future
Is it for us to decide?
Nope. And it's impossible for anybody to decide until
On 11/5/10 5:17 PM, Mark Polesky markpole...@yahoo.com wrote:
In case anyone cares, I finally was able to determine the
reference points for the individual non-staff lines. Here
they are:
CONTEXT REFERENCE POINT
--- ---
ChordNamesbaseline
NoteNames
On 11/6/10 11:32 AM, Mark Polesky markpole...@yahoo.com wrote:
7 proposals for renaming the 'space alist-key have been
discussed, but a decision has not yet been made. And I just
added an 8th proposal (initial-distance).
To recap, I think the arguments *for* each of these are
mostly
On 11/6/10 5:38 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Mark Polesky wrote Saturday, November 06, 2010 5:32 PM
7) basic-distance
8) initial-distance
I vote for either 7 or 8. What about you?
9) initial-separation
* longer but describes the meaning more accurately
now
On 11/6/10 6:46 PM, Mark Polesky markpole...@yahoo.com wrote:
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
On 11/6/10 7:17 PM, Mark Polesky markpole...@yahoo.com wrote:
Okay, it looks like we're converging here...
Renaming proposals, round 4:
CURRENT NAME PROPOSED NAME
-
next-staff staff-staff
default-next-staff default-staff-staff
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
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
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 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
On 11/8/10 1:14 PM, Mark Polesky markpole...@yahoo.com wrote:
Keith E OHara wrote:
We will use this in context that makes that first
qualifier almost redundant :
\override Context.StaffGrouper #'withingroup-staff-staff-spacing
This is an excellent point, and in response I'd like to
On 11/8/10 9:34 PM, Keith E OHara k-ohara5...@oco.net wrote:
On Mon, 08 Nov 2010 11:14:11 -0800, Mark Polesky markpole...@yahoo.com
wrote:
Similarly, I think the two 'staff-staff-spacing properties
would be intuitive and easy enough to keep separate,
mentally:
% space between
On 11/10/10 9:05 PM, Mark Polesky markpole...@yahoo.com wrote:
The \paper variables are completely absent from the IR.
Shouldn't they be included in an internals reference?
I assume so. Let's open a tracker issue
Carl
___
lilypond-devel
701 - 800 of 1841 matches
Mail list logo
