Skip to content

docs: Document methods to get the latest neovim #1626

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Mithrandir2k18
Copy link

Fixes #1583

List, link briefly describe some methods that get new neovim versions very quickly, as discussed in the linked issue. With this, pretty much anybody should find a convenient way to install and update. This additional shorter list adds value to newcomers because it only lists methods that update very quickly, which is a necessity for using kickstart, whereas neovims install.md is exhaustive, but doesn't mention the issue of outdated packages.

@oriori1703
Copy link
Contributor

This looks great 😄

@oriori1703
Copy link
Contributor

Do you think installing from tarball / building from source should also be mentioned, or are they too advanced / inconvenient for a beginner?

@Mithrandir2k18
Copy link
Author

Do you think installing from tarball / building from source should also be mentioned, or are they too advanced / inconvenient for a beginner?

I can't really speak for beginners here, I find installing from tarball (or appimage) pretty easy. They are both mentioned in the install.md over at the neovim repo. The other reason why I wouldn't list them here is that they don't have any kind of update functionality.

Imagine a beginner, following this readme, the package manager version is outdated, so they grab it as a tarball. 6 Months later, a breaking change forces them to upgrade. Realistically by now they have forgotten what a tarball even is, how they got it and so on.

But the same could happen with any other installation that isn't the distros main package manager, they could forget about bob, flatpack, etc. as well. I'll happily add it though, if you think it's valuable to have.

Copy link
Contributor

@oriori1703 oriori1703 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are probably right about the auto update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[docs] Document all sane ways to get the latest stable neovim release in the README
2 participants