From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Avoid canceling of events which do have multiple time-stamps
Date: Fri, 07 Nov 2014 17:31:05 -0500 [thread overview]
Message-ID: <87vbmqprrq.fsf@yale.edu> (raw)
In-Reply-To: 2014-11-07T11-42-46@devnull.Karl-Voit.at
Hi, Karl.
Karl Voit writes:
> For other events, I do have one single "* Volleyball" heading
> and multiple time-stamps for each occurrence in its body.
> (method B)
>
> Unfortunately in the agenda view, both entries are visualized
> the same way. This is causing issues in certain cases.
>
> For example, when I see an event on my agenda and I know that I
> don't have time for it, I usually cancel the event right away in
> my agenda.
>
> However, when this time-stamp occured only in the body of a
> heading (method B), cancelling does cancel *all* occurrences.
> For example when I cancel "Volleyball" on the agenda of
> 2014-09-06, I'd cancel also 2014-08-30 (in the past) and
> 2014-09-13 (in the future).
>
> And much worse: I do not notice my error.
>
> There is a certain issue with this: how to determine whether or
> not a time-stamp is the only one or if it is mentioned in the
> heading itself.
I use several time stamps as well, but I use
org-agenda-follow-mode by default (see the variable
`org-agenda-start-with-follow-mode') so I can see the entry with
its multiple entries before archiving or killing it.
> Is there a clever way to differ the two methods so that we are
> able to come up with different visualizations?
In the case of something like Volleyball, perhaps you might want
to look at habits: (info "(org) Tracking your habits")
Another option is to create subheadlines for each activity, and
avoid multiple timestamps.
Best,
--
Jorge.
prev parent reply other threads:[~2014-11-07 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:43 Avoid canceling of events which do have multiple time-stamps Karl Voit
2014-11-07 22:31 ` Jorge A. Alfaro-Murillo [this message]
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=87vbmqprrq.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--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).