unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 18005@debbugs.gnu.org
Subject: bug#18005: 24.4.50; In Emacs manual, tell users how to enter debugger for `user-error' errors
Date: Sat, 12 Jul 2014 10:59:57 -0700 (PDT)	[thread overview]
Message-ID: <6261d1cf-2fa0-48a4-a8f0-0727d270c0f2@default> (raw)

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@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''





             reply	other threads:[~2014-07-12 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 17:59 Drew Adams [this message]
2014-07-13  1:35 ` bug#18005: 24.4.50; In Emacs manual, tell users how to enter debugger for `user-error' errors 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

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6261d1cf-2fa0-48a4-a8f0-0727d270c0f2@default \
    --to=drew.adams@oracle.com \
    --cc=18005@debbugs.gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).