From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Adams Subject: Re: [ANN] Agenda speed up Date: Sun, 27 Aug 2017 22:53:54 +0200 Message-ID: <20170827205354.GS16429@volibear> References: <87h8wtugst.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46249) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dm4ZZ-0003gh-RC for emacs-orgmode@gnu.org; Sun, 27 Aug 2017 16:54:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dm4ZW-0008NZ-MN for emacs-orgmode@gnu.org; Sun, 27 Aug 2017 16:54:21 -0400 Received: from elephant.birch.relay.mailchannels.net ([23.83.209.57]:18936) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dm4ZW-0008FT-AF for emacs-orgmode@gnu.org; Sun, 27 Aug 2017 16:54:18 -0400 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 72CC8127D5E for ; Sun, 27 Aug 2017 20:54:00 +0000 (UTC) Received: from kefka.asoshared.com (unknown [100.96.139.204]) (Authenticated sender: asmallorange) by relay.mailchannels.net (Postfix) with ESMTPA id 27D3C127961 for ; Sun, 27 Aug 2017 20:54:00 +0000 (UTC) Received: from [31.187.192.61] (port=43440 helo=localhost) by kefka.asoshared.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1dm4ZC-002cxO-TG for emacs-orgmode@gnu.org; Sun, 27 Aug 2017 16:53:59 -0400 Content-Disposition: inline In-Reply-To: <87h8wtugst.fsf@nicolasgoaziou.fr> 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: emacs-orgmode@gnu.org On Sun, Aug 27, 2017 at 06:16:50PM +0200, Nicolas Goaziou wrote: > Hello, > > I rewrote the part responsible for agenda generation in "org-agenda.el". > Basically, I refactored some hot loops and introduced a cache mechanism > for data extracted out of agenda files. Sounds awesome. > The only thing that is expected to be defective is > `org-agenda-include-inactive-timestamps'. It has no effect at the > moment. I can activate it again, but I'm wondering if it's worth the > overhead. It is already possible to display clocks and closed timestamps > in the agenda. Other inactive timestamps could be ignored from the > agenda altogether. This is their sole purpose, after all. WDYT? Count me in as another major user of inactive timestamps. I use active timestamps only for appointments, and when I'm working on a task I constantly add inactive timestamps via single keypress macro. When I review what has happened in the agenda, I only toggle on the inactives when I need to see them. Professionally they have been lifesavers. When did I execute that command on that host? When did the user call? What hours do I need to bill? Etc. Please consider preserving the existing inactive timestamps functionality. ------------------------------------------------------------------ Russell Adams RLAdams@AdamsInfoServ.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3