On Thu, Oct 4, 2012 at 3:26 PM, David Kastrup d...@gnu.org wrote:
It's likely a more important consideration to divide the Guile and
LilyPond namespace rather than the LilyPond and user space.
To wit, convert
xxx = \something
into
#(define $xxx $something)
I assume that this would mean
Janek Warchoł janek.lilyp...@gmail.com writes:
On Thu, Oct 4, 2012 at 3:26 PM, David Kastrup d...@gnu.org wrote:
It's likely a more important consideration to divide the Guile and
LilyPond namespace rather than the LilyPond and user space.
To wit, convert
xxx = \something
into
#(define
On Fri, Oct 5, 2012 at 4:26 PM, David Kastrup d...@gnu.org wrote:
Janek Warchoł janek.lilyp...@gmail.com writes:
I assume that this would mean having to use #(define ) every time
we wanted to define a variable/command (e.g. notes = { c d e } and red
= \twear #'color #red).
Huh? Why?
I
Graham Percival gra...@percival-music.ca writes:
On Sat, Sep 15, 2012 at 10:25:17PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
For example, what about my hated idea of splitting namespaces of
music fuctions and identifiers? I'm not fond of perl, but
On Sun, Sep 23, 2012 at 11:21 PM, Graham Percival
gra...@percival-music.ca wrote:
Nothing's stopping us from having the normal \commands (including
both predefs and user-created and user-redefined), along with
$commands (which is completely empty and available for any user
definitions).
I see
Janek Warchoł janek.lilyp...@gmail.com writes:
On Sun, Sep 23, 2012 at 11:21 PM, Graham Percival
gra...@percival-music.ca wrote:
Nothing's stopping us from having the normal \commands (including
both predefs and user-created and user-redefined), along with
$commands (which is completely
Graham Percival wrote Sunday, September 23, 2012 3:20 AM
On Sat, Sep 15, 2012 at 10:25:17PM +0200, David Kastrup wrote:
I don't want to differentiate between predefined and user-defined
commands.
That's certainly a consistent view to take, but it might be worth
discussing that further
On Sun, Sep 23, 2012 at 09:19:03AM +0100, Sue Daniels wrote:
Graham Percival wrote Sunday, September 23, 2012 3:20 AM
That's certainly a consistent view to take, but it might be worth
discussing that further at some point. If there's a separate
namespace then I can't see any technical
On Sat, Sep 15, 2012 at 10:25:17PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
For example, what about my hated idea of splitting namespaces of
music fuctions and identifiers? I'm not fond of perl, but
something like this is unambiguous:
$F =
On Sat, Sep 15, 2012 at 07:56:52PM +0200, Werner LEMBERG wrote:
Distinguishing \f and \F while ignoring case is going to be a rather
difficult operation. While I generally try to accommodate a lot of
make that work requests, there are limits to what one can achieve
when fighting not
Graham Percival graham at percival-music.ca writes:
On Sat, Sep 15, 2012 at 07:56:52PM +0200, Werner LEMBERG wrote:
Distinguishing \f and \F while ignoring case is going to be a rather
difficult operation.
I agree that distinguishing \f and \F is difficult. However, if
the
I agree that distinguishing \f and \F is difficult. [...]
I did not hear any serious desire to allow both \f and \F as
distinct.
Ugh, it seems that you haven't read my strong objections a few hours
ago.
To the contrary, the request was to accept (and complain) if we
mistype
\SlurDown
Werner LEMBERG wl at gnu.org writes:
I did not hear any serious desire to allow both \f and \F as
distinct.
Ugh, it seems that you haven't read my strong objections a few hours
ago.
You mostly objected to LilyPond /ignoring/ case, for reasons that made sense.
I guess you did say:
the
Graham Percival gra...@percival-music.ca writes:
On Sat, Sep 15, 2012 at 07:56:52PM +0200, Werner LEMBERG wrote:
Distinguishing \f and \F while ignoring case is going to be a rather
difficult operation. While I generally try to accommodate a lot of
make that work requests, there are
Keith OHara k-ohara5...@oco.net writes:
Werner LEMBERG wl at gnu.org writes:
Please no heuristics.
By we I meant us humans in charge of the software. We humans would
avoid choosing names like keySignature and KeySignature distinguished
only by case.
No question about that. Coming up
I did not hear any serious desire to allow both \f and \F as
distinct.
Ugh, it seems that you haven't read my strong objections a few
hours ago.
You mostly objected to LilyPond /ignoring/ case, for reasons that
made sense.
Oops, yes.
Werner
16 matches
Mail list logo
