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.3 by root, Mon Jan 17 01:44:51 2005 UTC vs.
Revision 1.21 by root, Wed Jul 13 02:53:54 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 in sarge contains large
29 patches that considerably change the behaviour of rxvt-unicode.
30 Before reporting a bug to the original rxvt-unicode author please
31 download 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 "tic" outputs some error when compiling the terminfo entry.
72 Most likely it's the empty definition for "enacs=". Just replace it
73 by "enacs=\E[0@" and try again.
74
75 "bash"'s readline does not work correctly under rxvt.
37 I need a termcap file entry. 76 I need a termcap file entry.
77 One reason you might want this is that some distributions or
78 operating systems still compile some programs using the
79 long-obsoleted termcap library (Fedora Core's bash is one example)
80 and rely on a termcap entry for "rxvt-unicode".
81
38 You could use rxvt's termcap entry with resonable results in many 82 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 83 cases. You can also create a termcap entry by using terminfo's
40 infocmp program like this: 84 infocmp program like this:
41 85
42 infocmp -C rxvt-unicode 86 infocmp -C rxvt-unicode
43 87
44 OR you could this termcap entry: 88 Or you could use this termcap entry, generated by the command above:
45 89
46 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 90 rxvt-unicode|rxvt-unicode terminal (X Window System):\
47 :am:bw:eo:km:mi:ms:xn:xo:\ 91 :am:bw:eo:km:mi:ms:xn:xo:\
48 :co#80:it#8:li#24:\ 92 :co#80:it#8:li#24:lm#0:\
49 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 93 :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:\ 94 :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:\ 95 :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:\ 96 :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:\ 97 :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[@:\ 98 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
99 :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:\ 100 :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~:\ 101 :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~:\ 102 :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:\ 103 :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=:\ 104 :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:\ 105 :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:\ 106 :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:\ 107 :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:\ 108 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
64 :vs=\E[?25h: 109 :vs=\E[?25h:
65 110
66 Why does "ls" no longer have coloured output? 111 Why does "ls" no longer have coloured output?
67 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 112 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 113 decide wether a terminal has colour, but uses it's own configuration
… …
87 furthermore fail to even install the "rxvt-unicode" terminfo file, 132 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 133 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 134 log-in to another system it tells me about missing terminfo data? on
90 how to do this). 135 how to do this).
91 136
137 My numerical keypad acts weird and generates differing output?
138 Some Debian GNUL/Linux users seem to have this problem, although no
139 specific details were reported so far. It is possible that this is
140 caused by the wrong "TERM" setting, although the details of wether
141 and how this can happen are unknown, as "TERM=rxvt" should offer a
142 compatible keymap. See the answer to the previous question, and
143 please report if that helped.
144
92 Rxvt-unicode does not seem to understand the selected encoding? 145 Rxvt-unicode does not seem to understand the selected encoding?
93 Unicode does not seem to work? 146 Unicode does not seem to work?
94 If you encounter strange problems like typing an accented character 147 If you encounter strange problems like typing an accented character
95 but getting two unrelated other characters or similar, or if program 148 but getting two unrelated other characters or similar, or if program
96 output is subtly garbled, then you should check your locale 149 output is subtly garbled, then you should check your locale
97 settings. 150 settings.
98 151
99 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 152 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 153 programs. Often rxvt-unicode is started in the "C" locale, while the
101 login script running within the rxvt-unicode window changes the 154 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 155 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
103 not going to work. 156 is not going to work.
104 157
105 The best thing is to fix your startup environment, as you will 158 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 159 likely run into other problems. If nothing works you can try this in
107 your .profile. 160 your .profile.
108 161
109 printf '\e]701;%s\007' "$LC_CTYPE" 162 printf '\e]701;%s\007' "$LC_CTYPE"
110 163
111 If this doesn't work, then maybe you use a "LC_CTYPE" specification 164 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 165 not supported on your systems. Some systems have a "locale" command
113 which displays this. If it displays sth. like: 166 which displays this (also, "perl -e0" can be used to check locale
167 settings, as it will complain loudly if it cannot set the locale).
168 If it displays something like:
114 169
115 locale: Cannot set LC_CTYPE to default locale: ... 170 locale: Cannot set LC_CTYPE to default locale: ...
116 171
117 Then the locale you specified is not supported on your system. 172 Then the locale you specified is not supported on your system.
118 173
… …
126 Chances are that the font you (or the admin/package maintainer of 181 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 182 your system/os) have specified does not cover all the characters you
128 want to display. 183 want to display.
129 184
130 rxvt-unicode makes a best-effort try at finding a replacement font. 185 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. 186 Often the result is fine, but sometimes the chosen font looks
132 Many fonts have totally strange characters that don't resemble the 187 bad/ugly/wrong. Some fonts have totally strange characters that
133 correct glyph at all, and rxvt-unicode lacks the artificial 188 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 189 artificial intelligence to detect that a specific glyph is wrong: it
135 believe the font that the characters it contains indeed look 190 has to believe the font that the characters it claims to contain
136 correct. 191 indeed look correct.
137 192
138 In that case, select a font of your taste and add it to the font 193 In that case, select a font of your taste and add it to the font
139 list, e.g.: 194 list, e.g.:
140 195
141 rxvt -fn basefont,font2,font3... 196 rxvt -fn basefont,font2,font3...
… …
144 font. If the base font does not contain the character, it will go to 199 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 200 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 201 up this search and use less resources within rxvt-unicode and the
147 X-server. 202 X-server.
148 203
149 The only limitation is that all the fonts must not be larger than 204 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, 205 base font, as the base font defines the terminal character cell
151 which must be the same due to the way terminals work. 206 size, which must be the same due to the way terminals work.
152 207
153 Why do some chinese characters look so different than others? 208 Why do some chinese characters look so different than others?
154 This is because there is a difference between script and language -- 209 This is because there is a difference between script and language --
155 rxvt-unicode does not know which language the text that is output 210 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 211 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 212 first sees a japanese/chinese character, it might choose a japanese
158 it. Subsequent japanese characters will take that font. Now, many 213 font for display. Subsequent japanese characters will use that font.
159 chinese characters aren't represented in japanese fonts, so when the 214 Now, many chinese characters aren't represented in japanese fonts,
160 first non-japanese character comes up, rxvt-unicode will look for a 215 so when the first non-japanese character comes up, rxvt-unicode will
161 chinese font -- unfortunately at this point, it will still use the 216 look for a chinese font -- unfortunately at this point, it will
162 japanese font for japanese characters that are also chinese. 217 still use the japanese font for chinese characters that are also in
218 the japanese font.
163 219
164 The workaround is easy: just tag a chinese font at the end of your 220 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 221 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 222 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 223 japanese font first. If you expect more chinese, put a chinese font
168 first. 224 first.
169 225
170 In the future it might be possible to switch preferences at runtime 226 In the future it might be possible to switch language preferences at
171 (the internal data structure has no problem with using different 227 runtime (the internal data structure has no problem with using
172 fonts for the same character at the same time, but no interface for 228 different fonts for the same character at the same time, but no
173 this has been designed yet). 229 interface for this has been designed yet).
230
231 Until then, you might get away with switching fonts at runtime (see
232 "Can I switch the fonts at runtime?" later in this document).
174 233
175 Why does rxvt-unicode sometimes leave pixel droppings? 234 Why does rxvt-unicode sometimes leave pixel droppings?
176 Most fonts were not designed for terminal use, which means that 235 Most fonts were not designed for terminal use, which means that
177 character size varies a lot. A font that is otherwise fine for 236 character size varies a lot. A font that is otherwise fine for
178 terminal use might contain some characters that are simply too wide. 237 terminal use might contain some characters that are simply too wide.
… …
192 that doesn't work, you might be forced to use a different font. 251 that doesn't work, you might be forced to use a different font.
193 252
194 All of this is not a problem when using X11 core fonts, as their 253 All of this is not a problem when using X11 core fonts, as their
195 bounding box data is correct. 254 bounding box data is correct.
196 255
256 On Solaris 9, many line-drawing characters are too wide.
257 Seems to be a known bug, read
258 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
259 following ugly workaround to get non-double-wide-characters working:
260
261 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
262
197 My Compose (Multi_key) key is no longer working. 263 My Compose (Multi_key) key is no longer working.
198 The most common causes for this are that either your locale is not 264 The most common causes for this are that either your locale is not
199 set correctly, or you specified a preeditStyle that is not supported 265 set correctly, or you specified a preeditStyle that is not supported
200 by your input method. For example, if you specified OverTheSpot and 266 by your input method. For example, if you specified OverTheSpot and
201 your input method (e.g. the default input method handling Compose 267 your input method (e.g. the default input method handling Compose
… …
212 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for 278 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 279 other codes, too, such as "Ctrl-Shift-1-d" to type the default
214 telnet escape character and so on. 280 telnet escape character and so on.
215 281
216 How can I keep rxvt-unicode from using reverse video so much? 282 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 283 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 284 settings ("TERM=rxvt-unicode"), which will get rid of most of these
219 sure you have specified colours for italic and bold, as otherwise 285 effects. Then make sure you have specified colours for italic and
220 rxvt-unicode might use reverse video to simulate the effect: 286 bold, as otherwise rxvt-unicode might use reverse video to simulate
287 the effect:
221 288
222 URxvt*colorBD: white 289 URxvt.colorBD: white
223 URxvt*colorIT: green 290 URxvt.colorIT: green
224 291
225 Some programs assume totally weird colours (red instead of blue), how 292 Some programs assume totally weird colours (red instead of blue), how
226 can I fix that? 293 can I fix that?
227 For some unexplainable reason, some programs (i.e. irssi) assume a 294 For some unexplainable reason, some rare programs assume a very
228 very weird colour palette when confronted with a terminal with more 295 weird colour palette when confronted with a terminal with more than
229 than the standard 8 colours (rxvt-unicode supports 88). The right 296 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 297 of course, to fix these programs not to assume non-ISO colours
231 colours without very good reasons. 298 without very good reasons.
232 299
233 In the meantime, you can either edit your "urxvt" terminfo 300 In the meantime, you can either edit your "rxvt-unicode" terminfo
234 definition to only claim 8 colour support or use "TERM=rxvt", which 301 definition to only claim 8 colour support or use "TERM=rxvt", which
235 will fix colours but keep you from using other rxvt-unicode 302 will fix colours but keep you from using other rxvt-unicode
236 features. 303 features.
237 304
238 I am on FreeBSD and rxvt-unicode does not seem to work at all. 305 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__" 308 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
242 requires that wchar_t is represented as unicode. 309 requires that wchar_t is represented as unicode.
243 310
244 As you might have guessed, FreeBSD does neither define this symobl 311 As you might have guessed, FreeBSD does neither define this symobl
245 nor does it support it. Instead, it uses it's own internal 312 nor does it support it. Instead, it uses it's own internal
246 representation of wchar_t. This is, of course, completely legal. 313 representation of wchar_t. This is, of course, completely fine with
314 respect to standards.
247 315
316 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
317 and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
318
248 However, "__STDC_ISO_10646__" is the only sane way to support 319 "__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 320 apps in an OS, as using a locale-dependent (and non-standardized)
250 non-standardized) representation of wchar_t makes it impossible to 321 representation of wchar_t makes it impossible to convert between
251 convert between wchar_t (as used by X11 and your applications) and 322 wchar_t (as used by X11 and your applications) and any other
252 any other encoding without implementing OS-specific-wrappers for 323 encoding without implementing OS-specific-wrappers for each and
253 each and every locale. There simply are no APIs to convert wchar_t 324 every locale. There simply are no APIs to convert wchar_t into
254 into anything except the current locale encoding. 325 anything except the current locale encoding.
255 326
256 Some applications (such as the formidable mlterm) work around this 327 Some applications (such as the formidable mlterm) work around this
257 by carrying their own replacement functions for character set 328 by carrying their own replacement functions for character set
258 handling with them, and either implementing OS-dependent hacks or 329 handling with them, and either implementing OS-dependent hacks or
259 doing multiple conversions (which is slow and unreliable in case the 330 doing multiple conversions (which is slow and unreliable in case the
260 OS implements encodings slightly different than the terminal 331 OS implements encodings slightly different than the terminal
261 emulator). 332 emulator).
262 333
263 The rxvt-unicode author insists that the right way to fix this is in 334 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 335 the system libraries once and for all, instead of forcing every app
265 to carry complete replacements. 336 to carry complete replacements for them :)
337
338 I use Solaris 9 and it doesn't compile/work/etc.
339 Try the diff in doc/solaris9.patch as a base. It fixes the worst
340 problems with "wcwidth" and a compile problem.
341
342 How can I use rxvt-unicode under cygwin?
343 rxvt-unicode should compile and run out of the box on cygwin, using
344 the X11 libraries that come with cygwin. libW11 emulation is no
345 longer supported (and makes no sense, either, as it only supported a
346 single font). I recommend starting the X-server in "-multiwindow" or
347 "-rootless" mode instead, which will result in similar look&feel as
348 the old libW11 emulation.
349
350 At the time of this writing, cygwin didn't seem to support any
351 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
352 likely limited to 8-bit encodings.
266 353
267 How does rxvt-unicode determine the encoding to use? 354 How does rxvt-unicode determine the encoding to use?
268 Is there an option to switch encodings? 355 Is there an option to switch encodings?
269 Unlike some other terminals, rxvt-unicode has no encoding switch, 356 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 357 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
273 360
274 The reasons is that there exists a perfectly fine mechanism for 361 The reasons is that there exists a perfectly fine mechanism for
275 selecting the encoding, doing I/O and (most important) communicating 362 selecting the encoding, doing I/O and (most important) communicating
276 this to all applications so everybody agrees on character properties 363 this to all applications so everybody agrees on character properties
277 such as width and code number. This mechanism is the *locale*. 364 such as width and code number. This mechanism is the *locale*.
365 Applications not using that info will have problems (for example,
366 "xterm" gets the width of characters wrong as it uses it's own,
367 locale-independent table under all locales).
278 368
279 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 369 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
280 All programs doing the same (that is, most) will automatically agree 370 All programs doing the same (that is, most) will automatically agree
281 in the interpretation of characters. 371 in the interpretation of characters.
282 372
… …
290 "language_country.encoding", but other forms (i.e. "de" or "german") 380 "language_country.encoding", but other forms (i.e. "de" or "german")
291 are also common. 381 are also common.
292 382
293 Rxvt-unicode ignores all other locale categories, and except for the 383 Rxvt-unicode ignores all other locale categories, and except for the
294 encoding, ignores country or language-specific settings, i.e. 384 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. 385 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
386 rxvt-unicode.
296 387
297 If you want to use a specific encoding you have to make sure you 388 If you want to use a specific encoding you have to make sure you
298 start rxvt-unicode with the correct "LC_CTYPE" category. 389 start rxvt-unicode with the correct "LC_CTYPE" category.
299 390
300 Can I switch locales at runtime? 391 Can I switch locales at runtime?
301 Yes, using an escape sequence. Try sth. like this, which sets 392 Yes, using an escape sequence. Try something like this, which sets
302 rxvt-unicode's idea of "LC_CTYPE". 393 rxvt-unicode's idea of "LC_CTYPE".
303 394
304 printf '\e]701;%s\007' ja_JP.SJIS 395 printf '\e]701;%s\007' ja_JP.SJIS
305 396
306 See also the previous question. 397 See also the previous answer.
307 398
308 Sometimes this capability is rather handy when you want to work in 399 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 400 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 401 (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: 402 first switches to a locale supported by xjdic and back later:
312 403
313 printf '\e]701;%s\007' ja_JP.SJIS 404 printf '\e]701;%s\007' ja_JP.SJIS
314 xjdic -js 405 xjdic -js
315 printf '\e]701;%s\007' de_DE.UTF-8 406 printf '\e]701;%s\007' de_DE.UTF-8
316 407
408 You can also use xterm's "luit" program, which usually works fine,
409 except for some locales where character width differs between
410 program- and rxvt-unicode-locales.
411
317 Can I switch the fonts at runtime? 412 Can I switch the fonts at runtime?
318 Yes, using an escape sequence. Try sth. like this, which has the 413 Yes, using an escape sequence. Try something like this, which has
319 same effect as using the "-fn" switch, and takes effect immediately: 414 the same effect as using the "-fn" switch, and takes effect
415 immediately:
320 416
321 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 417 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
322 418
323 This is useful if you e.g. work primarily with japanese (and prefer 419 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, 420 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. 423 You can think of this as a kind of manual ISO-2022 switching.
328 424
329 Why do italic characters look as if clipped? 425 Why do italic characters look as if clipped?
330 Many fonts have difficulties with italic characters and hinting. For 426 Many fonts have difficulties with italic characters and hinting. For
331 example, the otherwise very nicely hinted font "xft:Bitstream Vera 427 example, the otherwise very nicely hinted font "xft:Bitstream Vera
332 Sans Mono" completely fails in it's italic face. A workaround is to 428 Sans Mono" completely fails in it's italic face. A workaround might
333 enable freetype autohinting, i.e. like this: 429 be to enable freetype autohinting, i.e. like this:
334 430
335 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 431 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
336 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 432 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
337 433
338 My input method wants <some encoding> but I want UTF-8, what can I do? 434 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 435 You can specify separate locales for the input method and the rest
340 of the terminal, using the resource "imlocale": 436 of the terminal, using the resource "imlocale":
341 437
… …
344 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 440 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 441 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, 442 be able to input characters outside "EUC-JP" in a normal way then,
347 as your input method limits you. 443 as your input method limits you.
348 444
445 Rxvt-unicode crashes when the X Input Method changes or exits.
446 Unfortunately, this is unavoidable, as the XIM protocol is racy by
447 design. Applications can avoid some crashes at the expense of memory
448 leaks, and Input Methods can avoid some crashes by careful ordering
449 at exit time. kinput2 (and derived input methods) generally
450 succeeds, while SCIM (or similar input methods) fails. In the end,
451 however, crashes cannot be completely avoided even if both sides
452 cooperate.
453
454 So the only workaround is not to kill your Input Method Servers.
455
349 Rxvt-unicode uses gobs of memory, how can I reduce that? 456 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 457 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 458 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 459 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 460 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 461 Xft font will be loaded accidentally when rxvt-unicode tries to find
355 characters. 462 a font for your characters.
356 463
357 Also, many people (me included) like large windows and even larger 464 Also, many people (me included) like large windows and even larger
358 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 465 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
359 use 6 bytes per screen cell. For a 160x?? window this amounts to 466 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 467 almost a kilobyte per line. A scrollback buffer of 10000 lines will
… …
404 resources (or as long-options). 511 resources (or as long-options).
405 512
406 Here are values that are supposed to resemble a VGA screen, 513 Here are values that are supposed to resemble a VGA screen,
407 including the murky brown that passes for low-intensity yellow: 514 including the murky brown that passes for low-intensity yellow:
408 515
409 URxvt*color0: #000000 516 URxvt.color0: #000000
410 URxvt*color1: #A80000 517 URxvt.color1: #A80000
411 URxvt*color2: #00A800 518 URxvt.color2: #00A800
412 URxvt*color3: #A8A800 519 URxvt.color3: #A8A800
413 URxvt*color4: #0000A8 520 URxvt.color4: #0000A8
414 URxvt*color5: #A800A8 521 URxvt.color5: #A800A8
415 URxvt*color6: #00A8A8 522 URxvt.color6: #00A8A8
416 URxvt*color7: #A8A8A8 523 URxvt.color7: #A8A8A8
417 524
418 URxvt*color8: #000054 525 URxvt.color8: #000054
419 URxvt*color9: #FF0054 526 URxvt.color9: #FF0054
420 URxvt*color10: #00FF54 527 URxvt.color10: #00FF54
421 URxvt*color11: #FFFF54 528 URxvt.color11: #FFFF54
422 URxvt*color12: #0000FF 529 URxvt.color12: #0000FF
423 URxvt*color13: #FF00FF 530 URxvt.color13: #FF00FF
424 URxvt*color14: #00FFFF 531 URxvt.color14: #00FFFF
425 URxvt*color15: #FFFFFF 532 URxvt.color15: #FFFFFF
426 533
427 And here is a more complete set of non-standard colors described as 534 And here is a more complete set of non-standard colors described
428 "pretty girly": 535 (not by me) as "pretty girly".
429 536
430 URxvt.cursorColor: #dc74d1 537 URxvt.cursorColor: #dc74d1
431 URxvt.pointerColor: #dc74d1 538 URxvt.pointerColor: #dc74d1
432 URxvt.background: #0e0e0e 539 URxvt.background: #0e0e0e
433 URxvt.foreground: #4ad5e1 540 URxvt.foreground: #4ad5e1
… …
444 URxvt.color6: #73f7ff 551 URxvt.color6: #73f7ff
445 URxvt.color14: #73f7ff 552 URxvt.color14: #73f7ff
446 URxvt.color7: #e1dddd 553 URxvt.color7: #e1dddd
447 URxvt.color15: #e1dddd 554 URxvt.color15: #e1dddd
448 555
556 How can I start rxvtd in a race-free way?
557 Despite it's name, rxvtd is not a real daemon, but more like a
558 server that answers rxvtc's requests, so it doesn't background
559 itself.
560
561 To ensure rxvtd is listening on it's socket, you can use the
562 following method to wait for the startup message before continuing:
563
564 { rxvtd & } | read
565
449 What's with the strange Backspace/Delete key behaviour? 566 What's with the strange Backspace/Delete key behaviour?
450 Assuming that the physical Backspace key corresponds to the 567 Assuming that the physical Backspace key corresponds to the
451 BackSpace keysym (not likely for Linux ... see the following 568 BackSpace keysym (not likely for Linux ... see the following
452 question) there are two standard values that can be used for 569 question) there are two standard values that can be used for
453 Backspace: "^H" and "^?". 570 Backspace: "^H" and "^?".
… …
471 588
472 # use Backspace = ^? 589 # use Backspace = ^?
473 $ stty erase ^? 590 $ stty erase ^?
474 $ rxvt 591 $ rxvt
475 592
476 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 593 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
477 594
478 For an existing rxvt-unicode: 595 For an existing rxvt-unicode:
479 596
480 # use Backspace = ^H 597 # use Backspace = ^H
481 $ stty erase ^H 598 $ stty erase ^H
… …
490 value properly reflects that. 607 value properly reflects that.
491 608
492 The Delete key is a another casualty of the ill-defined Backspace 609 The Delete key is a another casualty of the ill-defined Backspace
493 problem. To avoid confusion between the Backspace and Delete keys, 610 problem. To avoid confusion between the Backspace and Delete keys,
494 the Delete key has been assigned an escape sequence to match the 611 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. 612 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
613 termcap/terminfo.
496 614
497 Some other Backspace problems: 615 Some other Backspace problems:
498 616
499 some editors use termcap/terminfo, some editors (vim I'm told) 617 some editors use termcap/terminfo, some editors (vim I'm told)
500 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 618 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
506 There are some compile-time selections available via configure. 624 There are some compile-time selections available via configure.
507 Unless you have run "configure" with the "--disable-resources" 625 Unless you have run "configure" with the "--disable-resources"
508 option you can use the `keysym' resource to alter the keystrings 626 option you can use the `keysym' resource to alter the keystrings
509 associated with keysyms. 627 associated with keysyms.
510 628
511 Here's an example for a URxvt session started using `rxvt -name 629 Here's an example for a URxvt session started using "rxvt -name
512 URxvt' 630 URxvt"
513 631
514 URxvt*keysym.Home: \e[1~ 632 URxvt.keysym.Home: \033[1~
515 URxvt*keysym.End: \e[4~ 633 URxvt.keysym.End: \033[4~
516 URxvt*keysym.C-apostrophe: \e<C-'> 634 URxvt.keysym.C-apostrophe: \033<C-'>
517 URxvt*keysym.C-slash: \e<C-/> 635 URxvt.keysym.C-slash: \033<C-/>
518 URxvt*keysym.C-semicolon: \e<C-;> 636 URxvt.keysym.C-semicolon: \033<C-;>
519 URxvt*keysym.C-grave: \e<C-`> 637 URxvt.keysym.C-grave: \033<C-`>
520 URxvt*keysym.C-comma: \e<C-,> 638 URxvt.keysym.C-comma: \033<C-,>
521 URxvt*keysym.C-period: \e<C-.> 639 URxvt.keysym.C-period: \033<C-.>
522 URxvt*keysym.C-0x60: \e<C-`> 640 URxvt.keysym.C-0x60: \033<C-`>
523 URxvt*keysym.C-Tab: \e<C-Tab> 641 URxvt.keysym.C-Tab: \033<C-Tab>
524 URxvt*keysym.C-Return: \e<C-Return> 642 URxvt.keysym.C-Return: \033<C-Return>
525 URxvt*keysym.S-Return: \e<S-Return> 643 URxvt.keysym.S-Return: \033<S-Return>
526 URxvt*keysym.S-space: \e<S-Space> 644 URxvt.keysym.S-space: \033<S-Space>
527 URxvt*keysym.M-Up: \e<M-Up> 645 URxvt.keysym.M-Up: \033<M-Up>
528 URxvt*keysym.M-Down: \e<M-Down> 646 URxvt.keysym.M-Down: \033<M-Down>
529 URxvt*keysym.M-Left: \e<M-Left> 647 URxvt.keysym.M-Left: \033<M-Left>
530 URxvt*keysym.M-Right: \e<M-Right> 648 URxvt.keysym.M-Right: \033<M-Right>
531 URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.> 649 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
532 URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.> 650 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
533 URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007 651 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
652
653 See some more examples in the documentation for the keysym resource.
534 654
535 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 655 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How
536 do I make use of them? For example, the Sun Keyboard type 4 has the 656 do I make use of them? For example, the Sun Keyboard type 4 has the
537 following mappings that rxvt-unicode doesn't recognize. 657 following mappings that rxvt-unicode doesn't recognize.
538 KP_Insert == Insert 658 KP_Insert == Insert
… …
544 664
545 Rather than have rxvt-unicode try to accommodate all the various 665 Rather than have rxvt-unicode try to accommodate all the various
546 possible keyboard mappings, it is better to use `xmodmap' to remap 666 possible keyboard mappings, it is better to use `xmodmap' to remap
547 the keys as required for your particular machine. 667 the keys as required for your particular machine.
548 668
549 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 669 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
550 need this to decide about setting colors etc. 670 I need this to decide about setting colors etc.
551 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 671 rxvt and rxvt-unicode always export the variable "COLORTERM", so you
552 can check and see if that is set. Note that several programs, JED, 672 can check and see if that is set. Note that several programs, JED,
553 slrn, Midnight Commander automatically check this variable to decide 673 slrn, Midnight Commander automatically check this variable to decide
554 whether or not to use color. 674 whether or not to use color.
555 675
… …
586 Before sending me mail, you could go to IRC: "irc.freenode.net", 706 Before sending me mail, you could go to IRC: "irc.freenode.net",
587 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might 707 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might
588 be interested in learning about new and exciting problems (but not 708 be interested in learning about new and exciting problems (but not
589 FAQs :). 709 FAQs :).
590 710
591SYNOPSIS 711RXVT TECHNICAL REFERENCE
592 # set a new font set
593 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
594
595 # change the locale and tell rxvt-unicode about it
596 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
597
598 # set window title
599 printf '\33]2;%s\007' "new window title"
600
601DESCRIPTION 712DESCRIPTION
602 The rest of this document describes various technical aspects of 713 The rest of this document describes various technical aspects of
603 rxvt-unicode. First the description of supported command sequences, 714 rxvt-unicode. First the description of supported command sequences,
604 followed by menu and pixmap support and last by a description of all 715 followed by menu and pixmap support and last by a description of all
605 features selectable at "configure" time. 716 features selectable at "configure" time.
606 717
607RXVT TECHNICAL REFERENCE
608Definitions 718Definitions
609 "c" The literal character c. 719 "c" The literal character c.
610 720
611 "C" A single (required) character. 721 "C" A single (required) character.
612 722
… …
697 "ESC O" 807 "ESC O"
698 Single Shift Select of G3 Character Set (SS3): affects next 808 Single Shift Select of G3 Character Set (SS3): affects next
699 character only *unimplemented* 809 character only *unimplemented*
700 810
701 "ESC Z" 811 "ESC Z"
702 Obsolete form of returns: "ESC[?1;2C" *rxvt-unicode compile-time 812 Obsolete form of returns: "ESC [ ? 1 ; 2 C" *rxvt-unicode
703 option* 813 compile-time option*
704 814
705 "ESC c" 815 "ESC c"
706 Full reset (RIS) 816 Full reset (RIS)
707 817
708 "ESC n" 818 "ESC n"
709 Invoke the G2 Character Set (LS2) 819 Invoke the G2 Character Set (LS2)
710 820
711 "ESC o" 821 "ESC o"
712 Invoke the G3 Character Set (LS3) 822 Invoke the G3 Character Set (LS3)
713 823
714 "ESC" ( C> 824 "ESC ( C"
715 Designate G0 Character Set (ISO 2022), see below for values of "C". 825 Designate G0 Character Set (ISO 2022), see below for values of "C".
716 826
717 "ESC" ) C> 827 "ESC ) C"
718 Designate G1 Character Set (ISO 2022), see below for values of "C". 828 Designate G1 Character Set (ISO 2022), see below for values of "C".
719 829
720 "ESC * C" 830 "ESC * C"
721 Designate G2 Character Set (ISO 2022), see below for values of "C". 831 Designate G2 Character Set (ISO 2022), see below for values of "C".
722 832
… …
815 "ESC [ Ps a" 925 "ESC [ Ps a"
816 See "ESC [ Ps C" 926 See "ESC [ Ps C"
817 927
818 "ESC [ Ps c" 928 "ESC [ Ps c"
819 Send Device Attributes (DA) "Ps = 0" (or omitted): request 929 Send Device Attributes (DA) "Ps = 0" (or omitted): request
820 attributes from terminal returns: "ESC[?1;2c" (``I am a VT100 with 930 attributes from terminal returns: "ESC [ ? 1 ; 2 c" (``I am a VT100
821 Advanced Video Option'') 931 with Advanced Video Option'')
822 932
823 "ESC [ Ps d" 933 "ESC [ Ps d"
824 Cursor to Line "Ps" (VPA) 934 Cursor to Line "Ps" (VPA)
825 935
826 "ESC [ Ps e" 936 "ESC [ Ps e"
… …
900 (CSR) 1010 (CSR)
901 1011
902 "ESC [ s" 1012 "ESC [ s"
903 Save Cursor (SC) 1013 Save Cursor (SC)
904 1014
1015 "ESC [ Ps;Pt t"
1016 Window Operations
1017
1018 Ps = 1 Deiconify (map) window
1019 Ps = 2 Iconify window
1020 Ps = 3 ESC [ 3 ; X ; Y t Move window to (X|Y)
1021 Ps = 4 ESC [ 4 ; H ; W t Resize to WxH pixels
1022 Ps = 5 Raise window
1023 Ps = 6 Lower window
1024 Ps = 7 Refresh screen once
1025 Ps = 8 ESC [ 8 ; R ; C t Resize to R rows and C columns
1026 Ps = 11 Report window state (responds with Ps = 1 or Ps = 2)
1027 Ps = 13 Report window position (responds with Ps = 3)
1028 Ps = 14 Report window pixel size (responds with Ps = 4)
1029 Ps = 18 Report window text size (responds with Ps = 7)
1030 Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9
1031 Ps = 20 Reports icon label (ESC ] L NAME \234)
1032 Ps = 21 Reports window title (ESC ] l NAME \234)
1033 Ps = 24.. Set window height to Ps rows
1034
1035 "ESC [ u"
1036 Restore Cursor
1037
905 "ESC [ Ps x" 1038 "ESC [ Ps x"
906 Request Terminal Parameters (DECREQTPARM) 1039 Request Terminal Parameters (DECREQTPARM)
907
908 "ESC [ u"
909 Restore Cursor
910 1040
911 1041
912 1042
913DEC Private Modes 1043DEC Private Modes
914 "ESC [ ? Pm h" 1044 "ESC [ ? Pm h"
… …
1056 Ps = 13 Change colour of mouse foreground to Pt 1186 Ps = 13 Change colour of mouse foreground to Pt
1057 Ps = 17 Change colour of highlight characters to Pt 1187 Ps = 17 Change colour of highlight characters to Pt
1058 Ps = 18 Change colour of bold characters to Pt 1188 Ps = 18 Change colour of bold characters to Pt
1059 Ps = 19 Change colour of underlined characters to Pt 1189 Ps = 19 Change colour of underlined characters to Pt
1060 Ps = 20 Change default background to Pt 1190 Ps = 20 Change default background to Pt
1061 Ps = 39 Change default foreground colour to Pt rxvt compile-time option 1191 Ps = 39 Change default foreground colour to Pt.
1062 Ps = 46 Change Log File to Pt unimplemented 1192 Ps = 46 Change Log File to Pt unimplemented
1063 Ps = 49 Change default background colour to Pt rxvt compile-time option 1193 Ps = 49 Change default background colour to Pt.
1064 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 1194 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
1065 Ps = 55 Log all scrollback buffer and all of screen to Pt 1195 Ps = 55 Log all scrollback buffer and all of screen to Pt
1066 Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (rxvt extension) 1196 Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
1067 Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) 1197 Ps = 703 Menubar command Pt (Compile menubar).
1068 Ps = 704 Change colour of italic characters to Pt 1198 Ps = 704 Change colour of italic characters to Pt
1069 Ps = 705 Change background pixmap tint colour to Pt 1199 Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1070 Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1200 Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
1071 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. 1201 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
1072 Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. 1202 Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1073 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. 1203 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1204 Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1205 Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1074 1206
1075 1207
1076 1208
1077menuBar 1209menuBar
1078 The exact syntax used is *almost* solidified. In the menus, DON'T try to 1210 The exact syntax used is *almost* solidified. In the menus, DON'T try to
… …
1115 [menu] 1247 [menu]
1116 access the current menuBar for alteration 1248 access the current menuBar for alteration
1117 1249
1118 [title:+*string*] 1250 [title:+*string*]
1119 set the current menuBar's title to *string*, which may contain the 1251 set the current menuBar's title to *string*, which may contain the
1120 following format specifiers: %% : literal % character %n : rxvt name 1252 following format specifiers:
1121 (as per the -name command-line option) %v : rxvt version 1253
1254 B<%n> rxvt name (as per the B<-name> command-line option)
1255 B<%v> rxvt version
1256 B<%%> literal B<%> character
1122 1257
1123 [done] 1258 [done]
1124 set menuBar access as readonly. End-of-file tag for [read:+*file*] 1259 set menuBar access as readonly. End-of-file tag for [read:+*file*]
1125 operations. 1260 operations.
1126 1261
… …
1230 1365
1231 As a convenience for the many Emacs-type editors, *action* may start 1366 As a convenience for the many Emacs-type editors, *action* may start
1232 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if 1367 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if
1233 missed from M-x commands. 1368 missed from M-x commands.
1234 1369
1235 As a convenience for issuing XTerm ESC] sequences from a menubar (or 1370 As a convenience for issuing XTerm ESC ] sequences from a menubar (or
1236 quick arrow), a BEL (^G) will be appended if needed. 1371 quick arrow), a BEL (^G) will be appended if needed.
1237 1372
1238 For example, 1373 For example,
1239 M-xapropos is equivalent to \Exapropos\r 1374 M-xapropos is equivalent to \Exapropos\r
1240 1375
… …
1562 --enable-font-styles 1697 --enable-font-styles
1563 Add support for bold, *italic* and *bold italic* font styles. The 1698 Add support for bold, *italic* and *bold italic* font styles. The
1564 fonts can be set manually or automatically. 1699 fonts can be set manually or automatically.
1565 1700
1566 --with-codesets=NAME,... 1701 --with-codesets=NAME,...
1567 Compile in support for additional codeset (encoding) groups (eu, vn 1702 Compile in support for additional codeset (encoding) groups ("eu",
1568 are always compiled in, which includes most 8-bit character sets). 1703 "vn" are always compiled in, which includes most 8-bit character
1569 These codeset tables are currently only used for driving X11 core 1704 sets). These codeset tables are used for driving X11 core fonts,
1570 fonts, they are not required for Xft fonts. Compiling them in will 1705 they are not required for Xft fonts, although having them compiled
1571 make your binary bigger (together about 700kB), but it doesn't 1706 in lets rxvt-unicode choose replacement fonts more intelligently.
1572 increase memory usage unless you use an X11 font requiring one of 1707 Compiling them in will make your binary bigger (all of together cost
1573 these encodings. 1708 about 700kB), but it doesn't increase memory usage unless you use a
1709 font requiring one of these encodings.
1574 1710
1575 all all available codeset groups 1711 all all available codeset groups
1576 zh common chinese encodings 1712 zh common chinese encodings
1577 zh_ext rarely used but very big chinese encodigs 1713 zh_ext rarely used but very big chinese encodigs
1578 jp common japanese encodings 1714 jp common japanese encodings
… …
1602 accents are encoded as seperate unicode characters. This is done by 1738 accents are encoded as seperate unicode characters. This is done by
1603 using precomposited characters when available or creating new 1739 using precomposited characters when available or creating new
1604 pseudo-characters when no precomposed form exists. 1740 pseudo-characters when no precomposed form exists.
1605 1741
1606 Without --enable-unicode3, the number of additional precomposed 1742 Without --enable-unicode3, the number of additional precomposed
1607 characters is rather limited (2048, if this is full, rxvt will use 1743 characters is rather limited (2048, if this is full, rxvt-unicode
1608 the private use area, extending the number of combinations to 8448). 1744 will use the private use area, extending the number of combinations
1609 With --enable-unicode3, no practical limit exists. This will also 1745 to 8448). With --enable-unicode3, no practical limit exists.
1610 enable storage of characters >65535. 1746
1747 This option will also enable storage (but not display) of characters
1748 beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1611 1749
1612 The combining table also contains entries for arabic presentation 1750 The combining table also contains entries for arabic presentation
1613 forms, but these are not currently used. Bug me if you want these to 1751 forms, but these are not currently used. Bug me if you want these to
1614 be used. 1752 be used (and tell me how these are to be used...).
1615 1753
1616 --enable-fallback(=CLASS) 1754 --enable-fallback(=CLASS)
1617 When reading resource settings, also read settings for class CLASS 1755 When reading resource settings, also read settings for class CLASS
1618 (default: Rxvt). To disable resource fallback use 1756 (default: Rxvt). To disable resource fallback use
1619 --disable-fallback. 1757 --disable-fallback.
… …
1693 1831
1694 --enable-xgetdefault 1832 --enable-xgetdefault
1695 Make resources checking via XGetDefault() instead of our small 1833 Make resources checking via XGetDefault() instead of our small
1696 version which only checks ~/.Xdefaults, or if that doesn't exist 1834 version which only checks ~/.Xdefaults, or if that doesn't exist
1697 then ~/.Xresources. 1835 then ~/.Xresources.
1836
1837 Please note that nowadays, things like XIM will automatically pull
1838 in and use the full X resource manager, so the overhead of using it
1839 might be very small, if nonexistant.
1698 1840
1699 --enable-strings 1841 --enable-strings
1700 Add support for our possibly faster memset() function and other 1842 Add support for our possibly faster memset() function and other
1701 various routines, overriding your system's versions which may have 1843 various routines, overriding your system's versions which may have
1702 been hand-crafted in assembly or may require extra libraries to link 1844 been hand-crafted in assembly or may require extra libraries to link
… …
1713 1855
1714 A non-exhaustive list of features enabled by "--enable-frills" 1856 A non-exhaustive list of features enabled by "--enable-frills"
1715 (possibly in combination with other switches) is: 1857 (possibly in combination with other switches) is:
1716 1858
1717 MWM-hints 1859 MWM-hints
1860 EWMH-hints (pid, utf8 names) and protocols (ping)
1718 seperate underline colour 1861 seperate underline colour
1719 settable border widths and borderless switch 1862 settable border widths and borderless switch
1720 settable extra linespacing 1863 settable extra linespacing
1721 extra window properties (e.g. UTF-8 window names and PID)
1722 iso-14755-2 and -3, and visual feedback 1864 iso-14755-2 and -3, and visual feedback
1723 backindex and forwardindex escape sequence 1865 backindex and forwardindex escape sequence
1724 window op and locale change escape sequences 1866 window op and some xterm/OSC escape sequences
1725 tripleclickwords 1867 tripleclickwords
1726 settable insecure mode 1868 settable insecure mode
1869 keysym remapping support
1870 cursor blinking and underline cursor
1871 -embed and -pty-fd options
1727 1872
1728 --enable-iso14755 1873 --enable-iso14755
1729 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). 1874 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
1730 Basic support (section 5.1) is enabled by "--enable-frills", while 1875 Basic support (section 5.1) is enabled by "--enable-frills", while
1731 support for 5.2, 5.3 and 5.4 is enabled with this switch. 1876 support for 5.2, 5.3 and 5.4 is enabled with this switch.
… …
1761 --enable-smart-resize 1906 --enable-smart-resize
1762 Add smart growth/shrink behaviour when changing font size via from 1907 Add smart growth/shrink behaviour when changing font size via from
1763 hot keys. This should keep in a fixed position the rxvt corner which 1908 hot keys. This should keep in a fixed position the rxvt corner which
1764 is closest to a corner of the screen. 1909 is closest to a corner of the screen.
1765 1910
1766 --enable-cursor-blink
1767 Add support for a blinking cursor.
1768
1769 --enable-pointer-blank 1911 --enable-pointer-blank
1770 Add support to have the pointer disappear when typing or inactive. 1912 Add support to have the pointer disappear when typing or inactive.
1771 1913
1772 --with-name=NAME 1914 --with-name=NAME
1773 Set the basename for the installed binaries (default: "urxvt", 1915 Set the basename for the installed binaries (default: "urxvt",

Diff Legend

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