| 1 | FREQUENTLY ASKED QUESTIONS |
1 | FREQUENTLY ASKED QUESTIONS |
|
|
2 | The new selection selects pieces that are too big, how can I select |
|
|
3 | single words? |
|
|
4 | Yes. For example, if you want to select alphanumeric words, you can |
|
|
5 | use the following resource: |
|
|
6 | |
|
|
7 | URxvt.selection.pattern-0: ([[:word:]]+) |
|
|
8 | |
|
|
9 | If you click more than twice, the selection will be extended more |
|
|
10 | and more. |
|
|
11 | |
|
|
12 | To get a selection that is very similar to the old code, try this |
|
|
13 | pattern: |
|
|
14 | |
|
|
15 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
|
|
16 | |
|
|
17 | Please also note that the *LeftClick Shift-LeftClik* combination |
|
|
18 | also selects words like the old code. |
|
|
19 | |
|
|
20 | I don't like the new selection/popups/hotkeys/perl, how do I |
|
|
21 | change/disable it? |
|
|
22 | You can disable the perl extension completely by setting the |
|
|
23 | perl-ext-common resource to the empty string, which also keeps |
|
|
24 | rxvt-unicode from initialising perl, saving memory. |
|
|
25 | |
|
|
26 | If you only want to disable specific features, you first have to |
|
|
27 | identify which perl extension is responsible. For this, read the |
|
|
28 | section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For |
|
|
29 | example, to disable the selection-popup and option-popup, specify |
|
|
30 | this perl-ext-common resource: |
|
|
31 | |
|
|
32 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
33 | |
|
|
34 | This will keep the default extensions, but disable the two popup |
|
|
35 | extensions. Some extensions can also be configured, for example, |
|
|
36 | scrollback search mode is triggered by M-s. You can move it to any |
|
|
37 | other combination either by setting the searchable-scrollback |
|
|
38 | resource: |
|
|
39 | |
|
|
40 | URxvt.searchable-scrollback: CM-s |
|
|
41 | |
| 2 | Isn't rxvt supposed to be small? Don't all those features bloat? |
42 | Isn't rxvt supposed to be small? Don't all those features bloat? |
| 3 | I often get asked about this, and I think, no, they didn't cause |
43 | I often get asked about this, and I think, no, they didn't cause |
| 4 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
44 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
| 5 | can see that the urxvt binary is larger (due to some encoding tables |
45 | can see that the urxvt binary is larger (due to some encoding tables |
| 6 | always being compiled in), but it actually uses less memory (RSS) |
46 | always being compiled in), but it actually uses less memory (RSS) |
| … | |
… | |
| 35 | |
75 | |
| 36 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
76 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
| 37 | this still fares rather well. And compared to some monsters like |
77 | this still fares rather well. And compared to some monsters like |
| 38 | gnome-terminal (21152k + extra 4204k in separate processes) or |
78 | gnome-terminal (21152k + extra 4204k in separate processes) or |
| 39 | konsole (22200k + extra 43180k in daemons that stay around after |
79 | konsole (22200k + extra 43180k in daemons that stay around after |
| 40 | exit, plus half aminute of startup time, including the hundreds of |
80 | exit, plus half a minute of startup time, including the hundreds of |
| 41 | warnings it spits out), it fares extremely well *g*. |
81 | warnings it spits out), it fares extremely well *g*. |
| 42 | |
82 | |
| 43 | Why C++, isn't that unportable/bloated/uncool? |
83 | Why C++, isn't that unportable/bloated/uncool? |
| 44 | Is this a question? :) It comes up very often. The simple answer is: |
84 | Is this a question? :) It comes up very often. The simple answer is: |
| 45 | I had to write it, and C++ allowed me to write and maintain it in a |
85 | I had to write it, and C++ allowed me to write and maintain it in a |
| … | |
… | |
| 127 | |
167 | |
| 128 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
168 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
| 129 | safe? |
169 | safe? |
| 130 | Likely not. While I honestly try to make it secure, and am probably |
170 | Likely not. While I honestly try to make it secure, and am probably |
| 131 | not bad at it, I think it is simply unreasonable to expect all of |
171 | not bad at it, I think it is simply unreasonable to expect all of |
| 132 | freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to |
172 | freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode |
| 133 | all be secure. Also, rxvt-unicode disables some options when it |
173 | itself to all be secure. Also, rxvt-unicode disables some options |
| 134 | detects that it runs setuid or setgid, which is not nice. |
174 | when it detects that it runs setuid or setgid, which is not nice. |
|
|
175 | Besides, with the embedded perl interpreter the possibility for |
|
|
176 | security problems easily multiplies. |
| 135 | |
177 | |
| 136 | Elevated privileges are only required for utmp and pty operations on |
178 | Elevated privileges are only required for utmp and pty operations on |
| 137 | some systems (for example, GNU/Linux doesn't need any extra |
179 | some systems (for example, GNU/Linux doesn't need any extra |
| 138 | privileges for ptys, but some need it for utmp support). If |
180 | privileges for ptys, but some need it for utmp support). It is |
| 139 | rxvt-unicode doesn't support the library/setuid helper that your OS |
181 | planned to mvoe this into a forked handler process, but this is not |
| 140 | needs I'll be happy to assist you in implementing support for it. |
182 | yet done. |
| 141 | |
183 | |
| 142 | So, while setuid/setgid operation is supported and not a problem on |
184 | So, while setuid/setgid operation is supported and not a problem on |
| 143 | your typical single-user-no-other-logins unix desktop, always |
185 | your typical single-user-no-other-logins unix desktop, always |
| 144 | remember that its an awful lot of code, most of which isn't checked |
186 | remember that its an awful lot of code, most of which isn't checked |
| 145 | for security issues regularly. |
187 | for security issues regularly. |
| … | |
… | |
| 591 | Mouse cut/paste suddenly no longer works. |
633 | Mouse cut/paste suddenly no longer works. |
| 592 | Make sure that mouse reporting is actually turned off since killing |
634 | Make sure that mouse reporting is actually turned off since killing |
| 593 | some editors prematurely may leave the mouse in mouse report mode. |
635 | some editors prematurely may leave the mouse in mouse report mode. |
| 594 | I've heard that tcsh may use mouse reporting unless it otherwise |
636 | I've heard that tcsh may use mouse reporting unless it otherwise |
| 595 | specified. A quick check is to see if cut/paste works when the Alt |
637 | specified. A quick check is to see if cut/paste works when the Alt |
| 596 | or Shift keys are depressed. See rxvt(7) |
638 | or Shift keys are depressed. |
| 597 | |
639 | |
| 598 | What's with this bold/blink stuff? |
640 | What's with this bold/blink stuff? |
| 599 | If no bold colour is set via "colorBD:", bold will invert text using |
641 | If no bold colour is set via "colorBD:", bold will invert text using |
| 600 | the standard foreground colour. |
642 | the standard foreground colour. |
| 601 | |
643 | |
| … | |
… | |
| 687 | |
729 | |
| 688 | # use Backspace = ^? |
730 | # use Backspace = ^? |
| 689 | $ stty erase ^? |
731 | $ stty erase ^? |
| 690 | $ rxvt |
732 | $ rxvt |
| 691 | |
733 | |
| 692 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7). |
734 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
| 693 | |
735 | |
| 694 | For an existing rxvt-unicode: |
736 | For an existing rxvt-unicode: |
| 695 | |
737 | |
| 696 | # use Backspace = ^H |
738 | # use Backspace = ^H |
| 697 | $ stty erase ^H |
739 | $ stty erase ^H |
