Re: todo or not todo

2013-10-04 Thread Josef
Hi Terry, I noticed the presence of changes in the todo.py code, because I get now a lot of error messages: Traceback (most recent call last): File /home/dalcolmo/programs/leo/leo-editor/leo/core/leoPlugins.py, line 336, in callTagHandler result = handler(tag,keywords) File

Re: todo or not todo

2013-10-04 Thread Josef
For completeness, I get these error messages only when I set the check mark on the due date. btw, this is one of the most important plug-ins, though I do not use the progress features. On the other hand, I would sometimes need additional named fields, like the an action item ID, ID's of

Re: todo or not todo

2013-10-04 Thread Terry Brown
On Fri, 4 Oct 2013 06:39:44 -0700 (PDT) Josef joe...@gmx.net wrote: Hi Terry, I noticed the presence of changes in the todo.py code, because I get now a lot of error messages: I think that bug came in with the date icon, so it's 2-3 weeks old, I haven't pushed the next work date code yet.

Re: todo or not todo

2013-10-04 Thread Terry Brown
On Fri, 4 Oct 2013 06:48:05 -0700 (PDT) Josef joe...@gmx.net wrote: For completeness, I get these error messages only when I set the check mark on the due date. btw, this is one of the most important plug-ins, though I do not use the progress features. On the other hand, I would

Re: todo or not todo

2013-10-02 Thread Terry Brown
On Wed, 02 Oct 2013 17:13:30 -0400 gatesphere gatesph...@gmail.com wrote: I do the same as you, re: duedate as next-work date. :-) so obviously next work date was missing and needs to be there I agree the change is valid... duedate shouldn't change. I'd suggest using next-work-date to

Re: todo or not todo

2013-10-02 Thread gatesphere
On 10/2/2013 5:32 PM, Terry Brown wrote: On Wed, 02 Oct 2013 17:13:30 -0400 gatesphere gatesph...@gmail.com wrote: I do the same as you, re: duedate as next-work date. :-) so obviously next work date was missing and needs to be there Ayup :) I agree the change is valid... duedate shouldn't