Code Monkey home page Code Monkey logo

Comments (5)

BurntSushi avatar BurntSushi commented on May 18, 2024

Why not just whitelist the files you want to search in your ~/.rgignore? e.g., !a*.

(I think I had the same problem as you, so I just put !* in my $HOME/.rgignore, which whitelists anything that would otherwise be ignored by $HOME/.gitignore.)

from ripgrep.

kaushalmodi avatar kaushalmodi commented on May 18, 2024

Before whitelisting:

km²~/temp/:proj> rg foo --debug                                                                                                                                                                      09/24 1:26am
DEBUG:grep::search: regex ast:
Literal {
    chars: [
        'f',
        'o',
        'o'
    ],
    casei: false
}
DEBUG:grep::literals: literal prefixes detected: Literals { lits: [Complete(foo)], limit_size: 250, limit_class: 10 }
DEBUG:rg::ignore: ./SOMEPRJ/abc ignored by Pattern { from: "/home/kmodi/.gitignore", original: "a*", pat: "**/a*", whitelist: false, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/ghi ignored by Pattern { from: "/home/kmodi/.gitignore", original: "g*", pat: "**/g*", whitelist: false, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/.rgignore ignored because it is hidden
No files were searched, which means ripgrep probably applied a filter you didn't expect. Try running again with --debug.

After whitelisting by add !* to the very top of ~/.rgignore:

km²~/temp/:proj> rg foo --debug                                                                                                                                                                      09/24 1:31am
DEBUG:grep::search: regex ast:
Literal {
    chars: [
        'f',
        'o',
        'o'
    ],
    casei: false
}
DEBUG:grep::literals: literal prefixes detected: Literals { lits: [Complete(foo)], limit_size: 250, limit_class: 10 }
DEBUG:rg::ignore: ./SOMEPRJ whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/abc whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/abc/def whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/abc/def/XXX whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/abc/def/XXX/YYY whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/abc/def/XXX/YYY/bar whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/ghi whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/ghi/XXX whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/ghi/XXX/YYY whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/ghi/XXX/YYY/bar whitelisted by Pattern { from: "/home/kmodi/.rgignore", original: "!*", pat: "**/*", whitelist: true, only_dir: false }
DEBUG:rg::ignore: ./SOMEPRJ/.rgignore ignored because it is hidden
SOMEPRJ/abc/def/XXX/YYY/bar
1:foo

SOMEPRJ/ghi/XXX/YYY/bar
1:foo

I believe this works (just that this repeats the bug in #50).

Thanks,

I only concern is that if you implement a global ignore file in $HOME/ripgrep/ignore ( #45 ), then how would the priority work?

Then I would need to put !* in $HOME/ripgrep/ignore that would override the ignores in ~/.gitignore? But wouldn't that be the wrong order?

On the other hand, if I put !* in ~/.rgignore, then wouldn't that override all the ignores in $HOME/ripgrep/ignore? :)

from ripgrep.

BurntSushi avatar BurntSushi commented on May 18, 2024

It seems like the priority of any "global" ignores file should come strictly after any ignores from inside parent directories are considered. If you want to override ~/.gitignore then it makes sense that you should use a ~/.rgignore to do it.

from ripgrep.

BurntSushi avatar BurntSushi commented on May 18, 2024

It sounds like this use case should be solved either by a global ignore file (#45) or by using explicit per-directory overrides.

from ripgrep.

kaushalmodi avatar kaushalmodi commented on May 18, 2024

This issue was more related to #68.

The fix for that issue ( 8eeb0c0 ) fixes this issue too.

Thanks!

from ripgrep.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.