Implementing an embedded plugin list in tpm?

[briansalehi]

Hey community, I'm skimming through the list of available plugins mentioned
in the readme page and I'm trying to figure out which plugin suites my needs.

So far, I have opened at least 20 tabs to read through each of them and manually
have written the set -g @plugin "tmux-plugin/plugin-name" repeatedly.

Even though someone recommended to write a list of plugins in tpm's readme
page, but I find it unfortunate to not have an updated list in the tpm plugin itself.
Of course, the tpm plugin itself requires manual installation on a system besides
tmux, which I also find it a shortcoming, but ignoring the fact that tmux itself shoud
come with its plugin manager in a box, we could at least consider a key-binding
in tpm to list available plugins so that users can automatically install them by it.

To keep the story short, why don't we have a default key-binding in tpm to fetch
all available community approved plugins and list it somehow so that users can
select and install on demand? Any ideas on this feature?

[RossBarnie]

We could use the awesome-tmux project as the source of truth of "community-approved plugins". One of the main issues will be the maintenance of that list, the implementation can be relatively crude:

1. Listen for Prefix + L (or similar)
2. List projects in approved list with numbers, prompt user for number of project to add
3. Edit tmux config file above the run tpm command
4. Load plugins, reload tmux config

But to be honest it doesn't solve your problem. You'd still have to investigate each plugin for what it does, how it does it, what configuration is available, etc.