Re: [O] Orgmode repeater intervals with end date
Hi Kark and Tory, Karl Voit writes: > http://karl-voit.at/2017/01/15/org-clone-subtree-with-time-shift/ > I do think I remember that I linked to this article somewhere in > Worg. I've now added a FAQ to this in Worg. "How can I let a task repeat until a certain date?" Thanks! -- Bastien
Re: [O] Orgmode repeater intervals with end date
* Tory S. Anderson wrote: > I was very pleased to find, when browsing the manual for a > different reason, the 'orgmode' solution to the problem, which > provides daily customization ability and also maintains > exportability: `org-clone-subtree-with-timeshift`[1], with which I > can easily accomplish my goals and even consolidate my > notes-for-that-event-instance. I'm just writing this here because > it has totally upgraded my planning experience and I wish I'd > known about it sooner! You should subscribe to my blog ;-) http://karl-voit.at/2017/01/15/org-clone-subtree-with-time-shift/ I do think I remember that I linked to this article somewhere in Worg. -- get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode: > get Memacs from https://github.com/novoid/Memacs < Personal Information Management > http://Karl-Voit.at/tags/pim/ Emacs-related > http://Karl-Voit.at/tags/emacs/
Re: [O] Orgmode repeater intervals with end date
I was very pleased to find, when browsing the manual for a different reason, the 'orgmode' solution to the problem, which provides daily customization ability and also maintains exportability: `org-clone-subtree-with-timeshift`[1], with which I can easily accomplish my goals and even consolidate my notes-for-that-event-instance. I'm just writing this here because it has totally upgraded my planning experience and I wish I'd known about it sooner! Thanks all! - Tory Footnotes: [1] https://orgmode.org/manual/Structure-editing.html
Re: [O] Orgmode repeater intervals with end date
Hello, torys.ander...@gmail.com (Tory S. Anderson) writes: > Thanks; oddly, that works. > > *** TODO Personal Meeting > DEADLINE: <2018-01-10 Wed 16:00 .+2w>--<2018-04-18 Wed> FWIW, this syntax is not supported. It could do anything. Regards, -- Nicolas Goaziou
Re: [O] Orgmode repeater intervals with end date
Thanks; oddly, that works.
--8<---cut here---start->8---
*** TODO Personal Meeting
DEADLINE: <2018-01-10 Wed 16:00 .+2w>--<2018-04-18 Wed>
--8<---cut here---end--->8---
I still get a daily count on every day in the interim:
--8<---cut here---start->8---
(8/99): TODO Personal Meeting
--8<---cut here---end--->8---
But I suppose I can work around that. Oddly, it doesn't seem to
work with plain dates or with SCHEDULED: . Any idea why?
"numbch...@gmail.com" writes:
You can try this:
```
* Test repeat time range with end date
DEADLINE: <2018-01-01 Mon 12:00 .+2d>--<2018-01-13 Sat>
```
This will repeat, and end on the day 13. Also deadline works
fine.
[stardiviner] GPG key ID:
47C32433
IRC(freeenode): stardiviner Twitter:
@numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3
2433
Blog: http://stardiviner.github.io/
On Thu, Jan 11, 2018 at 7:37 PM, wrote:
On 2018-01-10 18:24, ed...@openmail.cc wrote:
Message: 8
Date: Tue, 09 Jan 2018 22:16:56 -0700
From: torys.ander...@gmail.com (Tory S. Anderson)
To: orgmode list
Subject: [O] Orgmode repeater intervals with end
date
Message-ID: <87incamgxj@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.
Have a look at https://www.gnu.org/software/emacs/manual/
html_node/emacs/Sexp-Diary-Entries.html However, I am not
sure if
you can use an Emacs sexp to specify an end date.
Ian.
Re: [O] Orgmode repeater intervals with end date
You can try this: ``` * Test repeat time range with end date DEADLINE: <2018-01-01 Mon 12:00 .+2d>--<2018-01-13 Sat> ``` This will repeat, and end on the day 13. Also deadline works fine. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Thu, Jan 11, 2018 at 7:37 PM, wrote: > On 2018-01-10 18:24, ed...@openmail.cc wrote: > >> Message: 8 >>> Date: Tue, 09 Jan 2018 22:16:56 -0700 >>> From: torys.ander...@gmail.com (Tory S. Anderson) >>> To: orgmode list >>> Subject: [O] Orgmode repeater intervals with end date >>> Message-ID: <87incamgxj@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. >> >> > Have a look at https://www.gnu.org/software/e > macs/manual/html_node/emacs/Sexp-Diary-Entries.html However, I am not > sure if you can use an Emacs sexp to specify an end date. > > Ian. > >
Re: [O] Orgmode repeater intervals with end date
On 2018-01-10 18:24, ed...@openmail.cc wrote: Message: 8 Date: Tue, 09 Jan 2018 22:16:56 -0700 From: torys.ander...@gmail.com (Tory S. Anderson) To: orgmode list Subject: [O] Orgmode repeater intervals with end date Message-ID: <87incamgxj@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. Have a look at https://www.gnu.org/software/emacs/manual/html_node/emacs/Sexp-Diary-Entries.html However, I am not sure if you can use an Emacs sexp to specify an end date. Ian.
Re: [O] Orgmode repeater intervals with end date
I just tried --8<---cut here---start->8--- DEADLINE: <2018-04-19 Thu> <2018-01-10 Wed 16:00 +2w> --8<---cut here---end--->8--- But unfortunately entries were still appearing after the deadline. ed...@openmail.cc writes: Message: 8 Date: Tue, 09 Jan 2018 22:16:56 -0700 From: torys.ander...@gmail.com (Tory S. Anderson) To: orgmode list Subject: [O] Orgmode repeater intervals with end date Message-ID: <87incamgxj@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!
Re: [O] Orgmode repeater intervals with end date
Message: 8 Date: Tue, 09 Jan 2018 22:16:56 -0700 From: torys.ander...@gmail.com (Tory S. Anderson) To: orgmode list Subject: [O] Orgmode repeater intervals with end date Message-ID: <87incamgxj@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!
[O] Orgmode repeater intervals with end date
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
