| 1 | =head1 NAME |
1 | =head1 NAME |
| 2 | |
2 | |
| 3 | RXVT TECHNICAL REFERENCE - command sequences and background information |
3 | RXVT REFERENCE - FAQ, command sequences and other background information |
|
|
4 | |
|
|
5 | =head1 FREQUENTLY ASKED QUESTIONS |
|
|
6 | |
|
|
7 | =over 4 |
|
|
8 | |
|
|
9 | =item How do I know which rxvt-unicode version I'm using? |
|
|
10 | |
|
|
11 | The version number is displayed with the usage (-h). Also the escape |
|
|
12 | sequence C<ESC[8n> sets the window title to the version number. |
|
|
13 | |
|
|
14 | =item When I log-in to another system it tells me about missing terminfo data? |
|
|
15 | |
|
|
16 | The terminal description used by rxvt-unicode is not as widely available |
|
|
17 | as that for xterm, or even rxvt (for which the same problem often arises). |
|
|
18 | |
|
|
19 | The correct solution for this problem is to install the terminfo, this can |
|
|
20 | be done like this (with ncurses' infocmp): |
|
|
21 | |
|
|
22 | REMOTE=remotesystem.domain |
|
|
23 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
|
|
24 | |
|
|
25 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
26 | |
|
|
27 | If you cannot or do not want to do this, then you can simply set |
|
|
28 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
|
|
29 | problems arising, which includes wrong keymapping, less and different |
|
|
30 | colours and some refresh errors in fullscreen applications. It's a nice |
|
|
31 | quick-and-dirty workaround for rare cases, though. |
|
|
32 | |
|
|
33 | If you always want to do this you can either recompile rxvt-unicode with |
|
|
34 | the desired TERM value or use a resource to set it: |
|
|
35 | |
|
|
36 | URxvt.termName: rxvt |
|
|
37 | |
|
|
38 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
|
|
39 | the rxvt terminfo file with the rxvt-unicode one. |
|
|
40 | |
|
|
41 | =item I need a termcap file entry. |
|
|
42 | |
|
|
43 | You could use rxvt's termcap entry with resonable results in many cases. |
|
|
44 | You can also create a termcap entry by using terminfo's infocmp program |
|
|
45 | like this: |
|
|
46 | |
|
|
47 | infocmp -C rxvt-unicode |
|
|
48 | |
|
|
49 | OR you could this termcap entry: |
|
|
50 | |
|
|
51 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
|
|
52 | :am:bw:eo:km:mi:ms:xn:xo:\ |
|
|
53 | :co#80:it#8:li#24:\ |
|
|
54 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
|
|
55 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
|
|
56 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ |
|
|
57 | :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ |
|
|
58 | :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ |
|
|
59 | :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ |
|
|
60 | :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
|
|
61 | :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ |
|
|
62 | :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ |
|
|
63 | :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ |
|
|
64 | :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ |
|
|
65 | :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ |
|
|
66 | :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ |
|
|
67 | :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ |
|
|
68 | :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
|
|
69 | :vs=\E[?25h: |
|
|
70 | |
|
|
71 | =item How can I configure rxvt-unicode so that it looks similar to the original rxvt? |
|
|
72 | |
|
|
73 | Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode |
|
|
74 | behave similar to the original rxvt: |
|
|
75 | |
|
|
76 | URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
|
|
77 | URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
|
|
78 | |
|
|
79 | =item Rxvt-unicode does not seem to understand the selected encoding? |
|
|
80 | |
|
|
81 | =item Unicode does not seem to work? |
|
|
82 | |
|
|
83 | If you encounter strange problems like typing an accented character but |
|
|
84 | getting two unrelated other characters or similar, or if program output is |
|
|
85 | subtly garbled, then you should check your locale settings. |
|
|
86 | |
|
|
87 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
|
|
88 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
|
|
89 | login script running within the rxvt-unicode window changes the locale to |
|
|
90 | sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
|
|
91 | |
|
|
92 | The best thing is to fix your startup environment, as you will likely run |
|
|
93 | into other problems. If nothing works you can try this in your .profile. |
|
|
94 | |
|
|
95 | printf '\e]701;%s\007' "$LC_CTYPE" |
|
|
96 | |
|
|
97 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
|
|
98 | supported on your systems. Some systems have a C<locale> command which |
|
|
99 | displays this. If it displays sth. like: |
|
|
100 | |
|
|
101 | locale: Cannot set LC_CTYPE to default locale: ... |
|
|
102 | |
|
|
103 | Then the locale you specified is not supported on your system. |
|
|
104 | |
|
|
105 | If nothing works and you are sure that everything is set correctly then |
|
|
106 | you will need to remember a little known fact: Some programs just don't |
|
|
107 | support locales :( |
|
|
108 | |
|
|
109 | =item Why do some characters look so much different than others? |
|
|
110 | |
|
|
111 | =item How does rxvt-unicode choose fonts? |
|
|
112 | |
|
|
113 | Most fonts do not contain the full range of Unicode, which is |
|
|
114 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
115 | your system/os) have specified does not cover all the characters you want |
|
|
116 | to display. |
|
|
117 | |
|
|
118 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
|
|
119 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
120 | bad. Many fonts have totally strange characters that don't resemble the |
|
|
121 | correct glyph at all, and rxvt-unicode lacks the artificial intelligence |
|
|
122 | to detect that a specific glyph is wrong: it has to believe the font that |
|
|
123 | the characters it contains indeed look correct. |
|
|
124 | |
|
|
125 | In that case, select a font of your taste and add it to the font list, |
|
|
126 | e.g.: |
|
|
127 | |
|
|
128 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
|
|
129 | |
|
|
130 | When rxvt-unicode sees a character, it will first look at the base |
|
|
131 | font. If the base font does not contain the character, it will go to the |
|
|
132 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
133 | search and use less resources within rxvt-unicode and the X-server. |
|
|
134 | |
|
|
135 | The only limitation is that all the fonts must not be larger than the base |
|
|
136 | font, as the base font defines the principal cell size, which must be the |
|
|
137 | same due to the way terminals work. |
|
|
138 | |
|
|
139 | =item Why do some chinese characters look so different than others? |
|
|
140 | |
|
|
141 | This is because there is a difference between script and language -- |
|
|
142 | rxvt-unicode does not know which language the text that is output |
|
|
143 | is, as it only knows the unicode character codes. If rxvt-unicode |
|
|
144 | first sees a japanese character, it might choose a japanese font for |
|
|
145 | it. Subsequent japanese characters will take that font. Now, many chinese |
|
|
146 | characters aren't represented in japanese fonts, so when the first |
|
|
147 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
148 | -- unfortunately at this point, it will still use the japanese font for |
|
|
149 | japanese characters that are also chinese. |
|
|
150 | |
|
|
151 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
152 | list (see the previous question). The key is to view the font list as |
|
|
153 | a preference list: If you expect more japanese, list a japanese font |
|
|
154 | first. If you expect more chinese, put a chinese font first. |
|
|
155 | |
|
|
156 | In the future it might be possible to switch preferences at runtime (the |
|
|
157 | internal data structure has no problem with using different fonts for |
|
|
158 | the same character at the same time, but no interface for this has been |
|
|
159 | designed yet). |
|
|
160 | |
|
|
161 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
|
|
162 | |
|
|
163 | Most fonts were not designed for terminal use, which means that character |
|
|
164 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
165 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
166 | these characters. For characters that are just "a bit" too wide a special |
|
|
167 | "careful" rendering mode is used that redraws adjacent characters. |
|
|
168 | |
|
|
169 | All of this requires that fonts do not lie about character sizes, |
|
|
170 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
171 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
172 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
173 | cases). |
|
|
174 | |
|
|
175 | It's not clear (to me at least), wether this is a bug in Xft, freetype, or |
|
|
176 | the respective font. If you encounter this problem there is no way to work |
|
|
177 | around this except by using a different font. |
|
|
178 | |
|
|
179 | All of this is not a problem when using X11 core fonts, as their bounding |
|
|
180 | box data is correct. |
|
|
181 | |
|
|
182 | =item My Compose (Multi_key) key is no longer working. |
|
|
183 | |
|
|
184 | The most common causes for this are that either your locale is not set |
|
|
185 | correctly, or you specified a B<preeditStyle> that is not supported by |
|
|
186 | your input method. For example, if you specified B<OverTheSpot> and |
|
|
187 | your input method (e.g. the default input method handling Compose keys) |
|
|
188 | does not support this (for instance because it is not visual), then |
|
|
189 | rxvt-unicode will continue without an input method. |
|
|
190 | |
|
|
191 | In this case either do not specify a B<preeditStyle> or specify more than |
|
|
192 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
|
|
193 | |
|
|
194 | =item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
|
|
195 | |
|
|
196 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
|
|
197 | international keyboards) or simply use ISO 14755 support to your |
|
|
198 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
199 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
|
|
200 | character and so on. |
|
|
201 | |
|
|
202 | =item How can I keep rxvt-unicode from using reverse video so much? |
|
|
203 | |
|
|
204 | First of all, make sure you are running with the right terminfo |
|
|
205 | (C<urxvt>), which will get rid of most of these effects. Then make sure |
|
|
206 | you have specified colours for italic and bold, as otherwise rxvt-unicode |
|
|
207 | might use reverse video to simulate the effect: |
|
|
208 | |
|
|
209 | URxvt*colorBD: white |
|
|
210 | URxvt*colorIT: green |
|
|
211 | |
|
|
212 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
|
|
213 | |
|
|
214 | For some unexplainable reason, some programs (i.e. irssi) assume a very |
|
|
215 | weird colour palette when confronted with a terminal with more than the |
|
|
216 | standard 8 colours (rxvt-unicode supports 88). The right fix is, of |
|
|
217 | course, to fix these programs not to assume non-ISO colours without very |
|
|
218 | good reasons. |
|
|
219 | |
|
|
220 | In the meantime, you can either edit your C<urxvt> terminfo definition to |
|
|
221 | only claim 8 colour support or use C<TERM=rxvt>, which will fix colours |
|
|
222 | but keep you from using other rxvt-unicode features. |
|
|
223 | |
|
|
224 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
|
|
225 | |
|
|
226 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
|
|
227 | in your compile environment, or an implementation that implements it, |
|
|
228 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
|
|
229 | B<wchar_t> is represented as unicode. |
|
|
230 | |
|
|
231 | As you might have guessed, FreeBSD does neither define this symobl nor |
|
|
232 | does it support it. Instead, it uses it's own internal representation of |
|
|
233 | B<wchar_t>. This is, of course, completely legal. |
|
|
234 | |
|
|
235 | However, C<__STDC_ISO_10646__> is the only sane way to support |
|
|
236 | multi-language apps in an OS, as using a locale-dependent (and |
|
|
237 | non-standardized) representation of B<wchar_t> makes it impossible to |
|
|
238 | convert between B<wchar_t> (as used by X11 and your applications) and any |
|
|
239 | other encoding without implementing OS-specific-wrappers for each and |
|
|
240 | every locale. There simply are no APIs to convert B<wchar_t> into anything |
|
|
241 | except the current locale encoding. |
|
|
242 | |
|
|
243 | Some applications (such as the formidable B<mlterm>) work around this |
|
|
244 | by carrying their own replacement functions for character set handling |
|
|
245 | with them, and either implementing OS-dependent hacks or doing multiple |
|
|
246 | conversions (which is slow and unreliable in case the OS implements |
|
|
247 | encodings slightly different than the terminal emulator). |
|
|
248 | |
|
|
249 | The rxvt-unicode author insists that the right way to fix this is in the |
|
|
250 | system libraries once and for all, instead of forcing every app to carry |
|
|
251 | complete replacements. |
|
|
252 | |
|
|
253 | =item How does rxvt-unicode determine the encoding to use? |
|
|
254 | |
|
|
255 | =item Is there an option to switch encodings? |
|
|
256 | |
|
|
257 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
|
|
258 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
|
|
259 | UTF-8 or any other encodings with respect to terminal I/O. |
|
|
260 | |
|
|
261 | The reasons is that there exists a perfectly fine mechanism for selecting |
|
|
262 | the encoding, doing I/O and (most important) communicating this to all |
|
|
263 | applications so everybody agrees on character properties such as width and |
|
|
264 | code number. This mechanism is the I<locale>. |
|
|
265 | |
|
|
266 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
|
|
267 | programs doing the same (that is, most) will automatically agree in the |
|
|
268 | interpretation of characters. |
|
|
269 | |
|
|
270 | Unfortunately, there is no system-independent way to select locales, nor |
|
|
271 | is there a standard on how locale specifiers will look like. |
|
|
272 | |
|
|
273 | On most systems, the content of the C<LC_CTYPE> environment variable |
|
|
274 | contains an arbitrary string which corresponds to an already-installed |
|
|
275 | locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>, |
|
|
276 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
|
|
277 | (i.e. C<de> or C<german>) are also common. |
|
|
278 | |
|
|
279 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
280 | the encoding, ignores country or language-specific settings, |
|
|
281 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode. |
|
|
282 | |
|
|
283 | If you want to use a specific encoding you have to make sure you start |
|
|
284 | rxvt-unicode with the correct C<LC_CTYPE> category. |
|
|
285 | |
|
|
286 | =item Can I switch locales at runtime? |
|
|
287 | |
|
|
288 | Yes, using an escape sequence. Try sth. like this, which sets |
|
|
289 | rxvt-unicode's idea of C<LC_CTYPE>. |
|
|
290 | |
|
|
291 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
292 | |
|
|
293 | See also the previous question. |
|
|
294 | |
|
|
295 | Sometimes this capability is rather handy when you want to work in one |
|
|
296 | locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For |
|
|
297 | example, I use this script to start C<xjdic>, which first switches to a |
|
|
298 | locale supported by xjdic and back later: |
|
|
299 | |
|
|
300 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
301 | xjdic -js |
|
|
302 | printf '\e]701;%s\007' de_DE.UTF-8 |
|
|
303 | |
|
|
304 | =item Can I switch the fonts at runtime? |
|
|
305 | |
|
|
306 | Yes, using an escape sequence. Try sth. like this, which has the same |
|
|
307 | effect as using the C<-fn> switch, and takes effect immediately: |
|
|
308 | |
|
|
309 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
|
|
310 | |
|
|
311 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
312 | japanese font), but you have to switch to chinese temporarily, where |
|
|
313 | japanese fonts would only be in your way. |
|
|
314 | |
|
|
315 | You can think of this as a kind of manual ISO-2022 switching. |
|
|
316 | |
|
|
317 | =item Why do italic characters look as if clipped? |
|
|
318 | |
|
|
319 | Many fonts have difficulties with italic characters and hinting. For |
|
|
320 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
|
|
321 | Mono> completely fails in it's italic face. A workaround is to enable |
|
|
322 | freetype autohinting, i.e. like this: |
|
|
323 | |
|
|
324 | URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
325 | URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
326 | |
|
|
327 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
|
|
328 | |
|
|
329 | You can specify separate locales for the input method and the rest of the |
|
|
330 | terminal, using the resource C<imlocale>: |
|
|
331 | |
|
|
332 | URxvt*imlocale: ja_JP.EUC-JP |
|
|
333 | |
|
|
334 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
|
|
335 | use your input method. Please note, however, that you will not be able to |
|
|
336 | input characters outside C<EUC-JP> in a normal way then, as your input |
|
|
337 | method limits you. |
|
|
338 | |
|
|
339 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
|
|
340 | |
|
|
341 | Rxvt-unicode tries to obey the rule of not charging you for sth. you |
|
|
342 | don't use. One thing you should try is to configure out all settings that |
|
|
343 | you don't need, for example, Xft support is a resource hog by design, |
|
|
344 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
345 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
346 | |
|
|
347 | Also, many people (me included) like large windows and even larger |
|
|
348 | scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
|
|
349 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
350 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
351 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
|
|
352 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
353 | |
|
|
354 | =item Can I speed up Xft rendering somehow? |
|
|
355 | |
|
|
356 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
357 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
358 | antialiasing (by appending C<:antialiasing=false>), which saves lots of |
|
|
359 | memory and also speeds up rendering considerably. |
|
|
360 | |
|
|
361 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
|
|
362 | |
|
|
363 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
364 | fall back to it's default font search list it will prefer X11 core |
|
|
365 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
366 | antialiasing disabled for most of them, because the author thinks they |
|
|
367 | look best that way. |
|
|
368 | |
|
|
369 | If you want antialiasing, you have to specify the fonts manually. |
|
|
370 | |
|
|
371 | =item Mouse cut/paste suddenly no longer works. |
|
|
372 | |
|
|
373 | Make sure that mouse reporting is actually turned off since killing |
|
|
374 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
375 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
376 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
377 | depressed. See @@RXVT_NAME@@(7) |
|
|
378 | |
|
|
379 | =item What's with this bold/blink stuff? |
|
|
380 | |
|
|
381 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
|
|
382 | standard foreground colour. |
|
|
383 | |
|
|
384 | For the standard background colour, blinking will actually make the |
|
|
385 | text blink when compiled with C<--enable-blinking>. with standard |
|
|
386 | colours. Without C<--enable-blinking>, the blink attribute will be |
|
|
387 | ignored. |
|
|
388 | |
|
|
389 | On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
390 | foreground/background colors. |
|
|
391 | |
|
|
392 | color0-7 are the low-intensity colors. |
|
|
393 | |
|
|
394 | color8-15 are the corresponding high-intensity colors. |
|
|
395 | |
|
|
396 | =item I don't like the screen colors. How do I change them? |
|
|
397 | |
|
|
398 | You can change the screen colors at run-time using F<~/.Xdefaults> |
|
|
399 | resources (or as long-options). |
|
|
400 | |
|
|
401 | Here are values that are supposed to resemble a VGA screen, |
|
|
402 | including the murky brown that passes for low-intensity yellow: |
|
|
403 | |
|
|
404 | URxvt*color0: #000000 |
|
|
405 | URxvt*color1: #A80000 |
|
|
406 | URxvt*color2: #00A800 |
|
|
407 | URxvt*color3: #A8A800 |
|
|
408 | URxvt*color4: #0000A8 |
|
|
409 | URxvt*color5: #A800A8 |
|
|
410 | URxvt*color6: #00A8A8 |
|
|
411 | URxvt*color7: #A8A8A8 |
|
|
412 | |
|
|
413 | URxvt*color8: #000054 |
|
|
414 | URxvt*color9: #FF0054 |
|
|
415 | URxvt*color10: #00FF54 |
|
|
416 | URxvt*color11: #FFFF54 |
|
|
417 | URxvt*color12: #0000FF |
|
|
418 | URxvt*color13: #FF00FF |
|
|
419 | URxvt*color14: #00FFFF |
|
|
420 | URxvt*color15: #FFFFFF |
|
|
421 | |
|
|
422 | And here is a more complete set of non-standard colors described as |
|
|
423 | "pretty girly": |
|
|
424 | |
|
|
425 | URxvt.cursorColor: #dc74d1 |
|
|
426 | URxvt.pointerColor: #dc74d1 |
|
|
427 | URxvt.background: #0e0e0e |
|
|
428 | URxvt.foreground: #4ad5e1 |
|
|
429 | URxvt.color0: #000000 |
|
|
430 | URxvt.color8: #8b8f93 |
|
|
431 | URxvt.color1: #dc74d1 |
|
|
432 | URxvt.color9: #dc74d1 |
|
|
433 | URxvt.color2: #0eb8c7 |
|
|
434 | URxvt.color10: #0eb8c7 |
|
|
435 | URxvt.color3: #dfe37e |
|
|
436 | URxvt.color11: #dfe37e |
|
|
437 | URxvt.color5: #9e88f0 |
|
|
438 | URxvt.color13: #9e88f0 |
|
|
439 | URxvt.color6: #73f7ff |
|
|
440 | URxvt.color14: #73f7ff |
|
|
441 | URxvt.color7: #e1dddd |
|
|
442 | URxvt.color15: #e1dddd |
|
|
443 | |
|
|
444 | =item What's with the strange Backspace/Delete key behaviour? |
|
|
445 | |
|
|
446 | Assuming that the physical Backspace key corresponds to the |
|
|
447 | BackSpace keysym (not likely for Linux ... see the following |
|
|
448 | question) there are two standard values that can be used for |
|
|
449 | Backspace: C<^H> and C<^?>. |
|
|
450 | |
|
|
451 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
452 | policy of using C<^?> when unsure, because it's the one only only correct |
|
|
453 | choice :). |
|
|
454 | |
|
|
455 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
456 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
457 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
458 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
|
|
459 | be used (which may not be the same as your stty setting). |
|
|
460 | |
|
|
461 | For starting a new rxvt-unicode: |
|
|
462 | |
|
|
463 | # use Backspace = ^H |
|
|
464 | $ stty erase ^H |
|
|
465 | $ @@RXVT_NAME@@ |
|
|
466 | |
|
|
467 | # use Backspace = ^? |
|
|
468 | $ stty erase ^? |
|
|
469 | $ @@RXVT_NAME@@ |
|
|
470 | |
|
|
471 | Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7). |
|
|
472 | |
|
|
473 | For an existing rxvt-unicode: |
|
|
474 | |
|
|
475 | # use Backspace = ^H |
|
|
476 | $ stty erase ^H |
|
|
477 | $ echo -n "^[[36h" |
|
|
478 | |
|
|
479 | # use Backspace = ^? |
|
|
480 | $ stty erase ^? |
|
|
481 | $ echo -n "^[[36l" |
|
|
482 | |
|
|
483 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
484 | if you use Backspace = C<^H>, make sure that the termcap/terminfo value |
|
|
485 | properly reflects that. |
|
|
486 | |
|
|
487 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
488 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
489 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
490 | (ESC[3~) and is in the supplied termcap/terminfo. |
|
|
491 | |
|
|
492 | Some other Backspace problems: |
|
|
493 | |
|
|
494 | some editors use termcap/terminfo, |
|
|
495 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
496 | GNU Emacs (and Emacs-like editors) use ^H for help. |
|
|
497 | |
|
|
498 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
499 | |
|
|
500 | =item I don't like the key-bindings. How do I change them? |
|
|
501 | |
|
|
502 | There are some compile-time selections available via configure. Unless |
|
|
503 | you have run "configure" with the C<--disable-resources> option you can |
|
|
504 | use the `keysym' resource to alter the keystrings associated with keysym |
|
|
505 | 0xFF00 - 0xFFFF (function, cursor keys, etc). |
|
|
506 | |
|
|
507 | Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270' |
|
|
508 | |
|
|
509 | !# ----- special uses ------: |
|
|
510 | ! tn3270 login, remap function and arrow keys. |
|
|
511 | tn3270*font: *clean-bold-*-*--15-* |
|
|
512 | |
|
|
513 | ! keysym - used by rxvt only |
|
|
514 | ! Delete - ^D |
|
|
515 | tn3270*keysym.0xFFFF: \004 |
|
|
516 | |
|
|
517 | ! Home - ^A |
|
|
518 | tn3270*keysym.0xFF50: \001 |
|
|
519 | ! Left - ^B |
|
|
520 | tn3270*keysym.0xFF51: \002 |
|
|
521 | ! Up - ^P |
|
|
522 | tn3270*keysym.0xFF52: \020 |
|
|
523 | ! Right - ^F |
|
|
524 | tn3270*keysym.0xFF53: \006 |
|
|
525 | ! Down - ^N |
|
|
526 | tn3270*keysym.0xFF54: \016 |
|
|
527 | ! End - ^E |
|
|
528 | tn3270*keysym.0xFF57: \005 |
|
|
529 | |
|
|
530 | ! F1 - F12 |
|
|
531 | tn3270*keysym.0xFFBE: \e1 |
|
|
532 | tn3270*keysym.0xFFBF: \e2 |
|
|
533 | tn3270*keysym.0xFFC0: \e3 |
|
|
534 | tn3270*keysym.0xFFC1: \e4 |
|
|
535 | tn3270*keysym.0xFFC2: \e5 |
|
|
536 | tn3270*keysym.0xFFC3: \e6 |
|
|
537 | tn3270*keysym.0xFFC4: \e7 |
|
|
538 | tn3270*keysym.0xFFC5: \e8 |
|
|
539 | tn3270*keysym.0xFFC6: \e9 |
|
|
540 | tn3270*keysym.0xFFC7: \e0 |
|
|
541 | tn3270*keysym.0xFFC8: \e- |
|
|
542 | tn3270*keysym.0xFFC9: \e= |
|
|
543 | |
|
|
544 | ! map Prior/Next to F7/F8 |
|
|
545 | tn3270*keysym.0xFF55: \e7 |
|
|
546 | tn3270*keysym.0xFF56: \e8 |
|
|
547 | |
|
|
548 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
|
|
549 | How do I make use of them? For example, the Sun Keyboard type 4 |
|
|
550 | has the following mappings that rxvt-unicode doesn't recognize. |
|
|
551 | |
|
|
552 | KP_Insert == Insert |
|
|
553 | F22 == Print |
|
|
554 | F27 == Home |
|
|
555 | F29 == Prior |
|
|
556 | F33 == End |
|
|
557 | F35 == Next |
|
|
558 | |
|
|
559 | Rather than have rxvt-unicode try to accommodate all the various possible keyboard |
|
|
560 | mappings, it is better to use `xmodmap' to remap the keys as required for |
|
|
561 | your particular machine. |
|
|
562 | |
|
|
563 | =item How do I distinguish if I'm running rxvt-unicode or a regular xterm? |
|
|
564 | I need this to decide about setting colors etc. |
|
|
565 | |
|
|
566 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
|
|
567 | check and see if that is set. Note that several programs, JED, slrn, |
|
|
568 | Midnight Commander automatically check this variable to decide whether or |
|
|
569 | not to use color. |
|
|
570 | |
|
|
571 | =item How do I set the correct, full IP address for the DISPLAY variable? |
|
|
572 | |
|
|
573 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
|
|
574 | insecure mode then it is possible to use the following shell script |
|
|
575 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
576 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
|
|
577 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
578 | regular xterm. |
|
|
579 | |
|
|
580 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
581 | snippets: |
|
|
582 | |
|
|
583 | # Bourne/Korn/POSIX family of shells: |
|
|
584 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
585 | if [ ${TERM:-foo} = xterm ]; then |
|
|
586 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
587 | echo -n '^[Z' |
|
|
588 | read term_id |
|
|
589 | stty icanon echo |
|
|
590 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
591 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
592 | read DISPLAY # set it in our local shell |
|
|
593 | fi |
|
|
594 | fi |
|
|
595 | |
|
|
596 | =item How do I compile the manual pages for myself? |
|
|
597 | |
|
|
598 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
|
|
599 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
|
|
600 | the doc subdirectory and enter C<make alldoc>. |
|
|
601 | |
|
|
602 | =item My question isn't answered here, can I ask a human? |
|
|
603 | |
|
|
604 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
|
|
605 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
|
|
606 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
607 | |
|
|
608 | =back |
| 4 | |
609 | |
| 5 | =head1 SYNOPSIS |
610 | =head1 SYNOPSIS |
| 6 | |
611 | |
| 7 | # set a new font set |
612 | # set a new font set |
| 8 | printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho" |
613 | printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho" |
| … | |
… | |
| 1479 | you use an X11 font requiring one of these encodings. |
2084 | you use an X11 font requiring one of these encodings. |
| 1480 | |
2085 | |
| 1481 | =begin table |
2086 | =begin table |
| 1482 | |
2087 | |
| 1483 | all all available codeset groups |
2088 | all all available codeset groups |
| 1484 | cn common chinese encodings |
2089 | zh common chinese encodings |
| 1485 | cn_ext rarely used but very big chinese encodigs |
2090 | zh_ext rarely used but very big chinese encodigs |
| 1486 | jp common japanese encodings |
2091 | jp common japanese encodings |
| 1487 | jp_ext rarely used but big japanese encodings |
2092 | jp_ext rarely used but big japanese encodings |
| 1488 | kr korean encodings |
2093 | kr korean encodings |
| 1489 | |
2094 | |
| 1490 | =end table |
2095 | =end table |
