🚀 go-pugleaf

Sirs,

  I just installed emacs 19.25 on my SPARCstation LX running SunOS 4.1.3C.
I've noted strange behaviour which I think is a bug.

  I prefer not to have a new X window pop up, so I called the executable
xemacs (in /usr/local/bin) and then created a one-line shell script called
emacs which contains the line  "xemacs -nw $*".  

  The problem is that when I exit this emacs the screen is not cleared,
leaving the status bar at the bottom of the xterm window, and worse yet,
the interrupt character is left as ^G, and there is no suspend character
(they should be ^C and ^Z).  Sometimes when I exit emacs it just hangs
and I don't get back to the shell at all.  I tried to demonstate the
problem using script, but emacs hung when I exited.  Here is what the
peudo-journalists call a dramatic re-enactment: 

    noether:myers> stty -a
    speed 9600 baud, 36 rows, 80 columns
    -parenb -parodd cs8 -cstopb -hupcl cread -clocal -crtscts 
    -ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc 
    ixon -ixany -ixoff imaxbel 
    isig iexten icanon -xcase echo echoe echok -echonl -noflsh -tostop 
    echoctl -echoprt echoke 
    opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel 
    erase  kill   werase rprnt  flush  lnext  susp   intr   quit   stop   eof
    ^?     ^U     ^W     ^R     ^O     ^V     ^Z/^Y  ^C     ^\     ^S/^Q  ^D     
    noether:myers> emacs
      [I just type ^X ^C, but status bar remains at bottom of screen]

    noether:myers> stty -a
    speed 9600 baud, 36 rows, 80 columns
    -parenb -parodd cs8 -cstopb -hupcl cread -clocal -crtscts 
    -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc 
    -ixon -ixany -ixoff -imaxbel 
    isig iexten icanon -xcase echo echoe echok -echonl -noflsh -tostop 
    echoctl -echoprt echoke 
    opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel 
    erase  kill   werase rprnt  flush  lnext  susp   intr   quit   stop   eof
    ^?     ^U                                        ^G                   ^D     

  This is not a problem if I use the basic executable xemacs.  It is not
a problem if I use "xemacs -nw".  It is not a problem if I use a shell alias
of emacs to xemacs -nw. It only seems to be a problem when emacs is run
from this shell script.  It happens whether it is a Bourne shell or C
shell script.

  I hope you can either fix this or suggest how I can get a default
command of "emacs" to fire up an emacs inside the xterm instead of
opening another window, with xemacs the alternative for poping a new
window for the emacs.  My users are new to unix and emacs and changing
the behaviour on them in such a radical way will confuse them.  

Thanks.


Eric Myers   	<myers@vassar.edu>  http://noether.vassar.edu/~myers/Myers.html
Department  of Physics and Astronomy       		Tel: 914-437-7080
Vassar College, Poughkeepsie, New York     		Fax: 914-437-5995