From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: Improving browsing and discoverability in the Packages Menu Date: Mon, 20 Apr 2015 16:38:30 +0800 Message-ID: <87twwbdwjd.fsf@ericabrahamsen.net> References: <871tjgj010.fsf@ericabrahamsen.net> <7b3b0d19-01d4-4f97-b85e-19383bee5605@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1429519156 32011 80.91.229.3 (20 Apr 2015 08:39:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Apr 2015 08:39:16 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 20 10:39:08 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 1Yk7EM-0004aK-LM for ged-emacs-devel@m.gmane.org; Mon, 20 Apr 2015 10:39:02 +0200 Original-Received: from localhost ([::1]:52321 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yk7EL-0004YJ-Se for ged-emacs-devel@m.gmane.org; Mon, 20 Apr 2015 04:39:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38054) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yk7EA-0004Y9-V3 for emacs-devel@gnu.org; Mon, 20 Apr 2015 04:38:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yk7E7-0002DQ-PA for emacs-devel@gnu.org; Mon, 20 Apr 2015 04:38:50 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:60083) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yk7E7-0002DG-IJ for emacs-devel@gnu.org; Mon, 20 Apr 2015 04:38:47 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Yk7E5-0004OJ-41 for emacs-devel@gnu.org; Mon, 20 Apr 2015 10:38:45 +0200 Original-Received: from 222.129.224.131 ([222.129.224.131]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Apr 2015 10:38:45 +0200 Original-Received: from eric by 222.129.224.131 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Apr 2015 10:38:45 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 49 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 222.129.224.131 User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:iiX0Ksfba5AA3jBj+7srniY/s3A= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:185691 Archived-At: Drew Adams writes: >> This would be nice to fix. `finder-known-keywords' looks like the >> place to start. Package filtering is only indirectly connected to the >> value of that variable, though. >> >> Filtering is done on keywords actually found in the packages. If >> package authors used `auto-insert' when creating their packages, >> they would be prompted to add keywords from `finder-known-keywords'. >> That leaves a lot of wiggle room for the insertion of random keywords. > > I'm not sure what you meant by the last part, so this comment might > be unrelated to your post. But I would like to remind us all that > `finder' functionality is not limited to the keywords found in > `finder-known-keywords'. > > Users can use any keywords they like in their library headers. > I would not like to see `finder.el' gravitate toward imposing some > particular set of keywords or expecting only some particular set. > >> In order to make filtering useful, it seems like it would be >> worthwhile fleshing out the taxonomy of `finder-known-keywords', >> and enforcing it -- ie, keywords not in that variable would be >> ignored by package filtering. > > I'm not sure I would object to something like that being done only > "by package filtering". But I would object to changing the point > of `finder.el' so that it generally becomes more rigid in that way. > > Even for only "package filtering", I have the question of why. > Why should package filtering be limited to some predefined list > of keywords? Just why should "keywords not in that variable... > be ignored by package filtering"? You're right, "enforcing" anything is probably a bad idea. But looking at the lists presented to you when filtering packages (or when doing an auto-insert in a new elisp file), it looks a lot like tag-rot: a whole lot of random overlapping categories and mis-matched types. I guess I agree that package authors should be able to put anything they want in the Keyword header. On the other hand, I want to be able to search for packages related to sending email messages from Emacs (for instance), and know that I'm not missing packages because their author tagged them as "email" instead of "mail". That sort of thing just makes the whole process feel broken. Maybe just expand the canonical list of curated keywords, then let package authors add their own on top of that? Eric