From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/78218 Path: news.gmane.org!not-for-mail From: chad Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: Application resource storage Date: Tue, 29 Mar 2011 13:51:28 -0700 Message-ID: References: <87d3ln9b7y.fsf@stupidchicken.com> <87aagqsh4e.fsf@lifelogs.com> <87y63xem1c.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1301432128 24875 80.91.229.12 (29 Mar 2011 20:55:28 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 29 Mar 2011 20:55:28 +0000 (UTC) Cc: ding@gnus.org, emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 29 22:55:24 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Q4fwb-0002HZ-OS for ged-emacs-devel@m.gmane.org; Tue, 29 Mar 2011 22:55:23 +0200 Original-Received: from localhost ([127.0.0.1]:59835 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q4fwB-00028A-6z for ged-emacs-devel@m.gmane.org; Tue, 29 Mar 2011 16:54:51 -0400 Original-Received: from [140.186.70.92] (port=57479 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q4ft3-00085d-MR for emacs-devel@gnu.org; Tue, 29 Mar 2011 16:51:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q4fsz-0006Gu-3f for emacs-devel@gnu.org; Tue, 29 Mar 2011 16:51:37 -0400 Original-Received: from mail-gx0-f169.google.com ([209.85.161.169]:32805) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q4fsz-0006Gp-1E for emacs-devel@gnu.org; Tue, 29 Mar 2011 16:51:33 -0400 Original-Received: by gxk23 with SMTP id 23so300433gxk.0 for ; Tue, 29 Mar 2011 13:51:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=XRn6XyCX19pcyd6BG+gWaZi0uVWX09WC+49yap7yVzY=; b=mGpKvCrORuBCq/Kcp+0WQ8vFuhJErVqZgK8QyqL6EWhNtsnSsf4q5UJWkUAhtfAqgS yDi5d0flP2Q1aIa/VF3tHWIw42+HW0dBN4womEZ/H7ysJoB1kw4mrh/VScCQTYDoty4l kvxJZWg/czbeuzAqhR/bULsM6MboZm4xsV93A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=p1jhdpeZXWGzdCRLCwnl8rBe6nBlvG04o10SKPFSvSCTcgYTlqeHWBjqGv+xJjsRDa uUAimoO/OyEgBi+amsIgYE8/XA1Gvw7q2QVRkB2MUsQ3VH5w+1CFVd4DoxaGWV41iGti MMBdmGTK0hv9jKM7ARvN8LQn/i6DKTTm/1gkQ= Original-Received: by 10.146.114.26 with SMTP id m26mr306619yac.30.1301431891418; Tue, 29 Mar 2011 13:51:31 -0700 (PDT) Original-Received: from [10.0.0.138] ([12.198.236.170]) by mx.google.com with ESMTPS id d20sm2743339ang.17.2011.03.29.13.51.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Mar 2011 13:51:30 -0700 (PDT) In-Reply-To: <87y63xem1c.fsf@lifelogs.com> X-Mailer: Apple Mail (2.1084) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.161.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:137871 gmane.emacs.gnus.general:78218 Archived-At: An idea: On Tue, 29 Mar 2011 21:34:05 +0200 Lars Magne Ingebrigtsen = wrote:=20 LMI> But if the question is of the kind "do you want to use port 587 = when LMI> connecting to smtp.gmail.com?", then that doesn't really map LMI> straightforwardly to a simple variable. It might map to an alist = of LMI> some kind, but the user may set that alist somewhere else, which=20 LMI> makes all this kind of tricky. I wonder if this isn't the key insight -- for all that I'm not a big = fan, custom does a decent job of trying to do all of the user-input = interactions. The trickiness seems to come in when something is set both = directly and via custom. If the custom machinery were to add a flag or = slot to a variable claiming it as custom-set, then we could at least = warn the user that a custom setting is being overridden, potentially = confirming the change, offering to push the change into custom, etc. If we added such a check to custom and to user-facing variable setters, = then the performance hit should be negligible. In other words, things = like set-variable would check to see if its argument was `customized', = and calling M-x custom would check to see if any of `its' variables had = been changed. Worth the trouble? *Chad=