aboutsummaryrefslogtreecommitdiff
path: root/scripts/theme-studio/test-nerd-icons-legend-dump.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-10 00:38:21 -0500
committerCraig Jennings <c@cjennings.net>2026-07-10 00:38:21 -0500
commit02c2e0ee8e00869681595bd7b80a98219563b39f (patch)
treee60c19fd1c3ce7f1802a39cb135b3c20ae772630 /scripts/theme-studio/test-nerd-icons-legend-dump.el
parent7f9c44023a89ef47a3a1a76a2ada4d69ba0ad678 (diff)
downloaddotemacs-02c2e0ee8e00869681595bd7b80a98219563b39f.tar.gz
dotemacs-02c2e0ee8e00869681595bd7b80a98219563b39f.zip
docs(design): survey where a curated "?" help menu fits
The mechanical half of the "?" convention task. I probed ten modes from their live keymaps rather than from source, because a package's define-key calls don't always agree with what lands in the map. Four modes have both ? and H free, so nov, eat, and the two elfeed modes can adopt the convention without displacing anything. Three bind ? to something small that adopting it would displace. mu4e-headers is the one real conflict: its ? marks mail unread, a state-mutating command in the marking family. magit already binds ? to its own dispatch. The convention isn't new, it's magit's habit generalized. I ran the probe in a throwaway batch Emacs rather than the daemon, since probing calibredb and mu4e in a live session would force-load them. mu4e isn't an ELPA package and needed its site-lisp path.
Diffstat (limited to 'scripts/theme-studio/test-nerd-icons-legend-dump.el')
0 files changed, 0 insertions, 0 deletions