Hacker News new | past | comments | ask | show | jobs | submit login

I've been doing something similar to track what I do at work for just over a year. I tried keeping a home journal with a similar technique, but it didn't stick.

I have a git repo set up, and I run: "vim `date -I`", which opens a text file named for the current date (2020-02-08 today for example). Then I'll put in notes about what it is I'm currently working on.

I've come up with the convention of separating tasks with three equal signs (===) and separating updates to a single task with (--).

The main thing it's been helpful for to me, which is honestly probably why I've kept up with it, is that I'm bad about doing my daily timesheets. So once a month when our accounting lady gets after me, I'll go back through my notes and fill everything in.




I use vim. Doing files based on timestamps sounds smart so I might steal that.

I used just one big file right now and one thing good about it is that you can search all your notes with one command.

I also use the uuid command to tag/reference sections. Then, I can just put the cursor on the uuid and hit '*' to jump right to that spot in the file.


Had never used `*` before. Turns out it's search for the word under the cursor. Handy.

I guess that's basically what you wrote, but I had to play with it a bit to understand.


A bit of a tip: while `*` is a search for a word onward, `#` is a reverse -- a search for a word backwards. Might help sometimes


Could you explain a bit more how you tag sections?

i have this function in .vimrc that puts in an entry header with the date + time. (use it as :Entry )

  "======================================================                                                                                                                                       
  "put an entry with the date/time (for keeping plan.txt)                                                                                                                                       
  "======================================================                                                                                                                                       
                                                                                                                                                                                              
  command! -nargs=* Entry call s:RunEntry()                                                                                                                                                     
                                                                                                                                      
  function! s:RunEntry()                                                                                                                                                                        
    let s:tm = "\n---" . strftime("%d/%m/%y %H:%M:%S") . "----------------------\n"                                                                                                             
                                                                                                                                                                                              
    execute "normal! i" . s:tm                                                                                                                                                                  
    " enter insert mode because it's time  to write stuff   now.                                                                                                                                  
    call feedkeys("i")                                                                                                                                                                          
  endfunction


I did this too, with the date and single keyword for future reference. That's said, I have difficulty to recall the topic if I reuse the same keyword.




Applications are open for YC Summer 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: