Was the file in a .gitignore by any chance? I've got my home folder in git to keep track of dot/config files and that always catches me out. Really dislike it defaulting to that ignoring files that are ignored by git.

▲

hrmtst93837 5 hours ago | parent | next [-]

In a repo, sure. On your own fs it feels like a footgun and every tool copies the behavior a little differently, which means you stop trusting the results and start wondering which files got skipped.

▲

worksonmine 8 hours ago | parent | prev [-]

> Really dislike it defaulting to that ignoring files that are ignored by git.

It's the reason I started using it. Got sick of grep returning results from node_modules etc.

▲

dataflow 7 hours ago | parent [-]

You started using it because it had that capability I imagine, not because it is the default. You could easily just alias a command with the right flag if the capability was opt-in.

▲

worksonmine 6 hours ago | parent [-]

No, because it was default.

> You could easily just alias a command with the right flag if the capability was opt-in.

I tried a search to make grep ignore .gitignore because `--exclude=...` got tedious and there was ripgrep to answer my prayers.

Maintaining an alias would be more work than just `rg 'regex' .venv` (which is tab-completed after `.v`) the few times I'm looking for something in there. I like to keep my aliases clean and not have to use rg-all to turn off the setting I turned on. Like in your case, `alias rg='rg -u'`, now how do you turn it off?

	▲	unop 21 minutes ago \| parent [-]
		`\rg foo` or `command rg foo`