bug#9054: 24.0.50; show source in other window

[Lars Ingebrigtsen]

Juri Linkov <juri@linkov.net> writes:

> I see help-function-def--button-function now uses pop-to-buffer-same-window.
> Should other button types do the same?  Such as help-function-cmacro,
> help-variable-def, help-face-def.

Yes, indeed; now fixed.

I didn't notice because I have

(setq help-window-select t)

and that makes these commands also work the same, but it should be
possible to have that nil and help-window-keep-selected t.  I think I've
now got all the various button types, but it's possible more of them
lurk somewhere.

> BTW, I can't find a discussion about scratch-buffer, so I'll ask here:
> when I accidentally delete the *scratch* buffer, the first thing I do is
> 'C-x b *scratch* RET' and discover an empty buffer.  I wonder would it help
> to add a '("\*scratch\*\\'" . scratch-buffer) to 'auto-mode-alist'
> that will recreate it after switching to a new buffer with this name?

Hm...  that seems quite attractive, but also somewhat surprising.  I
mean, `C-x b foo.c RET' doesn't put the resulting buffer in C mode.

On the other hand, the *scratch* buffer is slightly special, so perhaps
this would be helpful for users.  The reason I added the
`scratch-buffer' command is that I remember a number of users saying
that they'd accidentally killed the buffer, and couldn't find a way to
get it back to how it was working (because typing `M-x
lisp-interaction-mode' is a pretty obscure thing to say).

So perhaps it would be helpful to do what you say.

Does anybody have an opinion here?

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