From: Edward Welbourne <eddy@opera.no>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: customize
Date: Tue, 30 Jul 2002 17:44:50 +0200 [thread overview]
Message-ID: <E17ZZB4-0002f3-00@whorl.intern.opera.no> (raw)
In-Reply-To: <200207111201.g6BC1OM16938@aztec.santafe.edu> (message from Richard Stallman on Thu, 11 Jul 2002 06:01:24 -0600 (MDT))
Finally, emacs died on me (it must have overheard remarks about how
robust it is) so I was forced to start a new session, so set about
reproducing my original problem with customize, namely exceeding
max-lisp-eval-depth whenever I tried opening a file after using
customize. However, in a nice clean fresh session, the problem didn't
manifest itself: customize worked fine.
> Can you tell us precisely how to reproduce this?
evidently not. It's only ever happened in sessions many days old.
Eris alone knows what complications of session history may be involved.
> With that information, we could fix the problem.
aye, and without it's in no danger of being caught.
Bugs that know when to hide have better survival chances.
If it happens again, I'll try the toggle-debug-on-error and similar
tricks that you suggested, see if I can glean any further information.
At least in the ensuing discussion I've met plenty of useful pointers
on the care and feeding of customize :-)
Eddy.
prev parent reply other threads:[~2002-07-30 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 16:51 customize Edward Welbourne
2002-07-11 12:01 ` customize Richard Stallman
2002-07-11 16:29 ` customize Edward Welbourne
2002-07-25 21:02 ` customize Jeff Dwork
2002-07-30 15:44 ` Edward Welbourne [this message]
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=E17ZZB4-0002f3-00@whorl.intern.opera.no \
--to=eddy@opera.no \
--cc=bug-gnu-emacs@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).