stylix: improve Bash expression

[trueNAHO]

Addresses: #317 (comment)

[danth]

I suspect there are other places throughout various modules also in need of attention.

There are a few functions in lib which could be helpful when substituting data from Nix into a Bash script:

• lib.escapeShellArg
• lib.escapeShellArgs
• lib.toShellVar
• lib.toShellVars
• lib.toGNUCommandLineShell

See their definitions here and here for usage instructions.

Using pkgs.writeShellApplication rather than pkgs.writeShellScript or pkgs.writeShellScriptBin is also preferable, since it runs the generated script through ShellCheck.

[danth]

Wait - this is a pull request, not an issue. Oh well.

[danth]

lib.escapeShellArg is preferable since it handles the case where the string to be substituted contains a quotation mark.

[trueNAHO]

lib.escapeShellArg is preferable since it handles the case where the string to be substituted contains a quotation mark.

NixOS/nixpkgs#16973 resolved my confusion around ${lib.escapeShellArg pkgs.hello.pname} being preferred over "${pkgs.hello.pname}" or '${pkgs.hello.pname}':

• nixos/zsh: use `escapeShellArg' for shell aliases NixOS/nixpkgs#47471
• nixos/bash: Use escapeShellArg for shell aliases NixOS/nixpkgs#47984

[trueNAHO]

Potentially closes: #324.

[danth]

I see escapeShellArg being necessary for cfg.image since the file path is user-defined and could potentially contain any character.

cfg.polarity is enforced by the type system to only ever be one of light, dark or either, so we don't actually need quotation marks at all in that case since it will always be a single word.

[trueNAHO]

I see escapeShellArg being necessary for cfg.image since the file path is user-defined and could potentially contain any character.

Agreed. Unfortunately, despite my understanding of lib.escapeShellArg (#318 (comment)), I do not understand why f9b9bc7 resolved the mentioned issue. Do you know what the proper fix should be?

cfg.polarity is enforced by the type system to only ever be one of light, dark or either, so we don't actually need quotation marks at all in that case since it will always be a single word.

True. However, my Bash heart aches seeing a variable not being double quoted, as the cfg.polarity values may expand to multiple words in the future.

[danth]

lib.escapeShellArg arg uses toString arg, which behaves slightly differently to the ${arg} we were using previously.

https://github.com/NixOS/nixpkgs/blob/4f7b6bb6943837310c439a6d110f871da255e85e/lib/strings.nix#L454

Perhaps lib.escapeShellArg "${arg}" would get the proper result.