Update pandasoli/nekovim

[m15a]

Repo URL:

404 not found: https://github.com/pandasoli/nekovim

The repository looks like moved to https://git.sr.ht/~elisoli/nekovim.
See also the author's message: https://github.com/pandasoli.

Checklist:

• The plugin is specifically built for Neovim.
• The plugin is licensed.
• The lines end with a .. This is to conform to awesome-list linting and requirements.
• The title of the pull request is Add/Update/Remove `username/repo` (notice the backticks around `username/repo`) when adding a new plugin.
• The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else. No .. for Neovim.
• The description doesn't contain emojis.
• Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
• Acronyms (LSP, TS, YAML, etc.) are fully capitalized.

[DrKJeff16]

I've examined the structure of the plugin and... it throws me off:

---

Reasoning

There's a very real possibility of module collission. Take for instance the utils/ folder.
While there's no init.lua inside it can be problematic for people's configs, no matter how scuffed they are.

In Lua, this translates to:

require('utils.<module>')

We have a real issue with modules colliding for someone.

Thoughts, @Penaz91?

[Penaz91]

Usually plugin entry points are under lua/plugin_name.lua or lua/plugin_name/init.lua and the require() commands are relative to the plugin's lua directory, so I don't see many issues. I'm pretty sure any plugin that uses a utils module would collide otherwise, and I'm pretty sure you couldn' have tens of plugins installed if there really were name collisions.

I think it should be fine, and if there are collision issues, they should probably be sent to the plugin developer.