zsh-workers
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH 2/2] Increase default HISTSIZE to 1000
Date: Fri, 2 Sep 2022 04:49:44 -0500	[thread overview]
Message-ID: <CAMP44s0FbV1Ku1LpbESM7EYOXOWk+94cwP3KcdFqKm47iZymcQ@mail.gmail.com> (raw)
In-Reply-To: <20220902090132.GG5920@tarpaulin.shahaf.local2>

On Fri, Sep 2, 2022 at 4:01 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> Felipe Contreras wrote on Tue, Aug 30, 2022 at 22:18:54 -0500:

> > If the default is sensible it's not necessary for the user to change it.
> >
> > Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> > ---
> >  Etc/FAQ.yo                            | 13 +++++--------
> >  Functions/Newuser/zsh-newuser-install |  1 -
> >  StartupFiles/zshrc                    |  2 +-
> >  configure.ac                          |  2 +-
> >  4 files changed, 7 insertions(+), 11 deletions(-)
> >
> > diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
> > index dd573767e..4c058c363 100644
> > --- a/Etc/FAQ.yo
> > +++ b/Etc/FAQ.yo
> > @@ -1626,19 +1626,16 @@ work?)
> >  sect(Why is my history not being saved?)
> >  label(321)
> >
> > -  In zsh, you need to set three variables to make sure your history is
> > +  In zsh, you need to set two variables to make sure your history is
>
> If 1/2 is accepted, this sentence will be true for zsh 5.10

No, it's true for all versions of zsh.

Right now the default value of HISTSIZE is 30, therefore the text is
wrong, you don't need 3 variables, you only need 2: HISTFILE and
SAVEHIST.

In fact, I just learned APPEND_HISTORY is on by default, this means a
HISTSIZE of 30 is actually quite useful. You don't need to increase it
to make sure your history is written, you only need to increase it to
make sure you don't lose any history of your current shell instance.

Either way you don't *need* to set it, with this patch or without it.

And patch 1 certainly doesn't change the situation. All it does is
make sure SAVEHIST is the same as HISTSIZE, whether it's 1000, 200, or
30. HISTSIZE can be removed regardless of the previous patch.

-- 
Felipe Contreras


  reply	other threads:[~2022-09-02  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  3:18 [PATCH 0/2] Useful default of HISTSIZE Felipe Contreras
2022-08-31  3:18 ` [PATCH 1/2] Set SAVEHIST to $HISTSIZE by default Felipe Contreras
2022-09-02  8:59   ` Daniel Shahaf
2022-09-02  9:29     ` Felipe Contreras
2022-09-02 10:01       ` Daniel Shahaf
2022-09-02 13:25         ` Felipe Contreras
2022-09-06 20:13           ` Felipe Contreras
2022-08-31  3:18 ` [PATCH 2/2] Increase default HISTSIZE to 1000 Felipe Contreras
2022-09-02  9:01   ` Daniel Shahaf
2022-09-02  9:49     ` Felipe Contreras [this message]
2022-08-31  3:39 ` [PATCH 0/2] Useful default of HISTSIZE Lawrence Velázquez
2022-08-31  5:57   ` Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMP44s0FbV1Ku1LpbESM7EYOXOWk+94cwP3KcdFqKm47iZymcQ@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).