Changes between Version 2 and Version 3 of CustomKeyBindings

Show
Ignore:
Timestamp:
12/08/08 17:12:20 (6 years ago)
Author:
judah (IP: 76.170.234.70)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CustomKeyBindings

    v2 v3  
    22 
    33As 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) 
    54 - {{{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) 
    66 
    7 where {{{<string>}}} is a Haskell string and {{{<key>}}} is either: 
     7where {{{<term>}}} is a terminal name (optional), {{{<string>}}} is Haskell string syntax, and {{{<key>}}} is either: 
    88 - a single character 
    99 - `f<n>` (a function key) 
     
    5454}}} 
    5555 
     56Finally, 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{{{ 
     58keyseq: xterm-color "\ESC[5D" ctrl-lefT 
     59keyseq: xterm-color "\ESC[5C" ctrl-right 
     60keyseq: xterm "\ESC[1;5D" ctrl-left 
     61keyseq: xterm "\ESC[1;5C" ctrl-right 
     62}}} 
     63since `$TERM==xterm-color` means I'm using OS X's Terminal.app program, and `$TERM==xterm` means I'm using the X11 `xterm` program.