View Single Post
Posts: 1,873 | Thanked: 4,529 times | Joined on Mar 2010 @ North Potomac MD
#1304
[QUOTE=rebhana;673847]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?]

I get the same in the Debian chroot terminal.

Also, when using xvkbd the function keys do not work properly.
For example, in open office, F11 should bring up "styles and formatting" window. Instead it make open office full screen...

I find that as you get used to using the stylus on the keyboard
you can start pecking along rather quickly so it is nice to take advantage of. Do you know how to define the keys for the virtual keyboard?