Your ironic stance won't help your case.
Especially when what you describe is not true, 0 in 4.2 means 0.
FWIW, in the 4.3 README, under differences from 4.2:
n. Setting HISTSIZE to a value less than zero causes the history list to be
unlimited (setting it 0 zero disables the histor
I stand corrected... this isn't new. Still
when such numbers often mean unlimited and negative
ones are invalid, I see little or no utility in
truncating someone's histfile to 0. If someone wanted
to delete it, they would. Defaulting to truncation behavior
on changing those controls to '0'
On Fri, Oct 10, 2014 at 11:40 AM, Linda Walsh wrote:
> You DID read the release notes and changes from 4.2->4.3.
>
> Someone had the bright idea that .. in 4.2, '0' meant no limit in
> history (in bash and readline)... but in 4.3, '0' means 0 and throw
> away history while negative values mean ke
You DID read the release notes and changes from 4.2->4.3.
Someone had the bright idea that .. in 4.2, '0' meant no limit in
history (in bash and readline)... but in 4.3, '0' means 0 and throw
away history while negative values mean keep it all.
Perhaps you were hit by this brilliant new feature
Darshit Shah wrote:
> I'm running Bash 4.3.30(1)-release on Arch Linux. Recently after I rebooted
> by system I realized that all my Bash History had been erased. The
> ~/.bash_history file existed, but it was completely empty.
>
> The situation occurred just now once again. I boot up my system an
I'm running Bash 4.3.30(1)-release on Arch Linux. Recently after I rebooted by
system I realized that all my Bash History had been erased. The ~/.bash_history
file existed, but it was completely empty.
The situation occurred just now once again. I boot up my system and realize that
I have no b
