[fa.info-vax] BRDCST

info-vax (02/28/83)

>From GEOFF@SRI-CSL  Sun Feb 27 21:36:39 1983
Received: by UCBVAX.ARPA (3.314/3.5)
	id AA08131; 27 Feb 83 21:40:19 PST (Sun)
Mail-From: ARPANET host SANDIA rcvd at 6-Jan-83 0834-PST
Mail-From: ARPANET site MIT-MC rcvd at 6-Jan-83 0933-MST
To: INFO-VAX@MIT-MC
Remailed-Date: 27 Feb 1983 0857-PST
Remailed-From: the tty of Geoffrey S. Goodfellow  <Geoff5 at SRI-CSL>
Remailed-To: Info-VAX@SRI-CSL.ARPA: ;

OK, folks, it now handles H19's.  Any other requests?

Anyone have any comments on my suggestion for rectifying the associated
mailbox problem?  I'd appreciate comments on my scheme before I send it in...

Stew

info-vax (03/22/83)

>From GEOFF5@SRI-CSL  Mon Mar 21 17:02:02 1983
Received: by UCBVAX.ARPA (3.331/3.17)
	id AA01357; 21 Mar 83 17:03:13 PST (Mon)
To: info-vax@SRI-CSL, Li-Kai@YALE, AWalker@RUTGERS
Cc: STEW@MIT-MC
Remailed-Date: 20 Mar 1983 2309-PST
Remailed-From: the tty of Geoffrey S. Goodfellow  <Geoff5 at SRI-CSL>
Remailed-To: Info-VAX@SRI-CSL.ARPA: ;

My BRDCST program ignores mailbox messages that are not broadcasts.  I use
it as a subprocess underneath Gosling EMACS all the time and have never
seen random messages (blank or repeats) delivered.  Perhaps you could
do a SHOW TERM while the problem is happening and send me the results
so I can compare with my system.

I like the idea of checking the terminal state before writing the message
on the terminal.  I've modified my BRDCST to write the message on the
terminal only if it is /NOBROADCAST or /PASSALL.  It is always placed
in SENDS.TXT.  Messages can, of course, be temporarily disabled by setting
the terminal to /NOBRDCSTMBX after the BRDCST program starts up.

The new version is available by FTP from MIT-MC as VAX; BRDCST MAR

Stew