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:28:25 -0500 [thread overview]
Message-ID: <CAMP44s0gfi1jLFTN4vyQsjNOL_Zth1NHdc05JMx2a2+yHPGFAg@mail.gmail.com> (raw)
In-Reply-To: <a021d87e-6b58-7af9-a453-dac179cf5788@eastlink.ca>
On Sat, Apr 8, 2023 at 12:23 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
>
> On 2023-04-08 09:53, Roman Perepelitsa wrote:
> >
> > Yes. If you exit all shells, you'll have history from all of them
> > saved within $HISTFILE.
> >
> >
> I can't remember if it's stock or something I cobbled together for
> myself, but my history is updated in real time, I don't need to exit.
> All shells have all commands available from all other shells in real
> time. Only thing is that I have to press ENTER to update each shell to
> the current state. Tho my history selection function doesn't even need
> that, it's up to the second all the time.
You have SHARE_HISTORY on. It's not on by default.
Why not give a try to some minimal defauts?
mkdir -p /tmp/zsh
touch /tmp/zsh/.zshrc
ZDOTDIR=/tmp/zsh HISTFILE=/tmp/zsh/.history SAVEHIST=30 zsh
It seems nobody knows what vanilla zsh actually does.
> Mind, I've sometimes wanted to be able to isolate a shell from history
> and I expect that's easy, tho I don't know how.
Quite easy:
fc -p
It creates a new history stack (no $HISTFILE). To return to the previous one:
fc -P
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2023-04-14 14:42 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 ` .zsh_history Felipe Contreras
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 ` Felipe Contreras [this message]
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=CAMP44s0gfi1jLFTN4vyQsjNOL_Zth1NHdc05JMx2a2+yHPGFAg@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).