config.flags: keys and values are space separated by default

[nouritsu]

I am trying to write a wrapperModule for ghostty terminal.

Ghostty uses a simple key value config like -

language = de
font-family = "foo"
font-family = "bar"

It also supports the keys

config-file = /path/to/config # duh
config-default-files = <true/false> # if false, do not load configs from $XDG_CONFIG_HOME

These keys (and others) can also be passed in via the command line as

$ ghostty --config-default-files=false --config-file=/path/to/config

My implementation uses config.constructFiles to generate a file and pass config.flags to load the generated file.

When I try to create a wrapped package using this wrapper, ghostty launches but has CLI flag errors. Since the config.flags are translated into --config-default-files= true rather than --config-default-files=true, ghostty interprets this as separate flags --config-default-files= and true. This results in error error: cli:2:true: invalid field

Perhaps an additional check should be added which does not space separate the options if the key ends with a =? If there is another way to achieve flags which do not get space separated, I will proceed with PR #393 .

[BirdeeHub]

https://birdeehub.github.io/nix-wrapper-modules/modules/makeWrapper.html#flagseparator

^ sets the default

You can set it per item too!

https://birdeehub.github.io/nix-wrapper-modules/modules/makeWrapper.html#flagsnamesep

[nouritsu]

Neat! I'm sorry I am not too familiar with reading nix and rg flags was not helping TT