3 ms·
Nushell has a SQLite history mode which captures more metadata than is typical. I haven't looked into extending it, but it seems like a good setup for adding en
by __MatrixMan__ 3y ago
Nushell has a SQLite history mode which captures more metadata than is typical. I haven't looked into extending it, but it seems like a good setup for adding enough so that some of these cognitive requirements could be recovered from history rather than thought of up front.
Like if I tend to go down the wrong path, fix it, and then go down the right path, maybe that's a pattern that can be identified and then when I search history it finds two or three commands which together set me on the right path in the first place.
I mean, thinking ahead is always gonna be better, but I don't always.
- traviscj 3y agoI’ve done this enough times I chain the desired command and the cd together: cd ~/x/y/z && my-command So that when I CTRL-R for my-command it automatically reminds me.
- gumby 3y agoIf you’re doing this for history value put it in a subshell so it doesn’t change your working directory in a confusing way: (cd ~/x/y/z && my-command)
- chrisshroba 3y agoNeat idea, definitely going to use this! Thanks for sharing
- __MatrixMan__ 3y agocwd is one of the default fields. Here's my first nushell command: $ history | get 0 ╭─────────────────┬─────────────────────────────╮ │ start_timestamp │ 2023-12-15 15:39:12.872 UTC │ │ command │ ls │ │ cwd │ /home/matt/src/configs │ │ duration │ 31 ms │ │ exit_status │ 0 │ ╰─────────────────┴─────────────────────────────╯ It would take some smarts to figure out when to bind the cwd and when not to, but that would be the interesting part.