lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Add a \voicify command (issue 320820043 by address@hidden)


From: David Kastrup
Subject: Re: Add a \voicify command (issue 320820043 by address@hidden)
Date: Fri, 07 Apr 2017 22:15:00 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

"Trevor Daniels" <address@hidden> writes:

> David, you wrote Thursday, April 06, 2017 4:54 PM
>
>> You could try separate commands \voicifyUp and \voicifyDown .  I am not
>> sure whether or not \voicify should not be \voices or \voicing or
>> \voicings instead, possibly making for nicer compounds like that.
>> 
>> I mean, something like
>> 
>> \voices 1,3,4 ...
>
> Although you later argued cogently against compounds like \voicesUp I
> think \voices is a better choice than \voicify anyway, simply because
> it expresses its operation more clearly (not sure what meaning the word
> "voicify" would trigger in the mind - in Google it enables voice dictation;
> in Twitter it applies a filter, for example).  
>
> In other words \voices stands better than \voicify on its own merits.

One argument in favor of \voicify would be that \voices sounds like
setting a state rather than modifying a music expression.  It would be a
bit more talkative to say something like

\withVoices 1,3,4
<< \\ \\ >>

rather than

\voices 1,3,4
<< \\ \\ >>

So I'm not completely happy with \voices though all in all it's probably
still my favorite.

I did not come up with "voicify" all on my own: the internal function
for doing << \\ \\ >> was named like that before, so I just added a
user-level command using the same verbiage.

If we ever add a command for changing the default,

\defaultVoices ...

would definitely be less awkward than

\defaultVoicify ...
or
\defaultVoicification ...

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]