From davidw@u.washington.edu Mon Aug 15 16:05:09 PDT 1994
>From davidw@cac.washington.edu  Mon Aug 15 16:05:08 1994
Return-Path: <davidw@cac.washington.edu>
Received: from mx3.u.washington.edu by wells.u.washington.edu
	(5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA47743;
	Mon, 15 Aug 94 16:05:08 -0700
Received: from red2.cac.washington.edu by mx3.u.washington.edu
	(5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA03065;
	Mon, 15 Aug 94 16:05:07 -0700
Received: by red2.cac.washington.edu
	(5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA29810;
	Mon, 15 Aug 94 16:05:06 -0700
Date: Mon, 15 Aug 1994 16:05:06 -0700 (PDT)
From: David Wall <davidw@u.washington.edu>
To: change-l@u.washington.edu
Cc: Multiple recipients of list <change-l@u.washington.edu>
Subject: Re: new msgs routine
In-Reply-To: <9408152220.AA18712@homer09.u.washington.edu>
Message-Id: <Pine.ULT.3.90.940815154822.16080P-100000@red2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Eliot, 
  Thanks for implementing that.

I've only tested on saul, and I'm not done yet (I'm pretty confused.) But
I don't see how it can be ready for prime time - I can't understand how
this sequence could be possible: 

 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
saul2/wg10/davidw% uwmsgs -h
Message 182:
From: Computing and Communications Information <info@cac.washington.edu>
Date: Mon, 4 Apr 1994 14:25:24
Subject: Chain Letters
(11 lines)  
Message 205:
From: Computing and Communications Information <info@cac.washington.edu>
Date: Fri, 27 May 1994 15:17:49
Subject: Change in Cartridge Tape *TYPE* definitions
(24 lines)  
saul2/wg10/davidw% uwmsgs
saul2/wg10/davidw% uwmsgs -h
saul2/wg10/davidw% uwmsgs -vh
No new unread messages
saul2/wg10/davidw% uwmsgs 
saul2/wg10/davidw% uwmsgs ldskfj
usage: uwmsgs [hqv] [ Number ] [ -Number ]
saul2/wg10/davidw% uwmsgs -qh
There are new messages
saul2/wg10/davidw% uwmsgs
Message 182:
From: Computing and Communications Information <info@cac.washington.edu>
Date: Mon, 4 Apr 1994 14:25:24
Subject: Chain Letters
(11 lines)  More? [ynq] q
--Postponed--
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Did something along there reinitialize the .uwmsgsrc?

It looks like the effect of the "h" option is to mark every (unread) 
message as read.  That doesn't make sense to me.

And if the messages are marked as read, then "uwmsgs -h" gets you no 
output.  But I usually want to use the "h" function to recall a list of 
old messages I've read so that I can refer to one that I've forgotten the 
details of.

I realize that I'm not being clear about how it _should_ work.  
Unfortunately, I'm just finding out by inference how it does work - 
though that isn't much of an excuse.

--David Wall    Computing & Communications...Client Services  3-8491
                Univ. of Washington  HG-45   davidw@u.washington.edu

On Mon, 15 Aug 1994, Eliot Lim wrote:

> Date: Mon, 15 Aug 94 15:22:23 -0700
> From: Eliot Lim <eliot@u.washington.edu>
> To: Multiple recipients of list <change-l@u.washington.edu>
> Subject: Re: new msgs routine
> 
> no problem, the code to do msgs nnn and msgs -nnn (hah! how many of you know
> about this one? :) ) has been added.  the new executables have been installed
> on stein1, saul2 and mead2..  if i don't hear about any new problems, i will
> go ahead and schedule it for galaxy wide installation this wednesday.
> 
> 
> eliot
> 
.