On 07/06/2022 10:09, Samuel Wales wrote:
i must be confused. menus aside, you can currently capture and it
uses the org forest itself, so it is both crash-proof and snappy. and
you can yakshave as much as you want, starting a capture while doing a
capture. those were design goals.
you can even be in the middle of a capture, get distracted, navigate
around your forest, and find where you are in the middle of a capture.
goes with the original crash-proof and yakshave and snappy
use-original-buffer design goal.
so are we talking about menus then? is there truly a need to make
/menu state/ persistent or yakshaveable?
As soon as capture template is chosen, content is landed to the target
file and may be autosaved. I do not expect problems here.
However if two org-protocol handlers are launched without specified
template then behavior of Org becomes confusing. I meant this case.
Currently reading key from minibuffer serves as a kind of
synchronization tool.
Imagine what would happen if Emacs decided to show several capture menus
with keymap non-blocking interface in different virtual desktops.
Capture data should be saved somewhere till the user would discover
initially hidden menu.
For me applications spread over 4 virtual desktops and more than one
emacs frame is a usual case. I have not realized yet exact conditions
when capture buffer appears in the frame other than one displayed on the
active virtual desktop.
