It's a logger. Or rather it's there for you to use, instead of for the things you write. You give it words, it logs those words and keeps them well-fed and safe. Just like that:
$ logrs test!
Noted.
Logrs will also give you recaps of days:
$ logrs show today
07:51 - Test for file display
14:09 - test!
It sorts them neatly into daily files in ISO (yyyy-mm-dd) format, into a folder of your choosing.
(by default, ~/logs/, but editable in the ~/.logrs dotfile which is created upon use.)
Install with cargo install logrs.
There's a search subcommand that wraps grep:
$ logrs search logrs
/Users/az/logs//2016-10-18: 10:59 - wheee more improvements to logrs
/Users/az/logs//2016-11-20: 16:13 - logrs test search string stuff.
Well, handy for you there's a repl mode. Simply call logrs repl and it will be just as if the
prefix was typed for you every time. Enter quit to... quit.
The format is as it is to complement grep, so every entry is on one line, and grep doesn't just
give you fragments. Plus, it forms a mini timestamp with the file name, which is also nice.
Did you ever have a really obnoxious boss, that will rub things in your face for months, should you forget or mess something up? I did. It wasn't great. The latter part can't really be helped, but the 'forgetting things' part, is well and easily solved by just entering a note into Logrs whenever you are done with something, a commit, a function, a ticket, a meeting, a conversation, and so on. This creates a very compact paper-ish trail that can be used to ward off annoying and micromanaging bosses, like a voodoo charm.
-
logrs --config-- In-program configuration of the info kept in the dotfile. -
logrs archive-- Moving all things older to a month to a different folder, to avoid cluttering grep results. This will probably be automatic with a dotfile option.