GNU bug report logs -
#18005
24.4.50; In Emacs manual, tell users how to enter debugger for `user-error' errors
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Sat, 12 Jul 2014 18:01:02 UTC
Severity: wishlist
Tags: wontfix
Found in version 24.4.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18005 in the body.
You can then email your comments to 18005 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18005
; Package
emacs
.
(Sat, 12 Jul 2014 18:01:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 12 Jul 2014 18:01:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
The only hint about how to make Emacs enter the debugger for errors
deemed `user-error' is this mention, buried in the
`debug-ignored-errors' entry of the Elisp manual:
The normal value of this variable includes `user-error', as well
as several errors that happen often during editing but rarely
result from bugs in Lisp programs. However, "rarely" is not
"never"; if your program fails with an error that matches this
list, you may try changing this list to debug the error. The
easiest way is usually to set `debug-ignored-errors' to `nil'.
(FWIW, wrt this text: Is it really necessary to point out that
users can want to enter the debugger for other reasons that
tracking down a Lisp bug?)
It should be made *obvious* to users, in the *Emacs* manual, how to make
the debugger open for so-called "user errors".
In particular, some mention of how to do this should be added to any
descriptions of `debug-on-error' and `toggle-debug-on-error'. Yes,
*especially* since these have NO effect on this. Users will try these
and not understand how to get what they want in this regard. Here
is one proof: http://superuser.com/q/782313/250462.
(Hard to believe that something presumably designed with end users in
mind would not be documented wrt how to access the debugger. Of
course, `user-error' has NOTHING to do with user errors anyway...)
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-06-28 on ODIEONE
Bzr revision: 117431 rgm <at> gnu.org-20140628015517-eku6hj8mpgcvfnso
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/snapshot/trunk
--enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
-Ic:/Devel/emacs/include''
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18005
; Package
emacs
.
(Sun, 13 Jul 2014 01:36:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 18005 <at> debbugs.gnu.org (full text, mbox):
The whole point of introducing user-error was so that uninteresting
errors will not trigger the debugger. I see no need to mention in the
*Emacs* manual how to get round this.
(I am not going to get into a big debate about this.)
Added tag(s) wontfix.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 13 Jul 2014 01:37:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18005
; Package
emacs
.
(Sun, 13 Jul 2014 02:42:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 18005 <at> debbugs.gnu.org (full text, mbox):
> The whole point of introducing user-error was so that uninteresting
> errors will not trigger the debugger. I see no need to mention in the
> *Emacs* manual how to get round this.
"The whole point" should be to _let_ users not be bothered entering
the debugger for uninteresting errors. That's reasonable behavior.
*Enabling* that behavior is positive. Forcing it would be
counterproductive, as is not making clear what it is that controls it.
Not to mention the fact that what constitutes an "uninteresting
error" is not something fixed once and for all for everyone. It
can change, depending on the context. A user might well want to
take a look under the covers using the debugger in some context.
(The user who just now asked how to do it, for instance.)
> (I am not going to get into a big debate about this.)
No one asked you to.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18005
; Package
emacs
.
(Sun, 13 Jul 2014 21:55:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 18005 <at> debbugs.gnu.org (full text, mbox):
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
"The whole point" should be to _let_ users not be bothered entering
the debugger for uninteresting errors. That's reasonable behavior.
*Enabling* that behavior is positive. Forcing it would be
counterproductive, as is not making clear what it is that controls it.
I agree.
Not to mention the fact that what constitutes an "uninteresting
error" is not something fixed once and for all for everyone. It
can change, depending on the context. A user might well want to
take a look under the covers using the debugger in some context.
(The user who just now asked how to do it, for instance.)
I have several times wanted to enter the debugger because a
program triggered one of these errors which usually is caused by
bad user input. So I used the feature to enable that.
There should continue to be a convenient feature to enable that.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18005
; Package
emacs
.
(Fri, 29 Apr 2016 21:52:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 18005 <at> debbugs.gnu.org (full text, mbox):
Drew Adams <drew.adams <at> oracle.com> writes:
> The only hint about how to make Emacs enter the debugger for errors
> deemed `user-error' is this mention, buried in the
> `debug-ignored-errors' entry of the Elisp manual:
>
> The normal value of this variable includes `user-error', as well
> as several errors that happen often during editing but rarely
> result from bugs in Lisp programs. However, "rarely" is not
> "never"; if your program fails with an error that matches this
> list, you may try changing this list to debug the error. The
> easiest way is usually to set `debug-ignored-errors' to `nil'.
>
> (FWIW, wrt this text: Is it really necessary to point out that
> users can want to enter the debugger for other reasons that
> tracking down a Lisp bug?)
>
> It should be made *obvious* to users, in the *Emacs* manual, how to make
> the debugger open for so-called "user errors".
I think this belongs in the elisp manual, and the explanation there is
fine.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug closed, send any further explanations to
18005 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 29 Apr 2016 21:52:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18005
; Package
emacs
.
(Fri, 29 Apr 2016 22:55:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 18005 <at> debbugs.gnu.org (full text, mbox):
> > The only hint about how to make Emacs enter the debugger for errors
> > deemed `user-error' is this mention, buried in the
> > `debug-ignored-errors' entry of the Elisp manual:
> >
> > The normal value of this variable includes `user-error', as well
> > as several errors that happen often during editing but rarely
> > result from bugs in Lisp programs. However, "rarely" is not
> > "never"; if your program fails with an error that matches this
> > list, you may try changing this list to debug the error. The
> > easiest way is usually to set `debug-ignored-errors' to `nil'.
> >
> > (FWIW, wrt this text: Is it really necessary to point out that
> > users can want to enter the debugger for other reasons that
> > tracking down a Lisp bug?)
> >
> > It should be made *obvious* to users, in the *Emacs* manual, how to make
> > the debugger open for so-called "user errors".
>
> I think this belongs in the elisp manual, and the explanation there is
> fine.
I disagree (like RMS). How to enter the debugger, including for
"user" errors, is not information we should bury. It should be
mentioned in the Emacs manual, with a link to the Elisp manual
for more info.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 28 May 2016 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 9 years and 81 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.