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: Mon, 20 Jun 2011 17:51:25 +0200	[thread overview]
Message-ID: <2011-06-20T17-33-36@devnull.Karl-Voit.at> (raw)
In-Reply-To: 87y60wfu05.fsf@pinto.chemeng.ucl.ac.uk

* Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> IMHO: Org-mode does *not* seem to be made for managing calendar
>> events that go beyond simple one-time-occurrence events. 
>
> I would argue that this is not at all the case, especially if you
> consider that org uses a tree hierarchy and tags so that one can group
> separate entries in a variety of ways, 

This is fore sure a big advantage of Org-mode!

> 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?

> Most calendar tools require you to specify all the
> conditions for a particular "event" in one go whereas with org you can
> have a number of different entries for the same "event"... etc.

Full ack.

> Also, with sexp, you can manage practically anything you might like
> although, of course, it does require learning a certain amount of
> elisp.  Recurring events with exceptions are not a problem, for
> instance.

I'd consider myself tech-savvy. But without having learned (E)LISP
(yet), I can not use sexp-entries without reading a manual each time
I want to use it. This is nothing I'd consider for normal users or
daily use. It's not that end-user friendly (when you consider
end-users as users without ELISP knowledge).

For ELISP hackers this might work! But I am not sure how much
percentage of Emacs/Org-mode users actually learned ELISP.

And learning ELISP just to be able to write down a recurring event
seems «strange» to me.

> In any case, as always with computer tools, what works for you is what
> matters!  

Full Ack.

> For me, org is just plainly much more suitable for my mode of
> working; every other calendar system I have tried has constrained me
> much more.  But that's *me*.

This holds for most of the calendar systems out there, I totally
agree.

(This is why I still carry around my old PalmOS-PDA together with my
highly sophisticated Android smartphone...)

>> but you *have* to support at least the same featureset of Outlook
>> Calendar in order to think of a (two-way-) sync mechanism to
>> Org-mode.
>
> I guess this depends on what types of events you are likely to
> have in the outlook calendar.  In my case, only a small feature
> set is likely necessary (mostly repeating lectures and one off
> meetings) so a sync should be possible.  I don't think anybody is
> proposing a full-blown totally automatic sync mechanism between
> org and Outlook (or whatever) that covers the union of the two
> products' feature sets...  insanity lies in that direction ;-)

Sorry, I might have exaggerated a bit.

But since I was implementing a one-way-sync mechanism between two
different calendar systems I got a pretty good feeling of how
different you can define the very same thing. Recurring events with
exceptions is quite common but very hard to sync between different
systems! And I am sure that this is not the only example of «being
common and hard to do».

> But I'll worry about this later this year when forced to use MS...

Oh, sorry to hear about that :-(



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
with $THIS_TIMESTAMP_CONTAINING_REPEATS up to $THIS date». 

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.

-- 
Karl Voit

  reply	other threads:[~2011-06-20 15:51 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 [this message]
2011-06-20 17:19         ` Eric S Fraga
2011-06-21 12:32           ` Karl Voit
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:
  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=2011-06-20T17-33-36@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).