From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: How about lifting the limit of 35 tasks in org-clock-history? Date: Wed, 03 Oct 2018 12:51:27 +0200 Message-ID: <87woqznw0g.fsf@nicolasgoaziou.fr> References: <87h8jbjczo.fsf@mbork.pl> <87pnxwvzij.fsf@nicolasgoaziou.fr> <87zhx0ymvc.fsf@mbork.pl> <87zhwuu2u7.fsf@nicolasgoaziou.fr> <875zykzxjr.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41452) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g7eqb-0007hy-8z for emacs-orgmode@gnu.org; Wed, 03 Oct 2018 06:57:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g7ekc-0005pA-L2 for emacs-orgmode@gnu.org; Wed, 03 Oct 2018 06:51:34 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:57779) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1g7ekc-0005oM-Dj for emacs-orgmode@gnu.org; Wed, 03 Oct 2018 06:51:30 -0400 In-Reply-To: <875zykzxjr.fsf@mbork.pl> (Marcin Borkowski's message of "Tue, 02 Oct 2018 08:12:56 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Marcin Borkowski Cc: Org-Mode mailing list Hello, Marcin Borkowski 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. Regards, -- Nicolas Goaziou