From d2650dca2a7a11000b8f2f2dece4ff4cdb367ea1 Mon Sep 17 00:00:00 2001 From: ambaradan Date: Mon, 19 Sep 2022 17:32:01 +0200 Subject: [PATCH] Changed frontmatter titles for better understanding of the side menu. --- docs/books/nvchad/custom/plugins/lspconfig_lua.md | 14 +++++++------- docs/books/nvchad/custom/plugins/null_ls.md | 2 +- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/books/nvchad/custom/plugins/lspconfig_lua.md b/docs/books/nvchad/custom/plugins/lspconfig_lua.md index 0202923a93..22a1ef0e56 100644 --- a/docs/books/nvchad/custom/plugins/lspconfig_lua.md +++ b/docs/books/nvchad/custom/plugins/lspconfig_lua.md @@ -1,15 +1,15 @@ --- -title: lspconfig.lua +title: Language Server author: Franco Colussi contributors: Steven Spencer tested with: 8.6, 9.0 tags: - - nvchad - - coding - - editor + - nvchad + - coding + - editor --- -# `lspconfig.lua` +# lspconfig.lua This configuration file assigns the functionality defined in `nvim/lua/plugins/configs/lspconfig.lua` to the language servers we have installed with `Mason`. The language servers should be placed in the local servers according to this format: @@ -17,7 +17,7 @@ This configuration file assigns the functionality defined in `nvim/lua/plugins/c local servers = { "html", "marksman", "yamlls"} ``` -As pointed out earlier, there is no need to make explicit support for Lua as it is enabled by default by NvChad; however, the *lua-language-server* must be installed with *Mason* to be available in the IDE. +As pointed out earlier, there is no need to make explicit support for Lua as it is enabled by default by NvChad; however, the _lua-language-server_ must be installed with _Mason_ to be available in the IDE. Let us then look at our `lspconfig.lua` file: @@ -40,4 +40,4 @@ The first two instructions import the `on_attach` and `capabilities` features fr After the first configuration, it is advisable to exit and re-enter the editor before running SHIFT + :PackerSync. Subsequent language server entries to the configuration can be registered with SHIFT + :LspRestart without the need to reload the configuration. The next time a supported file is opened, it will bring up an icon at the bottom with associated LSP and language server used. This gives us confirmation that the LSP is running properly. -Summarizing, the `lspconfig.lua` file configures the functionality of the servers we install. It is a file that, after the first configuration, will not need much editing as long as we write documentation in Markdown. For more information on the **L**anguage **S**erver **P**rotocol you can consult the [dedicated page](../lsp.md). +Summarizing, the `lspconfig.lua` file configures the functionality of the servers we install. It is a file that, after the first configuration, will not need much editing as long as we write documentation in Markdown. For more information on the **L**anguage **S**erver **P**rotocol you can consult the [dedicated page](../lsp.md). diff --git a/docs/books/nvchad/custom/plugins/null_ls.md b/docs/books/nvchad/custom/plugins/null_ls.md index b1847319b5..fd044c5634 100644 --- a/docs/books/nvchad/custom/plugins/null_ls.md +++ b/docs/books/nvchad/custom/plugins/null_ls.md @@ -1,5 +1,5 @@ --- -title: Null-ls +title: Linter & Formatter author: Franco Colussi contributors: Steven Spencer tested with: 8.6, 9.0