]>
Commit | Line | Data |
---|---|---|
21a17e09 EZ |
1 | # My ~/.inputrc file is in -*- text -*- for easy editing with Emacs. |
2 | # | |
3 | # Notice the various bindings which are conditionalized depending | |
4 | # on which program is running, or what terminal is active. | |
5 | # | |
6 | ||
7 | # In all programs, all terminals, make sure this is bound. | |
8 | "\C-x\C-r": re-read-init-file | |
9 | ||
10 | # Hp terminals (and some others) have ugly default behaviour for C-h. | |
11 | "\C-h": backward-delete-char | |
12 | "\e\C-h": backward-kill-word | |
13 | "\C-xd": dump-functions | |
14 | ||
15 | # In xterm windows, make the arrow keys do the right thing. | |
16 | $if TERM=xterm | |
17 | "\e[A": previous-history | |
18 | "\e[B": next-history | |
19 | "\e[C": forward-char | |
20 | "\e[D": backward-char | |
21 | ||
22 | # Under Xterm in Bash, we bind local Function keys to do something useful. | |
23 | $if Bash | |
24 | "\e[11~": "Function Key 1" | |
25 | "\e[12~": "Function Key 2" | |
26 | "\e[13~": "Function Key 3" | |
27 | "\e[14~": "Function Key 4" | |
28 | "\e[15~": "Function Key 5" | |
29 | ||
30 | # I know the following escape sequence numbers are 1 greater than | |
31 | # the function key. Don't ask me why, I didn't design the xterm terminal. | |
32 | "\e[17~": "Function Key 6" | |
33 | "\e[18~": "Function Key 7" | |
34 | "\e[19~": "Function Key 8" | |
35 | "\e[20~": "Function Key 9" | |
36 | "\e[21~": "Function Key 10" | |
37 | $endif | |
38 | $endif | |
39 | ||
40 | # For Bash, all terminals, add some Bash specific hacks. | |
41 | $if Bash | |
42 | "\C-xv": show-bash-version | |
43 | "\C-x\C-e": shell-expand-line | |
44 | ||
45 | # Here is one for editing my path. | |
46 | "\C-xp": "$PATH\C-x\C-e\C-e\"\C-aPATH=\":\C-b" | |
47 | ||
48 | # Make C-x r read my mail in emacs. | |
49 | # "\C-xr": "emacs -f rmail\C-j" | |
50 | $endif | |
51 | ||
52 | # For FTP, different hacks: | |
53 | $if Ftp | |
54 | "\C-xg": "get \M-?" | |
55 | "\C-xt": "put \M-?" | |
56 | $endif | |
57 | ||
58 | " ": self-insert |