Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem I see is that if I ssh into 5 different remote hosts in a day, most of the commands are not executed on my host and thus not part of the local (or shared, distributed) history.

I suppose this could be solved with either:

- Some kind of modified ssh that sends back the commands to my host

- Some kind of smart terminal that can analyze commands to build up the history

Any ideas on how to practically solve this problem?



Every terminal has text input, but keylogger might be the simplest solution.


A keylogger doesn't see the results of tab completion.


You could install atuin on all your remote hosts, but that's not always practical


I guess we need a PostgreSQL backend.


same concern. I will probably use atuin local because it seems so cool. but the beauty of the shell is that it is by default so universal and portable and small, so I don't like the idea of dependencies for my use of it on remote machines. mentally I've gotten used to the idea that my local shell env is a very different beast than "normal " shell.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: