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 | |
|
|
42 | Why doesn't rxvt-unicode read my resources? |
|
|
43 | Well, why, indeed? It does, in a way very similar to other X |
|
|
44 | applications. Most importantly, this means that if you or your OS |
|
|
45 | loads resources into the X display (the right way to do it), |
|
|
46 | rxvt-unicode will ignore any resource files in your home directory. |
|
|
47 | It will only read $HOME/.Xdefaults when no resources are attached to |
|
|
48 | the display. |
|
|
49 | |
|
|
50 | If you have or use an $HOME/.Xresources file, chances are that |
|
|
51 | resources are loaded into your X-server. In this case, you have to |
|
|
52 | re-login after every change (or run xrdb -merge $HOME/.Xresources). |
|
|
53 | |
|
|
54 | Also consider the form resources have to use: |
|
|
55 | |
|
|
56 | URxvt.resource: value |
|
|
57 | |
|
|
58 | If you want to use another form (there are lots of different ways of |
|
|
59 | specifying resources), make sure you understand wether and why it |
|
|
60 | works. If unsure, use the form above. |
|
|
61 | |
|
|
62 | I can't get transparency working, what am I doing wrong? |
|
|
63 | First of all, transparency isn't officially supported in |
|
|
64 | rxvt-unicode, so you are mostly on your own. Do not bug the author |
|
|
65 | about it (but you may bug everybody else). Also, if you can't get it |
|
|
66 | working consider it a rite of passage: ... and you failed. |
|
|
67 | |
|
|
68 | Here are four ways to get transparency. Do read the manpage and |
|
|
69 | option descriptions for the programs mentioned and rxvt-unicode. |
|
|
70 | Really, do it! |
|
|
71 | |
|
|
72 | 1. Use inheritPixmap: |
|
|
73 | |
|
|
74 | Esetroot wallpaper.jpg |
|
|
75 | rxvt -ip -tint red -sh 40 |
|
|
76 | |
|
|
77 | That works. If you think it doesn't, you lack transparency and |
|
|
78 | tinting support, or you are unable to read. |
|
|
79 | |
|
|
80 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables |
|
|
81 | you to use effects other than tinting and shading: Just |
|
|
82 | shade/tint/whatever your picture with gimp: |
|
|
83 | |
|
|
84 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
85 | rxvt -pixmap background.xpm -pe automove-background |
|
|
86 | |
|
|
87 | That works. If you think it doesn't, you lack XPM and Perl support, |
|
|
88 | or you are unable to read. |
|
|
89 | |
|
|
90 | 3. Use an ARGB visual: |
|
|
91 | |
|
|
92 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
|
|
93 | |
|
|
94 | This requires XFT support, and the support of your X-server. If that |
|
|
95 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals |
|
|
96 | aren't there yet, no matter what they claim. Rxvt-Unicode contains |
|
|
97 | the neccessary bugfixes and workarounds for Xft and Xlib to make it |
|
|
98 | work, but that doesn't mean that your WM has the required kludges in |
|
|
99 | place. |
|
|
100 | |
|
|
101 | 4. Use xcompmgr and let it do the job: |
|
|
102 | |
|
|
103 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
104 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
105 | |
|
|
106 | Then click on a window you want to make transparent. Replace |
|
|
107 | 0xc0000000 by other values to change the degree of opacity. If it |
|
|
108 | doesn't work and your server crashes, you got to keep the pieces. |
|
|
109 | |
2 | Isn't rxvt supposed to be small? Don't all those features bloat? |
110 | 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 |
111 | 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 |
112 | 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 |
113 | 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) |
114 | always being compiled in), but it actually uses less memory (RSS) |
… | |
… | |
35 | |
143 | |
36 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
144 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
37 | this still fares rather well. And compared to some monsters like |
145 | this still fares rather well. And compared to some monsters like |
38 | gnome-terminal (21152k + extra 4204k in separate processes) or |
146 | gnome-terminal (21152k + extra 4204k in separate processes) or |
39 | konsole (22200k + extra 43180k in daemons that stay around after |
147 | konsole (22200k + extra 43180k in daemons that stay around after |
40 | exit, plus half aminute of startup time, including the hundreds of |
148 | exit, plus half a minute of startup time, including the hundreds of |
41 | warnings it spits out), it fares extremely well *g*. |
149 | warnings it spits out), it fares extremely well *g*. |
42 | |
150 | |
43 | Why C++, isn't that unportable/bloated/uncool? |
151 | Why C++, isn't that unportable/bloated/uncool? |
44 | Is this a question? :) It comes up very often. The simple answer is: |
152 | 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 |
153 | I had to write it, and C++ allowed me to write and maintain it in a |
… | |
… | |
73 | |
181 | |
74 | No large bloated libraries (of course, none were linked in |
182 | No large bloated libraries (of course, none were linked in |
75 | statically), except maybe libX11 :) |
183 | statically), except maybe libX11 :) |
76 | |
184 | |
77 | Does it support tabs, can I have a tabbed rxvt-unicode? |
185 | Does it support tabs, can I have a tabbed rxvt-unicode? |
78 | rxvt-unicode does not directly support tabs. It will work fine with |
186 | Beginning with version 7.3, there is a perl extension that |
79 | tabbing functionality of many window managers or similar tabbing |
187 | implements a simple tabbed terminal. It is installed by default, so |
80 | programs, and its embedding-features allow it to be embedded into |
188 | any of these should give you tabs: |
81 | other programs, as witnessed by doc/rxvt-tabbed or the upcoming |
189 | |
82 | "Gtk2::URxvt" perl module, which features a tabbed urxvt (murxvt) |
190 | rxvt -pe tabbed |
83 | terminal as an example embedding application. |
191 | |
|
|
192 | URxvt.perl-ext-common: default,tabbed |
|
|
193 | |
|
|
194 | It will also work fine with tabbing functionality of many window |
|
|
195 | managers or similar tabbing programs, and its embedding-features |
|
|
196 | allow it to be embedded into other programs, as witnessed by |
|
|
197 | doc/rxvt-tabbed or the upcoming "Gtk2::URxvt" perl module, which |
|
|
198 | features a tabbed urxvt (murxvt) terminal as an example embedding |
|
|
199 | application. |
84 | |
200 | |
85 | How do I know which rxvt-unicode version I'm using? |
201 | How do I know which rxvt-unicode version I'm using? |
86 | The version number is displayed with the usage (-h). Also the escape |
202 | 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. |
203 | 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 |
204 | When using the rxvtc client, the version displayed is that of the |
89 | daemon. |
205 | daemon. |
90 | |
206 | |
91 | I am using Debian GNU/Linux and have a problem... |
207 | I am using Debian GNU/Linux and have a problem... |
92 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
208 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
93 | patches that considerably change the behaviour of rxvt-unicode. |
209 | patches that considerably change the behaviour of rxvt-unicode (but |
94 | Before reporting a bug to the original rxvt-unicode author please |
210 | unfortunately this notice has been removed). Before reporting a bug |
95 | download and install the genuine version |
211 | to the original rxvt-unicode author please download and install the |
96 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
212 | genuine version (<http://software.schmorp.de#rxvt-unicode>) and try |
97 | problem. If you cannot, chances are that the problems are specific |
213 | 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 |
214 | problems are specific to Debian GNU/Linux, in which case it should |
99 | Debian Bug Tracking System (use "reportbug" to report the bug). |
215 | be reported via the Debian Bug Tracking System (use "reportbug" to |
|
|
216 | report the bug). |
100 | |
217 | |
101 | For other problems that also affect the Debian package, you can and |
218 | 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 |
219 | 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 |
220 | also a bug in the Debian version and it serves as a reminder for |
104 | other users that might encounter the same issue. |
221 | other users that might encounter the same issue. |
|
|
222 | |
|
|
223 | I am maintaining rxvt-unicode for distribution/OS XXX, any |
|
|
224 | recommendation? |
|
|
225 | You should build one binary with the default options. configure now |
|
|
226 | enables most useful options, and the trend goes to making them |
|
|
227 | runtime-switchable, too, so there is usually no drawback to enbaling |
|
|
228 | them, except higher disk and possibly memory usage. The perl |
|
|
229 | interpreter should be enabled, as important functionality (menus, |
|
|
230 | selection, likely more in the future) depends on it. |
|
|
231 | |
|
|
232 | You should not overwrite the "perl-ext-common" snd "perl-ext" |
|
|
233 | resources system-wide (except maybe with "defaults"). This will |
|
|
234 | result in useful behaviour. If your distribution aims at low memory, |
|
|
235 | add an empty "perl-ext-common" resource to the app-defaults file. |
|
|
236 | This will keep the perl interpreter disabled until the user enables |
|
|
237 | it. |
|
|
238 | |
|
|
239 | If you can/want build more binaries, I recommend building a minimal |
|
|
240 | one with "--disable-everything" (very useful) and a maximal one with |
|
|
241 | "--enable-everything" (less useful, it will be very big due to a lot |
|
|
242 | of encodings built-in that increase download times and are rarely |
|
|
243 | used). |
|
|
244 | |
|
|
245 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
|
|
246 | safe? |
|
|
247 | It should be, starting with release 7.1. You are encouraged to |
|
|
248 | properly install urxvt with privileges necessary for your OS now. |
|
|
249 | |
|
|
250 | When rxvt-unicode detects that it runs setuid or setgid, it will |
|
|
251 | fork into a helper process for privileged operations (pty handling |
|
|
252 | on some systems, utmp/wtmp/lastlog handling on others) and drop |
|
|
253 | privileges immediately. This is much safer than most other terminals |
|
|
254 | that keep privileges while running (but is more relevant to urxvt, |
|
|
255 | as it contains things as perl interpreters, which might be "helpful" |
|
|
256 | to attackers). |
|
|
257 | |
|
|
258 | This forking is done as the very first within main(), which is very |
|
|
259 | early and reduces possible bugs to initialisation code run before |
|
|
260 | main(), or things like the dynamic loader of your system, which |
|
|
261 | should result in very little risk. |
105 | |
262 | |
106 | When I log-in to another system it tells me about missing terminfo data? |
263 | 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 |
264 | The terminal description used by rxvt-unicode is not as widely |
108 | available as that for xterm, or even rxvt (for which the same |
265 | available as that for xterm, or even rxvt (for which the same |
109 | problem often arises). |
266 | problem often arises). |
… | |
… | |
497 | |
654 | |
498 | My input method wants <some encoding> but I want UTF-8, what can I do? |
655 | My input method wants <some encoding> but I want UTF-8, what can I do? |
499 | You can specify separate locales for the input method and the rest |
656 | You can specify separate locales for the input method and the rest |
500 | of the terminal, using the resource "imlocale": |
657 | of the terminal, using the resource "imlocale": |
501 | |
658 | |
502 | URxvt*imlocale: ja_JP.EUC-JP |
659 | URxvt.imlocale: ja_JP.EUC-JP |
503 | |
660 | |
504 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
661 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
505 | still use your input method. Please note, however, that you will not |
662 | still use your input method. Please note, however, that you will not |
506 | be able to input characters outside "EUC-JP" in a normal way then, |
663 | be able to input characters outside "EUC-JP" in a normal way then, |
507 | as your input method limits you. |
664 | as your input method limits you. |
… | |
… | |
550 | Mouse cut/paste suddenly no longer works. |
707 | Mouse cut/paste suddenly no longer works. |
551 | Make sure that mouse reporting is actually turned off since killing |
708 | Make sure that mouse reporting is actually turned off since killing |
552 | some editors prematurely may leave the mouse in mouse report mode. |
709 | some editors prematurely may leave the mouse in mouse report mode. |
553 | I've heard that tcsh may use mouse reporting unless it otherwise |
710 | 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 |
711 | specified. A quick check is to see if cut/paste works when the Alt |
555 | or Shift keys are depressed. See rxvt(7) |
712 | or Shift keys are depressed. |
556 | |
713 | |
557 | What's with this bold/blink stuff? |
714 | What's with this bold/blink stuff? |
558 | If no bold colour is set via "colorBD:", bold will invert text using |
715 | If no bold colour is set via "colorBD:", bold will invert text using |
559 | the standard foreground colour. |
716 | the standard foreground colour. |
560 | |
717 | |
… | |
… | |
646 | |
803 | |
647 | # use Backspace = ^? |
804 | # use Backspace = ^? |
648 | $ stty erase ^? |
805 | $ stty erase ^? |
649 | $ rxvt |
806 | $ rxvt |
650 | |
807 | |
651 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7). |
808 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
652 | |
809 | |
653 | For an existing rxvt-unicode: |
810 | For an existing rxvt-unicode: |
654 | |
811 | |
655 | # use Backspace = ^H |
812 | # use Backspace = ^H |
656 | $ stty erase ^H |
813 | $ stty erase ^H |