Re: ehelp woes, or why I hate a module that I love so much

[Juanma Barranquero <lektu@terra.es>]

On Wed, 26 Jun 2002 18:24:24 -0400, Richard Stallman <rms@gnu.org> wrote:

> I don't think anyone else is working on this, so if you want to
> develop these changes, please do.

First I'd like to get some input from people around here regarding why
it is necessary for ehelp to use its own command-loop. I sure would like
to get rid of it.

AFAICS, the command-loop is used only to (sort of) "force" the user to
do only pg-up, pg-down, quit, retain, etc. and show a prompt in the echo
area.

But in fact it is perfectly posible to switch to another window, kill
the electrified buffer, etc., so the command-loop is more of a nuisance
than any kind of help.

I think ehelp is conflating two different things: a framework to make
temporary, small-sized windows at the bottom of the frame and restore
the window configuration afterwards, and an "electric" interface to get
a reminding prompt and to dismiss the window with just one keystroke.

IMHO, there should be a splicit framework for temporary, small-sized
windows (using fit-window-to-buffer, etc), but its "electricity" should
be limited to defining a few useful keybindings. Moving around is
self-evident (I mean, all modes have a way to move around), and quitting
and remaining are just particular cases of burying or killing the buffer
or switching to another window. Or am I missing something important here?


                                                           /L/e/k/t/u