Remove wildly inaccurate OS specific install steps and point at the excellent offocial docs intead!#1353
Closed
Remove wildly inaccurate OS specific install steps and point at the excellent offocial docs intead!#1353
Conversation
number of axes. The official Neovim installation docs are excellent now. Leverage those instead.
Contributor
|
We have some extra dependencies, like |
Collaborator
Author
|
@VlaDexa I like that idea but it's unclear to me how to thread that needle. Would you consider proposing an alternative PR? You can even use the Github web UI to create it! :) |
Collaborator
Author
|
This problem really needs a fix but this isn't the right solution as it throws out too much. |
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
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.
The old platform / OS specificd install instructions were wildly incorrect along a number of axes. The official Neovim installation docs are excellent now. Leverage those instead.
(Note: As I've mentioned in the past, I'm generating a PR from this repo because I already run my own personal fork that has diverged a ton from master and can't generate PRs from there without a hand picked nightmare :)