Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: SSD-friendly history
- X-seq: zsh-users 28184
- From: Dominik Vogt <dominik.vogt@xxxxxx>
- To: Zsh Users <zsh-users@xxxxxxx>
- Subject: Re: SSD-friendly history
- Date: Thu, 6 Oct 2022 00:19:10 +0100
- Archived-at: <https://zsh.org/users/28184>
- In-reply-to: <CAH+w=7Y1_9Y83pmzj7j0tEBRF25atwZ1Owp1kQY_xLL8C_jh6Q@mail.gmail.com>
- List-id: <zsh-users.zsh.org>
- Mail-followup-to: Zsh Users <zsh-users@xxxxxxx>
- References: <Yz34Wf67KJolrztr@localhost> <CAH+w=7Y1_9Y83pmzj7j0tEBRF25atwZ1Owp1kQY_xLL8C_jh6Q@mail.gmail.com>
- Reply-to: dominik.vogt@xxxxxx
On Wed, Oct 05, 2022 at 03:50:43PM -0700, Bart Schaefer wrote:
> On Wed, Oct 5, 2022 at 2:34 PM Dominik Vogt <dominik.vogt@xxxxxx> wrote:
> > I'd really like to have a mechanism that appends to the history
> > until some maximum size is reached and then truncates it to some
> > much smaller size
>
> Setting INC_APPEND_HISTORY will cause the file to be rewritten only
> when it reaches 20% larger than SAVEHIST. There's no option to make
> that greater than 20% at this point.
>
> However, this would be a reason to make SAVEHIST a lot larger than
> HISTSIZE.
Disk space is not an issue. So, if I set
SAVEHIST=120000
HISTSIZE=100000
Then only 100.000 lines are loaded when the shell starts?
--
But how does this interact with duplicate handling, especially
with HIST_EXPIRE_DUPS_FIRST?
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
Messages sorted by:
Reverse Date,
Date,
Thread,
Author