From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Riedy Subject: Re: Best practice for canceled/moved recurring events Date: Sun, 24 Jul 2016 11:27:01 -0400 Message-ID: <87k2gbjbui.fsf@qNaN.cc.gatech.edu> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRLJE-0005o2-7a for emacs-orgmode@gnu.org; Sun, 24 Jul 2016 11:27:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bRLJ9-0006yb-7V for emacs-orgmode@gnu.org; Sun, 24 Jul 2016 11:27:16 -0400 Received: from plane.gmane.org ([80.91.229.3]:45143) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRLJ9-0006yX-0r for emacs-orgmode@gnu.org; Sun, 24 Jul 2016 11:27:11 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bRLJ6-0000IM-Cj for emacs-orgmode@gnu.org; Sun, 24 Jul 2016 17:27:08 +0200 Received: from c-98-252-131-64.hsd1.ga.comcast.net ([98.252.131.64]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 24 Jul 2016 17:27:08 +0200 Received: from jason by c-98-252-131-64.hsd1.ga.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 24 Jul 2016 17:27:08 +0200 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" To: emacs-orgmode@gnu.org And sabrewolfy@gmail.com writes: > What is the best way of dealing with scenarios where (1) the meeting "next > week" is on the Wednesday and (2) the meeting "two weeks" after that (or > whatever) is canceled? Right now, I keep the typical meeting (titled with "Standing: ") and add exceptions as separate events ("Exception: "). The version of owncloud I'm using as a sync target for org and my phone doesn't handle exceptions anyways.