mirror of
https://github.com/LunarVim/LunarVim.git
synced 2024-09-20 10:35:08 +02:00
Updated Home (markdown)
parent
aa9e82d56c
commit
aa17b384a3
1 changed files with 0 additions and 21 deletions
21
Home.md
21
Home.md
|
@ -40,28 +40,7 @@
|
||||||
- [Community links](#community-links)
|
- [Community links](#community-links)
|
||||||
- [TODO](#todo)
|
- [TODO](#todo)
|
||||||
|
|
||||||
# What’s included?
|
|
||||||
|
|
||||||
LunarVim provides neovim configuration files that take advantage of
|
|
||||||
tree-sitter and language server protocol. The configuration is written
|
|
||||||
in lua.
|
|
||||||
|
|
||||||
## Why do I want tree-sitter and LSP?
|
|
||||||
|
|
||||||
- Normally, an editor uses regular expression parsing for things like
|
|
||||||
highlighting and checking the syntax of your file. Each time you make
|
|
||||||
a change, the editor must re-parse the entire file. Tree-sitter, on
|
|
||||||
the other hand, transforms text into a syntax tree. Each time you make
|
|
||||||
a change, only the parts of the code that change need to be parsed.
|
|
||||||
This greatly improves the speed of parsing. This can make a huge
|
|
||||||
difference when editing large files.
|
|
||||||
|
|
||||||
- Neovim 0.5 including language server protocol means your editor can
|
|
||||||
provide: code actions, completions, formatting, navigating to
|
|
||||||
definitions, renaming, etc. The language server only has to be written
|
|
||||||
once and will work on any editor that supports LSP. Any improvements
|
|
||||||
made to the language server will immediately be used by all editors
|
|
||||||
that support LSP.
|
|
||||||
|
|
||||||
# Project Goals
|
# Project Goals
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue