From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: menu-bar-options-save and menu-bar-options-menu Date: Tue, 18 Jan 2005 12:02:40 -0800 Message-ID: References: <01c4fd94$Blat.v2.2.2$0cb21100@zahav.net.il> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1106079068 4115 80.91.229.6 (18 Jan 2005 20:11:08 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 18 Jan 2005 20:11:08 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 18 21:10:43 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CqzgY-0006wM-00 for ; Tue, 18 Jan 2005 21:10:42 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CqzsT-00035O-9f for ged-emacs-devel@m.gmane.org; Tue, 18 Jan 2005 15:23:01 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cqzr8-0002jh-5I for emacs-devel@gnu.org; Tue, 18 Jan 2005 15:21:38 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cqzr1-0002iB-MG for emacs-devel@gnu.org; Tue, 18 Jan 2005 15:21:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cqzr0-0002f8-Gw for emacs-devel@gnu.org; Tue, 18 Jan 2005 15:21:30 -0500 Original-Received: from [148.87.2.204] (helo=inet-mail4.oracle.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CqzYz-00033Z-VM; Tue, 18 Jan 2005 15:02:54 -0500 Original-Received: from inet-mail4.oracle.com (localhost [127.0.0.1]) by inet-mail4.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j0IK2ovT001080; Tue, 18 Jan 2005 12:02:50 -0800 (PST) Original-Received: from rgmsgw301.us.oracle.com (rgmsgw301.us.oracle.com [138.1.191.50]) by inet-mail4.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j0IK2lE5001043; Tue, 18 Jan 2005 12:02:48 -0800 (PST) Original-Received: from rgmsgw301.us.oracle.com (localhost [127.0.0.1]) by rgmsgw301.us.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j0IK2lxc026481; Tue, 18 Jan 2005 13:02:47 -0700 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-82-223.vpn.oracle.com [141.144.82.223]) by rgmsgw301.us.oracle.com (Switch-3.1.4/Switch-3.1.0) with SMTP id j0IK2kEu026435 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 18 Jan 2005 13:02:47 -0700 Original-To: "Eli Zaretskii" , X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <01c4fd94$Blat.v2.2.2$0cb21100@zahav.net.il> 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: main.gmane.org gmane.emacs.devel:32348 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:32348 > I expect that modifying the Options menu will be one thing > that customizing users will want to do - especially adding > options that are toggles. What options would you like to add? Tootsi Frootsi :-) Seriously, none. My point is not about the current content of the menu. My point is that we should look at the Options menu as something that will likely be customized (augmented). Users (or libraries) that create new options (e.g. toggles) might want to add them to the Options menu. That's all. This commonly happens when you add a plugin to many applications: the Preferences that a user can choose are updated to include options from the plugin. As for flexibility, I think the idea is that Customize is the flexible machinery you are looking for. That may be the idea, but I don't see how that idea or the flexible machinery helps here. I was just pointing out that there is an implicit coupling between the Options menu and the options treated by `menu-bar-options-save': the latter depends on the former, but this dependency is not handled automatically. If a user (or a library) changes the Options menu, it is likely that he will want/need to change the save command also. It would be convenient (and more modular and less error-prone) if the update to one automatically updated the other too. I mentioned some possible mechanisms; there are no doubt others (and better).