Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
wildcard matching does not work with zsh (ohmyzsh specifically)
See original GitHub issuespecifically ../prefix* and .../folder/** are not working
neither other wildcards seem to work.
same commands on the same machine working fine after switching to bash
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:10 (5 by maintainers)
Top Results From Across the Web
scp wildcard not working in zsh - Unix & Linux Stack Exchange
One strange thing, when I try to scp with a * wildcard, it does not work, and I have to drop into bash....
Read more >shell - ZSH doesn't identify "*" as "all files" - Stack Overflow
It's the difference between zsh and bash. zsh never will run a command that contains wildcard pattern that doesn't match existing files.
Read more >Using wildcards in commands with zsh - Super User
The quickest is to enclose the globbing characters with quotes. ... This will prevent ZSH to print an error when no match can...
Read more >A common mistake involving wildcards and the find command
As is I just have a grep wrapping shell script to give it some sane defaults which works fairly well.
Read more >Globbing wildcard characters with zsh - TechRepublic
Vincent Danen explains globbing with wildcard characters, and how using globbing in the z shell (zsh) yields powerful results.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
While suspecting this is a zsh quirk I could not find a solution/cause.
Of course right after filing the issue I found the culprit.
This is a zsh issue. zsh wants to expand * so have to escape *s…
e.g.
.../folder/\*\*Do you have any zsh environment variables set?