Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@gnu.org writes:
Assuming this is just difficult, not impossible, what would be the way
to do it?
The major difficulty is to keep an association table between headlines
in the pristine original buffer, and headlines in
Nicolas Goaziou n.goaz...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Greg Troxel g...@ir.bbn.com writes:
I didn't try to turn this on. My icalendar-relevant settings are
(setq org-icalendar-alarm-time 10)
(setq org-icalendar-use-scheduled nil)
(setq
Hi Greg,
Greg Troxel g...@ir.bbn.com writes:
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
Hello,
Bastien b...@gnu.org writes:
Nicolas, do you remember why we added IDs to all headlines and not
just the one that we be exported in the .ics file?
It is a bit difficult to do otherwise.
We don't know beforehand what headlines are going to be exported. We get
this information when a
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@gnu.org writes:
Nicolas, do you remember why we added IDs to all headlines and not
just the one that we be exported in the .ics file?
It is a bit difficult to do otherwise.
Assuming this is just difficult, not
Bastien b...@gnu.org writes:
Assuming this is just difficult, not impossible, what would be the way
to do it?
The major difficulty is to keep an association table between headlines
in the pristine original buffer, and headlines in the copy being
exported. Note that hooks and Babel code may
Greg Troxel g...@ir.bbn.com 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
Hello,
Greg Troxel g...@ir.bbn.com 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
Nicolas Goaziou n.goaz...@gmail.com writes:
Greg Troxel g...@ir.bbn.com 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
Greg Troxel g...@ir.bbn.com writes:
I guess that's an interesting question about what makes sense. Here's
the actual todo entry, with just a few words redacted. I don't see why
someone would want VEVENTS for this kind of history, but I suppose maybe
that's what you get when you turn on
Nicolas Goaziou n.goaz...@gmail.com writes:
Greg Troxel g...@ir.bbn.com writes:
I didn't try to turn this on. My icalendar-relevant settings are
(setq org-icalendar-alarm-time 10)
(setq org-icalendar-use-scheduled nil)
(setq org-icalendar-use-deadline nil)
I am trying
I use org for the usual notes-to-self and TODO - nothing super fancy. I
had been running from master of the git repo, but in 2013-01 stopped
updating, probably because I had some issue. The recent release
provoked me to try again, and this note reports some issues.
I had been running (for no
12 matches
Mail list logo
