From: Felipe Contreras <felipe.contreras@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: .zsh_history
Date: Fri, 14 Apr 2023 09:36:47 -0500 [thread overview]
Message-ID: <CAMP44s1dYQ=YWufkDYRcwtWvpuo0PV=M4hSZQ8gmMfF45DRfMQ@mail.gmail.com> (raw)
In-Reply-To: <f4514177-7d2a-cda1-b06c-4912951d41d5@eastlink.ca>
On Sat, Apr 8, 2023 at 12:54 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
>
> On 2023-04-08 10:27, Roman Perepelitsa wrote:
> >
> > Perry's options (which I've quoted in my original reply) require him
> > to exit zsh before history is written.
>
> I do remember that one's control of history is essentially perfect, you
> can get just about anything you want. History is one of those features
> of zsh that is tractable and understandable without too much head
> scratching and without any weird gotchas.
I couldn't disagree more.
Even zsh experts don't understand what HISTSIZE and SAVEHIST are for.
Nevermind their interactions with APPEND_HISTORY. Maybe the other
options are more understandable, but certainly not the basic ones.
Or you tell me, do you think everyone understands what this does?
HISTSIZE=100
SAVEHIST=200
--
Felipe Contreras
next prev parent reply other threads:[~2023-04-14 14:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 16:16 .zsh_history Perry Smith
2023-04-08 16:53 ` .zsh_history Roman Perepelitsa
2023-04-08 17:23 ` .zsh_history Ray Andrews
2023-04-08 17:27 ` .zsh_history Roman Perepelitsa
2023-04-08 17:35 ` .zsh_history Perry Smith
2023-04-08 17:54 ` .zsh_history Ray Andrews
2023-04-14 14:36 ` Felipe Contreras [this message]
2023-04-14 15:27 ` .zsh_history Ray Andrews
2023-04-15 4:49 ` .zsh_history Felipe Contreras
2023-04-15 15:29 ` .zsh_history Ray Andrews
2023-04-15 19:47 ` "Pull just the text of a single command" (was Re: .zsh_history) Bart Schaefer
2023-04-15 22:47 ` Ray Andrews
2023-04-15 23:26 ` Bart Schaefer
2023-04-16 15:53 ` Bart Schaefer
2023-04-16 16:37 ` Ray Andrews
2023-04-16 19:24 ` Ray Andrews
2023-04-16 7:38 ` .zsh_history Roman Perepelitsa
2023-04-16 14:53 ` .zsh_history Ray Andrews
2023-04-16 15:28 ` .zsh_history Bart Schaefer
2023-04-16 15:29 ` .zsh_history Roman Perepelitsa
2023-04-14 14:28 ` .zsh_history Felipe Contreras
2023-04-14 15:18 ` .zsh_history Ray Andrews
2023-04-14 14:00 ` .zsh_history Felipe Contreras
2023-04-14 14:51 ` .zsh_history 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='CAMP44s1dYQ=YWufkDYRcwtWvpuo0PV=M4hSZQ8gmMfF45DRfMQ@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@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).