emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode is not able to manage complex calendar events
Date: Tue, 21 Jun 2011 14:32:31 +0200	[thread overview]
Message-ID: <2011-06-21T14-18-15@devnull.Karl-Voit.at> (raw)
In-Reply-To: 8739j4xvxh.fsf@ucl.ac.uk

* Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Karl Voit <devnull@Karl-Voit.at> writes:
>> * Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>>> you can clone with time shift whole trees, etc.  
>> Oh, I have to look up that clone thing. This is new to me. Do you
>> happen to have an URL for this feature by instance?
> ,----[ org-clone-subtree-with-time-shift ]
>| ...
> `----

Wow, this is *great* news to me, thanks!

Although this is mentioned in chapter 2 of the Org-mode manual, I
strongly urge to mention this in section 8.3.2 «Repeated tasks»[1]

Where can I place this wish?

> Sure; elisp is non-trivial.  Point taken!

Thanks :-) The resulting problem is that things I can only express
using sexp is non-trivial too.

I'd be glad to see something like this:

       * Event <2011-06-21 Tue +1w> <-2011-06-28 Tue>

... which lets me express an exception (each tuesday starting with
today but not next week) in an easy to use way.

> If there's any complaint one might have about org, is that it can
> be used for so many different tasks (calendar, task management,
> document preparation, etc.)  that it can be overwhelming.  

Agree. But I'd consider the calendar use-case as the worst supported
usecase in this list. I have seen the talks of Carsten Dominik and
AFAIR he clearly says that Org-mode's focus is task oriented and not
calendar oriented.

> Think of one of those very large swiss army knives where
> you can spend minutes just trying to find the right "blade" ;-).  But
> I'm not complaining! :->

:-) Me too *g*

> In any case, the org manual, the org web site and Worg, not to mention
> this mailing list, provide a wealth of information and use cases.

I love the documentation of Org-mode - it's pretty good!

>> For ELISP-hackers out there: is this hard to do? A method which
>> can be called «generate a series of Org-mode time stamps starting
>> I could think of generating such a series of <2011-06-22 Wed>
>> <2011-06-29 Wed> ... just to be able to see all occurrences of an
>> event and delete one specific event in between if necessary. This
>> would ease exceptions for «ordinary» users like me.
> See above;  I use org-clone-subtree-with-time-shift for setting up, for
> instance, the lectures I have to give in a teaching term.  I set up the
> initial lectures for each relevant day in the week and then clone the
> subtrees, removing any exceptions (reading/study weeks, say) afterwards.

Sure, org-clone-subtree-with-time-shift is very cool indeed. But it
goes in this direction:

    * Event <2011-06-21 Tue>
    * Event <2011-06-28 Tue>
    * Event <2011-07-05 Tue>
    * Event <2011-07-12 Tue +1w>

But I aim in a slightly different direction:

    * Event
        <2011-06-21 Tue>
        <2011-06-28 Tue>: additional note
        <2011-07-05 Tue>
        <2011-07-12 Tue +1w>

The latter one works pretty well and keeps my Org-file more clear.

So org-clone-subtree-with-time-shift is helping a lot for the upper
method but my personal preference would be the second example.

Is there already any solution to this too?

  1. http://orgmode.org/org.html#Repeated-tasks
Karl Voit

  reply	other threads:[~2011-06-21 12:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18  2:09 org and microsoft exchange Skip Collins
2011-06-20  7:52 ` Eric S Fraga
2011-06-20 11:53   ` Holger Wenzel
2011-06-20 12:01     ` Skip Collins
2011-06-20 14:13     ` Jonathan Arkell
2011-06-26 13:35     ` Matthieu Lemerre
2011-06-27 17:14       ` Eric S Fraga
2011-06-27 19:13         ` Matthieu Lemerre
2011-06-28 23:16           ` Bastien
2011-07-07 19:13             ` Matthieu Lemerre
2011-07-08  9:26               ` Bastien
2011-06-29 16:44           ` Eric S Fraga
2011-07-07 19:21             ` Matthieu Lemerre
2011-07-08  9:02               ` Eric S Fraga
2011-07-08 22:14                 ` Achim Gratz
2011-06-20 11:53   ` Org-mode is not able to manage complex calendar events (was: org and microsoft exchange) Karl Voit
2011-06-20 14:38     ` Org-mode is not able to manage complex calendar events Eric S Fraga
2011-06-20 15:51       ` Karl Voit
2011-06-20 17:19         ` Eric S Fraga
2011-06-21 12:32           ` Karl Voit [this message]
2011-06-21 12:50             ` Rémi Vanicat
2011-06-21 16:46               ` Karl Voit
2011-06-21 15:12             ` Eric S Fraga
2011-06-21 17:24               ` Karl Voit
2011-06-28  9:36             ` Bastien
2011-06-28 12:19               ` How to place a feature wish (was: Org-mode is not able to manage complex calendar events) Karl Voit
2011-06-20 18:48         ` Org-mode is not able to manage complex calendar events Memnon Anon
2011-07-01 15:18     ` Bastien
2011-07-01 16:25       ` Karl Voit
2011-07-02  9:21         ` Bastien
2011-07-02 10:20           ` Karl Voit
2011-06-20 14:42   ` org and microsoft exchange Philipp Haselwarter
2011-06-20 15:04     ` Nick Dokos

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:

  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=2011-06-21T14-18-15@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \


* 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


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).