Compare commits

..

No commits in common. "3b2a37ef3d73152dec865701b2a04b4bdc985c19" and "6ec28999cb40b8a443a5148d846c57b4f81ed5a5" have entirely different histories.

3 changed files with 6 additions and 6 deletions

View file

@ -23,7 +23,7 @@ manner.
# flake.nix. For the sake of the argument, we will assume that the Neovim lua
# configuration is in a nvim/ directory relative to flake.nix.
vim = {
additionalRuntimePaths = [
additionalRuntimeDirectories = [
# This will be added to Neovim's runtime paths. Conceptually, this behaves
# very similarly to ~/.config/nvim but you may not place a top-level
# init.lua to be able to require it directly.
@ -41,7 +41,7 @@ directory, and call it with [](#opt-vim.luaConfigRC).
```nix
{pkgs, ...}: {
vim = {
additionalRuntimePaths = [
additionalRuntimeDirectories = [
# You can list more than one file here.
./nvim-custom-1

View file

@ -20,7 +20,7 @@ in {
'';
registers = mkOption {
type = str;
type = either str (listOf str);
default = "";
example = "unnamedplus";
description = ''
@ -33,8 +33,8 @@ in {
`"+"` ({command}`:h quoteplus`) instead of register `"*"` for all yank, delete,
change and put operations which would normally go to the unnamed register.
When `unnamed` and `unnamedplus` is included simultaneously as `"unnamed,unnamedplus"`,
yank and delete operations (but not put) will additionally copy the text into register `"*"`.
When `unnamed` and `unnamedplus` is included simultaneously yank and delete
operations (but not put) will additionally copy the text into register `"*"`.
Please see {command}`:h clipboard` for more details.

View file

@ -69,7 +69,7 @@
Use signs for diagnostics. See {command}`:help diagnostic-signs`.
:::{.note}
The code presented in that example section uses Lua expressions as object keys which
The code presented in that help section uses lua expressions as object keys which
only translate well if you use `lib.generators.mkLuaInline` as in the example.
:::
'';