ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.txt
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents):
Revision 1.1 by root, Tue Jan 11 02:24:59 2005 UTC vs.
Revision 1.19 by root, Sun Apr 17 22:36:13 2005 UTC

1NAME 1NAME
2 RXVT REFERENCE - FAQ, command sequences and other background information 2 RXVT REFERENCE - FAQ, command sequences and other background information
3
4SYNOPSIS
5 # set a new font set
6 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
7
8 # change the locale and tell rxvt-unicode about it
9 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
10
11 # set window title
12 printf '\33]2;%s\007' "new window title"
13
14DESCRIPTION
15 This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
16 all escape sequences, and other background information.
17
18 The newest version of this document is also available on the World Wide
19 Web at
20 <http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
3 21
4FREQUENTLY ASKED QUESTIONS 22FREQUENTLY ASKED QUESTIONS
5 How do I know which rxvt-unicode version I'm using? 23 How do I know which rxvt-unicode version I'm using?
6 The version number is displayed with the usage (-h). Also the escape 24 The version number is displayed with the usage (-h). Also the escape
7 sequence "ESC[8n" sets the window title to the version number. 25 sequence "ESC [ 8 n" sets the window title to the version number.
26
27 I am using Debian GNU/Linux and have a problem...
28 The Debian GNU/Linux package of rxvt-unicode contains large patches
29 that considerably change the behaviour of rxvt-unicode. Before
30 reporting a bug to the original rxvt-unicode author please download
31 and install the genuine version
32 (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
33 problem. If you cannot, chances are that the problems are specific
34 to Debian GNU/Linux, in which case it should be reported via the
35 Debian Bug Tracking System (use "reportbug" to report the bug).
36
37 For other problems that also affect the Debian package, you can and
38 probably should use the Debian BTS, too, because, after all, it's
39 also a bug in the Debian version and it serves as a reminder for
40 other users that might encounter the same issue.
8 41
9 When I log-in to another system it tells me about missing terminfo data? 42 When I log-in to another system it tells me about missing terminfo data?
10 The terminal description used by rxvt-unicode is not as widely 43 The terminal description used by rxvt-unicode is not as widely
11 available as that for xterm, or even rxvt (for which the same 44 available as that for xterm, or even rxvt (for which the same
12 problem often arises). 45 problem often arises).
… …
24 problems arising, which includes wrong keymapping, less and 57 problems arising, which includes wrong keymapping, less and
25 different colours and some refresh errors in fullscreen 58 different colours and some refresh errors in fullscreen
26 applications. It's a nice quick-and-dirty workaround for rare cases, 59 applications. It's a nice quick-and-dirty workaround for rare cases,
27 though. 60 though.
28 61
29 If you always want to do this you can either recompile rxvt-unicode 62 If you always want to do this (and are fine with the consequences)
30 with the desired TERM value or use a resource to set it: 63 you can either recompile rxvt-unicode with the desired TERM value or
64 use a resource to set it:
31 65
32 URxvt.termName: rxvt 66 URxvt.termName: rxvt
33 67
34 If you don't plan to use rxvt (quite common...) you could also 68 If you don't plan to use rxvt (quite common...) you could also
35 replace the rxvt terminfo file with the rxvt-unicode one. 69 replace the rxvt terminfo file with the rxvt-unicode one.
36 70
71 "bash"'s readline does not work correctly under rxvt.
37 I need a termcap file entry. 72 I need a termcap file entry.
73 One reason you might want this is that some distributions or
74 operating systems still compile some programs using the
75 long-obsoleted termcap library (Fedora Core's bash is one example)
76 and rely on a termcap entry for "rxvt-unicode".
77
38 You could use rxvt's termcap entry with resonable results in many 78 You could use rxvt's termcap entry with resonable results in many
39 cases. You can also create a termcap entry by using terminfo's 79 cases. You can also create a termcap entry by using terminfo's
40 infocmp program like this: 80 infocmp program like this:
41 81
42 infocmp -C rxvt-unicode 82 infocmp -C rxvt-unicode
43 83
44 OR you could this termcap entry: 84 Or you could use this termcap entry, generated by the command above:
45 85
46 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 86 rxvt-unicode|rxvt-unicode terminal (X Window System):\
47 :am:bw:eo:km:mi:ms:xn:xo:\ 87 :am:bw:eo:km:mi:ms:xn:xo:\
48 :co#80:it#8:li#24:\ 88 :co#80:it#8:li#24:lm#0:\
49 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 89 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
50 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ 90 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
51 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ 91 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
52 :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ 92 :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
53 :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ 93 :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
54 :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ 94 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
95 :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
55 :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ 96 :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
56 :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ 97 :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
57 :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ 98 :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
58 :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ 99 :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
59 :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ 100 :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
60 :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ 101 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
61 :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ 102 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
62 :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ 103 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
63 :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 104 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
64 :vs=\E[?25h: 105 :vs=\E[?25h:
65 106
66 Why does "ls" no longer have coloured output? 107 Why does "ls" no longer have coloured output?
67 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 108 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
68 decide wether a terminal has colour, but uses it's own configuration 109 decide wether a terminal has colour, but uses it's own configuration
… …
87 furthermore fail to even install the "rxvt-unicode" terminfo file, 128 furthermore fail to even install the "rxvt-unicode" terminfo file,
88 so you will need to install it on your own (See the question When I 129 so you will need to install it on your own (See the question When I
89 log-in to another system it tells me about missing terminfo data? on 130 log-in to another system it tells me about missing terminfo data? on
90 how to do this). 131 how to do this).
91 132
133 My numerical keypad acts weird and generates differing output?
134 Some Debian GNUL/Linux users seem to have this problem, although no
135 specific details were reported so far. It is possible that this is
136 caused by the wrong "TERM" setting, although the details of wether
137 and how this can happen are unknown, as "TERM=rxvt" should offer a
138 compatible keymap. See the answer to the previous question, and
139 please report if that helped.
140
92 Rxvt-unicode does not seem to understand the selected encoding? 141 Rxvt-unicode does not seem to understand the selected encoding?
93 Unicode does not seem to work? 142 Unicode does not seem to work?
94 If you encounter strange problems like typing an accented character 143 If you encounter strange problems like typing an accented character
95 but getting two unrelated other characters or similar, or if program 144 but getting two unrelated other characters or similar, or if program
96 output is subtly garbled, then you should check your locale 145 output is subtly garbled, then you should check your locale
97 settings. 146 settings.
98 147
99 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 148 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the
100 programs. Often rxvt-unicode is started in the "C" locale, while the 149 programs. Often rxvt-unicode is started in the "C" locale, while the
101 login script running within the rxvt-unicode window changes the 150 login script running within the rxvt-unicode window changes the
102 locale to sth. else, e.h. "en_GB.UTF-8". Needless to say, this is 151 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
103 not going to work. 152 is not going to work.
104 153
105 The best thing is to fix your startup environment, as you will 154 The best thing is to fix your startup environment, as you will
106 likely run into other problems. If nothing works you can try this in 155 likely run into other problems. If nothing works you can try this in
107 your .profile. 156 your .profile.
108 157
109 printf '\e]701;%s\007' "$LC_CTYPE" 158 printf '\e]701;%s\007' "$LC_CTYPE"
110 159
111 If this doesn't work, then maybe you use a "LC_CTYPE" specification 160 If this doesn't work, then maybe you use a "LC_CTYPE" specification
112 not supported on your systems. Some systems have a "locale" command 161 not supported on your systems. Some systems have a "locale" command
113 which displays this. If it displays sth. like: 162 which displays this (also, "perl -e0" can be used to check locale
163 settings, as it will complain loudly if it cannot set the locale).
164 If it displays something like:
114 165
115 locale: Cannot set LC_CTYPE to default locale: ... 166 locale: Cannot set LC_CTYPE to default locale: ...
116 167
117 Then the locale you specified is not supported on your system. 168 Then the locale you specified is not supported on your system.
118 169
… …
126 Chances are that the font you (or the admin/package maintainer of 177 Chances are that the font you (or the admin/package maintainer of
127 your system/os) have specified does not cover all the characters you 178 your system/os) have specified does not cover all the characters you
128 want to display. 179 want to display.
129 180
130 rxvt-unicode makes a best-effort try at finding a replacement font. 181 rxvt-unicode makes a best-effort try at finding a replacement font.
131 Often the result is fine, but sometimes the chosen font looks bad. 182 Often the result is fine, but sometimes the chosen font looks
132 Many fonts have totally strange characters that don't resemble the 183 bad/ugly/wrong. Some fonts have totally strange characters that
133 correct glyph at all, and rxvt-unicode lacks the artificial 184 don't resemble the correct glyph at all, and rxvt-unicode lacks the
134 intelligence to detect that a specific glyph is wrong: it has to 185 artificial intelligence to detect that a specific glyph is wrong: it
135 believe the font that the characters it contains indeed look 186 has to believe the font that the characters it claims to contain
136 correct. 187 indeed look correct.
137 188
138 In that case, select a font of your taste and add it to the font 189 In that case, select a font of your taste and add it to the font
139 list, e.g.: 190 list, e.g.:
140 191
141 rxvt -fn basefont,font2,font3... 192 rxvt -fn basefont,font2,font3...
… …
144 font. If the base font does not contain the character, it will go to 195 font. If the base font does not contain the character, it will go to
145 the next font, and so on. Specifying your own fonts will also speed 196 the next font, and so on. Specifying your own fonts will also speed
146 up this search and use less resources within rxvt-unicode and the 197 up this search and use less resources within rxvt-unicode and the
147 X-server. 198 X-server.
148 199
149 The only limitation is that all the fonts must not be larger than 200 The only limitation is that none of the fonts may be larger than the
150 the base font, as the base font defines the principal cell size, 201 base font, as the base font defines the terminal character cell
151 which must be the same due to the way terminals work. 202 size, which must be the same due to the way terminals work.
152 203
153 Why do some chinese characters look so different than others? 204 Why do some chinese characters look so different than others?
154 This is because there is a difference between script and language -- 205 This is because there is a difference between script and language --
155 rxvt-unicode does not know which language the text that is output 206 rxvt-unicode does not know which language the text that is output
156 is, as it only knows the unicode character codes. If rxvt-unicode 207 is, as it only knows the unicode character codes. If rxvt-unicode
157 first sees a japanese character, it might choose a japanese font for 208 first sees a japanese/chinese character, it might choose a japanese
158 it. Subsequent japanese characters will take that font. Now, many 209 font for display. Subsequent japanese characters will use that font.
159 chinese characters aren't represented in japanese fonts, so when the 210 Now, many chinese characters aren't represented in japanese fonts,
160 first non-japanese character comes up, rxvt-unicode will look for a 211 so when the first non-japanese character comes up, rxvt-unicode will
161 chinese font -- unfortunately at this point, it will still use the 212 look for a chinese font -- unfortunately at this point, it will
162 japanese font for japanese characters that are also chinese. 213 still use the japanese font for chinese characters that are also in
214 the japanese font.
163 215
164 The workaround is easy: just tag a chinese font at the end of your 216 The workaround is easy: just tag a chinese font at the end of your
165 font list (see the previous question). The key is to view the font 217 font list (see the previous question). The key is to view the font
166 list as a preference list: If you expect more japanese, list a 218 list as a preference list: If you expect more japanese, list a
167 japanese font first. If you expect more chinese, put a chinese font 219 japanese font first. If you expect more chinese, put a chinese font
168 first. 220 first.
169 221
170 In the future it might be possible to switch preferences at runtime 222 In the future it might be possible to switch language preferences at
171 (the internal data structure has no problem with using different 223 runtime (the internal data structure has no problem with using
172 fonts for the same character at the same time, but no interface for 224 different fonts for the same character at the same time, but no
173 this has been designed yet). 225 interface for this has been designed yet).
226
227 Until then, you might get away with switching fonts at runtime (see
228 "Can I switch the fonts at runtime?" later in this document).
174 229
175 Why does rxvt-unicode sometimes leave pixel droppings? 230 Why does rxvt-unicode sometimes leave pixel droppings?
176 Most fonts were not designed for terminal use, which means that 231 Most fonts were not designed for terminal use, which means that
177 character size varies a lot. A font that is otherwise fine for 232 character size varies a lot. A font that is otherwise fine for
178 terminal use might contain some characters that are simply too wide. 233 terminal use might contain some characters that are simply too wide.
… …
212 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for 267 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for
213 other codes, too, such as "Ctrl-Shift-1-d" to type the default 268 other codes, too, such as "Ctrl-Shift-1-d" to type the default
214 telnet escape character and so on. 269 telnet escape character and so on.
215 270
216 How can I keep rxvt-unicode from using reverse video so much? 271 How can I keep rxvt-unicode from using reverse video so much?
217 First of all, make sure you are running with the right terminfo 272 First of all, make sure you are running with the right terminal
218 ("urxvt"), which will get rid of most of these effects. Then make 273 settings ("TERM=rxvt-unicode"), which will get rid of most of these
219 sure you have specified colours for italic and bold, as otherwise 274 effects. Then make sure you have specified colours for italic and
220 rxvt-unicode might use reverse video to simulate the effect: 275 bold, as otherwise rxvt-unicode might use reverse video to simulate
276 the effect:
221 277
222 URxvt*colorBD: white 278 URxvt.colorBD: white
223 URxvt*colorIT: green 279 URxvt.colorIT: green
224 280
225 Some programs assume totally weird colours (red instead of blue), how 281 Some programs assume totally weird colours (red instead of blue), how
226 can I fix that? 282 can I fix that?
227 For some unexplainable reason, some programs (i.e. irssi) assume a 283 For some unexplainable reason, some rare programs assume a very
228 very weird colour palette when confronted with a terminal with more 284 weird colour palette when confronted with a terminal with more than
229 than the standard 8 colours (rxvt-unicode supports 88). The right 285 the standard 8 colours (rxvt-unicode supports 88). The right fix is,
230 fix is, of course, to fix these programs not to assume non-ISO 286 of course, to fix these programs not to assume non-ISO colours
231 colours without very good reasons. 287 without very good reasons.
232 288
233 In the meantime, you can either edit your "urxvt" terminfo 289 In the meantime, you can either edit your "rxvt-unicode" terminfo
234 definition to only claim 8 colour support or use "TERM=rxvt", which 290 definition to only claim 8 colour support or use "TERM=rxvt", which
235 will fix colours but keep you from using other rxvt-unicode 291 will fix colours but keep you from using other rxvt-unicode
236 features. 292 features.
237 293
238 I am on FreeBSD and rxvt-unicode does not seem to work at all. 294 I am on FreeBSD and rxvt-unicode does not seem to work at all.
… …
241 it, wether it defines the symbol or not. "__STDC_ISO_10646__" 297 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
242 requires that wchar_t is represented as unicode. 298 requires that wchar_t is represented as unicode.
243 299
244 As you might have guessed, FreeBSD does neither define this symobl 300 As you might have guessed, FreeBSD does neither define this symobl
245 nor does it support it. Instead, it uses it's own internal 301 nor does it support it. Instead, it uses it's own internal
246 representation of wchar_t. This is, of course, completely legal. 302 representation of wchar_t. This is, of course, completely fine with
303 respect to standards.
247 304
305 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
306 and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
307
248 However, "__STDC_ISO_10646__" is the only sane way to support 308 "__STDC_ISO_10646__" is the only sane way to support multi-language
249 multi-language apps in an OS, as using a locale-dependent (and 309 apps in an OS, as using a locale-dependent (and non-standardized)
250 non-standardized) representation of wchar_t makes it impossible to 310 representation of wchar_t makes it impossible to convert between
251 convert between wchar_t (as used by X11 and your applications) and 311 wchar_t (as used by X11 and your applications) and any other
252 any other encoding without implementing OS-specific-wrappers for 312 encoding without implementing OS-specific-wrappers for each and
253 each and every locale. There simply are no APIs to convert wchar_t 313 every locale. There simply are no APIs to convert wchar_t into
254 into anything except the current locale encoding. 314 anything except the current locale encoding.
255 315
256 Some applications (such as the formidable mlterm) work around this 316 Some applications (such as the formidable mlterm) work around this
257 by carrying their own replacement functions for character set 317 by carrying their own replacement functions for character set
258 handling with them, and either implementing OS-dependent hacks or 318 handling with them, and either implementing OS-dependent hacks or
259 doing multiple conversions (which is slow and unreliable in case the 319 doing multiple conversions (which is slow and unreliable in case the
260 OS implements encodings slightly different than the terminal 320 OS implements encodings slightly different than the terminal
261 emulator). 321 emulator).
262 322
263 The rxvt-unicode author insists that the right way to fix this is in 323 The rxvt-unicode author insists that the right way to fix this is in
264 the system libraries once and for all, instead of forcing every app 324 the system libraries once and for all, instead of forcing every app
265 to carry complete replacements. 325 to carry complete replacements for them :)
266 326
267 How does rxvt-unicode determine the encoding to use? 327 How does rxvt-unicode determine the encoding to use?
268 Is there an option to switch encodings? 328 Is there an option to switch encodings?
269 Unlike some other terminals, rxvt-unicode has no encoding switch, 329 Unlike some other terminals, rxvt-unicode has no encoding switch,
270 and no specific "utf-8" mode, such as xterm. In fact, it doesn't 330 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
273 333
274 The reasons is that there exists a perfectly fine mechanism for 334 The reasons is that there exists a perfectly fine mechanism for
275 selecting the encoding, doing I/O and (most important) communicating 335 selecting the encoding, doing I/O and (most important) communicating
276 this to all applications so everybody agrees on character properties 336 this to all applications so everybody agrees on character properties
277 such as width and code number. This mechanism is the *locale*. 337 such as width and code number. This mechanism is the *locale*.
338 Applications not using that info will have problems (for example,
339 "xterm" gets the width of characters wrong as it uses it's own,
340 locale-independent table under all locales).
278 341
279 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 342 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
280 All programs doing the same (that is, most) will automatically agree 343 All programs doing the same (that is, most) will automatically agree
281 in the interpretation of characters. 344 in the interpretation of characters.
282 345
… …
290 "language_country.encoding", but other forms (i.e. "de" or "german") 353 "language_country.encoding", but other forms (i.e. "de" or "german")
291 are also common. 354 are also common.
292 355
293 Rxvt-unicode ignores all other locale categories, and except for the 356 Rxvt-unicode ignores all other locale categories, and except for the
294 encoding, ignores country or language-specific settings, i.e. 357 encoding, ignores country or language-specific settings, i.e.
295 "de_DE.UTF-8" and "ja_JP.UTF-8" are the same for rxvt-unicode. 358 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
359 rxvt-unicode.
296 360
297 If you want to use a specific encoding you have to make sure you 361 If you want to use a specific encoding you have to make sure you
298 start rxvt-unicode with the correct "LC_CTYPE" category. 362 start rxvt-unicode with the correct "LC_CTYPE" category.
299 363
300 Can I switch locales at runtime? 364 Can I switch locales at runtime?
301 Yes, using an escape sequence. Try sth. like this, which sets 365 Yes, using an escape sequence. Try something like this, which sets
302 rxvt-unicode's idea of "LC_CTYPE". 366 rxvt-unicode's idea of "LC_CTYPE".
303 367
304 printf '\e]701;%s\007' ja_JP.SJIS 368 printf '\e]701;%s\007' ja_JP.SJIS
305 369
306 See also the previous question. 370 See also the previous answer.
307 371
308 Sometimes this capability is rather handy when you want to work in 372 Sometimes this capability is rather handy when you want to work in
309 one locale (e.g. "de_DE.UTF-8") but some programs don't support 373 one locale (e.g. "de_DE.UTF-8") but some programs don't support it
310 UTF-8. For example, I use this script to start "xjdic", which first 374 (e.g. UTF-8). For example, I use this script to start "xjdic", which
311 switches to a locale supported by xjdic and back later: 375 first switches to a locale supported by xjdic and back later:
312 376
313 printf '\e]701;%s\007' ja_JP.SJIS 377 printf '\e]701;%s\007' ja_JP.SJIS
314 xjdic -js 378 xjdic -js
315 printf '\e]701;%s\007' de_DE.UTF-8 379 printf '\e]701;%s\007' de_DE.UTF-8
316 380
381 You can also use xterm's "luit" program, which usually works fine,
382 except for some locales where character width differs between
383 program- and rxvt-unicode-locales.
384
317 Can I switch the fonts at runtime? 385 Can I switch the fonts at runtime?
318 Yes, using an escape sequence. Try sth. like this, which has the 386 Yes, using an escape sequence. Try something like this, which has
319 same effect as using the "-fn" switch, and takes effect immediately: 387 the same effect as using the "-fn" switch, and takes effect
388 immediately:
320 389
321 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 390 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
322 391
323 This is useful if you e.g. work primarily with japanese (and prefer 392 This is useful if you e.g. work primarily with japanese (and prefer
324 a japanese font), but you have to switch to chinese temporarily, 393 a japanese font), but you have to switch to chinese temporarily,
… …
327 You can think of this as a kind of manual ISO-2022 switching. 396 You can think of this as a kind of manual ISO-2022 switching.
328 397
329 Why do italic characters look as if clipped? 398 Why do italic characters look as if clipped?
330 Many fonts have difficulties with italic characters and hinting. For 399 Many fonts have difficulties with italic characters and hinting. For
331 example, the otherwise very nicely hinted font "xft:Bitstream Vera 400 example, the otherwise very nicely hinted font "xft:Bitstream Vera
332 Sans Mono" completely fails in it's italic face. A workaround is to 401 Sans Mono" completely fails in it's italic face. A workaround might
333 enable freetype autohinting, i.e. like this: 402 be to enable freetype autohinting, i.e. like this:
334 403
335 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 404 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
336 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 405 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
337 406
338 My input method wants <some encoding> but I want UTF-8, what can I do? 407 My input method wants <some encoding> but I want UTF-8, what can I do?
339 You can specify separate locales for the input method and the rest 408 You can specify separate locales for the input method and the rest
340 of the terminal, using the resource "imlocale": 409 of the terminal, using the resource "imlocale":
341 410
… …
344 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 413 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and
345 still use your input method. Please note, however, that you will not 414 still use your input method. Please note, however, that you will not
346 be able to input characters outside "EUC-JP" in a normal way then, 415 be able to input characters outside "EUC-JP" in a normal way then,
347 as your input method limits you. 416 as your input method limits you.
348 417
418 Rxvt-unicode crashes when the X Input Method changes or exits.
419 Unfortunately, this is unavoidable, as the XIM protocol is racy by
420 design. Applications can avoid some crashes at the expense of memory
421 leaks, and Input Methods can avoid some crashes by careful ordering
422 at exit time. kinput2 (and derived input methods) generally
423 succeeds, while SCIM (or similar input methods) fails. In the end,
424 however, crashes cannot be completely avoided even if both sides
425 cooperate.
426
427 So the only workaround is not to kill your Input Method Servers.
428
349 Rxvt-unicode uses gobs of memory, how can I reduce that? 429 Rxvt-unicode uses gobs of memory, how can I reduce that?
350 Rxvt-unicode tries to obey the rule of not charging you for sth. you 430 Rxvt-unicode tries to obey the rule of not charging you for
351 don't use. One thing you should try is to configure out all settings 431 something you don't use. One thing you should try is to configure
352 that you don't need, for example, Xft support is a resource hog by 432 out all settings that you don't need, for example, Xft support is a
353 design, when used. Compiling it out ensures that no Xft font will be 433 resource hog by design, when used. Compiling it out ensures that no
354 loaded accidentally when rxvt-unicode tries to find a font for your 434 Xft font will be loaded accidentally when rxvt-unicode tries to find
355 characters. 435 a font for your characters.
356 436
357 Also, many people (me included) like large windows and even larger 437 Also, many people (me included) like large windows and even larger
358 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 438 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
359 use 6 bytes per screen cell. For a 160x?? window this amounts to 439 use 6 bytes per screen cell. For a 160x?? window this amounts to
360 almost a kilobyte per line. A scrollback buffer of 10000 lines will 440 almost a kilobyte per line. A scrollback buffer of 10000 lines will
… …
404 resources (or as long-options). 484 resources (or as long-options).
405 485
406 Here are values that are supposed to resemble a VGA screen, 486 Here are values that are supposed to resemble a VGA screen,
407 including the murky brown that passes for low-intensity yellow: 487 including the murky brown that passes for low-intensity yellow:
408 488
409 URxvt*color0: #000000 489 URxvt.color0: #000000
410 URxvt*color1: #A80000 490 URxvt.color1: #A80000
411 URxvt*color2: #00A800 491 URxvt.color2: #00A800
412 URxvt*color3: #A8A800 492 URxvt.color3: #A8A800
413 URxvt*color4: #0000A8 493 URxvt.color4: #0000A8
414 URxvt*color5: #A800A8 494 URxvt.color5: #A800A8
415 URxvt*color6: #00A8A8 495 URxvt.color6: #00A8A8
416 URxvt*color7: #A8A8A8 496 URxvt.color7: #A8A8A8
417 497
418 URxvt*color8: #000054 498 URxvt.color8: #000054
419 URxvt*color9: #FF0054 499 URxvt.color9: #FF0054
420 URxvt*color10: #00FF54 500 URxvt.color10: #00FF54
421 URxvt*color11: #FFFF54 501 URxvt.color11: #FFFF54
422 URxvt*color12: #0000FF 502 URxvt.color12: #0000FF
423 URxvt*color13: #FF00FF 503 URxvt.color13: #FF00FF
424 URxvt*color14: #00FFFF 504 URxvt.color14: #00FFFF
425 URxvt*color15: #FFFFFF 505 URxvt.color15: #FFFFFF
426 506
427 And here is a more complete set of non-standard colors described as 507 And here is a more complete set of non-standard colors described
428 "pretty girly": 508 (not by me) as "pretty girly".
429 509
430 URxvt.cursorColor: #dc74d1 510 URxvt.cursorColor: #dc74d1
431 URxvt.pointerColor: #dc74d1 511 URxvt.pointerColor: #dc74d1
432 URxvt.background: #0e0e0e 512 URxvt.background: #0e0e0e
433 URxvt.foreground: #4ad5e1 513 URxvt.foreground: #4ad5e1
… …
444 URxvt.color6: #73f7ff 524 URxvt.color6: #73f7ff
445 URxvt.color14: #73f7ff 525 URxvt.color14: #73f7ff
446 URxvt.color7: #e1dddd 526 URxvt.color7: #e1dddd
447 URxvt.color15: #e1dddd 527 URxvt.color15: #e1dddd
448 528
529 How can I start rxvtd in a race-free way?
530 Despite it's name, rxvtd is not a real daemon, but more like a
531 server that answers rxvtc's requests, so it doesn't background
532 itself.
533
534 To ensure rxvtd is listening on it's socket, you can use the
535 following method to wait for the startup message before continuing:
536
537 { rxvtd & } | read
538
449 What's with the strange Backspace/Delete key behaviour? 539 What's with the strange Backspace/Delete key behaviour?
450 Assuming that the physical Backspace key corresponds to the 540 Assuming that the physical Backspace key corresponds to the
451 BackSpace keysym (not likely for Linux ... see the following 541 BackSpace keysym (not likely for Linux ... see the following
452 question) there are two standard values that can be used for 542 question) there are two standard values that can be used for
453 Backspace: "^H" and "^?". 543 Backspace: "^H" and "^?".
… …
471 561
472 # use Backspace = ^? 562 # use Backspace = ^?
473 $ stty erase ^? 563 $ stty erase ^?
474 $ rxvt 564 $ rxvt
475 565
476 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 566 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
477 567
478 For an existing rxvt-unicode: 568 For an existing rxvt-unicode:
479 569
480 # use Backspace = ^H 570 # use Backspace = ^H
481 $ stty erase ^H 571 $ stty erase ^H
… …
490 value properly reflects that. 580 value properly reflects that.
491 581
492 The Delete key is a another casualty of the ill-defined Backspace 582 The Delete key is a another casualty of the ill-defined Backspace
493 problem. To avoid confusion between the Backspace and Delete keys, 583 problem. To avoid confusion between the Backspace and Delete keys,
494 the Delete key has been assigned an escape sequence to match the 584 the Delete key has been assigned an escape sequence to match the
495 vt100 for Execute (ESC[3~) and is in the supplied termcap/terminfo. 585 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
586 termcap/terminfo.
496 587
497 Some other Backspace problems: 588 Some other Backspace problems:
498 589
499 some editors use termcap/terminfo, some editors (vim I'm told) 590 some editors use termcap/terminfo, some editors (vim I'm told)
500 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 591 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
504 595
505 I don't like the key-bindings. How do I change them? 596 I don't like the key-bindings. How do I change them?
506 There are some compile-time selections available via configure. 597 There are some compile-time selections available via configure.
507 Unless you have run "configure" with the "--disable-resources" 598 Unless you have run "configure" with the "--disable-resources"
508 option you can use the `keysym' resource to alter the keystrings 599 option you can use the `keysym' resource to alter the keystrings
509 associated with keysym 0xFF00 - 0xFFFF (function, cursor keys, etc). 600 associated with keysyms.
510 601
511 Here's an example for a tn3270 session started using `rxvt -name 602 Here's an example for a URxvt session started using "rxvt -name
512 tn3270' 603 URxvt"
513 604
514 !# ----- special uses ------: 605 URxvt.keysym.Home: \033[1~
515 ! tn3270 login, remap function and arrow keys. 606 URxvt.keysym.End: \033[4~
516 tn3270*font: *clean-bold-*-*--15-* 607 URxvt.keysym.C-apostrophe: \033<C-'>
608 URxvt.keysym.C-slash: \033<C-/>
609 URxvt.keysym.C-semicolon: \033<C-;>
610 URxvt.keysym.C-grave: \033<C-`>
611 URxvt.keysym.C-comma: \033<C-,>
612 URxvt.keysym.C-period: \033<C-.>
613 URxvt.keysym.C-0x60: \033<C-`>
614 URxvt.keysym.C-Tab: \033<C-Tab>
615 URxvt.keysym.C-Return: \033<C-Return>
616 URxvt.keysym.S-Return: \033<S-Return>
617 URxvt.keysym.S-space: \033<S-Space>
618 URxvt.keysym.M-Up: \033<M-Up>
619 URxvt.keysym.M-Down: \033<M-Down>
620 URxvt.keysym.M-Left: \033<M-Left>
621 URxvt.keysym.M-Right: \033<M-Right>
622 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
623 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
624 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
517 625
518 ! keysym - used by rxvt only 626 See some more examples in the documentation for the keysym resource.
519 ! Delete - ^D
520 tn3270*keysym.0xFFFF: \004
521
522 ! Home - ^A
523 tn3270*keysym.0xFF50: \001
524 ! Left - ^B
525 tn3270*keysym.0xFF51: \002
526 ! Up - ^P
527 tn3270*keysym.0xFF52: \020
528 ! Right - ^F
529 tn3270*keysym.0xFF53: \006
530 ! Down - ^N
531 tn3270*keysym.0xFF54: \016
532 ! End - ^E
533 tn3270*keysym.0xFF57: \005
534
535 ! F1 - F12
536 tn3270*keysym.0xFFBE: \e1
537 tn3270*keysym.0xFFBF: \e2
538 tn3270*keysym.0xFFC0: \e3
539 tn3270*keysym.0xFFC1: \e4
540 tn3270*keysym.0xFFC2: \e5
541 tn3270*keysym.0xFFC3: \e6
542 tn3270*keysym.0xFFC4: \e7
543 tn3270*keysym.0xFFC5: \e8
544 tn3270*keysym.0xFFC6: \e9
545 tn3270*keysym.0xFFC7: \e0
546 tn3270*keysym.0xFFC8: \e-
547 tn3270*keysym.0xFFC9: \e=
548
549 ! map Prior/Next to F7/F8
550 tn3270*keysym.0xFF55: \e7
551 tn3270*keysym.0xFF56: \e8
552 627
553 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 628 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How
554 do I make use of them? For example, the Sun Keyboard type 4 has the 629 do I make use of them? For example, the Sun Keyboard type 4 has the
555 following mappings that rxvt-unicode doesn't recognize. 630 following mappings that rxvt-unicode doesn't recognize.
556 KP_Insert == Insert 631 KP_Insert == Insert
… …
562 637
563 Rather than have rxvt-unicode try to accommodate all the various 638 Rather than have rxvt-unicode try to accommodate all the various
564 possible keyboard mappings, it is better to use `xmodmap' to remap 639 possible keyboard mappings, it is better to use `xmodmap' to remap
565 the keys as required for your particular machine. 640 the keys as required for your particular machine.
566 641
567 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 642 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
568 need this to decide about setting colors etc. 643 I need this to decide about setting colors etc.
569 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 644 rxvt and rxvt-unicode always export the variable "COLORTERM", so you
570 can check and see if that is set. Note that several programs, JED, 645 can check and see if that is set. Note that several programs, JED,
571 slrn, Midnight Commander automatically check this variable to decide 646 slrn, Midnight Commander automatically check this variable to decide
572 whether or not to use color. 647 whether or not to use color.
573 648
… …
604 Before sending me mail, you could go to IRC: "irc.freenode.net", 679 Before sending me mail, you could go to IRC: "irc.freenode.net",
605 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might 680 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might
606 be interested in learning about new and exciting problems (but not 681 be interested in learning about new and exciting problems (but not
607 FAQs :). 682 FAQs :).
608 683
609SYNOPSIS 684RXVT TECHNICAL REFERENCE
610 # set a new font set
611 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
612
613 # change the locale and tell rxvt-unicode about it
614 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
615
616 # set window title
617 printf '\33]2;%s\007' "new window title"
618
619DESCRIPTION 685DESCRIPTION
620 The rest of this document describes various technical aspects of 686 The rest of this document describes various technical aspects of
621 rxvt-unicode. First the description of supported command sequences, 687 rxvt-unicode. First the description of supported command sequences,
622 followed by menu and pixmap support and last by a description of all 688 followed by menu and pixmap support and last by a description of all
623 features selectable at "configure" time. 689 features selectable at "configure" time.
624 690
625RXVT TECHNICAL REFERENCE
626Definitions 691Definitions
627 "c" The literal character c. 692 "c" The literal character c.
628 693
629 "C" A single (required) character. 694 "C" A single (required) character.
630 695
… …
715 "ESC O" 780 "ESC O"
716 Single Shift Select of G3 Character Set (SS3): affects next 781 Single Shift Select of G3 Character Set (SS3): affects next
717 character only *unimplemented* 782 character only *unimplemented*
718 783
719 "ESC Z" 784 "ESC Z"
720 Obsolete form of returns: "ESC[?1;2C" *rxvt-unicode compile-time 785 Obsolete form of returns: "ESC [ ? 1 ; 2 C" *rxvt-unicode
721 option* 786 compile-time option*
722 787
723 "ESC c" 788 "ESC c"
724 Full reset (RIS) 789 Full reset (RIS)
725 790
726 "ESC n" 791 "ESC n"
727 Invoke the G2 Character Set (LS2) 792 Invoke the G2 Character Set (LS2)
728 793
729 "ESC o" 794 "ESC o"
730 Invoke the G3 Character Set (LS3) 795 Invoke the G3 Character Set (LS3)
731 796
732 "ESC" ( C> 797 "ESC ( C"
733 Designate G0 Character Set (ISO 2022), see below for values of "C". 798 Designate G0 Character Set (ISO 2022), see below for values of "C".
734 799
735 "ESC" ) C> 800 "ESC ) C"
736 Designate G1 Character Set (ISO 2022), see below for values of "C". 801 Designate G1 Character Set (ISO 2022), see below for values of "C".
737 802
738 "ESC * C" 803 "ESC * C"
739 Designate G2 Character Set (ISO 2022), see below for values of "C". 804 Designate G2 Character Set (ISO 2022), see below for values of "C".
740 805
… …
833 "ESC [ Ps a" 898 "ESC [ Ps a"
834 See "ESC [ Ps C" 899 See "ESC [ Ps C"
835 900
836 "ESC [ Ps c" 901 "ESC [ Ps c"
837 Send Device Attributes (DA) "Ps = 0" (or omitted): request 902 Send Device Attributes (DA) "Ps = 0" (or omitted): request
838 attributes from terminal returns: "ESC[?1;2c" (``I am a VT100 with 903 attributes from terminal returns: "ESC [ ? 1 ; 2 c" (``I am a VT100
839 Advanced Video Option'') 904 with Advanced Video Option'')
840 905
841 "ESC [ Ps d" 906 "ESC [ Ps d"
842 Cursor to Line "Ps" (VPA) 907 Cursor to Line "Ps" (VPA)
843 908
844 "ESC [ Ps e" 909 "ESC [ Ps e"
… …
918 (CSR) 983 (CSR)
919 984
920 "ESC [ s" 985 "ESC [ s"
921 Save Cursor (SC) 986 Save Cursor (SC)
922 987
988 "ESC [ Ps;Pt t"
989 Window Operations
990
991 Ps = 1 Deiconify (map) window
992 Ps = 2 Iconify window
993 Ps = 3 ESC [ 3 ; X ; Y t Move window to (X|Y)
994 Ps = 4 ESC [ 4 ; H ; W t Resize to WxH pixels
995 Ps = 5 Raise window
996 Ps = 6 Lower window
997 Ps = 7 Refresh screen once
998 Ps = 8 ESC [ 8 ; R ; C t Resize to R rows and C columns
999 Ps = 11 Report window state (responds with Ps = 1 or Ps = 2)
1000 Ps = 13 Report window position (responds with Ps = 3)
1001 Ps = 14 Report window pixel size (responds with Ps = 4)
1002 Ps = 18 Report window text size (responds with Ps = 7)
1003 Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9
1004 Ps = 20 Reports icon label (ESC ] L NAME \234)
1005 Ps = 21 Reports window title (ESC ] l NAME \234)
1006 Ps = 24.. Set window height to Ps rows
1007
1008 "ESC [ u"
1009 Restore Cursor
1010
923 "ESC [ Ps x" 1011 "ESC [ Ps x"
924 Request Terminal Parameters (DECREQTPARM) 1012 Request Terminal Parameters (DECREQTPARM)
925
926 "ESC [ u"
927 Restore Cursor
928 1013
929 1014
930 1015
931DEC Private Modes 1016DEC Private Modes
932 "ESC [ ? Pm h" 1017 "ESC [ ? Pm h"
… …
1074 Ps = 13 Change colour of mouse foreground to Pt 1159 Ps = 13 Change colour of mouse foreground to Pt
1075 Ps = 17 Change colour of highlight characters to Pt 1160 Ps = 17 Change colour of highlight characters to Pt
1076 Ps = 18 Change colour of bold characters to Pt 1161 Ps = 18 Change colour of bold characters to Pt
1077 Ps = 19 Change colour of underlined characters to Pt 1162 Ps = 19 Change colour of underlined characters to Pt
1078 Ps = 20 Change default background to Pt 1163 Ps = 20 Change default background to Pt
1079 Ps = 39 Change default foreground colour to Pt rxvt compile-time option 1164 Ps = 39 Change default foreground colour to Pt.
1080 Ps = 46 Change Log File to Pt unimplemented 1165 Ps = 46 Change Log File to Pt unimplemented
1081 Ps = 49 Change default background colour to Pt rxvt compile-time option 1166 Ps = 49 Change default background colour to Pt.
1082 Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n 1167 Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n
1083 Ps = 55 Log all scrollback buffer and all of screen to Pt 1168 Ps = 55 Log all scrollback buffer and all of screen to Pt
1084 Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (rxvt extension) 1169 Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
1085 Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) 1170 Ps = 703 Menubar command Pt (Compile menubar).
1086 Ps = 704 Change colour of italic characters to Pt 1171 Ps = 704 Change colour of italic characters to Pt
1087 Ps = 705 Change background pixmap tint colour to Pt 1172 Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1088 Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1173 Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
1089 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. 1174 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
1090 Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. 1175 Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1091 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. 1176 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1177 Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1178 Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1092 1179
1093 1180
1094 1181
1095menuBar 1182menuBar
1096 The exact syntax used is *almost* solidified. In the menus, DON'T try to 1183 The exact syntax used is *almost* solidified. In the menus, DON'T try to
… …
1133 [menu] 1220 [menu]
1134 access the current menuBar for alteration 1221 access the current menuBar for alteration
1135 1222
1136 [title:+*string*] 1223 [title:+*string*]
1137 set the current menuBar's title to *string*, which may contain the 1224 set the current menuBar's title to *string*, which may contain the
1138 following format specifiers: %% : literal % character %n : rxvt name 1225 following format specifiers:
1139 (as per the -name command-line option) %v : rxvt version 1226
1227 B<%n> rxvt name (as per the B<-name> command-line option)
1228 B<%v> rxvt version
1229 B<%%> literal B<%> character
1140 1230
1141 [done] 1231 [done]
1142 set menuBar access as readonly. End-of-file tag for [read:+*file*] 1232 set menuBar access as readonly. End-of-file tag for [read:+*file*]
1143 operations. 1233 operations.
1144 1234
… …
1248 1338
1249 As a convenience for the many Emacs-type editors, *action* may start 1339 As a convenience for the many Emacs-type editors, *action* may start
1250 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if 1340 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if
1251 missed from M-x commands. 1341 missed from M-x commands.
1252 1342
1253 As a convenience for issuing XTerm ESC] sequences from a menubar (or 1343 As a convenience for issuing XTerm ESC ] sequences from a menubar (or
1254 quick arrow), a BEL (^G) will be appended if needed. 1344 quick arrow), a BEL (^G) will be appended if needed.
1255 1345
1256 For example, 1346 For example,
1257 M-xapropos is equivalent to \Exapropos\r 1347 M-xapropos is equivalent to \Exapropos\r
1258 1348
… …
1580 --enable-font-styles 1670 --enable-font-styles
1581 Add support for bold, *italic* and *bold italic* font styles. The 1671 Add support for bold, *italic* and *bold italic* font styles. The
1582 fonts can be set manually or automatically. 1672 fonts can be set manually or automatically.
1583 1673
1584 --with-codesets=NAME,... 1674 --with-codesets=NAME,...
1585 Compile in support for additional codeset (encoding) groups (eu, vn 1675 Compile in support for additional codeset (encoding) groups ("eu",
1586 are always compiled in, which includes most 8-bit character sets). 1676 "vn" are always compiled in, which includes most 8-bit character
1587 These codeset tables are currently only used for driving X11 core 1677 sets). These codeset tables are used for driving X11 core fonts,
1588 fonts, they are not required for Xft fonts. Compiling them in will 1678 they are not required for Xft fonts, although having them compiled
1589 make your binary bigger (together about 700kB), but it doesn't 1679 in lets rxvt-unicode choose replacement fonts more intelligently.
1590 increase memory usage unless you use an X11 font requiring one of 1680 Compiling them in will make your binary bigger (all of together cost
1591 these encodings. 1681 about 700kB), but it doesn't increase memory usage unless you use a
1682 font requiring one of these encodings.
1592 1683
1593 all all available codeset groups 1684 all all available codeset groups
1594 zh common chinese encodings 1685 zh common chinese encodings
1595 zh_ext rarely used but very big chinese encodigs 1686 zh_ext rarely used but very big chinese encodigs
1596 jp common japanese encodings 1687 jp common japanese encodings
… …
1620 accents are encoded as seperate unicode characters. This is done by 1711 accents are encoded as seperate unicode characters. This is done by
1621 using precomposited characters when available or creating new 1712 using precomposited characters when available or creating new
1622 pseudo-characters when no precomposed form exists. 1713 pseudo-characters when no precomposed form exists.
1623 1714
1624 Without --enable-unicode3, the number of additional precomposed 1715 Without --enable-unicode3, the number of additional precomposed
1625 characters is rather limited (2048, if this is full, rxvt will use 1716 characters is rather limited (2048, if this is full, rxvt-unicode
1626 the private use area, extending the number of combinations to 8448). 1717 will use the private use area, extending the number of combinations
1627 With --enable-unicode3, no practical limit exists. This will also 1718 to 8448). With --enable-unicode3, no practical limit exists.
1628 enable storage of characters >65535. 1719
1720 This option will also enable storage (but not display) of characters
1721 beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1629 1722
1630 The combining table also contains entries for arabic presentation 1723 The combining table also contains entries for arabic presentation
1631 forms, but these are not currently used. Bug me if you want these to 1724 forms, but these are not currently used. Bug me if you want these to
1632 be used. 1725 be used (and tell me how these are to be used...).
1633 1726
1634 --enable-fallback(=CLASS) 1727 --enable-fallback(=CLASS)
1635 When reading resource settings, also read settings for class CLASS 1728 When reading resource settings, also read settings for class CLASS
1636 (default: Rxvt). To disable resource fallback use 1729 (default: Rxvt). To disable resource fallback use
1637 --disable-fallback. 1730 --disable-fallback.
… …
1711 1804
1712 --enable-xgetdefault 1805 --enable-xgetdefault
1713 Make resources checking via XGetDefault() instead of our small 1806 Make resources checking via XGetDefault() instead of our small
1714 version which only checks ~/.Xdefaults, or if that doesn't exist 1807 version which only checks ~/.Xdefaults, or if that doesn't exist
1715 then ~/.Xresources. 1808 then ~/.Xresources.
1809
1810 Please note that nowadays, things like XIM will automatically pull
1811 in and use the full X resource manager, so the overhead of using it
1812 might be very small, if nonexistant.
1716 1813
1717 --enable-strings 1814 --enable-strings
1718 Add support for our possibly faster memset() function and other 1815 Add support for our possibly faster memset() function and other
1719 various routines, overriding your system's versions which may have 1816 various routines, overriding your system's versions which may have
1720 been hand-crafted in assembly or may require extra libraries to link 1817 been hand-crafted in assembly or may require extra libraries to link
… …
1727 --enable-frills 1824 --enable-frills
1728 Add support for many small features that are not essential but nice 1825 Add support for many small features that are not essential but nice
1729 to have. Normally you want this, but for very small binaries you may 1826 to have. Normally you want this, but for very small binaries you may
1730 want to disable this. 1827 want to disable this.
1731 1828
1829 A non-exhaustive list of features enabled by "--enable-frills"
1830 (possibly in combination with other switches) is:
1831
1832 MWM-hints
1833 EWMH-hints (pid, utf8 names) and protocols (ping)
1834 seperate underline colour
1835 settable border widths and borderless switch
1836 settable extra linespacing
1837 iso-14755-2 and -3, and visual feedback
1838 backindex and forwardindex escape sequence
1839 window op and some xterm/OSC escape sequences
1840 tripleclickwords
1841 settable insecure mode
1842 keysym remapping support
1843 cursor blinking and underline cursor
1844 -embed and -pty-fd options
1845
1732 --enable-iso14755 1846 --enable-iso14755
1733 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). 1847 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
1734 Basic support (section 5.1) is enabled by "--enable-frills", while 1848 Basic support (section 5.1) is enabled by "--enable-frills", while
1735 support for 5.2, 5.3 and 5.4 is enabled with this switch. 1849 support for 5.2, 5.3 and 5.4 is enabled with this switch.
1736 1850
… …
1765 --enable-smart-resize 1879 --enable-smart-resize
1766 Add smart growth/shrink behaviour when changing font size via from 1880 Add smart growth/shrink behaviour when changing font size via from
1767 hot keys. This should keep in a fixed position the rxvt corner which 1881 hot keys. This should keep in a fixed position the rxvt corner which
1768 is closest to a corner of the screen. 1882 is closest to a corner of the screen.
1769 1883
1770 --enable-cursor-blink
1771 Add support for a blinking cursor.
1772
1773 --enable-pointer-blank 1884 --enable-pointer-blank
1774 Add support to have the pointer disappear when typing or inactive. 1885 Add support to have the pointer disappear when typing or inactive.
1775 1886
1776 --with-name=NAME 1887 --with-name=NAME
1777 Set the basename for the installed binaries (default: urxvt, 1888 Set the basename for the installed binaries (default: "urxvt",
1778 resulting in urxvt, urxvtd etc.). Specify --with-name=rxvt to 1889 resulting in "urxvt", "urxvtd" etc.). Specify "--with-name=rxvt" to
1779 replace rxvt. 1890 replace with "rxvt".
1780 1891
1781 --with-term=NAME 1892 --with-term=NAME
1782 Change the environmental variable for the terminal to NAME (default 1893 Change the environmental variable for the terminal to NAME (default
1783 "rxvt") 1894 "rxvt-unicode")
1784 1895
1785 --with-terminfo=PATH 1896 --with-terminfo=PATH
1786 Change the environmental variable for the path to the terminfo tree 1897 Change the environmental variable for the path to the terminfo tree
1787 to PATH. 1898 to PATH.
1788 1899

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines