notes VS Watson

I've documented some really cool things that vifm can do: https://github.com/sitaramc/notes/blob/master/vifm.mkd

So I wrote https://github.com/sitaramc/notes/blob/master/dac -- 30 lines of shell plus maybe another 30 or 40 of comments, and it does everything I want in a dotfile manager.

All this is painlessly taken care of by https://github.com/sitaramc/notes/blob/master/dac (documentation: https://github.com/sitaramc/notes/blob/master/dac.mkd)

If you have fzf installed, grab https://github.com/sitaramc/notes/blob/master/try, and run try dust. Then start typing -t jpg (for example). Then backspace over the jpg and change it to png. Or use some other options.

I hesitate to nominate any of them because (a) there are dozens or even hundreds of them and (b) I don't like any of them; I wrote my own because I needed a "hold" feature that no one had (i.e., when propagating changes to the repo, I want to hold back some parts of the change; https://github.com/sitaramc/notes/blob/master/dac.mkd explains better if you're interested

For those of you who are curious, https://github.com/sitaramc/notes/blob/master/vifm.mkd is my part "review" and part "tips and tricks" on vifm.

Most of my tools are in bash or perl, most of them less than 100 lines of code, (most of them are less than 200 even with comments). https://github.com/sitaramc/notes has all of them (terrible name for a repo full of tools I know; sorry!)

Absolutely vifm. My notes+tips/tricks on this at https://github.com/sitaramc/notes/blob/master/vifm.mkd

https://github.com/sitaramc/notes/blob/master/dac.mkd for documentation, https://github.com/sitaramc/notes/blob/master/dac.mkd for code, if you're interested.

if you're a vim user, you can't go wrong with vifm. My take on vifm is here: https://github.com/sitaramc/notes/blob/master/vifm.mkd -- can't hurt to give it a read (it's a wee bit outdated but not much; probably only the last section needs to be updated)

I like Watson https://github.com/TailorDev/Watson and it used to have a web backend (crick) but that seems to be abandoned.

For my particular use case, I use a cli timetracker called watson, code here:https://github.com/TailorDev/Watson

If you're a huge dork like me you could use watson, which I use for contract work. Say I'm about to start working on ticket XE-506 for Acme corp. When I start I run watson start Acme +XE-507, which assigns that task to Acme and tags it with XE-507 (multiple tags per entry supported too). At the end of the week, I run watson aggregate, which separates the logs into an aggregate of how much time I spent on what each day (helps if I leave a ticket during a day and come back to it).

I've used Watson for the past two years, and find it works well.

Nice. Take a look at Watson for another time tracking implementation.

hey! before you invest too much time into this, consider looking at: https://github.com/TailorDev/Watson