It is important to distinguish "keyboard accelerator keys"
interface with a keyboard interface.
To start slowly, note that a true graphical interface has elements
such as clickable icons and menus. To save a file using gvim's
graphical interface, one would use a mouse to pull down the File
Menu and then click on Save. But suppose
* one removed gvim's graphical interface components (to see
what this would look like, set guioptions=acM)
* put the image of a keyboard toward the bottom of the buffer
and then claimed that this gvim had a graphical interface because
one could use the mouse to click on the keyboard and do things
like save by clicking in sequence :w<cr>. One could interact with
such a gvim using only the mouse but does it really have a
"graphical interface"?
The above example shows that one can have a mouse only interface
that is not a graphical interface. Likewise, one can have a
keyboard only interface that is not a keyboard interface.
The essence of a keyboard interface is its conceptual nature;
it is based on language. "keyboard accelerator keys" are just
a bunch of perceptual keys -- that is why one needs visual
feedback (or rote memorization) while using them.
Bram has a very good introduction to learning the vim text editor.
After seeing that, if you still think you will profit by a
letter-prompter, you can create a prompter yourself: write a
script that prompts the user using information from the file
index.txt.
--Suresh
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
