From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: iCal export of repeated tasks
Date: Fri, 13 Jun 2008 12:48:05 +0100 [thread overview]
Message-ID: <20080613114805.GC8066@atlantic.linksys.moosehall> (raw)
In-Reply-To: <0C275B3E-BECB-4A5A-9B95-8C928046DE18@uva.nl>
On Fri, Jun 13, 2008 at 12:28:48PM +0200, Carsten Dominik wrote:
> On Jun 13, 2008, at 11:24 AM, Adam Spiers wrote:
> >The motivation is that while I very much like org's functionality for
> >automatically updating the timestamp on a repeated task once it has
> >been marked as done, I do not want tasks such as "water plants"
> >cluttering up my calendar forever into the future. I only care about
> >the next plant watering, not all others thereafter, and with screen
> >real estate always short in supply (especially on mobile devices!),
> >any possible savings are of value.
>
> I can see that this is useful, but I still insist that Org should
> export a repeated event as such.
As the *default* behaviour, without another behaviour being very
specifically requested by the user, I entirely agree :-)
> I am adding a hook, `org-before-save-iCalendar-file-hook'. You can
> add some special cookie in the headline of the entry, and then
> search for this cookie in the exported file and remove the
> repetition rule. How about that?
Yes thanks; that should do it, and will also possibly enable other use
cases via that hook.
> >Actually, now I think about it more, the above decluttering argument
> >applies equally to the Org agenda itself. So if it would be a more
> >consistent request from the point of view of maintaining an intuitive
> >UI or from ease of implementation, I would be perfectly happy if the
> >proposed property disabled display of all but the first instance of
> >the repeated task *everywhere*, i.e. not only in iCal exports, but
> >also in agenda displays.
>
> Org has the variable `org-agenda-repeating-timestamp-show-all' which
> allows to modify this behavior for all repeating time stamps, not
> for individual ones, though.
Well, perhaps you might consider it at some point in the future, or at
least a distinction between repeated events and repeated tasks.
I think we've now spent enough energy on this relatively minor
cosmetic issue though ;-)
prev parent reply other threads:[~2008-06-13 11:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 10:17 iCal export of repeated tasks Adam Spiers
2008-06-12 6:02 ` Carsten Dominik
2008-06-12 10:05 ` Adam Spiers
2008-06-12 10:54 ` Carsten Dominik
2008-06-12 11:47 ` Adam Spiers
2008-06-13 8:18 ` Carsten Dominik
2008-06-13 9:24 ` Adam Spiers
2008-06-13 9:55 ` Paul R
2008-06-13 12:01 ` Adam Spiers
2008-06-13 12:56 ` Paul R
2008-06-13 14:16 ` Adam Spiers
2008-06-13 10:28 ` Carsten Dominik
2008-06-13 11:48 ` Adam Spiers [this message]
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=20080613114805.GC8066@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.org \
--cc=emacs-orgmode@gnu.org \
/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).