View Single Post
rebhana's Avatar
Posts: 579 | Thanked: 471 times | Joined on Jan 2010 @ Austria
#1288
Originally Posted by mscion View Post
I've had similar problems. Also If I used Mod5 + up or other arrow
keys more than a few times in .xbindkeysrc, the new key
definition did not work. I have no clue why.
Actually my problem is xvkbd, not xbindkeys. If I just type
Code:
xvkbd -xsendevent -text "a"
in the Debian chroot terminal, I get (after a bunch of warning messages) "a" on the next command line. Similarly when I use "\[parenleft]" I get "(". But with a lot of other special characters such as "\[percent]", I get nothing at all. Most but not all of the characters that I can compose with Fn are not produced, plus all that are on the virtual keyboard.

mscion, do you have the same phenomenon or is it just me?

The warnings that xvkbd issues look unrelated to my problem:

Code:
Warning: Cannot convert string "-*-lucidatypewriter-bold-r-*-*-12-*-*-*-*-*-iso8859-1" to type FontStruct
Warning: Cannot convert string "-*-helvetica-bold-r-*-*-12-*-*-*-*-*-iso8859-1" to type FontStruct
Warning: Cannot convert string "-*-helvetica-medium-r-*-*-12-*-*-*-*-*-iso8859-1" to type FontStruct
Warning: Cannot convert string "-*-helvetica-medium-r-*-*-10-*-*-*-*-*-iso8859-1" to type FontStruct
xvkbd: Mode_switch not available as a modifier
xvkbd: although ISO_Level3_Shift is used instead, AltGr may not work correctly
__________________
Need more apps for the N900? Check out Qole's Easy Debian and read the wiki!
My Easy Debian installation log