… | |
… | |
18 | The newest version of this document is also available on the World Wide |
18 | The newest version of this document is also available on the World Wide |
19 | Web at |
19 | Web at |
20 | <http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
20 | <http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
21 | |
21 | |
22 | FREQUENTLY ASKED QUESTIONS |
22 | FREQUENTLY ASKED QUESTIONS |
23 | The new selection selects pieces that are too big, how can I select |
23 | The new selection selects pieces that are too big, how can I select single words? |
24 | single words? |
|
|
25 | If you want to select e.g. alphanumeric words, you can use the following |
24 | If you want to select e.g. alphanumeric words, you can use the following |
26 | setting: |
25 | setting: |
27 | |
26 | |
28 | URxvt.selection.pattern-0: ([[:word:]]+) |
27 | URxvt.selection.pattern-0: ([[:word:]]+) |
29 | |
28 | |
… | |
… | |
36 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
35 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
37 | |
36 | |
38 | Please also note that the *LeftClick Shift-LeftClik* combination also |
37 | Please also note that the *LeftClick Shift-LeftClik* combination also |
39 | selects words like the old code. |
38 | selects words like the old code. |
40 | |
39 | |
41 | I don't like the new selection/popups/hotkeys/perl, how do I |
40 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
42 | change/disable it? |
|
|
43 | You can disable the perl extension completely by setting the |
41 | You can disable the perl extension completely by setting the |
44 | perl-ext-common resource to the empty string, which also keeps |
42 | perl-ext-common resource to the empty string, which also keeps |
45 | rxvt-unicode from initialising perl, saving memory. |
43 | rxvt-unicode from initialising perl, saving memory. |
46 | |
44 | |
47 | If you only want to disable specific features, you first have to |
45 | If you only want to disable specific features, you first have to |
… | |
… | |
57 | scrollback search mode is triggered by M-s. You can move it to any other |
55 | scrollback search mode is triggered by M-s. You can move it to any other |
58 | combination either by setting the searchable-scrollback resource: |
56 | combination either by setting the searchable-scrollback resource: |
59 | |
57 | |
60 | URxvt.searchable-scrollback: CM-s |
58 | URxvt.searchable-scrollback: CM-s |
61 | |
59 | |
62 | The cursor moves when selecting text in the current input line, how |
60 | The cursor moves when selecting text in the current input line, how do I switch this off? |
63 | do I switch this off? |
|
|
64 | See next entry. |
61 | See next entry. |
65 | |
62 | |
66 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor |
63 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
67 | outputs strange escape sequences, how do I fix this? |
|
|
68 | These are caused by the "readline" perl extension. Under normal |
64 | These are caused by the "readline" perl extension. Under normal |
69 | circumstances, it will move your cursor around when you click into the |
65 | circumstances, it will move your cursor around when you click into the |
70 | line that contains it. It tries hard not to do this at the wrong moment, |
66 | line that contains it. It tries hard not to do this at the wrong moment, |
71 | but when running a program that doesn't parse cursor movements or in |
67 | but when running a program that doesn't parse cursor movements or in |
72 | some cases during rlogin sessions, it fails to detect this properly. |
68 | some cases during rlogin sessions, it fails to detect this properly. |
… | |
… | |
248 | For other problems that also affect the Debian package, you can and |
244 | For other problems that also affect the Debian package, you can and |
249 | probably should use the Debian BTS, too, because, after all, it's also a |
245 | probably should use the Debian BTS, too, because, after all, it's also a |
250 | bug in the Debian version and it serves as a reminder for other users |
246 | bug in the Debian version and it serves as a reminder for other users |
251 | that might encounter the same issue. |
247 | that might encounter the same issue. |
252 | |
248 | |
253 | I am maintaining rxvt-unicode for distribution/OS XXX, any |
249 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
254 | recommendation? |
|
|
255 | You should build one binary with the default options. configure now |
250 | You should build one binary with the default options. configure now |
256 | enables most useful options, and the trend goes to making them |
251 | enables most useful options, and the trend goes to making them |
257 | runtime-switchable, too, so there is usually no drawback to enbaling |
252 | runtime-switchable, too, so there is usually no drawback to enbaling |
258 | them, except higher disk and possibly memory usage. The perl interpreter |
253 | them, except higher disk and possibly memory usage. The perl interpreter |
259 | should be enabled, as important functionality (menus, selection, likely |
254 | should be enabled, as important functionality (menus, selection, likely |
… | |
… | |
881 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
876 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
882 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
877 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
883 | |
878 | |
884 | See some more examples in the documentation for the keysym resource. |
879 | See some more examples in the documentation for the keysym resource. |
885 | |
880 | |
886 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
881 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize. |
887 | How do I make use of them? For example, the Sun Keyboard type 4 |
|
|
888 | has the following mappings that rxvt-unicode doesn't recognize. |
|
|
889 | KP_Insert == Insert |
882 | KP_Insert == Insert |
890 | F22 == Print |
883 | F22 == Print |
891 | F27 == Home |
884 | F27 == Home |
892 | F29 == Prior |
885 | F29 == Prior |
893 | F33 == End |
886 | F33 == End |
… | |
… | |
895 | |
888 | |
896 | Rather than have rxvt-unicode try to accommodate all the various |
889 | Rather than have rxvt-unicode try to accommodate all the various |
897 | possible keyboard mappings, it is better to use `xmodmap' to remap the |
890 | possible keyboard mappings, it is better to use `xmodmap' to remap the |
898 | keys as required for your particular machine. |
891 | keys as required for your particular machine. |
899 | |
892 | |
900 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
893 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
901 | I need this to decide about setting colors etc. |
|
|
902 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
894 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
903 | check and see if that is set. Note that several programs, JED, slrn, |
895 | check and see if that is set. Note that several programs, JED, slrn, |
904 | Midnight Commander automatically check this variable to decide whether |
896 | Midnight Commander automatically check this variable to decide whether |
905 | or not to use color. |
897 | or not to use color. |
906 | |
898 | |