unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Improving browsing and discoverability in the Packages Menu
Date: Sun, 19 Apr 2015 10:59:39 +0800	[thread overview]
Message-ID: <871tjgj010.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAAdUY-KOPrBuKdwwaZ7UPi_WBmfpjw1s8zByLXYf3DB7W4Dyvg@mail.gmail.com

Artur Malabarba <bruce.connor.am@gmail.com> writes:


[...]

> Also regarding 3: We have keywords but they are not the same thing as
> categories. 
> I'm not saying we should come up with yet another classification, but
> I'm saying that keywords need some serious work. It's not obvious to
> the user what keywords are available or how to browse them. And
> they're sort of all over the place with a lot of overlap.

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.

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.

Eric




  parent reply	other threads:[~2015-04-19  2:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 22:38 Improving browsing and discoverability in the Packages Menu Artur Malabarba
2015-02-16  2:25 ` Stefan Monnier
2015-02-18 16:23 ` raman
2015-04-18 11:26   ` Ted Zlatanov
2015-04-18 13:25     ` Artur Malabarba
2015-04-18 13:25     ` Artur Malabarba
2015-04-18 21:11     ` raman
2015-04-18 23:05       ` Ted Zlatanov
2015-04-19  1:20         ` Alexis
2015-04-19  3:16           ` Stefan Monnier
2015-04-19  4:03             ` Alexis
2015-04-19 16:14             ` raman
2015-04-20  1:57               ` Stefan Monnier
2015-04-19 16:12         ` raman
2015-04-20  1:22           ` Ted Zlatanov
2015-04-20  9:02             ` Artur Malabarba
2015-04-20 15:18             ` raman
2015-04-20 15:23               ` Drew Adams
2015-04-21  0:20                 ` raman
2015-04-21  1:07                   ` Drew Adams
2015-04-19  2:59 ` Eric Abrahamsen [this message]
2015-04-19 14:58   ` Drew Adams
2015-04-20  8:38     ` Eric Abrahamsen
2015-04-20  9:26       ` Artur Malabarba
2015-04-20 10:17         ` Alexis
2015-04-20 11:30           ` Artur Malabarba
2015-04-20 14:32             ` Drew Adams
2015-04-20 17:32               ` Artur Malabarba
2015-04-20 18:17                 ` Drew Adams
2015-04-20 19:49                   ` Artur Malabarba
2015-04-20 20:30                     ` Drew Adams
2015-04-21  4:05                       ` Tassilo Horn
2015-04-21  5:25                         ` Drew Adams
2015-04-21  6:52                           ` Tassilo Horn
2015-04-21  9:04                             ` Eric Abrahamsen
2015-04-21 15:44                             ` Drew Adams
2015-04-20 14:03           ` Eric Abrahamsen

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=871tjgj010.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@gnu.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).