🚀 go-pugleaf

In article <2905@bingvaxu.cc.binghamton.edu> cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn) writes:
>1) Most of my scripts break in an annoying yet functional way.  I use
>the Sidekick editor for most of my scripts.  

Some editors write ^Z at the end of a file while others do not.  When
the editors write out ^Z the file size includes this so the shell was
quite willing to accept this as an input line and was not ignoring ^Z.
This has been fixed.  Send e-mail to me if you are having problems
with this.

>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.  It could
also be caused by SHELL being set wrong.  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.  Does
the programme that you are attempting to run require command.com with a
larger environment?  The Korn Shell's environment size is not fixed, it
can be as large as 64kb, and using the transient shell reduces the
size of the shell by 64kb so it should be able to run most programmes.

>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 :-)  You are actually editing a command from the shell
history file which has no blank lines.  If a blank line is needed to
type another command then ^C can be entered to interrupt the edit mode.
-- 
Andy Toy, Mortice Kern Systems Inc.,       Internet: andy@mks.com
  35 King Street North, Waterloo,       UUCP: uunet!watmath!mks!andy
      Ontario, CANADA N2J 2W9      Phone: 519/884-2270  FAX: 519/884-8861