[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: switch-to-buffer: for interactive use only
From: |
grischka |
Subject: |
Re: switch-to-buffer: for interactive use only |
Date: |
Thu, 14 Jul 2011 00:13:07 +0200 |
User-agent: |
Thunderbird 2.0.0.24 (Windows/20100228) |
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
- Re: switch-to-buffer: for interactive use only, (continued)
- Re: switch-to-buffer: for interactive use only, Stefan Monnier, 2011/07/10
- Re: switch-to-buffer: for interactive use only, Chong Yidong, 2011/07/11
- Re: switch-to-buffer: for interactive use only, Stefan Monnier, 2011/07/12
- Re: switch-to-buffer: for interactive use only, martin rudalics, 2011/07/12
- Re: switch-to-buffer: for interactive use only, Chong Yidong, 2011/07/13
- Re: switch-to-buffer: for interactive use only, martin rudalics, 2011/07/13
- Re: switch-to-buffer: for interactive use only, Chong Yidong, 2011/07/13
- Re: switch-to-buffer: for interactive use only, martin rudalics, 2011/07/09
Re: switch-to-buffer: for interactive use only,
grischka <=