From: martin rudalics <rudalics@gmx.at>
Cc: rms@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Stephen.Berman@bogus.example.com: Emacs hangs while edebugging recentf.el]
Date: Fri, 16 Dec 2005 08:23:16 +0100 [thread overview]
Message-ID: <43A26B64.6030901@gmx.at> (raw)
In-Reply-To: <87mzj1527v.fsf@stupidchicken.com>
> It works for me, at least using the recipe given in the original
> email. What steps are you using?
>
`edebug-defun' on `widget-field-find' and customizing some arbitrary
editable field. And `edebug-print-level' equalling 50. My (Windows ME)
swap area quickly grew from its usual 70MB to nearly 500MB before I was
able to kill Emacs.
next prev parent reply other threads:[~2005-12-16 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 18:39 [Stephen.Berman@bogus.example.com: Emacs hangs while edebugging recentf.el] martin rudalics
2005-12-16 0:12 ` Chong Yidong
2005-12-16 7:23 ` martin rudalics [this message]
2005-12-16 15:35 ` Chong Yidong
2005-12-17 11:39 ` martin rudalics
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=43A26B64.6030901@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=rms@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).