From: Eric S Fraga <email@example.com>
Subject: Re: Org-mode is not able to manage complex calendar events
Date: Tue, 21 Jun 2011 16:12:38 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <2011-06-21T14-18-15@devnull.Karl-Voit.at> (Karl Voit's message of "Tue, 21 Jun 2011 14:32:31 +0200")
Karl Voit <devnull@Karl-Voit.at> writes:
> * Eric S Fraga <email@example.com> wrote:
>> Karl Voit <devnull@Karl-Voit.at> writes:
>>> * Eric S Fraga <firstname.lastname@example.org> 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!
You're very welcome!
> 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»
> Where can I place this wish?
You've done so, to some degree, by expressing this on the mailing list.
Better yet, however, is to update the documentation yourself and submit
a patch! Instructions on how to contribute to org are on the web site
(I'm offline at the moment so cannot give you a direct link; sorry).
Patches to the documentation, in particular, are very welcome and
generally straightforward to generate!
>> 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.
Not possible without use of sexp entries, as far as I know.
>> 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.
Yes, I think that's a fair assessment. The trick to using org is to
realise that everything in life is really oriented around tasks;
calendaring then comes automatically from this! The problem is that
most people have gotten used to separating tasks from calendar views
(cf. separation between tasks lists and appointments) and so moving to
org can be a bit of a culture shock. If you start thinking from the
tasks first, the rest follows.
For instance, I'm working on a project; call it A. I create a headline
for this project (or a file, or a sub-headline, whatever). Under this
headline, I will create entries for finances, meetings, notes, actions,
etc. Everything in one place. Org then provides a number of "views" to
look at different aspects of this project: agenda view (akin to a
calendar), column view, sparse tree view, tags view, ... All of these
allow you to see, easily, the particular aspects of a project, or
collection of projects, that are important at any point.
> 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.
I would argue that this is a more limiting view as it is difficult to
add notes to each individual event, something I would often (always?)
want to do! If each event (meeting?) is a sub-headline of its own,
adding notes, actions that arise, etc is very easy.
Again, you can use org to "view" the information you have in different
ways so I would suggest you explore these views. For the above, maybe a
Log view in the agenda might give you what you want.
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 188.8.131.52
: using Org-mode version 7.5 (release_7.5.414.g56de5)
next prev parent reply other threads:[~2011-06-21 16:28 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
2011-06-21 12:50 ` Rémi Vanicat
2011-06-21 16:46 ` Karl Voit
2011-06-21 15:12 ` Eric S Fraga [this message]
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
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 \
* 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).