Re: Why a different syntax for projects and contexts?

todo.txt file parsabilities

While the debate rages on as to what the todo.txt file syntax should be,
I'm enjoying using vim and vimoutliner (vimoutliner.org is co-incedently
down for the week) In my small world, trying to master a gajillion details
of running a caffe with .txt tools, using reming, todo.py, vimoutliner and
many associated plug-ins and scripts to send the stuff to the "real world"
(website, print, google calendar, palm data) I managed to get the developer
of remind to offer a simple perl script that parses any text file for lines
that go ; "rem [whatever] %". This will allow me to keep my "reminders" in
my main working linuxcaffe.otl vimoutliner file.
now, (you see it coming, don't you ?) is there any reason why we might, in
defining out todo.txt syntax, start with any amount of whitespace and then
"({uppercaseletter}) and some text". That would allow (selfich ol') me use
the amazing vim and the folding power of vimoutliner, on my todos. 
Onece we have a clearer definition of a todo.txt file format, maybe we
could make a vim syntax highlighting file for it ??
thanks,
the entire silly effort of a full suite of PIM unixy apps is the focus of
the (slowly moving along) wyrdo.com project.
thanks all, 
djp

http://todotxt.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/todotxt/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/todotxt/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:todotxt-digest@... 
    mailto:todotxt-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    todotxt-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Re: todo.txt file parsabilities

Dear David

It's a desire of mine that the various todo scripts allow users to use whatever syntax they want for 
their todo.txt file. Like you want your own syntax with white space then an upper case letter then 
text and %. So why not? (Maybe that is my perl way of thinking -- There's More Than One Way To Do It 
-- whereas Python aims for one best way to do things.)

I made a prototype of this in perl, hoping it would pique the interest of others, but... I've yet to 
detect a surge in the interest level. See the email from me on July 11, 2007. I included a link to 
the script:
http://magnadev.com/todotxt/todotxt_multiformat_demo.zip

Also, would you mind sending me the perl script put together by the developer of remind?

Ron

David J Patrick wrote:
> 
> 
> While the debate rages on as to what the todo.txt file syntax should be,
> I'm enjoying using vim and vimoutliner (vimoutliner.org is co-incedently
> down for the week) In my small world, trying to master a gajillion details
> of running a caffe with .txt tools, using reming, todo.py, vimoutliner and
> many associated plug-ins and scripts to send the stuff to the "real world"
> (website, print, google calendar, palm data) I managed to get the developer
> of remind to offer a simple perl script that parses any text file for lines
> that go ; "rem [whatever] %". This will allow me to keep my "reminders" in
> my main working linuxcaffe.otl vimoutliner file.
> now, (you see it coming, don't you ?) is there any reason why we might, in
> defining out todo.txt syntax, start with any amount of whitespace and then
> "({uppercaseletter}) and some text". That would allow (selfich ol') me use
> the amazing vim and the folding power of vimoutliner, on my todos.
> Onece we have a clearer definition of a todo.txt file format, maybe we
> could make a vim syntax highlighting file for it ??
> thanks,
> the entire silly effort of a full suite of PIM unixy apps is the focus of
> the (slowly moving along) wyrdo.com project.
> thanks all,
> djp
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> No virus found in this incoming message.
> Checked by AVG Free Edition. 
> Version: 7.5.488 / Virus Database: 269.14.6/1061 - Release Date: 10/10/2007 8:43 AM

http://todotxt.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/todotxt/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/todotxt/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:todotxt-digest@... 
    mailto:todotxt-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    todotxt-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

dfs@...: Re: [Remind-Fans] a slacker syntax for .reminders ?]

in response to a thread on remind-fans@... chasing the ability to
work with "reminders" inline, in a text file. 
----- Forwarded message from "David F. Skoll"
<dfs@...> -----

> Date: Tue, 09 Oct 2007 19:36:18 -0400
> From: "David F. Skoll" <dfs@...>
> To: Users of the <remind-fans@...>
> Subject: Re: [Remind-Fans] a slacker syntax for .reminders ?
> 
> Daniel A Graham wrote:
> > Not perl, but here's a python script to do the job:
> 
> > remind = re.compile(r'^\s*rem\s.*$', re.IGNORECASE)
> 
> The original poster wanted lines cut at the final %.  So if you have:
> 
>     REM Monday MSG I hate %"Mondays%"   %
> 
> then Remind would be fed:
> 
> REM Monday MSG I hate %"Mondays%"
> 
> So here's a Perl one-liner:
> 
> perl -ne 'print "$1\n" if /^\s*(REM.*)%/i or /^\s*(REM.*)/i'
> 
> And a shell script:
> 
> #!/bin/sh
> perl -ne 'print "$1\n" if /^\s*(REM.*)%/i or /^\s*(REM.*)/i' $1 | remind -
> 
> (I am 100% certain a true Perl guru can combine the regexes, but
> I'm too lazy.)
> 
> Regards,
> 
> David.
> _______________________________________________
> Remind-fans mailing list
> Remind-fans@...
> http://lists.whatexit.org/mailman/listinfo/remind-fans

----- End forwarded message -----

http://todotxt.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/todotxt/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/todotxt/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:todotxt-digest@... 
    mailto:todotxt-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    todotxt-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

todo.txt enhancements

Logic of child tasks in todo.py

Does "child" mean that the child is a subtask of the parent task? 
Isn't it normal that you get child tasks completed before the parent?

If I do a child before the parent, I get the following:
$ t do 31
This task is a child of 30
Are you sure? (y/N)
y
Done 31: Order laptop cases
Archive done

A) 30 isn't the parent of 31, so that's a bug.
B) I don't understand why it must be confirmed.
C) I don't understand why it is archived.

