\acceptances for letting one context-def share accepts for another

\acceptances for letting one context-def share accepts for another


Also contains commits:

NR Changing Defaults: document \acceptances


Add regtest for \acceptances


Add output-module? definition to detect midi/layout

[dak, 2015-08-14 13:53:10]

Fix regtest

[pwm, 2015-08-17 14:10:17]

LGTM.  This will make using custom modified contexts much simpler, thanks!  

My only suggestion is that the plural form of "acceptances" sounds odd if there
are more than one:

\layout {
  % ... 
  \acceptances "MyStaff" "Staff"
  \acceptances "MyLyrics" "Lyrics"
}

What about \accept-like instead?

\layout {
  % ... 
  \accept-like "Staff" "MyStaff"
  \accept-like "Lyrics" "MyLyrics"
}

This is the name you suggested (for a different approach) here: 
http://lists.gnu.org/archive/html/bug-lilypond/2015-03/msg00020.html

I find it clearer and easier to understand than \acceptances.

[dak, 2015-08-17 14:32:38]

On 2015/08/17 14:10:17, pwm wrote:
> LGTM.  This will make using custom modified contexts much simpler, thanks!  
> 
> My only suggestion is that the plural form of "acceptances" sounds odd if
there
> are more than one:
> 
> \layout {
>   % ... 
>   \acceptances "MyStaff" "Staff"
>   \acceptances "MyLyrics" "Lyrics"
> }
> 
> What about \accept-like instead?
> 
> \layout {
>   % ... 
>   \accept-like "Staff" "MyStaff"
>   \accept-like "Lyrics" "MyLyrics"
> }
> 
> This is the name you suggested (for a different approach) here: 
> http://lists.gnu.org/archive/html/bug-lilypond/2015-03/msg00020.html
> 
> I find it clearer and easier to understand than \acceptances.

The problem I have is that it's hard to remember the order of arguments.  So I
decided to use assignment-like order.  A reasonably good name would have been
just \accepts but that is already taken.


\acceptances is gruesome but so far I cannot think of anything that I'd prefer
in good conscience.

[dak, 2015-08-17 14:36:39]

On 2015/08/17 14:10:17, pwm wrote:
> LGTM.  This will make using custom modified contexts much simpler, thanks!  
> 
> My only suggestion is that the plural form of "acceptances" sounds odd if
there
> are more than one:
> 
> \layout {
>   % ... 
>   \acceptances "MyStaff" "Staff"
>   \acceptances "MyLyrics" "Lyrics"
> }
> 
> What about \accept-like instead?
> 
> \layout {
>   % ... 
>   \accept-like "Staff" "MyStaff"
>   \accept-like "Lyrics" "MyLyrics"
> }
> 
> This is the name you suggested (for a different approach) here: 
> http://lists.gnu.org/archive/html/bug-lilypond/2015-03/msg00020.html
> 
> I find it clearer and easier to understand than \acceptances.

The plural is because it copies the acceptances of Staff (which is accepted by
GrandStaff, StaffGroup, PianoStaff, Score and stuff) and makes them acceptances
of MyStaff.

[dan_faithful.be, 2015-08-17 14:53:22]

On Aug 17, 2015, at 10:32 , dak@gnu.org wrote:
> 
> The problem I have is that it's hard to remember the order of arguments.
> So I decided to use assignment-like order.  A reasonably good name
> would have been just \accepts but that is already taken.

\accepts could be renamed if it would help, right?  (I’m at work and can’t spend
time brainstorming, but I couldn’t resist mentioning it.)

[dak, 2015-08-17 22:48:12]

On 2015/08/17 14:53:22, dan_faithful.be wrote:
> On Aug 17, 2015, at 10:32 , mailto:dak@gnu.org wrote:
> > 
> > The problem I have is that it's hard to remember the order of arguments.
> > So I decided to use assignment-like order.  A reasonably good name
> > would have been just \accepts but that is already taken.
> 
> \accepts could be renamed if it would help, right?  (I’m at work and can’t
spend
> time brainstorming, but I couldn’t resist mentioning it.)

Not worth throwing everything overboard.

Maybe \accept-equally "MyStaff" "Staff" ?  Still cumbersome but less awkward,
and "equally" is more compatible with the new-old order than "like".

[dan_faithful.be, 2015-08-17 23:36:59]

> On Aug 17, 2015, at 18:48 , dak@gnu.org wrote:
> 
> On 2015/08/17 14:53:22, dan_faithful.be wrote:
>> On Aug 17, 2015, at 10:32 , mailto:dak@gnu.org wrote:
>> >
>> > The problem I have is that it's hard to remember the order of
> arguments.
[…]
> Maybe \accept-equally "MyStaff" "Staff" ?  Still cumbersome but less
> awkward, and "equally" is more compatible with the new-old order than
> "like".

\accept-equally sounds like it makes the two context types interchangeable;
would it make sense to implement that instead?  (Maybe by running the current
algorithm once in each order?)  Then this problem disappears.

If you really want a one-way relationship, I can’t think of a single word that
makes the order obvious.  \accept X \as Y seems obvious.  Maybe \accept X = Y.
— 
Dan

[pwm, 2015-08-18 14:38:13]

I brainstormed some ideas:

\copy-acceptability
\copy-acceptance
\copy-acceptances
\acceptable-where
\accepts-alias
\acceptability-alias

...but I'm not sure any of those are better than the ones mentioned already. 
FWIW, I like how it is easier for me to understand what the command does with
\accept-equally or \accept-like, than with \acceptances.  Seems there are
trade-offs with any option.

[dak, 2015-08-18 14:46:02]

On 2015/08/18 14:38:13, pwm wrote:
> I brainstormed some ideas:
> 
> \copy-acceptability
> \copy-acceptance
> \copy-acceptances
> \acceptable-where
> \accepts-alias
> \acceptability-alias
> 
> ...but I'm not sure any of those are better than the ones mentioned already. 
> FWIW, I like how it is easier for me to understand what the command does with
> \accept-equally or \accept-like, than with \acceptances.  Seems there are
> trade-offs with any option.

Well, at least \acceptability would seem nicer than \acceptances.

\inherit-acceptability

would be somewhat descriptive but it is awkward in the sorting order and rather
verbose.

[pwm, 2015-08-19 01:45:05]

On 2015/08/18 14:46:02, dak wrote:
> 
> Well, at least \acceptability would seem nicer than \acceptances.
> 
> \inherit-acceptability
> 
> would be somewhat descriptive but it is awkward in the sorting order and
rather
> verbose.

Hmmm... 

  \inherit-acceptability "MyStaff" "Staff" 

is pretty good, if you ask me.  Easy to understand what it's used for and the
order of arguments is fairly clear.  I could see 

  \copy-acceptability "Staff" "MyStaff" 

working as well.  One thing that helps is this command likely won't be typed all
that frequently, so arguably concision/verbosity is less important.