all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: bug#981: 23.0.60; doc of debug-on-error
Date: Sun, 14 Sep 2008 14:59:11 -0700	[thread overview]
Message-ID: <006001c916b5$1eec3ce0$0200a8c0@us.oracle.com> (raw)

`debug-on-error' does not control what happens during Lisp rexpression
evaluation. But you cannot know this by looking at only the doc of
`debug-on-error'.  For example, evaluate this using either `C-x C-e'
in buffer *scratch or via `M-:':
(unwind-protect jjjjjjj (message "XXXX"))
 
`eval-expression-debug-on-error' is what controls this behavior. In
the Elisp manual, the doc for `debug-on-error' is on the same page as
the doc for `eval-expression-debug-on-error', but even so, a reader
might read only the `debug-on-error' part if that's what s?he is
looking up.
 
The `debug-on-error' description in the manual needs a "see below"
mention of `eval-expression-debug-on-error' and of the fact that
`debug-on-error' alone does not control what happens during such sexp
evaluation.
 
The `debug-on-error' doc string, likewise, needs to mention this and
cross-reference the doc string for `eval-expression-debug-on-error'.
 
I think what happened was that when `eval-expression-debug-on-error'
was introduced in Emacs 21 this doc dependency was overlooked - the
doc for `eval-expression-debug-on-error' was added but the doc for
`debug-on-error' was not updated accordingly. In Emacs 20,
`debug-on-error' is all there is, so its doc is complete and
sufficient.
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-09-03 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
 







             reply	other threads:[~2008-09-14 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <usabb2hwsw.fsf@fencepost.gnu.org>
2008-09-14 21:59 ` Drew Adams [this message]
2008-12-12  4:05   ` bug#981: marked as done (23.0.60; doc of debug-on-error) Emacs bug Tracking System

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='006001c916b5$1eec3ce0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=981@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@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 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.