2 ms·
Ctrl-R and sorting by time since the last run is nice, but odds are you run the same commands again and again WITHIN the context provided by the current directo
by csdvrx 2y ago
Ctrl-R and sorting by time since the last run is nice, but odds are you run the same commands again and again WITHIN the context provided by the current directory, so the cwd should be kept
Another important parameter is the number of successful runs: if you successfully ran the same command in the same directory 30 times in the last 30 days, it may be more useful that the one you have only run 1 time yesterday, so the exit value (like `false ;echo $?`) is another thing to keep
I have 2 bash shortcuts: one for a context-free search (Ctrl-T), while the default (Ctrl-R) is restricted to the current directory, and I throw everything (cwd, start time, stop time, exit value...) in a sqlite database to do more advanced queries (ex: on average, at which hour do I make more mistakes?)
- brigandish 2y agoCare to share the command(s) you're using to dump all that into SQLite?
- csdvrx 2y agoYou can get the config files from https://github.com/csdvrx/bash-timestamping-sqlite https://github.com/csdvrx/bash-timestamping-sqlite