todo.sh CLI doesn't read config file
I installed the `Todo.txt CLI` with Homebrew:
$ brew install todo-txt
I then attempted to create a new task:
$ todo.sh add "Test"
Fatal Error: Cannot read configuration file /Users/Mike/.todo/config
I can fix this by creating a symbolic link to todo.cfg:
$ sudo ln -s /usr/local/Cellar/todo-txt/2.10/todo.cfg /Users/Mike/.todo/config
But, I'm guessing that the symlink will break the next time Brew updates the todo-txt program. Is this the case?
If so, is there a more elegant way to overcome this?
If you are on the Mac platform, please consider trying TodoTxtMac, which is a free, open source native Cocoa todo.txt app. I have put a lot of work into it since its initial release, about a year ago, and it has matured into a fast, attractive, and stable GUI client with a ton of features. It is keyboard-centric, like Todotxt.net on Windows (which I also contribute to). If you tried it before and passed on it, please try it again. I'd love more users.
Web site (with screenshots): TodoTxtMac
I am getting back into the habit of using my todo list and I have created several IFTTT recipes to sync events with my todo list.
For example if i create a new Google Calendar event it is added to my todo.txt. I also create a daily review item. I am looking to see if there is any addon services to do the opposite - add a Google Calendar event when I create a new todo item?
I've looked at the addons and I can't find what I am looking for - I don't know if I am not looking hard enough or if it doesn't exist. Or if I can hack a solution using something like IFTTT, Pipes, or Zapier.
Hi, I'm a huge fan of the todo.txt idea. It's all very well-done. I just have one nit: it'd be nice if tarball'd releases preserved the executable bit on todo.sh. Then you could just tell people to extract with tar, instead of having to invoke chmod. Based on the group ownership in the archive, I'm guessing you're on Mac OS X, right? On my GNU Tar, executable bits are preserved when creating tarballs, and based on the FreeBSD tar(1) manpage I found, it seems like that version preserves executable bits, too. Perhaps Apple has patched FreeBSD tar to do weird things? I'd go ahead and report a GitHub Issue, but apparently I need to check with this list first. Hence this email. Thanks, Alex Jordan
How does the todo.txt file format work with non latin character sets ? Are there rules for languages like Japanese, Traditional Chinese, etc. regarding the fixed tokens ?
e.g, does a Japanese user need to mark a completed task with 'x' or can one use a kanji/katakana character ? Idem for priority (X) markers.
What if one of these tokens need more than one character ?
Are there todo.txt-related tools that already deal with these languages ?
Thanks in advance,
Sorry - I ain't a computer genius...
I have zsh as my default shell running inside OSX 10.9's Terminal app. Todo.txt is not displaying any colors. I assume this has got something to do with the bash being called by the todo.sh script. But, I ain't a computer genius...
Any suggestions on how to get colors working?