Skip to content

fix intro.txt document about Neovim#19605

Closed
brianhuster wants to merge 2 commits intovim:masterfrom
brianhuster:neovim
Closed

fix intro.txt document about Neovim#19605
brianhuster wants to merge 2 commits intovim:masterfrom
brianhuster:neovim

Conversation

@brianhuster
Copy link
Contributor

@brianhuster brianhuster commented Mar 7, 2026

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

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

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.
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
@chrisbra
Copy link
Member

chrisbra commented Mar 8, 2026

thanks

@brianhuster brianhuster deleted the neovim branch March 9, 2026 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants