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

On Wed, Jul 29, 2026 at 2:39 PM Stefan Monnier <[email protected]>
wrote:

> > How about we add a new property to bookmark handlers.  Just as we have
> > properties like (get handler 'bookmark-handler-type), we can add a new
> one
> > that indicates a handler handles its own display and we'd ignore
> > display-function in bookmark--jump-via when that property is present (or
> a
> > specific value).
>
> I'd rather we just make sure that whichever display-function is used
> behaves tolerably when the handler (incorrectly) displayed the
> buffer already.
>

I think the issue with this strategy is that there is no easy way to
determine what a handler might have done.  In the bufferlo case, for
example, new frames and/or tabs can be created and many underlying buffers
created (themselves being bookmark records).  Using a property seems more
reliable and doesn't require shenanigans.

And we should push to fix those misbehaving handlers.  I understand it
> can sometimes require some code surgery, but that's a reason to try and
> tolerate it, not a reason to refrain from asking for improvement.
>

In addition, we can improve handlers that need help.