2013/3/25 lilyp...@googlecode.com:
Comment #5 on issue 3266 by k-ohara5...@oco.net: \box overlaps
http://code.google.com/p/lilypond/issues/detail?id=3266
Without the boxes, the nested braces look quite pretty to me, but I have no
idea what musical meaning they are meant to convey.
Version
https://codereview.appspot.com/7834043/diff/2001/Documentation/snippets/new/applying-note-head-styles-depending-on-the-step-of-the-scale.ly
File
Documentation/snippets/new/applying-note-head-styles-depending-on-the-step-of-the-scale.ly
(right):
On 25 mars 2013, at 06:42, k-ohara5...@oco.net wrote:
Code looks good, but we could get the same result with
\override Accidental #'horizontal-skylines = #'()
Conceptually, I'm a fan of the snapping idea, but you're right that it takes
more time. Would this \override fix all problems of
On 25 mars 2013, at 07:10, k-ohara5...@oco.net wrote:
Thanks for taking the time to do this. No-one else knows enough of the
various stages of processing to bring all the pieces together.
It looks like you try to use a common UP/DOWN direction for the portions
of a broken slur, and the
On 2013/03/25 04:42:43, Keith wrote:
Code looks good, but we could get the same result with
\override Accidental #'horizontal-skylines = #'()
Incorporating the detailed outline of the accidental into the skyline
of the
chord costs time, then the iterative alignment of fingering costs
m...@mikesolomon.org wrote Monday, March 25, 2013 7:29 AM
On 25 mars 2013, at 07:10, k-ohara5...@oco.net wrote:
Conceptually, of course, there *are* two pieces. The other piece is
probably at the other end of the repeat. The automatic behavior is quite
good, so fortunately we will rarely
Hi Eluze (and everyone who'd like Lily to be case-insensitive),
On Mon, Mar 25, 2013 at 12:10 AM, Eluze elu...@gmail.com wrote:
janek.lilypond wrote
However, I think when discussing case-sensitiveness, we agreed to a
following convention: LilyPond should differentiate between upper- and
LGTM - maybe add the comment?
Cheers, Ian
https://codereview.appspot.com/7974046/diff/1/ly/titling-init.ly
File ly/titling-init.ly (right):
https://codereview.appspot.com/7974046/diff/1/ly/titling-init.ly#newcode144
ly/titling-init.ly:144:
% Check the page number in arg is not the same as the
LGTM, apart from comment on the doc-string.
Cheers, Ian
https://codereview.appspot.com/7799048/diff/3001/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (right):
https://codereview.appspot.com/7799048/diff/3001/scm/define-markup-commands.scm#newcode4286
On 2013/03/24 13:36:42, dak wrote:
https://codereview.appspot.com/7742044/diff/5001/scm/define-music-types.scm
File scm/define-music-types.scm (right):
https://codereview.appspot.com/7742044/diff/5001/scm/define-music-types.scm#newcode77
scm/define-music-types.scm:77: \n(no direction
LBTM - see comment in tracker issue:
http://code.google.com/p/lilypond/issues/detail?id=3268#c6
https://codereview.appspot.com/8009043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
pushed as 85d4958c021936c64b6ef9d514a6a2b0d269cc58, closed.
https://codereview.appspot.com/7815045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
janek.lilypond wrote
Uh, have you read David's email
http://lists.gnu.org/archive/html/lilypond-devel/2013-03/msg00448.html
?
sure, but honestly I can't see how the locale would interfere when
internally you change from/to upper-/lowercase.
The conversion between cases isn't as trivial as it
the problem is that LilyPond doesn't provide a full list of all
keywords
commands
music-functions
grobs
properties
internal options (the equivalent to doptions)
pitches
contexts
engravers
glyphs
scripts
languages
paper/header/layout … variables
(and probably a few more items)
The
Eluze writes:
lol - I gave an idea of what I mean, so please read (and answer to)
the full contribution!
Sorry ;-)
your silly answer isn't really a push towards a user-friendly
interface!
Yes, I'm working on that too. Too little time, seemingly, for
friendly answers. I'm working on that
Eluze elu...@gmail.com writes:
janek.lilypond wrote
Uh, have you read David's email
http://lists.gnu.org/archive/html/lilypond-devel/2013-03/msg00448.html
?
sure, but honestly I can't see how the locale would interfere when
internally you change from/to upper-/lowercase.
In Turkish,
Reviewers: Trevor Daniels,
Message:
On 2013/03/24 21:36:42, Trevor Daniels wrote:
I can still learn something new about LilyPond!
Thanks David - LGTM
(with a further suggestion)
https://codereview.appspot.com/7494049/diff/1/Documentation/notation/input.itely
File
Since the weather in Liguria improved a lot compared to yesterday, I've
been climbing all day. Considering my lack of regular practice as well
as the forthcoming nice weather reports, I'll probably not be able to
contribute a lot in the next days. I try getting my own contributions
managed, but
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Monday, March 25, 2013 9:11 PM
Subject: Leave of absence
Since the weather in Liguria improved a lot compared to yesterday, I've
been climbing all day. Considering my lack of regular practice as
LGTM, after removing the erroneous part of the regtest description.
On 2013/03/25 08:43:15, janek wrote:
Accidentals themselves use skylines to position themselves snugly:
http://code.google.com/p/lilypond/issues/detail?id=2811
Right. We decided it worth the time to have detailed skylines
On Mon, 25 Mar 2013 00:29:35 -0700, m...@mikesolomon.org m...@mikesolomon.org
wrote:
On 25 mars 2013, at 07:10, k-ohara5...@oco.net wrote:
It looks like you try to use a common UP/DOWN direction for the portions
of a broken slur, and the image you posted to the bug-tracker showed a
common
On 26 mars 2013, at 05:58, Keith OHara k-ohara5...@oco.net wrote:
On Mon, 25 Mar 2013 00:29:35 -0700, m...@mikesolomon.org
m...@mikesolomon.org wrote:
On 25 mars 2013, at 07:10, k-ohara5...@oco.net wrote:
It looks like you try to use a common UP/DOWN direction for the portions
of a
22 matches
Mail list logo
