From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Run builtins, functions, etc. under zpty
Date: Mon, 6 Nov 2000 06:59:59 +0000 [thread overview]
Message-ID: <1001106065959.ZM11686@candle.brasslantern.com> (raw)
In-Reply-To: <1001105223736.ZM1787@candle.brasslantern.com>
On Nov 5, 10:37pm, Bart Schaefer wrote:
}
} This patch copies code from the clone module into newptycmd(), so that the
} forked process set up on the pty is initially a clone of the current shell.
} Then instead of calling execve(), the command can be parsed and executed
} with execode().
I forgot that this requires a change to nslookup.
Also, I committed a tweak to newptycmd() after sending the patch in 13123,
to unset `interactive' in the cloned shell before calling execode(). This
seems like the right thing to do; the clone itself isn't interactive any
more, even if the command it's eval'ing probably is, and it prevents the
saving of history or sourcing of .zlogout should an `exec' or `exit' be
performed in the clone. (Patch for that not included here, it's in CVS.)
Index: Functions/Misc/nslookup
===================================================================
@@ -24,7 +24,7 @@
[[ -z "$pager" ]] && pager="${opager:-more}"
(( $#pmpt )) || pmpt=(-p '> ')
-zpty nslookup nslookup "$@"
+zpty nslookup command nslookup "${(q)@}"
zpty -r nslookup line '*
> '
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-11-06 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-05 22:37 Bart Schaefer
2000-11-06 6:59 ` Bart Schaefer [this message]
2000-11-08 12:38 ` Andrej Borsenkow
2000-11-08 16:48 ` Bart Schaefer
2000-11-08 17:15 ` Andrej Borsenkow
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=1001106065959.ZM11686@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).