From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-users@sunsite.auc.dk (Zsh list)
Subject: Re: vared -h question
Date: Fri, 24 Dec 1999 22:07:03 +0000 [thread overview]
Message-ID: <E121cqJ-0002yP-00.1999-12-24-22-05-47@cmailg5.svr.pol.co.uk> (raw)
In-Reply-To: "Greg Klanderman"'s message of "Fri, 24 Dec 1999 12:56:49 EST." <14435.46049.340193.377803@pdx.itasoftware.com>
Greg Klanderman wrote:
>
> Hi,
>
> I'm trying to use vared to implement a simple read/eval/print loop:
>
> while cmd="" && vared -p "cmd: " cmd ; do
> ## send cmd to server on host:port and print result
> done
>
> I'd like to have history work, and if I use the -h flag I can access
> the shell's history, but vared does not store the history of my
> entered commands into the shell history it seems. So it's a bit
> useless. Is there any way to do what I want, ie add a line into
> the history?
(I've redirected this to zsh-users.)
The answer should be to stick `print -s $cmd' as the first command inside
the loop, as well as adding the -h flag to vared. Embarassingly (at least
in the latest 3.1.6++), that doesn't work properly because you don't get
the most recent command in the history, though you do get the second most
recent --- i.e. the third time round the while-loop you'll be able to
re-edit what you entered on the first.
This is just the latest in a huge line of off-by-one errors in the history
code. Anyone want to fix it?
Happy Christmas and a bug-free 1900 to all zsh users.
(yes, it's a joke. no, I'm not expecting the world to end.)
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
parent reply other threads:[~1999-12-24 22:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <14435.46049.340193.377803@pdx.itasoftware.com>]
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=E121cqJ-0002yP-00.1999-12-24-22-05-47@cmailg5.svr.pol.co.uk \
--to=pws@pwstephenson.fsnet.co.uk \
--cc=zsh-users@sunsite.auc.dk \
/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).