-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
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
Invoke nix
on unsupported/unknown subcommands
#109
Comments
nix
on unknown subcommandsnix
on unsupported/unknown subcommands
I have pondered this for quite a while and I certainly want a good solution for this. Sadly I see a huge footgun potential here. nom takes nix from the PATH. In your case with the alias you are actually fine, but imagine someone using a symlink nix -> nom, then nom will recusively call itself. |
Ah, well. You actually don't set nix -> nom. |
I agree that symlinking In some cases ( Whether someone wants to If I ever have a problem with the alias, I just remove it and run |
Point taken. I had this on my radar anyway and will look into it. |
@lorenzleutgeb you can have a look at my code in #108 to create your own aliases. It's not 100% battle-tested but it's a starting point. |
Thanks @zeorin, that's super cool to see, but way too involved for me at the moment. |
I did
alias nix=nom
, and was very pleased with my newnix build
experience. Then, I wanted to runnix repl
, and was frustrated thatnom
does not "forward" this command tonix
transparently, i.e., it did not invokenix repl
.As long as you don't support all
nix
subcommands, please consider to just invokenix
: The commandnom foobar
should invokenix foobar
.In the meantime, I'll be using this workaround via Home Manager:
(and
alias nix=nix-nom
)The text was updated successfully, but these errors were encountered: