Skip to content

leading forward slash needs to be escaped for unknown reason #1277

@jspashett

Description

@jspashett

What version of ripgrep are you using?

C:\opt\bin>rg --version
ripgrep 11.0.1
-SIMD -AVX (compiled)
+SIMD -AVX (runtime)

How did you install ripgrep?

cargo install ripgrep

What operating system are you using ripgrep on?

Microsoft Windows [Version 10.0.17134.590]

Describe your question, feature request, or bug.

executing rg "/exchangecommshub"
against any files where a url component is /exchangecommshub does not match for reasons unknown. I assume ripgrep things its a path? This is in contrast to grep, and is surprising.

The leading path separator must be "escaped":
rg "[/]exchangecommshub"

If this is a bug, what are the steps to reproduce the behavior?

Corpus line:
https://redacted.com/redacted/redacted/v1/004022555784/exchangecommshub
Rg:
rg "/exchangecommshub"

If this is a bug, what is the actual behavior?

your
output
goes
here

If this is a bug, what is the expected behavior?

It should have found all files and lines within which contain the literal "/exchangecommshub" in the same way that grep behaves, or it should say why it is/will surprisingly differ from the grep output

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugA bug.wontfixA feature or bug that is unlikely to be implemented or fixed.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions