From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Edward Welbourne Newsgroups: gmane.emacs.devel Subject: Re: customize Date: Tue, 30 Jul 2002 10:32:28 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: References: <200207111201.g6BC1OM16938@aztec.santafe.edu> <15680.26449.937153.817907@localhost.localdomain> <200207271853.g6RIrdt10834@aztec.santafe.edu> Reply-To: eddy@opera.no NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1028018037 21938 127.0.0.1 (30 Jul 2002 08:33:57 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 30 Jul 2002 08:33:57 +0000 (UTC) Cc: abraham@dina.kvl.dk, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17ZSS4-0005hj-00 for ; Tue, 30 Jul 2002 10:33:56 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17ZSjh-0007Dq-00 for ; Tue, 30 Jul 2002 10:52:09 +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 17ZSSO-0005Pv-00; Tue, 30 Jul 2002 04:34:16 -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 17ZSRH-0005Ox-00 for ; Tue, 30 Jul 2002 04:33:07 -0400 Original-Received: from eddy by whorl.intern.opera.no with local (Exim 3.35 #1 (Debian)) id 17ZSQe-0000Ky-00; Tue, 30 Jul 2002 10:32:28 +0200 Original-To: Kai.Grossjohann@CS.Uni-Dortmund.DE Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:6170 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:6170 > Customize just adds two statements, custom-set-variable and > custom-set-faces. ah, each of which sets many, like setq can ? Nice. OK, I'd only used customize for one thing at a time thus far, so it'd appeared to have one statement per thing to be set ... mistaken extrapolation on my part here, exacerbated by paranoid reading of the comments in the custom-set-* statements, which appeared to say I shouldn't mess with them at all (which I read as not even moving them). That only leaves the scary behaviour I've had out of customize to date, which I'll report on when next I'm exiting emacs, or re-starting after a crash or re-boot (i.e. when I next don't have lots of state held by live buffers) ... however, the downside of reliable software (e.g. GNU/Linux and emacs in particular) is that this isn't guaranteed to happen several times per day ... indeed, this emacs session is now 20 days old and showing no signs of trouble. Eddy.