On 2018-10-03, at 12:51, Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote:
> Hello, > > Marcin Borkowski <mb...@mbork.pl> writes: > >> I attach a patch with a more verbose docstring. >> >> It is perhaps still not ideal - in particular, the warning is not >> visible in the Customize interface - but I do not think this is a big >> deal. My line of thinking is that: >> >> - if a user wants to change this setting, they will either look up the >> docstring and understand the limitation (btw, even the built-in way >> works for org-clock-history-length as high as 76 or so, provided you >> have a really high frame), or >> >> - use Customize, which is potentially a trouble - but in that case, >> I would assume that the user fiddles with org-clock-history-length >> because they clock in many tasks, and then they will see that the list >> in the *Clock Task Select* buffer is too long anyway, and dial the >> setting down. > > It sounds good. I applied your patch. Thank you. Thanks, too! (Also for your extremely fast reply, comparing to my one;-).) Best, -- Marcin Borkowski http://mbork.pl