emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Org-mode is not able to manage complex calendar events (was: org and microsoft exchange)
Date: Mon, 20 Jun 2011 13:53:36 +0200	[thread overview]
Message-ID: <2011-06-20T13-43-17@devnull.Karl-Voit.at> (raw)
In-Reply-To: 87aaddaqhz.fsf@ucl.ac.uk

* Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> In my case, it's more about calendar events than tasks.  My tasks are
> typically for my information only but meetings etc involve multiple
> people.

IMHO: Org-mode does *not* seem to be made for managing calendar
events that go beyond simple one-time-occurrence events. 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.

Yes, there is this sexp-workaround[1] for more complex things but
quite frankly: this is not an option for the ordinary user like me
(not having that much ELISP knowledge).

And even with sexp, you can not map recurring events with
exceptions, irregular recurring events, and so forth.

For me as a relatively newbee (related to Emacs and Org-mode) it is
clear that I can not move my current calendar environment to
Org-mode. Unfortunately.

So far, I do have my old calendar setup (in JPilot/PalmOS) and
additionally my task-only-related calendar in Org-mode.

But I'd love to see an advanced and easy to use calendar environment
in Org-mode!

I love Pimlical[2] and its DateBk6 for PalmOS in terms of: easy to
use, very flexible, able to map all kinds of complex requirements,

  1. http://www.gnu.org/software/emacs/manual/html_node/emacs/Sexp-Diary-Entries.html
  2. http://www.pimlicosoftware.com/
Karl Voit

  parent reply	other threads:[~2011-06-20 11:54 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   ` Karl Voit [this message]
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
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-20T13-43-17@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).