emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] observations on updating to recent org


From: Nicolas Goaziou
Subject: Re: [O] observations on updating to recent org
Date: Wed, 23 Apr 2014 18:16:11 +0200

Hello,

Greg Troxel <address@hidden> writes:

> 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.

You may want to use ELP to instrument Org and report where most time is
spent.

> I noticed that TODO entries got exported multiple times, apparently once
> for each inactive timestamp.  (I realize I need to prepare a minimal
> example.)

This is to be expected. Each plain timestamp defines a new VEVENT block.

By default, it shouldn't do this for inactive timestamps, though. See
`org-icalendar-with-timestamps'.

> 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.

Note that UID storing is off by default.

> 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.

This is not really possible without some sacrifices (which Bastien may
or may not want to do).  See other messages in this thread.

Also, since you don't need UID anyway, why is that a problem anymore?
I'm a bit confused here.


Regards,

-- 
Nicolas Goaziou



reply via email to

[Prev in Thread] Current Thread [Next in Thread]