No need for "normal Go". ex commands like r take addresses. vim +'$r!date' did.txt
Notably, this doesn't add the date at a reliable place in the file. Instead, it adds the date at the last place your cursor was when you had the file open last.
Keeping a plaintext “did” file
191–200 of 202 posts
Re: Keeping a plaintext “did” file
#192No need for "normal Go". ex commands like r take addresses. vim +'$r!date' did.txt
I think adding a command to go to the next line would be the sweet spot
Re: Keeping a plaintext “did” file
#193I was using Vimwiki for this stuff for long, but this idea seems promising for a daily journal. I mostly divide my tasks by day so I don't want timestamp to be added everytime I add an entry. Here's my aliases if it helps: alias ndid="nvim +'normal Go' +'r!date' +'normal o' +':exe \"normal i=============================\ \"' ~/Dropbox/did.txt" alias did="nvim +'normal G' +startinsert ~/Dropbox/did.txt" So use `n(ew)d…
You have a better memory than me. I would instantly forget whether or not I’ve added an entry for the day
Re: Keeping a plaintext “did” file
#194In my .zshrc I have todo() {vi '+$' ~/todo/$(date +Y/%m)} +() {echo + $* >> ~/todo/$(date +Y/%m)} -() {echo - - $* >> ~/todo/$(date +Y/%m)} Each month's entries are in a separate ~/todo/YYYY/MM file. The + command is to record something done. The - command is to enter a new task. The todo command is for editing this month's file -- add month-days, update entries, cleanup etc. Separately I have current and last 2 mont…
I have a thing for “want to do someday” called Asana but it’s never ending. My killer feature for a todo list would be either Auto Delete or auto “tell me a reason why I shouldn’t delete this”
Re: Keeping a plaintext “did” file
#195I just store all of my shell command-lines in a big file, including the date and current working directory. That way, I can always grep and see what I did. For stuff that doesn't happen on the commandline, I just type "echo" followed by a description of what I did, and it ends up in the history file just the same.
Lol at secret uses of echo. How are you logging your command line entries?
Re: Keeping a plaintext “did” file
#196I'll throw mine into the pile of other solutions posted here. I hope someone finds it useful: https://github.com/chrisallenlane/node-did
So do you have to keep this server running or do you have a separate nodemon script that auto starts on start up?
Re: Keeping a plaintext “did” file
#197In my .zshrc I have todo() {vi '+$' ~/todo/$(date +Y/%m)} +() {echo + $* >> ~/todo/$(date +Y/%m)} -() {echo - - $* >> ~/todo/$(date +Y/%m)} Each month's entries are in a separate ~/todo/YYYY/MM file. The + command is to record something done. The - command is to enter a new task. The todo command is for editing this month's file -- add month-days, update entries, cleanup etc. Separately I have current and last 2 mont…
I have a thing for “want to do someday” called Asana but it’s never ending. My killer feature for a todo list would be either Auto Delete or auto “tell me a reason why I shouldn’t delete this”
I wonder if you could script that with the API? Post a comment after a certain period of time and if you do not interact with it, delete the task.
Re: Keeping a plaintext “did” file
#198In my .zshrc I have todo() {vi '+$' ~/todo/$(date +Y/%m)} +() {echo + $* >> ~/todo/$(date +Y/%m)} -() {echo - - $* >> ~/todo/$(date +Y/%m)} Each month's entries are in a separate ~/todo/YYYY/MM file. The + command is to record something done. The - command is to enter a new task. The todo command is for editing this month's file -- add month-days, update entries, cleanup etc. Separately I have current and last 2 mont…
I have a thing for “want to do someday” called Asana but it’s never ending. My killer feature for a todo list would be either Auto Delete or auto “tell me a reason why I shouldn’t delete this”
In a way the whole point of making todo lists is mindfulness -- to pay attention to a task when needed. The point of automation is exactly opposite -- you don't want to pay attention to something!
A todo list is more effective if you do regular reviews (daily/weekly/month/yearly). Similarly mindfulness at the time of deleting a someday task may provide useful feedback.
Re: Keeping a plaintext “did” file
#199I'll throw mine into the pile of other solutions posted here. I hope someone finds it useful: https://github.com/chrisallenlane/node-did
So do you have to keep this server running or do you have a separate nodemon script that auto starts on start up?
There's no server here. This is just an executable written in node, which writes to a SQLite3 (flat-file) database.
Re: Keeping a plaintext “did” file
#200I put the author's terminal command into an Alfred Workflow: https://github.com/geberl/alfred-did-txt