Conversation
When completions happen with a local justfile present, global recipes are ignored. All this does is allow for them to appear. A better strategy may be to consume the `-g|--global-justfile` argument and use that to inspire the autocomplete. However, since running `just <GLOBAL_RECIPE>` without the `-g` flag works, I think this may violate the best approach.
That does not work for me |
You are right, I forgot I had fallback on the justfile! It may be better to consume the |
If the preceding flag is `--global-justfile | -g`, the recipe completions will now list the global recipes. We do not need path checking since global file resolution is already implemented.
|
This should work better now. It aligns better with existing behaviours and the presence of the |
|
I switched to using Clap's dynamic completion engine in #3167. The new completion engine calls into the I created #2406 to track improvements to the new completion engine in one place. The new completion engine attempts to respect command line flags like |
When completions happen with a local justfile present, global recipes are ignored. All this does is allow for them to appear. A better strategy may be to consume the
-g|--global-justfileargument and use that to inspire the autocomplete. However, since runningjust <GLOBAL_RECIPE>without the-gflag works, I think this may violate the best approach.