Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
RE: logout from interactive subshell
- X-seq: zsh-users 10837
- From: "Com MN PG P E B Consultant 3" <mn-pg-p-e-b-consultant-3.com@xxxxxxxxxxx>
- To: "Mikael Magnusson" <mikachu@xxxxxxxxx>
- Subject: RE: logout from interactive subshell
- Date: Thu, 12 Oct 2006 11:29:18 +0200
- Cc: <bug-bash@xxxxxxx>, "zsh-users Mailinglist" <zsh-users@xxxxxxxxxx>
- In-reply-to: <237967ef0610120210r1d3a8c57n8850a4872b846c77@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- Thread-index: Acbt30mgd9ldKYrzQRCNJST2eTn6AwAAIykw
- Thread-topic: logout from interactive subshell
> How about
> function rlogin() {command rlogin "$@"; exit}
> ?
Hmmmm.... I don't see how this could help me. Actually, your
solution would EXIT the shell I came from, after the login
has finished!! So I not only have to type all the "exit"s on
the remote host, I would even loose my current shell on the
local host.
Maybe to repeat what I would like to do:
A typical application would go like this:
rlogin foobar
DO SOME STUFF
cleartool setview myview # this creates a subshell
DO MORE STUFF
cleartool setview yourview # now I'm two subshells deep
DO STILL MORE STUFF
# Now I want to exit
exit
exit
logout
I would like to have a (interactive) command which does the final two
exits plus
a logout for me.
BTW, I could imagine a solution using 'expect', which does the login,
then hands
over the control to the user, and finally if the user is done, performs
the
exit and logout.
Ronald
--
Ronald Fischer (phone +49-89-63676431)
mailto:mn-pg-p-e-b-consultant-3.com@xxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author