The spec says:

If a client has access to environment variables, several standard ones exist to specify the language in which a client should operate. If not, then clients MUST make reasonable assumptions based on the information provided by the environment in which they operate (e.g. consulting navigator.languages in a browser, etc.).

Windows systems do have environment variables, but the

Is your feature request related to a problem? Please describe.

# build default.nix
nix-build -E 'with import <nixpkgs> {} ; callPackage ./default.nix {}'

this line things of nixpkgs> as a variable, but it actually should stay `.

Describe the solution you'd like

Best we to escapt <nixpkgs> some how.

Describe alternatives you've considered

currentl

To simplify the installation of cheat & cheatsheets, I created docker-cheat which packages both projects in a single 9 MB docker image. As it may be useful to others as well, I went ahead and linked the project here - specifically from the 'Related Projects' and ['Installing'](https://github.com/che