From: Bernd Eggink <eggink@uni-hamburg.de>
To: Zsh Workers <zsh-workers@sunsite.auc.dk>
Subject: Re: BUG: vared in script (was: vared in function)
Date: Thu, 1 Jun 2000 09:58:06 +0200 [thread overview]
Message-ID: <20000601095801.A370@eggink3.rrz.uni-hamburg.de> (raw)
In-Reply-To: <E12xGSP-0006NP-00.2000-05-31-22-55-21@mail2.svr.pol.co.uk>; from pws@pwstephenson.fsnet.co.uk on Wed, May 31, 2000 at 10:55:21PM +0100
On Wed, May 31, 2000 at 10:55:21PM +0100, Peter Stephenson wrote:
> Bernd Eggink wrote:
> > Argh...
> >
> > # t
> > vared -cp "Aha: " BLAH
> >
> > % t
> > t:vared:2: ZLE not enabled
> >
> > This breaks lots of my scripts!
> > On the command line, 'vared' works.
>
> (I take it that should be `script' rather than `function' in the subject
> line, functions are OK.)
Yes, of course. It has been rather late in the evening...
> I don't think there's any good reason why zle shouldn't be enabled
> especially, if it can find a terminal which it can, but until whoever made
> the change takes a look you can workaround it by giving zsh the -i option
> to run the script interactively. That might have other side effects,
> though.
It has.
# t
vared -cp "Aha: " BLAH
print $BLAH
% zsh -i t
Aha: hm
hm
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
t:zsh:3: use 'exit' to exit.
Regards,
Bernd
--
Bernd Eggink
Regionales Rechenzentrum der Uni Hamburg
eggink@uni-hamburg.de
http://www.rrz.uni-hamburg.de/eggink/BEggink.html
prev parent reply other threads:[~2000-06-01 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-31 21:06 BUG: vared in function Bernd Eggink
2000-05-31 21:55 ` Peter Stephenson
2000-05-31 22:28 ` Peter Stephenson
2000-06-01 0:00 ` Bart Schaefer
2000-06-01 4:55 ` Bart Schaefer
2000-06-01 7:58 ` Bernd Eggink [this message]
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=20000601095801.A370@eggink3.rrz.uni-hamburg.de \
--to=eggink@uni-hamburg.de \
--cc=zsh-workers@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).