>>>> "ms" == Michael Sperber
<sperber(a)informatik.uni-tuebingen.de> writes:
>>>> "Martin" == Martin Buchholz
<martin(a)xemacs.org> writes:
MS> So, you would rather be associated with Windows and Notepad?
MS> :-)
Martin> Yes.
Yikes!
ms> This disagreement is exactly the reason why we shouldn't get
ms> religious about the issue.
Um, you know, like, sorta,.... Anyway, I agree with Michael. I just
want this debate over with....
Ahem. If Customize (as much as I hate Customize) were keymap capable
and we had customize themes....
Isn't that where all these keystrokes should be going?
<TONGUE-IN-CHEEK>
Really, the solution is to leave ALL the defaults in their legacy
position, and for every key (moderate position: that excites this kind
of debate), we initially bind it to the function
`users-dont-do-any-work-anyway-so-lets-ask-him-what-this-key-should-do'.
This would be done _after_ reading .emacs, so all us legacy
keystrokers could setq
`i-have-work-to-do-so-dont-you-dare-touch-my-f**king-keymap' to t once
and never have to deal with it again.
</TONGUE-IN-CHEEK>
Realistically, with customize themes, we could put a `keymap' topic in
the Help menu (`keyboard' if you think PC users wouldn't catch on).
This could have a set of themes (Windose Notepad, Word, Happy
Hacking---disables all unnecessary keys, old-duffer-emacs,
the-one-true-keymap---alias for old-duffer-emacs and my personal
favorite, etc). Then there could be an optional `keymap test' which
drops the user into a test buffer and exercises as many of the
controversial or difficult keys as we can think of.
If we were serious about interface improvement. (I'm not, not enough
to implement the above :-( gomenne.)
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
__________________________________________________________________________
__________________________________________________________________________
What are those two straight lines for? "Free software rules."