This is reported by "xev" in response to the "'" key:
KeyPress event, serial 48, synthetic NO, window 0x1e00001,
    root 0x3af, subw 0x0, time 1860575, (170,-87), root:(1005,201),
    state 0x10, keycode 48 (keysym 0x27, apostrophe), same_screen YES,
    XLookupString gives 1 bytes: (27) "'"
    XmbLookupString gives 1 bytes: (27) "'"
    XFilterEvent returns: False

In lxterminal control v displays "'" though lxterminal doesn't.
"''" shows nothing and "'a" shows "a",
    likewise "'e" = "e", "'o" = "o", etc.

I've examined /etc/inputrc, .inputrc, /etc/bash.bashrc, ~/.bashrc,
/etc/profile, /etc/profile.d/*, ~/.profile, ~/.bash_profile,
both of the latter two just pull in ~/.bashrc which pulls in
bash.{aliases,environment,functions} which are just stuff that started out
in ~/.bashrc but got split out when it got unwieldy.

The only things I've got that tweek the keyboard are
/mc/bin/setkeys which is run by /etc/rc.local
and /mc/bin/xterm_bindings pulled in by bash.environment.
Both of these contain keyboard assignments for bash/readline editing functions
or jed editing functions and don't change how a single quote is handled.
They have been around so long they probably predate my awareness of inputrc.
98% of what is /mc/bin I wrote plus a few things I ran across and kept for
the ideas/lessons they taught.

mike@RPI4b3:~> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS="compose:lwin"
BACKSPACE="guess"

Durring the hours I've spent exploring this problem it has occured to me to
wonder why I would see this problem only in a desktop terminal window
but not on tty(1-10)? That suggests to me that it is not a readline problem
but I don't know much about keyboard mapping in X or wayland as I'm under now.

Suggestions on where to look next?

Thanks for your ideas and Merry Christmas,
Mike
--
No one's life, liberty, or property is safe while
    the legislature is in session.
    - Mel Greene's _The_Greatest_Joke_Book_Ever_

Reply via email to