We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Been attempting to audit Emacs eglot configurations vs. pylsp logs and behaviors (a frustrating and time-consuming process).
eglot
pylsp
pylsp code says; e.g.
return { "rope": {"extensionModules": MODULES},
self.__rope.prefs.set( "extension_modules", rope_config.get("extensionModules", [])
Yet the schema says string and not array.
"pylsp.rope.extensionModules": { "type": [ "string",
Is this innocuous or does it have negative effects? Do the rest of the entries need auditing is a question this raises...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Been attempting to audit Emacs
eglot
configurations vs.pylsp
logs and behaviors (a frustrating and time-consuming process).pylsp
code says; e.g.Yet the schema says string and not array.
Is this innocuous or does it have negative effects? Do the rest of the entries need auditing is a question this raises...
The text was updated successfully, but these errors were encountered: