🚀 go-pugleaf

: In fact, I completely disabled the separate minibuffer even as an
: option, because observation of users familiar with ordinary Emacs made
: it clear they could never quite figure out where it was or what it was
: doing.  I think if the minibuffer had not been separate to begin with
: (in Epoch), there would have been so few requests for it that it would
: have never been implemented, but I am not in a position to back this
: claim with any hard evidence, since for all I know, it was implemented
: _because_ of user requests which happened before I joined this mailing
: list two years ago.

I have to disagree you in this one.  During older emacs days (18.44), Doug 
Young modified emacs and create gnuvo with separate mini-buffer.  Gnuvo is
still being used by many HP users.  I switched to epoch two years ago
because the similarity and better lisp library support.  When FSF asking 
for ideas on version 19, separate mini-buffer is on the top of my list.  
As matter of today, epoch will be useless for me in my virtual windows 
system in a attached mini-buffer scheme.  I did try to use attach 
mini-buffer but that proven to be too much a productivity lost.  We've
a growing user community for epoch in HP.  So it is not a seldom used
feature.


	============================================================
	Peter Huang 		HP Response Center Lab
	Phone: (415)691-3417  	Email: huangp@mayfield.HP.COM
	100 Mayfield Avenue, MS 37MA, Mountain View, CA 94043
	============================================================