You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently discovered that nix-colors comes with a schemeToYAML helper function. This is a helpful function to manage my wezterm colorscheme. Docs to Wezterm load_base16_scheme
For context: this is how I configured wezterm
{inputs,lib,config,
...
}: letcfg=config.myHomeModules.wezterm;# generate a YAML file for wezterm to generate the colorschemepathToScheme=builtins.toFile"wezterm-base16.yaml"(inputs.nix-colors.lib.schemeToYAMLconfig.colorScheme);in{options.myHomeModules.wezterm={enable=lib.mkEnableOption"enables wezterm"//{default=false;};};config=lib.mkIfcfg.enable{programs={wezterm={enable=true;extraConfig='' -- load the base16 scheme from the path local colors, _ = wezterm.color.load_base16_scheme("${pathToScheme}") return { -- ## COLORSCHEME ## colors = colors, -- other config } '';};};};}
My question is, can we keep the utils? If that's out of the question, can you suggest an alternative method? Thank you.
Awesome tool btw 💯
The text was updated successfully, but these errors were encountered:
I recently discovered that
nix-colors
comes with aschemeToYAML
helper function. This is a helpful function to manage my wezterm colorscheme. Docs to Wezterm load_base16_schemeFor context: this is how I configured wezterm
My question is, can we keep the utils? If that's out of the question, can you suggest an alternative method? Thank you.
Awesome tool btw 💯
The text was updated successfully, but these errors were encountered: