On 29/06/2022 22:27, Timothy wrote:
Max Nikulin writes:
I also really don’t like how `org-mks' so forcefully grabs all keyboard input. I
can see it being nice to jump back to the buffer and see where the resource is
being used, which isn’t really possible using `org-mks'.
An idea: a menu entry that displays location in the org file that caused
the prompt. However it may require enough work to pass context data to
the function rendering menu.
I see you point concerning blocking modal prompt and I do not like it as
well. Have you seen the following thread:
Arthur Miller. Proposal: 'executable' org-capture-templaes. Wed, 22 Jun
2022 14:13:51 +0200.
https://list.orgmode.org/am9pr09mb49771cf015daecbf3e5f955e96...@am9pr09mb4977.eurprd09.prod.outlook.com
If it were merged already, would it be enough for you to implement the
dialog or the proposal lacks some features necessary for smooth user
experience?
The reason why I asked about `org-mks' is expectation of UI consistency
withing Org. It might help users having customized `display-buffer-alist'
Eric S Fraga. Re: Bug: org-no-popups disregards
display-buffer-fallback-action Sun, 14 Nov 2021 19:37:30 +0000.
https://list.orgmode.org/87tugeedfp....@ucl.ac.uk
Eric S Fraga. window management for logging and capturing notes. Sun, 10
Oct 2021 18:01:56 +0100.
https://87zgrgke4b....@ucl.ac.uk
I still do not like code adding a menu close enough to existing one, but
I will not object any more.
