-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Config clean up #339
Comments
Hey @cameronr sorry, been a bit busy with work lately. Yes, I've been wanting to streamline the configs for sometime now. Something that particularly bothers me is that the LSP gets confused as to what options are available to use. And yes the vimscript configs need to be supported as legacy but certainly shouldn't be the default checks. Maybe a more streamlined implementation in a I think the goal on a revamp like this should be to make the configs easily discoverable by the LSP, with proper docstring documentation for each field. |
No worries, this is just a background idea. Good point to make sure whatever we do works well with the lua ls. I'm still ruminating on this one. I'd like to do it at some point but may take some time. |
@rmagatti it's not done yet (still have to do readme, maybe unify autocmds), but i made a bunch of progress on the config cleanup. can see some of it here if you want to take an early look: it's working nicely with lua_ls (when using a config function, sadly lazy opts tables don't get the same treatment): |
Nice, that looks awesome! |
Closed in #359 |
I'm thinking about trying to revamp the config to something like:
I would plan to make the Lua config the default in the docs but I'd support the existing vimscript args. I think I'd add a
config.lua
file and do everything there but that's still just a thought.@rmagatti What do you think? Are there other changes you'd make?
The text was updated successfully, but these errors were encountered: