At 5:59 PM -0500 1/26/99, Tim Showalter wrote:
I don't think it makes sense (it isn't desirable) for multiple keeps
to be different than a single keep.
Ned's saying it isn't possible. That rules out desirability.
Yes, we are in violent agreement that multiple keep = single keep.
Is there any case where writing a message to a single mailbox twice is
useful?
As you said, if it isn't possible it doesn't matter if it is useful.
> I do agree that the rule needs to be that the default is only
taken when no
> other action of any sort, not just ones on a short list, has been.
So if a script only does a reply, is the message kept or discarded?
Neither is specified, so one has to be the default action.
Reply is not in draft 06, 05, or 04, because in LA, it was decided that
reply was dangerous without some sort of vacation-style protection
(limit number of replies in a single time period).
However, "no other action of any sort" would imply that it is discarded.
OK, let's assume for the sake of argument that "mark" or "reply" or
"foo" is a supported extension. If a script does one of these and
nothing else, is the message kept or discarded? If we say it is
discarded, that means discard is the default delivery state. There
is no such thing as no default delivery state. There has to be one,
because the code must either deliver the message or not.
(I wouldn't mind having a vacation command that also implied a keep, but
that's not what we're talking about here.)
What's wrong with saying that some actions affect delivery status,
and other actions don't?
If you're having these things in a UI, it doesn't matter what we say, we
can (we have to) assume the UI will just get it right.
But for the people designing the UI, and the people implementing scripts
using a text editor, the fewer special cases, the better.
It is much easier to explain this:
"A message that generates no actions gets filed into your INBOX."
than this:
"A mesasge that generates no delivery actions gets filed into your
INBOX. Delivery actions are ones which change the disposition of the
message, and they are reject, forward, and fileinto."
Is it easier to explain? Your simple statement doesn't answer the
question "What happens if a script does 'foo' and nothing else?"
This question does not go away, and it always has an answer. Either
we state the answer, or it is implementation dependent, which I think
is a Bad Thing.