From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: Customize buttons that change user's custom fileshouldaskforconfirmation Date: Sat, 19 Feb 2005 20:31:44 -0600 (CST) Message-ID: <200502200231.j1K2ViZ29840@raven.dms.auburn.edu> References: <00e301c509c1$9c761690$0200a8c0@sedrcw11488> <200502152320.j1FNKd310641@raven.dms.auburn.edu> <200502172257.j1HMvJN10856@raven.dms.auburn.edu> <200502181412.j1IECkj14736@raven.dms.auburn.edu> <200502182259.j1IMx6g23511@raven.dms.auburn.edu> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1108867381 8127 80.91.229.2 (20 Feb 2005 02:43:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 20 Feb 2005 02:43:01 +0000 (UTC) Cc: lennart.borgman.073@student.lu.se, rms@gnu.org, drew.adams@oracle.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Feb 20 03:43:00 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D2h3Z-0008N8-7R for ged-emacs-devel@m.gmane.org; Sun, 20 Feb 2005 03:42:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D2hH4-00075p-AH for ged-emacs-devel@m.gmane.org; Sat, 19 Feb 2005 21:56:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D2hGj-00071x-Er for emacs-devel@gnu.org; Sat, 19 Feb 2005 21:56:25 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D2hGT-0006tr-ND for emacs-devel@gnu.org; Sat, 19 Feb 2005 21:56:14 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D2hGT-0006rt-A6 for emacs-devel@gnu.org; Sat, 19 Feb 2005 21:56:09 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D2gus-00076g-27; Sat, 19 Feb 2005 21:33:50 -0500 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id j1K2Xg9N007997; Sat, 19 Feb 2005 20:33:42 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id j1K2ViZ29840; Sat, 19 Feb 2005 20:31:44 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: storm@cua.dk In-reply-to: (storm@cua.dk) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33642 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33642 Kim Storm wrote: I think I have understood your idea of "typical usage pattern", I do not believe so. I use Custom extensively as a _browser_ and _documentation tool_, but when I see an option I want to change and save, I do so. In my use of Custom as a browser and source of info, I often click on "Value Menus". I do not necessarily reclose them because I still may want to look at them later and there is no need to close them anyway. Right now, I can browse in a relaxed fashion without being careful. I do not even need to worry about accidental edits or anything. If I want to save an option all I have to do is check that one value and TAB RET. After your change, whenever I want to change something, I will have to worry about whatever else is in the buffer. Actually, I will not, because it would really be too cumbersome. Unless there is an expert option and it actually works, I would either use .emacs or put point on the option and do `M-x customize-option RET', thereby avoiding the trouble. As long as you don't use "Save", it's perfectly safe! That is _exactly_ why I would never use the all buffer save. Very few are familiar with a concept that forces you to save each change individually. So you really _do_ believe that this is a terribly difficult concept. Sincerely, Luc.