From 4d906b08970ef0b536bf0dd1a23a3b75a636f16d Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Wed, 24 Jun 2026 22:45:46 -0400 Subject: docs(spec): google-keep in-editor integration spec (draft, 5 open decisions) --- todo.org | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'todo.org') diff --git a/todo.org b/todo.org index 04a78da06..6c909e997 100644 --- a/todo.org +++ b/todo.org @@ -3757,7 +3757,8 @@ These may override useful defaults - review and pick better bindings: Display slack.el message and thread buffers in a dedicated popup window (side or bottom) and reuse that one window instead of spawning a new window per buffer. Likely a =display-buffer-alist= rule (or popper integration) in =modules/slack-config.el=. ** TODO [#C] google-keep in-editor integration — build, module-to-package :feature: -No in-editor Emacs google-keep package exists (researched 2026-06-24); only a one-shot Takeout-to-org importer, and the live API is unofficial (gkeepapi reverse-engineers the private mobile endpoint, with auth fragility). The existing google-keep MCP already gives agent-driven read/write. Craig wants a custom integration built here instead: surface Keep notes either as an org-capture-style popup or as a separate org-mode page with each note rendered as an org header. Build in =.emacs.d=, eventually extract to a standalone package (the VAMP / pearl module-to-package pattern). Data source: the google-keep MCP (or gkeepapi directly, accepting the unofficial-API risk). Spec it before building — decide the shape (popup vs org page), read-only vs read-write, and the auth/data path. +Build a native Keep integration: an org page of notes (each note an org header), read-only in v1, a gkeepapi Python subprocess bridge for data (the MCP is agent-only, not callable from elisp), auth via authinfo.gpg, eventually extracted to a standalone package. vNext: read-write, the org-capture-style popup, list rendering. +Spec: [[file:docs/specs/google-keep-emacs-integration-spec.org][google-keep-emacs-integration-spec.org]]. Five decisions are drafted with recommended calls and await Craig's confirmation (shape, direction, data path, auth, structure); the spec stays draft until they resolve. ** TODO [#D] Theme Studio nerd-icons vNext follow-ups :feature: Deferred from [[file:docs/specs/theme-studio-nerd-icons-colors-spec.org][theme-studio-nerd-icons-colors-spec.org]]: extend the legend to buffer-mode and command/symbol categories if the file set proves insufficient; -- cgit v1.2.3