From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Repeated teaching classes and stopping date
Date: Tue, 11 Nov 2014 12:06:33 +0100 [thread overview]
Message-ID: <877fz2dmiu.fsf@gmx.us> (raw)
In-Reply-To: 5461C3BB.1060305@lal.in2p3.fr
Xavier Garrido <garrido@lal.in2p3.fr> writes:
> Hi Rasmus,
>
> Le 10/11/2014 18:37, Rasmus a écrit :
>> Hi Xavier,
>>
>> Xavier Garrido <xavier.garrido@gmail.com> writes:
>>
>>> I'm trying to move to =org-agenda= and I'm converting some of my
>>> Google Calendar entries into Org agenda entries. I'm facing an issue
>>> with repeated tasks and how to properly stop the event. Consider the
>>> following entry :
>>>
>>> * [Master 1] Nuclear & particle class
>>> <2015-01-21 mer. 14:00-16:00 +1w>--<2015-03-22 dim.>
>>>
>>> For me it means, I will teach every week @ 14:00 to 16:00 until the
>>> 22th of March. I am surely doing something bad since the events
>>> actually appear every day until the 22th of March. It basically works
>>> when I remove the --<2015-03-22 dim.> but then how to stop the
>>> repeated tasks.
>>>
>>> Sorry if the answer is obvious but I have read org-mode manual
>>> (http://orgmode.org/manual/Repeated-tasks.html) and other "timestamp"
>>> related pages and I didn't find a way to do that.
>>
>> Did you check `org-class'? Also check
>> `org-clone-subtree-with-time-shift'. If you search for the latter you
>> will find a recent discussion on what I think is the topic you are
>> interested in.
>>
>
> Thanks for the hints, I should have read the FAQ first since my
> problem is clearly addressed (here for example
> http://orgmode.org/worg/org-faq.html#diary-sexp-in-org-files). In SO
> this guy also have the same problem
> http://stackoverflow.com/questions/2464598/org-mode-schedule-weekly-event-for-a-period
They also point to `org-class` in one of the answers.
> I will try to slightly modify the ical2org.awk file from Eric Fraga
> http://orgmode.org/worg/code/awk/ical2org.awk to automatically
> converts ical file into org and to manage this repeating task.
If you want... There are already two functions that were created for
this stuff.
> I have to say that it is a bit frustrating that the syntax <YYYY-MM-DD
> +1w>--<YYYY-MM-DD> is not working because it is pretty simple and
> quite elegant.
Patch welcome! I can see the syntax being somewhat intuitive, but I
think maybe the double use of "--" is confusing. Why not:
<YYYY-MM-DD> +1w> until <yyyy-mm-dd>
Anyway. . .
Cheers,
Rasmus
--
Bang bang
next prev parent reply other threads:[~2014-11-11 11:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 17:21 Repeated teaching classes and stopping date Xavier Garrido
2014-11-10 17:37 ` Rasmus
2014-11-11 8:07 ` Xavier Garrido
2014-11-11 11:06 ` Rasmus [this message]
2014-11-11 13:56 ` Karl Voit
2014-11-12 2:03 ` James Harkins
2014-11-13 8:26 ` Samuel Loury
2014-11-13 10:09 ` Eric S Fraga
2014-11-13 10:44 ` Samuel Loury
2014-11-13 16:22 ` Eric S Fraga
2014-11-14 9:42 ` Samuel Loury
2014-11-14 11:32 ` Eric S Fraga
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=877fz2dmiu.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).