From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with debug-on-entry in the Lisp debugger.
Date: Wed, 09 Mar 2005 11:58:47 -0500 [thread overview]
Message-ID: <E1D94WF-00066T-F2@fencepost.gnu.org> (raw)
In-Reply-To: <87is42c8yp.fsf@xs4all.nl> (message from Lute Kamstra on Tue, 08 Mar 2005 19:02:06 +0100)
Below is a quick "proof-of-concept" patch for src/eval.c and
lisp/emacs-lisp/debug.el to get a better idea of what I mean. As you
can see, the change to eval.c isn't that big.
The code is not unclean, but I don't think it is a real problem
that the debug-on-entry code is visible. So I'd rather not
go in this direction.
This is not the part of Emacs that is important to improve.
Hackers tend to focus their attention on the parts of Emacs
that make it seem more elegant in programmers' terms,
but this doesn't make Emacs more powerful or a better editor.
Could you possibly look at implementing something listed in etc/TODO?
next prev parent reply other threads:[~2005-03-09 16:58 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
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 [this message]
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=E1D94WF-00066T-F2@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).