lilypond-user
[Top][All Lists]
Advanced

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

Re: How to increase the distance between the last note of a measure and


From: David Kastrup
Subject: Re: How to increase the distance between the last note of a measure and the following bar line
Date: Fri, 13 Dec 2024 23:30:43 +0100
User-agent: Gnus/5.13 (Gnus v5.13)

Trevor Bača <trevorbaca@gmail.com> writes:

> On Fri, Dec 13, 2024 at 3:46 PM David Kastrup <dak@gnu.org> wrote:
>>
>> Why would you want to list a property that has no effect on a grob?
>>
>
> David, please go look at the IR 3.1 entry for TupletBracket ...
>
> https://lilypond.org/doc/v2.24/Documentation/internals/tupletbracket
>
> ... and tell me where on that page users learn that they have the ability
> to override the color of a tuplet bracket to red.
>
> Go ahead. Where is that information provided?

This is the last answer I will provide to this thread since I am sick of
the insinuation that the documentation of LilyPond is intended to annoy
people.

Can you please try not to switch the topic around with every post?
First you complain that not every property of a grob is listed.  Then
you complain that not every property having an effect is listed.

Then you post dares in order to show that I am talking BS.

So let us take the path here: the bottom of that page says

    This object supports the following interface(s): grob-interface,
    line-interface, outside-staff-interface, spanner-interface and
    tuplet-bracket-interface.

If you click on grob-interface, you get a long explanation of what
constitutes a grob, followed by a list of user-settable properties
including

     color (color)

        The color of this grob.

That an interface has properties does not mean that all of the
properties will be effective on all grobs having the interface.  You
think you can come up with a better way of autogenerating LilyPond's
documentation, but all you come up with is essentially "someone™ should
write and maintain a better version of all the internal documentation
manually".

The way to achieve this is to volunteer, not to complain.  But even then
it would be a maintainability nightmare.  We autogenerate the internals
documentation for a reason.  It is at least accurate.

-- 
David Kastrup



reply via email to

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