github-search-cli 9.10.1 → 9.10.3

package/CHANGELOG.md

@@ -6,6 +6,30 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). Publish
 
 ---
 
+## [9.10.3] — 2026-10-14 (released)
+
+### Fixed
+
+- **The help overlay documents `Ctrl+E`.** The utility-keys section listed `t`,
+  `Ctrl+X` and `Ctrl+C` but not the export shortcut, so the keybinding
+  reference was the one place `Ctrl+E` went unmentioned — the startup tip and
+  the README both advertised it. It now appears alongside the other utility
+  keys as `Ctrl+E` — "Export results (CSV / Markdown / JSON / text)".
+
+## [9.10.2] — 2026-10-14 (released)
+
+### Fixed
+
+- **`Ctrl+E` opens the export chooser.** The startup tip list advertises
+  "Press Ctrl+E to export results as CSV or Markdown", but no handler ever
+  claimed the chord: `Ctrl+E` did nothing on the results screen, and while the
+  query input was focused its emacs binding read the same chord as "move to
+  line end". The key handler now claims `Ctrl+E` before the input sees it and
+  opens the export overlay (JSON / CSV / Markdown / plain text). With results on
+  screen that is the shortest route to a `ghfind-export-<ts>.<ext>` file; with
+  an empty result list the status bar reports "No results to export — run a
+  search first" instead of opening an empty chooser.
+
 ## [9.10.1] — 2026-10-08 (released)
 
 ### Fixed

package/README.md

@@ -216,6 +216,7 @@ ghfind --completion fish | source
 | `↑` / `↓` — `j` / `k` | Navigate results & menus                       |
 | `Esc`                 | Open / close leader menu (contextual actions)  |
 | `Tab`                 | Auto-complete search qualifier                 |
+| `Ctrl+E`              | Export results (JSON / CSV / Markdown / text)  |
 | `?` or `Ctrl+H`       | Help overlay                                   |
 | `1`–`5`               | Switch trending tabs (Today → All)             |
 | `←` / `→` — `h` / `l` | Switch trending tabs (left/right)              |
@@ -388,6 +389,14 @@ for the architecture, measurements, and remaining work.
 
 Recent releases (full history in [CHANGELOG.md](CHANGELOG.md)):
 
+### v9.10.3
+
+- **The help overlay lists `Ctrl+E`** — the utility-keys section documented `t`, `Ctrl+X` and `Ctrl+C` but not the export shortcut the startup tip and the README already advertised
+
+### v9.10.2
+
+- **`Ctrl+E` opens the export chooser** — the startup tip advertised "Press Ctrl+E to export results as CSV or Markdown", but nothing bound the chord: it was ignored on the results screen and, while the query input had focus, its emacs binding read it as "move to line end"; it now opens the export overlay (JSON / CSV / Markdown / plain text), or reports that there is nothing to export yet
+
 ### v9.10.1
 
 - **`--interval` is parsed again** — it was documented in `--help`, the README, the how-to guide and all three shell completions, but `parseArgs` had no case for it, so `ghfind --watch --interval 60` searched for the literal string `--interval 60` and polled at the default 300s anyway
@@ -399,30 +408,6 @@ Recent releases (full history in [CHANGELOG.md](CHANGELOG.md)):
 - **The MCP `ghfind_user_profile` tool returns formatted text**, matching `ghfind_org_profile` and the CLI's default `ghfind user` output; the raw JSON still rides along in `data`
 - **Quit paths release the terminal** — the main TUI, the trending view and the package browser call `renderer.destroy()` before exiting, and the trending footer's `/` hint now matches the scroll-to-top key it actually binds
 
