Julia Evansstarted tracking todos for my programming side projects by just making a little (usually untracked) `todos.md` file in the project's directory and it's so much better than anything else I've ever tried
Owen Nelson@b0rk same. `~/Projects/notes.md` has it all for me.
Richard Littauer@b0rk can confirm. Is best way.
zaunkoenig@b0rk I agree that this is a good solution and always wondered if there is no better way. I knew people using OneNote, but it sucks.
Alex Willmer@b0rk I do similar with an untracked notes/*.md. A few files get promoted to Github Wiki pages for that project.
Ray Lee@b0rk same. I’ve been using the todo+ extension for vscode to add some key bindings and an archive ability, but it’s basically a markdown file. I like the idea of tools that progressively enhance text files.
sqrt(-1)@b0rk yes! this is the best way I've found so far
raphael@b0rk yeah, same. text editor of choice, markdown highlighting, ripgrep. i have yet to find any dedicated productivity/notetaking/knowledge management/snake oil app that comes close.
Dainius Happy 🇱🇹 ❤ 🇺🇦@anthroposamu @b0rk i didn’t try it because:
- closed-source
- electron
- does nothing i need that vim and ripgrep don’t do heaps better and faster
(but i did look at it, and discarded it alongside logseq, joplin, and zettlr)
@gekitsu sounds fair. I'm using it because i'm mainly living outside the command line and it saves files in a regular .md format.
@anthroposamu that, too, is entirely fair! it seems to work for a lot of people, and having the data in a format that’s not tethered to the software is certainly a big boon.
@gekitsu @anthroposamu I use both Obsidian and terminal based editor (Mostly #HelixEditor , but vi/m also works)
At times, I started the file in Obsidian and continued editing elsewhere (and vice versa) Beauty of text files (in this case Markdown)
Obsidian really shines when you need/use the plugins (Like excalidraw plugin by @zsviczian )
Jonathan Feldman@b0rk plaintext / markdown is literally the only thing that has ever worked for me for todo lists. I have tried a lot of apps! Nothing, for me, beats the flexibility and ease of a text file. So, go you!
sam.sh
Saul Pwanson@b0rk Agreed! It's the only way that works for me too. I call mine TODO.md (all caps for "meta" files, similar to README and LICENSE).
Gonzalo@b0rk maybe give Emacs and Org Mode a try? Could change your life :)
Faysal
Héloïse@b0rk have you created a shortcut in the org-agenda to access them or just open them as a regular file?
Sam Stokes@b0rk I wrote a very small bash script around this workflow so I could add todos with `todo Write readme` and cross them off with `todo -4`. https://gist.github.com/samstokes/5392339
Brandon Rohrer@b0rk the help-per-hassle ratio of this solution sounds astronomical
Philip Guo@b0rk yep it's old fashioned, but having things "near" what i'm working on helps so much ... i sometimes put todos directly in comments at the top of a file if it's file-scoped
Michael B. Johnson@b0rk mine is called DOING.md and I write down whatever I’m in the middle of before I switch context.
It’s so helpful. Been doing it for years, it works for me.
It’s so helpful. Been doing it for years, it works for me.
oisin@b0rk using magit I kind of like the idea of https://github.com/alphapapa/magit-todos but I also tend to accumulate todos I've no intention fixing any time soon which makes for an awful todo list
rudi@b0rk I do the same! Added a keystroke in emacs to open the current project’s todo.org file and it’s just the best thing.
Zekovski 🧣
Nicolas Delsaux@b0rk I tend to prefer creating github issues, as they feel more actionnable to me. I've long wanted to use https://github.com/git-bug/git-bug which feels more agnostic, provided I have a git repo
Zaͩnͦsͤt̀́rͤa̅̆̈@b0rk TextMate has a way of collecting all “#TODO:" items from all source code in the project. However, I think just one file with all TODO's is a better way to organize.
Also: I discovered a TODO list is not the same as the things I'm going “to do" today. I have a little notebook where I write what I'm going to do every day.
(maybe TODO.md is not the best name, but then again, what is the right name?)
kirchI used to use the Bash History for stuff like this, add comments to the command-line then `history | grep "#"` to see them ... but now I'm using this technique: https://github.com/todotxt/todo.txt
Chris M.@b0rk
I've been using todotxt.org from the command line for years. You can add projects via "+project" and filter by that. Simple, fast and thanks to my Nextcloud available everywhere on any platform
I've been using todotxt.org from the command line for years. You can add projects via "+project" and filter by that. Simple, fast and thanks to my Nextcloud available everywhere on any platform
requiem 🦫@b0rk this is great (I often put a section like this right in the README.md). I also tend to add a "journal.md" to each project where I just ramble as I work so there's at least some record of everything that doesn't quite make it into the more organized corners of the project.