⬡Search & filter

Search modes — token search

There is a single search input (the icon mode-tabs were removed in 0.2.7). Focusing it opens a scope dropdown; the mode is chosen by typing a prefix, which becomes a removable coloured chip inside the input.

Entry point

• ToolbarFocus the search box → a dropdown lists Author File Hash Code with example syntax. ↑↓ + Enter pick one.
• PrefixType author:, file:, hash:, code: (or @ for author) and it converts into a chip; no prefix = Message search.
• BackspaceOn an empty input, removes the active scope chip and returns to Message.

Message filter log --grep

1. Typing debounces, then Go re-runs log with grep.
2. The graph is re-laid-out over the matching commits — connectors reflect just the filtered set.

Hash prefix jump

1. Entered as a hash prefix (e.g. a0c103).
2. Resolved client-side against the loaded history to jump to the matching commit.

File search log.file

1. Enter a file name or path.
2. Go returns the commits touching that path (backs the same query as file history).

Author filter log --author

1. Enter an author name or email.
2. Go re-runs log with author server-side; the graph re-lays out over the matches.

Code search — pickaxe log -S

"When did this string appear or vanish?" Searches content changes, not messages — only commits where the number of occurrences of the string changed (introduced or removed) match. Unrelated commits that merely shipped alongside the string don't.

Entry point

• ToolbarPick the Code scope — a full-width monospace snippet box opens below the toolbar (auto-grows to 6 lines, paste-friendly, multi-line supported).

1. Unlike the other modes, code search runs only on Enter / the Search button — pickaxe scans every diff in history and is too expensive to run per keystroke. Shift+Enter inserts a newline; clearing the box restores the full log.
2. Go runs log with pickaxe (git log -S<string>); the graph re-lays out over the matches and the result count is flashed (N commits add or remove this snippet).
3. Why a commit matched — selecting a result restricts the detail pane's file list to the files where the snippet count actually changed (diff-tree -S, the pickaxe param on diff), labelled "· snippet matches". Opening a file's diff also highlights every occurrence of the snippet in the native diff editor.

Branch scope

Entry points

• Branch pillOpens a searchable branch picker with a pinned All branches first entry; the pill label reflects the active scope. (The separate All/This-branch toggle was removed in 0.2.7.)
• Pick a branchRestricts the log to that branch; picking All branches passes --all.