KW-EXPLORE(1)

👑 kw-explore — Explore folder 💅

okay bestie, so this page is the manual for kw-explore, which lives in the kw manual gang. it's the explore folder situation, and honestly? it's giving "I know exactly where that string is and I'm about to prove it." 🦋

---

✨ NAME ✨

kw-explore — Explore folder — fr fr, that's the whole name, no notes 🎀

---

⭐ SYNOPSIS ⭐

kw (e | explore) [(-l | --log) | (-g | --grep) | (-a | --all) |
--verbose]
       [(-c | --only-source) | (-H | --only-header)] [(-C[<num>] |
       --show-context[=<num>])] <expr> [-p] [<dir> | <file>]

like. look at her. she contains multitudes. 🌈

---

💖 DESCRIPTION 💖

so the explore command is, by default, a wrapper to git grep — it's out here searching for string matches in files under git control, or in the git log messages. that's her default era. 👑

but wait, there's more, because additional parameters extend her behavior so she can also cover all files in a directory (whether or not they're controlled by git, she does not discriminate 💅) and also swap out the search tool for the GNU grep utility. glow up.

so like, default usage: you can use kw e <function-name> to find <function-name> in the source directory. iconic. and if your string has spaces in it you have to quote your search, e.g. kw e "<str1> <str2>". do not skip the quotes, I am begging 🙈

---

🎀 OPTIONS 🎀

• -l, --log — search the git log history by using --log after the e. for instance, kw e --log <string-match>. bonus: you can also use -p to see the diff in the search. main character behavior ✨
• -g, --grep — search for string matches in directory contents using the GNU grep tool. for instance, kw e --grep <string-match>. she also covers files inside the .git directory, no gatekeeping 💜
• -a, --all — search for string matches in directory contents using the Git grep tool. for instance, kw e --all <string-match>. with this one, the search ignores files inside .git, except if it's called inside the .git directory. in other words, if you use this option you will notice that git grep is used first, and then GNU grep. two queens, one job 🫶
• -c | --only-source — with this option, it's possible to show only the results from the source. just the source, nothing else, periodt 💅
• -H | --only-header — with this option, it's possible to show only the results from the header. header only, she's exclusive 🎀
• -C[<num>] | --show-context[=<num>] — show <num> lines of additional context above and below the matched line. if <num> is not specified, the default value of 3 will be used. bestie, the default is three, write that down 📝
• --verbose — verbose mode lets you see the commands executed under the hood. it's giving backstage pass 🎟️✨

---

🌸 EXAMPLES 🌸

to show matched line with context using long-form flag:

kw explore --show-context=5 search_string

to show matched line with context using short flag:

kw explore -C5 search_string

search through all tracked and untracked files, default value of 3 will be used for context:

kw explore -C --all search_string

---

ok quick vibe check 💀 — that's literally everything the page says. every flag, every default, every example. no cap. don't come for me if you didn't quote your spaced-out search string, I warned you 🙈

---

and that's the whole page, bestie 🦋 this was kw-explore - Explore folder() — Explore folder(), that's the title and the footer energy, iconic of her honestly. mwah, slay, go find your strings. 💖✨🎀👑🌈