3 ms·

I did try rip "grep". rg "^SECRET" Find nothing. Try to contact someone who is asleep for half an hour, then they tell me they put it in there. grep

I did try rip "grep". rg "^SECRET" Find nothing. Try to contact someone who is asleep for half an hour, then they tell me they put it in there. grep -r "^SECRET" . yep, it is there, in an .env file. "Uhh yeah sorry I was using ripgrep and it doesn't search hidden files by default but it has a flag for it" "you wut?" "nevermind, thanks bye." <- that is ripgrep. Maybe we got off on the wrong foot. Anyway thanks for listing all the tools you're great.

StavrosK 8y ago
It does search hidden files, it doesn't search gitignored files. Why are you assuming it's identical to grep?
- nurettin 8y ago
  Have you installed it? nurettin@ ~ () $ mkdir test nurettin@ ~ () $ echo "TEST SOMETHING" > test/.env nurettin@ ~ () $ cd test nurettin@ ~/test () $ rg "TEST" Why I don't know, because it has grep in the name? Do you now realize where the confusion might be lying?
  - burntsushi 8y ago
    This is part the whole point of ripgrep. If you don't want it to do smart filtering, then you either alias `rg="rg -uu"` or just use grep if it's fast enough for you. Some people might miss this, yes. That's why it's mentioned in the first couple sentences of the man page.
    - nurettin 8y ago
      RTFM is an important thing we remind to eachother in order to reach for our own knowledge instead of relying upon others to give it to us. And yes, this most important bit of information is in the man page and the help text, but not at the top of the page people who came to actually download the tool will look first. Which is `https://github.com/burntsushi/ripgrep` https://github.com/burntsushi/ripgrep` .
      - burntsushi 8y ago
        Sure. I'm just trying to justify the actual behavior of ripgrep (which you are poo-pooing) by saying that it is at the very heart of what ripgrep is about. It's not some weird corner case that's supposed to bite you. It is its raison d'etre. The README mentions that it respects gitignore rules. I just updated it to include hidden/binary files. Thanks.
        nurettin 8y ago
        Poopoo sounds really funny. Haha. Still pretty sure grep is a confusing name for something which doesn't grep "because of smart filtering" <- that is just your rules, your way, whatever your heart desires, whatever you want to call "smart". This is not about Rust anymore (which I actually like) This is a point you seem to be ignoring in favor of opinions such as "this is the reason for this tool to exist" <- again, your way, your rules. It is circular to name something after something else, then making it act totally different, whatever you want it to do, changing output format, filtering files, then responding to confused people saying hey this is what I wanted. Yes it is. It doesn't change a thing. Thanks for the readme update.
        burntsushi 8y ago
        If I named it something totally different, people might say, "why didn't you just call it a grep, because that's basically what it is." Language and perspective is funny like that. > whatever you want to call "smart". Related: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#posix4ever https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#pos...
        unionpivo 8y ago
        I like rust, and I generally like this trend of rewrites, but I will have to support systems with old grep for a long time jet. So in cases where the new "improved" tool departs from old standard [1], it just add one more thing, that can screw you, especially if it comes over as a replacement. grepping for settings in dot files is not exactly a corner case for me. And setting up aliases to me it's similar. It will just mess with you on systems when you don't have them set up. I guess it depends what you primary use case is. I can see how a developer that spends most of his time on his desktop/laptop command line would find this good default. [1] And that it does so silently. If something fails hard or errors on the side of not filtering, its less of an issue.
- iruoy 8y ago
  From https://github.com/BurntSushi/ripgrep https://github.com/BurntSushi/ripgrep > Like other tools specialized to code search, ripgrep defaults to recursive directory search and won't search files ignored by your .gitignore files. It also ignores hidden and binary files by default.

StavrosK 8y ago

It does search hidden files, it doesn't search gitignored files. Why are you assuming it's identical to grep?

nurettin 8y ago
Have you installed it? nurettin@ ~ () $ mkdir test nurettin@ ~ () $ echo "TEST SOMETHING" > test/.env nurettin@ ~ () $ cd test nurettin@ ~/test () $ rg "TEST" Why I don't know, because it has grep in the name? Do you now realize where the confusion might be lying?
- burntsushi 8y ago
  This is part the whole point of ripgrep. If you don't want it to do smart filtering, then you either alias `rg="rg -uu"` or just use grep if it's fast enough for you. Some people might miss this, yes. That's why it's mentioned in the first couple sentences of the man page.
  - nurettin 8y ago
    RTFM is an important thing we remind to eachother in order to reach for our own knowledge instead of relying upon others to give it to us. And yes, this most important bit of information is in the man page and the help text, but not at the top of the page people who came to actually download the tool will look first. Which is `https://github.com/burntsushi/ripgrep` https://github.com/burntsushi/ripgrep` .
    - burntsushi 8y ago
      Sure. I'm just trying to justify the actual behavior of ripgrep (which you are poo-pooing) by saying that it is at the very heart of what ripgrep is about. It's not some weird corner case that's supposed to bite you. It is its raison d'etre. The README mentions that it respects gitignore rules. I just updated it to include hidden/binary files. Thanks.
      - nurettin 8y ago
        Poopoo sounds really funny. Haha. Still pretty sure grep is a confusing name for something which doesn't grep "because of smart filtering" <- that is just your rules, your way, whatever your heart desires, whatever you want to call "smart". This is not about Rust anymore (which I actually like) This is a point you seem to be ignoring in favor of opinions such as "this is the reason for this tool to exist" <- again, your way, your rules. It is circular to name something after something else, then making it act totally different, whatever you want it to do, changing output format, filtering files, then responding to confused people saying hey this is what I wanted. Yes it is. It doesn't change a thing. Thanks for the readme update.
        burntsushi 8y ago
        If I named it something totally different, people might say, "why didn't you just call it a grep, because that's basically what it is." Language and perspective is funny like that. > whatever you want to call "smart". Related: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#posix4ever https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#pos...
        unionpivo 8y ago
        I like rust, and I generally like this trend of rewrites, but I will have to support systems with old grep for a long time jet. So in cases where the new "improved" tool departs from old standard [1], it just add one more thing, that can screw you, especially if it comes over as a replacement. grepping for settings in dot files is not exactly a corner case for me. And setting up aliases to me it's similar. It will just mess with you on systems when you don't have them set up. I guess it depends what you primary use case is. I can see how a developer that spends most of his time on his desktop/laptop command line would find this good default. [1] And that it does so silently. If something fails hard or errors on the side of not filtering, its less of an issue.
iruoy 8y ago
From https://github.com/BurntSushi/ripgrep https://github.com/BurntSushi/ripgrep > Like other tools specialized to code search, ripgrep defaults to recursive directory search and won't search files ignored by your .gitignore files. It also ignores hidden and binary files by default.