On 22-Aug-05, at 2:17 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
If it would be slightly faster, then I'd say that we should change
the definitions
in ly/* , but we should leave the input/* snippets (ie the
user-viewed stuff)
alone. #up is easier to type than #UP. :)
actually, th
Graham Percival wrote:
1) is #up likely to stop working in the future? It works now, so
evidently there's
a lowercase to uppercase translation happening somewhere.
2) would it be faster to process #UP instead of #up (ie avoiding that
translation) ?
If it would be slightly faster, then I'd
On 19-Aug-05, at 2:49 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
I think it's a good idea to continue using #up and #down. This
reinforces the general
form of
\override (engraver.)grob #'property = #value
Hmm. There's still a question of style, in lily-library.scm we do
(define-pu
Graham Percival wrote:
On 18-Aug-05, at 5:21 PM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
Log message:
Direction #-1 to #down.
actually, in most cases, \down and \up should also work.
Hmm, I didn't know that.
That might be more lilyesque.
I disagree -- we use #3 and #'(
On 18-Aug-05, at 5:21 PM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
Log message:
Direction #-1 to #down.
actually, in most cases, \down and \up should also work.
Hmm, I didn't know that.
That might be more lilyesque.
I disagree -- we use #3 and #'(1 . -2) for many things
Graham Percival wrote:
Log message:
Direction #-1 to #down.
actually, in most cases, \down and \up should also work. That might be
more lilyesque.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
lilypond-devel
