rtk-ai/rtk

rg rewrite edge case

Open

#1367 opened on Apr 17, 2026

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallgood first issue

Description

llm attempted usage:

rg -n -U "document:\\s*\\{\\s*create:\" api/src scripts" ^ this works normally

after rewrite: rtk grep -n -U "document:\\s*\\{\\s*create:\" api/src scripts"%

usage output: /usr/bin/grep: Unmatched \{

Contributor guide

Tech stack
rust
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
understanding of regex escapingability to read Rust code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how the RTK grep subcommand passes the regex pattern to /usr/bin/grep. Compare with ripgrep's behavior. Look at the command construction in the grep implementation, likely in `src/commands/grep.rs` or similar. Check if there is any escaping or transformation applied to the pattern that causes the `{` to be unmatched. The issue may be related to how the pattern is sanitized or how arguments are passed to the system grep.