[worksonmine]

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?

[dataflow]

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

To be clear, I was not suggesting an alias for grep, but for a hypothetical alternate ripgrep that searches everything by default but has a flag to skip ignored files. Something like

  alias rgi='rg --skip-ignored'

or whatever. Or if it came with a short flag that could work too, so you could use it without an alias easily.

> Like in your case, `alias rg='rg -u'`, now how do you turn it off?

You don't use the same name, you make a new alias. Like rgi or something. Bonus point is you find out immediately if it's missing.

[worksonmine]

I use very short aliases with fallbacks to standard tools if ripgrep/fd/bat/... isn't installed. For my use searching files in `.gitignore` is useless 9/10 times, why would I want that to be default?

> Or if it came with a short flag that could work too

It does, `-.` for hidden and `-u` for hidden + ignored.

[dataflow]

> It does, `-.` for hidden and `-u` for hidden + ignored

I'm not sure you understood what I wrote? Those are opt-out. The entire discussion is about opt-in.

[worksonmine]

> Those are opt-out. The entire discussion is about opt-in.

Depends on your perspective, to me you have them flipped, and enabling them is "opt-in", i.e: "now I would like to see the hidden files please".

But I don't think I misunderstood you. You're telling me I should prefer hidden files to be the default, and I disagree and give my arguments. It's not more complicated than that.

To me rg only follows the same principle as the rest of my tools, fd requires `-H/--hidden`, ls `-a` or `-A` and so on. It is a big reason to why I prefer rg and fd over grep and find. Which brings us back to your first comment:

>> You started using it because it had that capability I imagine, not because it is the default.

[unop]

`\rg foo` or `command rg foo`