From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Problems with debug-on-entry in the Lisp debugger.
Date: Wed, 09 Mar 2005 18:30:05 +0100 [thread overview]
Message-ID: <87acpc7mn6.fsf@xs4all.nl> (raw)
In-Reply-To: <E1D94WK-000677-TB@fencepost.gnu.org> (Richard Stallman's message of "Wed, 09 Mar 2005 11:58:52 -0500")
Richard Stallman <rms@gnu.org> writes:
> > does it have any real impact?
>
> It can be confusing for new users of the debugger: Hey, what's
> that doing in my function? Did I put that there?
>
> The user probably rembemers having set "debug on entry" for the
> function, and has just been reminded by entering the debugger, so
> that ought to help him understand.
True.
> > If the aesthetic aspect is just more serious now that we
> > replace (debug 'debug) with (if (or inhibit-debug-on-entry
> > debugger-jumping-flag) nil (debug 'debug)), we can define a
> > function named e.g. `debug-entering' that will do the checking
> > of inhibit-debug-on-entry and debugger-jumping-flag.
>
> That would be somewhat better.
>
> Using the name implement-debug-on-entry will help the user figure
> out why it is there.
Ok, I'll implement this.
Lute.
next prev parent reply other threads:[~2005-03-09 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 11:05 Problems with debug-on-entry in the Lisp debugger Lute Kamstra
2005-03-07 13:31 ` Stefan Monnier
2005-03-07 15:20 ` Lute Kamstra
2005-03-07 16:32 ` Stefan Monnier
2005-03-08 18:57 ` Lute Kamstra
2005-03-09 16:58 ` Richard Stallman
2005-03-09 17:30 ` Lute Kamstra [this message]
2005-03-07 13:40 ` Kim F. Storm
2005-03-07 14:20 ` drkm
2005-03-07 14:45 ` Kim F. Storm
2005-03-08 2:53 ` Richard Stallman
2005-03-08 18:02 ` Lute Kamstra
2005-03-08 18:59 ` Stefan Monnier
2005-03-09 10:14 ` Lute Kamstra
2005-03-09 16:58 ` Richard Stallman
2005-03-09 16:58 ` Richard Stallman
2005-03-09 17:38 ` Lute Kamstra
2005-03-10 0:26 ` Kevin Rodgers
2005-03-11 1:47 ` Richard Stallman
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=87acpc7mn6.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).