Article View: comp.mail.mush
Article #612Re: Priorities in 7.2.0
From: Mark Sirota
Date: Wed, 05 Dec 1990 17:30
Date: Wed, 05 Dec 1990 17:30
41 lines
2738 bytes
2738 bytes
In article <3672@exodus.Eng.Sun.COM> argv@turnpike.Eng.Sun.COM (Dan Heller) writes:
>> However, there are two problems with this. First, messages without a
>> priority wind up last, rather than first, as they probably should. So I
>
> This is basically where I disagree.. I think higher priority messages
> should be listed first. Given that you want it the other way around,
> I see your problem and your idea about reversing the priorities and the
> sort seems to be the only way around it (and is also a reasonable idea).
Ahh, I think here we have the core of the problem. In thinking about it, I
agree, higher priority messages should be listed first. But the
inconsistency here is that with the default sorting order, new messages are
first - but then if one comes in while you're working, it gets stuck last.
Now, this is how it has always worked since the dawn of time; the mailbox is
a flat file and new things are appended to the end of it, and that's why my
first thought was that the sorting order was backwards. I think your way
makes more sense, actually, and I'd like to do it that way - except that new
messages, which I receive frequently, should be added in at the bottom of
the new message section (which should be sorted by priority, and
within that, chronologically by date).
In other words, I guess what I'm asking for is a way to filter a message
through a command when it first comes in, or a command to run whenever a new
message comes in (which in this case would be my script to set priority and
resort). I think that would solve all my problems.
> Of course, the option to do subsorting is really where this comes in most
> handy. That is, sort by author and then by status so I can group all the
> messages from someone together and group those that I haven't replied to
> separately.
Subsorting is indeed a truly wonderful thing. I wonder how I ever lived
without it.
Mark
--
Mark Sirota - Department of Electrical Engineering
University of Rochester, Rochester NY
Internet: msirota@ee.rochester.edu
UUCP: {decvax,garp,harvard,hombre,rutgers}!rochester!ur-valhalla!msirota
Technical Details
Message-ID:
<1990Dec5.173018.3282@ee.rochester.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!wuarchive!udel!rochester!uhura.cc.rochester.edu!ee.rochester.edu!msirotaReferences:
<1990Nov27.215502.25496@ee.rochester.edu> <3672@exodus.Eng.Sun.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!wuarchive!udel!rochester!uhura.cc.rochester.edu!ee.rochester.edu!msirota From: msirota@ee.rochester.edu (Mark Sirota) Newsgroups: comp.mail.mush Subject: Re: Priorities in 7.2.0 Message-ID: <1990Dec5.173018.3282@ee.rochester.edu> Date: 5 Dec 90 17:30:18 GMT References: <1990Nov27.215502.25496@ee.rochester.edu> <3672@exodus.Eng.Sun.COM> Reply-To: Mark Sirota <msirota@mars.ee.rochester.edu> Organization: University of Rochester Department of Electrical Engineering Lines: 41