From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Improving browsing and discoverability in the Packages Menu Date: Sat, 18 Apr 2015 14:25:42 +0100 Message-ID: References: <87r3rhoexe.fsf@lifelogs.com> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113746cc3c7e800513ffa2b5 X-Trace: ger.gmane.org 1429363550 17033 80.91.229.3 (18 Apr 2015 13:25:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Apr 2015 13:25:50 +0000 (UTC) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 18 15:25:50 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 1YjSkn-0006ng-L3 for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 15:25:49 +0200 Original-Received: from localhost ([::1]:45707 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjSkm-0005LQ-Nu for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 09:25:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40356) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjSki-0005LI-TZ for emacs-devel@gnu.org; Sat, 18 Apr 2015 09:25:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YjSkh-000854-TY for emacs-devel@gnu.org; Sat, 18 Apr 2015 09:25:44 -0400 Original-Received: from mail-qg0-x235.google.com ([2607:f8b0:400d:c04::235]:33625) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjSkh-00084y-I5 for emacs-devel@gnu.org; Sat, 18 Apr 2015 09:25:43 -0400 Original-Received: by qgdy78 with SMTP id y78so33822996qgd.0 for ; Sat, 18 Apr 2015 06:25:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=5w/GnopZy4z+BqgktQ6nUp0mKQwGUn6t7tBVYd5aAvI=; b=J4FpUc6c0SzP3wuJglsmih0M9noACcDUgxcRm1R2UJyuq8T8+DK3ZrvuRxFpAp7KKU lW6cspX9aY3hvGkrKiETwcre8Twx2+VrsB4rfKeR42cGQ+H7ImnSHBwLbBR0IreWeWlA /CLuhxPEB16bM/wHjGI5EP8p/+H/3ccT20p4OIlkU4xNcmXXK4x6Rph3B65fazXQ6loF drh+FgPhVx1l3/c8VjdarNwmLT2PTgTnG4ssn73cUf5jPDMrLnetQGWtRqjlbeaZkbxq iGIZo4uGRHyGN3KiERsFZUk9Kegw5EmEsqZcbZeWDCb/slIUky+iq5hakNbWJZFurzgW JQ4g== X-Received: by 10.140.151.15 with SMTP id 15mr8939090qhx.104.1429363543012; Sat, 18 Apr 2015 06:25:43 -0700 (PDT) Original-Received: by 10.229.237.136 with HTTP; Sat, 18 Apr 2015 06:25:42 -0700 (PDT) Original-Received: by 10.229.237.136 with HTTP; Sat, 18 Apr 2015 06:25:42 -0700 (PDT) In-Reply-To: <87r3rhoexe.fsf@lifelogs.com> X-Google-Sender-Auth: Hg2I1KzvMogQ2kE5OB-2knlmvpU X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c04::235 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:185579 Archived-At: --001a113746cc3c7e800513ffa2b5 Content-Type: text/plain; charset=UTF-8 > r> Many ways of filtering -- over and above the present "filter by > r> keywords" would be nice. > > r> 1. Hide all installed/builtin packages > r> 2. Hide packages from one or more repositories > > (Sorry for the late comment, I've been away. I don't think this has > happened, though?) It hasn't. > It would be easiest, I think, to make the source repo, the package > status, and other metadata (signed, etc.) into keywords and then enhance > the keyword browsing. The "filter" functionality Stefan suggested makes > sense across keywords *and* package names and descriptions, and can > easily be plugged into the current "Filter" function in the menu. Sounds very reasonable. We could also implement excluding keywords. So it would be easy to hide nil built-ins, for instance. > r> 3. Hide helper packages eg packages that would only be installed as a > r> dependency of something else that is user-facing > > I don't think it's good to ever hide those, This part is already done. Dependencies are not hidden, but are given a comment face and sorted after the installed packages. If the above is implemented, it should also be easy to hide them. --001a113746cc3c7e800513ffa2b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

> r> Many ways of filtering -- over and above the pres= ent "filter by
> r> keywords" would be nice.
>
> r> 1. Hide all installed/builtin packages
> r> 2. Hide packages from one or more repositories
>
> (Sorry for the late comment, I've been away.=C2=A0 I don't thi= nk this has
> happened, though?)

It hasn't.

> It would be easiest, I think, to make the source repo, = the package
> status, and other metadata (signed, etc.) into keywords and then enhan= ce
> the keyword browsing.=C2=A0 The "filter" functionality Stefa= n suggested makes
> sense across keywords *and* package names and descriptions, and can > easily be plugged into the current "Filter" function in the = menu.

Sounds very reasonable. We could also implement excluding ke= ywords. So it would be easy to hide nil built-ins, for instance.

> r> 3. Hide helper packages eg packages=C2=A0 that wo= uld only be installed as a
> r> dependency of something else that is user-facing
>
> I don't think it's good to ever hide those,

This part is already done. Dependencies are not hidden, but = are given a comment face and sorted after the installed packages.

If the above is implemented, it should also be easy to hide = them.

--001a113746cc3c7e800513ffa2b5--