Repository navigation
rtk rg --files <path> treats the path as a pattern when stdin is a pipe #4237
Description
rtk rg --files <path> does not read stdin. It still reacts to stdin, though, depending on how the agent's shell set it up:
$ rtk rg --files src/cmds/system </dev/null | head -2
src/cmds/system/ (19 files)
summary.rs
$ : | rtk rg --files src/cmds/system | head -2
src/cmds/system/summary.rs
src/cmds/system/ctest_cmd.rs
When stdin is a pipe, routing (stdin_is_readable()) takes the positional src/cmds/system to be the pattern and streams the output verbatim, tracked 0/0. When stdin is closed, the same command goes through the file-list path and gets compressed. The output is correct both times, but the saving depends on stdin instead of on the command.
Expected: --files takes paths, never a pattern, so it should route the same way whatever stdin is.
Seen on #4170's head, which adds the file-list fold shown above. The routing decision itself predates that PR.
Activity
rtk-wshm-sync-bot commentedon Sep 25, 2026
🔍 Automated Triage
bugmediumSummary
rtk rg --files <path>routes based on stdin readability instead of the command itself, so the fold/compression in #4170 only applies when stdin is closed.📁 Relevant files
src/cmds/rg.rsSuggested Actions
--filesby presence of the flag/positional path, notstdin_is_readable()rtk rg --files <path>with stdin both open (piped) and closedTriaged automatically by wshm · This is an automated analysis, not a human review.