diff --git a/index.xhtml b/index.xhtml index dff3e6d..83eb1ff 100644 --- a/index.xhtml +++ b/index.xhtml @@ -33,7 +33,7 @@
Table of Contents
Table of Contents
If you noticed a bug caused by nvf then please consider reporting it over the issue tracker.
Bugfixes, feature additions and upstreamed changes from your local configurations are always welcome in the the pull requests tab.
@@ -292,7 +292,7 @@ in theAs of v0.5, you may now specify the Neovim package that will be wrapped with +
As of v0.5, you may now specify the Neovim package that will be wrapped with
your configuration. This is done with the vim.package
option.
{inputs, pkgs, ...}: {
# using the neovim-nightly overlay
vim.package = inputs.neovim-overlay.packages.${pkgs.system}.neovim;
@@ -493,14 +493,18 @@ attribute names in afters
. For example
From the previous chapter, it should be clear that DAGs are useful, because you +
Table of Contents
From the previous chapter, it should be clear that DAGs are useful, because you can add code that relies on other code. However, if you don’t know what the entries are called, it’s hard to do that, so here is a list of the internal -entries in nvf:
vim.luaConfigRC
(top-level DAG):
(luaConfigPre
) - not a part of the actual DAG, instead, it’s simply
-inserted before the rest of the DAG
globalsScript
- used to set globals defined in vim.globals
basic
- used to set basic configuration options
theme
(this is simply placed before pluginConfigs
, meaning that surrounding entries don’t depend on it) - used to set up the theme, which has to be done before other plugins
pluginConfigs
- the result of the nested vim.pluginRC
(internal option,
-see the Custom Plugins page for adding your own
-plugins) DAG, used to set up internal plugins
extraPluginConfigs
- the result of vim.extraPlugins
, which is not a
+entries in nvf:
vim.luaConfigRC
(top-level DAG) (luaConfigPre
) - not a part of the actual DAG, instead, it’s simply
+inserted before the rest of the DAG
globalsScript
- used to set globals defined in vim.globals
basic
- used to set basic configuration options
optionsScript
- used to set options defined in vim.o
theme
(this is simply placed before pluginConfigs
, meaning that
+surrounding entries don’t depend on it) - used to set up the theme, which has
+to be done before other plugins
pluginConfigs
- the result of the nested vim.pluginRC
(internal option,
+see the Custom Plugins page for adding your
+own plugins) DAG, used to set up internal plugins
extraPluginConfigs
- the result of vim.extraPlugins
, which is not a
direct DAG, but is converted to, and resolved as one internally
mappings
- the result of vim.maps
Table of Contents
nvf is designed for developers as much as it is for the end user. I would like any potential contributor to be able to propagate their desired changes into the repository without the extra effort. As such, below are guides diff --git a/options.html b/options.html index 6c146e6..a960893 100644 --- a/options.html +++ b/options.html @@ -7846,10 +7846,10 @@ boolean
An attribute set containing global variable values for storing vim variables as early as possible. If populated, this option will set vim variables in the -built luaConfigRC as the first item.
E.g. {foo = “bar”} will set vim.g.foo
to “bar” where
-the type of bar
in the resulting vimscript will be
-infered from the type of the value in the {name = value}
-pair.
{foo = "bar";}
will set vim.g.foo
to “bar”, where
+the type of bar
in the resulting Lua value will be
+inferred from the type of the value in the {name = value;}
+pair passed to the option.
Type: attribute set
@@ -7857,6 +7857,11 @@ attribute setDefault:
{ }
Example:
{
+ some_variable = 42;
+}
+
+
Declared by:
@@ -19015,6 +19020,41 @@ list of (null or package or one of “alpha-nvim”, “bufdelete-nvim”, “ca |
vim.options
+
+
+An attribute set containing vim options to be set
+as early as possible. If populated, this option will
+set vim options in the built luaConfigRC after basic
+and before pluginConfigs
DAG entries.
{foo = "bar";}
will set vim.o.foo
to “bar”, where
+the type of bar
in the resulting Lua value will be
+inferred from the type of the value in the{name = value;}
+pair passed to the option.
Type: +attribute set
+ +Default:
+{ }
Example:
{
+ visualbell = true;
+}
+
+
+Declared by:
+
+
+<nvf/modules/wrapper/rc/options.nix>
+
+ |
vim.pluginRC