Lumping plugin scripts into rc/ and lib.kak is incohesive given the intended use-case of kakoune.cr. Each of these functions provide conflicts to other plugins which many people would prefer (auto-pair, surround, find, palette, etc) and none of these functions are related to the stated focus of kakoune.cr. Conglomerating unrelated functions into one project is a very poor design choice, especially in the context of a plugin. Most new users will choose not to bother with kakoune.cr after manually installing it (opposed to plug.kak) and finding out that the bloat will conflict with their preferred plugins and break their entire config.
At the very least the extra functions should be separated into a “library” repo:
still less repos to maintain for the author
understood that users copy/clone/source from the library however they see fit
kakoune.cr stays cohesive and predictable
kakoune.cr remains interoperable with existing configs and separate plugins
alexherbo2
commented
3 years ago
Lumping plugin scripts into rc/ and lib.kak is incohesive given the intended use-case of kakoune.cr. Each of these functions provide conflicts to other plugins which many people would prefer (auto-pair, surround, find, palette, etc) and none of these functions are related to the stated focus of kakoune.cr. Conglomerating unrelated functions into one project is a very poor design choice, especially in the context of a plugin. Most new users will choose not to bother with kakoune.cr after manually installing it (opposed to plug.kak) and finding out that the bloat will conflict with their preferred plugins and break their entire config.
At the very least the extra functions should be separated into a “library” repo: