On Tue, Mar 29, 2005 at 01:11:44PM -0600, Richard Rauch wrote:

> Well, if there are no misunderstandings, then, it seems that this is
> fixed in -current.

To avoid any further misunderstanings:

Do you have "proper Delete" key (when cursor "eats" the following characters,
not moving itself from its position) in the console (text) mode? In the
command line of the shell, in the applications too - never mind (at the
moment) the XTerm window?

> I'm not sure why it is not fixed in 2.0.  Since
> Christopher W. Richardson confirmed that X is able to tell the keys
                            ^^^^^^^^^^^^^^^^^^^^^^^^ so what?
> apart int 2.0.2, you might try upgrading to 2.0.2.

Why you're still writing about "solution for X" - I'm talking all the time
(since the very beginning) about text mode console, and not just about
XTerm-window. The "X-only" solution means, the problem is still here.

Of course, my proposal solves the problem for both text console & X.

> If that fixes the problem then there was a bug in 2.0.  If it does not fix
> the problem, then perhaps we do not fully understand one another.  (Though
> how adding a "Remove" coding for ^D and mapping that to the DEL key would
> solve this problem eludes me, if the already-existing BackSpace/Delete
> options do not help...)

It's very simple: when I've got a new symbol, with its numeric value 4
(<control>-<D>) I'm able then to "tie" that symbol to any key, and - using
wsconsctl - in any mode of operation, never mind, text or graphic.

Get back to my first message opening this thread - and you'll see the
solution.

If someone's telling, that "it's all OK, the keys are sending different
codes" - could I have the solution of the problem (not just separate
"workarounds" for X, for this and for that application...)?
-- 
				pozdrawiam / regards

						Zbigniew Baniewski