Folks,
Please see http://code.google.com/p/lilypond/issues/detail?id=2885. GUB is
broken and does not currently build the full output that it should. It
could be fixed by reverting Jan's commit, but that seems the wrong
approach - he obviously made the commit for a reason. Could someone
Hello,
On 10 Oct 2012, at 21:02, Werner LEMBERG w...@gnu.org wrote:
X-offset anyone?
... should be renamed IMHO. Regardless of our discussion, it
doesn't fit into the current naming scheme.
The corresponding axis is called X, and using x for a constant in
the expectation that the user
James pkx1...@gmail.com writes:
On 10 Oct 2012, at 21:02, Werner LEMBERG w...@gnu.org wrote:
X-offset anyone?
... should be renamed IMHO. Regardless of our discussion, it
doesn't fit into the current naming scheme.
The corresponding axis is called X, and using x for a constant in
the
Copying to a wider distribution of people who only sporadically write on
lilypond-devel (I hope I have most of the others covered via
lilypond-devel) since I need feedback on this. Issue 2883
URL:http://code.google.com/p/lilypond/issues/detail?id=2883 deals with
a mostly (apart from half a dozen
So far, the attempt to get feedback on this language change has
failed spectacularly,
At least I'm all for it, and Janek too. So it's not such a
spectacular failure IMHO.
but that is the point of the current review at
URL:http://codereview.appspot.com/6635050.
This is terribly awkward to
On Thu, Oct 11, 2012 at 8:27 PM, David Kastrup d...@gnu.org wrote:
But the _point_ of the _invasive_ patch and convert-ly rules was to get
feedback about what people think about a language change that
essentially makes it unnecessary for users to write symbols like #'xxx [...]
I LOVE this
[...] I still don't want to make the interpretation of identifiers
depend on case other than, of course, that you need to stick with
the exact spelling of an identifier once you picked its name.
Besides limiting the namespace of user variables, what are your
arguments against such a change?
Werner LEMBERG w...@gnu.org writes:
So far, the attempt to get feedback on this language change has
failed spectacularly,
At least I'm all for it, and Janek too. So it's not such a
spectacular failure IMHO.
but that is the point of the current review at
Werner LEMBERG w...@gnu.org writes:
[...] I still don't want to make the interpretation of identifiers
depend on case other than, of course, that you need to stick with
the exact spelling of an identifier once you picked its name.
Besides limiting the namespace of user variables, what are
David Nalesnik david.nales...@gmail.com writes:
On Thu, Oct 11, 2012 at 1:27 PM, David Kastrup d...@gnu.org wrote:
Though I don't particularly mind writing cryptic symbols like #'xxx
anymore (by now they're my old friends), I'm pretty sure I did as I
was struggling to learn the program.
On Tue, Oct 9, 2012 at 8:19 AM, m...@mikesolomon.org
m...@mikesolomon.org wrote:
Just a quick ping to let you know that I'm not dead - I've been swamped w/
work recently and just got engaged so I'm planning out a wedding (w00t!).
Dude, you're insane. (I knew it but I apparently had no idea
On Thu, Oct 11, 2012 at 6:11 PM, Valentin Villenave
valen...@villenave.net wrote:
On Tue, Oct 9, 2012 at 8:19 AM, m...@mikesolomon.org
m...@mikesolomon.org wrote:
Just a quick ping to let you know that I'm not dead - I've been swamped w/
work recently and just got engaged so I'm planning out
On Thu, Oct 11, 2012 at 09:11:27AM +0100, Phil Holmes wrote:
Please see http://code.google.com/p/lilypond/issues/detail?id=2885.
GUB is broken and does not currently build the full output that it
should. It could be fixed by reverting Jan's commit, but that seems
the wrong approach - he
For 20:00 MDT Sunday October 14
Defect:
Issue 2889
http://code.google.com/p/lilypond/issues/detail?id=2889: Bad unicode
char value in error message - R 6625078
http://codereview.appspot.com/6625078/
Enhancement:
Issue 2790
http://code.google.com/p/lilypond/issues/detail?id=2790:
\tweak Accidental.color #red cis
vs.
\override Voice.Accidental color #red
\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.
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.? Is this too expensive? Or is
16 matches
Mail list logo
