From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Re: table bug and SCHEDULED: issue Date: Tue, 21 Nov 2006 11:41:19 -0600 Message-ID: References: <8f522c9e1fadb59fad0a265b61f42547@science.uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GmZcc-00013M-St for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:41:26 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GmZcb-00012j-D8 for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:41:26 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GmZcb-00012g-Ap for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:41:25 -0500 Received: from [66.249.92.175] (helo=ug-out-1314.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GmZcY-0002TB-7J for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:41:24 -0500 Received: by ug-out-1314.google.com with SMTP id j3so1744096ugf for ; Tue, 21 Nov 2006 09:41:19 -0800 (PST) In-Reply-To: <8f522c9e1fadb59fad0a265b61f42547@science.uva.nl> Content-Disposition: inline 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 On 11/21/06, Carsten Dominik wrote: > > On Nov 20, 2006, at 17:49, Eddward DeVilla wrote: > Well, there is possibility that this might have worked, but I am not > convinced. > For me, if I use this file, I do get an entry "quick info" on November > 2 in > my agenda, I don't understand why you don't. The reason why it is in > the agenda is the naked time stamp, and has nothing to do with the > SCHEDULED keyword. Thats why this entry shows up only on the day and > is not forwarded like a scheduled item would be. > > Why are you not using: > > * quick info > |-----------------------------| > | Blah Blah blah | > | SCHEDULED: <2006-11-02 Thu> | > | DEADLINE: | > |-----------------------------| > > then this item would really be scheduled for this date. I forgot about the naked timestamps. That's why it probably worked on the day I first tested it. The table just grew into what it is. I originally had for each project something like * WORKING [/] Some project :product1: *** Quick info |-------------------------+-------------------| | problem report | 123 | | release | v4r5m6 | | estimate | 2 weeks | |-------------------------+-------------------| | start date | [date] | | base code complete | [date] | | secondary code complete | | | testing complete | | |-------------------------+-------------------| | toolset level | 10.3 | | build environment setup | | |-------------------------+-------------------| *** status ... *** [/] investigation ... *** [/] steps ... *** [/] secondary steps ... *** [/] testing ... As I've started using agenda I've begun to look into using active dates and the scheduling keywords. I was trying to replace "start date" with SCHEDULE: and I apparently fooled myself into thinking it worked once. :-) I'll probably just move the scheduling keywords under the project heading. Also, I tried to recreate the bug with undo in the table on cygwin. It doesn't happen there. It also hasn't been 100% re-creatable today on the original system. Unless someone else sees it, I would waste much time on it. If I see it again I'll see if I can narrow it down. Sorry. Edd