aboutsummaryrefslogtreecommitdiff
path: root/modules/mu4e-org-contacts-integration.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-02 20:46:46 -0500
committerCraig Jennings <c@cjennings.net>2026-06-02 20:46:46 -0500
commit09b3b136a007b592aef708b208c81e9453e848c2 (patch)
tree1d33cf1eb317a42a06bfbf85fe5d31dccfa472f7 /modules/mu4e-org-contacts-integration.el
parent13b053c2a99d30c1131d920a62febde6ee9a628b (diff)
downloaddotemacs-09b3b136a007b592aef708b208c81e9453e848c2.tar.gz
dotemacs-09b3b136a007b592aef708b208c81e9453e848c2.zip
refactor(linear): reduce to a vanilla pearl setup
The config carried a full custom command surface: a hand-built C-; L keymap, which-key labels, a lazy API-key loader wired in as advice, and a pinned DeepSat team id. That's worth keeping only if the out-of-box pearl experience isn't good enough on its own, and the point now is to find out. Stripped it back to exactly what pearl's README documents for a first install: pearl owns its own keymap (pearl-mode binds the command surface under pearl-keymap-prefix, default C-; L, in any Linear buffer), no global binding, no advice. The API key comes from authinfo.gpg via auth-source-pick-first-password, and the synced file moves to gtd/linear.org under org-directory. The only deviation from the README is loading from the local checkout at ~/code/pearl instead of an archive. Deleted tests/test-linear-config.el — it covered the custom helpers (the key-loader advice, the keymap wiring) that no longer exist. What's left is declarative use-package config with nothing of its own to test.
Diffstat (limited to 'modules/mu4e-org-contacts-integration.el')
0 files changed, 0 insertions, 0 deletions