On the other hand: Wouldn't it be possible to make LilyPond simply
walk over all possible combinations to find out whether, say,
foo.bar
is a context followed by a property, or a property followed by a
sub-property, etc.?
Technically impossible. At the time an \override is parsed, the
I guess it's time to make it official: I'm stepping down as
project manager. I'll stick around for a while to review patches
on countdowns and participate in policy discussions, but don't be
surprised if I'm gone for good in a few months.
It's been quite a ride for the past 9 or 10 years
Werner LEMBERG w...@gnu.org writes:
On the other hand: Wouldn't it be possible to make LilyPond simply
walk over all possible combinations to find out whether, say,
foo.bar
is a context followed by a property, or a property followed by a
sub-property, etc.?
Technically impossible. At
On 2012-10-12 00:25, David Kastrup wrote: \tweak gets one symbol list,
\override gets two symbol lists. The
symbol list for \tweak may optionally start with a grob name, the first
symbol list for \override may optionally start with a context name. I
can offer \tweak color.Accidental #red
David,
On Fri, Oct 12, 2012 at 7:57 AM, David Kastrup d...@gnu.org wrote:
AFAIK, compilers do something similar, warning about ambiguities.
It is one of the sad facets of communication that the mood-deteriorating
effects of unintentional satire are quite similar to that of the real
deal.
I
On Fri, Oct 12, 2012 at 9:01 AM, Graham Percival
gra...@percival-music.ca wrote:
I guess it's time to make it official: I'm stepping down as
project manager. I'll stick around for a while to review patches
on countdowns and participate in policy discussions, but don't be
surprised if I'm gone
David Kastrup wrote Thursday, October 11, 2012 7:27 PM
I need feedback. Read on.
I am enthusuastic about these changes. They will remove
one of the major obscacles to tyros trying to master the syntax.
This is a wonderful achievement!
And give their opinion about what does not quite
Graham, you wrote Friday, October 12, 2012 8:01 AM
I guess it's time to make it official: I'm stepping down as
project manager.
That's a real blow. You've made an immense contribution to
LilyPond over the years. It won't be the same without you!
But nothing lasts forever; the time has
Graham Percival gra...@percival-music.ca writes:
I guess it's time to make it official: I'm stepping down as
project manager. I'll stick around for a while to review patches
on countdowns and participate in policy discussions, but don't be
surprised if I'm gone for good in a few months.
Trevor Daniels t.dani...@treda.co.uk writes:
There are a few areas of the documentation that will need manual
change, partly to explain the new syntax, partly to correct the
indentation of lines following changed lines, and maybe one or two
others.
_Very_ much so. However, a major
2012/10/12 David Kastrup d...@gnu.org:
Trevor Daniels t.dani...@treda.co.uk writes:
I'm less concerned than Werner about the inconsistency of the
tweak syntax. The context needs to be specified only rarely, and
it is a small price to pay for the enormous gain.
Well, strictly speaking we are
Graham,
let me express my gratitude for all work you did on LilyPond.
I have to admit that when i began my LilyPond adventure, you seemed to
be scary and unenthusiastic, very down-to-the-earth. However, as the
time passed i have learned that this impression was wrong, and that
you are a vital
Janek Warchoł janek.lilyp...@gmail.com writes:
On Fri, Oct 12, 2012 at 7:57 AM, David Kastrup d...@gnu.org wrote:
AFAIK, compilers do something similar, warning about ambiguities.
It is one of the sad facets of communication that the mood-deteriorating
effects of unintentional satire are
2012/10/9 David Kastrup d...@gnu.org:
Since this patch series is a bit humongous for reviewing in a single
Rietveld review and it would take two months to get every patch in
sequence through an individual review, I am putting this series out as
an experiment to the list.
Let's see how we
David Kastrup wrote Friday, October 12, 2012 12:23 PM
Trevor Daniels t.dani...@treda.co.uk writes:
X-offset and friends. I'd prefer to change these to x/y-offset, to
unify the letter-casing of properties. Can also be addressed later.
addressed later implies that this is a related
Hi,
i'm short on time so i'll try to be brief - hopefully this won't cause
any misunderstanding.
David, i understand that some comments and questions may look like the
sender is questioning your knowledge in some area.
I want to assure you that when i ask such a stupid question, i'm not
Trevor Daniels t.dani...@treda.co.uk writes:
I see really only two reasonably
consistent solutions that both involve _not_ using \tweak for the
grobbed variant:
\tweakGrob Accidental color #red cis
or
\single \override Accidental color = #red cis
since the latter is now available.
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Friday, October 12, 2012 12:23 PM
Trevor Daniels t.dani...@treda.co.uk writes:
X-offset and friends. I'd prefer to change these to x/y-offset, to
unify the letter-casing of properties. Can also be addressed later.
- Original Message -
From: Trevor Daniels t.dani...@treda.co.uk
To: Graham Percival gra...@percival-music.ca
Cc: Lily-Devel List lilypond-devel@gnu.org
Sent: Friday, October 12, 2012 11:51 AM
Subject: Re: stepping down as project manager
Graham, you wrote Friday, October 12, 2012
I'm less concerned than Werner about the inconsistency of the tweak
syntax. The context needs to be specified only rarely, and it is a
small price to pay for the enormous gain. Hopefully the error
message that results when it is specified incorrectly will be or can
be made to be helpful.
Am 12.10.2012 16:48, schrieb David Kastrup:
Trevor Daniels t.dani...@treda.co.uk writes:
I see really only two reasonably
consistent solutions that both involve _not_ using \tweak for the
grobbed variant:
\tweakGrob Accidental color #red cis
or
\single \override Accidental color = #red cis
Am 12.10.2012 21:01, schrieb Marc Hohl:
Am 12.10.2012 16:48, schrieb David Kastrup:
Trevor Daniels t.dani...@treda.co.uk writes:
I see really only two reasonably
consistent solutions that both involve _not_ using \tweak for the
grobbed variant:
\tweakGrob Accidental color #red cis
or
Am 12.10.2012 09:01, schrieb Graham Percival:
I guess it's time to make it official: I'm stepping down as
project manager. I'll stick around for a while to review patches
on countdowns and participate in policy discussions, but don't be
surprised if I'm gone for good in a few months.
It's sad
However, one could change the current
\tweak Accidental.color into
\grob Accidental \tweak color ...
and similarly for other tweaks: \grob name would just take the next
music element, take a look at the last applied tweak and make it
specific to one grob type. Better names welcome. It
Hi,
inspired by Graham i'm organizing Weekly Summaries For Busy Lily
Developers [1]. Here are the guidelines:
- *anyone* can post them
- they *don't have* to be complete. Just summarize important emails
that you remember.
- if you see that something is missing, just post it in a reply. Keep it
2012/10/12 Trevor Daniels t.dani...@treda.co.uk:
Graham, you wrote Friday, October 12, 2012 8:01 AM
I guess it's time to make it official: I'm stepping down as
project manager.
That's a real blow. You've made an immense contribution to
LilyPond over the years. It won't be the same
On Fri, Oct 12, 2012 at 9:10 PM, Marc Hohl m...@hohlart.de wrote:
... what about
\for Accidental \tweak color ...?
I could live with that, as well as \tweakGrob and \on Accidental
\tweak ... and \grob Accidental \tweak. However, i don't consider any
of them particularly elegant.
Probably the
I guess it's time to make it official: I'm stepping down as project
manager. I'll stick around for a while to review patches on
countdowns and participate in policy discussions, but don't be
surprised if I'm gone for good in a few months.
It's sad to hear that ...
Indeed.
I can only
Werner LEMBERG w...@gnu.org writes:
I'm less concerned than Werner about the inconsistency of the tweak
syntax. The context needs to be specified only rarely, and it is a
small price to pay for the enormous gain. Hopefully the error
message that results when it is specified incorrectly will
Janek Warchoł janek.lilyp...@gmail.com writes:
Hi,
inspired by Graham i'm organizing Weekly Summaries For Busy Lily
Developers [1]. Here are the guidelines:
- *anyone* can post them
- they *don't have* to be complete. Just summarize important emails
that you remember.
- if you see that
On Fri, Oct 12, 2012 at 10:34 PM, David Kastrup d...@gnu.org wrote:
Well, the user-friendliness faction demands the option to have LilyPond
behave case-insensitively. I certainly won't support making this a
default, but I also don't want to make case have meaning independent
from being part
[...] it is a pity that I'm trampling on David's nerves because
many of my questions are naive.
I have no really good suggestions here regarding my reactions.
Probably one should aim for a more curious than skeptical tone. It
is obvious that lecturing people does more for my ego than
In ly/music-functions-init.ly I see code like the following:
crossStaff =
#(define-music-function (parser location notes) (ly:music?)
(_i Create cross-staff stems)
#{
\override Stem #'cross-staff = #cross-staff-connect
\override Flag #'style = #'no-flag
$notes
\revert Stem
On Fri, Oct 12, 2012 at 01:03:38PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
I'll do the thing
which every computer science student should do at least once in
their life: I'll make my own language. I'm not comfortable with
the level of abstractions
Graham Percival gra...@percival-music.ca writes:
- triplets written with 3:2. I'll probably use python for the
language, so having a dictionary of hard-coded rules like
\tuplet x:y = \tuplet y/x (or \times y/x )
will be really easy. And since it's a python script, it would
be
Hi,
here's the first issue of LilyPond's weekly Busy Developer's
Summary. Its aim is to help people that are too busy to read all
LilyPond emails to keep up with the most important stuff; this week
seems to be particularly dense in this regard. Enjoy!
WHAT IMPORTANT HAPPENED
Graham Percival
I like it.
http://codereview.appspot.com/6635050/diff/15002/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
http://codereview.appspot.com/6635050/diff/15002/Documentation/notation/changing-defaults.itely#newcode4202
37 matches
Mail list logo