-### v9.10.0
-
-- **The TUI is now fully clickable** — the mouse was already enabled (OpenTUI emitted and hit-tested every event) but nothing consumed them, so they were silently discarded; click selects, double-click opens, the wheel scrolls, and clicking outside an overlay closes it
-- **Clicks reuse the keyboard's own code paths** — a click calls `setSelectedIndex`, which emits the same `selectionChanged` event `↑`/`↓` does, so the detail pane, graph and packages view work identically with no parallel mouse branch to drift
-- **Every surface responds** — results, landing mode cards, trending tabs, the update dialog's buttons, and all seven overlay lists (history, bookmarks, saved searches, topics, export, share, command menu), with hover highlighting and a pointer cursor
-- **A <kbd>☰ menu</kbd> button in the bottom-right corner** opens the command menu; it floats above the layout and hides while an overlay is open
-- **The scroll wheel no longer scrolls the wrong pane** — a pre-existing bug: scroll events that hit nothing fell through to the focused renderable, so scrolling in the README viewer moved the _result selection_ instead of the README
-- **Clicks over read-only text now register** — every `TextRenderable` defaults to OpenTUI's text-selection mode, which consumed left-presses as a selection drag before ghfind's handlers ran, so the detail pane and comparison table ignored clicks entirely
-- **`Space` now always types a space, and `Esc` opens the command menu** — `Space` opened the menu only while the query input was unfocused, and the only thing that unfocused it was clicking a result row, so `Space` worked only after a mouse click; `Esc` already closed every overlay, so it gains a meaning rather than losing one
-- **A hover highlight no longer painted lists magenta** — OpenTUI's colour parser accepts only hex and CSS names, so an `rgba()` tint fell through to its magenta fallback
-
-### v9.9.0
-
-- **Queries are understood before they are sent** — every surface (TUI, CLI, MCP, `--watch`) parses and checks a query first, so a typo or bad value fails with a specific message and a fix instead of an opaque GitHub 422 or a misleading "network error"; previously only the TUI ran validation at all
-- **Qualifier typos are corrected** — `langauge:Rust` → `language:Rust`, `star:1000` → `stars:1000`, `push:>` → `pushed:>`; correction is limited to the qualifiers ghfind knows, so `is:`, `has:` and `props.*` are never mangled
-- **Counts accept `k`/`m`** — `stars:10k` → `stars:>=10000`, `size:1m`, `stars:1k..10k`; a bare count keeps GitHub's exact-match meaning, so `stars:100` is still exactly 100
-- **Values are validated per qualifier** — numeric counts, `fork:true|false|only`, `archived:true|false`, calendar-checked ISO8601 dates for `created`/`pushed`/`updated`, the `visibility:` enum, and `in:` fields; documented comma-lists like `in:name,description` still work
-- **Zero results suggest how to loosen the query** — `No results for "rust stars:>=5000000"` now offers `Try: rust stars:>=500000`, ranked by how sharply each qualifier narrows results
-- **`GHFIND_LOG=<path>` writes TUI diagnostics to a file** — the TUI's logger was a silent no-op, making API failures undiagnosable; token values are redacted from logged URLs
-- **A 403 no longer claims SSO is the cause** — SSO enforcement, secondary rate limits and org restrictions all produce it, and the message asserted the first one unconditionally; it now reports GitHub's own reason
-- **The post-upgrade panel no longer reappears on every launch** — it was triggered by a version inequality nothing ever cleared, so it showed after every single launch _including_ after "later" or "never"; it now acknowledges itself once shown
-- **A prerelease is no longer offered as an upgrade** — the version comparison used by Node and the compiled binaries reported `9.9.0-beta.1` as newer than `9.9.0`, i.e. a downgrade; it now follows npm ordering and ignores build metadata
-- **A new [how-to guide](docs/HOW-TO.md)** — token setup, writing queries, reading results, recovering from errors, and copy-paste recipes
-
 ## License
 
 MIT

package/dist/cli.js

