61–70 of 75 posts
So, this syncs through a hosted server somewhere? Can I host my own? That information should be front and center imo, I didn't see in anywhere in the Readme.
I also did not like that it's hidden away in the code. It is easy to self-host it though. https://github.com/ddworken/hishtory/issues/7 I also did not enjoy that the install script is not in the repo.
I didn't see the install.py script in the repo. Would be a good idea to include it. What was much more interesting to me is how this tool hooks into the shell to record commands. This can be found here: https://github.com/ddworken/hishtory/tree/master/client/lib/...
Also, Github pro tip: Press `t` when on any github repo to bring up fuzzy matching that can be used to easily find any specific file.
Does it handle multiple writers on the same machine? For example two people ssh-ing with the same user to a remote machine with hishtory
Earlier quoted context omitted.
It just adds to it, your standard shell history is still there and completely unaffected by this tool. And if you prefer using your native shell's control-r you can also do that. > if I delete something using `hishtory redact` does it delete it from my native shell history too It does not (though if you think it should, please open an issue and I'm happy to add this!) > Also just a heads up, I find the demo gif to be…
Hi, Sometimes things slips into shell-history, it’s convenient to be able to redact it. Is the history visible and editable by the user ? ( does not have to be overriding a existing command )
Anyone/anything solving the issue of bash histories in multiple (intricated) tmux sessions is an INSTANT win !!!! [Q: can this tool help? As far as in understand, it seems that YEEEES!!!]
Just tried this, and it appears to cause a very significant lag (~2 sec) after each shell command. Removing the sourcing of the config from bashrc and opening a new shell immediately gets rid of the lag. Maybe it's because I have HISTSIZE set to a large value...
How does this compare to Atuin [0]? [0]: https://atuin.sh/
Atuin* also allows for opt-in sync, easily hosting your own server, and switching search context for your shell history (ie whether you want to search the current directory, session, host, or all history on all hosts). We also have a bunch of different search modes that query history differently (fuzzy, prefix, etc) But otherwise yes, the tools are pretty similar! Nice to see another in the space *: context, I'm the…
Earlier quoted context omitted.
Some apps only accept password in commandline. The better written ones might accept it in env but that will also stay in history. But if someone have access to your home they can put keylogger in the .profile/.bashrc so it's not really relevant...
Sure, but something like this also works well: `the-command --password $(read -s;echo $REPLY)`
also you still have the `export REPLY=password` in history.
sure you can source it out of file but, well, that file have same permissions (or looser! if you forgot to change) as your .bash_history file.
`cat password|command` is the safest one (or, well, something 12 factor app clowns hate, a config file)
How does this compare to Atuin [0]? [0]: https://atuin.sh/
Atuin* also allows for opt-in sync, easily hosting your own server, and switching search context for your shell history (ie whether you want to search the current directory, session, host, or all history on all hosts). We also have a bunch of different search modes that query history differently (fuzzy, prefix, etc) But otherwise yes, the tools are pretty similar! Nice to see another in the space *: context, I'm the…
There's an app for Macs with iCloud sync as well: https://loshadki.app/shellhistory/