The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Unable to use 'f' key only in bash

    Discussion in 'Linux Compatibility and Software' started by Falco152, Feb 8, 2011.

  1. Falco152

    Falco152 Notebook Demon

    Reputations:
    442
    Messages:
    1,882
    Likes Received:
    75
    Trophy Points:
    66
    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
     
  2. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
    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/
     
  3. Falco152

    Falco152 Notebook Demon

    Reputations:
    442
    Messages:
    1,882
    Likes Received:
    75
    Trophy Points:
    66
    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...
     
  4. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
    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.
     
  5. Falco152

    Falco152 Notebook Demon

    Reputations:
    442
    Messages:
    1,882
    Likes Received:
    75
    Trophy Points:
    66
    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.
     
  6. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
    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.
     
  7. Falco152

    Falco152 Notebook Demon

    Reputations:
    442
    Messages:
    1,882
    Likes Received:
    75
    Trophy Points:
    66
    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 :)