feat(neovim)!: pull flake information from envvar
This makes so we don't have to rely on writing an extra derivation just for the parsed lsp configuration. Thus, the `programs.neovim.nixd.hostname` settings has been dropped and you can migrate your `programs.neovim.nixd.location` to `programs.neovim.flakePath` if you do not set the `FLAKE` envvar anywhere.
This commit is contained in:
parent
5090767ba2
commit
5b99eaffea
5 changed files with 34 additions and 49 deletions
|
@ -4,16 +4,14 @@ The module extends `programs.neovim`.
|
|||
|
||||
## Module options
|
||||
|
||||
### programs.neovim.nixd.hostname
|
||||
|
||||
By default [nixd] is enabled, you **need** to pass the current machine's
|
||||
hostname that is used to generate your system.
|
||||
|
||||
### programs.neovim.nixd.location
|
||||
### programs.neovim.flakePath
|
||||
|
||||
The location of your system's flake, [nixd] will execute an expression defined in the LSP's configuration that reads
|
||||
the flake's contents to evaluate [NixOS] and [Home Manager] options.
|
||||
|
||||
This setting is optional since other programs might force you to set the `FLAKE` environment variable; if this is not
|
||||
set by the time you open [neovim] it will spout an error, impeding critical plugins from starting.
|
||||
|
||||
### programs.neovim.ollama.enable
|
||||
|
||||
Whether to add an [ollama] package to be used with [ollama.nvim](https://github.com/nomnivore/ollama.nvim).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue