From 815cb6d09d617689c797b14268530a91cbe0bea7 Mon Sep 17 00:00:00 2001 From: Alex Lai Date: Fri, 24 Nov 2023 17:06:32 +0800 Subject: [PATCH] Update faq.md --- versioned_docs/version-1.3/faq.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/versioned_docs/version-1.3/faq.md b/versioned_docs/version-1.3/faq.md index 1ebbc8b1..08e3cc1b 100644 --- a/versioned_docs/version-1.3/faq.md +++ b/versioned_docs/version-1.3/faq.md @@ -22,6 +22,17 @@ export LUNARVIM_BASE_DIR="${LUNARVIM_BASE_DIR:-"$HOME/.local/share/lunarvim/lvim exec neovide -- -u "$LUNARVIM_BASE_DIR/init.lua" "$@" ``` +Or you can set `$NEOVIM_BIN` env variable to let neovide start with lvim by default +```sh +export NEOVIM_BIN=$(which lvim) +``` + +``` +$ neovide --help + --neovim-bin + Which NeoVim binary to invoke headlessly instead of `nvim` found on $PATH +``` + ## What is `null-ls` and why do you use it? For C/C++ we have the `clangd` by `llvm` which can also use its siblings' abilities `clang-tidy` and `clang-format` to support additional linting and formatting. But something like `pyright` doesn't support formatting, so we use `null-ls` to register `black` and `flake8` for example, as a "fake" language server.