John H. Robinson, IV wrote:
I am going to guess that the correct answer of using the X11 method of
selecting the text in the To: widget and pasting it into the ``body''
window vi editor instance is not going to be acceptable.
It is if pasting UTF-8 source text into an ISO-8859-1 destination text
is acceptable or if requiring manual overrides every time the character
set changes.
It is also acceptable if you are required to actually put the vi window
into insert mode first before the text hits.
If, however, you actually expect cut-and-paste for your "integrated
editor of your choice" to say, work as well as Windows circa 1998, then,
no, it's not.
The key question: How do we identify what the character encoding is for
the Entry widget and for the vi instance and how do we harmonize the two?
Assuming the vi widget is actually an xterm with Fancy Wrapping: set the
font as required when creating the vi widget to begin with, and the
proper LANG and all that. IOW: it is done when the ``body'' window is
instantiated.
Correct. But you had to *manually* set those up. As well as *manually*
establish vi into insert mode.
Somehow, I don't think most people would consider that to be a good
example of "integrating the editor of your choice". And, if you do,
then you already have the hooks to launch an external version and import
the edited text anyway. Since that's what is wanted, how does what
currently exists not meet the requirements?
Mutt and Lynx both allow me to use the editor of my choice.
They both used to choke quite badly if your editor fed them UTF-16 text.
Has that changed?
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
