Single asterisk behaviour
See original GitHub issueI seem to get odd results when using the single asterisk wildcard *
. For example, let’s take the following string:
HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Shockwave 12
The pattern *ave 12
matches, as expected, but *ave*2
(which uses 2 asterisks) does not, neither doe Shock* 12
(which uses a single asterisk, but not as the first character in the pattern).
Is this the expected behaviour? If so, what’s the rationale behind it?
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Questions about Asterisk's behavior
Hi All, I'm developing a propreitary codec and I want to use Asterisk as a call manager. Asterisk itself does not need to...
Read more >Odd behavior with voice-to-text after single asterisks
If I tap in front of the bullet point and try voice-to-text again, it types the first letter of the first spoken word,...
Read more >Confused about the behavior of asterisk in ls command
The windows dir command would just show me the directories matching /etc/rc* how can I get this behavior from ls (without using the...
Read more >Procedure of the survey: Q = Question. Single asterisk
Single asterisk : multiple-answers were possible. Explicit behaviour could be chosen by the variables horn, headlight flasher, hand gesture and direct indicator.
Read more >What does a bare asterisk do in a Python parameter list ...
The behaviour for the single asterisk derives from PEP-3102 . Quoting the related section: The second syntactical change is to allow the ...
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 FreeTop 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
Top GitHub Comments
@cocowalla - this is now fixed if you upgrade to: https://www.nuget.org/packages/DotNet.Glob/1.6.0
Ok - have replicated this bug. Will fix in next release.