| … | |
… | |
| 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 | I don't like the new selection/popups/hotkeys/perl, how do I |
|
|
24 | change/disable it? |
|
|
25 | You can disable the perl extension completely by setting the |
|
|
26 | perl-ext-common resource to the empty string, which also keeps |
|
|
27 | rxvt-unicode from initialising perl, saving memory. |
|
|
28 | |
|
|
29 | If you only want to disable specific features, you first have to |
|
|
30 | identify which perl extension is responsible. For this, read the |
|
|
31 | section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For |
|
|
32 | example, to disable the selection-popup and option-popup, specify |
|
|
33 | this perl-ext-common resource: |
|
|
34 | |
|
|
35 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
36 | |
|
|
37 | This will keep the default extensions, but disable the two popup |
|
|
38 | extensions. Some extensions can also be configured, for example, |
|
|
39 | scrollback search mode is triggered by M-s. You can move it to any |
|
|
40 | other combination either by setting the searchable-scrollback |
|
|
41 | resource: |
|
|
42 | |
|
|
43 | URxvt.searchable-scrollback: CM-s |
|
|
44 | |
| 23 | Isn't rxvt supposed to be small? Don't all those features bloat? |
45 | Isn't rxvt supposed to be small? Don't all those features bloat? |
| 24 | I often get asked about this, and I think, no, they didn't cause |
46 | I often get asked about this, and I think, no, they didn't cause |
| 25 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
47 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
| 26 | can see that the urxvt binary is larger (due to some encoding tables |
48 | can see that the urxvt binary is larger (due to some encoding tables |
| 27 | always being compiled in), but it actually uses less memory (RSS) |
49 | always being compiled in), but it actually uses less memory (RSS) |
| … | |
… | |
| 148 | |
170 | |
| 149 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
171 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
| 150 | safe? |
172 | safe? |
| 151 | Likely not. While I honestly try to make it secure, and am probably |
173 | Likely not. While I honestly try to make it secure, and am probably |
| 152 | not bad at it, I think it is simply unreasonable to expect all of |
174 | not bad at it, I think it is simply unreasonable to expect all of |
| 153 | freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to |
175 | freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode |
| 154 | all be secure. Also, rxvt-unicode disables some options when it |
176 | itself to all be secure. Also, rxvt-unicode disables some options |
| 155 | detects that it runs setuid or setgid, which is not nice. |
177 | when it detects that it runs setuid or setgid, which is not nice. |
|
|
178 | Besides, with the embedded perl interpreter the possibility for |
|
|
179 | security problems easily multiplies. |
| 156 | |
180 | |
| 157 | Elevated privileges are only required for utmp and pty operations on |
181 | Elevated privileges are only required for utmp and pty operations on |
| 158 | some systems (for example, GNU/Linux doesn't need any extra |
182 | some systems (for example, GNU/Linux doesn't need any extra |
| 159 | privileges for ptys, but some need it for utmp support). If |
183 | privileges for ptys, but some need it for utmp support). It is |
| 160 | rxvt-unicode doesn't support the library/setuid helper that your OS |
184 | planned to mvoe this into a forked handler process, but this is not |
| 161 | needs I'll be happy to assist you in implementing support for it. |
185 | yet done. |
| 162 | |
186 | |
| 163 | So, while setuid/setgid operation is supported and not a problem on |
187 | So, while setuid/setgid operation is supported and not a problem on |
| 164 | your typical single-user-no-other-logins unix desktop, always |
188 | your typical single-user-no-other-logins unix desktop, always |
| 165 | remember that its an awful lot of code, most of which isn't checked |
189 | remember that its an awful lot of code, most of which isn't checked |
| 166 | for security issues regularly. |
190 | for security issues regularly. |
| … | |
… | |
| 1961 | it. |
1985 | it. |
| 1962 | |
1986 | |
| 1963 | --disable-resources |
1987 | --disable-resources |
| 1964 | Removes any support for resource checking. |
1988 | Removes any support for resource checking. |
| 1965 | |
1989 | |
| 1966 | --enable-xgetdefault |
|
|
| 1967 | Make resources checking via XGetDefault() instead of our small |
|
|
| 1968 | version which only checks ~/.Xdefaults, or if that doesn't exist |
|
|
| 1969 | then ~/.Xresources. |
|
|
| 1970 | |
|
|
| 1971 | Please note that nowadays, things like XIM will automatically pull |
|
|
| 1972 | in and use the full X resource manager, so the overhead of using it |
|
|
| 1973 | might be very small, if nonexistant. |
|
|
| 1974 | |
|
|
| 1975 | --enable-strings (default: off) |
1990 | --enable-strings (default: off) |
| 1976 | Add support for our possibly faster memset() function and other |
1991 | Add support for our possibly faster memset() function and other |
| 1977 | various routines, overriding your system's versions which may have |
1992 | various routines, overriding your system's versions which may have |
| 1978 | been hand-crafted in assembly or may require extra libraries to link |
1993 | been hand-crafted in assembly or may require extra libraries to link |
| 1979 | in. (this breaks ANSI-C rules and has problems on many GNU/Linux |
1994 | in. (this breaks ANSI-C rules and has problems on many GNU/Linux |
