[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tue, 30 Jul 2002 17:44:50 +0200
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 :-)