Re: Random loss of bash history

[Linda Walsh]

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', serves little purpose
other than to potentially wipe someone's history and keep
it disabled -- when if that's really what they wanted, the'd
just turn the option off.

So, it's not a brilliant NEW feature.  It's a brilliant
design.  Period.

Happier?

(Sitting corrected...;-) )


Pierre Gaston wrote:
> On Fri, Oct 10, 2014 at 11:40 AM, Linda Walsh <bash@tlinx.org 
> <mailto:bash@tlinx.org>> 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 keep it all.
>
>     Perhaps you were hit by this brilliant new feature -- no doubt
>     a new POSIX blessing.
>
>
> Your ironic stance won't help your case.
> Especially when what you describe is not true, 0 in 4.2 means 0.
>
> $ HISTSIZE=10
> $ echo $BASH_VERSION
> 4.2.53(1)-release
> $ history
>   999  PS1=\$\
>  1000  HIST_SIZE=10
>  1001  echo $BASH_VERSION
>  1002  history
> $ HISTSIZE=0
> $ history
> $