bug#9054: 24.0.50; show source in other window

[Lars Ingebrigtsen]

martin rudalics <rudalics@gmx.at> writes:

> I think we should specify something like a _general_ `display-buffer'
> text property that would specify the basic (aka historic) action
> (`pop-to-buffer' in the case at hand) here.  Then have `display-buffer',
> before it does its `display-buffer-assq-regexp' job, look whether there
> "is a `display-buffer' text property around where the user just clicked
> or where point is" and perform a corresponding action based on whether
> `display-buffer-alist' has a "somehow specified" entry (not a regexp and
> not a function) for it and do either that or what the `display-buffer'
> text-property says.

I'm not sure I understand how that would look in practice.  That is,
what the user would actually put into display-buffer-alist to get the
desired action here.

>> `help-window-select' is (if you squint at it) the kinda-sorta user
>> option in the opposite direction,
>
> `help-window-select' is for users who want to get rid of the *Help*
> window by just typing "q" thus avoiding the "Type \"q\" in help window"
> excursion where they have to explicitly select the *Help* window just to
> quit it.

That's not why I've set it -- I've set it so that I can `C-h foo RET s'
without a `C-x C-o' in the middle.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no