You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 13, 2024. It is now read-only.
on_attach = <on_attach you would pass to nvim-lspconfig>, -- required
capabilities = <capabilities you would pass to nvim-lspconfig>, -- required
Could we get expansion on what "pass to nvim-lspconfig" looks like, example code on how you would do that?
For folks not extremely familiar with lspconfig, it's not right away clear on what we are intended to do.
Perhaps a "working example" lua.init file with the bare minimum necessary to demo this plugin on its own working in an /examples folder could work, and then just link to that in the readme?
IE:
"Full bare minimum working example here: [Link]"
The text was updated successfully, but these errors were encountered:
I am interested in this as well. i was unable to get the CSInstallRoslyn command to work as it continuously errors, but i was able to install Roslyn from the GitHub repository. I wonder what should a config look like to connect this plugin to a local Roslyn install in my home directory?
That seems out of scope of this github issues discussion. The scope is discussing if the README's documentation is clear enough or needs improvement and, if so, what would be better.
For these lines of the Readme here:
Could we get expansion on what "pass to nvim-lspconfig" looks like, example code on how you would do that?
For folks not extremely familiar with lspconfig, it's not right away clear on what we are intended to do.
Perhaps a "working example" lua.init file with the bare minimum necessary to demo this plugin on its own working in an
/examples
folder could work, and then just link to that in the readme?IE:
"Full bare minimum working example here: [Link]"
The text was updated successfully, but these errors were encountered: