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

"Wildcard has no match" exception is unergonomic #1852

Open
1 task done
tesujimath opened this issue Nov 4, 2024 · 0 comments
Open
1 task done

"Wildcard has no match" exception is unergonomic #1852

tesujimath opened this issue Nov 4, 2024 · 0 comments

Comments

@tesujimath
Copy link

What new feature should Elvish have?

I see that the exception throwing by default when wildcards have no match was added some time ago in response to a real issue.

However, the behaviour we have now is rather awkward. For example, when wanting to delete any file matching some set of wildcards:

> ls
a  ab  abc
> rm -f ab* bc*
Exception: wildcard has no match
  [tty 38]:1:11-13: rm -f ab* bc*
> ls
a  ab  abc

> rm -f ab*[nomatch-ok] bc*[nomatch-ok]
> ls
a

Bash is much more convenient:

> bash
$ ls
a  ab  abc
$ rm -f ab* bc*
$ ls
a

Could there be room for a rethink here?

Output of "elvish -version"

0.21.0

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ❓Triage
Development

No branches or pull requests

1 participant