From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: A proposal for removing obsolete packages Date: Sat, 23 Jan 2016 17:56:00 -0800 (PST) Message-ID: <0b303f17-ace7-45f8-b5d3-828ff0ed0ab9@default> References: <83twmkkv16.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1453600595 8021 80.91.229.3 (24 Jan 2016 01:56:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 24 Jan 2016 01:56:35 +0000 (UTC) Cc: johnw@gnu.org, emacs-devel@gnu.org, Richard Stallman , monnier@iro.umontreal.ca To: Andrew Hyatt Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 24 02:56:22 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aN9ug-00066B-5v for ged-emacs-devel@m.gmane.org; Sun, 24 Jan 2016 02:56:22 +0100 Original-Received: from localhost ([::1]:58997 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aN9uf-0008Ox-57 for ged-emacs-devel@m.gmane.org; Sat, 23 Jan 2016 20:56:21 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33600) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aN9uX-0008Lj-Q2 for emacs-devel@gnu.org; Sat, 23 Jan 2016 20:56:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aN9uS-0006wo-QF for emacs-devel@gnu.org; Sat, 23 Jan 2016 20:56:13 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:45004) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aN9uS-0006wc-IH; Sat, 23 Jan 2016 20:56:08 -0500 Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u0O1u0Vn024265 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 24 Jan 2016 01:56:01 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u0O1u01f000536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 24 Jan 2016 01:56:00 GMT Original-Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by userv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u0O1txeD018105; Sun, 24 Jan 2016 01:55:59 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: aserv0021.oracle.com [141.146.126.233] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:198676 Archived-At: > > Really? Just how do you "use Customize" to get a listing such as > > `list-options' provides? How do you use `M-x customize' to get > > such a listing? > > > > I don't think you can get such a listing. Certainly not with just > > `M-x customize'. And `customize-apropos .*' doesn't give you the > > same thing (no complete doc strings, and not just options, etc.). Both of those messages are incorrect in what they tell users now. > > If I'm right that there is no real substitute provided by Customize > > then I think that command `list-options' (renamed, if necessary) > > should be kept. It could be moved to one of the `cus*.el' files, > > if you really plan to toss `options.el'. >=20 > I hadn't used options before, but I tried now. I guess I don't see > the usefulness of the command. It gives you a readable, searchable buffer of all of the options, together with their values and complete doc strings. To me, that can be useful. And I don't see that Customize provides any replacement for it - nothing at all similar, AFAICT. > What I thought you were described above > seems useful indeed - a list of everything customized (for those who > don't want to fiddle with elisp). A list of everything that you have customized but not saved is a different topic. It is not what `list-options' is for. But FWIW, the command you describe already exists: `customize-customized' (though it returns info also about faces). And command `customize-saved', if by "customized" you meant customized and saved. > But list-options instead gives much, > much more than that in a buffer 38k lines long. Yes. It is not about options that you have customized - that's a different topic. And it's not just about listing all of the options with one-line descriptions. It's about what `list-options' does: lists all options together with their current values and complete doc strings. > What is the use of this, and why is it more useful than, say, > customize-browse? See above for the usefulness. There is no reason to compare it with `customize-browse' - that's irrelevant, unless you are claiming that it provides the same functionality and so is a replacement. Just because `customize-browse' can be useful is no reason that `list-options' cannot also be useful. Similarly for `customize-apropos-options', which is more like what `list-options' does (with a regexp of `.*'). And you cannot search across all (complete) doc strings with `customize-apropos-options' - you need to open each entry individually, to see its full doc string. (Isearch could perhaps be modified to automatically open `customize-apropos*' entries that have search hits, instead of ignoring text in closed entries. But that's not the case today.) Anyway, you need not find the command useful for it to be useful to others. (There are people who do not find `customize-browse' to be particularly useful...) Try `apropos-documentation', which is not about options, but which is another buffer that shows you complete doc strings, across which you can search etc. Useful, no? An improvement to `list-options' could be to have it list only matches for some apropos input. But even now by listing all options it can be useful. If the `customize-apropos*' commands were improved to show what `list-options' shows (searchable full doc strings and current values) then `customize-apropos-options' might provide a replacement for `list-options'. But that's not yet the case.