Skip to content
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

cabal sandbox init --sandbox<tab> creates sandbox named --list-options #3648

Closed
lspitzner opened this issue Jul 31, 2016 · 4 comments
Closed

Comments

@lspitzner
Copy link
Collaborator

There must be a more reliable approach to this whole bash-completion. seems way too easy to break at every corner.

@lspitzner
Copy link
Collaborator Author

my bash-completion is that of master branch (minus the new-build addition, which is irrelevant).

@0xmohit
Copy link
Contributor

0xmohit commented Aug 6, 2016

The culprit appears to be eval "${cmd[@]}" here.

Wondering if --dry-run should also be passed along.

@23Skidoo
Copy link
Member

23Skidoo commented Aug 6, 2016

The problem is that sandbox init and other subcommands don't support --list-options. I believe that if #1257 was implemented, bash completion would work as is.

@ezyang ezyang added this to the Obsoleted by nix-local-build milestone Aug 24, 2016
@gbaz
Copy link
Collaborator

gbaz commented Aug 28, 2021

closing as obsolete

@gbaz gbaz closed this as completed Aug 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants