deprecate snippets/ remove from plugin list

[ghost]

Description of the problem or steps to reproduce

One other thing I had much trouble with was the snippetnext, I just could not figure out how to work with the placeholders $1 like

#ifndef `toupper(vim_snippets#Filename('$1_H', 'UNTITLED_H'))`
#define $1

#endif /* end of include guard: $1 */

if I start to type it does not work, if I first hit snippetnext, it does not work

there does not seem to be any activity on fixing issues so I'd recommend removing it from the plugin list because it just does not work (only extremely basic).

[tommyshem]

It is a simple snippet insert plugin as it say's on the GitHub page. Type known snippet and press Alt-s for snippet to be replaced. Works great for me using it for Go snippets on Linux.

The above snippet will not work as it is a vim snippet, auto-fill from filename converted to uppercase. Try a different snippet to see if you have the same problems.

The developer updated it 24 days go. (He does not update a lot but he does take pull requests)

[ghost]

The issue is: the normal micro user does not create pull requests but expects working software. The vim completions are shipped with the plugin so it‘s reasonable to expect them to work.

[tommyshem]

There is problems with most of the plugins but as the micro editor is moving forward and adding new features they get better, not just removing plugins from the list because you are having problems. Is it crashing micro editor, if not then it should not be removed, it should have issues logged on their github page, unless it crashes micro editor then log issues here. There is hundreds of snippets over different programming languages and the idea is you make your own snippets to use. I use this plugin-in and removing it from the list will make it harder to install and harder for new users to find. Micro itself has over 100 issues so no software works perfect out of the box.

[ghost]

There is hundreds of snippets over different programming languages and the idea is you make your own snippets to use.

I thought these hundreds of snippets were supposed to be used so that not everyone has to replicate them.

make it harder to install and harder for new users to find

it will reduce disappointment if they find that micro plugins do not work as advertised, they think it's their fault and loose time

Micro itself has over 100 issues

critical issues are addressed very quickly, the count does not necessarily represent the regressions, in the snippets plugin that regression is severe cause most of the supplied commands do not work