-
Currently, `seafile-ignore.txt` only supports `*` and `?` wildcards. Furthermore, it works completely different from `.gitignore`.
The main problem is in uses of [`glib`'s glob pattern matching](ht…
-
## CVE-2024-4067 - Medium Severity Vulnerability
Vulnerable Libraries - micromatch-3.1.10.tgz, micromatch-4.0.2.tgz, micromatch-4.0.4.tgz, micromatch-2.3.11.tgz
micromatch-3.1.10.tgz
Glob matching…
-
I would like to match an output by it's port name and it's model name.
Something like:
```
output DP-1 'Acer Technologies Acer KG241 P 0x0000F372' mode 1920x1080@144Hz
```
Currently, one ca…
-
@split only specifies the names of output files via a matching glob. This is error prone and inflexible. Let the actual names be returned from the function.
-
Implement the KEYS command, which returns all the keys that match the provided pattern.
Reference: https://redis.io/docs/latest/commands/keys/
## Client-Server Spec:
Command File: ./internal/mo…
-
## Wanted feature
The `Operator` built from `Redis` could use `scan` to `list` entries matching the [glob-style pattern of redis](https://redis.io/commands/keys/).
## Real scene
There is a fu…
-
The two overloads of `Glob.Match` currently take `in ReadOnlySpan`, meaning that the text must be in UTF-16 format. Do we need to support matching directly against UTF-8?
-
Is there a plan to support string alternatives with curly braces, like `{foo,bar}program` matching `fooprogram` and `barprogram`?
To avoid code duplication in the matcher, I was thinking it might be …
-
e.g.
``` ruby
glob('spec/**/*_spec.rb') # glob instead of watch to prevent issues with strings
```
Technically, this could be done with a custom Watcher/"matcher", e.g.:
``` ruby
watch(glob('spec/…
-
## Summary
Recently, when running the exporter with a large configuration (i.e. around 3k entries), we saw a big heap allocation to store the state inside the FSM for glob matching. This issue is j…