[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: how to make decisions?
From: |
David Kastrup |
Subject: |
Re: how to make decisions? |
Date: |
Wed, 05 Sep 2012 18:44:25 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) |
Francisco Vila <address@hidden> writes:
> 2012/9/4 Trevor Daniels <address@hidden>:
>> So what problems do the users have, exactly? We should address this
>> question first. Janek apparently has his list, which would be a good start.
>> But we should not invent problems where they don't exist. I've probably
>> read every email on the user list for the last 4 years, and
>> inconsistent parser
>> rules have not figured prominently. Another example is the considerable
>> discussion so far about pre- and post-fix notation. Again, has this been a
>> problem prominent on the user list? I don't think so. So why try
>> to solve it?
>> Especially in ways that would screw all existing code. In fact, I
>> don't think
>> /users/ have any serious problems with the syntax as it currently exists,
>> other than getting to grips with it initially.
>
> Very true, in my opinion.
>
> For newcomers, the whole paradigm is a challenge. However, once they
> have the basics, musicians can learn the rules.
>
> \offtopic {
> New Spanish users find it difficult to get used to very common
> keystrokes which are only under AltGr in Spanish keyboards. So, lesson
> zero for the language from a practical POV is:
>
> {{{{
> }}}}
> \\\\
> {}{}{}{}
> \{} \{} \{}
>
> Now you are prepared to write \relative f { c }.
>
> What I once found embarrassing was to try \key d (and no \major or
> \minor afterwards) and fail to compile because, in my mind, "in D"
> means \key d \major with \major by default. Then I learned that \key
> has two non-optional arguments
It has two optional ones. Being in end position, they can only be
skipped by an explicit \default. If I remember correctly, skipping just
one caused an error message, so \key \default works, but \key c\default
doesn't.
> and now I think optional arguments are problematic.
>
> Regarding \relative optional_pitch {}, I think the optional pitch is
> very problematic and now it's time to mandate a pitch argument, forbid
> the obsolete form "\relative {}" and convert-ly it into "\relative f
> {}".
That does not make sense. The obsolete form "\relative {}" is to be
converted to "\relative c' {}" if at all. I _wish_ it would have been
defined as "\relative f {}" since that is logically very much related to
leaving the pitch off altogether. But history has decided otherwise.
--
David Kastrup
- Re: how to make decisions?, (continued)
- Re: how to make decisions?, Keith OHara, 2012/09/05
- Re: how to make decisions?, Trevor Daniels, 2012/09/05
- Re: how to make decisions?, Keith OHara, 2012/09/05
- Require delimiters to clarify context? [was: how to make decisions?], Trevor Daniels, 2012/09/05
- Re: Require delimiters to clarify context? [was: how to make decisions?], Keith OHara, 2012/09/05
- Re: how to make decisions?, David Kastrup, 2012/09/05
- Re: how to make decisions?, Han-Wen Nienhuys, 2012/09/05
- Re: how to make decisions?, Francisco Vila, 2012/09/05
- Re: how to make decisions?,
David Kastrup <=
- Re: how to make decisions?, Keith OHara, 2012/09/05
- Re: how to make decisions? (was: [GLISS] differentiating pre/post/neutral commands), Han-Wen Nienhuys, 2012/09/03
- Re: how to make decisions? (was: [GLISS] differentiating pre/post/neutral commands), Janek Warchoł, 2012/09/03
- Re: how to make decisions?, David Kastrup, 2012/09/03
Re: [GLISS] differentiating pre/post/neutral commands, Xavier Scheuer, 2012/09/01
Re: [GLISS] differentiating pre/post/neutral commands, Nicolas Sceaux, 2012/09/01