[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Which key for textarea external editor? (was: textarea n

From: Leonid Pauzner
Subject: Re: lynx-dev Which key for textarea external editor? (was: textarea no wrap ...)
Date: Thu, 11 Nov 1999 12:26:13 +0300 (MSK)

10-Nov-99 19:12 Klaus Weide wrote:
> On Wed, 10 Nov 1999, Leonid Pauzner wrote:

>> IMHO textarea editing key should be assigned by default, otherwise a
>> majority of users will lost the feature.

> You have a good point.

>> Why so much pluralism here? (^Ve, ^Xe, ^E^E, etc., but no default value)

> It's not that it has to stay the way it is.

> I started implementing the various ways, rather than having endless
Indeed, that was a beter way:) thanks.

> discussions about the "best" way beforehand.  So the discussion about
> what should be the default can take place now - the mechanisms are
> implemented to pick from (and test).  It's now just a matter of changing
> the value in one of the internal tables.

Reading feedback, seems the consensus reached:
^E^E as default mapping for any key binding table,
also ^Xe for those who use bash-like binding (at least).

The latter fall down to the old problem: meaning of "e" is not the same
as "e" outside of input field. That is overloaded (EDIT/DWIMEDIT) which
may lead to confusion (or not).

As of escape character (you call it PASS), the documentation
should be corrected in several plases (now we have several paragraphes
in User Guide about ^V, and possible workarounds for ^V^V, a notes in
keystrokes/edit_help.html, alt_edit.html, lynx.cfg, else?)
I have not yet looked into keybinding patch not integrated into dev14.

> I do dislike ^Ve as the default binding, for various reasons.  (Briefly:
> ^V doesn't work for some; it's not logical; it takes away 'e'=EDIT.
> For more elaboration, see the "^Ve considered harmful" thread in the
> achive for February, also other messages with "^V" in the subject.)

> ^X as a prefix is a natural for anyone familiar with emacs, or a shell
> that uses emacs bindings.  That should be a lot of users.  Unfortunately
> ^X as prefix is incompatible with the historical Lynx binding as ERASE.
> (Is anyone actually using it for that purpose?  Note it duplicates ^U.
> Personally I'd like to ditch ^X=ERASE, or ditch the Lineedit Bindings
> that use it completely...  but I didn't presume to make such a radical
> change.)

> That leaves (if ^X is unditchable) ^E^E.  There is no technical reason
> why that can't be the binding in all three current Lineedit styles.
> It just isn't, currently, but adding it is a simple change in two
> tables.

> So there you have a brief rehash of my reasoning.  I come to the
> conclusion that, if there is to be one "standard" default, it ought
> to be ^E^E.  Or, alternatively, get rid of ^X=ERASE.  Or, alternatively,
> make Bash-like the default.  Discuss...

>> A person who need a [huge] choice may edit lynx.cfg on a personal basis,
>> isn't it? From the other hand, if there is a choice, which value will be
>> displayed at statusline?

> Well, one of them...  hopefully the best.

>    Klaus

reply via email to

[Prev in Thread] Current Thread [Next in Thread]