terminfo not termcap. Nothing uses termcap these days. I don't run kde so I can't point you to the specific option, but somewhere in its settings/preferences konsole should allow you to set the terminal type.

1 members found this post helpful.

I appreciate your input. It seems, however, that we have opened a can of worms already... in the Slackware 14.2 ncurses package, I used a rather old xterm definition. Old, but it worked with just about everything (including konsole). Perhaps I'll revert to that. Once we got the bugs related to the backspace key ironed out, either it worked for everyone or nobody was bothered enough by it to report bugs.

Anyway, I'm still considering what to do about this. Whatever action is taken, I'll be open to any complaints or criticism about. It won't be set in stone.

Okeydoke, I'll butt-out until you decide what's what.

Only for information , sbopkg aparently is ok , wellcome screen is seeying good , but is not true.

search one package and go build , then see for a moment when start download sources how , text screen its going disordering in sbo menu dialog , like others.

Then i suspect this change affect all dialog tools in minor or mayor portion.

Only with manual intervention , changind the default kde konsole profile to linux works.

Ok, I appreciate that you're being pragmatic here, and the frustration in this rant is not aimed at you, but it seems a shame that xterm users must now forgo the advantages/efficiency of having the ECMA-48 specified repeat character sequence simply because konsole's developers were too idle to implement it and too incompetent to give konsole its own unique terminfo entry and use it by default.

Even the basic 'ansi' terminfo entry has this feature enabled!


I won't be following this change here, IMO it's simply too useful a feature to just throw away.


Apologies for the rant: this sort of thing triggers me.

1 members found this post helpful.

Thanks Pat. I really wasn't expecting you to do that, though it feels like the right solution.


I'm afraid this is incorrect. rxvt-unicode uses ^? for backspace just like the linux console. It was right the way it was.

On the off-chance that it's useful, I've attached a simple ncurses program that I've been toying with to learn how to do robust keyboard handling (still not 100% there: I'm finding keypad(__,True); is as much a hindrance as a help); it is useful for detecting bs/del issues and determining what other sequences the function keys generate in various terminals. If you try it with keypad enabled you'll see the bs/del issue with the new terminfo file vs old.

1 members found this post helpful.

Hmmm... why was my backspace key broken then without the change?

I remember that program. I'll take a look, thanks.

PS And, of course, now everything seems to work just fine with the default kbs=^?. What can I say - terminal handling has always been "interesting" to say the least. I'll change it back to the upstream defaults. Thanks!

1 members found this post helpful.

It might possibly have been a rogue Rxvt Xresource. URxvt honours both Rxvt.* and URxvt.* resources and rxvt does use kbs=^H by default so there's plenty of scope for things to get messed up.


The program has evolved a little since the last version I posted (I'd forgotten I'd posted it before). I'm using it as a testbed to develop a reusable input function for use in my other ncurses projects. And, yes, the inconsistencies in trying to deal with different terminal emulators are extremely annoying and ncurses/terminfo seem to only get you part of the way there.


Anyway, thanks for your time and efforts on this one.

Hello.
When I put in KDE Console > Settings > Edit current profile: TERM=xterm-color or TERM=linux
in Midnight Commander "F3" (view) key now works like "*" (invert selection), "F2" key punts "/" in command line.

Could it be the same problem like with slackpkg?

After switch to text console (Ctrl+Alt+F6) Midnight Commander F2 and F3 works properly.

The new default for konsole is TERM=konsole.
From -current ChangeLog.txt
But Konsole won't pick that change if you have TERM set in '~/.kde/share/apps/konsole/Shell.profile'
(or if you have the file anyway, I guess).
If think it's better delete that file and then run konsole, it will show TERM=konsole, which fixes the mc behaviour.

1 members found this post helpful.

Pat. Just wanted to say that I think you came up with a good solution for this by splitting the xterm/xterm-new definitions the way you did in the latest current updates. Real xterm users just need to make sure they set XTerm.termName: xterm-new in their Xresources, and everyone else is happy using the older more compatible definitions. Nicely done. Thank you.

4 members found this post helpful.