From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Oleh Krehel Newsgroups: gmane.emacs.devel Subject: Re: Adding a few more finder keywords Date: Tue, 09 Jun 2015 08:52:57 +0200 Message-ID: <87zj49jrue.fsf@gmail.com> 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 X-Trace: ger.gmane.org 1433833196 6817 80.91.229.3 (9 Jun 2015 06:59:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 9 Jun 2015 06:59:56 +0000 (UTC) Cc: Stefan Monnier , Artur Malabarba , emacs-devel To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 09 08:59:51 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 1Z2DVm-0003lz-2t for ged-emacs-devel@m.gmane.org; Tue, 09 Jun 2015 08:59:50 +0200 Original-Received: from localhost ([::1]:33341 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2DVl-0003U8-Fw for ged-emacs-devel@m.gmane.org; Tue, 09 Jun 2015 02:59:49 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54557) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2DVi-0003U2-6F for emacs-devel@gnu.org; Tue, 09 Jun 2015 02:59:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z2DVe-0005GP-Ta for emacs-devel@gnu.org; Tue, 09 Jun 2015 02:59:46 -0400 Original-Received: from mail-wi0-x22e.google.com ([2a00:1450:400c:c05::22e]:36622) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2DVe-0005Fx-MS for emacs-devel@gnu.org; Tue, 09 Jun 2015 02:59:42 -0400 Original-Received: by wigg3 with SMTP id g3so6374287wig.1 for ; Mon, 08 Jun 2015 23:59:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=IfIoagi0sMZqyAKOWTBqXVk6+uqKh8EteMPzMXyv8O4=; b=kmtrbBNZm4yJOIYVcuoXldOUaqXPwQMuhIrdqGoyYtPIUSXpzETxIgeD24UV6dPxjT +OxqQjd7kiHawzVv9skofJ4xXzscrsaFQC1XhqFtEjM1aORFY8hugz39NkIcqRdNBHx6 QiZEmhqFrbIjPMYzdaheU4ZYkCYMyOWZ+Fjepy+2o2fwj0wh2F9HMGioQWcmnU6RIku7 Li9ka3UsHQC92qb36QEhSDgCgnA0y/kdSFRBEiPOpWr5j2ZXvZdPGCWpQc0r01dFmz0p NEHQGW1fqhBrPWaCrM42PL9nnuPWamFCh9FtFggz+bAAm2NrbLOMyRSEK22FTAMWdCf0 KLtw== X-Received: by 10.180.96.232 with SMTP id dv8mr5352358wib.22.1433833181303; Mon, 08 Jun 2015 23:59:41 -0700 (PDT) Original-Received: from firefly (dyn069045.nbw.tue.nl. [131.155.69.45]) by mx.google.com with ESMTPSA id vz2sm7813669wjc.18.2015.06.08.23.59.35 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 08 Jun 2015 23:59:35 -0700 (PDT) In-Reply-To: <873821xzon.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Tue, 09 Jun 2015 13:39:51 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::22e 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:187118 Archived-At: "Stephen J. Turnbull" writes: > 1. There *should* be a list of "recommended keywords" which package > maintainers can easily access for reference when choosing keywords > to specify for their packages and users can refer to get an idea > of the keywords maintainers are likely to use. This is what I was thinking. And it would facilitate adding an option to filter the package list by tags. I mean not searching (that should be there too), but browsing. 2000 packages is a lot, but if you narrow to a "git" tag, you'll get less than 50, which means there's a chance to browse them all. Similarly, "theme" should be a tag, enabling the user to browse all available themes. Most common package managers have an option to narrow to a tag. Emacs could be more flexible to allow e.g. a "+git +file -theme" tag filter. To give an example, Synaptic package manager has around 50 sections, featuring separate sections for R, Haskell, OCaml, PHP, Ruby etc. So if a user wants to see everything Emacs has to offer on Ruby, he'll just filter to a "ruby" tag. And then it's the package's author's fault if he didn't specify the proper tag. These tags could be also used to make the built-in files more visible. For instance, I've learned about cmacexp.el on this mailing list. But I could (and would prefer to) have learned about it by looking at the "c" tag. Here's the result of git grep: lisp/find-file.el:5: ;; Keywords: c, matching, tools lisp/obsolete/cc-compat.el:9:;; Keywords: c languages lisp/progmodes/cc-align.el:13:;; Keywords: c languages lisp/progmodes/cc-bytecomp.el:8:;; Keywords: c languages lisp/progmodes/cc-cmds.el:13:;; Keywords: c languages lisp/progmodes/cc-defs.el:13:;; Keywords: c languages lisp/progmodes/cc-engine.el:13:;; Keywords: c languages lisp/progmodes/cc-fonts.el:9:;; Keywords: c languages lisp/progmodes/cc-guess.el:10:;; Keywords: c languages oop lisp/progmodes/cc-langs.el:13:;; Keywords: c languages lisp/progmodes/cc-menus.el:12:;; Keywords: c languages lisp/progmodes/cc-mode.el:13:;; Keywords: c languages lisp/progmodes/cc-styles.el:13:;; Keywords: c languages lisp/progmodes/cc-vars.el:13:;; Keywords: c languages lisp/progmodes/cmacexp.el:8:;; Keywords: c lisp/progmodes/cpp.el:6:;; Keywords: c, faces, tools lisp/progmodes/cwarn.el:6:;; Keywords: c, languages, faces lisp/progmodes/ebrowse.el:7:;; Keywords: C++ tags tools lisp/progmodes/flymake.el:8:;; Keywords: c languages tools lisp/progmodes/hideif.el:8:;; Keywords: c, outlines lisp/progmodes/hideshow.el:7:;; Keywords: C C++ java lisp tools editing comments blocks hiding outlines lisp/tooltip.el:6:;; Keywords: help c mouse tools It could look a lot more pretty with the package description and all. And the point is that a person who appreciates C will likely check out all 22 built-in files that have the "c" tag.