From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Troxel Subject: Re: observations on updating to recent org Date: Wed, 23 Apr 2014 11:55:18 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41079) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WczWF-0003Sp-Lh for emacs-orgmode@gnu.org; Wed, 23 Apr 2014 11:55:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WczWA-0001lF-Je for emacs-orgmode@gnu.org; Wed, 23 Apr 2014 11:55:31 -0400 Received: from fnord.ir.bbn.com ([192.1.100.210]:62328) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WczW9-0001kS-Vc for emacs-orgmode@gnu.org; Wed, 23 Apr 2014 11:55:26 -0400 In-Reply-To: (Greg Troxel's message of "Tue, 22 Apr 2014 13:43:17 -0400") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Greg Troxel writes: > Exporting to ical as a single file took a really long time, perhaps a > whole minute, whereas it used to take a second to a few seconds. The > resulting export did seem ok. I timed this. With 6161 lines in 14 org-mode files (about 2175 of which are due to PROPERTIES/ID/END), doing a combined export took 88s of cpu time. emacs-23.4.1, NetBSD 6, i386, plenty of RAM, Core i5 2.9 GHz. In contrast, starting up emacs and generating the agenda took 0.97s. I noticed that TODO entries got exported multiple times, apparently once for each inactive timestamp. (I realize I need to prepare a minimal example.) > I used to get an ID PROPERTIES entries for nodes that were exported to the > calendar, which was basically nodes that had an active timestamp. > But now I had a huge number of changes, adding ID to every node, even > those with no real content and just children. Is this a feature? Thanks for the comments; I see the point that this is hard.. For now, I've just turned off uid storing, because I don't sync the exported calendar, and I'll nuke the ID entries and properties drawers at some point; I find them distracting when editing. I wonder if there's some way to go back and store the UID when it actually needs to be generated, so that UIDs are only stored for entries that actually have been exported. I only want to export appointments, by which I mean entries with active timestamps, which are pretty few in number compared to nodes. Greg --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlNX4mYACgkQ+vesoDJhHiXEHACcD4edtMQLUm9mIeMd/igE7kgZ JdYAnA4fxMrAcfcbTUS22KnOpXDQKgDE =e5OU -----END PGP SIGNATURE----- --=-=-=--