Skip to content
Struis edited this page Aug 21, 2026 · 6 revisions

FAQ

Is the search regex-compatible? Yes — choose Regex as the match mode. It uses Rust's regex engine (character classes, |, quantifiers, anchors, groups, (?i) flags). Backreferences and look-around aren't supported (a linear-time performance guarantee). See Usage.

How do I search a folder straight from Explorer? Enable it once in ⚙ Settings → Explorer integration, then right-click a folder → Search with InSearch (Windows 11: under Show more options). See Installation.

Does it search inside PDFs / Word / Excel files? Yes — pdf, docx, and xls/xlsx/ods are decoded to text and searched. PDF results depend on the PDF containing real text (scanned images have none). See Supported formats.

What's "block" mode? One result per timestamp-to-timestamp log block instead of per line — so a match inside a multi-line stack trace shows the whole block. See Usage.

Does InSearch build an index or run in the background? No. Searches run on demand over the folders you pick; there's no daemon and no index to maintain.

Does it send anything over the network? No. InSearch is entirely local — no telemetry, no update checks. See Security & privacy.

Why are some results capped? The UI holds up to 10,000 matches to stay responsive; refine your query (or use the Filter results box) to narrow down.

Can I run it headless / script it? Use insearch-cli — it prints path:line: text and is pipe-friendly. See Usage.


© Struis ICT — https://struisict.com · Buy me a coffee ☕

Clone this wiki locally