From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: add keyword search and display in details for list-packages Date: Thu, 21 Nov 2013 09:44:39 -0500 Message-ID: References: <87wql1w6io.fsf@flea.lifelogs.com> <87r4axu4dm.fsf@flea.lifelogs.com> <87k3gorvs4.fsf@flea.lifelogs.com> <87eh6adbqr.fsf@flea.lifelogs.com> <87a9gyc8pp.fsf_-_@flea.lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1385045094 2639 80.91.229.3 (21 Nov 2013 14:44:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Nov 2013 14:44:54 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 21 15:44:59 2013 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 1VjVV4-00018x-Ul for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2013 15:44:59 +0100 Original-Received: from localhost ([::1]:33610 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjVV4-0004FO-JL for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2013 09:44:58 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33736) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjVUv-0004Er-0U for emacs-devel@gnu.org; Thu, 21 Nov 2013 09:44:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VjVUn-0001pG-NC for emacs-devel@gnu.org; Thu, 21 Nov 2013 09:44:48 -0500 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:47987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjVUn-0001oz-Gh for emacs-devel@gnu.org; Thu, 21 Nov 2013 09:44:41 -0500 Original-Received: from faina.iro.umontreal.ca (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id rALEidJe014217; Thu, 21 Nov 2013 09:44:39 -0500 Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id 606ADB5162; Thu, 21 Nov 2013 09:44:39 -0500 (EST) In-Reply-To: <87a9gyc8pp.fsf_-_@flea.lifelogs.com> (Ted Zlatanov's message of "Thu, 21 Nov 2013 06:09:22 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV4768=0 X-NAI-Spam-Version: 2.3.0.9362 : core <4768> : inlines <246> : streams <1077677> : uri <1601837> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 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:165482 Archived-At: >>> I think the Keywords should also be shown in the package description and >>> maybe available for filtering, WDYT? XF> I agree. Showing the dependencies would be useful, too. Adding dependencies in the package description sounds good, indeed. > OK. Any objections to: > * adding filtering by Keywords in the packages list? OK. > * showing the Keywords in the packages list? Not sure how you plan to do that. > * showing the Keywords in the package description? OK. > ;; - should store the package's keywords in archive-contents, then > ;; let the users filter the package-menu by keyword. See > ;; finder-by-keyword. > so it seems this will require backend work by the GNU ELPA tools to put > the Keywords in the package description. Stefan, WDYT? If you want to filter by keywords, I see 3 options: - add keywords in archive-contents. - let package.el download all packages to extract keywords from them. - use a separate file alongside archive-contents. Option 2 is only included for completeness since it makes little sense. Option 1 probably makes most sense. Option 3 could make sense if filtering by keyword is rare and if the size of the keywords data is significantly larger than the size of archive-contents. IOW, option 1 sounds best. > Finally, in addition to the Keywords, is there a package category, > meaning a single word to describe its purpose? No, and I don't think we'll ever be able to categorize this way. > It might be more suitable for display in the packages list and could > let us set up a hierarchy in the packages list to avoid the current > "2500+ entries in a flat list" situation. We could just as well browse by keywords. Stefan