Just my .2 cents inline. Just a word of caution for users on master. The new keymap functions like (keymap-set-after ...) are still bumpy. If you want any item to appear in the menu, check that the text shown in the menu item passes (key-valid-p). This is currently not the case for 'Show/Hide' 'Export/Publish', etc.
Yet another .2 cents, /PA On Mon, 10 Nov 2025 at 05:52, Tor-björn Claesson <[email protected]> wrote: > Some errors crept along in the previous version, here is a fixed one, > sorry for the spam. > > So, to recapitulate I have two questions, one small and one about the > scope of this patch. > > The small one: should we drop the description field and always use the > first line of the docstring for menu titles? This feels much smoother. > That depends on how you craft either... Don't docstrings tend to grow (even their first line)? The big: should this be about choosing an "action" at point, or a > more general framework for presenting menus? If it remains small in > scope, should we find an other name than org-menu? > I was a bit tired of the wealth of information shown after C-c C-e and went for a more contained version with which-key in the minibuffer. In my case, it helps me compress the functions I really need into a menu... Cheers > Tor-björn > > -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler "Sagen's Paradeiser" (ORF: Als Radiohören gefährlich war) => write BE! Year 1 of the New Koprocracy
