3 ms·

I also vote for "do what gitignore does". My plan is to add support for the new file name, deprecate .agignore, and update docs everywhere. But it'd be a while

by ggreer 10y ago

I also vote for "do what gitignore does". My plan is to add support for the new file name, deprecate .agignore, and update docs everywhere. But it'd be a while before I removed .agignore completely. I really like .ignore, and I like it because it's generic. The information I want it to convey is: > Dear programs, > If you are traversing this directory, please ignore these things. Of course, some programs could still benefit from having application-specific ignore files, but it'd cut down on a lot of cruft and repetition.

burntsushi 10y ago
Let's do it. https://github.com/BurntSushi/ripgrep/issues/40 https://github.com/BurntSushi/ripgrep/issues/40
- ggreer 10y ago
  …and merged: https://github.com/ggreer/the_silver_searcher/pull/974 https://github.com/ggreer/the_silver_searcher/pull/974 I'll tag a new release in a day or two. Also, it looks like the sift author is getting on the .ignore train: https://github.com/svent/sift/issues/78#issuecomment-249335277 https://github.com/svent/sift/issues/78#issuecomment-2493352... This worked out pretty well. :)
  - burntsushi 10y ago
    Same! https://github.com/BurntSushi/ripgrep/pull/41 https://github.com/BurntSushi/ripgrep/pull/41 Agreed :-)
    - deleted 10y ago
      [deleted]
    - tonglil 10y ago
      This is probably the best case of out-in-the-open open source developers of similar-but-different tools collaborating on a new standard and implementing them in record time that I have ever seen. Keep it up all (rg/ag/sift)!
      - scott_karana 10y ago
        I completely agree. That was one of the most reasonable and level-headed discussions between strangers I have _ever_ seen on the Internet!
- deleted 10y ago
  [deleted]