HG(GREP)

💖 NAME 💖

hg grep — bestie, it's literally search for a pattern in specified files. That's it. That's the whole gig. ✨

🌸 SYNOPSIS 🌸

hg grep [--diff] [OPTION]... PATTERN [FILE]...

🦋 DESCRIPTION 🦋

Okay so picture this: you wanna hunt down a regular expression across the files you picked, and you can do it in your working directory or in your revision history — and yes, for the entire repository. 👑

By default, grep searches the repo files sitting in your working directory and just prints the files where it found a match. Want historical revisions instead of the working directory? That's what the --rev flag is for, no cap.

Wanna search historical revision differences instead — the ones where the match status actually changed? Use the --diff flag. The tea: a - means a match that becomes a non-match, and a + means a non-match that becomes a match. It's giving glow-up vs. glow-down. 💀

PATTERN can be any Python (roughly Perl-compatible) regular expression. Slay.

If you don't specify any FILEs and you didn't supply the --rev flag, then every file in the working directory gets searched. And if you are using --rev and you're specifying FILEs, use the --follow argument so it also follows those FILEs across renames and copies. That part matters, don't skip it. 🫶

✨ Template ✨

These keywords are supported in addition to the common template keywords and functions. Also peek at hg help templates, bestie.

• change — String. Character denoting insertion + or removal -. Only available if --diff is specified.
• lineno — Integer. Line number of the match.
• path — String. Repository-absolute path of the file.
• texts — List of text chunks.

And each entry of {texts} provides these sub-keywords, iykyk:

• matched — Boolean. True if the chunk matches the specified pattern.
• text — String. Chunk content.

See hg help templates.operators for the list expansion syntax.

Returns 0 if a match is found, 1 otherwise. Periodt. 💅

🎀 OPTIONS 🎀

• -0, --print0 — end fields with NUL. (yes, the null byte, iconic)
• --all — an alias to --diff (DEPRECATED). ⚠️ It's giving legacy, bestie.
• --diff — search revision differences for when the pattern was added or removed
• -a, --text — treat all files as text
• -f, --follow — follow changeset history, or file history across copies and renames
• -i, --ignore-case — ignore case when matching
• -l, --files-with-matches — print only filenames and revisions that match
• -n, --line-number — print matching line numbers
• -r,--rev <REV[+]> — search files changed within revision range
• --all-files — include all files in the changeset while grepping (DEPRECATED). ⚠️ Also legacy, also still real.
• -u, --user — list the author (long with -v)
• -d, --date — list the date (short with -q)
• -T,--template <TEMPLATE> — display with template
• -I,--include <PATTERN[+]> — include names matching the given patterns
• -X,--exclude <PATTERN[+]> — exclude names matching the given patterns

[+] marked option can be specified multiple times. So go off, stack 'em up. 💖

Okay so that's the whole hg grep manual — every flag, every keyword, every deprecated lil relic, all accounted for, fr fr. It's from the HG(GREP) page, and yeah the footer says the same thing: HG(GREP). Go search something and make it everyone's problem. 🧚‍♀️💜