Skip to content
Struis ICT edited this page Aug 23, 2026 · 7 revisions

Usage

Add one or more folders, type a query, and matches stream in as InSearch walks the tree and searches inside each file. Results appear in a File / Line / Match table with the matched text highlighted.

Search modes

Pick a match mode from the dropdown:

Mode Meaning
Substring plain literal text (default)
Regex a regular expression — see below
All words every space-separated word must appear (AND), in any order
Any words any of the space-separated words may appear (OR)

Plus:

  • Exclude — a separate field for words that must not appear (NOT).
  • Whole word — match whole words only (word boundaries).
  • Case — Smart (case-insensitive unless your query has an uppercase letter), Case sensitive, or Ignore case.

Regex syntax

Regex mode uses Rust's regex engine (the same one as ripgrep): character classes, |, quantifiers, anchors (^ $ \b), groups, \d \w \s, and inline flags like (?i). For performance it is linear-time, so backreferences and look-around are not supported.

Line vs. block

  • Line — one result per matching line.
  • Block — one result per timestamp-to-timestamp block. A line that begins with a timestamp (ISO-8601, syslog, MM/DD/YYYY, or epoch) starts a block; following non-timestamped lines (stack traces, pretty-printed JSON, …) belong to it. Ideal for logs.

Live vs. Watch

  • Live — search-as-you-type; each change re-scans the chosen folders.
  • Watch — keep results live as files change. New matches in growing logs appear automatically (log-tailing); removed files drop out.

Filters

Open ⚑ Filters to narrow a search. Every filter is empty by default and self-activating — a blank field is ignored, so you only fill in the ones you need. Filters are kept for the session (not written to disk unless you Save the search). Every date field accepts YYYY-MM-DD with an optional HH:MM, and each has a 📅 calendar button.

Filter Narrows to…
Name files matching a glob (*.log); click the .* chip to switch that pattern to regex
Type only these extensions, and/or not these
Size KB a min–max size range
Recent files modified within the last N days
File date files whose last-modified time is in an after → before window
Entry time log entries whose in-content timestamp is in a from → to window

File date vs. Entry time

These answer different questions:

  • File date filters on the file's modification time — i.e. which files to search.
  • Entry time filters on the timestamp written inside each match (ISO-8601, syslog, MM/DD/YYYY, or epoch) — i.e. which log entries to keep. It slices a multi-day log down to just the lines/blocks in your window, regardless of when the file was last written. (In Line mode, lines without their own timestamp are dropped while this filter is active; in Block mode, a block inherits its opening timestamp.)

Once an Entry-time bound is set, a ⚡ skip files older than "from" toggle appears — an optional accelerator that skips any file whose modified time predates the lower bound (its newest entry can't be in range) without reading it. Turn it off if file timestamps aren't reliable (e.g. copied or touched files).

Working with results

Switch the results View between Compact (File · Line · Match) and Detailed, which adds Folder, Size, and Modified columns. (Metadata is read lazily for the rows on screen, so Compact searches stay fast.)

  • Double-click a file name — or anywhere on its row — to open the file in its default app.
  • Right-click a result for: Open, Reveal in file manager, Copy path, Copy matched text, Copy result (path:line: text), and Copy all results.
  • Export the visible results to CSV, JSON, or plain text.
  • Filter results — a box that narrows the current list without re-searching.
  • The status bar shows the match count, files scanned, and elapsed time.

Recent & saved searches

  • 🕘 Recent — reuse a recent query.
  • ★ Saved — save the current query, options, filters, and folders under a name and restore it all later. Loading a saved search replaces your current filters with the saved set (and opens the Filters panel if it carries any). Recents and saved searches persist between sessions.

CLI

insearch-cli is a headless search harness:

insearch-cli <pattern> <root> [more roots...] [--regex] [--gitignore]

It prints path:line: text for each match and is pipe-friendly (works with head, grep -q, etc.).


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

Clone this wiki locally