We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#! nix-shell
#! nix
Of the many things nix-shell does, "entering an environment" and "wrapping an interpreted script" have absolutely nothing to do with each other.
nix-shell
In particular, the shebang feature is not limited to shell scripts.
It would greatly ease telling a story around Nix features (and making it discoverable) if independent features would have distinguishable names.
I imagine making it work for nix would require doing something involved to the top-level nix command.
nix
Therefore, a cheap alternative would be to introduce a dedicated alias such as nix-interpreter or nix-script.
nix-interpreter
nix-script
The text was updated successfully, but these errors were encountered:
Linked: #5189
Sorry, something went wrong.
This was fixed by #8327, right?
No branches or pull requests
Of the many things
nix-shell
does, "entering an environment" and "wrapping an interpreted script" have absolutely nothing to do with each other.In particular, the shebang feature is not limited to shell scripts.
It would greatly ease telling a story around Nix features (and making it discoverable) if independent features would have distinguishable names.
Alternatives
I imagine making it work for
nix
would require doing something involved to the top-levelnix
command.Therefore, a cheap alternative would be to introduce a dedicated alias such as
nix-interpreter
ornix-script
.The text was updated successfully, but these errors were encountered: