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 urxvtperl(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 |
… | |
… | |
100 | |
140 | |
101 | For other problems that also affect the Debian package, you can and |
141 | For other problems that also affect the Debian package, you can and |
102 | probably should use the Debian BTS, too, because, after all, it's |
142 | probably should use the Debian BTS, too, because, after all, it's |
103 | also a bug in the Debian version and it serves as a reminder for |
143 | also a bug in the Debian version and it serves as a reminder for |
104 | other users that might encounter the same issue. |
144 | other users that might encounter the same issue. |
|
|
145 | |
|
|
146 | I am maintaining rxvt-unicode for distribution/OS XXX, any |
|
|
147 | recommendation? |
|
|
148 | You should build one binary with the default options. configure now |
|
|
149 | enables most useful options, and the trend goes to making them |
|
|
150 | runtime-switchable, too, so there is usually no drawback to enbaling |
|
|
151 | them, except higher disk and possibly memory usage. The perl |
|
|
152 | interpreter should be enabled, as important functionality (menus, |
|
|
153 | selection, likely more in the future) depends on it. |
|
|
154 | |
|
|
155 | You should not overwrite the "perl-ext-common" snd "perl-ext" |
|
|
156 | resources system-wide (except maybe with "defaults"). This will |
|
|
157 | result in useful behaviour. If your distribution aims at low memory, |
|
|
158 | add an empty "perl-ext-common" resource to the app-defaults file. |
|
|
159 | This will keep the perl interpreter disabled until the user enables |
|
|
160 | it. |
|
|
161 | |
|
|
162 | If you can/want build more binaries, I recommend building a minimal |
|
|
163 | one with "--disable-everything" (very useful) and a maximal one with |
|
|
164 | "--enable-everything" (less useful, it will be very big due to a lot |
|
|
165 | of encodings built-in that increase download times and are rarely |
|
|
166 | used). |
|
|
167 | |
|
|
168 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
|
|
169 | safe? |
|
|
170 | Likely not. While I honestly try to make it secure, and am probably |
|
|
171 | not bad at it, I think it is simply unreasonable to expect all of |
|
|
172 | freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode |
|
|
173 | itself to all be secure. Also, rxvt-unicode disables some options |
|
|
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. |
|
|
177 | |
|
|
178 | Elevated privileges are only required for utmp and pty operations on |
|
|
179 | some systems (for example, GNU/Linux doesn't need any extra |
|
|
180 | privileges for ptys, but some need it for utmp support). It is |
|
|
181 | planned to mvoe this into a forked handler process, but this is not |
|
|
182 | yet done. |
|
|
183 | |
|
|
184 | So, while setuid/setgid operation is supported and not a problem on |
|
|
185 | your typical single-user-no-other-logins unix desktop, always |
|
|
186 | remember that its an awful lot of code, most of which isn't checked |
|
|
187 | for security issues regularly. |
105 | |
188 | |
106 | When I log-in to another system it tells me about missing terminfo data? |
189 | When I log-in to another system it tells me about missing terminfo data? |
107 | The terminal description used by rxvt-unicode is not as widely |
190 | The terminal description used by rxvt-unicode is not as widely |
108 | available as that for xterm, or even rxvt (for which the same |
191 | available as that for xterm, or even rxvt (for which the same |
109 | problem often arises). |
192 | problem often arises). |
… | |
… | |
550 | Mouse cut/paste suddenly no longer works. |
633 | Mouse cut/paste suddenly no longer works. |
551 | Make sure that mouse reporting is actually turned off since killing |
634 | Make sure that mouse reporting is actually turned off since killing |
552 | some editors prematurely may leave the mouse in mouse report mode. |
635 | some editors prematurely may leave the mouse in mouse report mode. |
553 | 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 |
554 | 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 |
555 | or Shift keys are depressed. See urxvt(7) |
638 | or Shift keys are depressed. |
556 | |
639 | |
557 | What's with this bold/blink stuff? |
640 | What's with this bold/blink stuff? |
558 | 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 |
559 | the standard foreground colour. |
642 | the standard foreground colour. |
560 | |
643 | |
… | |
… | |
646 | |
729 | |
647 | # use Backspace = ^? |
730 | # use Backspace = ^? |
648 | $ stty erase ^? |
731 | $ stty erase ^? |
649 | $ urxvt |
732 | $ urxvt |
650 | |
733 | |
651 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7). |
734 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
652 | |
735 | |
653 | For an existing rxvt-unicode: |
736 | For an existing rxvt-unicode: |
654 | |
737 | |
655 | # use Backspace = ^H |
738 | # use Backspace = ^H |
656 | $ stty erase ^H |
739 | $ stty erase ^H |