lunarvim.org icon indicating copy to clipboard operation
lunarvim.org copied to clipboard

Adding related plugins section to the languages

Open premell opened this issue 3 years ago • 3 comments

There are a lot of language specific plugins which currently exists in the "plugins" section. I think it would be better to either have the language specific ones in the language section, or have them in both places.

premell avatar Aug 16 '21 12:08 premell

We can link from the language section to the relevant plugin. I don't want to copy the entire plugin configuration to both places. It adds a maintenance burden. And I think the extra plugin section is the right place to keep all these plugins.

Here are the vuepress docs on creating these links: https://vuepressbook.com/tutorial/tutorial2.html#creating-links

rebuilt avatar Aug 17 '21 08:08 rebuilt

Hmm maybe, but it feels strange to have language specific plugins in the plugin section, since they are irrelevant to 90% of users. Many of these language specific plugins are also very likely to be used when you are using said language, in comparison to regular plugins. Since you probably want to use many of the plugins associated with a specific language it feels annoying to have to read through all the plugins in the plugins section to find the relevant ones. Another alternative is to have a subsection in the plugins section with "Language specific plugins". This way you can easily find the plugins relevant to your language, people that don't use that language don't have to have the general plugins list diluted by irrelevant ones and the information don't have to be duplicated, avoiding the maintenance burden.

premell avatar Aug 17 '21 09:08 premell

Putting plugins directly in the language section gets tricky fast. We are going to have to make decisions about the placement of every single plugin. Some language plugins will not be easily assigned a single language.

For example emmet-ls supports html and css files. Where do you place it? Since we don't put it in the plugins section anymore do we now put it in html and link to the css language? Do we place the full configuration in both? There's a request for the plugin to support react files. If react support is added, do we then add the configuration to react as well?

Similarly, the 'colorizer' plugin is listed under the colorschemes section. But it's probably useful to many different languages. Are we going to add it to the languages sections of html, css, vue, tailwind, javascriptreact, typescriptreact, svelte etc?

rebuilt avatar Aug 17 '21 17:08 rebuilt

Closing since its inactive.

vonPB avatar Oct 20 '22 13:10 vonPB