I've followed these instructions to the letter, and still nothing works.
Whether I use a vanilla putty session, (I blew it away and re-installed from scratch to ensure that nothing was left over from my earlier attempts to configure). Or a vanilla SSH 3.2.9 (build 283) (Also re-installed from scratch).
In both cases, with the .inputrc file from above, uploaded using the SSH file transfer widget and bound using the command shown. Nothing works.
I also tried logging out and logging back in, in the forelorn hope that the .inputrc file would be read and acted upon when a new session was started, but still nothing changed. I think that the problem lies in the set up at the host end rather than PC end. Maybe it is non-standard. Surely not everyone using a (RH 7) linux system has to go through this?
None of the edit keys do anything at all except the backspace key? I cannot even retrieve the previous command using the up-arrow.
All of which has made my use of Linux over the last 6-weeks a less than wow experience.
In reply to Re: Re: (OT): .inputrc mapping PC keyboard to sensible set vi or set emacs functions.
by BrowserUk
in thread (OT): .inputrc mapping PC keyboard to sensible set vi or set emacs functions.
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |