zsh-users
 help / color / mirror / code / Atom feed
From: OG Code Poet <ogcodepoet@gmail.com>
To: zsh-users@zsh.org
Subject: Read/write multiple histories from non-interactive shell
Date: Sun, 12 Feb 2023 23:35:39 -0800	[thread overview]
Message-ID: <CADmFDtV9uQk6u1OmobJiMAMm6kSo63M+L0q1hCsvmNr+4_L2Xg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

Let's say there is a non-interactive script with multiple form fields (each
with a different vared), and a user can enter the form multiple times. I
want to preserve individual history for each form field.

There are two possibilities:

1. Keep history internal to the script
        I couldn't find an interface for this. Doing ``fc -p`` once in the
beginning of script does provide an internal history, but it is shared
between all vareds (which is not ideal).
2. Keep history external to the script
        Not all ``fc`` commands work. ``fc -R`` does read correctly from
external history files. But ``print -s``, ``fc-W`` and ``fc -A`` do not.
Seems the only option is to do an echo "$string"
>>~/path//form_entry_1.hist file. But I guess that has disadvantages
because it lacks the benefits that zsh provides in resolving duplicates.

Is there a way out? Should this also be copied to zsh-workers for feature
request?

Thanks!

P.S. I can be slow to respond.

[-- Attachment #2: Type: text/html, Size: 1187 bytes --]

             reply	other threads:[~2023-02-13  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  7:35 OG Code Poet [this message]
2023-02-13  7:43 ` Lawrence Velázquez
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=CADmFDtV9uQk6u1OmobJiMAMm6kSo63M+L0q1hCsvmNr+4_L2Xg@mail.gmail.com \
    --to=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).