4 ms·

What's it like with many shells/panes in multiplexers open? I often find my history from one or another either lost or not available across different ones.

by IanCal 3y ago

shawabawa3 3y ago
Syncs instantly between them You can optionally filter by the current window session, current machine, or commands across all machines you have atuin installed on
wodenokoto 3y ago
I believe it’s a setting. You can choose to save history and either merge history on session exit or immediately. At least it is a setting for zsh
- pletnes 3y ago
  You’d think this would be even more robust with a sqlish storage backend than the usual text files used for history.
  - gkbrk 3y ago
    Appending to files should be atomic, so I don't think you'll run into any corruption issues just by appending.
conradludgate 3y ago
With atuin, it's available immediately on other local session (panes, windows, tabs etc). There's also remote sync, so after some configurable amount of time, it's even available on other devices.
- ellieh 3y ago
  + if you don’t like this, you can have it filter by session by default!
  - niels_bom 3y ago
    Thank you for this awesome tool!
- IanCal 3y ago
  Spectacular, thanks!
brasic 3y ago
Works great! To me the reliable instant history sync between tmux panes is one of the best features of atuin. I tried many things to get this working with vanilla bash and it always seemed flaky.
Evidlo 3y ago
You can get that with bash with this config: # append to .bash_history and reread after each command export PROMPT_COMMAND="history -a;$PROMPT_COMMAND" # append to .bash_history instead of overwriting shopt -s histappend
- ptspts 3y ago
  Except that this doesn't save commands which haven't finished yet, and it never saves the current pending command when the shell is killed (e.g. the user closes the terminal window or logs out or the SSH connection is broken). Sometimes the rare, long-running commands are the most valuable. If I set up history software, it should preserve all history, and as early as possible.

What's it like with many shells/panes in multiplexers open? I often find my history from one or another either lost or not available across different ones.

by IanCal 3y ago

What's it like with many shells/panes in multiplexers open? I often find my history from one or another either lost or not available across different ones.

shawabawa3 3y ago

Syncs instantly between them You can optionally filter by the current window session, current machine, or commands across all machines you have atuin installed on

wodenokoto 3y ago

I believe it’s a setting. You can choose to save history and either merge history on session exit or immediately. At least it is a setting for zsh

pletnes 3y ago
You’d think this would be even more robust with a sqlish storage backend than the usual text files used for history.
- gkbrk 3y ago
  Appending to files should be atomic, so I don't think you'll run into any corruption issues just by appending.

conradludgate 3y ago

With atuin, it's available immediately on other local session (panes, windows, tabs etc). There's also remote sync, so after some configurable amount of time, it's even available on other devices.

ellieh 3y ago
+ if you don’t like this, you can have it filter by session by default!
- niels_bom 3y ago
  Thank you for this awesome tool!
IanCal 3y ago
Spectacular, thanks!

brasic 3y ago

Works great! To me the reliable instant history sync between tmux panes is one of the best features of atuin. I tried many things to get this working with vanilla bash and it always seemed flaky.

Evidlo 3y ago

You can get that with bash with this config: # append to .bash_history and reread after each command export PROMPT_COMMAND="history -a;$PROMPT_COMMAND" # append to .bash_history instead of overwriting shopt -s histappend

ptspts 3y ago
Except that this doesn't save commands which haven't finished yet, and it never saves the current pending command when the shell is killed (e.g. the user closes the terminal window or logs out or the SSH connection is broken). Sometimes the rare, long-running commands are the most valuable. If I set up history software, it should preserve all history, and as early as possible.