emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Avoid canceling of events which do have multiple time-stamps
Date: Fri, 7 Nov 2014 11:43:55 +0100	[thread overview]
Message-ID: <2014-11-07T11-42-46@devnull.Karl-Voit.at> (raw)

Hi!

Sometimes, I use single events and use
"org-clone-subtree-with-time-shift" to create clones for multiple
occurrences. (method A)

: ** <2014-08-30 Sat 15:00-17:00> Volleyball
:
: Do some sport.


For other events, I do have one single "* Volleyball" heading and
multiple time-stamps for each occurrence in its body. (method B)

: 
: ** Volleyball
: 
: - <2014-08-30 Sat 15:00-17:00> 
: - <2014-09-06 Sat 15:00-17:00> 
: - <2014-09-13 Sat 15:00-17:00> 


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.

Is there a clever way to differ the two methods so that we are able to
come up with different visualizations?

What are your thoughts on this issue?

next             reply	other threads:[~2014-11-07 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 10:43 Karl Voit [this message]
2014-11-07 22:31 ` Avoid canceling of events which do have multiple time-stamps Jorge A. Alfaro-Murillo

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=2014-11-07T11-42-46@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

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