I struggled knowing where to put the script at step 2. ("place it somewhere in your $PATH."), so I ended up doing

alias plop='less ~/.zsh_history_ext | grep -a --color=never "${PWD}   " | cut -f1 -d"|" | tail'

in my .zshrc, it kind of does the job.

... you can just add following to your .zshrc file

function jog {
  grep -v "jog" ~/.zsh_history_ext | grep -a --color=never "${PWD}   " | cut -f1 -d"⋮" | tail
}

function zshaddhistory() {
  echo "${1%%$'\n'}⋮${PWD}   " >> ~/.zsh_history_ext
}

If I have a historical entry cat test | grep word when you run jog your output would be:

$ jog
cat test

instead of

$ jog
cat test | grep word

suggestion to use a special character for the break.
Something like: ⋮

On most systems, echo ... >> file will create a new file with permissions set to 664. However, .zsh_history_ext should be 600, the same as .zsh_history. I've created #10 to address this.

$ cd
$ echo '123
456'

$ cat ~/.zsh_history_ext
$ echo '123
456'|/home/user   

$ jog
456'

jog shows just the last line of a multi-line command

I don't get where the name comes from. Which is important to remember using new aliases.

How about herestory? Or cwdhist? Something else?

Thanks for creating this, I love a simple tool (yay for one liners!)

I may be missing something, but it’d be nice to have an easy way to run one of the commands in the history.

This would probably turn this into a not-a-one-liner-anymore, and maybe ZSH already has a way to turn that list into something runnable, but something like this would be cool (for me, at least 😅):

$> jog
1. ls -la
2. make
3. make clean
4. sudo rm -rf /

Type a number to run the command again, any other key to exit: [ ]

Alternatively, the ability to run a command with jog 3 would also be interesting.

Again, thanks for sharing!