Mush 6.4 to 6.5 Patch Kit, Part 6 of 6

Sat Apr 29 03:52:24 AEST 1989

Since this piece of the patch is smaller, it seems a good place for some
editorial remarks.  As has been noted, the first 5 parts are the original
kit (or as much so as there can be an original of something that started
out as one 20k file and has turned into a 200k 6-part monster), and this
file represents some late-breaking but important bug fixes.

This kit has been posted with the full knowledge and consent of Dan Heller.
He just happens to be too busy right now to organize it.  (Actually, *I'm*
too busy right now to organize it either, and I sincerely hope that it is
just about finished consuming my spare time.  But having got started it's
hard to quit.)  This patch kit takes care of all currently known bugs in
mush 6.4, but it also throws in some new features, which may of course
have bugs of their own.

If you have general questions, comments, or even bug reports, there is
currently a mush mailing list: mush-users at garp.mit.edu, subscription
requests to mush-users-request at garp.mit.edu -- and there may soon be a
mush newsgroup: comp.mail.mush -- and some mush discussion appears on
comp.mail.misc.  Or just blaze away to Dan or me; obviously, considering
the monster we've created, we must *like* to get E-mail. :-) :-/ :-o
However, we encourage use of the mailing list and/or newsgroups first,
so that (a) bugs become general knowledge, both to cut down duplicate bug
reports and so they can be avoided by other users; (b) other mush users
have a chance to share their insights; (c) when questions are answered,
the largest possible audience sees the answers, cutting down repetition.

A complete copy of mush-6.5 can be obtained by anonymous ftp from
ucbvax.berkeley.edu, as a compressed tar file.  The file is mush-6.5.tar.Z
in directory pub.  This copy will be kept reasonably up-to-date as bug
fixes are made.  If you do not have ftp access, send mail to Dan Heller at
one of the addresses below -- he will be handling mailed copies.

				Bart Schaefer <schaefer at cse.ogc.edu>
				Dan Heller <island!argv at cad.berkeley.edu>
					or <dheller at cory.berkeley.edu>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Part 6 of the Mush 6.5 Upgrade Kit.  Read the instructions in part 1.
---------------------------------------------------------------------------
Prereq: Part5
*** mush-6.4/kit.check	Tue Apr 18 17:29:04 1989
--- kit.check	Tue Apr 18 17:29:04 1989
***************
*** 1 ****
!  Part5 
--- 1 ----
!  Part5-check 
*** phase2/README-6.5	Fri Apr 28 10:48:15 1989
--- README-6.5	Fri Apr 28 10:48:04 1989
***************
*** 1,7 ****
  Changes/bugfixes in Mush 6.5 from 6.4:
  --------------------------------------

! Changed VERSION to 6.5 and date to 4/03/89.

  [mmdf and suntools specific changes are at the bottom]

--- 1,7 ----
  Changes/bugfixes in Mush 6.5 from 6.4:
  --------------------------------------

! Changed VERSION to 6.5 and date to 4/17/89.

  [mmdf and suntools specific changes are at the bottom]

*** phase2/mush.1	Tue Apr 18 09:26:39 1989
--- mush.1	Fri Apr 21 13:19:10 1989
***************
*** 94,100 ****
  .I Mush
  (full word forms in parentheses):
  .TP
! \-b
  (\-blindcarbon, \-blind)
  The list of Blind Carbon Copy recipients is set on the command line.
  If more than one address or an address containing spaces is specified, the
--- 94,100 ----
  .I Mush
  (full word forms in parentheses):
  .TP
! \-b bcc-list
  (\-blindcarbon, \-blind)
  The list of Blind Carbon Copy recipients is set on the command line.
  If more than one address or an address containing spaces is specified, the
***************
*** 3174,3179 ****
--- 3174,3181 ----
  Neither the user or the hostname needs to match; only the domain name must
  be required to match.
  .RE
+ .\" Nroff note: RE takes us all the way out of TP, so step back in again.
+ .RS
  .sp
  Example:
  .sp
***************
*** 3237,3242 ****
--- 3239,3245 ----
  .sp
  Note that mail sent via redirection from the calling shell will not
  sign letters or append fortunes.
+ .RE
  .TP
  .B cdpath
  (String)
***************
*** 3300,3327 ****
  .B edit_hdrs
  (Boolean)
  When in letter-composition mode (via \fBmail\fR or \fBreply\fR, etc),
! the headers of the outgoing message is stored in the same buffer as
! the text of the letter.  So, if the editor is called to edit the message
! buffer, the headers of the message can be edited as well.  There are
! some restrictions, however.
  .sp
! There must be a To: header.  Without this, mush will not deliver the
! letter.  Instead, the editor must be reentered and a To: header with
! a valid recipient must be inserted.  Just because a valid Cc: header
! exists does not affect this restriction.  You may have as many To: and
! Cc: headers as you like.
  .sp
! The From: header must not be altered.  Altering this header will
! result in a warning and it will be replaced by a correct one.
  .sp
  The Date: header will always be replaced by one with a more accurate
! time and date stamp.  Therefore, changing or removing this header has
! no effect.
  .sp
  You cannot add a Status: header and blank headers are dropped.
  For example, if an empty Cc: header exists, the header will
! not show up in the outgoing message.  Therefore, leaving empty
! headers has no effect.
  .sp
  Aliases specified on the command line are expanded and put into the
  message buffer in their expanded form regardless of the value of
--- 3303,3333 ----
  .B edit_hdrs
  (Boolean)
  When in letter-composition mode (via \fBmail\fR or \fBreply\fR, etc),
! the headers of the outgoing message are stored in the same buffer as
! the text of the letter.
! So, if the editor is called to edit the message
! buffer, the headers of the message can be edited as well.
! However, there are some restrictions.
  .sp
! There must be a To: header.
! Without this, mush will not deliver the letter.
! Instead, the editor must be reentered and a To: header with
! a valid recipient must be inserted.
! A valid Cc: header does not remove this restriction.
! You may have as many To: and Cc: headers as you like.
  .sp
! The From: header must not be altered.
! Altering this header will result in a warning and it will be replaced by a
! correct one.
  .sp
  The Date: header will always be replaced by one with a more accurate
! time and date stamp.
! Therefore, changing or removing this header has no effect.
  .sp
  You cannot add a Status: header and blank headers are dropped.
  For example, if an empty Cc: header exists, the header will
! not show up in the outgoing message.
! Therefore, leaving empty headers has no effect.
  .sp
  Aliases specified on the command line are expanded and put into the
  message buffer in their expanded form regardless of the value of
***************
*** 3329,3335 ****
  However, if the user changes the headers using the editor and specifies
  aliases, those aliases will not be expanded if
  .B no_expand
! is set.  Otherwise, they are expanded as usual.
  .sp
  The headers Bcc: and Fcc: are removed as expected.
  .sp
--- 3335,3342 ----
  However, if the user changes the headers using the editor and specifies
  aliases, those aliases will not be expanded if
  .B no_expand
! is set.
! Otherwise, they are expanded as usual.
  .sp
  The headers Bcc: and Fcc: are removed as expected.
  .sp
***************
*** 3336,3348 ****
  One added side effect of
  .B edit_hdrs
  is that you can add an Fcc: header to specify a \*QFile Carbon Copy\*U.
! This must be a full pathname to a file or program.  For programs, the
! pathname must be preceded by a pipe character (|).
  .sp
  When using
  .B edit_hdrs,
! certain tilde escapes do