Re: Bug#3146: 1.1 installation: ae doesn't work
Raul Miller <rdm@tad.micro.umn.edu> said:
> Bill Mitchell:
> > 2. The standard ae modeless keymappings from upstream:
> > File read and write ^R ^W Left, down, up, right arrow keys
> > Version, quit ^K^V ^C ^K^C Word left and right ^A ^D
> > Macros ^KM Page down and up ^N ^P
> > Help on and off F1 Front and end of line ^F ^E
> > Redraw ^L Top and bottom of file ^T ^B
> > Insert typed keys Delete left and right BACKSPACE ^X
> > Literal escape ^V Block, cut, paste F2 F3 F4
> > Undo ^U Invert case F5
> > (and, actually, help=F1 would be a problem here)
>
> Why is help=F1 a problem here when it's not a problem in your custom
> map?
What got us started on this was a need to support terminals which do
not have function keys. My modifications to our current function-key
based map accepted loss of nonessential functionality, and left nonessential
functions mapped to unaliased function keys. My presumption is that
the motivation in going to this map is to achieve more functionality
on function-key-less terminals and, accepting thqat, the sole function
still mapped to a (possibly nonexistant) function key looks to me
like a problem.
> My preference for this (non-custom) map is that it's one less thing to
> deal with in the long run. If there's better reasons for going
> custom, I'll manage.
I always have to run ae while reading the menu anyhow. I guess I'm more
comfortable using one-handed c9ommand keystrokes with which I'm not
familar than two-handed command keystrokes with which I'm not familiar.
Reply to: