Piers Cawley

Yeah, I was trying to avoid the long `which-key-declare-prefixes` approach because I wanted to try and declare a binding once and only once. Then again, I've already written macros to...

Hmm... I rejigged my `which-key--maybe-get-prefix-title` to try `(or (menu-prompt binding) (symbol-name binding))` when setting `alternate`, which lets me do: ``` elisp (define-prefix-command `my-prefix nil "prefix") (which-key--maybe-get-prefix-title) ;; => "prefix" ```...

Yeah, but when I bind them I can do: ``` elisp (define-key global (kbd (concat my-leader " K")) `(keymap "Kpref" . ,actual-map)) ``` Which is ugly as sin, but easily...

Ah... that's not going to work. Can't use an anonymous keymap; have to use a symbolic name or there's nothing to do a lookup on. Drat.

I'm about to raise a pull request that fixes things by rejigging `which-key--get-current-keybindings` with something that doesn't do its work by parsing the `describe-current-keybindings`, so we can inspect the actual...

Right, it's [PR#144](https://github.com/justbur/emacs-which-key/pull/144)

> Is there a reason to support setting the "special block -> front-matter" association using Org keywords? At present, I build bofh.org.uk in a Github Action that works by grabbing...

Actually, so long as the special blocks alist is marked as safe to be made buffer local, I can get away with: ```emacs-lisp # -*- mode: org; org-hugo-special-block-type-properties: (("announcement" :front-matter...

I'm not particularly attached to the mechanism by which something is hoisted to the .md file's front matter, I just want to avoid having to mess with `:export_hugo_custom_front_matter:` if I...

This seems to have sat for a couple of years with no serious objections. Is there anything that can be done to move it forward (or backward – out of...