From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [BUG] APPEND_HISTORY leads to complete reread + rewrite of histfile
Date: Wed, 6 Dec 2017 11:52:37 -0800 [thread overview]
Message-ID: <CAH+w=7bFD30+KtKp5ibSOUaWjjO5ZoBwoLs2v8_VTrnfmp2zgg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bSdmPztA59b2DpAPxWN6-P0vqpYy7Qr6V_JtUdOvkc7g@mail.gmail.com>
On Wed, Dec 6, 2017 at 11:51 AM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
>
> This happens because of HISTSIZE and the various HIST_*DUP* options.
Er, please read "SAVEHIST" everywhere that I just wrote "HISTSIZE". Sorry.
next prev parent reply other threads:[~2017-12-06 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 19:31 Zeshy
2017-12-06 19:51 ` Bart Schaefer
2017-12-06 19:52 ` Bart Schaefer [this message]
2017-12-21 20:52 ` Zeshy
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='CAH+w=7bFD30+KtKp5ibSOUaWjjO5ZoBwoLs2v8_VTrnfmp2zgg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--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).