-
-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TRACKING] Use mkNeovimPlugin
treewide
#2638
Comments
mkNeovimPlugin
treewide
When I was building the documentation for nixvim on darwin I ran into this:
This might be related to fixing nixvim documentation to build on darwin. |
Maybe it would be worth it to separate this into separate issues so that they can be tracked and closed automatically as PRs targeting them are merged? |
Not sure about this... It would lead to a lot of them. |
Is it possible to write a script to rewite the options for |
Well, it would maybe be possible, but it would never be exhaustive. There are a lot of edge cases and it would be a very complex endeavor. "Old" non- |
I mean you could make it only compatible with certain option definitions then for everything else left should be done manually. |
Yes, you could surely implement some partial solution that could alleviate a part of the burden. Of course PR/ideas are welcome :) |
I had a bit of success using copilot for this purpose. I think if you setup a prompt correctly with a couple of
examples of before-and-after versions of some plugins, then it would probably do a very good job of at least making an initial conversion for some of the
simpler plugins.
|
I remember doing hat for a couple and it works very well if you find examples that handle all the option types relevant to the file you're converting. |
Just creating a tracker to keep track of what plugins need to be migrated to modern mkNeovimPlugin.
Backup - need to merge into new list
The text was updated successfully, but these errors were encountered: