🚀 go-pugleaf

Please do not leave out the ability to have a separate minibuffer.  I concur
with previous messages, and contribute these reasons for keeping it:

1) Fitts law as applied to one's eyes: The minibuffer is always in one place,
   at the bottom of the display/monitor in my case => always know where to
   find it.
2) 1 to 1 mapping of minibuffer screen to minibuffer buffer => nice and
   understandable.
3) Minibuffer is as wide as the monitor/display => easy to handle long file
   paths, etc.
4) Net savings of screen real estate as compared to minibuffer-per-epoch-
   screen.  I.e., minibuffer-per-screen "wastes" 1 line on each screen as
   compared to separate minibuffer.

Three more points come in because I use the olvwm virtual window manager;
perhaps these hold true for tvtwm and others:

5) The minibuffer is "sticky" under olvwm, which means it remains in the same
   place on all virtual screens.  So if I switch to a screen in which no other
   Epoch screens are present, I have not lost access to epoch, just move the
   pointer into the minibuffer screen.
6) Fitts law as applied to mouse pointer movement: Whenever I want access to
   epoch, I can slam the mouse towards the minibuffer, which, since it is
   glued to the bottom of the display, is a cinch to reach.


                                                     ,-------.
						    /  	 |    \
        Dave Bristor                               /     |     \
        bristor@sun.com                            |     |     |
#include <disclaimer.h>                            \    /|\    /
                                                    \  / | \  /
                                                     `-------'