From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcin Borkowski <mbork@mbork.pl>
Subject: Re: How about lifting the limit of 35 tasks in org-clock-history?
Date: Wed, 03 Oct 2018 14:19:57 +0200
Message-ID: <87murvb4sy.fsf@mbork.pl>
References: <87h8jbjczo.fsf@mbork.pl> <87pnxwvzij.fsf@nicolasgoaziou.fr>
	<87zhx0ymvc.fsf@mbork.pl> <87zhwuu2u7.fsf@nicolasgoaziou.fr>
	<875zykzxjr.fsf@mbork.pl> <87woqznw0g.fsf@nicolasgoaziou.fr>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60749)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mbork@mbork.pl>) id 1g7g9p-00038j-2P
	for emacs-orgmode@gnu.org; Wed, 03 Oct 2018 08:21:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mbork@mbork.pl>) id 1g7g9k-0004he-TB
	for emacs-orgmode@gnu.org; Wed, 03 Oct 2018 08:21:36 -0400
Received: from mail.mojserwer.eu ([195.110.48.8]:33650)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mbork@mbork.pl>) id 1g7g9k-0004gJ-L1
	for emacs-orgmode@gnu.org; Wed, 03 Oct 2018 08:21:32 -0400
In-reply-to: <87woqznw0g.fsf@nicolasgoaziou.fr>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>


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