From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: How about lifting the limit of 35 tasks in org-clock-history?
Date: Thu, 06 Sep 2018 16:18:08 +0200
Message-ID: <87zhwuu2u7.fsf@nicolasgoaziou.fr>
References: <87h8jbjczo.fsf@mbork.pl> <87pnxwvzij.fsf@nicolasgoaziou.fr>
	<87zhx0ymvc.fsf@mbork.pl>
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]:53759)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1fxv6u-000695-9J
	for emacs-orgmode@gnu.org; Thu, 06 Sep 2018 10:18:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1fxv6q-0006Q2-69
	for emacs-orgmode@gnu.org; Thu, 06 Sep 2018 10:18:16 -0400
Received: from relay2-d.mail.gandi.net ([217.70.183.194]:33861)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1fxv6p-0006OR-Ua
	for emacs-orgmode@gnu.org; Thu, 06 Sep 2018 10:18:12 -0400
In-Reply-To: <87zhx0ymvc.fsf@mbork.pl> (Marcin Borkowski's message of "Sun, 02
	Sep 2018 16:50:31 +0200")
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: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>

Hello,

Marcin Borkowski <mbork@mbork.pl> writes:

> I decided to put a warning about this in the docstring in my patch.  My
> assumption was that this is enough.  If a user wants to change the
> default, he will most probably see the docstring and will have to
> actively ignore the warning.

I don't think this is enough. As you put it, it instills doubt without
explaining anything. Why 35? Why "may not work"? What "may not work"?

> I do not use the vanilla Org way of selecting tasks to clock from
> history - I use org-mru-clock, for which the restriction doesn't make
> sense.  So we have something else to use,

I meant "have something else to use out of the box". I.e., not with an
external library.

I agree with the idea of removing this limitation, but I'm not convinced
your patch is ideal yet.

Regards,

-- 
Nicolas Goaziou