From: Anthony Iano-Fletcher <Anthony.Iano-Fletcher@maths.nott.ac.uk>
To: zsh-workers@math.gatech.edu
Subject: interact
Date: Thu, 15 Jun 95 18:17:09 BST [thread overview]
Message-ID: <9506151717.AA26957@guinness> (raw)
I recieved no response to my question about how to turn control
over to a user for an interactive session part way through running
a zsh script, in the same way that you can in the expect language.
Ive looked at the source and it would seem that the command
source /dev/tty
will do most of what I want (except give a prompt and have the
zle command line editting work).
I have 2 options....
1. special case the command 'source /dev/tty' to set the
options INTERACTIVE and SHINSTDIN before the tty is
read in the source function in utils.c. You will still
get the original behavour using 'source //dev/tty'.
2. allow the source (and .) built-ins to accept a -i flag,i.e.
source -i /dev/tty
to force it into a fit state for an interactive session.
This involves small modifications to the source function in
utils.c and to the bin_dot function in builtins.c.
There is a slight variation is option 1 and that is to special case
'source /dev/xxxxx', whatever xxxxx may be.
I have implemented both versions to try them out and Im happy with
them all. I would welcome any comments.
To put this in its historical context.... this is not the first time
that I've wished to run a script setting up various functions and
variables and then wanted to pass control to the user. I find that
my only existing solution is clumsy.
Anthony.
next reply other threads:[~1995-06-15 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-06-15 17:17 Anthony Iano-Fletcher [this message]
1995-06-16 9:35 ` interact P.Stephenson
-- strict thread matches above, loose matches on Subject: below --
1995-06-16 12:32 interact Anthony Iano-Fletcher
1995-06-16 14:49 ` interact P.Stephenson
1995-06-08 11:17 interact Anthony Iano-Fletcher
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=9506151717.AA26957@guinness \
--to=anthony.iano-fletcher@maths.nott.ac.uk \
--cc=zsh-workers@math.gatech.edu \
/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).