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
Sometimes I issue commands that take a URL parameter and oftentimes I forget to explicitly quote the parameter, resulting in the message No matches for wildcard 'https://....'. See help \wildcards-globbing`.`
As far as I understand the documentation, this whole concept is there exclusively for files, making it a host-only solution. It would be super convenient if parameters that start with http:// or https:// (or other protocols) simply run until the next whitespace and do not try to interpret question marks, ampersands or asterisk characters.
The text was updated successfully, but these errors were encountered:
I'm using fish, version 3.7.1
Sometimes I issue commands that take a URL parameter and oftentimes I forget to explicitly quote the parameter, resulting in the message
No matches for wildcard 'https://....'. See help \
wildcards-globbing`.`As far as I understand the documentation, this whole concept is there exclusively for files, making it a host-only solution. It would be super convenient if parameters that start with http:// or https:// (or other protocols) simply run until the next whitespace and do not try to interpret question marks, ampersands or asterisk characters.
The text was updated successfully, but these errors were encountered: