Skip to content
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

Add option to allow empty wildcard #1482

ghost opened this issue May 28, 2014 · 1 comment

Add option to allow empty wildcard #1482

ghost opened this issue May 28, 2014 · 1 comment


Copy link

ghost commented May 28, 2014

For example, * would return no arguments if the working directory were empty, */ if it contained no subdirectories, etc. It would either be a shell option or a separate syntax.

This is useful for scripting.

@ridiculousfish ridiculousfish added this to the fish-tank milestone Oct 3, 2014
Copy link

lilyball commented Oct 14, 2014

cab115c changes unmatched wildcard behavior to allow the job to continue running. Wildcards used interactively will still print an error, but the job will proceed and the wildcard will expand to zero arguments. Wildcards used inside scripts or functions will not print an error at all. In both cases, the wildcard expansion will set $status to 124, though this will nearly always get subsequently modified by the job itself.

@zanchey zanchey modified the milestones: next-minor, fish-tank Oct 14, 2014
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

4 participants