doc: add WIP nvim example config #17
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Robzz
force-pushed
the
doc/nvim-example-config
branch
from
367bc1f
to
ad51913
Compare
|
I added an lspconfig based example using my fork (happy to send the PR their way once we're happy with it). |
Robzz
force-pushed
the
doc/nvim-example-config
branch
from
657b958
to
50bfff1
Compare
|
Just added a comment in this thread: #2 (comment) Excited to get this into nvim-lspconfig! |
Robzz
force-pushed
the
doc/nvim-example-config
branch
from
50bfff1
to
e1bddde
Compare
|
PR opened yesterday, took a bit longer than I would have liked but time is what it is. Waiting on me writing a bit of docs. |
This looks awesome thank you! Let me know if I can assist at all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an example configuration for neovim.
This to do before this is ready for merging:
nvim-lspconfigrepository. On top of providing a sane default config, this allows automated proper management of the language server lifecycle, because to be clear the provided sample code kinda smells: never detaches closed buffers, never shuts the LSP down, you get the idea, it's naive.nvim-cmpside. Support for multiline ghost-text was literally merged 2 days ago, and there are additional PRs addressing limitations that are actively being worked on, such as the suggestions window currently being drawn on top of the ghost text (PR 1955). In its current state, it's a bit rough around the edges, but it should be good enough to play with for the curious.textDocument/generationfunction. I still need to look into how that works, but thenvim-lspconfigdocs point towards setting up anLspAttachautofunction handler withvim.api.nvim_create_user_command()Closes #2