Re: -dcrop not included in 2.20?

[Tomohiro Tatejima]

I'm sorry for late reply.

I am not sure I have understood your opinions correctly, but 2.20 is
going to be released without including the feature?
If so, should we remove the entry listed in changes.tely:1061-1063,
"An argument, @code{-dcrop} ..."?

Tomohiro Tatejima

2017-11-14 0:52 GMT+09:00 Étienne Beaulé <address@hidden>:
> There isn't anything else to the option that I can think of; it does exactly
> what I intended it to do, nothing more or less. So, I'd keep it in the
> current form. I can't really see how else it could fit in the code without
> problems arising.
>
> Étienne
>
> 2017-11-13 4:54 GMT-04:00 David Kastrup <address@hidden>:
>>
>> Tomohiro Tatejima <address@hidden> writes:
>>
>> > Hello,
>> >
>> > I found that the -dcrop option (Issue 5165) is not included in
>> > stable/2.20 branch although the feature is listed in the changes
>> > document.
>> >
>> > Will it be included in 2.20? or upcoming 2.21 (and therefore the entry
>> > of the documentation should be removed)?
>>
>> I've taken a look.  Currently I am undecided.  The code is separated
>> well enough and clearly does not get exercised without specifying the
>> option.  So it's not going to harm existing functionality.  I am not
>> sure it will stay around in exactly this form.  But, well, that's a weak
>> argument against it.
>>
>> --
>> David Kastrup
>>
>> _______________________________________________
>> lilypond-devel mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
>