todo.txt-cli VS zk

FSNotes for macOS and iOS is one I used for a little while.

https://fsnot.es/

todo.txt is another thing that comes to mind.

http://todotxt.org/

And of course pretty much all of *nix.

Since at least 2012 I've also been using a text file format from http://todotxt.org/ and more recently I wrote a program that takes a crontab-like list to pre-generate entries on a daily, by-day-name (every Sunday for example), and I also pull in a list of holidays from gov.uk, so they are also populated.

[^1]: (https://github.com/blacksmithgu/obsidian-dataview)

It's a web app implementing the todo.txt format (see http://todotxt.org/). It's an exercise to learn frontend currently, I doubt I could successfully monetize it. Would appreciate any feedback!

That format is really similar to todo.txt format, worth taking a look at http://todotxt.org/ (which in turn has application links).

For todo and schedule I use todo.txt (http://todotxt.org/) a plain file managed by scripts which build agenda and plumber to keep track of unique keys.

The ToDo.Txt format makes it easy to use across devices/software, but this is really limited to ToDos.

Here’s the todo.sh features for those interested. There are several addons for it as well: https://github.com/todotxt/todo.txt-cli

Good idea, something similar to todotxt.org. But no 1) iPhone app 2) you need to sigh up and keep your notes at developers servers 3) subscriptions?! come on!

There are a couple different routes you can go down. If your goal is to learn CLI stuff, it's hard to beat using shell-scripting for a simple app like a todo manager. Storing them in a plain-text file, a little sed/grep/awk and you're well on your way. For inspiration & hints, you might check out https://todotxt.org However, you can rapidly hit performance issues and limitations on available tooling if you stick to just POSIX tools.

I use org-mode with the journal plugin, but I'm soon going to switch to zk[0]. My technique is called interstitional journaling[1], and I just keep track of my location (I travel a lot) and the date, which gets generated by org. You can set up an interstitional journal in anything though, Logseq[2] supports it out of the box.

[0] (https://github.com/mickael-menu/zk)

Personally, I'm using zk for now. What's nice about is that it aims to be a common-denominator between all the popular zettelkasten markdown formats out there. So the notes you write with it will be forward-compatible with many other note-taking apps like Obsidian.

If you want to go full terminal workspace - you could use Zk (https://github.com/mickael-menu/zk) + editor of your choice. It is just markdown under the hood, but it comes with quite a few good features that majority of the tools have now (tags, backlinks, front matter, templates, etc). I wrote a post about my setup literally yesterday (it was a bit more editor oriented though) https://www.reddit.com/r/HelixEditor/comments/144x6r3/escape_hatch_xd/

I selected Helix as it is phenomenally fast, I love out of the box feature set, key bindings are intuitive and it looks sick :) To manage my notes I found ZK - very cool CLI with extensibility in mind.

I use https://github.com/mickael-menu/zk

For now, with a couple aliases wrapping nb as I try it out. I'm also planning to give https://github.com/mickael-menu/zk a shot, it looks to be almost exactly what I'm looking for an offers a vim plugin to boot.

mds is grepping notes' names and items' names (links and code snippets). and also moving forward/backward along the graph. I used to use https://github.com/mickael-menu/zk, it was messing me up, giving too much info, each line of every file.

Big fan of zk and zk-nvim. The biggest drawback was that link insertion depended on cmp, but now there's work to add linking as a direct LSP command. I've been using that since it's been merged in, and it makes creating and linking notes on the fly a breeze!