Newsgroups: comp.mail.mush
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!malgudi!kannan
From: kannan@oar.net (Kannan Varadhan)
Subject: Problems with mush version 6.4
Message-ID: <1991Apr23.205311.16097@oar.net>
Sender: kannan@oar.net (Kannan Varadhan)
Organization: Ohio Supercomputer Center
Date: Tue, 23 Apr 1991 20:53:11 GMT
Lines: 40


I am not sure if there is a later version than 6.4, but since I just got
it off tut.cis.ohio-state.edu, and installed it, I thought I'd mention
some problems here...

1.	`set asksub' does not force asking the user for a subject when
invoked directly from the commandline, as

		% mush luser

The fix is a one-liner as...

===================================================================
RCS file: RCS/main.c,v
retrieving revision 1.1
diff -r1.1 main.c
158c158
<       if (do_set(set_options, "ask"))
---
>       if (do_set(set_options, "ask") || do_set(set_options, "asksub"))


2.	This doesn't qualify directly as a bug, but...
Unless either "ask" or "asksub" is set, mush will put a 'Subject: <empty>'
line on the tty, and continue blissfully onward, much to the chagrin of
the lay user.

3.	mush checks for new mail, even when the user is in the midst of
composing a message....more chagrin.

4.	More as a feature request, could there be a settable variable,
say, `check_new_mail', which is by default turned on, but, when turned
off, will not check for, and display new mail status until the user
exits mush?


Kannan
-- 
Kannan Varadhan, Internet Engineer (OARnet),		+1 614 292 4137
Ohio Supercomputer Center, 1224, Kinnear Rd.,  Columbus, OH 43212