1 | FREQUENTLY ASKED QUESTIONS |
1 | FREQUENTLY ASKED QUESTIONS |
|
|
2 | The new selection selects pieces that are too big/too small, can I |
|
|
3 | change this? |
|
|
4 | Yes. For example, if you want to select smaller pieces ("words") you |
|
|
5 | can 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 | I don't like the new selection/popups/hotkeys/perl, how do I |
|
|
18 | change/disable it? |
|
|
19 | You can disable the perl extension completely by setting the |
|
|
20 | perl-ext-common resource to the empty string, which also keeps |
|
|
21 | rxvt-unicode from initialising perl, saving memory. |
|
|
22 | |
|
|
23 | If you only want to disable specific features, you first have to |
|
|
24 | identify which perl extension is responsible. For this, read the |
|
|
25 | section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For |
|
|
26 | example, to disable the selection-popup and option-popup, specify |
|
|
27 | this perl-ext-common resource: |
|
|
28 | |
|
|
29 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
30 | |
|
|
31 | This will keep the default extensions, but disable the two popup |
|
|
32 | extensions. Some extensions can also be configured, for example, |
|
|
33 | scrollback search mode is triggered by M-s. You can move it to any |
|
|
34 | other combination either by setting the searchable-scrollback |
|
|
35 | resource: |
|
|
36 | |
|
|
37 | URxvt.searchable-scrollback: CM-s |
|
|
38 | |
2 | Isn't rxvt supposed to be small? Don't all those features bloat? |
39 | 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 |
40 | 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 |
41 | 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 |
42 | 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) |
43 | always being compiled in), but it actually uses less memory (RSS) |
… | |
… | |
35 | |
72 | |
36 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
73 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
37 | this still fares rather well. And compared to some monsters like |
74 | this still fares rather well. And compared to some monsters like |
38 | gnome-terminal (21152k + extra 4204k in separate processes) or |
75 | gnome-terminal (21152k + extra 4204k in separate processes) or |
39 | konsole (22200k + extra 43180k in daemons that stay around after |
76 | konsole (22200k + extra 43180k in daemons that stay around after |
40 | exit, plus half aminute of startup time, including the hundreds of |
77 | exit, plus half a minute of startup time, including the hundreds of |
41 | warnings it spits out), it fares extremely well *g*. |
78 | warnings it spits out), it fares extremely well *g*. |
42 | |
79 | |
43 | Why C++, isn't that unportable/bloated/uncool? |
80 | Why C++, isn't that unportable/bloated/uncool? |
44 | Is this a question? :) It comes up very often. The simple answer is: |
81 | 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 |
82 | I had to write it, and C++ allowed me to write and maintain it in a |
… | |
… | |
127 | |
164 | |
128 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
165 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
129 | safe? |
166 | safe? |
130 | Likely not. While I honestly try to make it secure, and am probably |
167 | 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 |
168 | not bad at it, I think it is simply unreasonable to expect all of |
132 | freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to |
169 | freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode |
133 | all be secure. Also, rxvt-unicode disables some options when it |
170 | itself to all be secure. Also, rxvt-unicode disables some options |
134 | detects that it runs setuid or setgid, which is not nice. |
171 | when it detects that it runs setuid or setgid, which is not nice. |
|
|
172 | Besides, with the embedded perl interpreter the possibility for |
|
|
173 | security problems easily multiplies. |
135 | |
174 | |
136 | Elevated privileges are only required for utmp and pty operations on |
175 | Elevated privileges are only required for utmp and pty operations on |
137 | some systems (for example, GNU/Linux doesn't need any extra |
176 | some systems (for example, GNU/Linux doesn't need any extra |
138 | privileges for ptys, but some need it for utmp support). If |
177 | 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 |
178 | 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. |
179 | yet done. |
141 | |
180 | |
142 | So, while setuid/setgid operation is supported and not a problem on |
181 | So, while setuid/setgid operation is supported and not a problem on |
143 | your typical single-user-no-other-logins unix desktop, always |
182 | 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 |
183 | remember that its an awful lot of code, most of which isn't checked |
145 | for security issues regularly. |
184 | for security issues regularly. |