To use these options modify your home.nix such that it has the format
{ pkgs, ... }:
let
nurNoPkgs = import <nur> { pkgs = null; };
in
{
import = [ nurNoPkgs.repos.rycee.hmModules.name … ];
# …
}
where name is
emacs-init
for options under programs.emacs.init, or
theme-base16
for options under theme.base16 and
enableBase16Theme options for various
Home Manager modules.
_module.argsAdditional arguments passed to each module in addition to ones
like lib, config,
and pkgs, modulesPath.
This option is also available to all submodules. Submodules do not
inherit args from their parent module, nor do they provide args to
their parent module or sibling submodules. The sole exception to
this is the argument name which is provided by
parent modules to a submodule and contains the attribute name
the submodule is bound to, or a unique generated name if it is
not bound to an attribute.
Some arguments are already passed by default, of which the following cannot be changed with this option:
lib: The nixpkgs library.config: The results of all options after merging the values from all modules together.options: The options declared in all modules.specialArgs: The specialArgs argument passed to evalModules.All attributes of specialArgs
Whereas option values can generally depend on other option values
thanks to laziness, this does not apply to imports, which
must be computed statically before anything else.
For this reason, callers of the module system can provide specialArgs
which are available during import resolution.
For NixOS, specialArgs includes
modulesPath, which allows you to import
extra modules from the nixpkgs package tree without having to
somehow make the module aware of the location of the
nixpkgs or NixOS directories.
{ modulesPath, ... }: {
imports = [
(modulesPath + "/profiles/minimal.nix")
];
}
For NixOS, the default value for this option includes at least this argument:
pkgs: The nixpkgs package set according to
the nixpkgs.pkgs option.
Type: lazy attribute set of raw value
Declared by:
<nur-rycee/lib/modules.nix>
|
gtk.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/gtk.nix>
|
programs.bat.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/bat.nix>
|
programs.emacs.enableBase16ThemeBuild Base16 theme for Emacs. Note, this does not actually enable the theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/emacs.nix>
|
programs.emacs.init.enableWhether to enable Emacs configuration.
Type: boolean
Default: false
Example: true
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.packageQuickstartWhether to enable package-quickstart. This will make sure that
package.el is activated and all autoloads are
available.
If disabled you can save quite a few milliseconds on the startup time,
but you will most likely have to tweak the command
option of various packages.
As an example, running (emacs-init-time) on an Emacs
configuration with this option enabled reported ~300ms. Disabling the
option dropped the init time to ~200ms.
Type: boolean
Default: true
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.earlyInitConfiguration lines to add in early-init.el.
Type: strings concatenated with "\n"
Default: ""
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.postludeConfiguration lines to add in the end of
init.el.
Type: strings concatenated with "\n"
Default: ""
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.preludeConfiguration lines to add in the beginning of
init.el.
Type: strings concatenated with "\n"
Default: ""
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.recommendedGcSettingsWhether to enable recommended garbage collection settings.
This will reduce garbage collection frequency during startup and while the minibuffer is active.
Type: boolean
Default: false
Example: true
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.startupTimerWhether to enable Emacs startup duration timer.
Type: boolean
Default: false
Example: true
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackageAttribute set of use-package configurations.
Type: attribute set of (submodule)
Default: { }
Example:
{
dhall-mode = {
mode = [ ''"\\.dhall\\'"'' ];
};
}
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.enableWhether to enable Emacs package ‹name›.
Type: boolean
Default: false
Example: true
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.packageThe package to use for this module. Either the package name within the Emacs package set or a function taking the Emacs package set and returning a package.
Type: name of package or (function from epkgs to package)
Default: "‹name›"
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.afterThe entries to use for :after.
Type: list of string
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.bindThe entries to use for :bind.
Type: attribute set of string
Default: { }
Example:
{
"M-<down>" = "drag-stuff-down";
"M-<up>" = "drag-stuff-up";
}Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.bindKeyMapThe entries to use for :bind-keymap.
Type: attribute set of string
Default: { }
Example:
{
"C-c p" = "projectile-command-map";
}Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.bindLocalThe entries to use for local keymaps in :bind.
Type: attribute set of attribute set of string
Default: { }
Example:
{
helm-command-map = {
"C-c h" = "helm-execute-persistent-action";
};
}Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.chordsThe entries to use for :chords.
Type: attribute set of string
Default: { }
Example:
{
jj = "ace-jump-char-mode";
jk = "ace-jump-word-mode";
}Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.commandThe entries to use for :commands.
Type: list of string
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.configCode to place in the :config section.
Type: strings concatenated with "\n"
Default: ""
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.deferThe :defer setting.
Type: boolean or positive integer, meaning >0
Default: false
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.definesThe entries to use for :defines.
Type: list of string
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.demandThe :demand setting.
Type: boolean
Default: false
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.diminishThe entries to use for :diminish.
Type: list of string
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.earlyInitLines to add to programs.emacs.init.earlyInit when
this package is enabled.
Note, the package is not automatically loaded so you will have to
require the necessary features yourself.
Type: strings concatenated with "\n"
Default: ""
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.extraConfigAdditional lines to place in the use-package configuration.
Type: strings concatenated with "\n"
Default: ""
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.extraPackagesExtra packages to add to home.packages.
Type: list of package
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.functionsThe entries to use for :functions.
Type: list of string
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.hookThe entries to use for :hook.
Type: list of string
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.initThe entries to use for :init.
Type: strings concatenated with "\n"
Default: ""
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackage.<name>.modeThe entries to use for :mode.
Type: list of string
Default: [ ]
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.emacs.init.usePackageVerboseWhether to enable verbose use-package mode.
Type: boolean
Default: false
Example: true
Declared by:
<nur-rycee/emacs-init.nix>
|
programs.gnome-terminal.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/gnome-terminal.nix>
|
programs.jq.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/jq.nix>
|
programs.rofi.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/rofi.nix>
|
services.dunst.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/dunst.nix>
|
services.polybar.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/polybar.nix>
|
services.screen-locker.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/screen-locker.nix>
|
services.xscreensaver.enableBase16ThemeEnable Base16 theme.
Type: boolean
Default: true
Example: false
Declared by:
<nur-rycee/theme-base16/xscreensaver.nix>
|
theme.base16.colors.base00Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base01Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base02Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base03Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base04Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base05Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base06Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base07Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base08Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base09Color value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base0AColor value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base0BColor value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base0CColor value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base0DColor value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base0EColor value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.colors.base0FColor value. Either a hexadecimal or decimal RGB triplet must be given. If a hexadecimal triplet is given then the decimal triplet is automatically populated, and vice versa. That is, the example could be equivalently written
{ hex.r = "b1"; hex.g = "2a"; hex.b = "2a"; }
And
"red dec: ${dec.r}, red hex: ${hex.r}, rgb hex: ${hex.rgb}"
would expand to “red dec: 177, red hex: b1, rgb hex: b12a2a”.
Type: submodule
Example:
{
dec = {
b = 42;
g = 42;
r = 177;
};
}Declared by:
<nur-rycee/theme-base16>
|
theme.base16.kindWhether theme is dark or light. The default value is determined by a basic heuristic, if an incorrect value is found then this option must be set explicitly.
Type: one of "dark", "light"
Default:
"light", if sum of RGB components of base00 color ≥ 382, "dark", otherwise
Example: "dark"
Declared by:
<nur-rycee/theme-base16>
|
theme.base16.nameThe theme name.
Type: string
Example: "My-Fine-Theme"
Declared by:
<nur-rycee/theme-base16>
|