From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: (BUG?) Problem with proper time frame in agenda. Date: Tue, 8 Aug 2006 13:29:03 +0200 Message-ID: <40e94bde2da43c1e6b30f500c72d2d10@science.uva.nl> References: Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GAPlr-00072t-KX for emacs-orgmode@gnu.org; Tue, 08 Aug 2006 07:29:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GAPlp-00072Y-5R for emacs-orgmode@gnu.org; Tue, 08 Aug 2006 07:29:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GAPlo-00072N-Pg for emacs-orgmode@gnu.org; Tue, 08 Aug 2006 07:29:12 -0400 Received: from [146.50.4.51] (helo=imap.science.uva.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GAPqG-0002NL-E4 for emacs-orgmode@gnu.org; Tue, 08 Aug 2006 07:33:48 -0400 In-Reply-To: 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: Juraj Kubelka Cc: emacs-orgmode@gnu.org On Aug 8, 2006, at 12:26, Juraj Kubelka wrote: > Hi All! > > I have org file like example below. But some time stamps are not > correctly displayed (see example below) in agenda view (org-agenda). I > use emacs snapshot (22.0.51.1) and Org-mode version 4.43. Is it > Org-mode bug or just my mistake? > + <2006-08-11 P=E1 09:16>--<2006-08-12 So 13:20> > - doesn't work: there is "2006-08-11 13:20" in agenda. This is a bug in parsing, when looking for a time it just takes one,=20 not checking if this is a range. I'll see if I can do something,=20 probably removing the time-of-day display for ranges entirely. > + <2006-08-14 Po 10:08>--<2006-08-16 St 11:20> > - doesn't work: it is not displayed in agenda. The agenda assumes that there is only one agenda-relevant time stamp or=20= range associated with any headline in the buffer. When it has found=20 one, it jumps to the next headline, skipping anything in between, to=20 speed up parsing. That's why each time you have several stamps or=20 ranges, only the first is taken seriously. Hmmm. need to think about=20= this, what the right course of action would be. Comments welcome. Thanks for the report. - Carsten=