From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18005@debbugs.gnu.org
Subject: bug#18005: 24.4.50; In Emacs manual, tell users how to enter debugger for `user-error' errors
Date: Fri, 29 Apr 2016 15:53:57 -0700 (PDT) [thread overview]
Message-ID: <a3ee075e-5411-4096-bdf4-7371ad5b71ae@default> (raw)
In-Reply-To: <87twiknkx0.fsf@gnus.org>
> > 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.
prev parent reply other threads:[~2016-04-29 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 17:59 bug#18005: 24.4.50; In Emacs manual, tell users how to enter debugger for `user-error' errors Drew Adams
2014-07-13 1:35 ` Glenn Morris
2014-07-13 2:41 ` Drew Adams
2014-07-13 21:54 ` Richard Stallman
2016-04-29 21:51 ` Lars Ingebrigtsen
2016-04-29 22:53 ` Drew Adams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3ee075e-5411-4096-bdf4-7371ad5b71ae@default \
--to=drew.adams@oracle.com \
--cc=18005@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.