cmorgan@mntgfx.mentor.com (Clark Morgan @ APD x4813) (05/26/89)
Hello, Apollo users of MUSH.
I have been told that several Apollo users are having problems with
MUSH. I know of two problems with MUSH 6.4/6.5 (all patch levels).
I have fixes for both.
Problem #1:
Suppose you are running MUSH in Curses mode and iconify the pad
in which MUSH is executing. Suppose you then logout. You will
find that the DM can't kill the MUSH process :-( . Apply this
fix (by hand) to the function cleanup() in file signals.c:
Old code fragment:
#ifdef CURSES
if (iscurses)
iscurses = FALSE, endwin();
#endif /* CURSES */
New code fragment:
#ifdef CURSES
if (iscurses)
{
iscurses = FALSE;
if (sig != SIGHUP)
endwin();
}
#endif /* CURSES */
Notes:
a) This is not a MUSH problem, this is an Apollo problem.
b) Make sure the preprocessor directives (#ifdef and #endif)
begin in column 1!
c) Bart and Dan may add a patch similar to this to MUSH (they're
still discussing its merits), so make a copy of the original
signals.c and save it _before_ applying this fix so that you
can later patch with their future mods.
Problem #2:
If you use MUSH in Shell mode, you will find that interrupts
(^C/^Q) don't work. This is a big pain if you want to blow
away a message that you're composing. To work around this
problem, invoke MUSH thusly:
mush -e -S
The "-e" switch tells MUSH to not run in cbreak mode. In
non-cbreak mode, you will find that editing messages via
~t, ~s, etc. has changed. You will _not_ be prompted with
the old contents of the header. Instead, you must completely
retype the header. So it's a tradeoff. Which feature do
you want most in Shell mode?
--
Clark O. Morgan -- Mentor Graphics Corp.
cmorgan@mntgfx.mentor.com ...!tektronix!sequent!mntgfx!cmorgan