Nic

http://todotxt.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/todotxt/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/todotxt/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:todotxt-digest@... 
    mailto:todotxt-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    todotxt-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Re: Logic of child tasks in todo.py

Hi Nic,

Sorry for the confusion.  I'm afraid child tasks is not really
supported properly in todo.py and I suggest you don't use it.  I'm not
even sure which versions out there have child tasks still in.  

I tried to rewrite child tasks for the jobdone project - but this is
currently stalled / broken / nasty.  It turned out to be quite a
tricky think to implement and everyone had a different idea of how it
should work.

I am now heavily into my MBA and don't have time for anything.  I've
even started using just plain vim with highlighting and some macros
rather than todo.py -- heresy!

My original idea for child tasks was that they were hidden from normal
view.  You would do the top task and the child would be promoted to a
top level task etc.  Doing child tasks is risky unless you have
indented done syntax -- you can see how it gets messy.

If you would like to describe how you think it should work then
someone might agree and modify todo.py!

Graham

--- In todotxt@..., "Nic" <yahoo <at> ...> wrote:
>
> Does "child" mean that the child is a subtask of the parent task? 
> Isn't it normal that you get child tasks completed before the parent?
> 
> If I do a child before the parent, I get the following:
> $ t do 31
> This task is a child of 30
> Are you sure? (y/N)
> y
> Done 31: Order laptop cases
> Archive done
> 
> A) 30 isn't the parent of 31, so that's a bug.
> B) I don't understand why it must be confirmed.
> C) I don't understand why it is archived.
> 
> Nic
>

http://todotxt.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/todotxt/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/todotxt/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:todotxt-digest@... 
    mailto:todotxt-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    todotxt-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Re: todo.txt enhancements

Hi D,

Some of your requests are already available in some shape or another.
 If you look at todo_cron.py in the repository you will see that it
does the repetition.  I use this daily and it works well for me. 
There are some bugs / features missing but it may suit you.

As for dependent tasks - this is what I refer to as child tasks.  I
started to code this in todo.py but as I mentioned in another post it
got rather complicated.  If you look at jobdone/todo.py you will see
another attempt using object orientation, but again unfortunately I
have left this in a rather unfinished state.

My solution to all this stuff at the moment is to use my favorite
editor (vim) to do everything other than todo_cron.py.  I just indent
child tasks by 4 spaces (like python code) and keep these indented
tasks out of the way using folding when above 4.

