-
|
Below I copied an example from the docs about extending configurations: If I understand this correctly, # Apply initial configuration
initialConfig = (wrappers.wrapperModules.tmux.eval {
pkgs = pkgs;
plugins = [ pkgs.tmuxPlugins.onedark-theme ];
}).config;
# Extend with additional configuration
extendedConfig = initialConfig.eval { # <--(1)
clock24 = false;
}; # <--(2)
# Access the wrapper
actualPackage = extendedConfig.config.wrapper; # <--(3)
# Extend it again!
apackage = (actualPackage.eval {
vimVisualKeys = true;
modeKeys = "vi";
statusKeys = "vi";
}).config.wrapper;
# and again!
packageAgain = apackage.wrap {
prefix = "C-Space";
}; |
Beta Was this translation helpful? Give feedback.
Answered by
BirdeeHub
Nov 15, 2025
Replies: 1 comment 6 replies
-
|
You are correct. I wanted to show the full Which do you think is best? extendedModule, or apply? |
Beta Was this translation helpful? Give feedback.
6 replies
Answer selected by
zenoli
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You are correct. I wanted to show the full
.config.wrapperpath but theextendedConfigname might be a bit confusing when its actually the raw result of evalModulesWhich do you think is best? extendedModule, or apply?