> On Apr 18, 2021, at 7:12 PM, Ananth Chellappa <ananth...@gmail.com> wrote: > > Even this guy https://paulh.consulting/ > thought it was easy before deciding it was worth $500 of his time to try > adding it :)
I don't know who "this guy" is. There are a lot of very skilled developers who aren't specifically versed in the paradigms or particulars of shells. There's nothing wrong with that, but it's also not really a compelling argument in favor of changing the fundamental behavior of a shell option. > analog@DESKTOP-O264A5N ~ $ set HISTFILE=/home/analog/.bash_history This does not set the HISTFILE shell variable or affect the history mechanism in any way. It clears all positional parameters except the first, which is set to 'HISTFILE=/home/analog/.bash_history'. > 2150 echo a private command <---- Yikes, this was in private mode! I > shouldn't see this after "exiting" > 2151 echo an evil command <---- private mode. LV suggested that using > HISTFILE unset/set would be be HISTFILE doesn't affect the internal history list, only the external history file. It wasn't clear to me that you cared about the former. -- vq
