bug#81467: [PATCH] Make bookmark-jump work with other-window/frame/tab-prefix

 > Unlike Man-bookmark-jump that can let-bind Man-notify-method to 'meek',
 > there is no easy way to refactor shell-bookmark-jump to not use
 > pop-to-buffer.  And there are other existing handlers that display
 > the buffer too.  So we are back to the same problem of preventing
 > the double display in bookmark--jump-via.

Could you explain the problem in a more general manner?  I'm too silly
to understand it so far.  AFAICT we want to display a buffer and there
are two or more agents who would display it in different ways.

Let's assume two agents where agent1 acts first but agent2 should
eventually prevail from the user's perspective.  Now agent1 displays the
buffer and agent2 either accepts the choice due to a reuse-window
condition or displays the buffer in another window due to something like
inhibit-same-window.  So we should either run agent2's choice first and
have agent1 accept it or manage to make agent1's choice a NOOP.  Is that
a faithful description?

And there seems to be the further aspect that agent1 selects the chosen
window and agent2 does not want to do that so we would either have to
re-select the previous window or have make agent1's selection a NOOP.

Are there further aspects?

martin