From: Marcin Borkowski <mbork@mbork.pl>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: How about lifting the limit of 35 tasks in org-clock-history?
Date: Wed, 03 Oct 2018 14:19:57 +0200 [thread overview]
Message-ID: <87murvb4sy.fsf@mbork.pl> (raw)
In-Reply-To: <87woqznw0g.fsf@nicolasgoaziou.fr>
On 2018-10-03, at 12:51, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Marcin Borkowski <mbork@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
prev parent reply other threads:[~2018-10-03 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 5:56 How about lifting the limit of 35 tasks in org-clock-history? Marcin Borkowski
2018-09-02 12:45 ` Nicolas Goaziou
2018-09-02 14:50 ` Marcin Borkowski
2018-09-06 14:11 ` Marcin Borkowski
2018-09-06 14:18 ` Nicolas Goaziou
2018-09-08 15:28 ` Marcin Borkowski
2018-10-02 6:12 ` Marcin Borkowski
2018-10-03 10:51 ` Nicolas Goaziou
2018-10-03 12:19 ` Marcin Borkowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87murvb4sy.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).