Re:Which command did you run 1731 days ago?
by traviscj on Sunday January 21, 2024 @06:06AM
(#39077417)
I’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.
Re:Which command did you run 1731 days ago?
by gumby on Sunday January 21, 2024 @08:02AM
(#39078071)
If 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)
Re:Which command did you run 1731 days ago?
by chrisshroba on Sunday January 21, 2024 @11:14AM
(#39079774)
Neat idea, definitely going to use this! Thanks for sharing
Re:Which command did you run 1731 days ago?
by __MatrixMan__ on Sunday January 21, 2024 @07:12PM
(#39084481)
cwd 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.
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.