Why would you want syncing? Different machines have different file layouts and different installed executables. Any common commands are either coincidental or part of some fleet operation better managed through an actual remote management system.
Atuin replaces your existing shell history with a SQLite database
181–190 of 198 posts
Re: Atuin replaces your existing shell history with a SQLite database
#182Is there a Windows/Powershell port coming anytime soon? Honestly this is the one tool missing from my macOS workflow that I can't cross plat yet.
Re: Atuin replaces your existing shell history with a SQLite database
#183Earlier quoted context omitted.
there's this little gotcha you might want to be aware of: https://github.com/ellie/atuin/issues/752#issuecomment-14518...
Can you tell me if my understanding of this issue is correct? Let's say I run a command where I've pasted in a credential from my password manager: ` some-cli login username my-secret-password` (note space at beginning) Normally this would prevent the command from getting saved in any meaningful way in my bash history, so that if I later run a malicious script, it can't collect secrets from my bash history. With the…
Re: Atuin replaces your existing shell history with a SQLite database
#184I found atuin introduced friction where there wasn't any before, so I stopped using it and reverted to ripgrepping zsh_history.
Do you remember what that friction point was?
Re: Atuin replaces your existing shell history with a SQLite database
#185The 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 t…
Re: Atuin replaces your existing shell history with a SQLite database
#186I always wondered if one could feed history into some abstract parser (or nowadays, maybe a LLM) to extract the most frequent "idioms": ls | grep | less vs ls ~ | grep .bak | less ls .config | grep *rc | less you get the idea
Re: Atuin replaces your existing shell history with a SQLite database
#187Earlier quoted context omitted.
Most stemming use cases are trivially solved with a regex. That's the point he was making. The difference between a beginner and expert with regexes is quite a lot.
Ahhh, interesting point. "We could learn advanced regexes... or we could just use FTS5". Hard call. :)
Re: Atuin replaces your existing shell history with a SQLite database
#188Re: Atuin replaces your existing shell history with a SQLite database
#189Earlier quoted context omitted.
Most stemming use cases are trivially solved with a regex. That's the point he was making. The difference between a beginner and expert with regexes is quite a lot.
Ahhh, interesting point. "We could learn advanced regexes... or we could just use FTS5". Hard call. :)
Re: Atuin replaces your existing shell history with a SQLite database
#190There's also McFly which does the same thing. https://github.com/cantino/mcfly I've only used McFly and found it to be pretty great. My only complaint is the default search mode is SQL strings, so you have to use `%` for wildcards. I wish it was a more forgiving, less exact search. Has anyone used both and could compare them?