unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleh Krehel <ohwoeowho@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>,
	Artur Malabarba <bruce.connor.am@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Adding a few more finder keywords
Date: Tue, 09 Jun 2015 08:52:57 +0200	[thread overview]
Message-ID: <87zj49jrue.fsf@gmail.com> (raw)
In-Reply-To: <873821xzon.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Tue, 09 Jun 2015 13:39:51 +0900")

"Stephen J. Turnbull" <stephen@xemacs.org> 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.



  reply	other threads:[~2015-06-09  6:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 16:59 Adding a few more finder keywords Artur Malabarba
2015-04-25 18:51 ` Drew Adams
2015-04-25 19:23   ` Artur Malabarba
2015-06-08 14:56 ` Oleh Krehel
2015-06-08 15:37   ` Drew Adams
2015-06-08 15:43     ` Oleh Krehel
2015-06-08 16:20       ` Drew Adams
2015-06-08 16:15   ` Artur Malabarba
2015-06-08 16:19     ` Artur Malabarba
2015-06-08 16:27       ` Drew Adams
2015-06-08 20:59   ` Stefan Monnier
2015-06-09  4:39     ` Stephen J. Turnbull
2015-06-09  6:52       ` Oleh Krehel [this message]
2015-06-09  8:02         ` Artur Malabarba
2015-06-09  8:54           ` Oleh Krehel
2015-06-09 14:22       ` Drew Adams
2015-06-09 14:47         ` Oleh Krehel
2015-06-09 16:05           ` Drew Adams
2015-06-09 16:47             ` Oleh Krehel
2015-06-09 17:19               ` Drew Adams
2015-06-09 16:08           ` Stephen J. Turnbull

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zj49jrue.fsf@gmail.com \
    --to=ohwoeowho@gmail.com \
    --cc=bruce.connor.am@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=stephen@xemacs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).