Bash Completion Script

[graemeg]

Hi @andrewd207 ,

Following on from the issue discussion: #8 (comment)

The current script already works really well. 👏 I haven't actually looked into detail how it works - or any bash completion script for that matter. But maybe what our one could do (if possible) is call 'pasbuild resolve' and parse all the possible profiles, modules and plug-ins detected by pasbuild. Then those could be presented as arguments for the -p and -m too.

Like I say, no idea how those scripts work, but if possible, that should make it more "context aware"... depending on which project you are in, the options for -p and -m will differ.

[andrewd207]

Hi @graemeg , for the -m option it's already filtered by

_pasbuild_goal_supports_module() {
    case "$1" in
        compile|resolve|dependency-tree|install) return 0 ;;
        *) return 1 ;;
    esac
}

I'm seeing that at some point that list got shortened. It was supposed to be "compile|resolve|dependency-tree|install|clean|test|test|compile|process-resources|process-resources". AI is great but also stupid sometimes.

I think -p just always works for everything. Internally it's already calling pasbuild resolve to get lists of modules and if you choose one like pasbuild compile -m fpgui-framework -p <tab> it will suggest agg debug freetype macos memleak profiler release unix windows

Not a big deal but pasbuild clean doesn't need -p option but it will still suggest it. Things like that.

Again, any new options need updating in the bash script too. The 'compile' option is in 3 places. Two Lists about goals and one about supporting the --m option.