-
Notifications
You must be signed in to change notification settings - Fork 842
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
can't tab-complete to get filenames running stack exec
for tools
#832
Comments
You should be able to run That said, tab completion for |
So, I discovered https://github.com/commercialhaskell/stack/wiki/Shell-autocompletion now… that's nice enough, though I think it just allows completion for stack arguments. Better than not having that, though it isn't what I wanted here really. |
I'm having the same issue, #1343 seems to claim that this is working but I have only been able to autocomplete on options. |
@Cypher1 It will only complete to executables specified in your project. This is a tradeoff. Do we let the user complete to anything on the PATH (the one constructed when stack execing), or do we prioritize things from your project? I'm thinking I might have gone the wrong way here, thinking it makes more sense to have it search the PATH, and not return any results from PATH when the prefix is empty. What do y'all think? |
Thanks @mgsloan it seems that it was a stack 1.5 feature! Can this be closed now? |
Is that possible to complete filename after runghc? |
For example, if I use stack to install hlint, as in
stack build hlint
, then I must use stack to run it, and can't just dohlint
on its own. It would be ideal to not always needstack exec hlint
, but even if we accept that longer command, I can't tab-complete to get filenames then. So, this is far less ideal than pre-stack situation (but I want to stick to Stack generally, not go back to cabal install or system-level stuff for tools like this).The text was updated successfully, but these errors were encountered: