So I updated bash to the latest under Slack current. One obvious upgrade was the new colors that showed for certain files/dirs with special permissions. But another was a problem: the Delete key now prints a '~' character and does not DEL like it's supposed to.

Anyone know what's going on?

I don't have that problem in Slackware-current.
Did you just upgrade the bash package of Slackware-current on an older release of Slackware, or did you also install/upgrade all the rest of Slackware-current? The first is a definite road to disaster.

Eric

I use slackpkg to upgrade the entire distribution (at least the packages I installed), originally 10.2 and I track current continuously.

Unless Pat added a package that isn't updated automatically from 10.2, or a config file is misconfigured ... anyone have any ideas?

Just one of many reasons why 'only upgrading what I have' is a road to this forum's favorite question "I upgraded foo, and faa stopped working"

You cannot.....REPEAT CANNOT 'upgrade' just one or two packages to 'current' without getting ALOT of errors. So many packages need so many other programs that you are asking for trouble.Your old Slackware system may not even HAVE the 'other programs' that a 'upgraded package' requires.

If I do a fresh install, then 'current' is fine.

Just do one thing before you allow another 'upgrade'....Do a search on this forum of the single word 'upgrade'....Then try it.

Thanks for nothing.

Anyone else have any ideas as far as bash goes?

Nothing? If you would have done what I suggested BEFORE you 'upgraded' willy-nilly, you would not be in this situation. I was just trying to save you even more grief later.

The simple fix is to remap your keyboard. Search the forum for in-depth discussions on how to do so.

The harder way is to keep the attitude going.

Either way, my 'Del' works.

Hey, all you had to say was that. No need for the flame. If you have nothing constructive to say initially, just don't say it bro. Stick to the topic, plz.

What installation do you have? If full, than take for example slapt-get and upgrade all the packages (not alsa, headers, etc..) with the current release of Slackware. If you prefer the manual way, go to ftp://ftp.slackware.com/pub/slackwar...t/PACKAGES.TXT, run pkgtool and check if you have the same packages installed, which are listed there. If not, try to think if it is required by bash. If yes, then download and install this package.
I also think that you could run setup and maybe remap keyboard.

A few examples of packages that are new in Slackware current (so, upgrading is impossible for these)

openldap-client
cairo
db44
db42

Not installing these, will break many things.

Eric

Interesting. I came across cairo and openldap-client, but I've been dubious about the other two until you mentioned them.

The quickest way I can tell if the system is missing dependencies is from error messages. Like cairo, it was pretty easy because everything was broken and it kept printing an error message about a missing cairo lib.

Let's see if installing those will fix the problem. I've already tried remapping the keybd, but no dice. It's a very old keybd ... IBM ca. 1985

I love the clickyness of the keys. )

Oh, and I forgot to mention. This problem only surfaces in X. I use KDE, so my preferred terminal app is Konsole.

hey how do you get the del to work? > for zsh or bash preferably the first.

Hello,

you must check your /etc/inputrc to see if you have the line :
"\e[3~": delete-char

or put it in your ~/.inputrc

It does. I actually lost the use of 4 keys (now that I finally used it a little more and noticed): Insert, Delete, Page Up and Page Down all do the same thing: '~'

It does it in a console under X and also if I use Putty to ssh into my machine.

It gets weirder.....

I had this problem with my del key after I had edited my /etc/inputrc, in fact I had written "set bell-style none" at the end of the file instead of uncommenting the line at the beginning.

I had the same problem than you, only in console (or konsole), and not in X applications.

Have you tried to create a ~/.inputrc to override /etc/inputrc and see if the problem comes from this file ?