Re: The Modernization of Emacs: keyboard shortcuts pain



Xah Lee <xah@xxxxxxxxxx> writes:

Xah Lee wrote:
«
Why Emacs's Keyboard Shortcuts Are Painful
http://xahlee.org/emacs/emacs_kb_shortcuts_pain.html
»

Alain Picard wrote:

«First of all, they're not called "shortcuts", they're called "key
bindings".»

"Keyboard Shortcuts", is the more well known and standard term.
"Keybindings", is almost unknown, except among Emacs users. The above
is the practical aspect. In a idealistic aspect, it is arguable that

I perceive you are Asian...

Look, this is just an idea, but there is a conceptual difference
between a world that emphasizes the visual, the effect, and hides the
mechanism; and one which emphasizes the mechanisms and how things
work. Mainly because in one world the users are forced to not
understand, and in the other the users can understand if they wish. In
any case, in the second world, users get to the effects by the route
of first understanding the mechanisms. That way, they undertstand not
only the "desried" effects, but also all the limitations and foibles.

For what its worth, the difference between the textual and literal
(=detailed, accurate w.r.t mechanisms) thought in the West, and
visual and presentational (=emotive, appealing, innaccurate w.r.t
mechanisms) thought in the East, are similar. To me this is a
terrible misuse (in a business sense a fantastic success in creating
a consumer culure) of the first-class visuo-geometric capabilities of
Asian people (it doesn't work nearly as well in the West, where
people generally get turned off by such methods and in any case as
far as I've read we lack the same level of visuo-geometric IQ).

It also explains in some ways the tendency in Japan to not be
innovative or go into business for yourself, but to hang with the big
guys for protection.

Now, of course the exceptions are legion, and all the Asian people
I've met who are number one in their field are as precise in their
understanding of the mechanisms of their field and would never think
to put this precision in a way that hides the mechanism unless they
were trying to fool non-experts, but you're not talking about the
exceptions here, you're saying the norm want keys that reflect the
effect rather than the mechanism. Sorry, emacs is not commercial
software, and people want to stay close to the mechanism, because
nobody else is going to do the legwork but the users themselves.
--
Gernot Hassenpflug
.



Relevant Pages

  • Re: To assert or not to assert...
    ... assert is intended to catch ... Memory allocation faults. ... exceptions (either OS-specific, or involving a custom-made ... special handling code built on top of OS-specific mechanisms (such as Win32 ...
    (comp.lang.c)
  • Re: A solution for the allocation failures problem
    ... exception safe code with the mechanisms C provides for all of the ... reasons it's very hard to use multiple points of return. ... Exceptions simplify the callee at the expense of more work in the caller. ...
    (comp.lang.c)
  • Re: COM sometimes turns exceptions into HRESULTs, sometimes doesnt - why?
    ... The proxy/stub pair must try and handle exceptions, so as not to tear down the mechanisms for marshalling, which may run on a secondary thread. ... If your COM object is constrained to be used from C++, and only from the same thread (strictly speaking, apartment) in the same process, I wonder why you went to the trouble of making it a COM object in the first place. ...
    (microsoft.public.win32.programmer.ole)