Actually Esc [ F and Esc [ H are the correct sequences, the older variants  
(Esc [  1 ~ and Esc [ 4 ~) just happen to work as well.  
 
If you prefer the old sequences, go 
 
Settings -> Keyboard -> XTerm (XFree 3.x.x) 
 
Or am I overlooking something?

As said, the current settings don't work in for example mc. This is because in
the 6.x days RedHat decided (and was correct in doing so) that xterm bindings
where a mess and should be standardised. In those days it was decided that home
and end send ESC [ 1 ~ and ESC [ 4 ~. This is what the RH shipped termcap /
terminfo say, even in skipjack beta 2 also since these days all RH shipped xterm
& friends send these ESC-sequences. But in skipjack beta2 both konsole and rxvt
are broken. But xterm and gnome-terminal still send these. This is btw also
according to the debian keyboard policy, and thus ensures compatibility when
telnetting to / from debian.

Also note that non XFree xterms (sun,hp) still send the old (and standard)
ESC-sequences. Way they ever changed is a mistery since this breaks telnet
between different versions, and for just that reason changing them now in the
middle of a stable RH series is a bad idea!

The very basics of terminals say that terminfo and the actual behaviour should
match. And for compatibilities sake, ESC sequences once chosen may never change,
new ones for new functionality may be added, but old ones should never change.

Is anything going to actually happen with this bug, if this becames the new
default behaviour a lott of apps will break in one of the major terminals
shipped with RH, and RH travels back to the 5.x days on this aspect of usability.

Still not fixed in 8.0. Bad, in the 7.0 / 7.1 times I and a few people at RedHat
spent a lott of time getting this right, and now the setup is broken again.

Lett me scream this:

A TERMINAL SHOULD SEND THE KEY (ESC) SEQUENCES THAT TERMCAP/TERMINFO SAY IT WILL
SEND FOR A CERTAIN KEY.

gnome-terminal gets it right, xterm gets it right, konsole is broken. Also note
that selecting the keyboard profile for xterm-xfree-3.3 will fail to because
this sends the correct sequences for home-end but the wrong ones for F1-F4 .

As I already said this is a known bug and was fixed in the past, this time I've
managed to find my old bug: bug 15682. It also contains 2 different fixes for
kde2, which very likely still apply to kde3.

Please fix this, not working keys like home and end are a MAJOR usabelity issue.
 You've know idea hoe many of my linux usign friends and students complain about
this.

Onr last note I believe that the terminal behaviour should not be configurable
at all, but thats a different discussion. Please at least get the default setup
fixed.

This bug is still there in Phoebe.

I can't find an example app since most apps seem to include a workaround but any
app using just ncurses (as intented) will fail because konsole sends ^[[F for
end instead of ^[[4~ same for home. Take a look at the redhat created
/etc/inputrc . Here end is binded to ^[[4~ . It also works in konsole because
inputrc contains a binding for ^[[F to for telnet from the freebsd konsole. So
this is just pure luck. Please fix this. Xterm end is supposed to send ^[[4~ and
home ^[[1~ this is an official RedHat point of view. So konsole is broken also
do "tput khome > log" and check the context of log. (tput uses ncurses / terminfo)

I just tried:

mv /usr/share/apps/konsole/default.Keytab /usr/share/apps/konsole/default.keytab
(changing the extension from Keytab to keytab watch the case)

And then editing default.keytab unfortunatly this doesn't change the default
keytab but instead adds an extra entry to the settings->keyboard menu. So the
real defaults are hardcoded somewhere in the source :|

Also I've found 2 other keyboard related konsole bugs, which I will add to
bugzilla after a coffee break :)

Still there in severn, I'm willing to write a patch for this and bugs 80650 and
80651, if you're willing to include it :)

Created attachment 94801 [details]
Patch fixing the described problems and also fixing bug 80651

This patch touches the same files as kdebase-3.1.2-keydefs.patch, maybe they
should be merged? In any this one must be applied after that one!

ping

Hi Hans, i have merged your patch in kdebase-3.1.4-keydefs.patch.
kdebase-3.1.4-3 should have this fix. Many thanks for your patch file.

>Still there in severn, I'm willing to write a patch for this and bugs 80650 and
>80651, if you're willing to include it :)

Please attach your patch file here, i will add it in next rebuild of course ;-)

GRRR, this bug has resurfaced in FC2, see bug 124803.