Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!leah!bingvaxu!cjoslyn
From: cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Some problems with the latest MKS Toolkit
Message-ID: <2920@bingvaxu.cc.binghamton.edu>
Date: 6 Feb 90 01:11:16 GMT
References: <2905@bingvaxu.cc.binghamton.edu> <1990Feb5.202345.6668@mks.com>
Reply-To: cjoslyn@bingvaxu.cc.binghamton.edu.cc.binghamton.edu (Cliff Joslyn)
Organization: SUNY Binghamton, NY
Lines: 59

Apologies for carrying on by News, my mailer's broken to UUCP these days.

In article <1990Feb5.202345.6668@mks.com> andy@mks.com (Andy Toy) writes:
>In article <2905@bingvaxu.cc.binghamton.edu> cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn) writes:
>>2) I have a script 'exdos.ksh': exec $COMSPEC -e:4000
>>	C> exit
>>This now hangs the machine.
>
>It is possible that you are exiting from your top-level shell.  

I should have clarified this: I also have an alias:

	alias -x exdos=". /mks/sh/exdos.ksh"

So when I enter:

	% exdos

I am *intending* to replaced my top-level shell with command.com.  This
*worked* on the previous version.  This is screwed up, I know, but there
used to be a *reason* for all this fooling around. . .

>It could
>also be caused by SHELL being set wrong.  

I have: export SHELL=/mks/bin/sh.exe

>No memory is being saved by
>exec'ing command.com from a subshell so using alias exdos="command -e:4000"
>should work better since this will avoid invoking another subshell.  

Yes, but I want to use exec to replace sh.exe with command.com.

>Does
>the programme that you are attempting to run require command.com with a
>larger environment?  

My intent is to replace sh.exe with command.com since even with the new
transient shell I can squeeze out a bit more RAM.  Maybe that's no
longer useful, or the transient shell breaks exec.  

Let's try to simplify this: should this work from the top level shell in
config.  5? It hangs for me now:

	% exec command.com

>>3) A much smaller point: in Emacs editing mode of the shell, in the
>>previous version typing down-arrow when at the end of the history list
>>would give a blank line.  Now it gives an error bell.  Perhaps this is a
>>"feature"?
>
>This is a feature :-)  

Oh, those damned features. . .at least make them switch-settable?
-- 
O------------------------------------------------------------------------->
| Cliff Joslyn, Cybernetician at Large, cjoslyn@bingvaxu.cc.binghamton.edu
| Systems Science, SUNY Binghamton, Box 1070, Binghamton NY 13901, USA
V All the world is biscuit shaped. . .