can't tab-complete to get filenames running stack exec for tools

[wolftune]

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 do hlint on its own. It would be ideal to not always need stack 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).

[borsboom]

You should be able to run stack install hlint, which will put hlint in ~/.local/bin (which you should add to your PATH). Then you can just use hlint normally, and this is the preferred way to set up such tools.

That said, tab completion for stack exec would be really nice. optparse-applicative has some support for custom completors, and it might be possible to use that to pass completion through to the command being execed, but I have no idea how difficult that would be. A pull request would be most welcome!

[wolftune]

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.

[Cypher1]

I'm having the same issue, #1343 seems to claim that this is working but I have only been able to autocomplete on options.

[mgsloan]

@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?

[Cypher1]

Thanks @mgsloan it seems that it was a stack 1.5 feature!

Can this be closed now?

[soulomoon]

Is that possible to complete filename after runghc?