@@ -2154,7 +2154,7 @@ var cached = null;
 function getVersion() {
   if (cached) return cached;
   if (true) {
-    cached = "9.10.1";
+    cached = "9.10.3";
     return cached;
   }
   try {
@@ -4177,6 +4177,10 @@ function buildHelpSections() {
       title: " Utility Keys ",
       titleColor: "muted",
       rows: [
+        {
+          keys: "Ctrl+E",
+          action: "Export results (CSV / Markdown / JSON / text)"
+        },
         { keys: "t", action: "Cycle theme (light / dark / solarized)" },
         { keys: "Ctrl+X", action: "Copy repo URL to clipboard" },
         { keys: "Ctrl+C", action: "Copy search query to clipboard" }
@@ -8000,6 +8004,16 @@ ${pack.description ?? ""}`;
       showOverlay("help");
       return;
     }
+    if (key.ctrl && key.name === "e") {
+      key.stopPropagation();
+      if (currentRepos.length > 0) {
+        showOverlay("export");
+      } else {
+        setStatus("No results to export \u2014 run a search first");
+      }
+      renderer.requestRender();
+      return;
+    }
     if (key.name === "tab") {
       if (searchBox.visible) {
         const val = searchInput.value;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "github-search-cli",
-  "version": "9.10.1",
+  "version": "9.10.3",
   "description": "Search GitHub from your terminal — repo search, trending repos, npm package search, bookmarks, deep-dive, compare, export. Keyboard + mouse TUI + pipeable CLI.",
   "type": "module",
   "packageManager": "bun@1",

package/release-notes/9.10.2.md

@@ -0,0 +1,26 @@
+# v9.10.2
+
+A one-key release: the export shortcut the app has been advertising in its own
+startup tips now exists.
+
+## `Ctrl+E` exported nothing
+
+The tip list in `src/tips.ts` advertises _"Press Ctrl+E to export results as
+CSV or Markdown"_. Nothing bound the chord. On the results screen `Ctrl+E` was
+ignored outright, and while the query input had focus the line editor's default
+emacs binding claimed the same chord as "move to line end" — the one place it
+did something, it did the wrong thing.
+
+The key handler now claims `Ctrl+E` before the input ever sees it, and opens
+the export overlay: JSON, CSV, Markdown, or plain text.
+
+- With results on screen, `Ctrl+E` goes straight to the chooser — no detour
+  through the leader menu (`Esc` → Navigate → Export) — and writes the same
+  `ghfind-export-<ts>.<ext>` file the overlay always wrote.
+- With an empty result list it does not open an empty chooser: the status bar
+  says `No results to export — run a search first`.
+
+## Nothing else changed
+
+The export overlay itself is untouched — the shortcut drives the existing
+overlay rather than growing a second code path that could drift from it.

package/release-notes/9.10.3.md

@@ -0,0 +1,27 @@
+# v9.10.3
+
+A one-row documentation release: the in-app help screen now lists the export
+shortcut.
+
+## The help overlay skipped `Ctrl+E`
+
+`?` (or `Ctrl+H`) opens the keybinding reference. Its **Utility Keys** section
+read `t`, `Ctrl+X`, `Ctrl+C` — and stopped there. So `Ctrl+E` was the one key
+that ghfind never documented in the place you actually look keys up, even
+though everything else already mentioned it: the startup tip rotates through
+_"Press Ctrl+E to export results as CSV or Markdown"_, and the README's global
+shortcut table carries the row.
+
+It is now the first row of that section, with the other utility keys:
+
+```
+Ctrl+E        Export results (CSV / Markdown / JSON / text)
+t             Cycle theme (light / dark / solarized)
+Ctrl+X        Copy repo URL to clipboard
+Ctrl+C        Copy search query to clipboard
+```
+
+## Nothing else changed
+
+The shortcut itself landed in 9.10.2; this release only documents it. No
+behaviour, output, or CLI surface changes.

package/src/help.ts

@@ -173,6 +173,10 @@ export function buildHelpSections(): HelpSection[] {
       title: " Utility Keys ",
       titleColor: "muted",
       rows: [
+        {
+          keys: "Ctrl+E",
+          action: "Export results (CSV / Markdown / JSON / text)",
+        },
         { keys: "t", action: "Cycle theme (light / dark / solarized)" },
         { keys: "Ctrl+X", action: "Copy repo URL to clipboard" },
         { keys: "Ctrl+C", action: "Copy search query to clipboard" },

package/src/tui.ts

@@ -3458,6 +3458,20 @@ ${pack.description ?? ""}`;
       showOverlay("help");
       return;
     }
+    // Ctrl+E opens the export chooser (CSV / Markdown / JSON / plain text)
+    // straight from the results — the shortcut the startup tip advertises.
+    // Claim the chord first: while the query input is focused its default
+    // emacs binding would otherwise also treat Ctrl+E as "move to line end".
+    if (key.ctrl && key.name === "e") {
+      key.stopPropagation();
+      if (currentRepos.length > 0) {
+        showOverlay("export");
+      } else {
+        setStatus("No results to export — run a search first");
+      }
+      renderer.requestRender();
+      return;
+    }
 
     // Tab auto-completes qualifiers in search input
     if (key.name === "tab") {