fix intro.txt document about Neovim#19605
Closed
brianhuster wants to merge 2 commits intovim:masterfrom
Closed
Conversation
Just to fix some phrases: - "A Vim clone". Neovim document says that it is not a clone, but just a fork https://neovim.io/doc/user/nvim/#nvim - "Supports a remote GUI". Neovim supports any UI (both GUI and TUI) that implements its UI protocol, so "a" is not correct - "Integration with scripting languages". This is true, but it is also true to Vim (which supports 8 scripting languages AFAIK), so this probably doesn't need to be said in this document. Instead, what makes Neovim unique in this "scripting languages" aspect is its first class support for Lua.
zeertzjq
reviewed
Mar 7, 2026
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
Member
|
thanks |
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.
Just to fix some phrases:
I also doubt about "making development more complex", but I am not sure, so I'll leave it as-is. Perhaps @zeertzjq and @glepnir who have had many direct contributions to both Vim and Neovim will have better comments