From: edgar@openmail.cc
To: emacs-orgmode@gnu.org
Subject: Re: Orgmode repeater intervals with end date
Date: Wed, 10 Jan 2018 18:24:19 +0000 [thread overview]
Message-ID: <10de9788c5b4686b88064175fcddf55d@openmail.cc> (raw)
> Message: 8
> Date: Tue, 09 Jan 2018 22:16:56 -0700
> From: torys.anderson@gmail.com (Tory S. Anderson)
> To: orgmode list <emacs-orgmode@gnu.org>
> Subject: [O] Orgmode repeater intervals with end date
> Message-ID: <87incamgxj.fsf@byu.edu>
> Content-Type: text/plain; format=flowed
>
> Hi all,
>
> When repeater intervals are set on on org dates (eg =<2018-01-10
> Wed 16:00 +2w>=)
> the output is exported nicely to ical and appears
> nicely in agenda. Is there anyway to put an end-date on org dates
> so that the +2w will not just continue forever?
>
> I could use org-class, but then it wouldn't be exported to ical
> nicely. I was hopefully with <2018-01-10 Wed 16:00
> +2w>--<2018-04-10 Wed 16:00 +2w> but this just put the range as
> counting every day in the interim. Is there an existing way to
> have an end-date on a repeating cycle?
>
> - Tory
Have you tried with DEADLINE:? I seem to remember to have read something
like that somewhere. Don't trust me. If it helps, I am glad, but I am
not sure.
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next reply other threads:[~2018-01-10 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 18:24 edgar [this message]
2018-01-10 20:17 ` Orgmode repeater intervals with end date Tory S. Anderson
2018-01-11 11:37 ` lists
2018-01-13 2:06 ` numbchild
2018-01-18 1:26 ` Tory S. Anderson
2018-01-18 14:02 ` Nicolas Goaziou
2018-01-30 15:44 ` Tory S. Anderson
2018-02-07 15:19 ` Karl Voit
2018-04-26 23:34 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 5:16 Tory S. Anderson
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=10de9788c5b4686b88064175fcddf55d@openmail.cc \
--to=edgar@openmail.cc \
--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).