From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Improving browsing and discoverability in the Packages Menu Date: Sat, 18 Apr 2015 07:26:37 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87r3rhoexe.fsf@lifelogs.com> References: Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1429356442 11203 80.91.229.3 (18 Apr 2015 11:27:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Apr 2015 11:27:22 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 18 13:27:07 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 1YjQts-0000Xp-Ne for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 13:27:04 +0200 Original-Received: from localhost ([::1]:45270 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjQtr-0000Ib-Vp for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 07:27:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41302) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjQto-0000IM-2I for emacs-devel@gnu.org; Sat, 18 Apr 2015 07:27:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YjQtk-00044W-Rd for emacs-devel@gnu.org; Sat, 18 Apr 2015 07:26:59 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:58184) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjQtk-00044S-LI for emacs-devel@gnu.org; Sat, 18 Apr 2015 07:26:56 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YjQtc-0000QS-WC for emacs-devel@gnu.org; Sat, 18 Apr 2015 13:26:49 +0200 Original-Received: from c-98-229-61-72.hsd1.ma.comcast.net ([98.229.61.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 18 Apr 2015 13:26:48 +0200 Original-Received: from tzz by c-98-229-61-72.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 18 Apr 2015 13:26:48 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 27 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-229-61-72.hsd1.ma.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:CnI9Xe4vHx6FqBLPc+hxL59AFBc= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:185568 Archived-At: On Wed, 18 Feb 2015 08:23:51 -0800 raman wrote: 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 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. 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, but maybe they could be given the "required-by=user-level-package" tags (multiples would be OK)? And then in the UI they could be presented in a visually different way. But hiding them would be a problem if you end up installing things you didn't want. Ted