A very kind person on #vim wrote a script that sorts todo.txt files
with indented tasks by keeping the child tasks with the parent.  This
work very well.

Another innovation I've been employing is to sort my file in vim using
the above sorting script and then using this format for due dates:

(10/16) +todotxt  <at> email list about vim sort script
(10/17 09:00)  <at> out get the bus
(A) a random important event
+foo a normal event

This simple format keeps the most pressing things at the top of the file.

I then also use _keyword syntax to get things out of the way towards
the bottom of the file.  For example:

+todo normal task up here
_someday finish jobdone.py
_wait  <at> email from bob
----+task that requires reply from bob (---- are spaces)
_week +foo do something next week at some point... 
_month clean the house

This all sorts nicely using regular sort (if no children) or using
fancy IndentSort (if child tasks)

You can find the vim stuff in the editors folder in the repository. 
There is the script and a syntax highlighting file that all go in your
~/.vim folder in appropriate places.  See the readme in this folder
for more info:

http://todotxt.googlecode.com/svn/trunk/editors/

Sorry for the rushed explanation -- hopefully the other thread that
talks about vim will pick up this info too.

back to the grind...

Graham

--- In todotxt@..., Damian Glenny <dglenny <at> ...> wrote:
>
> Hi all,
> I confess - I became dissatisfied with todo.txt, and drifted off into 
> the realms of trying every *# <at> %ing online or cross-platform task
manager 
> on the planet. This has taken some time, it has to be said.
> 
> I am now heading back into the text-based fold somewhat sheepishly, but 
> I am determined to make a solid fist of it this time. To this end, I 
> would like to add the following features to todo.py:
> 
>     * task repetition - provide the ability for tasks to be re-inserted
>       into the task list on completion based on (flexible) syntax.
>       Perhaps something like:
>           o &week, &w, &weekly (repeat one week after marked as
complete)
>           o &week-mon (repeat next Monday after marked as complete)
>           o &mon-1 (repeat on the first of each month)
>           o &1-2- (repeat on the first of February each year. You m-d-y
>             people can submit a patch for a config parameter :) )
>           o etc
>     * task dependence - make one task 'not-doable' (for want of a better
>       word) until its dependent task is completed; perhaps show it in
>       gray text, and it would be nice for the tasks to display together
>       in the list
>     * group by project/context - I suspect that birdseye already does
>       this to most people's satisfaction
> 
> So, before I start hacking and changing - has anyone already done
any of 
> these? Any suggestions that don't involve ridiculously long syntax like 
> {2007-12-03 13:02:56 GMT} or REPEAT-every-month?
> 
> D
>

http://todotxt.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/todotxt/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/todotxt/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:todotxt-digest@... 
    mailto:todotxt-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    todotxt-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Re: Re: Logic of child tasks in todo.py

On Tue, Oct 16, 2007 at 02:22:24PM -0000, Graham Davies wrote:
> 
> Hi Nic,
> 
> Sorry for the confusion.  I'm afraid child tasks is not really
> supported properly in todo.py and I suggest you don't use it.  I'm not
> even sure which versions out there have child tasks still in.  
Well let's just avoid that, shall we ? 
> If you would like to describe how you think it should work then
> someone might agree and modify todo.py!
From where I sit, I'd todo.txt to keep entries in a vimoutliner .otl file.
when creating an item, todo.whatever should look for a line in the file
that matches the project, and slap the new todo under that. If I go and
indent the task, using vimoutliner, todo.scriptinglanguage should then see
that as a child task. todo.youknowwhat should otherwise ignore any line that doesn't
start with (SINGLEUPPERCASEALPHA) 
That way I could keep the todos neatly with other info and notes about the
project, in a magical folding text file. 
but that's just me.
also, I'd like to be able to do the same thing with "remind" entries. 
djp

http://todotxt.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/todotxt/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/todotxt/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:todotxt-digest@... 
    mailto:todotxt-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    todotxt-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Quick question about birdseye.py and projects with no open tasks