From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Voit Subject: Avoid canceling of events which do have multiple time-stamps Date: Fri, 7 Nov 2014 11:43:55 +0100 Message-ID: <2014-11-07T11-42-46@devnull.Karl-Voit.at> Reply-To: Karl Voit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53243) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xmh1f-0004uv-7l for emacs-orgmode@gnu.org; Fri, 07 Nov 2014 05:44:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xmh1X-0003xh-GC for emacs-orgmode@gnu.org; Fri, 07 Nov 2014 05:44:19 -0500 Received: from plane.gmane.org ([80.91.229.3]:55075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xmh1X-0003xP-9n for emacs-orgmode@gnu.org; Fri, 07 Nov 2014 05:44:11 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Xmh1V-0001rA-1m for emacs-orgmode@gnu.org; Fri, 07 Nov 2014 11:44:09 +0100 Received: from d86-32-14-16.cust.tele2.at ([86.32.14.16]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Nov 2014 11:44:09 +0100 Received: from news1142 by d86-32-14-16.cust.tele2.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Nov 2014 11:44:09 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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?