Changes between Version 2 and Version 3 of CustomKeyBindings
- Timestamp:
- 12/08/08 17:12:20 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CustomKeyBindings
v2 v3 2 2 3 3 As of version 0.4.1, the user may specify custom key bindings in their `.haskeline` file. The two new settings are: 4 - {{{keyseq: <string> <key>}}} (POSIX-only: add a new key sequence)5 4 - {{{bind: <key> <key>}}} (bind the first key to the actions of the second key) 5 - {{{keyseq: <term> <string> <key>}}} (POSIX-only: add a new key sequence) 6 6 7 where {{{< string>}}} is a Haskell stringand {{{<key>}}} is either:7 where {{{<term>}}} is a terminal name (optional), {{{<string>}}} is Haskell string syntax, and {{{<key>}}} is either: 8 8 - a single character 9 9 - `f<n>` (a function key) … … 54 54 }}} 55 55 56 Finally, we may want to restrict the above key sequences to a given terminal (as selected by the $TERM variable). For example, on my system I have: 57 {{{ 58 keyseq: xterm-color "\ESC[5D" ctrl-lefT 59 keyseq: xterm-color "\ESC[5C" ctrl-right 60 keyseq: xterm "\ESC[1;5D" ctrl-left 61 keyseq: xterm "\ESC[1;5C" ctrl-right 62 }}} 63 since `$TERM==xterm-color` means I'm using OS X's Terminal.app program, and `$TERM==xterm` means I'm using the X11 `xterm` program.
