From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Edward Welbourne Newsgroups: gmane.emacs.bugs Subject: Re: customize Date: Tue, 30 Jul 2002 17:44:50 +0200 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: <200207111201.g6BC1OM16938@aztec.santafe.edu> Reply-To: eddy@opera.no NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1028043909 22652 127.0.0.1 (30 Jul 2002 15:45:09 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 30 Jul 2002 15:45:09 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17ZZBE-0005sf-00 for ; Tue, 30 Jul 2002 17:45:00 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17ZZBe-0001WF-00; Tue, 30 Jul 2002 11:45:26 -0400 Original-Received: from pat.opera.com ([193.69.113.22] helo=whorl.intern.opera.no) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17ZZB7-0001V6-00; Tue, 30 Jul 2002 11:44:53 -0400 Original-Received: from eddy by whorl.intern.opera.no with local (Exim 3.35 #1 (Debian)) id 17ZZB4-0002f3-00; Tue, 30 Jul 2002 17:44:50 +0200 Original-To: rms@gnu.org In-Reply-To: <200207111201.g6BC1OM16938@aztec.santafe.edu> (message from Richard Stallman on Thu, 11 Jul 2002 06:01:24 -0600 (MDT)) Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:2996 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:2996 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.