BurntSushi/ripgrep · error

{line_number}: {err}

Error message

{line_number}: {err}

What it means

Error "{line_number}: {err}" thrown in BurntSushi/ripgrep.

Source

Thrown at crates/core/flags/config.rs:102

fn parse_reader<R: std::io::Read>(
    rdr: R,
) -> anyhow::Result<(Vec<OsString>, Vec<anyhow::Error>)> {
    let mut bufrdr = std::io::BufReader::new(rdr);
    let (mut args, mut errs) = (vec![], vec![]);
    let mut line_number = 0;
    bufrdr.for_byte_line_with_terminator(|line| {
        line_number += 1;

        let line = line.trim();
        if line.is_empty() || line[0] == b'#' {
            return Ok(true);
        }
        match line.to_os_str() {
            Ok(osstr) => {
                args.push(osstr.to_os_string());
            }
            Err(err) => {
                errs.push(anyhow::anyhow!("{line_number}: {err}"));
            }
        }
        Ok(true)
    })?;
    Ok((args, errs))
}

#[cfg(test)]
mod tests {
    use super::parse_reader;
    use std::ffi::OsString;

    #[test]
    fn basic() {
        let (args, errs) = parse_reader(
            &b"\
# Test
--context=0

View on GitHub (pinned to 3fce3b5bb0)

Solutions

1. Open the config file at the reported line number and fix the syntax error described
2. Validate the config file format against the expected schema

When it happens

Trigger: Thrown at crates/core/flags/config.rs:102 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of BurntSushi/ripgrep@3fce3b5bb0 (2026-08-06). Data as JSON: /data/errors/98faac0d91d85554.json. Report an issue: GitHub.