Hey @silasdb; great work, and thank you for publishing the results so that others can reuse them! As a wiki page, the todotxt.org add-ons page should be editable by everyone, so go ahead and add links to your work.
For my own configuration, I've achieved something similar, but I chose a different approach; I have a dateex extension of the date command, and I'm injecting this into all of todo.txt via a shell date() { dateex "$@"; }; export -f date function in todo.cfg. So I don't need a custom add-on like your d (but I think the way you've implement that as a wrapper is quite elegant), but I'm limited to generic dates (due:tomorrow) and cannot use shortcuts like due:+1.
add action, and process any m:marker or m:(marker with spaces) syntax by expanding human-readable or relative dates (and also relative task references), via this script. I could directly use my custom dateex there, but by overriding the original date command, it automatically also gets used in other add-ons (for example, I use a schedule command for tasks due in the future).
d is such a small name that is easy to write but difficult to reason about. Do you see any problem with that?
Hello everyone here! Just wanted to say @ransome1 I’m really enjoying Sleek. I read the message from @jason-mehmel and decided to try it. Congrats for your work.
thanks for the kind words. If you find any bugs or if you miss an important function, let me know: https://github.com/ransome1/sleek
pablito1755 Arcturus (Gitter): The original set of formatting rules are here : https://github.com/todotxt/todo.txt There is nothing explicitly mentionned about a whitespace at the start of the line. I would imagine it depends on individual client implementations. Some will surely be more forgiving than others.
pablito1755 I hadn't noticed that before, but per the docs it would seem "ls -f ical" should do it.
pablito1755-f : Specify the OUTPUT format, being 'text' (default), 'dot' or 'ical' or
'json'.
...
* 'ical' - iCalendar (RFC 2445). Is not supported in Python 3.2. Be aware
that this is not a read-only operation, todo items may obtain
an 'ical' tag with a unique ID. Completed todo items may be
archived.
sed or awk should be enough to parse and re-format as CSV. You can indeed write your own small add-on for it; this would allow a convenient todo.sh trek2csv > stats.csv invocation.
1 reply