Graham Percival wrote Thu, 12 Jun 2008 08:48:12 +0200
Arjan Bos <[EMAIL PROTECTED]> wrote:
If it were only for `#' denoted strings, I agree with you, but there
are plenty of other inconsistencies in the LilyPond syntax that are
fully understandable from the viewpoint of the program, but mak
On Thu, 12 Jun 2008 08:48:12 +0200
Arjan Bos <[EMAIL PROTECTED]> wrote:
> If it were only for `#' denoted strings, I agree with you, but there
> are plenty of other inconsistencies in the LilyPond syntax that are
> fully understandable from the viewpoint of the program, but make
> almost no
On 11 jun 2008, at 23:48, Graham Percival wrote:
Rewriting the parser for such a trivial thing would be a waste of
resources. Just get used to typing #, just like {} or ,' or any
other piece of lilypond input. The docs are supposed to use #""
all the time, to reinforce this point.
If it we
I Wrote:
(...)
Va falloir ajouter les doigtés dans les traductions de la doc, alors, et
(...)
Shame on me!
Wrong addresses...(and Snippet?id=435)
--
Sorry,
FM
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/lis
Bonjour,
Valentin Villenave a écrit :
Yes, French keyboard layout is much more annoying (it requires
twisting your right hand to have the thumb on AltGr and the middle
finger on the alpha-num "3" key).
Va falloir ajouter les doigtés dans les traductions de la doc, alors, et
prévoir des sous-p
2008/6/11 Graham Percival <[EMAIL PROTECTED]>:
> Oh, come on! What is so hard about typing #? On an English
> keyboard, you already need to be pressing the shift key to get the
> " that you'll type for your string anyway.
Yes, French keyboard layout is much more annoying (it requires
twisting yo
On Wed, 11 Jun 2008 23:28:00 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/6/11 Nicolas Sceaux <[EMAIL PROTECTED]>:
> > Tis its extensibility that make LilyPond more likely to be able to
> > fit the more users needs, and its extensibility is made possible
> > because LilyPond is pro
2008/6/11 Nicolas Sceaux <[EMAIL PROTECTED]>:
> Bullshit.
There may be one point on which I tend to agree with Arjan: it's not
always handy to constantly put a hash character before text strings.
If I remember correctly (but I may have been hallucinating), you have
some functions in your framewor
Le 11 juin 08 à 13:21, Arjan Bos a écrit :
May I chime in a bit here? This prodding of the scheme interpreter
is one of the few things I do not like in the lilypond syntax. I do
love LilyPond and as a programmer at heart, I adore its syntax.
However, as a programmer, it is my duty to let th
May I chime in a bit here? This prodding of the scheme interpreter is
one of the few things I do not like in the lilypond syntax. I do love
LilyPond and as a programmer at heart, I adore its syntax. However, as
a programmer, it is my duty to let the computer do the work instead of
the user.
2008/6/11 Stefan Thomas <[EMAIL PROTECTED]>:
> But unfortunately this doesn't work:
> langsamer = { \movement "subito meno mosso" "4" #69 }
You have to add a # before each quoted string:
langsamer = { \movement #"subito meno mosso" #"4" #69 }
It's in order to tell the Scheme interpreter: "hey
11 matches
Mail list logo
