Confirmed problem. Actually, I am also unable to bind even "\M-f" usefully (no matter what I put in my .inputrc, it still does forward-word).
However, if I set the locale (via LANG) to "C", then the binding works in console, rxvt and xterm; and gnome-terminal, *if* you also set Terminal -> Set Character Encoding to something like "Western (ISO-8859-1)" (might need to add it).
locale seems to be an issue for every terminal, so it's probably not a terminal issue... It also seems to affect more than just bash, so it's not a bash issue either. Looks like a bug in readline (as reported).
Also, the output of "bind -s" is strange in UTF-8 locales... it seems to output a single, high-order byte as the name of the bound "\M-o", which is obviously not a valid UTF-8 sequence.
I did my testing on Dapper Dan, with libreadline5-5.1-7build1
Confirmed problem. Actually, I am also unable to bind even "\M-f" usefully (no matter what I put in my .inputrc, it still does forward-word).
However, if I set the locale (via LANG) to "C", then the binding works in console, rxvt and xterm; and gnome-terminal, *if* you also set Terminal -> Set Character Encoding to something like "Western (ISO-8859-1)" (might need to add it).
locale seems to be an issue for every terminal, so it's probably not a terminal issue... It also seems to affect more than just bash, so it's not a bash issue either. Looks like a bug in readline (as reported).
Also, the output of "bind -s" is strange in UTF-8 locales... it seems to output a single, high-order byte as the name of the bound "\M-o", which is obviously not a valid UTF-8 sequence.
I did my testing on Dapper Dan, with libreadline5- 5.1-7build1