From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Small bug and sorting suggestion Date: Mon, 20 Nov 2006 09:55:11 +0100 Message-ID: <52618b2a856a0e823f0439f83867385e@science.uva.nl> References: <87fycgjkzy.fsf@tallis.ilo.ucl.ac.uk> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gm5Vf-0003dI-Sg for emacs-orgmode@gnu.org; Mon, 20 Nov 2006 04:32:15 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gm5Vc-0003d6-Uw for emacs-orgmode@gnu.org; Mon, 20 Nov 2006 04:32:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gm5Vc-0003d3-SP for emacs-orgmode@gnu.org; Mon, 20 Nov 2006 04:32:12 -0500 Received: from [146.50.4.51] (helo=imap.science.uva.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gm5Vc-0002r2-ML for emacs-orgmode@gnu.org; Mon, 20 Nov 2006 04:32:13 -0500 In-Reply-To: <87fycgjkzy.fsf@tallis.ilo.ucl.ac.uk> 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: Bastien Cc: emacs-orgmode@gnu.org On Nov 19, 2006, at 2:14, Bastien wrote: > Hi Carsten and list, > > headlines containing a time interval after SCHEDULED are not "closed" > properly (org-log-done is t). The adding of "CLOSED" yields this: > > * WAITING Salon Educ@tice > SCHEDULED: <2006-11-15 mer>--<2006-11-17 ven> > > * DONE Salon Educ@tice > --<2006-11-17 ven> CLOSED: [2006-11-18 sam] > > Maybe i shouldn't use time interval after SCHEDULED, but i find it > useful. Note that this does not happen with DEADLINE instead of > SCHEDULED. Tested with org v4.56. Indeed, SCHEDULED is not intended to be used with a time interval. The time/date interval you give in such a case will not be interpreted as a scheduling interval, but just as a block appointment. I can see, however, that it could make sense to use it like this. An item marked by SCHEDULED: -- will show up on all days in the interval, but will also be carried forward as an overdue scheduled item, until you mark it done. Hmmm, a nice, unintended feature. For now I am leaving it undocumented, but I have fixed the problem you describe above, for the next version. Thanks for the report. > The feature suggestion is this one: since you're working on sorting, > what about sorting headlines depending on the date they're attached > to? > > I've got a headline called "Call for paper" where I put all the CFP > and that would be great to have them automagically sorted. I take it that you are talking about sorting tree-nodes in the Org-mode buffer, similar to Carles Cave's request? > This could be either an absolute order (first coming headline first > displayed, no matter if it's SCHEDULED or DEADLINE) or a mix between > categories and dates (DEADLINE first with sorted items, then SCHEDULED > with sorted items, etc). Hmmm again - if I read this, it looks to me that you are in fact talking about sorting in the agenda buffer. Which one is it? - Carsten