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:44 +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=089e012291a25100240513ffa26c X-Trace: ger.gmane.org 1429363575 17603 80.91.229.3 (18 Apr 2015 13:26:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Apr 2015 13:26:15 +0000 (UTC) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 18 15:26:10 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 1YjSl7-00072P-S8 for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 15:26:10 +0200 Original-Received: from localhost ([::1]:45711 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjSl6-0005om-Sx for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 09:26:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40367) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjSkk-0005LP-GS for emacs-devel@gnu.org; Sat, 18 Apr 2015 09:25:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YjSkj-00085R-HI for emacs-devel@gnu.org; Sat, 18 Apr 2015 09:25:46 -0400 Original-Received: from mail-lb0-x22d.google.com ([2a00:1450:4010:c04::22d]:36025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjSkj-00085E-8V for emacs-devel@gnu.org; Sat, 18 Apr 2015 09:25:45 -0400 Original-Received: by lbbqq2 with SMTP id qq2so101321482lbb.3 for ; Sat, 18 Apr 2015 06:25:44 -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=i3h0MEv2q+w6GHF8KZ6bjaFX58mrEDoQrLVH6dv+2aM=; b=o6lEavoH/1KbwP4qHOBSOxGEYtPzCsdVuvyzHHxz7goI+Xub5oJ6EanteFg6vuyj4t y7Qgj+iCT8o2Ge/Twedza+DuO1CcGMLSxr2whsDqWTQa6AeCspSTh072rmJ+g4JWOuKf fG3VoEG0HBjWu9ASVS6lmhn6Ai45mbj0ZtW/to2LsFeVs8jQuqj4a+pbKxNavbBXc28F oS2eSzyxSIOG5Eag0bBkll4Yl4FQ9dz6nUBSnRqovWDdNGzK1t5NZZfD9Ql7GrJraCeA iETtqbSrcKWC5I4aJBEtvAmRprYRajPcNXhgNRZSKsieCEkkZZJNkMBWeSRYOEqzLI4g +E4Q== X-Received: by 10.152.2.105 with SMTP id 9mr8286538lat.16.1429363544356; Sat, 18 Apr 2015 06:25:44 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Sat, 18 Apr 2015 06:25:44 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Sat, 18 Apr 2015 06:25:44 -0700 (PDT) In-Reply-To: <87r3rhoexe.fsf@lifelogs.com> X-Google-Sender-Auth: VDC1Eo07XGBnYBAc38kTonzdnc8 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::22d 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:185580 Archived-At: --089e012291a25100240513ffa26c 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. --089e012291a25100240513ffa26c 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.

--089e012291a25100240513ffa26c--