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: Adding a few more finder keywords Date: Tue, 9 Jun 2015 07:22:59 -0700 (PDT) Message-ID: <048d389e-cd09-468e-b93f-729505e56ab0@default> References: <87sia2l04r.fsf@gmail.com> <873821xzon.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1433859834 28948 80.91.229.3 (9 Jun 2015 14:23:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 9 Jun 2015 14:23:54 +0000 (UTC) Cc: Oleh Krehel , Artur Malabarba , emacs-devel To: "Stephen J. Turnbull" , Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 09 16:23:42 2015 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 1Z2KRD-0001xj-TW for ged-emacs-devel@m.gmane.org; Tue, 09 Jun 2015 16:23:36 +0200 Original-Received: from localhost ([::1]:35406 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2KRD-0003dj-9J for ged-emacs-devel@m.gmane.org; Tue, 09 Jun 2015 10:23:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36783) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2KQn-0003bY-Vi for emacs-devel@gnu.org; Tue, 09 Jun 2015 10:23:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z2KQj-0002Dj-SR for emacs-devel@gnu.org; Tue, 09 Jun 2015 10:23:09 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:19359) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2KQj-0002DN-Ld for emacs-devel@gnu.org; Tue, 09 Jun 2015 10:23:05 -0400 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 t59EN1gT011390 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 9 Jun 2015 14:23:01 GMT Original-Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id t59EN06f002623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Jun 2015 14:23:01 GMT Original-Received: from abhmp0016.oracle.com (abhmp0016.oracle.com [141.146.116.22]) by aserv0122.oracle.com (8.13.8/8.13.8) with ESMTP id t59EN0v6016547; Tue, 9 Jun 2015 14:23:00 GMT In-Reply-To: <873821xzon.fsf@uwakimon.sk.tsukuba.ac.jp> 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:187124 Archived-At: > > We could decide that the specific keywords are unwanted, tho. >=20 > An "unwanted" keyword doesn't exist though. Somebody wanted it or > it wasn't in Keywords: in the first place. And although every human > is unique, very few humans are so unique that they'll choose a keyword > that nobody else would use to look up packages. >=20 > So I think what you mean by "unwanted" is mostly "redundant (because > a> synonym)". It seems to me that >=20 > 1. There *should* be a list of "recommended keywords" which package > maintainers can easily access for reference... > 2. There *should* be a database of synonyms of recommended keywords > for use by maintainers... > 3. There should be a tool to walk the libraries... > Probably this tool only needs to be run at release time... >=20 > There's no need to be fascist about keyword maintenance... I pretty much agree with all of those points, as being good things to have. But possibilities that work only with a set of "recommended", predefined keywords, e.g. for the package system, should use a different file-header keyword from `Keywords:'. You want something different from what `Keywords:' has always been, something that conflicts with its usage? Fine, just add a new file-header keyword for that. Happiness all around. However, just as we should not co-opt `Keywords:', so we should not co-opt `finder'. Finder works with `Keywords:' in a particular way. It is fine to extend finder so that it does additional things, for particular use cases or in particular environments (e.g., for Emacs maintainers or for the package system), but what it does with `Keywords:' should not be cannibalized for the new features. Again, let it do those things with a new file-header keyword. If some of the things finder will do are the same, then let it do them with both `Keywords:' and the new file-header keyword. IOW, to the extent that some part of the updated finder does not conflict with the normal interpretation/use of `Keywords:', let it be used for both. Should be a no-brainer. `Keywords:' ain't broke; don't "fix" it. Feel free to add new features that do something different and have a different motivation. But don't bother `Keywords:' just to implement what you need. It's not hard for you to leave `Keywords:' alone, for its original, more flexible, use cases.