Skip to content

Conversation

@jtmonroe
Copy link

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.

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.
@laniakea64
Copy link
Contributor

running just <GLOBAL_RECIPE> without the -g flag works,

That does not work for me

@jtmonroe
Copy link
Author

jtmonroe commented Dec 10, 2025

running just <GLOBAL_RECIPE> without the -g flag works,

That does not work for me

You are right, I forgot I had fallback on the justfile! It may be better to consume the -g argument then. Thoughts?

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.
@jtmonroe
Copy link
Author

This should work better now. It aligns better with existing behaviours and the presence of the --global-justfile | -g flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants