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.2 by root, Sun Jan 16 15:59:45 2005 UTC vs.
Revision 1.28 by root, Sat Dec 24 12:55:17 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 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>.
21
4FREQUENTLY ASKED QUESTIONS 22FREQUENTLY ASKED QUESTIONS
23 Isn't rxvt supposed to be small? Don't all those features bloat?
24 I often get asked about this, and I think, no, they didn't cause
25 extra bloat. If you compare a minimal rxvt and a minimal urxvt, you
26 can see that the urxvt binary is larger (due to some encoding tables
27 always being compiled in), but it actually uses less memory (RSS)
28 after startup. Even with "--disable-everything", this comparison is
29 a bit unfair, as many features unique to urxvt (locale, encoding
30 conversion, iso14755 etc.) are already in use in this mode.
31
32 text data bss drs rss filename
33 98398 1664 24 15695 1824 rxvt --disable-everything
34 188985 9048 66616 18222 1788 urxvt --disable-everything
35
36 When you "--enable-everything" (which _is_ unfair, as this involves
37 xft and full locale/XIM support which are quite bloaty inside libX11
38 and my libc), the two diverge, but not unreasnobaly so.
39
40 text data bss drs rss filename
41 163431 2152 24 20123 2060 rxvt --enable-everything
42 1035683 49680 66648 29096 3680 urxvt --enable-everything
43
44 The very large size of the text section is explained by the
45 east-asian encoding tables, which, if unused, take up disk space but
46 nothing else and can be compiled out unless you rely on X11 core
47 fonts that use those encodings. The BSS size comes from the 64k
48 emergency buffer that my c++ compiler allocates (but of course
49 doesn't use unless you are out of memory). Also, using an xft font
50 instead of a core font immediately adds a few megabytes of RSS. Xft
51 indeed is responsible for a lot of RSS even when not used.
52
53 Of course, due to every character using two or four bytes instead of
54 one, a large scrollback buffer will ultimately make rxvt-unicode use
55 more memory.
56
57 Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k),
58 this still fares rather well. And compared to some monsters like
59 gnome-terminal (21152k + extra 4204k in separate processes) or
60 konsole (22200k + extra 43180k in daemons that stay around after
61 exit, plus half aminute of startup time, including the hundreds of
62 warnings it spits out), it fares extremely well *g*.
63
64 Why C++, isn't that unportable/bloated/uncool?
65 Is this a question? :) It comes up very often. The simple answer is:
66 I had to write it, and C++ allowed me to write and maintain it in a
67 fraction of the time and effort (which is a scarce resource for me).
68 Put even shorter: It simply wouldn't exist without C++.
69
70 My personal stance on this is that C++ is less portable than C, but
71 in the case of rxvt-unicode this hardly matters, as its portability
72 limits are defined by things like X11, pseudo terminals, locale
73 support and unix domain sockets, which are all less portable than
74 C++ itself.
75
76 Regarding the bloat, see the above question: It's easy to write
77 programs in C that use gobs of memory, an certainly possible to
78 write programs in C++ that don't. C++ also often comes with large
79 libraries, but this is not necessarily the case with GCC. Here is
80 what rxvt links against on my system with a minimal config:
81
82 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
83 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
84 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
85 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
86
87 And here is rxvt-unicode:
88
89 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
90 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
91 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
92 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
93 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
94
95 No large bloated libraries (of course, none were linked in
96 statically), except maybe libX11 :)
97
98 Does it support tabs, can I have a tabbed rxvt-unicode?
99 rxvt-unicode does not directly support tabs. It will work fine with
100 tabbing functionality of many window managers or similar tabbing
101 programs, and its embedding-features allow it to be embedded into
102 other programs, as witnessed by doc/rxvt-tabbed or the upcoming
103 "Gtk2::URxvt" perl module, which features a tabbed urxvt (murxvt)
104 terminal as an example embedding application.
105
5 How do I know which rxvt-unicode version I'm using? 106 How do I know which rxvt-unicode version I'm using?
6 The version number is displayed with the usage (-h). Also the escape 107 The version number is displayed with the usage (-h). Also the escape
7 sequence "ESC[8n" sets the window title to the version number. 108 sequence "ESC [ 8 n" sets the window title to the version number.
109 When using the urxvtc client, the version displayed is that of the
110 daemon.
111
112 I am using Debian GNU/Linux and have a problem...
113 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
114 patches that considerably change the behaviour of rxvt-unicode.
115 Before reporting a bug to the original rxvt-unicode author please
116 download and install the genuine version
117 (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
118 problem. If you cannot, chances are that the problems are specific
119 to Debian GNU/Linux, in which case it should be reported via the
120 Debian Bug Tracking System (use "reportbug" to report the bug).
121
122 For other problems that also affect the Debian package, you can and
123 probably should use the Debian BTS, too, because, after all, it's
124 also a bug in the Debian version and it serves as a reminder for
125 other users that might encounter the same issue.
8 126
9 When I log-in to another system it tells me about missing terminfo data? 127 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 128 The terminal description used by rxvt-unicode is not as widely
11 available as that for xterm, or even rxvt (for which the same 129 available as that for xterm, or even rxvt (for which the same
12 problem often arises). 130 problem often arises).
… …
24 problems arising, which includes wrong keymapping, less and 142 problems arising, which includes wrong keymapping, less and
25 different colours and some refresh errors in fullscreen 143 different colours and some refresh errors in fullscreen
26 applications. It's a nice quick-and-dirty workaround for rare cases, 144 applications. It's a nice quick-and-dirty workaround for rare cases,
27 though. 145 though.
28 146
29 If you always want to do this you can either recompile rxvt-unicode 147 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: 148 you can either recompile rxvt-unicode with the desired TERM value or
149 use a resource to set it:
31 150
32 URxvt.termName: rxvt 151 URxvt.termName: rxvt
33 152
34 If you don't plan to use rxvt (quite common...) you could also 153 If you don't plan to use rxvt (quite common...) you could also
35 replace the rxvt terminfo file with the rxvt-unicode one. 154 replace the rxvt terminfo file with the rxvt-unicode one.
36 155
156 "tic" outputs some error when compiling the terminfo entry.
157 Most likely it's the empty definition for "enacs=". Just replace it
158 by "enacs=\E[0@" and try again.
159
160 "bash"'s readline does not work correctly under urxvt.
37 I need a termcap file entry. 161 I need a termcap file entry.
162 One reason you might want this is that some distributions or
163 operating systems still compile some programs using the
164 long-obsoleted termcap library (Fedora Core's bash is one example)
165 and rely on a termcap entry for "rxvt-unicode".
166
38 You could use rxvt's termcap entry with resonable results in many 167 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 168 cases. You can also create a termcap entry by using terminfo's
40 infocmp program like this: 169 infocmp program like this:
41 170
42 infocmp -C rxvt-unicode 171 infocmp -C rxvt-unicode
43 172
44 OR you could this termcap entry: 173 Or you could use this termcap entry, generated by the command above:
45 174
46 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 175 rxvt-unicode|rxvt-unicode terminal (X Window System):\
47 :am:bw:eo:km:mi:ms:xn:xo:\ 176 :am:bw:eo:km:mi:ms:xn:xo:\
48 :co#80:it#8:li#24:\ 177 :co#80:it#8:li#24:lm#0:\
49 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 178 :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:\ 179 :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:\ 180 :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:\ 181 :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:\ 182 :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[@:\ 183 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
184 :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:\ 185 :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~:\ 186 :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~:\ 187 :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:\ 188 :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=:\ 189 :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:\ 190 :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:\ 191 :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:\ 192 :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:\ 193 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
64 :vs=\E[?25h: 194 :vs=\E[?25h:
65 195
66 Why does "ls" no longer have coloured output? 196 Why does "ls" no longer have coloured output?
67 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 197 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 198 decide wether a terminal has colour, but uses it's own configuration
… …
87 furthermore fail to even install the "rxvt-unicode" terminfo file, 217 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 218 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 219 log-in to another system it tells me about missing terminfo data? on
90 how to do this). 220 how to do this).
91 221
222 My numerical keypad acts weird and generates differing output?
223 Some Debian GNUL/Linux users seem to have this problem, although no
224 specific details were reported so far. It is possible that this is
225 caused by the wrong "TERM" setting, although the details of wether
226 and how this can happen are unknown, as "TERM=rxvt" should offer a
227 compatible keymap. See the answer to the previous question, and
228 please report if that helped.
229
92 Rxvt-unicode does not seem to understand the selected encoding? 230 Rxvt-unicode does not seem to understand the selected encoding?
93 Unicode does not seem to work? 231 Unicode does not seem to work?
94 If you encounter strange problems like typing an accented character 232 If you encounter strange problems like typing an accented character
95 but getting two unrelated other characters or similar, or if program 233 but getting two unrelated other characters or similar, or if program
96 output is subtly garbled, then you should check your locale 234 output is subtly garbled, then you should check your locale
97 settings. 235 settings.
98 236
99 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 237 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 238 programs. Often rxvt-unicode is started in the "C" locale, while the
101 login script running within the rxvt-unicode window changes the 239 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 240 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
103 not going to work. 241 is not going to work.
104 242
105 The best thing is to fix your startup environment, as you will 243 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 244 likely run into other problems. If nothing works you can try this in
107 your .profile. 245 your .profile.
108 246
109 printf '\e]701;%s\007' "$LC_CTYPE" 247 printf '\e]701;%s\007' "$LC_CTYPE"
110 248
111 If this doesn't work, then maybe you use a "LC_CTYPE" specification 249 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 250 not supported on your systems. Some systems have a "locale" command
113 which displays this. If it displays sth. like: 251 which displays this (also, "perl -e0" can be used to check locale
252 settings, as it will complain loudly if it cannot set the locale).
253 If it displays something like:
114 254
115 locale: Cannot set LC_CTYPE to default locale: ... 255 locale: Cannot set LC_CTYPE to default locale: ...
116 256
117 Then the locale you specified is not supported on your system. 257 Then the locale you specified is not supported on your system.
118 258
… …
126 Chances are that the font you (or the admin/package maintainer of 266 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 267 your system/os) have specified does not cover all the characters you
128 want to display. 268 want to display.
129 269
130 rxvt-unicode makes a best-effort try at finding a replacement font. 270 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. 271 Often the result is fine, but sometimes the chosen font looks
132 Many fonts have totally strange characters that don't resemble the 272 bad/ugly/wrong. Some fonts have totally strange characters that
133 correct glyph at all, and rxvt-unicode lacks the artificial 273 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 274 artificial intelligence to detect that a specific glyph is wrong: it
135 believe the font that the characters it contains indeed look 275 has to believe the font that the characters it claims to contain
136 correct. 276 indeed look correct.
137 277
138 In that case, select a font of your taste and add it to the font 278 In that case, select a font of your taste and add it to the font
139 list, e.g.: 279 list, e.g.:
140 280
141 rxvt -fn basefont,font2,font3... 281 urxvt -fn basefont,font2,font3...
142 282
143 When rxvt-unicode sees a character, it will first look at the base 283 When rxvt-unicode sees a character, it will first look at the base
144 font. If the base font does not contain the character, it will go to 284 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 285 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 286 up this search and use less resources within rxvt-unicode and the
147 X-server. 287 X-server.
148 288
149 The only limitation is that all the fonts must not be larger than 289 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, 290 base font, as the base font defines the terminal character cell
151 which must be the same due to the way terminals work. 291 size, which must be the same due to the way terminals work.
152 292
153 Why do some chinese characters look so different than others? 293 Why do some chinese characters look so different than others?
154 This is because there is a difference between script and language -- 294 This is because there is a difference between script and language --
155 rxvt-unicode does not know which language the text that is output 295 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 296 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 297 first sees a japanese/chinese character, it might choose a japanese
158 it. Subsequent japanese characters will take that font. Now, many 298 font for display. Subsequent japanese characters will use that font.
159 chinese characters aren't represented in japanese fonts, so when the 299 Now, many chinese characters aren't represented in japanese fonts,
160 first non-japanese character comes up, rxvt-unicode will look for a 300 so when the first non-japanese character comes up, rxvt-unicode will
161 chinese font -- unfortunately at this point, it will still use the 301 look for a chinese font -- unfortunately at this point, it will
162 japanese font for japanese characters that are also chinese. 302 still use the japanese font for chinese characters that are also in
303 the japanese font.
163 304
164 The workaround is easy: just tag a chinese font at the end of your 305 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 306 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 307 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 308 japanese font first. If you expect more chinese, put a chinese font
168 first. 309 first.
169 310
170 In the future it might be possible to switch preferences at runtime 311 In the future it might be possible to switch language preferences at
171 (the internal data structure has no problem with using different 312 runtime (the internal data structure has no problem with using
172 fonts for the same character at the same time, but no interface for 313 different fonts for the same character at the same time, but no
173 this has been designed yet). 314 interface for this has been designed yet).
315
316 Until then, you might get away with switching fonts at runtime (see
317 "Can I switch the fonts at runtime?" later in this document).
174 318
175 Why does rxvt-unicode sometimes leave pixel droppings? 319 Why does rxvt-unicode sometimes leave pixel droppings?
176 Most fonts were not designed for terminal use, which means that 320 Most fonts were not designed for terminal use, which means that
177 character size varies a lot. A font that is otherwise fine for 321 character size varies a lot. A font that is otherwise fine for
178 terminal use might contain some characters that are simply too wide. 322 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. 336 that doesn't work, you might be forced to use a different font.
193 337
194 All of this is not a problem when using X11 core fonts, as their 338 All of this is not a problem when using X11 core fonts, as their
195 bounding box data is correct. 339 bounding box data is correct.
196 340
341 On Solaris 9, many line-drawing characters are too wide.
342 Seems to be a known bug, read
343 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
344 following ugly workaround to get non-double-wide-characters working:
345
346 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
347
197 My Compose (Multi_key) key is no longer working. 348 My Compose (Multi_key) key is no longer working.
198 The most common causes for this are that either your locale is not 349 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 350 set correctly, or you specified a preeditStyle that is not supported
200 by your input method. For example, if you specified OverTheSpot and 351 by your input method. For example, if you specified OverTheSpot and
201 your input method (e.g. the default input method handling Compose 352 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 363 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 364 other codes, too, such as "Ctrl-Shift-1-d" to type the default
214 telnet escape character and so on. 365 telnet escape character and so on.
215 366
216 How can I keep rxvt-unicode from using reverse video so much? 367 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 368 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 369 settings ("TERM=rxvt-unicode"), which will get rid of most of these
219 sure you have specified colours for italic and bold, as otherwise 370 effects. Then make sure you have specified colours for italic and
220 rxvt-unicode might use reverse video to simulate the effect: 371 bold, as otherwise rxvt-unicode might use reverse video to simulate
372 the effect:
221 373
222 URxvt*colorBD: white 374 URxvt.colorBD: white
223 URxvt*colorIT: green 375 URxvt.colorIT: green
224 376
225 Some programs assume totally weird colours (red instead of blue), how 377 Some programs assume totally weird colours (red instead of blue), how
226 can I fix that? 378 can I fix that?
227 For some unexplainable reason, some programs (i.e. irssi) assume a 379 For some unexplainable reason, some rare programs assume a very
228 very weird colour palette when confronted with a terminal with more 380 weird colour palette when confronted with a terminal with more than
229 than the standard 8 colours (rxvt-unicode supports 88). The right 381 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 382 of course, to fix these programs not to assume non-ISO colours
231 colours without very good reasons. 383 without very good reasons.
232 384
233 In the meantime, you can either edit your "urxvt" terminfo 385 In the meantime, you can either edit your "rxvt-unicode" terminfo
234 definition to only claim 8 colour support or use "TERM=rxvt", which 386 definition to only claim 8 colour support or use "TERM=rxvt", which
235 will fix colours but keep you from using other rxvt-unicode 387 will fix colours but keep you from using other rxvt-unicode
236 features. 388 features.
237 389
238 I am on FreeBSD and rxvt-unicode does not seem to work at all. 390 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__" 393 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
242 requires that wchar_t is represented as unicode. 394 requires that wchar_t is represented as unicode.
243 395
244 As you might have guessed, FreeBSD does neither define this symobl 396 As you might have guessed, FreeBSD does neither define this symobl
245 nor does it support it. Instead, it uses it's own internal 397 nor does it support it. Instead, it uses it's own internal
246 representation of wchar_t. This is, of course, completely legal. 398 representation of wchar_t. This is, of course, completely fine with
399 respect to standards.
247 400
401 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
402 and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
403
248 However, "__STDC_ISO_10646__" is the only sane way to support 404 "__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 405 apps in an OS, as using a locale-dependent (and non-standardized)
250 non-standardized) representation of wchar_t makes it impossible to 406 representation of wchar_t makes it impossible to convert between
251 convert between wchar_t (as used by X11 and your applications) and 407 wchar_t (as used by X11 and your applications) and any other
252 any other encoding without implementing OS-specific-wrappers for 408 encoding without implementing OS-specific-wrappers for each and
253 each and every locale. There simply are no APIs to convert wchar_t 409 every locale. There simply are no APIs to convert wchar_t into
254 into anything except the current locale encoding. 410 anything except the current locale encoding.
255 411
256 Some applications (such as the formidable mlterm) work around this 412 Some applications (such as the formidable mlterm) work around this
257 by carrying their own replacement functions for character set 413 by carrying their own replacement functions for character set
258 handling with them, and either implementing OS-dependent hacks or 414 handling with them, and either implementing OS-dependent hacks or
259 doing multiple conversions (which is slow and unreliable in case the 415 doing multiple conversions (which is slow and unreliable in case the
260 OS implements encodings slightly different than the terminal 416 OS implements encodings slightly different than the terminal
261 emulator). 417 emulator).
262 418
263 The rxvt-unicode author insists that the right way to fix this is in 419 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 420 the system libraries once and for all, instead of forcing every app
265 to carry complete replacements. 421 to carry complete replacements for them :)
422
423 I use Solaris 9 and it doesn't compile/work/etc.
424 Try the diff in doc/solaris9.patch as a base. It fixes the worst
425 problems with "wcwidth" and a compile problem.
426
427 How can I use rxvt-unicode under cygwin?
428 rxvt-unicode should compile and run out of the box on cygwin, using
429 the X11 libraries that come with cygwin. libW11 emulation is no
430 longer supported (and makes no sense, either, as it only supported a
431 single font). I recommend starting the X-server in "-multiwindow" or
432 "-rootless" mode instead, which will result in similar look&feel as
433 the old libW11 emulation.
434
435 At the time of this writing, cygwin didn't seem to support any
436 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
437 likely limited to 8-bit encodings.
266 438
267 How does rxvt-unicode determine the encoding to use? 439 How does rxvt-unicode determine the encoding to use?
268 Is there an option to switch encodings? 440 Is there an option to switch encodings?
269 Unlike some other terminals, rxvt-unicode has no encoding switch, 441 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 442 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
273 445
274 The reasons is that there exists a perfectly fine mechanism for 446 The reasons is that there exists a perfectly fine mechanism for
275 selecting the encoding, doing I/O and (most important) communicating 447 selecting the encoding, doing I/O and (most important) communicating
276 this to all applications so everybody agrees on character properties 448 this to all applications so everybody agrees on character properties
277 such as width and code number. This mechanism is the *locale*. 449 such as width and code number. This mechanism is the *locale*.
450 Applications not using that info will have problems (for example,
451 "xterm" gets the width of characters wrong as it uses it's own,
452 locale-independent table under all locales).
278 453
279 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 454 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
280 All programs doing the same (that is, most) will automatically agree 455 All programs doing the same (that is, most) will automatically agree
281 in the interpretation of characters. 456 in the interpretation of characters.
282 457
… …
290 "language_country.encoding", but other forms (i.e. "de" or "german") 465 "language_country.encoding", but other forms (i.e. "de" or "german")
291 are also common. 466 are also common.
292 467
293 Rxvt-unicode ignores all other locale categories, and except for the 468 Rxvt-unicode ignores all other locale categories, and except for the
294 encoding, ignores country or language-specific settings, i.e. 469 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. 470 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
471 rxvt-unicode.
296 472
297 If you want to use a specific encoding you have to make sure you 473 If you want to use a specific encoding you have to make sure you
298 start rxvt-unicode with the correct "LC_CTYPE" category. 474 start rxvt-unicode with the correct "LC_CTYPE" category.
299 475
300 Can I switch locales at runtime? 476 Can I switch locales at runtime?
301 Yes, using an escape sequence. Try sth. like this, which sets 477 Yes, using an escape sequence. Try something like this, which sets
302 rxvt-unicode's idea of "LC_CTYPE". 478 rxvt-unicode's idea of "LC_CTYPE".
303 479
304 printf '\e]701;%s\007' ja_JP.SJIS 480 printf '\e]701;%s\007' ja_JP.SJIS
305 481
306 See also the previous question. 482 See also the previous answer.
307 483
308 Sometimes this capability is rather handy when you want to work in 484 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 485 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 486 (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: 487 first switches to a locale supported by xjdic and back later:
312 488
313 printf '\e]701;%s\007' ja_JP.SJIS 489 printf '\e]701;%s\007' ja_JP.SJIS
314 xjdic -js 490 xjdic -js
315 printf '\e]701;%s\007' de_DE.UTF-8 491 printf '\e]701;%s\007' de_DE.UTF-8
316 492
493 You can also use xterm's "luit" program, which usually works fine,
494 except for some locales where character width differs between
495 program- and rxvt-unicode-locales.
496
317 Can I switch the fonts at runtime? 497 Can I switch the fonts at runtime?
318 Yes, using an escape sequence. Try sth. like this, which has the 498 Yes, using an escape sequence. Try something like this, which has
319 same effect as using the "-fn" switch, and takes effect immediately: 499 the same effect as using the "-fn" switch, and takes effect
500 immediately:
320 501
321 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 502 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
322 503
323 This is useful if you e.g. work primarily with japanese (and prefer 504 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, 505 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. 508 You can think of this as a kind of manual ISO-2022 switching.
328 509
329 Why do italic characters look as if clipped? 510 Why do italic characters look as if clipped?
330 Many fonts have difficulties with italic characters and hinting. For 511 Many fonts have difficulties with italic characters and hinting. For
331 example, the otherwise very nicely hinted font "xft:Bitstream Vera 512 example, the otherwise very nicely hinted font "xft:Bitstream Vera
332 Sans Mono" completely fails in it's italic face. A workaround is to 513 Sans Mono" completely fails in it's italic face. A workaround might
333 enable freetype autohinting, i.e. like this: 514 be to enable freetype autohinting, i.e. like this:
334 515
335 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 516 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
336 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 517 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
337 518
338 My input method wants <some encoding> but I want UTF-8, what can I do? 519 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 520 You can specify separate locales for the input method and the rest
340 of the terminal, using the resource "imlocale": 521 of the terminal, using the resource "imlocale":
341 522
… …
344 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 525 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 526 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, 527 be able to input characters outside "EUC-JP" in a normal way then,
347 as your input method limits you. 528 as your input method limits you.
348 529
530 Rxvt-unicode crashes when the X Input Method changes or exits.
531 Unfortunately, this is unavoidable, as the XIM protocol is racy by
532 design. Applications can avoid some crashes at the expense of memory
533 leaks, and Input Methods can avoid some crashes by careful ordering
534 at exit time. kinput2 (and derived input methods) generally
535 succeeds, while SCIM (or similar input methods) fails. In the end,
536 however, crashes cannot be completely avoided even if both sides
537 cooperate.
538
539 So the only workaround is not to kill your Input Method Servers.
540
349 Rxvt-unicode uses gobs of memory, how can I reduce that? 541 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 542 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 543 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 544 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 545 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 546 Xft font will be loaded accidentally when rxvt-unicode tries to find
355 characters. 547 a font for your characters.
356 548
357 Also, many people (me included) like large windows and even larger 549 Also, many people (me included) like large windows and even larger
358 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 550 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
359 use 6 bytes per screen cell. For a 160x?? window this amounts to 551 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 552 almost a kilobyte per line. A scrollback buffer of 10000 lines will
… …
362 it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. 554 it gets worse, as rxvt-unicode then uses 8 bytes per screen cell.
363 555
364 Can I speed up Xft rendering somehow? 556 Can I speed up Xft rendering somehow?
365 Yes, the most obvious way to speed it up is to avoid Xft entirely, 557 Yes, the most obvious way to speed it up is to avoid Xft entirely,
366 as it is simply slow. If you still want Xft fonts you might try to 558 as it is simply slow. If you still want Xft fonts you might try to
367 disable antialiasing (by appending ":antialiasing=false"), which 559 disable antialiasing (by appending ":antialias=false"), which saves
368 saves lots of memory and also speeds up rendering considerably. 560 lots of memory and also speeds up rendering considerably.
369 561
370 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? 562 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
371 Rxvt-unicode will use whatever you specify as a font. If it needs to 563 Rxvt-unicode will use whatever you specify as a font. If it needs to
372 fall back to it's default font search list it will prefer X11 core 564 fall back to it's default font search list it will prefer X11 core
373 fonts, because they are small and fast, and then use Xft fonts. It 565 fonts, because they are small and fast, and then use Xft fonts. It
… …
379 Mouse cut/paste suddenly no longer works. 571 Mouse cut/paste suddenly no longer works.
380 Make sure that mouse reporting is actually turned off since killing 572 Make sure that mouse reporting is actually turned off since killing
381 some editors prematurely may leave the mouse in mouse report mode. 573 some editors prematurely may leave the mouse in mouse report mode.
382 I've heard that tcsh may use mouse reporting unless it otherwise 574 I've heard that tcsh may use mouse reporting unless it otherwise
383 specified. A quick check is to see if cut/paste works when the Alt 575 specified. A quick check is to see if cut/paste works when the Alt
384 or Shift keys are depressed. See rxvt(7) 576 or Shift keys are depressed. See urxvt(7)
385 577
386 What's with this bold/blink stuff? 578 What's with this bold/blink stuff?
387 If no bold colour is set via "colorBD:", bold will invert text using 579 If no bold colour is set via "colorBD:", bold will invert text using
388 the standard foreground colour. 580 the standard foreground colour.
389 581
… …
404 resources (or as long-options). 596 resources (or as long-options).
405 597
406 Here are values that are supposed to resemble a VGA screen, 598 Here are values that are supposed to resemble a VGA screen,
407 including the murky brown that passes for low-intensity yellow: 599 including the murky brown that passes for low-intensity yellow:
408 600
409 URxvt*color0: #000000 601 URxvt.color0: #000000
410 URxvt*color1: #A80000 602 URxvt.color1: #A80000
411 URxvt*color2: #00A800 603 URxvt.color2: #00A800
412 URxvt*color3: #A8A800 604 URxvt.color3: #A8A800
413 URxvt*color4: #0000A8 605 URxvt.color4: #0000A8
414 URxvt*color5: #A800A8 606 URxvt.color5: #A800A8
415 URxvt*color6: #00A8A8 607 URxvt.color6: #00A8A8
416 URxvt*color7: #A8A8A8 608 URxvt.color7: #A8A8A8
417 609
418 URxvt*color8: #000054 610 URxvt.color8: #000054
419 URxvt*color9: #FF0054 611 URxvt.color9: #FF0054
420 URxvt*color10: #00FF54 612 URxvt.color10: #00FF54
421 URxvt*color11: #FFFF54 613 URxvt.color11: #FFFF54
422 URxvt*color12: #0000FF 614 URxvt.color12: #0000FF
423 URxvt*color13: #FF00FF 615 URxvt.color13: #FF00FF
424 URxvt*color14: #00FFFF 616 URxvt.color14: #00FFFF
425 URxvt*color15: #FFFFFF 617 URxvt.color15: #FFFFFF
426 618
427 And here is a more complete set of non-standard colors described as 619 And here is a more complete set of non-standard colors described
428 "pretty girly": 620 (not by me) as "pretty girly".
429 621
430 URxvt.cursorColor: #dc74d1 622 URxvt.cursorColor: #dc74d1
431 URxvt.pointerColor: #dc74d1 623 URxvt.pointerColor: #dc74d1
432 URxvt.background: #0e0e0e 624 URxvt.background: #0e0e0e
433 URxvt.foreground: #4ad5e1 625 URxvt.foreground: #4ad5e1
… …
444 URxvt.color6: #73f7ff 636 URxvt.color6: #73f7ff
445 URxvt.color14: #73f7ff 637 URxvt.color14: #73f7ff
446 URxvt.color7: #e1dddd 638 URxvt.color7: #e1dddd
447 URxvt.color15: #e1dddd 639 URxvt.color15: #e1dddd
448 640
641 How can I start urxvtd in a race-free way?
642 Try "urxvtd -f -o", which tells urxvtd to open the display, create
643 the listening socket and then fork.
644
449 What's with the strange Backspace/Delete key behaviour? 645 What's with the strange Backspace/Delete key behaviour?
450 Assuming that the physical Backspace key corresponds to the 646 Assuming that the physical Backspace key corresponds to the
451 BackSpace keysym (not likely for Linux ... see the following 647 BackSpace keysym (not likely for Linux ... see the following
452 question) there are two standard values that can be used for 648 question) there are two standard values that can be used for
453 Backspace: "^H" and "^?". 649 Backspace: "^H" and "^?".
… …
465 661
466 For starting a new rxvt-unicode: 662 For starting a new rxvt-unicode:
467 663
468 # use Backspace = ^H 664 # use Backspace = ^H
469 $ stty erase ^H 665 $ stty erase ^H
470 $ rxvt 666 $ urxvt
471 667
472 # use Backspace = ^? 668 # use Backspace = ^?
473 $ stty erase ^? 669 $ stty erase ^?
474 $ rxvt 670 $ urxvt
475 671
476 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 672 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7).
477 673
478 For an existing rxvt-unicode: 674 For an existing rxvt-unicode:
479 675
480 # use Backspace = ^H 676 # use Backspace = ^H
481 $ stty erase ^H 677 $ stty erase ^H
… …
490 value properly reflects that. 686 value properly reflects that.
491 687
492 The Delete key is a another casualty of the ill-defined Backspace 688 The Delete key is a another casualty of the ill-defined Backspace
493 problem. To avoid confusion between the Backspace and Delete keys, 689 problem. To avoid confusion between the Backspace and Delete keys,
494 the Delete key has been assigned an escape sequence to match the 690 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. 691 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
692 termcap/terminfo.
496 693
497 Some other Backspace problems: 694 Some other Backspace problems:
498 695
499 some editors use termcap/terminfo, some editors (vim I'm told) 696 some editors use termcap/terminfo, some editors (vim I'm told)
500 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 697 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
506 There are some compile-time selections available via configure. 703 There are some compile-time selections available via configure.
507 Unless you have run "configure" with the "--disable-resources" 704 Unless you have run "configure" with the "--disable-resources"
508 option you can use the `keysym' resource to alter the keystrings 705 option you can use the `keysym' resource to alter the keystrings
509 associated with keysyms. 706 associated with keysyms.
510 707
511 Here's an example for a URxvt session started using `rxvt -name 708 Here's an example for a URxvt session started using "urxvt -name
512 URxvt' 709 URxvt"
513 710
514 URxvt*keysym.Home: \e[1~ 711 URxvt.keysym.Home: \033[1~
515 URxvt*keysym.End: \e[4~ 712 URxvt.keysym.End: \033[4~
516 URxvt*keysym.C-apostrophe: \e<C-'> 713 URxvt.keysym.C-apostrophe: \033<C-'>
517 URxvt*keysym.C-slash: \e<C-/> 714 URxvt.keysym.C-slash: \033<C-/>
518 URxvt*keysym.C-semicolon: \e<C-;> 715 URxvt.keysym.C-semicolon: \033<C-;>
519 URxvt*keysym.C-grave: \e<C-`> 716 URxvt.keysym.C-grave: \033<C-`>
520 URxvt*keysym.C-comma: \e<C-,> 717 URxvt.keysym.C-comma: \033<C-,>
521 URxvt*keysym.C-period: \e<C-.> 718 URxvt.keysym.C-period: \033<C-.>
522 URxvt*keysym.C-0x60: \e<C-`> 719 URxvt.keysym.C-0x60: \033<C-`>
523 URxvt*keysym.C-Tab: \e<C-Tab> 720 URxvt.keysym.C-Tab: \033<C-Tab>
524 URxvt*keysym.C-Return: \e<C-Return> 721 URxvt.keysym.C-Return: \033<C-Return>
525 URxvt*keysym.S-Return: \e<S-Return> 722 URxvt.keysym.S-Return: \033<S-Return>
526 URxvt*keysym.S-space: \e<S-Space> 723 URxvt.keysym.S-space: \033<S-Space>
527 URxvt*keysym.M-Up: \e<M-Up> 724 URxvt.keysym.M-Up: \033<M-Up>
528 URxvt*keysym.M-Down: \e<M-Down> 725 URxvt.keysym.M-Down: \033<M-Down>
529 URxvt*keysym.M-Left: \e<M-Left> 726 URxvt.keysym.M-Left: \033<M-Left>
530 URxvt*keysym.M-Right: \e<M-Right> 727 URxvt.keysym.M-Right: \033<M-Right>
531 URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.> 728 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
532 URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.> 729 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
533 URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007 730 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
731
732 See some more examples in the documentation for the keysym resource.
534 733
535 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 734 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 735 do I make use of them? For example, the Sun Keyboard type 4 has the
537 following mappings that rxvt-unicode doesn't recognize. 736 following mappings that rxvt-unicode doesn't recognize.
538 KP_Insert == Insert 737 KP_Insert == Insert
… …
544 743
545 Rather than have rxvt-unicode try to accommodate all the various 744 Rather than have rxvt-unicode try to accommodate all the various
546 possible keyboard mappings, it is better to use `xmodmap' to remap 745 possible keyboard mappings, it is better to use `xmodmap' to remap
547 the keys as required for your particular machine. 746 the keys as required for your particular machine.
548 747
549 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 748 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
550 need this to decide about setting colors etc. 749 I need this to decide about setting colors etc.
551 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 750 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, 751 can check and see if that is set. Note that several programs, JED,
553 slrn, Midnight Commander automatically check this variable to decide 752 slrn, Midnight Commander automatically check this variable to decide
554 whether or not to use color. 753 whether or not to use color.
555 754
… …
586 Before sending me mail, you could go to IRC: "irc.freenode.net", 785 Before sending me mail, you could go to IRC: "irc.freenode.net",
587 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might 786 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might
588 be interested in learning about new and exciting problems (but not 787 be interested in learning about new and exciting problems (but not
589 FAQs :). 788 FAQs :).
590 789
591SYNOPSIS 790RXVT 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 791DESCRIPTION
602 The rest of this document describes various technical aspects of 792 The rest of this document describes various technical aspects of
603 rxvt-unicode. First the description of supported command sequences, 793 rxvt-unicode. First the description of supported command sequences,
604 followed by menu and pixmap support and last by a description of all 794 followed by menu and pixmap support and last by a description of all
605 features selectable at "configure" time. 795 features selectable at "configure" time.
606 796
607RXVT TECHNICAL REFERENCE
608Definitions 797Definitions
609 "c" The literal character c. 798 "c" The literal character c.
610 799
611 "C" A single (required) character. 800 "C" A single (required) character.
612 801
… …
697 "ESC O" 886 "ESC O"
698 Single Shift Select of G3 Character Set (SS3): affects next 887 Single Shift Select of G3 Character Set (SS3): affects next
699 character only *unimplemented* 888 character only *unimplemented*
700 889
701 "ESC Z" 890 "ESC Z"
702 Obsolete form of returns: "ESC[?1;2C" *rxvt-unicode compile-time 891 Obsolete form of returns: "ESC [ ? 1 ; 2 C" *rxvt-unicode
703 option* 892 compile-time option*
704 893
705 "ESC c" 894 "ESC c"
706 Full reset (RIS) 895 Full reset (RIS)
707 896
708 "ESC n" 897 "ESC n"
709 Invoke the G2 Character Set (LS2) 898 Invoke the G2 Character Set (LS2)
710 899
711 "ESC o" 900 "ESC o"
712 Invoke the G3 Character Set (LS3) 901 Invoke the G3 Character Set (LS3)
713 902
714 "ESC" ( C> 903 "ESC ( C"
715 Designate G0 Character Set (ISO 2022), see below for values of "C". 904 Designate G0 Character Set (ISO 2022), see below for values of "C".
716 905
717 "ESC" ) C> 906 "ESC ) C"
718 Designate G1 Character Set (ISO 2022), see below for values of "C". 907 Designate G1 Character Set (ISO 2022), see below for values of "C".
719 908
720 "ESC * C" 909 "ESC * C"
721 Designate G2 Character Set (ISO 2022), see below for values of "C". 910 Designate G2 Character Set (ISO 2022), see below for values of "C".
722 911
… …
815 "ESC [ Ps a" 1004 "ESC [ Ps a"
816 See "ESC [ Ps C" 1005 See "ESC [ Ps C"
817 1006
818 "ESC [ Ps c" 1007 "ESC [ Ps c"
819 Send Device Attributes (DA) "Ps = 0" (or omitted): request 1008 Send Device Attributes (DA) "Ps = 0" (or omitted): request
820 attributes from terminal returns: "ESC[?1;2c" (``I am a VT100 with 1009 attributes from terminal returns: "ESC [ ? 1 ; 2 c" (``I am a VT100
821 Advanced Video Option'') 1010 with Advanced Video Option'')
822 1011
823 "ESC [ Ps d" 1012 "ESC [ Ps d"
824 Cursor to Line "Ps" (VPA) 1013 Cursor to Line "Ps" (VPA)
825 1014
826 "ESC [ Ps e" 1015 "ESC [ Ps e"
… …
900 (CSR) 1089 (CSR)
901 1090
902 "ESC [ s" 1091 "ESC [ s"
903 Save Cursor (SC) 1092 Save Cursor (SC)
904 1093
1094 "ESC [ Ps;Pt t"
1095 Window Operations
1096
1097 Ps = 1 Deiconify (map) window
1098 Ps = 2 Iconify window
1099 Ps = 3 ESC [ 3 ; X ; Y t Move window to (X|Y)
1100 Ps = 4 ESC [ 4 ; H ; W t Resize to WxH pixels
1101 Ps = 5 Raise window
1102 Ps = 6 Lower window
1103 Ps = 7 Refresh screen once
1104 Ps = 8 ESC [ 8 ; R ; C t Resize to R rows and C columns
1105 Ps = 11 Report window state (responds with Ps = 1 or Ps = 2)
1106 Ps = 13 Report window position (responds with Ps = 3)
1107 Ps = 14 Report window pixel size (responds with Ps = 4)
1108 Ps = 18 Report window text size (responds with Ps = 7)
1109 Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9
1110 Ps = 20 Reports icon label (ESC ] L NAME \234)
1111 Ps = 21 Reports window title (ESC ] l NAME \234)
1112 Ps = 24.. Set window height to Ps rows
1113
1114 "ESC [ u"
1115 Restore Cursor
1116
905 "ESC [ Ps x" 1117 "ESC [ Ps x"
906 Request Terminal Parameters (DECREQTPARM) 1118 Request Terminal Parameters (DECREQTPARM)
907
908 "ESC [ u"
909 Restore Cursor
910 1119
911 1120
912 1121
913DEC Private Modes 1122DEC Private Modes
914 "ESC [ ? Pm h" 1123 "ESC [ ? Pm h"
… …
1056 Ps = 13 Change colour of mouse foreground to Pt 1265 Ps = 13 Change colour of mouse foreground to Pt
1057 Ps = 17 Change colour of highlight characters to Pt 1266 Ps = 17 Change colour of highlight characters to Pt
1058 Ps = 18 Change colour of bold characters to Pt 1267 Ps = 18 Change colour of bold characters to Pt
1059 Ps = 19 Change colour of underlined characters to Pt 1268 Ps = 19 Change colour of underlined characters to Pt
1060 Ps = 20 Change default background to Pt 1269 Ps = 20 Change default background to Pt
1061 Ps = 39 Change default foreground colour to Pt rxvt compile-time option 1270 Ps = 39 Change default foreground colour to Pt.
1062 Ps = 46 Change Log File to Pt unimplemented 1271 Ps = 46 Change Log File to Pt unimplemented
1063 Ps = 49 Change default background colour to Pt rxvt compile-time option 1272 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 1273 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 1274 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) 1275 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) 1276 Ps = 703 Menubar command Pt (Compile menubar).
1068 Ps = 704 Change colour of italic characters to Pt 1277 Ps = 704 Change colour of italic characters to Pt
1069 Ps = 705 Change background pixmap tint colour to Pt 1278 Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1070 Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1279 Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
1071 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. 1280 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. 1281 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. 1282 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1283 Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1284 Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1074 1285
1075 1286
1076 1287
1077menuBar 1288menuBar
1078 The exact syntax used is *almost* solidified. In the menus, DON'T try to 1289 The exact syntax used is *almost* solidified. In the menus, DON'T try to
… …
1115 [menu] 1326 [menu]
1116 access the current menuBar for alteration 1327 access the current menuBar for alteration
1117 1328
1118 [title:+*string*] 1329 [title:+*string*]
1119 set the current menuBar's title to *string*, which may contain the 1330 set the current menuBar's title to *string*, which may contain the
1120 following format specifiers: %% : literal % character %n : rxvt name 1331 following format specifiers:
1121 (as per the -name command-line option) %v : rxvt version 1332
1333 B<%n> rxvt name (as per the B<-name> command-line option)
1334 B<%v> rxvt version
1335 B<%%> literal B<%> character
1122 1336
1123 [done] 1337 [done]
1124 set menuBar access as readonly. End-of-file tag for [read:+*file*] 1338 set menuBar access as readonly. End-of-file tag for [read:+*file*]
1125 operations. 1339 operations.
1126 1340
… …
1230 1444
1231 As a convenience for the many Emacs-type editors, *action* may start 1445 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 1446 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if
1233 missed from M-x commands. 1447 missed from M-x commands.
1234 1448
1235 As a convenience for issuing XTerm ESC] sequences from a menubar (or 1449 As a convenience for issuing XTerm ESC ] sequences from a menubar (or
1236 quick arrow), a BEL (^G) will be appended if needed. 1450 quick arrow), a BEL (^G) will be appended if needed.
1237 1451
1238 For example, 1452 For example,
1239 M-xapropos is equivalent to \Exapropos\r 1453 M-xapropos is equivalent to \Exapropos\r
1240 1454
… …
1540 XK_KP_8 8 ESC O x 1754 XK_KP_8 8 ESC O x
1541 XK_KP_9 9 ESC O y 1755 XK_KP_9 9 ESC O y
1542 1756
1543CONFIGURE OPTIONS 1757CONFIGURE OPTIONS
1544 General hint: if you get compile errors, then likely your configuration 1758 General hint: if you get compile errors, then likely your configuration
1545 hasn't been tested well. Either try with --enable-everything or use the 1759 hasn't been tested well. Either try with "--enable-everything" or use
1546 ./reconf script as a base for experiments. ./reconf is used by myself, 1760 the ./reconf script as a base for experiments. ./reconf is used by
1547 so it should generally be a working config. Of course, you should always 1761 myself, so it should generally be a working config. Of course, you
1548 report when a combination doesn't work, so it can be fixed. Marc Lehmann 1762 should always report when a combination doesn't work, so it can be
1549 <rxvt@schmorp.de>. 1763 fixed. Marc Lehmann <rxvt@schmorp.de>.
1764
1765 All
1550 1766
1551 --enable-everything 1767 --enable-everything
1552 Add support for all non-multichoice options listed in "./configure 1768 Add (or remove) support for all non-multichoice options listed in
1553 --help". Note that unlike other enable options this is order 1769 "./configure --help".
1554 dependant. You can specify this and then disable options which this
1555 enables by *following* this with the appropriate commands.
1556 1770
1557 --enable-xft 1771 You can specify this and then disable options you do not like by
1772 *following* this with the appropriate "--disable-..." arguments, or
1773 you can start with a minimal configuration by specifying
1774 "--disable-everything" and than adding just the "--enable-..."
1775 arguments you want.
1776
1777 --enable-xft (default: enabled)
1558 Add support for Xft (anti-aliases, among others) fonts. Xft fonts 1778 Add support for Xft (anti-aliases, among others) fonts. Xft fonts
1559 are slower and require lots of memory, but as long as you don't use 1779 are slower and require lots of memory, but as long as you don't use
1560 them, you don't pay for them. 1780 them, you don't pay for them.
1561 1781
1562 --enable-font-styles 1782 --enable-font-styles (default: on)
1563 Add support for bold, *italic* and *bold italic* font styles. The 1783 Add support for bold, *italic* and *bold italic* font styles. The
1564 fonts can be set manually or automatically. 1784 fonts can be set manually or automatically.
1565 1785
1566 --with-codesets=NAME,... 1786 --with-codesets=NAME,... (default: all)
1567 Compile in support for additional codeset (encoding) groups (eu, vn 1787 Compile in support for additional codeset (encoding) groups ("eu",
1568 are always compiled in, which includes most 8-bit character sets). 1788 "vn" are always compiled in, which includes most 8-bit character
1569 These codeset tables are currently only used for driving X11 core 1789 sets). These codeset tables are used for driving X11 core fonts,
1570 fonts, they are not required for Xft fonts. Compiling them in will 1790 they are not required for Xft fonts, although having them compiled
1571 make your binary bigger (together about 700kB), but it doesn't 1791 in lets rxvt-unicode choose replacement fonts more intelligently.
1572 increase memory usage unless you use an X11 font requiring one of 1792 Compiling them in will make your binary bigger (all of together cost
1573 these encodings. 1793 about 700kB), but it doesn't increase memory usage unless you use a
1794 font requiring one of these encodings.
1574 1795
1575 all all available codeset groups 1796 all all available codeset groups
1576 zh common chinese encodings 1797 zh common chinese encodings
1577 zh_ext rarely used but very big chinese encodigs 1798 zh_ext rarely used but very big chinese encodigs
1578 jp common japanese encodings 1799 jp common japanese encodings
1579 jp_ext rarely used but big japanese encodings 1800 jp_ext rarely used but big japanese encodings
1580 kr korean encodings 1801 kr korean encodings
1581 1802
1582 --enable-xim 1803 --enable-xim (default: on)
1583 Add support for XIM (X Input Method) protocol. This allows using 1804 Add support for XIM (X Input Method) protocol. This allows using
1584 alternative input methods (e.g. kinput2) and will also correctly set 1805 alternative input methods (e.g. kinput2) and will also correctly set
1585 up the input for people using dead keys or compose keys. 1806 up the input for people using dead keys or compose keys.
1586 1807
1587 --enable-unicode3 1808 --enable-unicode3 (default: off)
1588 Enable direct support for displaying unicode codepoints above 65535 1809 Enable direct support for displaying unicode codepoints above 65535
1589 (the basic multilingual page). This increases storage requirements 1810 (the basic multilingual page). This increases storage requirements
1590 per character from 2 to 4 bytes. X11 fonts do not yet support these 1811 per character from 2 to 4 bytes. X11 fonts do not yet support these
1591 extra characters, but Xft does. 1812 extra characters, but Xft does.
1592 1813
… …
1594 even without this flag, but the number of such characters is limited 1815 even without this flag, but the number of such characters is limited
1595 to a view thousand (shared with combining characters, see next 1816 to a view thousand (shared with combining characters, see next
1596 switch), and right now rxvt-unicode cannot display them 1817 switch), and right now rxvt-unicode cannot display them
1597 (input/output and cut&paste still work, though). 1818 (input/output and cut&paste still work, though).
1598 1819
1599 --enable-combining 1820 --enable-combining (default: on)
1600 Enable automatic composition of combining characters into composite 1821 Enable automatic composition of combining characters into composite
1601 characters. This is required for proper viewing of text where 1822 characters. This is required for proper viewing of text where
1602 accents are encoded as seperate unicode characters. This is done by 1823 accents are encoded as seperate unicode characters. This is done by
1603 using precomposited characters when available or creating new 1824 using precomposited characters when available or creating new
1604 pseudo-characters when no precomposed form exists. 1825 pseudo-characters when no precomposed form exists.
1605 1826
1606 Without --enable-unicode3, the number of additional precomposed 1827 Without --enable-unicode3, the number of additional precomposed
1607 characters is rather limited (2048, if this is full, rxvt will use 1828 characters is rather limited (2048, if this is full, rxvt-unicode
1608 the private use area, extending the number of combinations to 8448). 1829 will use the private use area, extending the number of combinations
1609 With --enable-unicode3, no practical limit exists. This will also 1830 to 8448). With --enable-unicode3, no practical limit exists.
1610 enable storage of characters >65535. 1831
1832 This option will also enable storage (but not display) of characters
1833 beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1611 1834
1612 The combining table also contains entries for arabic presentation 1835 The combining table also contains entries for arabic presentation
1613 forms, but these are not currently used. Bug me if you want these to 1836 forms, but these are not currently used. Bug me if you want these to
1614 be used. 1837 be used (and tell me how these are to be used...).
1615 1838
1616 --enable-fallback(=CLASS) 1839 --enable-fallback(=CLASS) (default: Rxvt)
1617 When reading resource settings, also read settings for class CLASS 1840 When reading resource settings, also read settings for class CLASS.
1618 (default: Rxvt). To disable resource fallback use 1841 To disable resource fallback use --disable-fallback.
1619 --disable-fallback.
1620 1842
1621 --with-res-name=NAME 1843 --with-res-name=NAME (default: urxvt)
1622 Use the given name (default: urxvt) as default application name when 1844 Use the given name as default application name when reading
1623 reading resources. Specify --with-res-name=rxvt to replace rxvt. 1845 resources. Specify --with-res-name=rxvt to replace rxvt.
1624 1846
1625 --with-res-class=CLASS 1847 --with-res-class=CLASS /default: URxvt)
1626 Use the given class (default: URxvt) as default application class 1848 Use the given class as default application class when reading
1627 when reading resources. Specify --with-res-class=Rxvt to replace 1849 resources. Specify --with-res-class=Rxvt to replace rxvt.
1628 rxvt.
1629 1850
1630 --enable-utmp 1851 --enable-utmp (default: on)
1631 Write user and tty to utmp file (used by programs like w) at start 1852 Write user and tty to utmp file (used by programs like w) at start
1632 of rxvt execution and delete information when rxvt exits. 1853 of rxvt execution and delete information when rxvt exits.
1633 1854
1634 --enable-wtmp 1855 --enable-wtmp (default: on)
1635 Write user and tty to wtmp file (used by programs like last) at 1856 Write user and tty to wtmp file (used by programs like last) at
1636 start of rxvt execution and write logout when rxvt exits. This 1857 start of rxvt execution and write logout when rxvt exits. This
1637 option requires --enable-utmp to also be specified. 1858 option requires --enable-utmp to also be specified.
1638 1859
1639 --enable-lastlog 1860 --enable-lastlog (default: on)
1640 Write user and tty to lastlog file (used by programs like lastlogin) 1861 Write user and tty to lastlog file (used by programs like lastlogin)
1641 at start of rxvt execution. This option requires --enable-utmp to 1862 at start of rxvt execution. This option requires --enable-utmp to
1642 also be specified. 1863 also be specified.
1643 1864
1644 --enable-xpm-background 1865 --enable-xpm-background (default: off)
1645 Add support for XPM background pixmaps. 1866 Add support for XPM background pixmaps.
1646 1867
1647 --enable-transparency 1868 --enable-transparency (default: off)
1648 Add support for inheriting parent backgrounds thus giving a fake 1869 Add support for inheriting parent backgrounds thus giving a fake
1649 transparency to the term. 1870 transparency to the term.
1650 1871
1651 --enable-fading 1872 --enable-fading (default: on)
1652 Add support for fading the text when focus is lost. 1873 Add support for fading the text when focus is lost (requires
1874 "--enable-transparency").
1653 1875
1654 --enable-tinting 1876 --enable-tinting (default: on)
1655 Add support for tinting of transparent backgrounds. 1877 Add support for tinting of transparent backgrounds (requires
1878 "--enable-transparency").
1656 1879
1657 --enable-menubar 1880 --enable-menubar (default: off)
1658 Add support for our menu bar system (this interacts badly with 1881 Add support for our menu bar system (this interacts badly with
1659 dynamic locale switching currently). 1882 dynamic locale switching currently).
1660 1883
1661 --enable-rxvt-scroll 1884 --enable-rxvt-scroll (default: on)
1662 Add support for the original rxvt scrollbar. 1885 Add support for the original rxvt scrollbar.
1663 1886
1664 --enable-next-scroll 1887 --enable-next-scroll (default: on)
1665 Add support for a NeXT-like scrollbar. 1888 Add support for a NeXT-like scrollbar.
1666 1889
1667 --enable-xterm-scroll 1890 --enable-xterm-scroll (default: on)
1668 Add support for an Xterm-like scrollbar. 1891 Add support for an Xterm-like scrollbar.
1669 1892
1670 --enable-plain-scroll 1893 --enable-plain-scroll (default: on)
1671 Add support for a very unobtrusive, plain-looking scrollbar that is 1894 Add support for a very unobtrusive, plain-looking scrollbar that is
1672 the favourite of the rxvt-unicode author, having used it for many 1895 the favourite of the rxvt-unicode author, having used it for many
1673 years. 1896 years.
1674 1897
1675 --enable-half-shadow 1898 --enable-half-shadow (default: off)
1676 Make shadows on the scrollbar only half the normal width & height. 1899 Make shadows on the scrollbar only half the normal width & height.
1677 only applicable to rxvt scrollbars. 1900 only applicable to rxvt scrollbars.
1678 1901
1679 --enable-ttygid 1902 --enable-ttygid (default: off)
1680 Change tty device setting to group "tty" - only use this if your 1903 Change tty device setting to group "tty" - only use this if your
1681 system uses this type of security. 1904 system uses this type of security.
1682 1905
1683 --disable-backspace-key 1906 --disable-backspace-key
1684 Disable any handling of the backspace key by us - let the X server 1907 Removes any handling of the backspace key by us - let the X server
1685 do it. 1908 do it.
1686 1909
1687 --disable-delete-key 1910 --disable-delete-key
1688 Disable any handling of the delete key by us - let the X server do 1911 Removes any handling of the delete key by us - let the X server do
1689 it. 1912 it.
1690 1913
1691 --disable-resources 1914 --disable-resources
1692 Remove all resources checking. 1915 Removes any support for resource checking.
1693 1916
1694 --enable-xgetdefault 1917 --enable-xgetdefault
1695 Make resources checking via XGetDefault() instead of our small 1918 Make resources checking via XGetDefault() instead of our small
1696 version which only checks ~/.Xdefaults, or if that doesn't exist 1919 version which only checks ~/.Xdefaults, or if that doesn't exist
1697 then ~/.Xresources. 1920 then ~/.Xresources.
1698 1921
1699 --enable-strings 1922 Please note that nowadays, things like XIM will automatically pull
1923 in and use the full X resource manager, so the overhead of using it
1924 might be very small, if nonexistant.
1925
1926 --enable-strings (default: off)
1700 Add support for our possibly faster memset() function and other 1927 Add support for our possibly faster memset() function and other
1701 various routines, overriding your system's versions which may have 1928 various routines, overriding your system's versions which may have
1702 been hand-crafted in assembly or may require extra libraries to link 1929 been hand-crafted in assembly or may require extra libraries to link
1703 in. (this breaks ANSI-C rules and has problems on many GNU/Linux 1930 in. (this breaks ANSI-C rules and has problems on many GNU/Linux
1704 systems). 1931 systems).
1705 1932
1706 --disable-swapscreen 1933 --disable-swapscreen
1707 Remove support for swap screen. 1934 Remove support for secondary/swap screen.
1708 1935
1709 --enable-frills 1936 --enable-frills (default: on)
1710 Add support for many small features that are not essential but nice 1937 Add support for many small features that are not essential but nice
1711 to have. Normally you want this, but for very small binaries you may 1938 to have. Normally you want this, but for very small binaries you may
1712 want to disable this. 1939 want to disable this.
1713 1940
1714 A non-exhaustive list of features enabled by "--enable-frills" 1941 A non-exhaustive list of features enabled by "--enable-frills"
1715 (possibly in combination with other switches) is: 1942 (possibly in combination with other switches) is:
1716 1943
1717 MWM-hints 1944 MWM-hints
1945 EWMH-hints (pid, utf8 names) and protocols (ping)
1718 seperate underline colour 1946 seperate underline colour
1719 settable border widths and borderless switch 1947 settable border widths and borderless switch
1720 settable extra linespacing 1948 settable extra linespacing
1721 extra window properties (e.g. UTF-8 window names and PID)
1722 iso-14755-2 and -3, and visual feedback 1949 iso-14755-2 and -3, and visual feedback
1723 backindex and forwardindex escape sequence 1950 backindex and forwardindex escape sequence
1724 window op and locale change escape sequences 1951 window op and some xterm/OSC escape sequences
1725 tripleclickwords 1952 tripleclickwords
1726 settable insecure mode 1953 settable insecure mode
1954 keysym remapping support
1955 cursor blinking and underline cursor
1956 -embed, -pty-fd and -hold options
1727 1957
1728 --enable-iso14755 1958 --enable-iso14755 (default: on)
1729 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). 1959 Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
1730 Basic support (section 5.1) is enabled by "--enable-frills", while 1960 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. 1961 support for 5.2, 5.3 and 5.4 is enabled with this switch.
1732 1962
1733 --enable-keepscrolling 1963 --enable-keepscrolling (default: on)
1734 Add support for continual scrolling of the display when you hold the 1964 Add support for continual scrolling of the display when you hold the
1735 mouse button down on a scrollbar arrow. 1965 mouse button down on a scrollbar arrow.
1736 1966
1737 --enable-mousewheel 1967 --enable-mousewheel (default: on)
1738 Add support for scrolling via mouse wheel or buttons 4 & 5. 1968 Add support for scrolling via mouse wheel or buttons 4 & 5.
1739 1969
1740 --enable-slipwheeling 1970 --enable-slipwheeling (default: on)
1741 Add support for continual scrolling (using the mouse wheel as an 1971 Add support for continual scrolling (using the mouse wheel as an
1742 accelerator) while the control key is held down. This option 1972 accelerator) while the control key is held down. This option
1743 requires --enable-mousewheel to also be specified. 1973 requires --enable-mousewheel to also be specified.
1744 1974
1745 --disable-new-selection 1975 --disable-new-selection
1746 Remove support for mouse selection style like that of xterm. 1976 Remove support for mouse selection style like that of xterm.
1747 1977
1748 --enable-dmalloc 1978 --enable-dmalloc (default: off)
1749 Use Gray Watson's malloc - which is good for debugging See 1979 Use Gray Watson's malloc - which is good for debugging See
1750 http://www.letters.com/dmalloc/ for details If you use either this 1980 http://www.letters.com/dmalloc/ for details If you use either this
1751 or the next option, you may need to edit src/Makefile after 1981 or the next option, you may need to edit src/Makefile after
1752 compiling to point DINCLUDE and DLIB to the right places. 1982 compiling to point DINCLUDE and DLIB to the right places.
1753 1983
1754 You can only use either this option and the following (should you 1984 You can only use either this option and the following (should you
1755 use either) . 1985 use either) .
1756 1986
1757 --enable-dlmalloc 1987 --enable-dlmalloc (default: off)
1758 Use Doug Lea's malloc - which is good for a production version See 1988 Use Doug Lea's malloc - which is good for a production version See
1759 <http://g.oswego.edu/dl/html/malloc.html> for details. 1989 <http://g.oswego.edu/dl/html/malloc.html> for details.
1760 1990
1761 --enable-smart-resize 1991 --enable-smart-resize (default: on)
1762 Add smart growth/shrink behaviour when changing font size via from 1992 Add smart growth/shrink behaviour when changing font size via hot
1763 hot keys. This should keep in a fixed position the rxvt corner which 1993 keys. This should keep the window corner which is closest to a
1764 is closest to a corner of the screen. 1994 corner of the screen in a fixed position.
1765 1995
1766 --enable-cursor-blink
1767 Add support for a blinking cursor.
1768
1769 --enable-pointer-blank 1996 --enable-pointer-blank (default: on)
1770 Add support to have the pointer disappear when typing or inactive. 1997 Add support to have the pointer disappear when typing or inactive.
1771 1998
1772 --with-name=NAME 1999 --with-name=NAME (default: urxvt)
1773 Set the basename for the installed binaries (default: urxvt, 2000 Set the basename for the installed binaries, resulting in "urxvt",
1774 resulting in urxvt, urxvtd etc.). Specify --with-name=rxvt to 2001 "urxvtd" etc.). Specify "--with-name=rxvt" to replace with "rxvt".
1775 replace rxvt.
1776 2002
1777 --with-term=NAME 2003 --with-term=NAME (default: rxvt-unicode)
1778 Change the environmental variable for the terminal to NAME (default 2004 Change the environmental variable for the terminal to NAME.
1779 "rxvt")
1780 2005
1781 --with-terminfo=PATH 2006 --with-terminfo=PATH
1782 Change the environmental variable for the path to the terminfo tree 2007 Change the environmental variable for the path to the terminfo tree
1783 to PATH. 2008 to PATH.
1784 2009

Diff Legend

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