From: "Lawrence Velázquez" <larryv@zsh.org>
To: "OG Code Poet" <ogcodepoet@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Read/write multiple histories from non-interactive shell
Date: Mon, 13 Feb 2023 02:43:09 -0500 [thread overview]
Message-ID: <e3e4b8d6-a23c-4386-9f0a-6faa6a08e864@app.fastmail.com> (raw)
In-Reply-To: <CADmFDtV9uQk6u1OmobJiMAMm6kSo63M+L0q1hCsvmNr+4_L2Xg@mail.gmail.com>
On Mon, Feb 13, 2023, at 2:35 AM, OG Code Poet wrote:
> Should this also be copied to zsh-workers for feature request?
No, zsh-users is already forwarded to zsh-workers automatically.
--
vq
next prev parent reply other threads:[~2023-02-13 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 7:35 OG Code Poet
2023-02-13 7:43 ` Lawrence Velázquez [this message]
2023-02-13 8:18 ` Roman Perepelitsa
2023-02-13 8:57 ` OG Code Poet
2023-02-13 9:43 ` Roman Perepelitsa
2023-02-16 6:14 ` OG Code Poet
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=e3e4b8d6-a23c-4386-9f0a-6faa6a08e864@app.fastmail.com \
--to=larryv@zsh.org \
--cc=ogcodepoet@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).