Re: add fermata markup commands (issue 344160043 by lilypond@maltemeyn.de)

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: add fermata markup commands (issue 344160043 by lilypond@maltemeyn.de)

Malte Meyn-3
On 2019/04/29 06:14:40, Malte Meyn wrote:
> fix documentation

This time I did a make doc-stage-1 for english and german docs. I hope
that’s enough …

https://codereview.appspot.com/344160043/
_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: add fermata markup commands (issue 344160043 by lilypond@maltemeyn.de)

lemzwerg
I wonder whether it makes sense to use more camel case for the macro
names, this is, \shortFermata, \longFermata, etc.

https://codereview.appspot.com/344160043/

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: add fermata markup commands (issue 344160043 by lilypond@maltemeyn.de)

Malte Meyn-3
In reply to this post by Malte Meyn-3
On 2019/04/29 20:15:30, lemzwerg wrote:
> I wonder whether it makes sense to use more camel case for the macro
names, this
> is, \shortFermata, \longFermata, etc.

Hm … that would need new names also for other scripts like \reverseTurn,
\halfOpen and probably many others like \prallMordent, \prallPrall,
\upMordent, \snapPizzicato, \signumCongruentiae.

What happened to GLISS? camelCase vs. lowercase and others is mentioned
in section 14.7 of the CG …

https://codereview.appspot.com/344160043/
_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: add fermata markup commands (issue 344160043 by lilypond@maltemeyn.de)

David Kastrup
[hidden email] writes:

> On 2019/04/29 20:15:30, lemzwerg wrote:
>> I wonder whether it makes sense to use more camel case for the macro
> names, this
>> is, \shortFermata, \longFermata, etc.
>
> Hm … that would need new names also for other scripts like \reverseTurn,
> \halfOpen and probably many others like \prallMordent, \prallPrall,
> \upMordent, \snapPizzicato, \signumCongruentiae.
>
> What happened to GLISS? camelCase vs. lowercase and others is mentioned
> in section 14.7 of the CG …
>
> https://codereview.appspot.com/344160043/

GLISS has fallen a bit by the wayside: as I understand it, it was to a
good degree an endeavor driven by non-programmers (at least not core
programmers) to get focused proposals for better human interfaces for
LilyPond that programmers then can tackle.  The composition of core
programmers and users and the balance of things being hardwired into
LilyPond (where simple changes required a core programmer) and things
being programmable at an advanced user level as long as they met certain
limitations has significantly shifted since then, and so have the
discussion and decision and code making processes.

Like with many slow-moving changes, not everything that was a good idea
remains as desirable as it once was and as the way to do things changes,
the set of people enjoying doing them also changes, partly because of a
change in the actual matter at hand, partly because of changes in the
community doing them.

Whether you want to call it GLISS or not, consistency in interfaces does
make some sense but it usually is a good idea to work on those mostly
when there is a comparatively fresh stable branch out.

--
David Kastrup

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel