Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?
On 2015-08-09 12:39:32 +0200, Nicolas George wrote:
> If everything was not already complicated enough, shift, control and
> caps-lock have each a fixed value in the state mask, but all the other
> modifiers (from num-lock to alt-gr, including meta and super) arrive to the
> application as mod1 to mod5, with an arbitrary mapping. Applications (or
> toolkits) that want to allow alt- or meta-prefixed shortcuts are supposed to
> inspect the key mapping table to identify the correct modX. They usually get
> it wrong, frequently hard-coding mod1 = alt (to react to it) and mod2 =
> num-lock (to ignore it).
And now the Alt/Meta modifier should be called Alt instead of Meta
as some applications (e.g. Firefox) don't support Meta.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: