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
Possible Future Work? #4
Comments
|
Broke these out into separate issues to have a little more room to focus on each. Edited this post down to reflect new locations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are some things I would like for it to do:
1. better support for bashFinished in #5alias
definitions, where currently itdoes not handle them at all.
2. better support for programs which call other programs, like
See #6xargs «cmd»
. This one is not a principled solution, but I thinkan investment in to handling common "higher order" programs like
this would pay off well.
3. development of a "strict mode" where the PATH is unset, to improveSee #9the guarantee
4. have a "traced execution" model where executing speciallySee #9instrumented "resholved" scripts record any programs executed which
are not in their Nix closure. This indicates a scope leak and
resolution failure.
5. a buildInputs setup hook, which automatically resholves all of the outputs of a Nix build.See #8what do you think about these things?
The text was updated successfully, but these errors were encountered: