Hi. @inkarkat I finally finished the add-ons I told you about weeks (months?) ago: https://github.com/silasdb/d ; https://github.com/silasdb/due
thanks for the help!
not sure if you (or someone else?) want to add them to todotxt.org add-ons page
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.
The obvious thing that I forgot to mention here (but I think had mentioned earlier already) is that for those date expansions to work, I override the built-in
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).
BTW,
d is such a small name that is easy to write but difficult to reason about. Do you see any problem with that?
@silasdb If there's a more descriptive longer name, that would be better. Though it should be trivial to rename, anyway. That's also the problem with my own setup; many of those commands are connected and dependent on each other, so it's hard to use just a few of them without adopting the whole setup. The code has been out there on GitHub for several years; I haven't received much feedback on it yet.
Trying to resolve the following: creation of todo.txt.bak file. I have been using Todo.txt for some time and just started using CLI on Linux Mint XFCE. Since then, the todo.txt.bak get created and IFTTT recurring "appends" are posted to that file and not todo.txt. I am using Dropbox for file location. All other devices, Android, Windows 10 (work), Chrome Extension are then not updated. Is there something to change with the CLI? Thanks in advance!
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
@kvnmck1986_twitter Have a look at https://github.com/todotxt/todo.txt-cli/discussions/327; there's a link to a workaround in there. And please comment if you think that such a feature should be built-in.
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.
ive found some libraries that ill probably end up writing my own script for, which is probably the easiest solve
@7596ff Ah, interesting! So you need the done date (or at least its month) and extract the show from the task text, right? Since this is a straightforward line-to-line translation,
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.
Hi, here is a little cli-tool to generate caldav calendar events with due dates from your todo.txt files (either webdav hosted or local) - https://github.com/szmt/simplelivingiscomplex
anybody?
excuse me, is there simple serverless js app?
1 reply
hi all, brand new noob to todo.txt. I am using the mac CLI from brew, and built an alfred workflow to be able to run a shell command to todo.sh. I am running into an issue where sometimes new tasks are appended to the lines of the prior completed task (looks like an iteration issue on the number) anyone run into this kind of problem before?
@AdamBD: I haven't had or seen that problem. But it sounds to me like it is a problem of inconsistent line seperators. Traditionally mac uses one char to mark line endings and unix uses a different one.
Take a look at https://formulae.brew.sh/formula-linux/dos2unix to make them consistant
/ where would I insert this into the flow?
The todotxt-CLI has a history in the unix world and mac has a history in both the unix (as macOS X was based on NeXt; a unix) and the mac world (mac 9 and earlier had no unix history). This can lead to some strange edge causes. Call the mac2unix before the CLI call that causes the problem. HTH
Hi, I'm new to Gitter and to todotxt. I love the idea of todotxt, but it seems mainly aimed at opensource developers. I thought I would use it to have a todo list on dropbox and use it via my PC, my iPhone and iPad. However, I couldn't find tools that worked for the iPhone on dropbox.
I am seriously investigating using excel instead. I suspect this will support my basic user level functionality. I would be interested in feedback on using some other tools than basic text editors or open source tools that have limited availability to a non developer. Note, I will probably print off my todo list occasionally to carry around in written form as well.