| 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 | If you want to select e.g. alphanumeric words, you can use the following |
|
|
5 | setting: |
|
|
6 | |
|
|
7 | URxvt.selection.pattern-0: ([[:word:]]+) |
|
|
8 | |
|
|
9 | If you click more than twice, the selection will be extended more and |
|
|
10 | 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 also |
|
|
18 | 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 section |
|
|
28 | PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For example, to |
|
|
29 | disable the selection-popup and option-popup, specify this |
|
|
30 | 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 other |
|
|
37 | combination either by setting the searchable-scrollback resource: |
|
|
38 | |
|
|
39 | URxvt.searchable-scrollback: CM-s |
|
|
40 | |
|
|
41 | The cursor moves when selecting text in the current input line, how |
|
|
42 | do I switch this off? |
|
|
43 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor |
|
|
44 | outputs strange escape sequences, how do I fix this? |
|
|
45 | These are caused by the "readline" perl extension. Under normal |
|
|
46 | circumstances, it will move your cursor around when you click into the |
|
|
47 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
48 | but when running a program that doesn't parse cursor movements or in |
|
|
49 | some cases during rlogin sessions, it fails to detect this properly. |
|
|
50 | |
|
|
51 | You can permamently switch this feature off by disabling the "readline" |
|
|
52 | extension: |
|
|
53 | |
|
|
54 | URxvt.perl-ext-common: default,-readline |
|
|
55 | |
|
|
56 | Why doesn't rxvt-unicode read my resources? |
|
|
57 | Well, why, indeed? It does, in a way very similar to other X |
|
|
58 | applications. Most importantly, this means that if you or your OS loads |
|
|
59 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
60 | ignore any resource files in your home directory. It will only read |
|
|
61 | $HOME/.Xdefaults when no resources are attached to the display. |
|
|
62 | |
|
|
63 | If you have or use an $HOME/.Xresources file, chances are that resources |
|
|
64 | are loaded into your X-server. In this case, you have to re-login after |
|
|
65 | every change (or run xrdb -merge $HOME/.Xresources). |
|
|
66 | |
|
|
67 | Also consider the form resources have to use: |
|
|
68 | |
|
|
69 | URxvt.resource: value |
|
|
70 | |
|
|
71 | If you want to use another form (there are lots of different ways of |
|
|
72 | specifying resources), make sure you understand wether and why it works. |
|
|
73 | If unsure, use the form above. |
|
|
74 | |
|
|
75 | I can't get transparency working, what am I doing wrong? |
|
|
76 | First of all, transparency isn't officially supported in rxvt-unicode, |
|
|
77 | so you are mostly on your own. Do not bug the author about it (but you |
|
|
78 | may bug everybody else). Also, if you can't get it working consider it a |
|
|
79 | rite of passage: ... and you failed. |
|
|
80 | |
|
|
81 | Here are four ways to get transparency. Do read the manpage and option |
|
|
82 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
|
|
83 | |
|
|
84 | 1. Use inheritPixmap: |
|
|
85 | |
|
|
86 | Esetroot wallpaper.jpg |
|
|
87 | rxvt -ip -tint red -sh 40 |
|
|
88 | |
|
|
89 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
90 | support, or you are unable to read. |
|
|
91 | |
|
|
92 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
|
|
93 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
94 | your picture with gimp: |
|
|
95 | |
|
|
96 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
97 | rxvt -pixmap background.xpm -pe automove-background |
|
|
98 | |
|
|
99 | That works. If you think it doesn't, you lack XPM and Perl support, or |
|
|
100 | you are unable to read. |
|
|
101 | |
|
|
102 | 3. Use an ARGB visual: |
|
|
103 | |
|
|
104 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
|
|
105 | |
|
|
106 | This requires XFT support, and the support of your X-server. If that |
|
|
107 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
108 | there yet, no matter what they claim. Rxvt-Unicode contains the |
|
|
109 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
|
|
110 | but that doesn't mean that your WM has the required kludges in place. |
|
|
111 | |
|
|
112 | 4. Use xcompmgr and let it do the job: |
|
|
113 | |
|
|
114 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
115 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
116 | |
|
|
117 | Then click on a window you want to make transparent. Replace 0xc0000000 |
|
|
118 | by other values to change the degree of opacity. If it doesn't work and |
|
|
119 | your server crashes, you got to keep the pieces. |
|
|
120 | |
| 2 | Isn't rxvt supposed to be small? Don't all those features bloat? |
121 | 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 |
122 | I often get asked about this, and I think, no, they didn't cause extra |
| 4 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
123 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
| 5 | can see that the urxvt binary is larger (due to some encoding tables |
124 | that the urxvt binary is larger (due to some encoding tables always |
| 6 | always being compiled in), but it actually uses less memory (RSS) |
125 | being compiled in), but it actually uses less memory (RSS) after |
| 7 | after startup. Even with "--disable-everything", this comparison is |
126 | startup. Even with "--disable-everything", this comparison is a bit |
| 8 | a bit unfair, as many features unique to urxvt (locale, encoding |
127 | unfair, as many features unique to urxvt (locale, encoding conversion, |
| 9 | conversion, iso14755 etc.) are already in use in this mode. |
128 | iso14755 etc.) are already in use in this mode. |
| 10 | |
129 | |
| 11 | text data bss drs rss filename |
130 | text data bss drs rss filename |
| 12 | 98398 1664 24 15695 1824 rxvt --disable-everything |
131 | 98398 1664 24 15695 1824 rxvt --disable-everything |
| 13 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
132 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
| 14 | |
133 | |
| 15 | When you "--enable-everything" (which _is_ unfair, as this involves |
134 | When you "--enable-everything" (which _is_ unfair, as this involves xft |
| 16 | xft and full locale/XIM support which are quite bloaty inside libX11 |
135 | and full locale/XIM support which are quite bloaty inside libX11 and my |
| 17 | and my libc), the two diverge, but not unreasnobaly so. |
136 | libc), the two diverge, but not unreasnobaly so. |
| 18 | |
137 | |
| 19 | text data bss drs rss filename |
138 | text data bss drs rss filename |
| 20 | 163431 2152 24 20123 2060 rxvt --enable-everything |
139 | 163431 2152 24 20123 2060 rxvt --enable-everything |
| 21 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
140 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
| 22 | |
141 | |
| 23 | The very large size of the text section is explained by the |
142 | The very large size of the text section is explained by the east-asian |
| 24 | east-asian encoding tables, which, if unused, take up disk space but |
143 | encoding tables, which, if unused, take up disk space but nothing else |
| 25 | nothing else and can be compiled out unless you rely on X11 core |
144 | and can be compiled out unless you rely on X11 core fonts that use those |
| 26 | fonts that use those encodings. The BSS size comes from the 64k |
145 | encodings. The BSS size comes from the 64k emergency buffer that my c++ |
| 27 | emergency buffer that my c++ compiler allocates (but of course |
146 | compiler allocates (but of course doesn't use unless you are out of |
| 28 | doesn't use unless you are out of memory). Also, using an xft font |
147 | memory). Also, using an xft font instead of a core font immediately adds |
| 29 | instead of a core font immediately adds a few megabytes of RSS. Xft |
148 | a few megabytes of RSS. Xft indeed is responsible for a lot of RSS even |
| 30 | indeed is responsible for a lot of RSS even when not used. |
149 | when not used. |
| 31 | |
150 | |
| 32 | Of course, due to every character using two or four bytes instead of |
151 | Of course, due to every character using two or four bytes instead of |
| 33 | one, a large scrollback buffer will ultimately make rxvt-unicode use |
152 | one, a large scrollback buffer will ultimately make rxvt-unicode use |
| 34 | more memory. |
153 | more memory. |
| 35 | |
154 | |
| 36 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
155 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
| 37 | this still fares rather well. And compared to some monsters like |
156 | still fares rather well. And compared to some monsters like |
| 38 | gnome-terminal (21152k + extra 4204k in separate processes) or |
157 | gnome-terminal (21152k + extra 4204k in separate processes) or konsole |
| 39 | konsole (22200k + extra 43180k in daemons that stay around after |
158 | (22200k + extra 43180k in daemons that stay around after exit, plus half |
| 40 | exit, plus half aminute of startup time, including the hundreds of |
159 | a minute of startup time, including the hundreds of warnings it spits |
| 41 | warnings it spits out), it fares extremely well *g*. |
160 | out), it fares extremely well *g*. |
| 42 | |
161 | |
| 43 | Why C++, isn't that unportable/bloated/uncool? |
162 | Why C++, isn't that unportable/bloated/uncool? |
| 44 | Is this a question? :) It comes up very often. The simple answer is: |
163 | Is this a question? :) It comes up very often. The simple answer is: I |
| 45 | I had to write it, and C++ allowed me to write and maintain it in a |
164 | had to write it, and C++ allowed me to write and maintain it in a |
| 46 | fraction of the time and effort (which is a scarce resource for me). |
165 | fraction of the time and effort (which is a scarce resource for me). Put |
| 47 | Put even shorter: It simply wouldn't exist without C++. |
166 | even shorter: It simply wouldn't exist without C++. |
| 48 | |
167 | |
| 49 | My personal stance on this is that C++ is less portable than C, but |
168 | My personal stance on this is that C++ is less portable than C, but in |
| 50 | in the case of rxvt-unicode this hardly matters, as its portability |
169 | the case of rxvt-unicode this hardly matters, as its portability limits |
| 51 | limits are defined by things like X11, pseudo terminals, locale |
170 | are defined by things like X11, pseudo terminals, locale support and |
| 52 | support and unix domain sockets, which are all less portable than |
171 | unix domain sockets, which are all less portable than C++ itself. |
| 53 | C++ itself. |
|
|
| 54 | |
172 | |
| 55 | Regarding the bloat, see the above question: It's easy to write |
173 | Regarding the bloat, see the above question: It's easy to write programs |
| 56 | programs in C that use gobs of memory, an certainly possible to |
174 | in C that use gobs of memory, an certainly possible to write programs in |
| 57 | write programs in C++ that don't. C++ also often comes with large |
175 | C++ that don't. C++ also often comes with large libraries, but this is |
| 58 | libraries, but this is not necessarily the case with GCC. Here is |
176 | not necessarily the case with GCC. Here is what rxvt links against on my |
| 59 | what rxvt links against on my system with a minimal config: |
177 | system with a minimal config: |
| 60 | |
178 | |
| 61 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
179 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
| 62 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
180 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
| 63 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
181 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
| 64 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
182 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
| 65 | |
183 | |
| 66 | And here is rxvt-unicode: |
184 | And here is rxvt-unicode: |
| 67 | |
185 | |
| 68 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
186 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
| 69 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
187 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
| 70 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
188 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
| 71 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
189 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
| 72 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
190 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
| 73 | |
191 | |
| 74 | No large bloated libraries (of course, none were linked in |
192 | No large bloated libraries (of course, none were linked in statically), |
| 75 | statically), except maybe libX11 :) |
193 | except maybe libX11 :) |
| 76 | |
194 | |
| 77 | Does it support tabs, can I have a tabbed rxvt-unicode? |
195 | Does it support tabs, can I have a tabbed rxvt-unicode? |
| 78 | rxvt-unicode does not directly support tabs. It will work fine with |
196 | Beginning with version 7.3, there is a perl extension that implements a |
| 79 | tabbing functionality of many window managers or similar tabbing |
197 | simple tabbed terminal. It is installed by default, so any of these |
| 80 | programs, and its embedding-features allow it to be embedded into |
198 | should give you tabs: |
| 81 | other programs, as witnessed by doc/rxvt-tabbed or the upcoming |
199 | |
|
|
200 | rxvt -pe tabbed |
|
|
201 | |
|
|
202 | URxvt.perl-ext-common: default,tabbed |
|
|
203 | |
|
|
204 | It will also work fine with tabbing functionality of many window |
|
|
205 | managers or similar tabbing programs, and its embedding-features allow |
|
|
206 | it to be embedded into other programs, as witnessed by doc/rxvt-tabbed |
| 82 | "Gtk2::URxvt" perl module, which features a tabbed urxvt (murxvt) |
207 | or the upcoming "Gtk2::URxvt" perl module, which features a tabbed urxvt |
| 83 | terminal as an example embedding application. |
208 | (murxvt) terminal as an example embedding application. |
| 84 | |
209 | |
| 85 | How do I know which rxvt-unicode version I'm using? |
210 | How do I know which rxvt-unicode version I'm using? |
| 86 | The version number is displayed with the usage (-h). Also the escape |
211 | 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. |
212 | sequence "ESC [ 8 n" sets the window title to the version number. When |
| 88 | When using the rxvtc client, the version displayed is that of the |
213 | using the rxvtc client, the version displayed is that of the daemon. |
| 89 | daemon. |
|
|
| 90 | |
214 | |
| 91 | I am using Debian GNU/Linux and have a problem... |
215 | I am using Debian GNU/Linux and have a problem... |
| 92 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
216 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
| 93 | patches that considerably change the behaviour of rxvt-unicode. |
217 | patches that considerably change the behaviour of rxvt-unicode (but |
| 94 | Before reporting a bug to the original rxvt-unicode author please |
218 | unfortunately this notice has been removed). Before reporting a bug to |
| 95 | download and install the genuine version |
219 | the original rxvt-unicode author please download and install the genuine |
| 96 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
220 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
| 97 | problem. If you cannot, chances are that the problems are specific |
221 | the problem. If you cannot, chances are that the problems are specific |
| 98 | to Debian GNU/Linux, in which case it should be reported via the |
222 | to Debian GNU/Linux, in which case it should be reported via the Debian |
| 99 | Debian Bug Tracking System (use "reportbug" to report the bug). |
223 | Bug Tracking System (use "reportbug" to report the bug). |
| 100 | |
224 | |
| 101 | For other problems that also affect the Debian package, you can and |
225 | 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 |
226 | probably should use the Debian BTS, too, because, after all, it's also a |
| 103 | also a bug in the Debian version and it serves as a reminder for |
227 | bug in the Debian version and it serves as a reminder for other users |
| 104 | other users that might encounter the same issue. |
228 | that might encounter the same issue. |
| 105 | |
229 | |
| 106 | I am maintaining rxvt-unicode for distribution/OS XXX, any |
230 | I am maintaining rxvt-unicode for distribution/OS XXX, any |
| 107 | recommendation? |
231 | recommendation? |
| 108 | You should build one binary with the default options. configure now |
232 | You should build one binary with the default options. configure now |
| 109 | enables most useful options, and the trend goes to making them |
233 | enables most useful options, and the trend goes to making them |
| 110 | runtime-switchable, too, so there is usually no drawback to enbaling |
234 | runtime-switchable, too, so there is usually no drawback to enbaling |
| 111 | them, except higher disk and possibly memory usage. The perl |
235 | them, except higher disk and possibly memory usage. The perl interpreter |
| 112 | interpreter should be enabled, as important functionality (menus, |
236 | should be enabled, as important functionality (menus, selection, likely |
| 113 | selection, likely more in the future) depends on it. |
237 | more in the future) depends on it. |
| 114 | |
238 | |
| 115 | You should not overwrite the "perl-ext-common" snd "perl-ext" |
239 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
| 116 | resources system-wide (except maybe with "defaults"). This will |
240 | system-wide (except maybe with "defaults"). This will result in useful |
| 117 | result in useful behaviour. If your distribution aims at low memory, |
241 | behaviour. If your distribution aims at low memory, add an empty |
| 118 | add an empty "perl-ext-common" resource to the app-defaults file. |
242 | "perl-ext-common" resource to the app-defaults file. This will keep the |
| 119 | This will keep the perl interpreter disabled until the user enables |
243 | perl interpreter disabled until the user enables it. |
| 120 | it. |
|
|
| 121 | |
244 | |
| 122 | If you can/want build more binaries, I recommend building a minimal |
245 | If you can/want build more binaries, I recommend building a minimal one |
| 123 | one with "--disable-everything" (very useful) and a maximal one with |
246 | with "--disable-everything" (very useful) and a maximal one with |
| 124 | "--enable-everything" (less useful, it will be very big due to a lot |
247 | "--enable-everything" (less useful, it will be very big due to a lot of |
| 125 | of encodings built-in that increase download times and are rarely |
248 | encodings built-in that increase download times and are rarely used). |
| 126 | used). |
|
|
| 127 | |
249 | |
| 128 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
250 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
| 129 | safe? |
251 | It should be, starting with release 7.1. You are encouraged to properly |
| 130 | Likely not. While I honestly try to make it secure, and am probably |
252 | install urxvt with privileges necessary for your OS now. |
| 131 | not bad at it, I think it is simply unreasonable to expect all of |
|
|
| 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 | |
253 | |
| 136 | Elevated privileges are only required for utmp and pty operations on |
254 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
| 137 | some systems (for example, GNU/Linux doesn't need any extra |
255 | into a helper process for privileged operations (pty handling on some |
| 138 | privileges for ptys, but some need it for utmp support). If |
256 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
| 139 | rxvt-unicode doesn't support the library/setuid helper that your OS |
257 | immediately. This is much safer than most other terminals that keep |
| 140 | needs I'll be happy to assist you in implementing support for it. |
258 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
259 | things as perl interpreters, which might be "helpful" to attackers). |
| 141 | |
260 | |
| 142 | So, while setuid/setgid operation is supported and not a problem on |
261 | This forking is done as the very first within main(), which is very |
| 143 | your typical single-user-no-other-logins unix desktop, always |
262 | 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 |
263 | main(), or things like the dynamic loader of your system, which should |
| 145 | for security issues regularly. |
264 | result in very little risk. |
| 146 | |
265 | |
| 147 | When I log-in to another system it tells me about missing terminfo data? |
266 | 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 |
267 | The terminal description used by rxvt-unicode is not as widely available |
| 149 | available as that for xterm, or even rxvt (for which the same |
268 | as that for xterm, or even rxvt (for which the same problem often |
| 150 | problem often arises). |
269 | arises). |
| 151 | |
270 | |
| 152 | The correct solution for this problem is to install the terminfo, |
271 | The correct solution for this problem is to install the terminfo, this |
| 153 | this can be done like this (with ncurses' infocmp): |
272 | can be done like this (with ncurses' infocmp): |
| 154 | |
273 | |
| 155 | REMOTE=remotesystem.domain |
274 | REMOTE=remotesystem.domain |
| 156 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
275 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
| 157 | |
276 | |
| 158 | ... or by installing rxvt-unicode normally on the remote system, |
277 | ... or by installing rxvt-unicode normally on the remote system, |
| 159 | |
278 | |
| 160 | If you cannot or do not want to do this, then you can simply set |
279 | If you cannot or do not want to do this, then you can simply set |
| 161 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
280 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
| 162 | problems arising, which includes wrong keymapping, less and |
281 | problems arising, which includes wrong keymapping, less and different |
| 163 | different colours and some refresh errors in fullscreen |
282 | colours and some refresh errors in fullscreen applications. It's a nice |
| 164 | applications. It's a nice quick-and-dirty workaround for rare cases, |
283 | quick-and-dirty workaround for rare cases, though. |
| 165 | though. |
|
|
| 166 | |
284 | |
| 167 | If you always want to do this (and are fine with the consequences) |
285 | If you always want to do this (and are fine with the consequences) you |
| 168 | you can either recompile rxvt-unicode with the desired TERM value or |
286 | can either recompile rxvt-unicode with the desired TERM value or use a |
| 169 | use a resource to set it: |
287 | resource to set it: |
| 170 | |
288 | |
| 171 | URxvt.termName: rxvt |
289 | URxvt.termName: rxvt |
| 172 | |
290 | |
| 173 | If you don't plan to use rxvt (quite common...) you could also |
291 | If you don't plan to use rxvt (quite common...) you could also replace |
| 174 | replace the rxvt terminfo file with the rxvt-unicode one. |
292 | the rxvt terminfo file with the rxvt-unicode one. |
| 175 | |
293 | |
| 176 | "tic" outputs some error when compiling the terminfo entry. |
294 | "tic" outputs some error when compiling the terminfo entry. |
| 177 | Most likely it's the empty definition for "enacs=". Just replace it |
295 | Most likely it's the empty definition for "enacs=". Just replace it by |
| 178 | by "enacs=\E[0@" and try again. |
296 | "enacs=\E[0@" and try again. |
| 179 | |
297 | |
| 180 | "bash"'s readline does not work correctly under rxvt. |
298 | "bash"'s readline does not work correctly under rxvt. |
| 181 | I need a termcap file entry. |
299 | I need a termcap file entry. |
| 182 | One reason you might want this is that some distributions or |
300 | One reason you might want this is that some distributions or operating |
| 183 | operating systems still compile some programs using the |
301 | systems still compile some programs using the long-obsoleted termcap |
| 184 | long-obsoleted termcap library (Fedora Core's bash is one example) |
302 | library (Fedora Core's bash is one example) and rely on a termcap entry |
| 185 | and rely on a termcap entry for "rxvt-unicode". |
303 | for "rxvt-unicode". |
| 186 | |
304 | |
| 187 | You could use rxvt's termcap entry with resonable results in many |
305 | You could use rxvt's termcap entry with resonable results in many cases. |
| 188 | cases. You can also create a termcap entry by using terminfo's |
306 | You can also create a termcap entry by using terminfo's infocmp program |
| 189 | infocmp program like this: |
307 | like this: |
| 190 | |
308 | |
| 191 | infocmp -C rxvt-unicode |
309 | infocmp -C rxvt-unicode |
| 192 | |
310 | |
| 193 | Or you could use this termcap entry, generated by the command above: |
311 | Or you could use this termcap entry, generated by the command above: |
| 194 | |
312 | |
| 195 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
313 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
| 196 | :am:bw:eo:km:mi:ms:xn:xo:\ |
314 | :am:bw:eo:km:mi:ms:xn:xo:\ |
| 197 | :co#80:it#8:li#24:lm#0:\ |
315 | :co#80:it#8:li#24:lm#0:\ |
| 198 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
316 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
| 199 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
317 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
| 200 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
318 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
| 201 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
319 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
| 202 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
320 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
| 203 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
321 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
| 204 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
322 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
| 205 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
323 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
| 206 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
324 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
| 207 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
325 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
| 208 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
326 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
| 209 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
327 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
| 210 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
328 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
| 211 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
329 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
| 212 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
330 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
| 213 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
331 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
| 214 | :vs=\E[?25h: |
332 | :vs=\E[?25h: |
| 215 | |
333 | |
| 216 | Why does "ls" no longer have coloured output? |
334 | Why does "ls" no longer have coloured output? |
| 217 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
335 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 218 | decide wether a terminal has colour, but uses it's own configuration |
336 | decide wether a terminal has colour, but uses it's own configuration |
| 219 | file. Needless to say, "rxvt-unicode" is not in it's default file |
337 | file. Needless to say, "rxvt-unicode" is not in it's default file (among |
| 220 | (among with most other terminals supporting colour). Either add: |
338 | with most other terminals supporting colour). Either add: |
| 221 | |
339 | |
| 222 | TERM rxvt-unicode |
340 | TERM rxvt-unicode |
| 223 | |
341 | |
| 224 | to "/etc/DIR_COLORS" or simply add: |
342 | to "/etc/DIR_COLORS" or simply add: |
| 225 | |
343 | |
| 226 | alias ls='ls --color=auto' |
344 | alias ls='ls --color=auto' |
| 227 | |
345 | |
| 228 | to your ".profile" or ".bashrc". |
346 | to your ".profile" or ".bashrc". |
| 229 | |
347 | |
| 230 | Why doesn't vim/emacs etc. use the 88 colour mode? |
348 | Why doesn't vim/emacs etc. use the 88 colour mode? |
| 231 | Why doesn't vim/emacs etc. make use of italic? |
349 | Why doesn't vim/emacs etc. make use of italic? |
| 232 | Why are the secondary screen-related options not working properly? |
350 | Why are the secondary screen-related options not working properly? |
| 233 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
351 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
| 234 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
352 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
| 235 | setting "TERM" to "rxvt", which doesn't have these extra features. |
353 | setting "TERM" to "rxvt", which doesn't have these extra features. |
| 236 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
354 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
| 237 | furthermore fail to even install the "rxvt-unicode" terminfo file, |
355 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
| 238 | so you will need to install it on your own (See the question When I |
356 | you will need to install it on your own (See the question When I log-in |
| 239 | log-in to another system it tells me about missing terminfo data? on |
357 | to another system it tells me about missing terminfo data? on how to do |
| 240 | how to do this). |
358 | this). |
| 241 | |
359 | |
| 242 | My numerical keypad acts weird and generates differing output? |
360 | My numerical keypad acts weird and generates differing output? |
| 243 | Some Debian GNUL/Linux users seem to have this problem, although no |
361 | Some Debian GNUL/Linux users seem to have this problem, although no |
| 244 | specific details were reported so far. It is possible that this is |
362 | specific details were reported so far. It is possible that this is |
| 245 | caused by the wrong "TERM" setting, although the details of wether |
363 | caused by the wrong "TERM" setting, although the details of wether and |
| 246 | and how this can happen are unknown, as "TERM=rxvt" should offer a |
364 | how this can happen are unknown, as "TERM=rxvt" should offer a |
| 247 | compatible keymap. See the answer to the previous question, and |
365 | compatible keymap. See the answer to the previous question, and please |
| 248 | please report if that helped. |
366 | report if that helped. |
| 249 | |
367 | |
| 250 | Rxvt-unicode does not seem to understand the selected encoding? |
368 | Rxvt-unicode does not seem to understand the selected encoding? |
| 251 | Unicode does not seem to work? |
369 | Unicode does not seem to work? |
| 252 | If you encounter strange problems like typing an accented character |
370 | If you encounter strange problems like typing an accented character but |
| 253 | but getting two unrelated other characters or similar, or if program |
371 | getting two unrelated other characters or similar, or if program output |
| 254 | output is subtly garbled, then you should check your locale |
372 | is subtly garbled, then you should check your locale settings. |
| 255 | settings. |
|
|
| 256 | |
373 | |
| 257 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
374 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
| 258 | programs. Often rxvt-unicode is started in the "C" locale, while the |
375 | programs. Often rxvt-unicode is started in the "C" locale, while the |
| 259 | login script running within the rxvt-unicode window changes the |
376 | login script running within the rxvt-unicode window changes the locale |
| 260 | locale to something else, e.g. "en_GB.UTF-8". Needless to say, this |
377 | to something else, e.g. "en_GB.UTF-8". Needless to say, this is not |
| 261 | is not going to work. |
378 | going to work. |
| 262 | |
379 | |
| 263 | The best thing is to fix your startup environment, as you will |
380 | The best thing is to fix your startup environment, as you will likely |
| 264 | likely run into other problems. If nothing works you can try this in |
381 | run into other problems. If nothing works you can try this in your |
| 265 | your .profile. |
382 | .profile. |
| 266 | |
383 | |
| 267 | printf '\e]701;%s\007' "$LC_CTYPE" |
384 | printf '\e]701;%s\007' "$LC_CTYPE" |
| 268 | |
385 | |
| 269 | If this doesn't work, then maybe you use a "LC_CTYPE" specification |
386 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
| 270 | not supported on your systems. Some systems have a "locale" command |
387 | supported on your systems. Some systems have a "locale" command which |
| 271 | which displays this (also, "perl -e0" can be used to check locale |
388 | displays this (also, "perl -e0" can be used to check locale settings, as |
| 272 | settings, as it will complain loudly if it cannot set the locale). |
389 | it will complain loudly if it cannot set the locale). If it displays |
| 273 | If it displays something like: |
390 | something like: |
| 274 | |
391 | |
| 275 | locale: Cannot set LC_CTYPE to default locale: ... |
392 | locale: Cannot set LC_CTYPE to default locale: ... |
| 276 | |
393 | |
| 277 | Then the locale you specified is not supported on your system. |
394 | Then the locale you specified is not supported on your system. |
| 278 | |
395 | |
| 279 | If nothing works and you are sure that everything is set correctly |
396 | If nothing works and you are sure that everything is set correctly then |
| 280 | then you will need to remember a little known fact: Some programs |
397 | you will need to remember a little known fact: Some programs just don't |
| 281 | just don't support locales :( |
398 | support locales :( |
| 282 | |
399 | |
| 283 | Why do some characters look so much different than others? |
400 | Why do some characters look so much different than others? |
| 284 | How does rxvt-unicode choose fonts? |
401 | How does rxvt-unicode choose fonts? |
| 285 | Most fonts do not contain the full range of Unicode, which is fine. |
402 | Most fonts do not contain the full range of Unicode, which is fine. |
| 286 | Chances are that the font you (or the admin/package maintainer of |
403 | Chances are that the font you (or the admin/package maintainer of your |
| 287 | your system/os) have specified does not cover all the characters you |
404 | system/os) have specified does not cover all the characters you want to |
| 288 | want to display. |
405 | display. |
| 289 | |
406 | |
| 290 | rxvt-unicode makes a best-effort try at finding a replacement font. |
407 | rxvt-unicode makes a best-effort try at finding a replacement font. |
| 291 | Often the result is fine, but sometimes the chosen font looks |
408 | Often the result is fine, but sometimes the chosen font looks |
| 292 | bad/ugly/wrong. Some fonts have totally strange characters that |
409 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
| 293 | don't resemble the correct glyph at all, and rxvt-unicode lacks the |
410 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
| 294 | artificial intelligence to detect that a specific glyph is wrong: it |
411 | intelligence to detect that a specific glyph is wrong: it has to believe |
| 295 | has to believe the font that the characters it claims to contain |
412 | the font that the characters it claims to contain indeed look correct. |
| 296 | indeed look correct. |
|
|
| 297 | |
413 | |
| 298 | In that case, select a font of your taste and add it to the font |
414 | In that case, select a font of your taste and add it to the font list, |
| 299 | list, e.g.: |
415 | e.g.: |
| 300 | |
416 | |
| 301 | rxvt -fn basefont,font2,font3... |
417 | rxvt -fn basefont,font2,font3... |
| 302 | |
418 | |
| 303 | When rxvt-unicode sees a character, it will first look at the base |
419 | When rxvt-unicode sees a character, it will first look at the base font. |
| 304 | font. If the base font does not contain the character, it will go to |
420 | If the base font does not contain the character, it will go to the next |
| 305 | the next font, and so on. Specifying your own fonts will also speed |
421 | font, and so on. Specifying your own fonts will also speed up this |
| 306 | up this search and use less resources within rxvt-unicode and the |
422 | search and use less resources within rxvt-unicode and the X-server. |
| 307 | X-server. |
|
|
| 308 | |
423 | |
| 309 | The only limitation is that none of the fonts may be larger than the |
424 | The only limitation is that none of the fonts may be larger than the |
| 310 | base font, as the base font defines the terminal character cell |
425 | base font, as the base font defines the terminal character cell size, |
| 311 | size, which must be the same due to the way terminals work. |
426 | which must be the same due to the way terminals work. |
| 312 | |
427 | |
| 313 | Why do some chinese characters look so different than others? |
428 | Why do some chinese characters look so different than others? |
| 314 | This is because there is a difference between script and language -- |
429 | This is because there is a difference between script and language -- |
| 315 | rxvt-unicode does not know which language the text that is output |
430 | rxvt-unicode does not know which language the text that is output is, as |
| 316 | is, as it only knows the unicode character codes. If rxvt-unicode |
431 | it only knows the unicode character codes. If rxvt-unicode first sees a |
| 317 | first sees a japanese/chinese character, it might choose a japanese |
432 | japanese/chinese character, it might choose a japanese font for display. |
| 318 | font for display. Subsequent japanese characters will use that font. |
433 | Subsequent japanese characters will use that font. Now, many chinese |
| 319 | Now, many chinese characters aren't represented in japanese fonts, |
434 | characters aren't represented in japanese fonts, so when the first |
| 320 | so when the first non-japanese character comes up, rxvt-unicode will |
435 | non-japanese character comes up, rxvt-unicode will look for a chinese |
| 321 | look for a chinese font -- unfortunately at this point, it will |
436 | font -- unfortunately at this point, it will still use the japanese font |
| 322 | still use the japanese font for chinese characters that are also in |
437 | for chinese characters that are also in the japanese font. |
| 323 | the japanese font. |
|
|
| 324 | |
438 | |
| 325 | The workaround is easy: just tag a chinese font at the end of your |
439 | The workaround is easy: just tag a chinese font at the end of your font |
| 326 | font list (see the previous question). The key is to view the font |
440 | list (see the previous question). The key is to view the font list as a |
| 327 | list as a preference list: If you expect more japanese, list a |
441 | preference list: If you expect more japanese, list a japanese font |
| 328 | japanese font first. If you expect more chinese, put a chinese font |
442 | first. If you expect more chinese, put a chinese font first. |
| 329 | first. |
|
|
| 330 | |
443 | |
| 331 | In the future it might be possible to switch language preferences at |
444 | In the future it might be possible to switch language preferences at |
| 332 | runtime (the internal data structure has no problem with using |
445 | runtime (the internal data structure has no problem with using different |
| 333 | different fonts for the same character at the same time, but no |
446 | fonts for the same character at the same time, but no interface for this |
| 334 | interface for this has been designed yet). |
447 | has been designed yet). |
| 335 | |
448 | |
| 336 | Until then, you might get away with switching fonts at runtime (see |
449 | Until then, you might get away with switching fonts at runtime (see "Can |
| 337 | "Can I switch the fonts at runtime?" later in this document). |
450 | I switch the fonts at runtime?" later in this document). |
| 338 | |
451 | |
| 339 | Why does rxvt-unicode sometimes leave pixel droppings? |
452 | Why does rxvt-unicode sometimes leave pixel droppings? |
| 340 | Most fonts were not designed for terminal use, which means that |
453 | Most fonts were not designed for terminal use, which means that |
| 341 | character size varies a lot. A font that is otherwise fine for |
454 | character size varies a lot. A font that is otherwise fine for terminal |
| 342 | terminal use might contain some characters that are simply too wide. |
455 | use might contain some characters that are simply too wide. Rxvt-unicode |
| 343 | Rxvt-unicode will avoid these characters. For characters that are |
456 | will avoid these characters. For characters that are just "a bit" too |
| 344 | just "a bit" too wide a special "careful" rendering mode is used |
457 | wide a special "careful" rendering mode is used that redraws adjacent |
| 345 | that redraws adjacent characters. |
458 | characters. |
| 346 | |
459 | |
| 347 | All of this requires that fonts do not lie about character sizes, |
460 | All of this requires that fonts do not lie about character sizes, |
| 348 | however: Xft fonts often draw glyphs larger than their acclaimed |
461 | however: Xft fonts often draw glyphs larger than their acclaimed |
| 349 | bounding box, and rxvt-unicode has no way of detecting this (the |
462 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
| 350 | correct way is to ask for the character bounding box, which |
463 | way is to ask for the character bounding box, which unfortunately is |
| 351 | unfortunately is wrong in these cases). |
464 | wrong in these cases). |
| 352 | |
465 | |
| 353 | It's not clear (to me at least), wether this is a bug in Xft, |
466 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
| 354 | freetype, or the respective font. If you encounter this problem you |
467 | or the respective font. If you encounter this problem you might try |
| 355 | might try using the "-lsp" option to give the font more height. If |
468 | using the "-lsp" option to give the font more height. If that doesn't |
| 356 | that doesn't work, you might be forced to use a different font. |
469 | work, you might be forced to use a different font. |
| 357 | |
470 | |
| 358 | All of this is not a problem when using X11 core fonts, as their |
471 | All of this is not a problem when using X11 core fonts, as their |
| 359 | bounding box data is correct. |
472 | bounding box data is correct. |
| 360 | |
473 | |
| 361 | On Solaris 9, many line-drawing characters are too wide. |
474 | On Solaris 9, many line-drawing characters are too wide. |
| 362 | Seems to be a known bug, read |
475 | Seems to be a known bug, read |
| 363 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
476 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
| 364 | following ugly workaround to get non-double-wide-characters working: |
477 | following ugly workaround to get non-double-wide-characters working: |
| 365 | |
478 | |
| 366 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
479 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
| 367 | |
480 | |
| 368 | My Compose (Multi_key) key is no longer working. |
481 | My Compose (Multi_key) key is no longer working. |
| 369 | The most common causes for this are that either your locale is not |
482 | The most common causes for this are that either your locale is not set |
| 370 | set correctly, or you specified a preeditStyle that is not supported |
483 | correctly, or you specified a preeditStyle that is not supported by your |
| 371 | by your input method. For example, if you specified OverTheSpot and |
484 | input method. For example, if you specified OverTheSpot and your input |
| 372 | your input method (e.g. the default input method handling Compose |
485 | method (e.g. the default input method handling Compose keys) does not |
| 373 | keys) does not support this (for instance because it is not visual), |
486 | support this (for instance because it is not visual), then rxvt-unicode |
| 374 | then rxvt-unicode will continue without an input method. |
487 | will continue without an input method. |
| 375 | |
488 | |
| 376 | In this case either do not specify a preeditStyle or specify more |
489 | In this case either do not specify a preeditStyle or specify more than |
| 377 | than one pre-edit style, such as OverTheSpot,Root,None. |
490 | one pre-edit style, such as OverTheSpot,Root,None. |
| 378 | |
491 | |
| 379 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO |
492 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
| 380 | 14755 |
|
|
| 381 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
493 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
| 382 | international keyboards) or simply use ISO 14755 support to your |
494 | international keyboards) or simply use ISO 14755 support to your |
| 383 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
495 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
| 384 | other codes, too, such as "Ctrl-Shift-1-d" to type the default |
496 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
| 385 | telnet escape character and so on. |
497 | escape character and so on. |
| 386 | |
498 | |
| 387 | How can I keep rxvt-unicode from using reverse video so much? |
499 | How can I keep rxvt-unicode from using reverse video so much? |
| 388 | First of all, make sure you are running with the right terminal |
500 | First of all, make sure you are running with the right terminal settings |
| 389 | settings ("TERM=rxvt-unicode"), which will get rid of most of these |
501 | ("TERM=rxvt-unicode"), which will get rid of most of these effects. Then |
| 390 | effects. Then make sure you have specified colours for italic and |
502 | make sure you have specified colours for italic and bold, as otherwise |
| 391 | bold, as otherwise rxvt-unicode might use reverse video to simulate |
503 | rxvt-unicode might use reverse video to simulate the effect: |
| 392 | the effect: |
|
|
| 393 | |
504 | |
| 394 | URxvt.colorBD: white |
505 | URxvt.colorBD: white |
| 395 | URxvt.colorIT: green |
506 | URxvt.colorIT: green |
| 396 | |
507 | |
| 397 | Some programs assume totally weird colours (red instead of blue), how |
508 | Some programs assume totally weird colours (red instead of blue), how can I fix that? |
| 398 | can I fix that? |
|
|
| 399 | For some unexplainable reason, some rare programs assume a very |
509 | For some unexplainable reason, some rare programs assume a very weird |
| 400 | weird colour palette when confronted with a terminal with more than |
510 | colour palette when confronted with a terminal with more than the |
| 401 | the standard 8 colours (rxvt-unicode supports 88). The right fix is, |
511 | standard 8 colours (rxvt-unicode supports 88). The right fix is, of |
| 402 | of course, to fix these programs not to assume non-ISO colours |
512 | course, to fix these programs not to assume non-ISO colours without very |
| 403 | without very good reasons. |
513 | good reasons. |
| 404 | |
514 | |
| 405 | In the meantime, you can either edit your "rxvt-unicode" terminfo |
515 | In the meantime, you can either edit your "rxvt-unicode" terminfo |
| 406 | definition to only claim 8 colour support or use "TERM=rxvt", which |
516 | definition to only claim 8 colour support or use "TERM=rxvt", which will |
| 407 | will fix colours but keep you from using other rxvt-unicode |
517 | fix colours but keep you from using other rxvt-unicode features. |
| 408 | features. |
|
|
| 409 | |
518 | |
| 410 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
519 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
| 411 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined |
520 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
| 412 | in your compile environment, or an implementation that implements |
521 | your compile environment, or an implementation that implements it, |
| 413 | it, wether it defines the symbol or not. "__STDC_ISO_10646__" |
522 | wether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
| 414 | requires that wchar_t is represented as unicode. |
523 | wchar_t is represented as unicode. |
| 415 | |
524 | |
| 416 | As you might have guessed, FreeBSD does neither define this symobl |
525 | As you might have guessed, FreeBSD does neither define this symobl nor |
| 417 | nor does it support it. Instead, it uses it's own internal |
526 | does it support it. Instead, it uses it's own internal representation of |
| 418 | representation of wchar_t. This is, of course, completely fine with |
527 | wchar_t. This is, of course, completely fine with respect to standards. |
| 419 | respect to standards. |
|
|
| 420 | |
528 | |
| 421 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" |
529 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
| 422 | and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
530 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
| 423 | |
531 | |
| 424 | "__STDC_ISO_10646__" is the only sane way to support multi-language |
532 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
| 425 | apps in an OS, as using a locale-dependent (and non-standardized) |
533 | in an OS, as using a locale-dependent (and non-standardized) |
| 426 | representation of wchar_t makes it impossible to convert between |
534 | representation of wchar_t makes it impossible to convert between wchar_t |
| 427 | wchar_t (as used by X11 and your applications) and any other |
535 | (as used by X11 and your applications) and any other encoding without |
| 428 | encoding without implementing OS-specific-wrappers for each and |
536 | implementing OS-specific-wrappers for each and every locale. There |
| 429 | every locale. There simply are no APIs to convert wchar_t into |
537 | simply are no APIs to convert wchar_t into anything except the current |
| 430 | anything except the current locale encoding. |
538 | locale encoding. |
| 431 | |
539 | |
| 432 | Some applications (such as the formidable mlterm) work around this |
540 | Some applications (such as the formidable mlterm) work around this by |
| 433 | by carrying their own replacement functions for character set |
541 | carrying their own replacement functions for character set handling with |
| 434 | handling with them, and either implementing OS-dependent hacks or |
542 | them, and either implementing OS-dependent hacks or doing multiple |
| 435 | doing multiple conversions (which is slow and unreliable in case the |
543 | conversions (which is slow and unreliable in case the OS implements |
| 436 | OS implements encodings slightly different than the terminal |
544 | encodings slightly different than the terminal emulator). |
| 437 | emulator). |
|
|
| 438 | |
545 | |
| 439 | The rxvt-unicode author insists that the right way to fix this is in |
546 | The rxvt-unicode author insists that the right way to fix this is in the |
| 440 | the system libraries once and for all, instead of forcing every app |
547 | system libraries once and for all, instead of forcing every app to carry |
| 441 | to carry complete replacements for them :) |
548 | complete replacements for them :) |
| 442 | |
549 | |
| 443 | I use Solaris 9 and it doesn't compile/work/etc. |
550 | I use Solaris 9 and it doesn't compile/work/etc. |
| 444 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
551 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
| 445 | problems with "wcwidth" and a compile problem. |
552 | problems with "wcwidth" and a compile problem. |
| 446 | |
553 | |
| 447 | How can I use rxvt-unicode under cygwin? |
554 | How can I use rxvt-unicode under cygwin? |
| 448 | rxvt-unicode should compile and run out of the box on cygwin, using |
555 | rxvt-unicode should compile and run out of the box on cygwin, using the |
| 449 | the X11 libraries that come with cygwin. libW11 emulation is no |
556 | X11 libraries that come with cygwin. libW11 emulation is no longer |
| 450 | longer supported (and makes no sense, either, as it only supported a |
557 | supported (and makes no sense, either, as it only supported a single |
| 451 | single font). I recommend starting the X-server in "-multiwindow" or |
558 | font). I recommend starting the X-server in "-multiwindow" or |
| 452 | "-rootless" mode instead, which will result in similar look&feel as |
559 | "-rootless" mode instead, which will result in similar look&feel as the |
| 453 | the old libW11 emulation. |
560 | old libW11 emulation. |
| 454 | |
561 | |
| 455 | At the time of this writing, cygwin didn't seem to support any |
562 | At the time of this writing, cygwin didn't seem to support any |
| 456 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
563 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
| 457 | likely limited to 8-bit encodings. |
564 | likely limited to 8-bit encodings. |
| 458 | |
565 | |
| 459 | How does rxvt-unicode determine the encoding to use? |
566 | How does rxvt-unicode determine the encoding to use? |
| 460 | Is there an option to switch encodings? |
567 | Is there an option to switch encodings? |
| 461 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
568 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
| 462 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
569 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know |
| 463 | even know about UTF-8 or any other encodings with respect to |
570 | about UTF-8 or any other encodings with respect to terminal I/O. |
| 464 | terminal I/O. |
|
|
| 465 | |
571 | |
| 466 | The reasons is that there exists a perfectly fine mechanism for |
572 | The reasons is that there exists a perfectly fine mechanism for |
| 467 | selecting the encoding, doing I/O and (most important) communicating |
573 | selecting the encoding, doing I/O and (most important) communicating |
| 468 | this to all applications so everybody agrees on character properties |
574 | this to all applications so everybody agrees on character properties |
| 469 | such as width and code number. This mechanism is the *locale*. |
575 | such as width and code number. This mechanism is the *locale*. |
| 470 | Applications not using that info will have problems (for example, |
576 | Applications not using that info will have problems (for example, |
| 471 | "xterm" gets the width of characters wrong as it uses it's own, |
577 | "xterm" gets the width of characters wrong as it uses it's own, |
| 472 | locale-independent table under all locales). |
578 | locale-independent table under all locales). |
| 473 | |
579 | |
| 474 | Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. |
580 | Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All |
| 475 | All programs doing the same (that is, most) will automatically agree |
581 | programs doing the same (that is, most) will automatically agree in the |
| 476 | in the interpretation of characters. |
582 | interpretation of characters. |
| 477 | |
583 | |
| 478 | Unfortunately, there is no system-independent way to select locales, |
584 | Unfortunately, there is no system-independent way to select locales, nor |
| 479 | nor is there a standard on how locale specifiers will look like. |
585 | is there a standard on how locale specifiers will look like. |
| 480 | |
586 | |
| 481 | On most systems, the content of the "LC_CTYPE" environment variable |
587 | On most systems, the content of the "LC_CTYPE" environment variable |
| 482 | contains an arbitrary string which corresponds to an |
588 | contains an arbitrary string which corresponds to an already-installed |
| 483 | already-installed locale. Common names for locales are |
589 | locale. Common names for locales are "en_US.UTF-8", "de_DE.ISO-8859-15", |
| 484 | "en_US.UTF-8", "de_DE.ISO-8859-15", "ja_JP.EUC-JP", i.e. |
590 | "ja_JP.EUC-JP", i.e. "language_country.encoding", but other forms (i.e. |
| 485 | "language_country.encoding", but other forms (i.e. "de" or "german") |
591 | "de" or "german") are also common. |
| 486 | are also common. |
|
|
| 487 | |
592 | |
| 488 | Rxvt-unicode ignores all other locale categories, and except for the |
593 | Rxvt-unicode ignores all other locale categories, and except for the |
| 489 | encoding, ignores country or language-specific settings, i.e. |
594 | encoding, ignores country or language-specific settings, i.e. |
| 490 | "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to |
595 | "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to rxvt-unicode. |
| 491 | rxvt-unicode. |
|
|
| 492 | |
596 | |
| 493 | If you want to use a specific encoding you have to make sure you |
597 | If you want to use a specific encoding you have to make sure you start |
| 494 | start rxvt-unicode with the correct "LC_CTYPE" category. |
598 | rxvt-unicode with the correct "LC_CTYPE" category. |
| 495 | |
599 | |
| 496 | Can I switch locales at runtime? |
600 | Can I switch locales at runtime? |
| 497 | Yes, using an escape sequence. Try something like this, which sets |
601 | Yes, using an escape sequence. Try something like this, which sets |
| 498 | rxvt-unicode's idea of "LC_CTYPE". |
602 | rxvt-unicode's idea of "LC_CTYPE". |
| 499 | |
603 | |
|
|
604 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
605 | |
|
|
606 | See also the previous answer. |
|
|
607 | |
|
|
608 | Sometimes this capability is rather handy when you want to work in one |
|
|
609 | locale (e.g. "de_DE.UTF-8") but some programs don't support it (e.g. |
|
|
610 | UTF-8). For example, I use this script to start "xjdic", which first |
|
|
611 | switches to a locale supported by xjdic and back later: |
|
|
612 | |
| 500 | printf '\e]701;%s\007' ja_JP.SJIS |
613 | printf '\e]701;%s\007' ja_JP.SJIS |
| 501 | |
|
|
| 502 | See also the previous answer. |
|
|
| 503 | |
|
|
| 504 | Sometimes this capability is rather handy when you want to work in |
|
|
| 505 | one locale (e.g. "de_DE.UTF-8") but some programs don't support it |
|
|
| 506 | (e.g. UTF-8). For example, I use this script to start "xjdic", which |
|
|
| 507 | first switches to a locale supported by xjdic and back later: |
|
|
| 508 | |
|
|
| 509 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
| 510 | xjdic -js |
614 | xjdic -js |
| 511 | printf '\e]701;%s\007' de_DE.UTF-8 |
615 | printf '\e]701;%s\007' de_DE.UTF-8 |
| 512 | |
616 | |
| 513 | You can also use xterm's "luit" program, which usually works fine, |
617 | You can also use xterm's "luit" program, which usually works fine, |
| 514 | except for some locales where character width differs between |
618 | except for some locales where character width differs between program- |
| 515 | program- and rxvt-unicode-locales. |
619 | and rxvt-unicode-locales. |
| 516 | |
620 | |
| 517 | Can I switch the fonts at runtime? |
621 | Can I switch the fonts at runtime? |
| 518 | Yes, using an escape sequence. Try something like this, which has |
622 | Yes, using an escape sequence. Try something like this, which has the |
| 519 | the same effect as using the "-fn" switch, and takes effect |
623 | same effect as using the "-fn" switch, and takes effect immediately: |
| 520 | immediately: |
|
|
| 521 | |
624 | |
| 522 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
625 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
| 523 | |
626 | |
| 524 | This is useful if you e.g. work primarily with japanese (and prefer |
627 | This is useful if you e.g. work primarily with japanese (and prefer a |
| 525 | a japanese font), but you have to switch to chinese temporarily, |
628 | japanese font), but you have to switch to chinese temporarily, where |
| 526 | where japanese fonts would only be in your way. |
629 | japanese fonts would only be in your way. |
| 527 | |
630 | |
| 528 | You can think of this as a kind of manual ISO-2022 switching. |
631 | You can think of this as a kind of manual ISO-2022 switching. |
| 529 | |
632 | |
| 530 | Why do italic characters look as if clipped? |
633 | Why do italic characters look as if clipped? |
| 531 | Many fonts have difficulties with italic characters and hinting. For |
634 | Many fonts have difficulties with italic characters and hinting. For |
| 532 | example, the otherwise very nicely hinted font "xft:Bitstream Vera |
635 | example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans |
| 533 | Sans Mono" completely fails in it's italic face. A workaround might |
636 | Mono" completely fails in it's italic face. A workaround might be to |
| 534 | be to enable freetype autohinting, i.e. like this: |
637 | enable freetype autohinting, i.e. like this: |
| 535 | |
638 | |
| 536 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
639 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
| 537 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
640 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
| 538 | |
641 | |
| 539 | My input method wants <some encoding> but I want UTF-8, what can I do? |
642 | 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 |
643 | You can specify separate locales for the input method and the rest of |
| 541 | of the terminal, using the resource "imlocale": |
644 | the terminal, using the resource "imlocale": |
| 542 | |
645 | |
| 543 | URxvt*imlocale: ja_JP.EUC-JP |
646 | URxvt.imlocale: ja_JP.EUC-JP |
| 544 | |
647 | |
| 545 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
648 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still |
| 546 | still use your input method. Please note, however, that you will not |
649 | use your input method. Please note, however, that you will not be able |
| 547 | be able to input characters outside "EUC-JP" in a normal way then, |
650 | to input characters outside "EUC-JP" in a normal way then, as your input |
| 548 | as your input method limits you. |
651 | method limits you. |
| 549 | |
652 | |
| 550 | Rxvt-unicode crashes when the X Input Method changes or exits. |
653 | Rxvt-unicode crashes when the X Input Method changes or exits. |
| 551 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
654 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
| 552 | design. Applications can avoid some crashes at the expense of memory |
655 | design. Applications can avoid some crashes at the expense of memory |
| 553 | leaks, and Input Methods can avoid some crashes by careful ordering |
656 | leaks, and Input Methods can avoid some crashes by careful ordering at |
| 554 | at exit time. kinput2 (and derived input methods) generally |
657 | exit time. kinput2 (and derived input methods) generally succeeds, while |
| 555 | succeeds, while SCIM (or similar input methods) fails. In the end, |
658 | SCIM (or similar input methods) fails. In the end, however, crashes |
| 556 | however, crashes cannot be completely avoided even if both sides |
659 | cannot be completely avoided even if both sides cooperate. |
| 557 | cooperate. |
|
|
| 558 | |
660 | |
| 559 | So the only workaround is not to kill your Input Method Servers. |
661 | So the only workaround is not to kill your Input Method Servers. |
| 560 | |
662 | |
| 561 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
663 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 562 | Rxvt-unicode tries to obey the rule of not charging you for |
664 | Rxvt-unicode tries to obey the rule of not charging you for something |
| 563 | something you don't use. One thing you should try is to configure |
665 | you don't use. One thing you should try is to configure out all settings |
| 564 | out all settings that you don't need, for example, Xft support is a |
666 | that you don't need, for example, Xft support is a resource hog by |
| 565 | resource hog by design, when used. Compiling it out ensures that no |
667 | design, when used. Compiling it out ensures that no Xft font will be |
| 566 | Xft font will be loaded accidentally when rxvt-unicode tries to find |
668 | loaded accidentally when rxvt-unicode tries to find a font for your |
| 567 | a font for your characters. |
669 | characters. |
| 568 | |
670 | |
| 569 | Also, many people (me included) like large windows and even larger |
671 | Also, many people (me included) like large windows and even larger |
| 570 | scrollback buffers: Without "--enable-unicode3", rxvt-unicode will |
672 | scrollback buffers: Without "--enable-unicode3", rxvt-unicode will use 6 |
| 571 | use 6 bytes per screen cell. For a 160x?? window this amounts to |
673 | bytes per screen cell. For a 160x?? window this amounts to almost a |
| 572 | almost a kilobyte per line. A scrollback buffer of 10000 lines will |
674 | kilobyte per line. A scrollback buffer of 10000 lines will then (if |
| 573 | then (if full) use 10 Megabytes of memory. With "--enable-unicode3" |
675 | full) use 10 Megabytes of memory. With "--enable-unicode3" it gets |
| 574 | it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
676 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
| 575 | |
677 | |
| 576 | Can I speed up Xft rendering somehow? |
678 | Can I speed up Xft rendering somehow? |
| 577 | Yes, the most obvious way to speed it up is to avoid Xft entirely, |
679 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as it |
| 578 | as it is simply slow. If you still want Xft fonts you might try to |
680 | is simply slow. If you still want Xft fonts you might try to disable |
| 579 | disable antialiasing (by appending ":antialias=false"), which saves |
681 | antialiasing (by appending ":antialias=false"), which saves lots of |
| 580 | lots of memory and also speeds up rendering considerably. |
682 | memory and also speeds up rendering considerably. |
| 581 | |
683 | |
| 582 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
684 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
| 583 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
685 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
| 584 | fall back to it's default font search list it will prefer X11 core |
686 | fall back to it's default font search list it will prefer X11 core |
| 585 | fonts, because they are small and fast, and then use Xft fonts. It |
687 | fonts, because they are small and fast, and then use Xft fonts. It has |
| 586 | has antialiasing disabled for most of them, because the author |
688 | antialiasing disabled for most of them, because the author thinks they |
| 587 | thinks they look best that way. |
689 | look best that way. |
| 588 | |
690 | |
| 589 | If you want antialiasing, you have to specify the fonts manually. |
691 | If you want antialiasing, you have to specify the fonts manually. |
| 590 | |
692 | |
| 591 | Mouse cut/paste suddenly no longer works. |
693 | Mouse cut/paste suddenly no longer works. |
| 592 | Make sure that mouse reporting is actually turned off since killing |
694 | Make sure that mouse reporting is actually turned off since killing some |
| 593 | some editors prematurely may leave the mouse in mouse report mode. |
695 | editors prematurely may leave the mouse in mouse report mode. I've heard |
| 594 | I've heard that tcsh may use mouse reporting unless it otherwise |
696 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
| 595 | specified. A quick check is to see if cut/paste works when the Alt |
697 | check is to see if cut/paste works when the Alt or Shift keys are |
| 596 | or Shift keys are depressed. See rxvt(7) |
698 | depressed. |
| 597 | |
699 | |
| 598 | What's with this bold/blink stuff? |
700 | What's with this bold/blink stuff? |
| 599 | If no bold colour is set via "colorBD:", bold will invert text using |
701 | If no bold colour is set via "colorBD:", bold will invert text using the |
| 600 | the standard foreground colour. |
702 | standard foreground colour. |
| 601 | |
703 | |
| 602 | For the standard background colour, blinking will actually make the |
704 | For the standard background colour, blinking will actually make the text |
| 603 | text blink when compiled with "--enable-blinking". with standard |
705 | blink when compiled with "--enable-blinking". with standard colours. |
| 604 | colours. Without "--enable-blinking", the blink attribute will be |
706 | Without "--enable-blinking", the blink attribute will be ignored. |
| 605 | ignored. |
|
|
| 606 | |
707 | |
| 607 | On ANSI colours, bold/blink attributes are used to set |
708 | On ANSI colours, bold/blink attributes are used to set high-intensity |
| 608 | high-intensity foreground/background colors. |
709 | foreground/background colors. |
| 609 | |
710 | |
| 610 | color0-7 are the low-intensity colors. |
711 | color0-7 are the low-intensity colors. |
| 611 | |
712 | |
| 612 | color8-15 are the corresponding high-intensity colors. |
713 | color8-15 are the corresponding high-intensity colors. |
| 613 | |
714 | |
| 614 | I don't like the screen colors. How do I change them? |
715 | I don't like the screen colors. How do I change them? |
| 615 | You can change the screen colors at run-time using ~/.Xdefaults |
716 | You can change the screen colors at run-time using ~/.Xdefaults |
| 616 | resources (or as long-options). |
717 | resources (or as long-options). |
| 617 | |
718 | |
| 618 | Here are values that are supposed to resemble a VGA screen, |
719 | Here are values that are supposed to resemble a VGA screen, including |
| 619 | including the murky brown that passes for low-intensity yellow: |
720 | the murky brown that passes for low-intensity yellow: |
| 620 | |
721 | |
| 621 | URxvt.color0: #000000 |
722 | URxvt.color0: #000000 |
| 622 | URxvt.color1: #A80000 |
723 | URxvt.color1: #A80000 |
| 623 | URxvt.color2: #00A800 |
724 | URxvt.color2: #00A800 |
| 624 | URxvt.color3: #A8A800 |
725 | URxvt.color3: #A8A800 |
| 625 | URxvt.color4: #0000A8 |
726 | URxvt.color4: #0000A8 |
| 626 | URxvt.color5: #A800A8 |
727 | URxvt.color5: #A800A8 |
| 627 | URxvt.color6: #00A8A8 |
728 | URxvt.color6: #00A8A8 |
| 628 | URxvt.color7: #A8A8A8 |
729 | URxvt.color7: #A8A8A8 |
| 629 | |
730 | |
| 630 | URxvt.color8: #000054 |
731 | URxvt.color8: #000054 |
| 631 | URxvt.color9: #FF0054 |
732 | URxvt.color9: #FF0054 |
| 632 | URxvt.color10: #00FF54 |
733 | URxvt.color10: #00FF54 |
| 633 | URxvt.color11: #FFFF54 |
734 | URxvt.color11: #FFFF54 |
| 634 | URxvt.color12: #0000FF |
735 | URxvt.color12: #0000FF |
| 635 | URxvt.color13: #FF00FF |
736 | URxvt.color13: #FF00FF |
| 636 | URxvt.color14: #00FFFF |
737 | URxvt.color14: #00FFFF |
| 637 | URxvt.color15: #FFFFFF |
738 | URxvt.color15: #FFFFFF |
| 638 | |
739 | |
| 639 | And here is a more complete set of non-standard colors described |
740 | And here is a more complete set of non-standard colors described (not by |
| 640 | (not by me) as "pretty girly". |
741 | me) as "pretty girly". |
| 641 | |
742 | |
| 642 | URxvt.cursorColor: #dc74d1 |
743 | URxvt.cursorColor: #dc74d1 |
| 643 | URxvt.pointerColor: #dc74d1 |
744 | URxvt.pointerColor: #dc74d1 |
| 644 | URxvt.background: #0e0e0e |
745 | URxvt.background: #0e0e0e |
| 645 | URxvt.foreground: #4ad5e1 |
746 | URxvt.foreground: #4ad5e1 |
| 646 | URxvt.color0: #000000 |
747 | URxvt.color0: #000000 |
| 647 | URxvt.color8: #8b8f93 |
748 | URxvt.color8: #8b8f93 |
| 648 | URxvt.color1: #dc74d1 |
749 | URxvt.color1: #dc74d1 |
| 649 | URxvt.color9: #dc74d1 |
750 | URxvt.color9: #dc74d1 |
| 650 | URxvt.color2: #0eb8c7 |
751 | URxvt.color2: #0eb8c7 |
| 651 | URxvt.color10: #0eb8c7 |
752 | URxvt.color10: #0eb8c7 |
| 652 | URxvt.color3: #dfe37e |
753 | URxvt.color3: #dfe37e |
| 653 | URxvt.color11: #dfe37e |
754 | URxvt.color11: #dfe37e |
| 654 | URxvt.color5: #9e88f0 |
755 | URxvt.color5: #9e88f0 |
| 655 | URxvt.color13: #9e88f0 |
756 | URxvt.color13: #9e88f0 |
| 656 | URxvt.color6: #73f7ff |
757 | URxvt.color6: #73f7ff |
| 657 | URxvt.color14: #73f7ff |
758 | URxvt.color14: #73f7ff |
| 658 | URxvt.color7: #e1dddd |
759 | URxvt.color7: #e1dddd |
| 659 | URxvt.color15: #e1dddd |
760 | URxvt.color15: #e1dddd |
| 660 | |
761 | |
| 661 | How can I start rxvtd in a race-free way? |
762 | How can I start rxvtd in a race-free way? |
| 662 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
763 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
| 663 | listening socket and then fork. |
764 | listening socket and then fork. |
| 664 | |
765 | |
| 665 | What's with the strange Backspace/Delete key behaviour? |
766 | What's with the strange Backspace/Delete key behaviour? |
| 666 | Assuming that the physical Backspace key corresponds to the |
767 | Assuming that the physical Backspace key corresponds to the BackSpace |
| 667 | BackSpace keysym (not likely for Linux ... see the following |
768 | keysym (not likely for Linux ... see the following question) there are |
| 668 | question) there are two standard values that can be used for |
769 | two standard values that can be used for Backspace: "^H" and "^?". |
| 669 | Backspace: "^H" and "^?". |
|
|
| 670 | |
770 | |
| 671 | Historically, either value is correct, but rxvt-unicode adopts the |
771 | Historically, either value is correct, but rxvt-unicode adopts the |
| 672 | debian policy of using "^?" when unsure, because it's the one only |
772 | debian policy of using "^?" when unsure, because it's the one only only |
| 673 | only correct choice :). |
773 | correct choice :). |
| 674 | |
774 | |
| 675 | Rxvt-unicode tries to inherit the current stty settings and uses the |
775 | Rxvt-unicode tries to inherit the current stty settings and uses the |
| 676 | value of `erase' to guess the value for backspace. If rxvt-unicode |
776 | value of `erase' to guess the value for backspace. If rxvt-unicode |
| 677 | wasn't started from a terminal (say, from a menu or by remote |
777 | wasn't started from a terminal (say, from a menu or by remote shell), |
| 678 | shell), then the system value of `erase', which corresponds to |
778 | then the system value of `erase', which corresponds to CERASE in |
| 679 | CERASE in <termios.h>, will be used (which may not be the same as |
779 | <termios.h>, will be used (which may not be the same as your stty |
| 680 | your stty setting). |
780 | setting). |
| 681 | |
781 | |
| 682 | For starting a new rxvt-unicode: |
782 | For starting a new rxvt-unicode: |
| 683 | |
783 | |
| 684 | # use Backspace = ^H |
784 | # use Backspace = ^H |
| 685 | $ stty erase ^H |
785 | $ stty erase ^H |
| 686 | $ rxvt |
786 | $ rxvt |
| 687 | |
787 | |
| 688 | # use Backspace = ^? |
788 | # use Backspace = ^? |
| 689 | $ stty erase ^? |
789 | $ stty erase ^? |
| 690 | $ rxvt |
790 | $ rxvt |
| 691 | |
791 | |
| 692 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7). |
792 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
| 693 | |
793 | |
| 694 | For an existing rxvt-unicode: |
794 | For an existing rxvt-unicode: |
| 695 | |
795 | |
| 696 | # use Backspace = ^H |
796 | # use Backspace = ^H |
| 697 | $ stty erase ^H |
797 | $ stty erase ^H |
| 698 | $ echo -n "^[[36h" |
798 | $ echo -n "^[[36h" |
| 699 | |
799 | |
| 700 | # use Backspace = ^? |
800 | # use Backspace = ^? |
| 701 | $ stty erase ^? |
801 | $ stty erase ^? |
| 702 | $ echo -n "^[[36l" |
802 | $ echo -n "^[[36l" |
| 703 | |
803 | |
| 704 | This helps satisfy some of the Backspace discrepancies that occur, |
804 | This helps satisfy some of the Backspace discrepancies that occur, but |
| 705 | but if you use Backspace = "^H", make sure that the termcap/terminfo |
805 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
| 706 | value properly reflects that. |
806 | properly reflects that. |
| 707 | |
807 | |
| 708 | The Delete key is a another casualty of the ill-defined Backspace |
808 | The Delete key is a another casualty of the ill-defined Backspace |
| 709 | problem. To avoid confusion between the Backspace and Delete keys, |
809 | problem. To avoid confusion between the Backspace and Delete keys, the |
| 710 | the Delete key has been assigned an escape sequence to match the |
810 | Delete key has been assigned an escape sequence to match the vt100 for |
| 711 | vt100 for Execute ("ESC [ 3 ~") and is in the supplied |
811 | Execute ("ESC [ 3 ~") and is in the supplied termcap/terminfo. |
| 712 | termcap/terminfo. |
|
|
| 713 | |
812 | |
| 714 | Some other Backspace problems: |
813 | Some other Backspace problems: |
| 715 | |
814 | |
| 716 | some editors use termcap/terminfo, some editors (vim I'm told) |
815 | some editors use termcap/terminfo, some editors (vim I'm told) expect |
| 717 | expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for |
816 | Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for help. |
| 718 | help. |
|
|
| 719 | |
817 | |
| 720 | Perhaps someday this will all be resolved in a consistent manner. |
818 | Perhaps someday this will all be resolved in a consistent manner. |
| 721 | |
819 | |
| 722 | I don't like the key-bindings. How do I change them? |
820 | I don't like the key-bindings. How do I change them? |
| 723 | There are some compile-time selections available via configure. |
821 | There are some compile-time selections available via configure. Unless |
| 724 | Unless you have run "configure" with the "--disable-resources" |
822 | you have run "configure" with the "--disable-resources" option you can |
| 725 | option you can use the `keysym' resource to alter the keystrings |
823 | use the `keysym' resource to alter the keystrings associated with |
| 726 | associated with keysyms. |
824 | keysyms. |
| 727 | |
825 | |
| 728 | Here's an example for a URxvt session started using "rxvt -name |
826 | Here's an example for a URxvt session started using "rxvt -name URxvt" |
| 729 | URxvt" |
|
|
| 730 | |
827 | |
| 731 | URxvt.keysym.Home: \033[1~ |
828 | URxvt.keysym.Home: \033[1~ |
| 732 | URxvt.keysym.End: \033[4~ |
829 | URxvt.keysym.End: \033[4~ |
| 733 | URxvt.keysym.C-apostrophe: \033<C-'> |
830 | URxvt.keysym.C-apostrophe: \033<C-'> |
| 734 | URxvt.keysym.C-slash: \033<C-/> |
831 | URxvt.keysym.C-slash: \033<C-/> |
| 735 | URxvt.keysym.C-semicolon: \033<C-;> |
832 | URxvt.keysym.C-semicolon: \033<C-;> |
| 736 | URxvt.keysym.C-grave: \033<C-`> |
833 | URxvt.keysym.C-grave: \033<C-`> |
| 737 | URxvt.keysym.C-comma: \033<C-,> |
834 | URxvt.keysym.C-comma: \033<C-,> |
| 738 | URxvt.keysym.C-period: \033<C-.> |
835 | URxvt.keysym.C-period: \033<C-.> |
| 739 | URxvt.keysym.C-0x60: \033<C-`> |
836 | URxvt.keysym.C-0x60: \033<C-`> |
| 740 | URxvt.keysym.C-Tab: \033<C-Tab> |
837 | URxvt.keysym.C-Tab: \033<C-Tab> |
| 741 | URxvt.keysym.C-Return: \033<C-Return> |
838 | URxvt.keysym.C-Return: \033<C-Return> |
| 742 | URxvt.keysym.S-Return: \033<S-Return> |
839 | URxvt.keysym.S-Return: \033<S-Return> |
| 743 | URxvt.keysym.S-space: \033<S-Space> |
840 | URxvt.keysym.S-space: \033<S-Space> |
| 744 | URxvt.keysym.M-Up: \033<M-Up> |
841 | URxvt.keysym.M-Up: \033<M-Up> |
| 745 | URxvt.keysym.M-Down: \033<M-Down> |
842 | URxvt.keysym.M-Down: \033<M-Down> |
| 746 | URxvt.keysym.M-Left: \033<M-Left> |
843 | URxvt.keysym.M-Left: \033<M-Left> |
| 747 | URxvt.keysym.M-Right: \033<M-Right> |
844 | URxvt.keysym.M-Right: \033<M-Right> |
| 748 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
845 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
| 749 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
846 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
| 750 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
847 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
| 751 | |
848 | |
| 752 | See some more examples in the documentation for the keysym resource. |
849 | See some more examples in the documentation for the keysym resource. |
| 753 | |
850 | |
| 754 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How |
851 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
| 755 | do I make use of them? For example, the Sun Keyboard type 4 has the |
852 | How do I make use of them? For example, the Sun Keyboard type 4 |
| 756 | following mappings that rxvt-unicode doesn't recognize. |
853 | has the following mappings that rxvt-unicode doesn't recognize. |
| 757 | KP_Insert == Insert |
854 | KP_Insert == Insert |
| 758 | F22 == Print |
855 | F22 == Print |
| 759 | F27 == Home |
856 | F27 == Home |
| 760 | F29 == Prior |
857 | F29 == Prior |
| 761 | F33 == End |
858 | F33 == End |
| 762 | F35 == Next |
859 | F35 == Next |
| 763 | |
860 | |
| 764 | Rather than have rxvt-unicode try to accommodate all the various |
861 | Rather than have rxvt-unicode try to accommodate all the various |
| 765 | possible keyboard mappings, it is better to use `xmodmap' to remap |
862 | possible keyboard mappings, it is better to use `xmodmap' to remap the |
| 766 | the keys as required for your particular machine. |
863 | keys as required for your particular machine. |
| 767 | |
864 | |
| 768 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
865 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
| 769 | I need this to decide about setting colors etc. |
866 | I need this to decide about setting colors etc. |
| 770 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you |
867 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
| 771 | can check and see if that is set. Note that several programs, JED, |
868 | check and see if that is set. Note that several programs, JED, slrn, |
| 772 | slrn, Midnight Commander automatically check this variable to decide |
869 | Midnight Commander automatically check this variable to decide whether |
| 773 | whether or not to use color. |
870 | or not to use color. |
| 774 | |
871 | |
| 775 | How do I set the correct, full IP address for the DISPLAY variable? |
872 | How do I set the correct, full IP address for the DISPLAY variable? |
| 776 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
873 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
| 777 | insecure mode then it is possible to use the following shell script |
874 | insecure mode then it is possible to use the following shell script |
| 778 | snippets to correctly set the display. If your version of |
875 | snippets to correctly set the display. If your version of rxvt-unicode |
| 779 | rxvt-unicode wasn't also compiled with ESCZ_ANSWER (as assumed in |
876 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) |
| 780 | these snippets) then the COLORTERM variable can be used to |
877 | then the COLORTERM variable can be used to distinguish rxvt-unicode from |
| 781 | distinguish rxvt-unicode from a regular xterm. |
878 | a regular xterm. |
| 782 | |
879 | |
| 783 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell |
880 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
| 784 | script snippets: |
881 | snippets: |
| 785 | |
882 | |
| 786 | # Bourne/Korn/POSIX family of shells: |
883 | # Bourne/Korn/POSIX family of shells: |
| 787 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
884 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
| 788 | if [ ${TERM:-foo} = xterm ]; then |
885 | if [ ${TERM:-foo} = xterm ]; then |
| 789 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
886 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
| 790 | echo -n '^[Z' |
887 | echo -n '^[Z' |
| 791 | read term_id |
888 | read term_id |
| 792 | stty icanon echo |
889 | stty icanon echo |
| 793 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
890 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
| 794 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
891 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
| 795 | read DISPLAY # set it in our local shell |
892 | read DISPLAY # set it in our local shell |
| 796 | fi |
|
|
| 797 | fi |
893 | fi |
|
|
894 | fi |
| 798 | |
895 | |
| 799 | How do I compile the manual pages for myself? |
896 | How do I compile the manual pages for myself? |
| 800 | You need to have a recent version of perl installed as |
897 | You need to have a recent version of perl installed as /usr/bin/perl, |
| 801 | /usr/bin/perl, one that comes with pod2man, pod2text and pod2html. |
898 | one that comes with pod2man, pod2text and pod2html. Then go to the doc |
| 802 | Then go to the doc subdirectory and enter "make alldoc". |
899 | subdirectory and enter "make alldoc". |
| 803 | |
900 | |
| 804 | My question isn't answered here, can I ask a human? |
901 | My question isn't answered here, can I ask a human? |
| 805 | Before sending me mail, you could go to IRC: "irc.freenode.net", |
902 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
| 806 | channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might |
903 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
| 807 | be interested in learning about new and exciting problems (but not |
904 | interested in learning about new and exciting problems (but not FAQs :). |
| 808 | FAQs :). |
|
|
| 809 | |
905 | |
