> that's because they're not standard. you can use them if you map them > with /dev/kbmap. > > cpu% cat fkeys > 0 59 '☺ > 0 60 '☹
For some definition of "standard", really. The thing is that the letter "a" is a clear concept no one is likely to argue with (and even there, different keyboard layouts throw a spanner in the works, but at least one assumes the keyboard has clear labels in place), but using F1-F2-F3 as mouse buttons is a totally different idea and needs to gain critical mass (think F1 as the Help key) before developers can safely commit to it. Chording itself is not at fault, although Gabriel is perfectly right when suggesting that remembering more than a few combinations becomes very difficult. What is problematic is assigning the type of meaning to each chord that meets with mass approval. Given that needs vary and some chords are bound to be easier than others, this is an unlikely expectation. Add the option to fall back to a keyboard shortcut and the intent is readily defeated. What may assist a lot would be visual hints, where the mouse pointer or the colour of the highlight reflects the status of the chord. But I doubt that one would come up with a consensus on such meanings where there are more than a few like in RIO or ACME. ++L
