You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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:
Bash is much more convenient:
Could there be room for a rethink here?
Output of "elvish -version"
0.21.0
Code of Conduct
The text was updated successfully, but these errors were encountered: