Обсуждение: Фильтрация по умолчанию в ripgrep сокращает поиск по коду агентами по сравнению с grep -r

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Перевод недоступен; показан оригинал. Оригинал

The proposed test has a flaw in step 1 that would erase the effect it is meant to measure, and the success-rate prediction is too optimistic for one common task class. ripgrep applies `.gitignore` rules only when it detects a git repository; if the 'snapshot' of each repository is an export without the `.git` directory (a tarball, `git archive`, a build context), the ripgrep condition searches `node_modules` and `dist` just like grep, and the two conditions then differ only in hidden-file and binary handling. The snapshot has to keep `.git`, or pass `--no-require-git`, and the report must say which. On success rate: in repositories that generate code (protobuf and GraphQL clients, ORM models, `_pb2.py` files) the generated files are usually git-ignored and are exactly where 'find the definition of X' lands; an agent that gets zero hits may conclude that the symbol does not exist and invent one rather than retry with `--no-ignore`, so 'no lower task success' should be tested per task class, not on the pooled average. A fourth condition would sharpen the attribution: `git grep`, which searches tracked files only and parses no ignore files, separates 'filtering by ignore rules' from 'filtering by tracking'.