🚀 go-pugleaf

In article <DSCHIEB.93May27153644@muse.cv.nrao.edu> dschieb@muse.cv.nrao.edu (Darrell Schiebel) writes:
> In article <1u2npd$atc@terminator.rs.itd.umich.edu> Jim.Rees@umich.edu writes:
> >
> > I also can't figure out how to get it to work the way I like to use epoch,
> > which is to have a single minibuffer, and each buffer in its own window.  I
> > think this can be done but I haven't figured it out yet.  It's got a
> > variable you can set to give each buffer its own window ("screen" in epoch
> > terminology, "frame" in emacs, "window" to X) but it doesn't really work
> > the way I want.
>
>  I couldn't figure this out either, and I posted this question
>  to 'gnu.emacs.help' to no avail. I hope the epoch/lemacs merger
>  will retain this functionality!! As near as I can tell, currently
>  neither emacs-19 nor lucid emacs allows one to have a single 
>  minibuffer which is shared by all screens/frames and resides in a 
>  screen/frame of its own.

	Well, I was wrong, the 'make-frame'/'new-frame' commands give
	everything necessary to have a separate minibuffer, and it seems 
	to do it in a very nice way. I think something like the following
	works:

		(setq default-minibuffer-frame 
		    (new-frame 
		        '((width . 400) (height . 1) 
		          (minibuffer . only))))

	then after that the following will create a minibufferless
	frame: 

		(new-frame '((minibuffer . none)))

	At least this is close to what is required.

							Darrell Schiebel