Live data from Hacker News

Keeping a plaintext “did” file

theptrk.com

11–20 of 202 posts

Re: Keeping a plaintext “did” file

#15

Isn't this effectively what code commits are for? If you've done something worth noting, it should probably be in a commit anyway.

Yeah commits are great for logging code changes.

I started using the did file while learning a new language, don’t remember which. I’d have 15 tabs open with different docs and tutorials but very very little actual code written or way to mark where I was. I settled on a single text file and It was super helpful to just look back a week and notice there was some measurable progress.

Re: Keeping a plaintext “did” file

#18
post #4
post #3

If the file does not exist, then vim +'normal Go' +'r!date' ~/did.txt creates a file with the first two lines being blank.

hm, good thinking, I guess I should run `touch` to create the empty file first.

> hm, good thinking, I guess I should run `touch` to create the empty file first.

vim is perfectly fine if you invoke it with the name of a non-existent file; it will just create it.

Re: Keeping a plaintext “did” file

#19
post #14
post #10

I have a windows notepad file for the same reason. F5 prints the date/time stamp.

or you can just start the file with: .LOG one of the few extra features notepad have =)

Wow! I truly wonder whether that's in there to scratch one Windows engineer's personal itch some day back in 1998 or something ;-)

Re: Keeping a plaintext “did” file

#20
Great idea. Welcome to the .txt family. A while ago I published Journal.TXT - a single-text file format for journals and the human multi-document format for writers. See https://journaltxt.github.io

PS: I also started Awesome .TXT - A collection of awesome .TXT tools, formats, services, tips & tricks and more. See https://github.com/officetxt/awesome-txt

Post reply on HN