From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Un-SCHEDULING isn't working for me :-( Date: Mon, 4 Feb 2008 11:00:38 +0100 Message-ID: <8D234451-94DB-4F1F-B99E-A00B107285D3@science.uva.nl> References: <14146.1202080374@localhost> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JLy8Y-00057g-Cl for emacs-orgmode@gnu.org; Mon, 04 Feb 2008 05:01:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JLy8Q-000524-Lr for emacs-orgmode@gnu.org; Mon, 04 Feb 2008 05:01:12 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JLy8Q-00051f-BZ for emacs-orgmode@gnu.org; Mon, 04 Feb 2008 05:01:06 -0500 Received: from ug-out-1314.google.com ([66.249.92.170]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JLy8P-0008LK-HZ for emacs-orgmode@gnu.org; Mon, 04 Feb 2008 05:01:06 -0500 Received: by ug-out-1314.google.com with SMTP id a2so1421383ugf.48 for ; Mon, 04 Feb 2008 02:00:43 -0800 (PST) In-Reply-To: <14146.1202080374@localhost> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: pete@smtl.co.uk Cc: org-mode mailing list On Feb 4, 2008, at 12:12 AM, Pete Phillips wrote: > I am trying to Un-Schedule something. In the *Org Agenda* buffer I > press: > > C-u C-c C-s > > the buffer says: > > "Item is no longer Scheduled" > > but when I regenerate the buffer, it still has the scheduling > information. > > The line looks like this: > > **** WAITING Jim to set up All Wales review group SCHEDULED: > <2008-01-28 Mon> :Office:Jim: > For this command, Org-mode assumes that the SCHEDULED timestamp is on the second line, just *after* the heading. Your timestamp is in the headline, sort-of a non-standard location. Anyway nonstandard locations are alowed, so I better fix this. Will be in the next release. - Carsten