From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: observations on updating to recent org
Date: Wed, 23 Apr 2014 18:59:44 +0200 [thread overview]
Message-ID: <877g6gm16n.fsf@gmail.com> (raw)
In-Reply-To: <rmioazsui5n.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "Wed, 23 Apr 2014 12:25:56 -0400")
Greg Troxel <gdt@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 events from inactive timestamps.
>
> ***** TODO [#C] order more [redacted]
> SCHEDULED: <2014-04-28 Mon .+4w>
> - State "DONE" from "TODO" [2013-11-07 Thu 10:30]
> - State "DONE" from "TODO" [2013-08-05 Mon 16:27]
> - State "DONE" from "WAITING" [2013-06-04 Tue 10:27]
> - State "WAITING" from "TODO" [2013-05-28 Tue 11:19] \\
> ordered via [redacted]
> - State "DONE" from "TODO" [2013-03-25 Mon 23:16]
> laura did
> - State "DONE" from "WAITING" [2013-01-08 Tue 11:49]
> - State "WAITING" from "TODO" [2012-12-18 Tue 20:41] \\
> ordered
> - State "TODO" from "WAITING" [2012-09-20 Thu 13:05]
> - State "WAITING" from "TODO" [2012-09-13 Thu 10:01] \\
> ordered
> - State "DONE" from "TODO" [2012-07-12 Thu 10:39]
> - State "DONE" from "TODO" [2012-06-04 Mon 14:22]
> - State "DONE" from "TODO" [2012-03-27 Tue 08:54]
> - State "DONE" from "TODO" [2011-10-01 Sat 08:10]
> :PROPERTIES:
> :ID: b617c8e4-c8f2-11e0-8735-000476353fb4
> :LAST_REPEAT: [2013-11-07 Thu 10:30]
> :END:
By default, no VEVENT should be created from any timestamp in your
example.
>> By default, it shouldn't do this for inactive timestamps, though. See
>> `org-icalendar-with-timestamps'.
>
> 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 to get ics entries only for headlines with active
> timestamps.
It is a bug then. I'll look into it in a few hours.
> It's not a problem for me any more. It just seems really unfortunate
> for others in the general case to have extra content in every headline
> when it isn't necessary.
If there are few exported headlines in the document, it is also possible
to keep `org-icalendar-store-UID' to nil and add ID value manually for
each of them.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-04-23 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 17:43 observations on updating to recent org Greg Troxel
2014-04-23 6:16 ` Bastien
2014-04-23 7:47 ` Nicolas Goaziou
2014-04-23 8:17 ` Bastien
2014-04-23 11:58 ` Nicolas Goaziou
2014-05-06 9:22 ` Bastien
2014-04-23 15:55 ` Greg Troxel
2014-04-23 16:16 ` Nicolas Goaziou
2014-04-23 16:25 ` Greg Troxel
2014-04-23 16:59 ` Nicolas Goaziou [this message]
2014-04-23 19:44 ` Nicolas Goaziou
2014-04-24 12:20 ` Greg Troxel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877g6gm16n.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gdt@ir.bbn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).