Re: switch-to-buffer: for interactive use only

[grischka <grishka@gmx.de>]

> I think that we want two types of `switch-to-buffer' functions:
> 
> (1) [...] C-x b [...] set-window-buffer' based [...] not callable
>     from Elisp.
> 
> (2) [...] callable from Elisp.
> 
> Anything wrong with this approach?

Yes.  I've observed this elsewhere earlier. It means that emacs to
support its native UI, uses tricks that aren't available for the
mere mortals.  However if there is anything that actually flies
then it's the built-in always existing UI's such as completion or
help.

Only naturally that people will want their thing work equally well,
sooner or later learn the necessary tricks and then you are back in
the situation where you have zero control for consistency because
your freshly designed interface is consequently bypassed by, which
is only worse, those who actually care for good UI.

--- grischka

> 
> martin