mjhjmtu

Use case: distribute zsh's history between machines in source control.

Is that something that I can achieve with zsh's history -- put history in version control the sync between mahcines? This is to avoid re-typing commands and quick trace.

Modify PROMPT_COMMAND since it executes before each new prompt line.

11:40:22 jmunsch@pop-os network → export OLD_PROMPT=$PROMPT_COMMAND
11:52:38 jmunsch@pop-os network → unset PROMPT_COMMAND && export PROMPT_COMMAND="echo ssh copy the files to another machine; $PROMPT_COMMAND"
ssh copy the files to another machine
11:52:38 jmunsch@pop-os network → pwd
/etc/systemd/network
ssh copy the files to another machine
11:52:38 jmunsch@pop-os network → export PROMPT_COMMAND=$OLD_PROMPT
11:53:09 jmunsch@pop-os network → 

One possible way to do this, you can update the .zshrc on each machine, this would also work for a .bashrc, i'm not sure how reliable, or consistent it will be if a bunch of commands are running across multiple machines at the same time:

# across terminals, sessions, and machines
export machine1=192.168.43.70
export OLD_PROMPT=$PROMPT_COMMAND
unset PROMPT_COMMAND
export PROMPT_COMMAND="history -a; history -c; history -r; scp ~/.zsh_history $machine1:~/.zsh_history; $PROMPT_COMMAND"

history flags explained:

• 
  -a append the current session history to the history file


• 
  -c clear the sessions history


• 
  -r read the history file into the session history

scp explained:

• ssh copy your current ~/.zsh_history


• to a remote location on machine1 `$machine1:/home/someuser/remote/location


• you can do this for multiple machines by repeating the ssh copy for each address

To make it easier to do this

• Setup key based ssh login.


• Add hostnames/usernames to the .ssh/ssh_config.