| 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 |
| … | |
… | |
| 73 | |
113 | |
| 74 | No large bloated libraries (of course, none were linked in |
114 | No large bloated libraries (of course, none were linked in |
| 75 | statically), except maybe libX11 :) |
115 | statically), except maybe libX11 :) |
| 76 | |
116 | |
| 77 | Does it support tabs, can I have a tabbed rxvt-unicode? |
117 | Does it support tabs, can I have a tabbed rxvt-unicode? |
| 78 | rxvt-unicode does not directly support tabs. It will work fine with |
118 | Beginning with version 7.3, there is a perl extension that |
| 79 | tabbing functionality of many window managers or similar tabbing |
119 | implements a simple tabbed terminal. It is installed by default, so |
| 80 | programs, and its embedding-features allow it to be embedded into |
120 | any of these should give you tabs: |
| 81 | other programs, as witnessed by doc/rxvt-tabbed or the upcoming |
121 | |
| 82 | "Gtk2::URxvt" perl module, which features a tabbed urxvt (murxvt) |
122 | rxvt -pe tabbed |
| 83 | terminal as an example embedding application. |
123 | |
|
|
124 | URxvt.perl-ext-common: default,tabbed |
|
|
125 | |
|
|
126 | It will also work fine with tabbing functionality of many window |
|
|
127 | managers or similar tabbing programs, and its embedding-features |
|
|
128 | allow it to be embedded into other programs, as witnessed by |
|
|
129 | doc/rxvt-tabbed or the upcoming "Gtk2::URxvt" perl module, which |
|
|
130 | features a tabbed urxvt (murxvt) terminal as an example embedding |
|
|
131 | application. |
| 84 | |
132 | |
| 85 | How do I know which rxvt-unicode version I'm using? |
133 | How do I know which rxvt-unicode version I'm using? |
| 86 | The version number is displayed with the usage (-h). Also the escape |
134 | The version number is displayed with the usage (-h). Also the escape |
| 87 | sequence "ESC [ 8 n" sets the window title to the version number. |
135 | sequence "ESC [ 8 n" sets the window title to the version number. |
| 88 | When using the rxvtc client, the version displayed is that of the |
136 | When using the rxvtc client, the version displayed is that of the |
| 89 | daemon. |
137 | daemon. |
| 90 | |
138 | |
| 91 | I am using Debian GNU/Linux and have a problem... |
139 | I am using Debian GNU/Linux and have a problem... |
| 92 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
140 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
| 93 | patches that considerably change the behaviour of rxvt-unicode. |
141 | patches that considerably change the behaviour of rxvt-unicode (but |
| 94 | Before reporting a bug to the original rxvt-unicode author please |
142 | unfortunately this notice has been removed). Before reporting a bug |
| 95 | download and install the genuine version |
143 | to the original rxvt-unicode author please download and install the |
| 96 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
144 | genuine version (<http://software.schmorp.de#rxvt-unicode>) and try |
| 97 | problem. If you cannot, chances are that the problems are specific |
145 | to reproduce the problem. If you cannot, chances are that the |
| 98 | to Debian GNU/Linux, in which case it should be reported via the |
146 | problems are specific to Debian GNU/Linux, in which case it should |
| 99 | Debian Bug Tracking System (use "reportbug" to report the bug). |
147 | be reported via the Debian Bug Tracking System (use "reportbug" to |
|
|
148 | report the bug). |
| 100 | |
149 | |
| 101 | For other problems that also affect the Debian package, you can and |
150 | 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 |
151 | 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 |
152 | also a bug in the Debian version and it serves as a reminder for |
| 104 | other users that might encounter the same issue. |
153 | other users that might encounter the same issue. |
| … | |
… | |
| 125 | of encodings built-in that increase download times and are rarely |
174 | of encodings built-in that increase download times and are rarely |
| 126 | used). |
175 | used). |
| 127 | |
176 | |
| 128 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
177 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
| 129 | safe? |
178 | safe? |
| 130 | Likely not. While I honestly try to make it secure, and am probably |
179 | It should be, starting with release 7.1. You are encouraged to |
| 131 | not bad at it, I think it is simply unreasonable to expect all of |
180 | properly install urxvt with privileges necessary for your OS now. |
| 132 | freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to |
|
|
| 133 | all be secure. Also, rxvt-unicode disables some options when it |
|
|
| 134 | detects that it runs setuid or setgid, which is not nice. |
|
|
| 135 | |
181 | |
| 136 | Elevated privileges are only required for utmp and pty operations on |
182 | When rxvt-unicode detects that it runs setuid or setgid, it will |
| 137 | some systems (for example, GNU/Linux doesn't need any extra |
183 | fork into a helper process for privileged operations (pty handling |
| 138 | privileges for ptys, but some need it for utmp support). If |
184 | on some systems, utmp/wtmp/lastlog handling on others) and drop |
| 139 | rxvt-unicode doesn't support the library/setuid helper that your OS |
185 | privileges immediately. This is much safer than most other terminals |
| 140 | needs I'll be happy to assist you in implementing support for it. |
186 | that keep privileges while running (but is more relevant to urxvt, |
|
|
187 | as it contains things as perl interpreters, which might be "helpful" |
|
|
188 | to attackers). |
| 141 | |
189 | |
| 142 | So, while setuid/setgid operation is supported and not a problem on |
190 | This forking is done as the very first within main(), which is very |
| 143 | your typical single-user-no-other-logins unix desktop, always |
191 | early and reduces possible bugs to initialisation code run before |
| 144 | remember that its an awful lot of code, most of which isn't checked |
192 | main(), or things like the dynamic loader of your system, which |
| 145 | for security issues regularly. |
193 | should result in very little risk. |
| 146 | |
194 | |
| 147 | When I log-in to another system it tells me about missing terminfo data? |
195 | When I log-in to another system it tells me about missing terminfo data? |
| 148 | The terminal description used by rxvt-unicode is not as widely |
196 | The terminal description used by rxvt-unicode is not as widely |
| 149 | available as that for xterm, or even rxvt (for which the same |
197 | available as that for xterm, or even rxvt (for which the same |
| 150 | problem often arises). |
198 | problem often arises). |
| … | |
… | |
| 538 | |
586 | |
| 539 | My input method wants <some encoding> but I want UTF-8, what can I do? |
587 | My input method wants <some encoding> but I want UTF-8, what can I do? |
| 540 | You can specify separate locales for the input method and the rest |
588 | You can specify separate locales for the input method and the rest |
| 541 | of the terminal, using the resource "imlocale": |
589 | of the terminal, using the resource "imlocale": |
| 542 | |
590 | |
| 543 | URxvt*imlocale: ja_JP.EUC-JP |
591 | URxvt.imlocale: ja_JP.EUC-JP |
| 544 | |
592 | |
| 545 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
593 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
| 546 | still use your input method. Please note, however, that you will not |
594 | still use your input method. Please note, however, that you will not |
| 547 | be able to input characters outside "EUC-JP" in a normal way then, |
595 | be able to input characters outside "EUC-JP" in a normal way then, |
| 548 | as your input method limits you. |
596 | as your input method limits you. |
| … | |
… | |
| 591 | Mouse cut/paste suddenly no longer works. |
639 | Mouse cut/paste suddenly no longer works. |
| 592 | Make sure that mouse reporting is actually turned off since killing |
640 | Make sure that mouse reporting is actually turned off since killing |
| 593 | some editors prematurely may leave the mouse in mouse report mode. |
641 | some editors prematurely may leave the mouse in mouse report mode. |
| 594 | I've heard that tcsh may use mouse reporting unless it otherwise |
642 | 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 |
643 | specified. A quick check is to see if cut/paste works when the Alt |
| 596 | or Shift keys are depressed. See rxvt(7) |
644 | or Shift keys are depressed. |
| 597 | |
645 | |
| 598 | What's with this bold/blink stuff? |
646 | What's with this bold/blink stuff? |
| 599 | If no bold colour is set via "colorBD:", bold will invert text using |
647 | If no bold colour is set via "colorBD:", bold will invert text using |
| 600 | the standard foreground colour. |
648 | the standard foreground colour. |
| 601 | |
649 | |
| … | |
… | |
| 687 | |
735 | |
| 688 | # use Backspace = ^? |
736 | # use Backspace = ^? |
| 689 | $ stty erase ^? |
737 | $ stty erase ^? |
| 690 | $ rxvt |
738 | $ rxvt |
| 691 | |
739 | |
| 692 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7). |
740 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
| 693 | |
741 | |
| 694 | For an existing rxvt-unicode: |
742 | For an existing rxvt-unicode: |
| 695 | |
743 | |
| 696 | # use Backspace = ^H |
744 | # use Backspace = ^H |
| 697 | $ stty erase ^H |
745 | $ stty erase ^H |
