[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why should interactive search results raise errors?
From: |
Richard Stallman |
Subject: |
Re: Why should interactive search results raise errors? |
Date: |
Thu, 04 May 2006 10:17:11 -0400 |
I still believe that interactive search commands should not raise
errors. However I think adding these commands now to
debug-ingnored-errors is the better solution now. Could we please do
that now?
I see no reason to change this. Lots of commands signal errors when
they can't do what they are asked to do; why shouldn't these?
I think the better answer is to create a new error class called `user-error'
which would be then added to debug-ignored-errors. Then we can replace most
elements of debug-ignored-errors by changing the signalling code so as to
signal a `user-error' rather than an `error'.
That is not necessarily a bad idea, but I am not sure whether it is
really possible to distinguish "user errors" from other errors at the
level of calls to `signal'.
`debug-ignored-errors' does make an attempt to distinguish which
errors are _probably_ user errors, but it cannot really know,
and sometimes this criterion gets the wrong answer.
Re: Why should interactive search results raise errors?, Stefan Monnier, 2006/05/03
Re: Why should interactive search results raise errors?, Kim F. Storm, 2006/05/04