From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Inconsistency in meaning of "user options" Date: Tue, 13 Dec 2005 00:33:00 +0100 Message-ID: <439E08AC.5000502@student.lu.se> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1134431054 16985 80.91.229.2 (12 Dec 2005 23:44:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Dec 2005 23:44:14 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 13 00:44:06 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ElxJ7-0001kw-1E for ged-emacs-devel@m.gmane.org; Tue, 13 Dec 2005 00:42:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElxJc-00016R-7z for ged-emacs-devel@m.gmane.org; Mon, 12 Dec 2005 18:42:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ElxAn-0006Rm-Ty for emacs-devel@gnu.org; Mon, 12 Dec 2005 18:33:38 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ElxAm-0006RP-JR for emacs-devel@gnu.org; Mon, 12 Dec 2005 18:33:37 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElxAm-0006RL-8k for emacs-devel@gnu.org; Mon, 12 Dec 2005 18:33:36 -0500 Original-Received: from [81.228.8.83] (helo=pne-smtpout1-sn2.hy.skanova.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ElxCZ-0002AK-MO for emacs-devel@gnu.org; Mon, 12 Dec 2005 18:35:27 -0500 Original-Received: from [192.168.123.121] (83.249.218.244) by pne-smtpout1-sn2.hy.skanova.net (7.2.060.1) id 43995DE9000F0DE3; Tue, 13 Dec 2005 00:33:00 +0100 User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en Original-To: Drew Adams In-Reply-To: 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:47577 Archived-At: Drew Adams wrote: > Sometimes we use the term "user options" to mean > "customizable variable" or "variable meant for the user to set". > But sometimes we use it to mean "any settings you can customize", > which includes faces as well. > > I think we should make this consistent. There is more than > one way to do it; all of them will take work. > The question is, which one is better? > >We discussed this a while back, but I agree that it would be good to come to >a conclusion. Are you proposing that we discuss and decide this _now_, and >make the necessary changes before the 22.1 release? > >If so, here are a few thoughts: > > - "Option" means choice. > > Why do we then have to distinguish between variables and faces? Does not option comprise both? If it does then I think option is a good term to use here. > - If we chose to reserve "user option" for user-settable variables (those >that have `*' as doc-string first char or are defined with defcustom), > > Do I misremember, was not those going to be converted to defcustoms, or? >On another subject, I think it's unfortunate that the terms "customize" and >"customizable" have been appropriated for a particular kind of customization >(using Custom buffers) - especially in an editor (++) that is all about >customization (not Customization). It makes communicating about >customization much more complex and confusing. It would be a lot better if >Customize were called Foobar or Whatever. > > That would maybe be good. Perhaps could we use these terms?: 1) user options 2) custom options (to be distinguished from "Custom options" ;-) I guess the meaning here is obvious, but just in case: 1 - those can not be set with Custom, 2 - those can be set with custom.