Added additional information to make installing Hyuga easier. #21
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
Instructions on how to register Hyuga using the more widely used lspconfig have been added, and installation of Hyuga itself using `pipx` on *Nix systems (mainly Arch deals with this) where the global Python environment is isolated and running `pip install hyuga` without adding `--break-system-packages` is impossible.
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.
Instructions on how to register Hyuga using lspconfig have been added, and instructions on the installation of Hyuga itself on Linux distributions that use externally managed Python environments (primarily Arch), where trying to
pip3 install hyugawithout--break-system-packagesis literally impossible, have also been added (pipx, as mentioned in the aforementioned spec is the most common way of installing packages via pip on EME distros)These additions are all hurdles I faced that I had to figure out myself. I'm hoping to include this information so that the next person doesn't have to go through the same 2 hour installation process I had to go through.
That, and lspconfig is generally the most popular way to deal with language servers in Neovim nowadays.
I hope this helps save someone from a future headache.