From: Perry Smith <pedz@easesoftware.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Ray Andrews <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: .zsh_history
Date: Sat, 8 Apr 2023 12:35:09 -0500 [thread overview]
Message-ID: <720C7A28-A3CD-4EDC-A8AB-52F56F02BD49@easesoftware.com> (raw)
In-Reply-To: <CAN=4vMpbHXhRn07Ng5cGrP+MDivNzo=7wC56PwgdYrR8AVahtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
> On Apr 8, 2023, at 12:27, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
>
> On Sat, Apr 8, 2023 at 7: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.
>
> Indeed, there are options that do this. All options are described in
> `man zshoptions`.
>
> Perry's options (which I've quoted in my original reply) require him
> to exit zsh before history is written.
Yea. I’ve seen those options. Generally that isn’t my pain point. It is (was) Apple’s session stuff and not having history from long ago.
Thank you all
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-08 17:36 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 ` Perry Smith [this message]
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 ` .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=720C7A28-A3CD-4EDC-A8AB-52F56F02BD49@easesoftware.com \
--to=pedz@easesoftware.com \
--cc=rayandrews@eastlink.ca \
--cc=roman.perepelitsa@gmail.com \
--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).