Re: bash history
On Sun, Jul 28, 2024 at 12:25 AM Mike Castle <dalgoda+debian@gmail.com> wrote:
>
> On Sat, Jul 27, 2024 at 2:50 PM mick.crane <mick.crane@gmail.com> wrote:
> > Is this something that can be changed so history is shared between
> > virtual terminals?
>
> [...]
> For me, I see up bash with the following features:
> * Unbounded history
> * History is immediately saved to disk after each command finishes
> * I keep history under source control (currently git) and regularly
> (well, for some definition of "regularly"), merge them across machines
This is an unusual use case (to me). Why do you save history in a
version control system?
> [...]
> For the record, I deal with the expected conflicts when merging
> history files across machines by using a simple python program that
> parses the history file (that includes the timestamps), discards the
> conflict markers, orders by timestamps, and writes it back out. It is
> by no means perfect, but "good enough for me".
>
> For those worried about the unbounded history, I started doing that
> about ten years ago and my work history is currently just shy of
> 180,000 commands. It would likely be less if I turned on the
> "erasedups" feature, but I like to keep the context. And I've seen
> comments about folks who have multiple decades of shell history. On
> modern machines, it simply isn't an issue.
Out of curiosity, do you scrub the file regularly for credentials,
like usernames and passwords, and remove entries?
Jeff
Reply to: