> Can be typed pretty rapidly too: hold down right shift with your little
> finger and <> fall under the index and middle fingers.
..not everyone uses us keyboard
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo
Why not use an empty pair of braces, which at the moment are just ignored by
the parser, to dignify chord repetition:
<> gives
3<> gives
c <> gives c - ie <> ignored as now if preceding element is
not a chord
Can be typed pretty rapidly too: hold down right shift with your little
fing
Anthony W. Youngman schrieb:
In message <49da120a.7090...@hohlart.de>, Marc Hohl
writes
1) personally, I would use the "%", but this is the comment sign and
can't be used.
(perhaps this would be even possible, but ... NO!)
Oh my gosh, please, NOOO
As Han-Wen has said, parsing is impor
In message <49da120a.7090...@hohlart.de>, Marc Hohl
writes
1) personally, I would use the "%", but this is the comment sign and
can't be used.
(perhaps this would be even possible, but ... NO!)
Oh my gosh, please, NOOO
As Han-Wen has said, parsing is important. In another life I work w
I would avoid getting in this discussion before the feature is
complete. Just call it \r (using an identifier or keyword), and see
how it works in practice. When it is debugged, think of a character.
The advantage of not using a letter a-z is that there are no backward
compat problems with sourc
Despite the fact that it would cause massive problems in parsing, a line
like
c4 4 4 4
is not quite readable for me.
As lilypond is THE tool for typesetting beautiful scores, the source
file should
reflect the beauty. So I should be able to grasp the score at first sight,
and in my opinion,
On Mon, Apr 6, 2009 at 9:23 AM, Jan Nieuwenhuizen
wrote:
>> as long as I have anything to do with LilyPond, I will veto changes
>> like this that introduce inconsistent whitespace handling in the
>> syntax.
>
> What was the problem with this again? It is not so much inconsistent
> whitepace, it's
Op zondag 05-04-2009 om 18:13 uur [tijdzone -0300], schreef Han-Wen
Nienhuys:
> as long as I have anything to do with LilyPond, I will veto changes
> like this that introduce inconsistent whitespace handling in the
> syntax.
What was the problem with this again? It is not so much inconsistent
wh
