I'm running out of ideas to track and fix it.
I tried using the default .bash_profile, .bashrc, and .inputrc.
My colleagues have no issues with theirs.
I wonder if you guys have other ideas that I don't have.
I'm running CentOS 2.6.18-164.15.1.el5PAE, GNU bash version 3.2.25
-
ALLurGroceries Vegan Vermin Super Moderator
Are you talking about the F1-F12 keys, the Fn "function" key combos, or the actual letter F?
Are you using gnome-terminal? Have you tried it in xterm?
For gnome-terminal, there are keyboard preferences in Edit->Keyboard Shortcuts, look there to see if that key is bound to any special function.
You can also manually edit the profile config in ~/.gconf/apps/gnome-terminal/ -
The actual letter F.
I tried using xterm, gnome-terminal, and konsole, same result. Even the non x11 terminals.
Only my bash shell has the problem, my csh works fine though... -
ALLurGroceries Vegan Vermin Super Moderator
You haven't done anything to /etc/inputrc? If you set up a new user, does it have the same problem (that would be a cheaphax way to tell if it's a user config problem or global)?
It could be a problem with your keymap or locale. On Debian, it'd be dpkg-reconfigure console-data and dpkg-reconfigure locales respectively, but I have no idea about CentOS. -
Unfortunately, I do not have root access to these machines.
It is a user config problem.... Other users has no problems.
The only files that I mess with bash is ~/.bashrc, ~/.bash_profile, and ~/.inputrc but I reverted them back to campus defaults.
It is possible it is a keymap problem, but it's odd that does filter out my 'f' when I use copy and paste.
I can't figure the correct terminology to determine a button keycode and what it is bound to. So my google search is failing me. -
ALLurGroceries Vegan Vermin Super Moderator
The keyboard hardware produces a scancode, which becomes a keycode in software.
Look at dumpkeys, setkeycodes, showkey, etc. manpages. I'm not sure where your problem is, .inputrc would have been my guess. -
Thanks...your insight help me track down the problem.
Turns out, I was missing a comment # in one of my comments in .inputrc.
Ugh... I need sleep, can't believe I missed that several times over.
Plus you help me out to fix my superL key as well, totally unrelated
Unable to use 'f' key only in bash
Discussion in 'Linux Compatibility and Software' started by Falco152, Feb 8, 2011.