Thread View: gnu.epoch.misc
4 messages
4 total messages
Started by David.BRistor
Thu, 25 Feb 1993 19:46
save the separate minibuffer!
Author: David.BRistor
Date: Thu, 25 Feb 1993 19:46
Date: Thu, 25 Feb 1993 19:46
33 lines
2295 bytes
2295 bytes
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> \ /|\ /
\ / | \ /
`-------'
Re: save the separate minibuffer! (not!)
Author: Jerry Graves
Date: Sat, 27 Feb 1993 01:00
Date: Sat, 27 Feb 1993 01:00
18 lines
1671 bytes
1671 bytes
I won't say that those who prefer a separate minibuffer don't deserve a choice, but it would be my guess the Jamie and fellow coders at Lucid would have less of a headache by eliminating a seldom used option. If it makes any difference, when I upgraded Epoch from 3.2 to 4.0, everyone here was very pleased that this orphan minibuffer had finally returned home. 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. -Jerry
Re: save the separate minibuffer! (not!)
Author: Jeff Putnam
Date: Sat, 27 Feb 1993 15:48
Date: Sat, 27 Feb 1993 15:48
44 lines
2953 bytes
2953 bytes
In article <9302262151.AA00473@banach.math.ep.utexas.edu> jerry@math.ep.utexas.EDU (Jerry Graves) writes: >I won't say that those who prefer a separate minibuffer don't deserve >a choice, but it would be my guess the Jamie and fellow coders at >Lucid would have less of a headache by eliminating a seldom used >option. If it makes any difference, when I upgraded Epoch from 3.2 to >4.0, everyone here was very pleased that this orphan minibuffer had >finally returned home. >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 disagree with this post in two ways. First, I very much like the separate minibuffer. Mine sits at the bottom of my screen and I know where to look for it automatically. I must admit that for the first couple of days I was confused, but since then I've tried Epoch without the separate minibuffer and found it very annoying. Second, (and without meaning to flame) I find the attitude of 'I know whats best for the users at my site, so I'll just "disable [...] even as an option"' to be more than annoying. Vendors and system managers fall into this all too often. This attitude is not only patronizing, it is usually wrong. I dont consider myself particularly a "power user" or anything, but I want to be able to make up my own mind about options - and 95% of the time when someone else makes such determination it turns out to be wrong for _someone_. Options should be optional. Leave them that way. -- jefu <=> Jeff Putnam - New Mexico Tech <=> jefu@nmt.edu "Daffodils go Ping! and Oink! // They Really are alarming I'm scared of big geraniums // And I'm sure that Lilac's harming" (Dr. Bertram X. Fegg)
Re: save the separate minibuffer! (not!)
Author: Simon Marshall
Date: Fri, 05 Mar 1993 14:10
Date: Fri, 05 Mar 1993 14:10
30 lines
2271 bytes
2271 bytes
In article <9302262151.AA00473@banach.math.ep.utexas.edu> jerry@math.ep.utexas.EDU (Jerry Graves) writes: >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. How thoughtful of you. Perhaps you should disable other options too, in case it confuses users? Maybe you should replace emacs with vi, to prevent those of us who start life with vi from moving up to emacs and getting confused? > 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. Arguing that if users had never heard of separate minibuffers, they would never have asked for it is a little pointless. I must admit that it took me a while to get used to having one minibuffer in one place, but I felt that it was sensible and would be a benefit. I would like to have the choice, I hope that Lucid/Epoch keep it. But we get what we pay for, don't we?! Si. -- Simon Marshall, Dept. of Computer Science, University of Hull, Hull HU6 7RX, UK "Football isn't about life and death. It's more important than that." Bill Email: S.Marshall@cs.hull.ac.uk Phone: +44 482 465951 Fax: 466666 Shankley
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads