xbindkeys-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xbindkeys-devel] xbindkeys translates unicode spaces to ASCII space?


From: Jim Snyder
Subject: [Xbindkeys-devel] xbindkeys translates unicode spaces to ASCII space?
Date: Mon, 26 Mar 2018 11:14:13 -0400

Issue: xbindkeys seems to be translating em3space (U+2004) to ASCII space (0x20)

I've looked online, but the recipes I've found don't produce the results I 
expect.

Here's what I did.

I checked that typing:

        $ xdotool key em3space

in the terminal causes an em3space (a "thin" space) to be printed to the 
terminal.

Added to $HOME/.xbindkeysrc:
__________

        # type unicode em3space
        "xdotool key em3space"
        alt + space
__________

However when I type:

        $ <Alt>+<space>

in the terminal an ASCII space is printed on the terminal, not an em3space.
__________

As said, my immediate impression is that xbindkeys is translating em3space to 
ASCII space.

Or do I misunderstand how to use xbindkeys?

Or (3rd possibility) might the default key mapping or some other default X11 
functionality be intervening before xbindkeys gets its hands on the 
<Alt>+<space> key sequence? 

Incidentally, I get the functionality I want (to wit: an em3space in response 
to AltGr+space) with the following lines in .xmodmap:
_________

# AltGr as Mode switch
keycode 108 = Mode_switch

# space + two unicode spaces
keycode 65 = space emspace em3space
_________

(System: I'm running a fully patched archlinux x86_64 with the plan9port window 
manager (rio), which has its own notion of Unicode glyphs, so that's another 
possible source of confusion.)

Thanks for any pointers / tips / whatever.

                        Jim Snyder





reply via email to

[Prev in Thread] Current Thread [Next in Thread]