rg doesn't search in .sh and .cmd files unless I use "--hiden"?

[tawmoto]

Hi,

I have 2 files, package.sh and package.cmd, seems that rg ignores them unless I use --hidden parameter, altough the files are not hidden.
This means I always have to search with "--hidden", otherwise I don't get the proper results?

thanks

[BurntSushi]

It is unclear to me whether you're aware of the extent of ripgrep's automatic filtering. In particular, you only mention hidden files as something that could be filtered out, but ripgrep will filter out other things as well. From the second sentence of the README:

By default, ripgrep will respect gitignore rules and automatically skip hidden files/directories and binary files.

The user guide also has a section on automatic filtering.

I have 2 files, package.sh and package.cmd, seems that rg ignores them unless I use --hidden parameter, altough the files are not hidden.

Help me help you. Don't tell, show. Here's how to do it.

This means I always have to search with "--hidden", otherwise I don't get the proper results?

If some files are correctly being filtered out but you want to include them without passing a switch every time, then you're of course able to whitelist files.

[tawmoto]

Thank you for taking the time to explain in detail.
I am a long time linux grep user, but newbie with rg and TBH, I expected to behave similarly, because linux grep is kinda the original one.

I have to admit, I almost never read lengthy README for my trivial tools. In 15 years, I’ve never even looked at grep’s documentation - if it even has one. :-)

Thank you again for this nice tool.

[BurntSushi]

GNU grep certainly has a very lengthy manual itself. See info grep. Both GNU grep and ripgrep have many features. But ripgrep does add a few more that take up more surface area. Particularly its support for filtering is a fair bit more sophisticated than GNU grep.

I expected to behave similarly

Yes. You aren't the first. This is why ripgrep's automatic filtering is mentioned at the top of the man page, the README, the github description and even the -h and --help output. This is put at the top of each of these things precisely so that you don't need to read a "lengthy" manual to discover this behavior of ripgrep. ripgrep's automatic filtering is its defining feature, and it inherits this tradition from tools like ack and ag (the silver searcher).

See also: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#posix4ever