From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
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: Sun, 13 Jul 2014 17:54:24 -0400 [thread overview]
Message-ID: <E1X6Riy-0004mT-2h@fencepost.gnu.org> (raw)
In-Reply-To: <d383746c-d757-4e6b-9c24-5e6b97b7ebf0@default> (message from Drew Adams on Sat, 12 Jul 2014 19:41:13 -0700 (PDT))
[[[ 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.
next prev parent reply other threads:[~2014-07-13 21:54 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 [this message]
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=E1X6Riy-0004mT-2h@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=18005@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).