rg --debug should output information about ignore files being read.

Currently it outputs something like the following, but it is not clear where the patterns are coming from:

% rg --no-config --debug foo
DEBUG|rg::args|src/args.rs:544: not reading config files because --no-config is present
DEBUG|grep_regex::literal|grep-regex/src/literal.rs:59: literal prefixes detected: Literals {

Is it possible to add an option -prune, to not explore sub-directories, when the current directory has been matched ? (like find -prune)

I think it would be a good idea to mention the tee command, probably somewhere in the "Cat, Less, Tail and Head" chapter

It’s probably straight-forward for some people using Docker more regularly than me, but it took a while to find out how to run truffleHog from Docker with my locally cloned repo:

cd /path/to/git_repo
docker run --rm -v `pwd`:/proj dxa4481/trufflehog file:///proj

• -v mounts the current working dir (`pwd`) to the /proj dir in the Docker container
• file:///proj refer

https://github.com/intel/hyperscan/blob/master/doc/dev-reference/chimera.rst says Currently only static library is supported for Chimera, so please use static build type when configure CMake build options.

Can someone help/guide me build dynamic lib

I hate regex too and would rather not use it but my coworker do and it makes code review very hard.

I wonder if there could be a simple way to use your awesome service to improve code review.

My first idea was to document code with a link to your service identifying uniquely the regex in the code.

What do you think about it?

I was bitten pretty hard (my fault!) by a subtle difference in eXtended mode's handling of spaces in character classes. I was expecting (except in a much more complicated context) (?x)[ ] to match a single space as it does with pcre2, but that does not seem to be the case (and doesn't seem to be documented?).

In PCRE2, (?x) enables spurious use of whitespace everywhere except in character c

Please describe the minimum necessary steps to reproduce this issue:

The example given in README for API some is not working as intended.
Link to example in REPL

const mm = require('micromatch');
// mm.some(list, patterns[, options]);

console.log(mm.some(['foo.js', 'bar.js'], ['*.js', '!foo.js']));
// true
console.log(mm.so

I assume the majority of users who come across sd are likely also using other popular Rust-based CLI tools like fd and rg:

• sharkdp/fd@app.rs#L70-L75
• [BurntSushi/ripgrep@app.rs#L1175-L1178](https://github.com/BurntSushi/ripgrep/blob/8ebc113847926922bb85fb5a01c175319fb1e8d4/src/app.rs#L1

Please pretend I attached a pull request which replaces all instances of regex2fat with REGEX2~1. Thank you.

A few restrictions are supported for “holes” already.
A search for alphanumeric characters and punctuation can be specified by a syntax which is slightly different from other filter possibilities.

I imagine that advanced filters could be specified directly after the match identifier.

• Character class
• Regular expression
• Predefi

Add a new demo

The following example should render as bold and italics at the same time:

***foobar***

Like this: foobar

However it is only rendered in bold style.