<<< Date Index >>>     <<< Thread Index >>>

Re: Commands should not stop and cause an error



On Fri, Jun 11, 2004 at 08:39:29PM +0200, Jens Paulus wrote:
> well, then it should at least be no error message. I dislike error
> messages if there is no real error. This kind of message then should at
> least no be highlighted in the typical error message way. If there is a
> beep then also no beep should be there but only a simple text message.

The error message is (or may be) helpful for a blind person using a
screen reader.  It is also useful for people who are on a slow link.
Many times an e-mail happens to end close to the bottom of your
mailer's window, but it may not be obvious that it is the end (becuase
it has no signature, or whatever).  Providing no feedback to the user
reading such a message, especially on a slow link, may leave them in
the dark about what's going on -- possibly leaving them thinking that
their link is broken.

I think this behavior is, at least by default, the right one.

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail.  Sorry for the inconvenience.  Thank the spammers.

Attachment: pgptd3xlep5DC.pgp
Description: PGP signature