bug#49057: 28.0.50; windmove-display-in-direction ignores windmove-display-no-select

[martin rudalics]

> But wouldn't this be too confusing for users, when users will call
> `pop-to-buffer' with the new alist entry 'select', and it still will select
> the unintended window as `pop-to-buffer' currently does?

`pop-to-buffer' has to select the window chosen by `display-buffer'
regardless of whether `display-buffer' selected it or not.  Do we
violate this principle anywhere?  The basic difference I'd propose is to
have `pop-to-buffer' bind

 (display-buffer-overriding-action '(nil ((select . t))))

around the `display-buffer' call and so `display-buffer' will select the
chosen window regardless of any user customizations.

martin