Malabarba / paradox

Project for modernizing Emacs' Package Menu. With package ratings, usage statistics, customizability, and more.
GNU General Public License v2.0
561 stars 36 forks source link

feature request: hiearchical package list #163

Open Davidbrcz opened 5 years ago

Davidbrcz commented 5 years ago

Hi,

Is is possible to display the list of packages not flat but in a hierarchical manner (in similar way to what's is done in org mode) according to some regex/tagging ?

For instance, all the packages for flycheck could be under a same entry, same goes for company, counsel, ... That way, I would be easier to browse the list of packages and discover relevant packages.

Thanks !

Malabarba commented 5 years ago

It's something that could potentially be implemented, but no, it's not possible at the moment.

Unfortunately it would also be quite difficult, because the package buffer uses tabulated-list-mode for its structure.

Davidbrcz commented 5 years ago

Ok for folding in org mode. But what do you think about some kind of virtual packages. Instead of displaying all of flycheck packages, simply an entry flychek-packages and pressing enter/what ever key would display a new buffer with all the packages in it.

Malabarba commented 5 years ago

That sounds very plausible, but it's still quite a delicate structural change. I think I'd be more comfortable if that were implemented as a separate package somehow.

Davidbrcz commented 5 years ago

Ok. I'll look into in when I'll have time

a13 commented 5 years ago

There are keywords in package descriptions which you can click, flycheck is one of them

Davidbrcz commented 5 years ago

Strange I had missed that up to now... Very convenient feature, even if the keywords are a bit too wide.

For instance, if I look into the flycheck package, its keywords are convenience, languages, and tools (even if avy-flycheck has a flycheck keyword, not all flycheck-related packages do ...). So I guess it's up to package maintainer (and maybe repo ?) to update their keywords.

a13 commented 5 years ago

So I guess it's up to package maintainer (and maybe repo ?) to update their keywords.

yes, these are written in the code, so you always can make a pull request :)