"Sylvain Abélard" <[EMAIL PROTECTED]> writes: > I still don"t know if that's technically and easily feasible,
Tuomo suggested one way of doing this (using bdoc), another might be to use a menu structure to represent commonly used commands and set up a helper-function that would call a particular menu entry, which would then be bound rather than the lua code itself. The bdoc method is likely to be more informative, but the menu method is probably more likely to survive unsophisticated changes to keybindings. Basically you'd be setting up a kluge of a "command" type on top of the lua function calls. > but > that's what some games do (Prince of Persia 3/4) and for some friends > that like dvorak, it really was welcome when it bound four keys in the > right place (e, o and...) instead of just looking for the famous WASD > (which must be pretty much scattered everywhere). ",a;h" if you're wondering.... As a dvorak user I tend to change my keybindings extensively. You can get used to anything, of course -- I still use hjkl, even thought the keys I press would be "jcvp" on a qwerty keyboard. But for a lot of less frequently used commands I use custom menus bound to keys via mod_query. And I use app.lua instead of virtually all of the navigational keybindings. > Just looking for those four keys are a pain on an azerty (fr) keyboard > when you can't change the config can be quite disturbing. -- Jeremy Hankins <[EMAIL PROTECTED]> PGP fingerprint: 748F 4D16 538E 75D6 8333 9E10 D212 B5ED 37D0 0A03
