docs(tip-and-tricks): Neovim LSP setup guide#576
Open
DudeNr33 wants to merge 2 commits intorobotcodedev:mainfrom
Open
docs(tip-and-tricks): Neovim LSP setup guide#576DudeNr33 wants to merge 2 commits intorobotcodedev:mainfrom
DudeNr33 wants to merge 2 commits intorobotcodedev:mainfrom
Conversation
More robust implementation of get_python_path helper function.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi @d-biehl,
as discussed at RoboCon I created a small guide how to get LSP working inside Neovim with properly resolving keywords from third party libraries.
For the "globally" installed RobotCode option I chose a slightly different approach compared to the way the VS Code plugin handles it: instead of using the Python interpreter of the project and adding the bundled RobotCode installation to the PYTHONPATH, it uses the RobotCode installed via Mason and adds the virtual environment of the project to the PYTHONPATH.
Mason has deprecated their APIs to find the installation directory of the packages it manages and explicitly states the directory structure is not treated as stable interface and may change, thus this should be the more robust approach.
Tested on both Linux and Windows.
I am open to where in the docs this should go.