From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric S Fraga Subject: Re: scheduled item taking time from inactive time stamp Date: Fri, 20 Feb 2009 14:44:38 +0000 Message-ID: <18846.49622.996441.373253@pinto.chemeng.ucl.ac.uk> References: <547849.78457.qm@web28303.mail.ukl.yahoo.com> <0576FFE1-09CF-4CF1-8A59-B80C87A8DC24@uva.nl> <18846.43978.321051.411022@pinto.chemeng.ucl.ac.uk> <18846.47429.876760.8948@pinto.chemeng.ucl.ac.uk> Reply-To: e.fraga@ucl.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LaWcP-00040C-Sj for emacs-orgmode@gnu.org; Fri, 20 Feb 2009 09:44:45 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LaWcO-000400-Gi for emacs-orgmode@gnu.org; Fri, 20 Feb 2009 09:44:45 -0500 Received: from [199.232.76.173] (port=36749 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LaWcO-0003zx-Bc for emacs-orgmode@gnu.org; Fri, 20 Feb 2009 09:44:44 -0500 Received: from vscani-a.ucl.ac.uk ([144.82.108.29]:35124) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LaWcN-00016m-TI for emacs-orgmode@gnu.org; Fri, 20 Feb 2009 09:44:44 -0500 In-Reply-To: From: Eric S Fraga 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: Carsten Dominik Cc: emacs-orgmode@gnu.org Carsten Dominik writes: > > However, my original question still stands: does it really make sense > > for org-mode's agenda view to take the "time" for an activity that has > > been scheduled for that day from an inactive time stamp when the > > active one in the SCHEDULE entry has no time element? > > The reason for this behavior is that I wanted to support things like > > * TODO Meeting at 2pm > <2009-01-01 Thu> > > i.e. loose time information that may be in the header. > > The regular expression looking for a time also matches the > time you had in the time stamp. Ah, okay, that makes perfect sense. Thanks! I guess I don't think of having the time and date separate ever but I can where others might like that. > I think the right approach is to not put the time stamp into the > header line at all. Why would you want the *creation* time in such > an exposed place???? It's because I sometimes want to sort entries according to date/time of creation as opposed to date/time of actual activity performed. I can work around this without difficulty, I think, so thanks all again for all the input!