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

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents):
Revision 1.1 by root, Tue Jan 11 02:24:59 2005 UTC vs.
Revision 1.40 by root, Thu Jan 12 05:37:34 2006 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 I don't like the new selection/popups/hotkeys/perl, how do I
24 change/disable it?
25 You can disable the perl extension completely by setting the
26 perl-ext-common resource to the empty string, which also keeps
27 rxvt-unicode from initialising perl, saving memory.
28
29 If you only want to disable specific features, you first have to
30 identify which perl extension is responsible. For this, read the
31 section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For
32 example, to disable the selection-popup and option-popup, specify
33 this perl-ext-common resource:
34
35 URxvt.perl-ext-common: default,-selection-popup,-option-popup
36
37 This will keep the default extensions, but disable the two popup
38 extensions. Some extensions can also be configured, for example,
39 scrollback search mode is triggered by M-s. You can move it to any
40 other combination either by setting the searchable-scrollback
41 resource:
42
43 URxvt.searchable-scrollback: CM-s
44
45 Isn't rxvt supposed to be small? Don't all those features bloat?
46 I often get asked about this, and I think, no, they didn't cause
47 extra bloat. If you compare a minimal rxvt and a minimal urxvt, you
48 can see that the urxvt binary is larger (due to some encoding tables
49 always being compiled in), but it actually uses less memory (RSS)
50 after startup. Even with "--disable-everything", this comparison is
51 a bit unfair, as many features unique to urxvt (locale, encoding
52 conversion, iso14755 etc.) are already in use in this mode.
53
54 text data bss drs rss filename
55 98398 1664 24 15695 1824 rxvt --disable-everything
56 188985 9048 66616 18222 1788 urxvt --disable-everything
57
58 When you "--enable-everything" (which _is_ unfair, as this involves
59 xft and full locale/XIM support which are quite bloaty inside libX11
60 and my libc), the two diverge, but not unreasnobaly so.
61
62 text data bss drs rss filename
63 163431 2152 24 20123 2060 rxvt --enable-everything
64 1035683 49680 66648 29096 3680 urxvt --enable-everything
65
66 The very large size of the text section is explained by the
67 east-asian encoding tables, which, if unused, take up disk space but
68 nothing else and can be compiled out unless you rely on X11 core
69 fonts that use those encodings. The BSS size comes from the 64k
70 emergency buffer that my c++ compiler allocates (but of course
71 doesn't use unless you are out of memory). Also, using an xft font
72 instead of a core font immediately adds a few megabytes of RSS. Xft
73 indeed is responsible for a lot of RSS even when not used.
74
75 Of course, due to every character using two or four bytes instead of
76 one, a large scrollback buffer will ultimately make rxvt-unicode use
77 more memory.
78
79 Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k),
80 this still fares rather well. And compared to some monsters like
81 gnome-terminal (21152k + extra 4204k in separate processes) or
82 konsole (22200k + extra 43180k in daemons that stay around after
83 exit, plus half a minute of startup time, including the hundreds of
84 warnings it spits out), it fares extremely well *g*.
85
86 Why C++, isn't that unportable/bloated/uncool?
87 Is this a question? :) It comes up very often. The simple answer is:
88 I had to write it, and C++ allowed me to write and maintain it in a
89 fraction of the time and effort (which is a scarce resource for me).
90 Put even shorter: It simply wouldn't exist without C++.
91
92 My personal stance on this is that C++ is less portable than C, but
93 in the case of rxvt-unicode this hardly matters, as its portability
94 limits are defined by things like X11, pseudo terminals, locale
95 support and unix domain sockets, which are all less portable than
96 C++ itself.
97
98 Regarding the bloat, see the above question: It's easy to write
99 programs in C that use gobs of memory, an certainly possible to
100 write programs in C++ that don't. C++ also often comes with large
101 libraries, but this is not necessarily the case with GCC. Here is
102 what rxvt links against on my system with a minimal config:
103
104 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
105 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
106 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
107 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
108
109 And here is rxvt-unicode:
110
111 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
112 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
113 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
114 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
115 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
116
117 No large bloated libraries (of course, none were linked in
118 statically), except maybe libX11 :)
119
120 Does it support tabs, can I have a tabbed rxvt-unicode?
121 rxvt-unicode does not directly support tabs. It will work fine with
122 tabbing functionality of many window managers or similar tabbing
123 programs, and its embedding-features allow it to be embedded into
124 other programs, as witnessed by doc/rxvt-tabbed or the upcoming
125 "Gtk2::URxvt" perl module, which features a tabbed urxvt (murxvt)
126 terminal as an example embedding application.
127
5 How do I know which rxvt-unicode version I'm using? 128 How do I know which rxvt-unicode version I'm using?
6 The version number is displayed with the usage (-h). Also the escape 129 The version number is displayed with the usage (-h). Also the escape
7 sequence "ESC[8n" sets the window title to the version number. 130 sequence "ESC [ 8 n" sets the window title to the version number.
131 When using the rxvtc client, the version displayed is that of the
132 daemon.
133
134 I am using Debian GNU/Linux and have a problem...
135 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
136 patches that considerably change the behaviour of rxvt-unicode.
137 Before reporting a bug to the original rxvt-unicode author please
138 download and install the genuine version
139 (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
140 problem. If you cannot, chances are that the problems are specific
141 to Debian GNU/Linux, in which case it should be reported via the
142 Debian Bug Tracking System (use "reportbug" to report the bug).
143
144 For other problems that also affect the Debian package, you can and
145 probably should use the Debian BTS, too, because, after all, it's
146 also a bug in the Debian version and it serves as a reminder for
147 other users that might encounter the same issue.
148
149 I am maintaining rxvt-unicode for distribution/OS XXX, any
150 recommendation?
151 You should build one binary with the default options. configure now
152 enables most useful options, and the trend goes to making them
153 runtime-switchable, too, so there is usually no drawback to enbaling
154 them, except higher disk and possibly memory usage. The perl
155 interpreter should be enabled, as important functionality (menus,
156 selection, likely more in the future) depends on it.
157
158 You should not overwrite the "perl-ext-common" snd "perl-ext"
159 resources system-wide (except maybe with "defaults"). This will
160 result in useful behaviour. If your distribution aims at low memory,
161 add an empty "perl-ext-common" resource to the app-defaults file.
162 This will keep the perl interpreter disabled until the user enables
163 it.
164
165 If you can/want build more binaries, I recommend building a minimal
166 one with "--disable-everything" (very useful) and a maximal one with
167 "--enable-everything" (less useful, it will be very big due to a lot
168 of encodings built-in that increase download times and are rarely
169 used).
170
171 I need to make it setuid/setgid to support utmp/ptys on my OS, is this
172 safe?
173 Likely not. While I honestly try to make it secure, and am probably
174 not bad at it, I think it is simply unreasonable to expect all of
175 freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode
176 itself to all be secure. Also, rxvt-unicode disables some options
177 when it detects that it runs setuid or setgid, which is not nice.
178 Besides, with the embedded perl interpreter the possibility for
179 security problems easily multiplies.
180
181 Elevated privileges are only required for utmp and pty operations on
182 some systems (for example, GNU/Linux doesn't need any extra
183 privileges for ptys, but some need it for utmp support). It is
184 planned to mvoe this into a forked handler process, but this is not
185 yet done.
186
187 So, while setuid/setgid operation is supported and not a problem on
188 your typical single-user-no-other-logins unix desktop, always
189 remember that its an awful lot of code, most of which isn't checked
190 for security issues regularly.
8 191
9 When I log-in to another system it tells me about missing terminfo data? 192 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 193 The terminal description used by rxvt-unicode is not as widely
11 available as that for xterm, or even rxvt (for which the same 194 available as that for xterm, or even rxvt (for which the same
12 problem often arises). 195 problem often arises).
… …
24 problems arising, which includes wrong keymapping, less and 207 problems arising, which includes wrong keymapping, less and
25 different colours and some refresh errors in fullscreen 208 different colours and some refresh errors in fullscreen
26 applications. It's a nice quick-and-dirty workaround for rare cases, 209 applications. It's a nice quick-and-dirty workaround for rare cases,
27 though. 210 though.
28 211
29 If you always want to do this you can either recompile rxvt-unicode 212 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: 213 you can either recompile rxvt-unicode with the desired TERM value or
214 use a resource to set it:
31 215
32 URxvt.termName: rxvt 216 URxvt.termName: rxvt
33 217
34 If you don't plan to use rxvt (quite common...) you could also 218 If you don't plan to use rxvt (quite common...) you could also
35 replace the rxvt terminfo file with the rxvt-unicode one. 219 replace the rxvt terminfo file with the rxvt-unicode one.
36 220
221 "tic" outputs some error when compiling the terminfo entry.
222 Most likely it's the empty definition for "enacs=". Just replace it
223 by "enacs=\E[0@" and try again.
224
225 "bash"'s readline does not work correctly under rxvt.
37 I need a termcap file entry. 226 I need a termcap file entry.
227 One reason you might want this is that some distributions or
228 operating systems still compile some programs using the
229 long-obsoleted termcap library (Fedora Core's bash is one example)
230 and rely on a termcap entry for "rxvt-unicode".
231
38 You could use rxvt's termcap entry with resonable results in many 232 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 233 cases. You can also create a termcap entry by using terminfo's
40 infocmp program like this: 234 infocmp program like this:
41 235
42 infocmp -C rxvt-unicode 236 infocmp -C rxvt-unicode
43 237
44 OR you could this termcap entry: 238 Or you could use this termcap entry, generated by the command above:
45 239
46 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 240 rxvt-unicode|rxvt-unicode terminal (X Window System):\
47 :am:bw:eo:km:mi:ms:xn:xo:\ 241 :am:bw:eo:km:mi:ms:xn:xo:\
48 :co#80:it#8:li#24:\ 242 :co#80:it#8:li#24:lm#0:\
49 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 243 :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:\ 244 :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:\ 245 :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:\ 246 :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:\ 247 :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[@:\ 248 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
249 :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:\ 250 :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~:\ 251 :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~:\ 252 :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:\ 253 :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=:\ 254 :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:\ 255 :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:\ 256 :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:\ 257 :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:\ 258 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
64 :vs=\E[?25h: 259 :vs=\E[?25h:
65 260
66 Why does "ls" no longer have coloured output? 261 Why does "ls" no longer have coloured output?
67 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 262 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 263 decide wether a terminal has colour, but uses it's own configuration
… …
87 furthermore fail to even install the "rxvt-unicode" terminfo file, 282 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 283 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 284 log-in to another system it tells me about missing terminfo data? on
90 how to do this). 285 how to do this).
91 286
287 My numerical keypad acts weird and generates differing output?
288 Some Debian GNUL/Linux users seem to have this problem, although no
289 specific details were reported so far. It is possible that this is
290 caused by the wrong "TERM" setting, although the details of wether
291 and how this can happen are unknown, as "TERM=rxvt" should offer a
292 compatible keymap. See the answer to the previous question, and
293 please report if that helped.
294
92 Rxvt-unicode does not seem to understand the selected encoding? 295 Rxvt-unicode does not seem to understand the selected encoding?
93 Unicode does not seem to work? 296 Unicode does not seem to work?
94 If you encounter strange problems like typing an accented character 297 If you encounter strange problems like typing an accented character
95 but getting two unrelated other characters or similar, or if program 298 but getting two unrelated other characters or similar, or if program
96 output is subtly garbled, then you should check your locale 299 output is subtly garbled, then you should check your locale
97 settings. 300 settings.
98 301
99 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 302 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 303 programs. Often rxvt-unicode is started in the "C" locale, while the
101 login script running within the rxvt-unicode window changes the 304 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 305 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
103 not going to work. 306 is not going to work.
104 307
105 The best thing is to fix your startup environment, as you will 308 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 309 likely run into other problems. If nothing works you can try this in
107 your .profile. 310 your .profile.
108 311
109 printf '\e]701;%s\007' "$LC_CTYPE" 312 printf '\e]701;%s\007' "$LC_CTYPE"
110 313
111 If this doesn't work, then maybe you use a "LC_CTYPE" specification 314 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 315 not supported on your systems. Some systems have a "locale" command
113 which displays this. If it displays sth. like: 316 which displays this (also, "perl -e0" can be used to check locale
317 settings, as it will complain loudly if it cannot set the locale).
318 If it displays something like:
114 319
115 locale: Cannot set LC_CTYPE to default locale: ... 320 locale: Cannot set LC_CTYPE to default locale: ...
116 321
117 Then the locale you specified is not supported on your system. 322 Then the locale you specified is not supported on your system.
118 323
… …
126 Chances are that the font you (or the admin/package maintainer of 331 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 332 your system/os) have specified does not cover all the characters you
128 want to display. 333 want to display.
129 334
130 rxvt-unicode makes a best-effort try at finding a replacement font. 335 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. 336 Often the result is fine, but sometimes the chosen font looks
132 Many fonts have totally strange characters that don't resemble the 337 bad/ugly/wrong. Some fonts have totally strange characters that
133 correct glyph at all, and rxvt-unicode lacks the artificial 338 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 339 artificial intelligence to detect that a specific glyph is wrong: it
135 believe the font that the characters it contains indeed look 340 has to believe the font that the characters it claims to contain
136 correct. 341 indeed look correct.
137 342
138 In that case, select a font of your taste and add it to the font 343 In that case, select a font of your taste and add it to the font
139 list, e.g.: 344 list, e.g.:
140 345
141 rxvt -fn basefont,font2,font3... 346 rxvt -fn basefont,font2,font3...
… …
144 font. If the base font does not contain the character, it will go to 349 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 350 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 351 up this search and use less resources within rxvt-unicode and the
147 X-server. 352 X-server.
148 353
149 The only limitation is that all the fonts must not be larger than 354 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, 355 base font, as the base font defines the terminal character cell
151 which must be the same due to the way terminals work. 356 size, which must be the same due to the way terminals work.
152 357
153 Why do some chinese characters look so different than others? 358 Why do some chinese characters look so different than others?
154 This is because there is a difference between script and language -- 359 This is because there is a difference between script and language --
155 rxvt-unicode does not know which language the text that is output 360 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 361 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 362 first sees a japanese/chinese character, it might choose a japanese
158 it. Subsequent japanese characters will take that font. Now, many 363 font for display. Subsequent japanese characters will use that font.
159 chinese characters aren't represented in japanese fonts, so when the 364 Now, many chinese characters aren't represented in japanese fonts,
160 first non-japanese character comes up, rxvt-unicode will look for a 365 so when the first non-japanese character comes up, rxvt-unicode will
161 chinese font -- unfortunately at this point, it will still use the 366 look for a chinese font -- unfortunately at this point, it will
162 japanese font for japanese characters that are also chinese. 367 still use the japanese font for chinese characters that are also in
368 the japanese font.
163 369
164 The workaround is easy: just tag a chinese font at the end of your 370 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 371 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 372 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 373 japanese font first. If you expect more chinese, put a chinese font
168 first. 374 first.
169 375
170 In the future it might be possible to switch preferences at runtime 376 In the future it might be possible to switch language preferences at
171 (the internal data structure has no problem with using different 377 runtime (the internal data structure has no problem with using
172 fonts for the same character at the same time, but no interface for 378 different fonts for the same character at the same time, but no
173 this has been designed yet). 379 interface for this has been designed yet).
380
381 Until then, you might get away with switching fonts at runtime (see
382 "Can I switch the fonts at runtime?" later in this document).
174 383
175 Why does rxvt-unicode sometimes leave pixel droppings? 384 Why does rxvt-unicode sometimes leave pixel droppings?
176 Most fonts were not designed for terminal use, which means that 385 Most fonts were not designed for terminal use, which means that
177 character size varies a lot. A font that is otherwise fine for 386 character size varies a lot. A font that is otherwise fine for
178 terminal use might contain some characters that are simply too wide. 387 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. 401 that doesn't work, you might be forced to use a different font.
193 402
194 All of this is not a problem when using X11 core fonts, as their 403 All of this is not a problem when using X11 core fonts, as their
195 bounding box data is correct. 404 bounding box data is correct.
196 405
406 On Solaris 9, many line-drawing characters are too wide.
407 Seems to be a known bug, read
408 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
409 following ugly workaround to get non-double-wide-characters working:
410
411 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
412
197 My Compose (Multi_key) key is no longer working. 413 My Compose (Multi_key) key is no longer working.
198 The most common causes for this are that either your locale is not 414 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 415 set correctly, or you specified a preeditStyle that is not supported
200 by your input method. For example, if you specified OverTheSpot and 416 by your input method. For example, if you specified OverTheSpot and
201 your input method (e.g. the default input method handling Compose 417 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 428 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 429 other codes, too, such as "Ctrl-Shift-1-d" to type the default
214 telnet escape character and so on. 430 telnet escape character and so on.
215 431
216 How can I keep rxvt-unicode from using reverse video so much? 432 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 433 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 434 settings ("TERM=rxvt-unicode"), which will get rid of most of these
219 sure you have specified colours for italic and bold, as otherwise 435 effects. Then make sure you have specified colours for italic and
220 rxvt-unicode might use reverse video to simulate the effect: 436 bold, as otherwise rxvt-unicode might use reverse video to simulate
437 the effect:
221 438
222 URxvt*colorBD: white 439 URxvt.colorBD: white
223 URxvt*colorIT: green 440 URxvt.colorIT: green
224 441
225 Some programs assume totally weird colours (red instead of blue), how 442 Some programs assume totally weird colours (red instead of blue), how
226 can I fix that? 443 can I fix that?
227 For some unexplainable reason, some programs (i.e. irssi) assume a 444 For some unexplainable reason, some rare programs assume a very
228 very weird colour palette when confronted with a terminal with more 445 weird colour palette when confronted with a terminal with more than
229 than the standard 8 colours (rxvt-unicode supports 88). The right 446 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 447 of course, to fix these programs not to assume non-ISO colours
231 colours without very good reasons. 448 without very good reasons.
232 449
233 In the meantime, you can either edit your "urxvt" terminfo 450 In the meantime, you can either edit your "rxvt-unicode" terminfo
234 definition to only claim 8 colour support or use "TERM=rxvt", which 451 definition to only claim 8 colour support or use "TERM=rxvt", which
235 will fix colours but keep you from using other rxvt-unicode 452 will fix colours but keep you from using other rxvt-unicode
236 features. 453 features.
237 454
238 I am on FreeBSD and rxvt-unicode does not seem to work at all. 455 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__" 458 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
242 requires that wchar_t is represented as unicode. 459 requires that wchar_t is represented as unicode.
243 460
244 As you might have guessed, FreeBSD does neither define this symobl 461 As you might have guessed, FreeBSD does neither define this symobl
245 nor does it support it. Instead, it uses it's own internal 462 nor does it support it. Instead, it uses it's own internal
246 representation of wchar_t. This is, of course, completely legal. 463 representation of wchar_t. This is, of course, completely fine with
464 respect to standards.
247 465
466 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
467 and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
468
248 However, "__STDC_ISO_10646__" is the only sane way to support 469 "__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 470 apps in an OS, as using a locale-dependent (and non-standardized)
250 non-standardized) representation of wchar_t makes it impossible to 471 representation of wchar_t makes it impossible to convert between
251 convert between wchar_t (as used by X11 and your applications) and 472 wchar_t (as used by X11 and your applications) and any other
252 any other encoding without implementing OS-specific-wrappers for 473 encoding without implementing OS-specific-wrappers for each and
253 each and every locale. There simply are no APIs to convert wchar_t 474 every locale. There simply are no APIs to convert wchar_t into
254 into anything except the current locale encoding. 475 anything except the current locale encoding.
255 476
256 Some applications (such as the formidable mlterm) work around this 477 Some applications (such as the formidable mlterm) work around this
257 by carrying their own replacement functions for character set 478 by carrying their own replacement functions for character set
258 handling with them, and either implementing OS-dependent hacks or 479 handling with them, and either implementing OS-dependent hacks or
259 doing multiple conversions (which is slow and unreliable in case the 480 doing multiple conversions (which is slow and unreliable in case the
260 OS implements encodings slightly different than the terminal 481 OS implements encodings slightly different than the terminal
261 emulator). 482 emulator).
262 483
263 The rxvt-unicode author insists that the right way to fix this is in 484 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 485 the system libraries once and for all, instead of forcing every app
265 to carry complete replacements. 486 to carry complete replacements for them :)
487
488 I use Solaris 9 and it doesn't compile/work/etc.
489 Try the diff in doc/solaris9.patch as a base. It fixes the worst
490 problems with "wcwidth" and a compile problem.
491
492 How can I use rxvt-unicode under cygwin?
493 rxvt-unicode should compile and run out of the box on cygwin, using
494 the X11 libraries that come with cygwin. libW11 emulation is no
495 longer supported (and makes no sense, either, as it only supported a
496 single font). I recommend starting the X-server in "-multiwindow" or
497 "-rootless" mode instead, which will result in similar look&feel as
498 the old libW11 emulation.
499
500 At the time of this writing, cygwin didn't seem to support any
501 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
502 likely limited to 8-bit encodings.
266 503
267 How does rxvt-unicode determine the encoding to use? 504 How does rxvt-unicode determine the encoding to use?
268 Is there an option to switch encodings? 505 Is there an option to switch encodings?
269 Unlike some other terminals, rxvt-unicode has no encoding switch, 506 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 507 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
273 510
274 The reasons is that there exists a perfectly fine mechanism for 511 The reasons is that there exists a perfectly fine mechanism for
275 selecting the encoding, doing I/O and (most important) communicating 512 selecting the encoding, doing I/O and (most important) communicating
276 this to all applications so everybody agrees on character properties 513 this to all applications so everybody agrees on character properties
277 such as width and code number. This mechanism is the *locale*. 514 such as width and code number. This mechanism is the *locale*.
515 Applications not using that info will have problems (for example,
516 "xterm" gets the width of characters wrong as it uses it's own,
517 locale-independent table under all locales).
278 518
279 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 519 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
280 All programs doing the same (that is, most) will automatically agree 520 All programs doing the same (that is, most) will automatically agree
281 in the interpretation of characters. 521 in the interpretation of characters.
282 522
… …
290 "language_country.encoding", but other forms (i.e. "de" or "german") 530 "language_country.encoding", but other forms (i.e. "de" or "german")
291 are also common. 531 are also common.
292 532
293 Rxvt-unicode ignores all other locale categories, and except for the 533 Rxvt-unicode ignores all other locale categories, and except for the
294 encoding, ignores country or language-specific settings, i.e. 534 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. 535 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
536 rxvt-unicode.
296 537
297 If you want to use a specific encoding you have to make sure you 538 If you want to use a specific encoding you have to make sure you
298 start rxvt-unicode with the correct "LC_CTYPE" category. 539 start rxvt-unicode with the correct "LC_CTYPE" category.
299 540
300 Can I switch locales at runtime? 541 Can I switch locales at runtime?
301 Yes, using an escape sequence. Try sth. like this, which sets 542 Yes, using an escape sequence. Try something like this, which sets
302 rxvt-unicode's idea of "LC_CTYPE". 543 rxvt-unicode's idea of "LC_CTYPE".
303 544
304 printf '\e]701;%s\007' ja_JP.SJIS 545 printf '\e]701;%s\007' ja_JP.SJIS
305 546
306 See also the previous question. 547 See also the previous answer.
307 548
308 Sometimes this capability is rather handy when you want to work in 549 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 550 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 551 (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: 552 first switches to a locale supported by xjdic and back later:
312 553
313 printf '\e]701;%s\007' ja_JP.SJIS 554 printf '\e]701;%s\007' ja_JP.SJIS
314 xjdic -js 555 xjdic -js
315 printf '\e]701;%s\007' de_DE.UTF-8 556 printf '\e]701;%s\007' de_DE.UTF-8
316 557
558 You can also use xterm's "luit" program, which usually works fine,
559 except for some locales where character width differs between
560 program- and rxvt-unicode-locales.
561
317 Can I switch the fonts at runtime? 562 Can I switch the fonts at runtime?
318 Yes, using an escape sequence. Try sth. like this, which has the 563 Yes, using an escape sequence. Try something like this, which has
319 same effect as using the "-fn" switch, and takes effect immediately: 564 the same effect as using the "-fn" switch, and takes effect
565 immediately:
320 566
321 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 567 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
322 568
323 This is useful if you e.g. work primarily with japanese (and prefer 569 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, 570 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. 573 You can think of this as a kind of manual ISO-2022 switching.
328 574
329 Why do italic characters look as if clipped? 575 Why do italic characters look as if clipped?
330 Many fonts have difficulties with italic characters and hinting. For 576 Many fonts have difficulties with italic characters and hinting. For
331 example, the otherwise very nicely hinted font "xft:Bitstream Vera 577 example, the otherwise very nicely hinted font "xft:Bitstream Vera
332 Sans Mono" completely fails in it's italic face. A workaround is to 578 Sans Mono" completely fails in it's italic face. A workaround might
333 enable freetype autohinting, i.e. like this: 579 be to enable freetype autohinting, i.e. like this:
334 580
335 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 581 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
336 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 582 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
337 583
338 My input method wants <some encoding> but I want UTF-8, what can I do? 584 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 585 You can specify separate locales for the input method and the rest
340 of the terminal, using the resource "imlocale": 586 of the terminal, using the resource "imlocale":
341 587
… …
344 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 590 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 591 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, 592 be able to input characters outside "EUC-JP" in a normal way then,
347 as your input method limits you. 593 as your input method limits you.
348 594
595 Rxvt-unicode crashes when the X Input Method changes or exits.
596 Unfortunately, this is unavoidable, as the XIM protocol is racy by
597 design. Applications can avoid some crashes at the expense of memory
598 leaks, and Input Methods can avoid some crashes by careful ordering
599 at exit time. kinput2 (and derived input methods) generally
600 succeeds, while SCIM (or similar input methods) fails. In the end,
601 however, crashes cannot be completely avoided even if both sides
602 cooperate.
603
604 So the only workaround is not to kill your Input Method Servers.
605
349 Rxvt-unicode uses gobs of memory, how can I reduce that? 606 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 607 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 608 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 609 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 610 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 611 Xft font will be loaded accidentally when rxvt-unicode tries to find
355 characters. 612 a font for your characters.
356 613
357 Also, many people (me included) like large windows and even larger 614 Also, many people (me included) like large windows and even larger
358 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 615 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
359 use 6 bytes per screen cell. For a 160x?? window this amounts to 616 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 617 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. 619 it gets worse, as rxvt-unicode then uses 8 bytes per screen cell.
363 620
364 Can I speed up Xft rendering somehow? 621 Can I speed up Xft rendering somehow?
365 Yes, the most obvious way to speed it up is to avoid Xft entirely, 622 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 623 as it is simply slow. If you still want Xft fonts you might try to
367 disable antialiasing (by appending ":antialiasing=false"), which 624 disable antialiasing (by appending ":antialias=false"), which saves
368 saves lots of memory and also speeds up rendering considerably. 625 lots of memory and also speeds up rendering considerably.
369 626
370 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? 627 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 628 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 629 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 630 fonts, because they are small and fast, and then use Xft fonts. It
… …
404 resources (or as long-options). 661 resources (or as long-options).
405 662
406 Here are values that are supposed to resemble a VGA screen, 663 Here are values that are supposed to resemble a VGA screen,
407 including the murky brown that passes for low-intensity yellow: 664 including the murky brown that passes for low-intensity yellow:
408 665
409 URxvt*color0: #000000 666 URxvt.color0: #000000
410 URxvt*color1: #A80000 667 URxvt.color1: #A80000
411 URxvt*color2: #00A800 668 URxvt.color2: #00A800
412 URxvt*color3: #A8A800 669 URxvt.color3: #A8A800
413 URxvt*color4: #0000A8 670 URxvt.color4: #0000A8
414 URxvt*color5: #A800A8 671 URxvt.color5: #A800A8
415 URxvt*color6: #00A8A8 672 URxvt.color6: #00A8A8
416 URxvt*color7: #A8A8A8 673 URxvt.color7: #A8A8A8
417 674
418 URxvt*color8: #000054 675 URxvt.color8: #000054
419 URxvt*color9: #FF0054 676 URxvt.color9: #FF0054
420 URxvt*color10: #00FF54 677 URxvt.color10: #00FF54
421 URxvt*color11: #FFFF54 678 URxvt.color11: #FFFF54
422 URxvt*color12: #0000FF 679 URxvt.color12: #0000FF
423 URxvt*color13: #FF00FF 680 URxvt.color13: #FF00FF
424 URxvt*color14: #00FFFF 681 URxvt.color14: #00FFFF
425 URxvt*color15: #FFFFFF 682 URxvt.color15: #FFFFFF
426 683
427 And here is a more complete set of non-standard colors described as 684 And here is a more complete set of non-standard colors described
428 "pretty girly": 685 (not by me) as "pretty girly".
429 686
430 URxvt.cursorColor: #dc74d1 687 URxvt.cursorColor: #dc74d1
431 URxvt.pointerColor: #dc74d1 688 URxvt.pointerColor: #dc74d1
432 URxvt.background: #0e0e0e 689 URxvt.background: #0e0e0e
433 URxvt.foreground: #4ad5e1 690 URxvt.foreground: #4ad5e1
… …
444 URxvt.color6: #73f7ff 701 URxvt.color6: #73f7ff
445 URxvt.color14: #73f7ff 702 URxvt.color14: #73f7ff
446 URxvt.color7: #e1dddd 703 URxvt.color7: #e1dddd
447 URxvt.color15: #e1dddd 704 URxvt.color15: #e1dddd
448 705
706 How can I start rxvtd in a race-free way?
707 Try "rxvtd -f -o", which tells rxvtd to open the display, create the
708 listening socket and then fork.
709
449 What's with the strange Backspace/Delete key behaviour? 710 What's with the strange Backspace/Delete key behaviour?
450 Assuming that the physical Backspace key corresponds to the 711 Assuming that the physical Backspace key corresponds to the
451 BackSpace keysym (not likely for Linux ... see the following 712 BackSpace keysym (not likely for Linux ... see the following
452 question) there are two standard values that can be used for 713 question) there are two standard values that can be used for
453 Backspace: "^H" and "^?". 714 Backspace: "^H" and "^?".
… …
471 732
472 # use Backspace = ^? 733 # use Backspace = ^?
473 $ stty erase ^? 734 $ stty erase ^?
474 $ rxvt 735 $ rxvt
475 736
476 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 737 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
477 738
478 For an existing rxvt-unicode: 739 For an existing rxvt-unicode:
479 740
480 # use Backspace = ^H 741 # use Backspace = ^H
481 $ stty erase ^H 742 $ stty erase ^H
… …
490 value properly reflects that. 751 value properly reflects that.
491 752
492 The Delete key is a another casualty of the ill-defined Backspace 753 The Delete key is a another casualty of the ill-defined Backspace
493 problem. To avoid confusion between the Backspace and Delete keys, 754 problem. To avoid confusion between the Backspace and Delete keys,
494 the Delete key has been assigned an escape sequence to match the 755 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. 756 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
757 termcap/terminfo.
496 758
497 Some other Backspace problems: 759 Some other Backspace problems:
498 760
499 some editors use termcap/terminfo, some editors (vim I'm told) 761 some editors use termcap/terminfo, some editors (vim I'm told)
500 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 762 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
504 766
505 I don't like the key-bindings. How do I change them? 767 I don't like the key-bindings. How do I change them?
506 There are some compile-time selections available via configure. 768 There are some compile-time selections available via configure.
507 Unless you have run "configure" with the "--disable-resources" 769 Unless you have run "configure" with the "--disable-resources"
508 option you can use the `keysym' resource to alter the keystrings 770 option you can use the `keysym' resource to alter the keystrings
509 associated with keysym 0xFF00 - 0xFFFF (function, cursor keys, etc). 771 associated with keysyms.
510 772
511 Here's an example for a tn3270 session started using `rxvt -name 773 Here's an example for a URxvt session started using "rxvt -name
512 tn3270' 774 URxvt"
513 775
514 !# ----- special uses ------: 776 URxvt.keysym.Home: \033[1~
515 ! tn3270 login, remap function and arrow keys. 777 URxvt.keysym.End: \033[4~
516 tn3270*font: *clean-bold-*-*--15-* 778 URxvt.keysym.C-apostrophe: \033<C-'>
779 URxvt.keysym.C-slash: \033<C-/>
780 URxvt.keysym.C-semicolon: \033<C-;>
781 URxvt.keysym.C-grave: \033<C-`>
782 URxvt.keysym.C-comma: \033<C-,>
783 URxvt.keysym.C-period: \033<C-.>
784 URxvt.keysym.C-0x60: \033<C-`>
785 URxvt.keysym.C-Tab: \033<C-Tab>
786 URxvt.keysym.C-Return: \033<C-Return>
787 URxvt.keysym.S-Return: \033<S-Return>
788 URxvt.keysym.S-space: \033<S-Space>
789 URxvt.keysym.M-Up: \033<M-Up>
790 URxvt.keysym.M-Down: \033<M-Down>
791 URxvt.keysym.M-Left: \033<M-Left>
792 URxvt.keysym.M-Right: \033<M-Right>
793 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
794 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
795 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
517 796
518 ! keysym - used by rxvt only 797 See some more examples in the documentation for the keysym resource.
519 ! Delete - ^D
520 tn3270*keysym.0xFFFF: \004
521
522 ! Home - ^A
523 tn3270*keysym.0xFF50: \001
524 ! Left - ^B
525 tn3270*keysym.0xFF51: \002
526 ! Up - ^P
527 tn3270*keysym.0xFF52: \020
528 ! Right - ^F
529 tn3270*keysym.0xFF53: \006
530 ! Down - ^N
531 tn3270*keysym.0xFF54: \016
532 ! End - ^E
533 tn3270*keysym.0xFF57: \005
534
535 ! F1 - F12
536 tn3270*keysym.0xFFBE: \e1
537 tn3270*keysym.0xFFBF: \e2
538 tn3270*keysym.0xFFC0: \e3
539 tn3270*keysym.0xFFC1: \e4
540 tn3270*keysym.0xFFC2: \e5
541 tn3270*keysym.0xFFC3: \e6
542 tn3270*keysym.0xFFC4: \e7
543 tn3270*keysym.0xFFC5: \e8
544 tn3270*keysym.0xFFC6: \e9
545 tn3270*keysym.0xFFC7: \e0
546 tn3270*keysym.0xFFC8: \e-
547 tn3270*keysym.0xFFC9: \e=
548
549 ! map Prior/Next to F7/F8
550 tn3270*keysym.0xFF55: \e7
551 tn3270*keysym.0xFF56: \e8
552 798
553 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 799 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How
554 do I make use of them? For example, the Sun Keyboard type 4 has the 800 do I make use of them? For example, the Sun Keyboard type 4 has the
555 following mappings that rxvt-unicode doesn't recognize. 801 following mappings that rxvt-unicode doesn't recognize.
556 KP_Insert == Insert 802 KP_Insert == Insert
… …
562 808
563 Rather than have rxvt-unicode try to accommodate all the various 809 Rather than have rxvt-unicode try to accommodate all the various
564 possible keyboard mappings, it is better to use `xmodmap' to remap 810 possible keyboard mappings, it is better to use `xmodmap' to remap
565 the keys as required for your particular machine. 811 the keys as required for your particular machine.
566 812
567 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 813 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
568 need this to decide about setting colors etc. 814 I need this to decide about setting colors etc.
569 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 815 rxvt and rxvt-unicode always export the variable "COLORTERM", so you
570 can check and see if that is set. Note that several programs, JED, 816 can check and see if that is set. Note that several programs, JED,
571 slrn, Midnight Commander automatically check this variable to decide 817 slrn, Midnight Commander automatically check this variable to decide
572 whether or not to use color. 818 whether or not to use color.
573 819
… …
604 Before sending me mail, you could go to IRC: "irc.freenode.net", 850 Before sending me mail, you could go to IRC: "irc.freenode.net",
605 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might 851 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might
606 be interested in learning about new and exciting problems (but not 852 be interested in learning about new and exciting problems (but not
607 FAQs :). 853 FAQs :).
608 854
609SYNOPSIS 855RXVT TECHNICAL REFERENCE
610 # set a new font set
611 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
612
613 # change the locale and tell rxvt-unicode about it
614 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
615
616 # set window title
617 printf '\33]2;%s\007' "new window title"
618
619DESCRIPTION 856DESCRIPTION
620 The rest of this document describes various technical aspects of 857 The rest of this document describes various technical aspects of
621 rxvt-unicode. First the description of supported command sequences, 858 rxvt-unicode. First the description of supported command sequences,
622 followed by menu and pixmap support and last by a description of all 859 followed by menu and pixmap support and last by a description of all
623 features selectable at "configure" time. 860 features selectable at "configure" time.
624 861
625RXVT TECHNICAL REFERENCE
626Definitions 862Definitions
627 "c" The literal character c. 863 "c" The literal character c.
628 864
629 "C" A single (required) character. 865 "C" A single (required) character.
630 866
… …
715 "ESC O" 951 "ESC O"
716 Single Shift Select of G3 Character Set (SS3): affects next 952 Single Shift Select of G3 Character Set (SS3): affects next
717 character only *unimplemented* 953 character only *unimplemented*
718 954
719 "ESC Z" 955 "ESC Z"
720 Obsolete form of returns: "ESC[?1;2C" *rxvt-unicode compile-time 956 Obsolete form of returns: "ESC [ ? 1 ; 2 C" *rxvt-unicode
721 option* 957 compile-time option*
722 958
723 "ESC c" 959 "ESC c"
724 Full reset (RIS) 960 Full reset (RIS)
725 961
726 "ESC n" 962 "ESC n"
727 Invoke the G2 Character Set (LS2) 963 Invoke the G2 Character Set (LS2)
728 964
729 "ESC o" 965 "ESC o"
730 Invoke the G3 Character Set (LS3) 966 Invoke the G3 Character Set (LS3)
731 967
732 "ESC" ( C> 968 "ESC ( C"
733 Designate G0 Character Set (ISO 2022), see below for values of "C". 969 Designate G0 Character Set (ISO 2022), see below for values of "C".
734 970
735 "ESC" ) C> 971 "ESC ) C"
736 Designate G1 Character Set (ISO 2022), see below for values of "C". 972 Designate G1 Character Set (ISO 2022), see below for values of "C".
737 973
738 "ESC * C" 974 "ESC * C"
739 Designate G2 Character Set (ISO 2022), see below for values of "C". 975 Designate G2 Character Set (ISO 2022), see below for values of "C".
740 976
… …
833 "ESC [ Ps a" 1069 "ESC [ Ps a"
834 See "ESC [ Ps C" 1070 See "ESC [ Ps C"
835 1071
836 "ESC [ Ps c" 1072 "ESC [ Ps c"
837 Send Device Attributes (DA) "Ps = 0" (or omitted): request 1073 Send Device Attributes (DA) "Ps = 0" (or omitted): request
838 attributes from terminal returns: "ESC[?1;2c" (``I am a VT100 with 1074 attributes from terminal returns: "ESC [ ? 1 ; 2 c" (``I am a VT100
839 Advanced Video Option'') 1075 with Advanced Video Option'')
840 1076
841 "ESC [ Ps d" 1077 "ESC [ Ps d"
842 Cursor to Line "Ps" (VPA) 1078 Cursor to Line "Ps" (VPA)
843 1079
844 "ESC [ Ps e" 1080 "ESC [ Ps e"
… …
918 (CSR) 1154 (CSR)
919 1155
920 "ESC [ s" 1156 "ESC [ s"
921 Save Cursor (SC) 1157 Save Cursor (SC)
922 1158
1159 "ESC [ Ps;Pt t"
1160 Window Operations
1161
1162 Ps = 1 Deiconify (map) window
1163 Ps = 2 Iconify window
1164 Ps = 3 ESC [ 3 ; X ; Y t Move window to (X|Y)
1165 Ps = 4 ESC [ 4 ; H ; W t Resize to WxH pixels
1166 Ps = 5 Raise window
1167 Ps = 6 Lower window
1168 Ps = 7 Refresh screen once
1169 Ps = 8 ESC [ 8 ; R ; C t Resize to R rows and C columns
1170 Ps = 11 Report window state (responds with Ps = 1 or Ps = 2)
1171 Ps = 13 Report window position (responds with Ps = 3)
1172 Ps = 14 Report window pixel size (responds with Ps = 4)
1173 Ps = 18 Report window text size (responds with Ps = 7)
1174 Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9
1175 Ps = 20 Reports icon label (ESC ] L NAME \234)
1176 Ps = 21 Reports window title (ESC ] l NAME \234)
1177 Ps = 24.. Set window height to Ps rows
1178
1179 "ESC [ u"
1180 Restore Cursor
1181
923 "ESC [ Ps x" 1182 "ESC [ Ps x"
924 Request Terminal Parameters (DECREQTPARM) 1183 Request Terminal Parameters (DECREQTPARM)
925
926 "ESC [ u"
927 Restore Cursor
928 1184
929 1185
930 1186
931DEC Private Modes 1187DEC Private Modes
932 "ESC [ ? Pm h" 1188 "ESC [ ? Pm h"
… …
1039 l Scroll to bottom on TTY output 1295 l Scroll to bottom on TTY output
1040 1296
1041 "Ps = 1011" (rxvt) 1297 "Ps = 1011" (rxvt)
1042 h Scroll to bottom when a key is pressed 1298 h Scroll to bottom when a key is pressed
1043 l Don't scroll to bottom when a key is pressed 1299 l Don't scroll to bottom when a key is pressed
1300
1301 "Ps = 1021" (rxvt)
1302 h Bold/italic implies high intensity (see option -is)
1303 l Font styles have no effect on intensity (Compile styles)
1044 1304
1045 "Ps = 1047" 1305 "Ps = 1047"
1046 h Use Alternate Screen Buffer 1306 h Use Alternate Screen Buffer
1047 l Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it 1307 l Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1048 1308
… …
1071 Ps = 10 Change colour of text foreground to Pt (NB: may change in future) 1331 Ps = 10 Change colour of text foreground to Pt (NB: may change in future)
1072 Ps = 11 Change colour of text background to Pt (NB: may change in future) 1332 Ps = 11 Change colour of text background to Pt (NB: may change in future)
1073 Ps = 12 Change colour of text cursor foreground to Pt 1333 Ps = 12 Change colour of text cursor foreground to Pt
1074 Ps = 13 Change colour of mouse foreground to Pt 1334 Ps = 13 Change colour of mouse foreground to Pt
1075 Ps = 17 Change colour of highlight characters to Pt 1335 Ps = 17 Change colour of highlight characters to Pt
1076 Ps = 18 Change colour of bold characters to Pt 1336 Ps = 18 Change colour of bold characters to Pt [deprecated, see 706]
1077 Ps = 19 Change colour of underlined characters to Pt 1337 Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707]
1078 Ps = 20 Change default background to Pt 1338 Ps = 20 Change default background to Pt
1079 Ps = 39 Change default foreground colour to Pt rxvt compile-time option 1339 Ps = 39 Change default foreground colour to Pt.
1080 Ps = 46 Change Log File to Pt unimplemented 1340 Ps = 46 Change Log File to Pt unimplemented
1081 Ps = 49 Change default background colour to Pt rxvt compile-time option 1341 Ps = 49 Change default background colour to Pt.
1082 Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n 1342 Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n
1083 Ps = 55 Log all scrollback buffer and all of screen to Pt 1343 Ps = 55 Log all scrollback buffer and all of screen to Pt
1084 Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (rxvt extension) 1344 Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
1085 Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) 1345 Ps = 703 Menubar command Pt (Compile menubar).
1086 Ps = 704 Change colour of italic characters to Pt 1346 Ps = 704 Change colour of italic characters to Pt
1087 Ps = 705 Change background pixmap tint colour to Pt 1347 Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1348 Ps = 706 Change colour of bold characters to Pt
1349 Ps = 707 Change colour of underlined characters to Pt
1088 Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1350 Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
1089 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. 1351 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
1090 Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. 1352 Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1091 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. 1353 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1354 Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1355 Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1356 Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
1092 1357
1093 1358
1094 1359
1095menuBar 1360menuBar
1096 The exact syntax used is *almost* solidified. In the menus, DON'T try to 1361 The exact syntax used is *almost* solidified. In the menus, DON'T try to
… …
1133 [menu] 1398 [menu]
1134 access the current menuBar for alteration 1399 access the current menuBar for alteration
1135 1400
1136 [title:+*string*] 1401 [title:+*string*]
1137 set the current menuBar's title to *string*, which may contain the 1402 set the current menuBar's title to *string*, which may contain the
1138 following format specifiers: %% : literal % character %n : rxvt name 1403 following format specifiers:
1139 (as per the -name command-line option) %v : rxvt version 1404
1405 B<%n> rxvt name (as per the B<-name> command-line option)
1406 B<%v> rxvt version
1407 B<%%> literal B<%> character
1140 1408
1141 [done] 1409 [done]
1142 set menuBar access as readonly. End-of-file tag for [read:+*file*] 1410 set menuBar access as readonly. End-of-file tag for [read:+*file*]
1143 operations. 1411 operations.
1144 1412
… …
1248 1516
1249 As a convenience for the many Emacs-type editors, *action* may start 1517 As a convenience for the many Emacs-type editors, *action* may start
1250 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if 1518 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if
1251 missed from M-x commands. 1519 missed from M-x commands.
1252 1520
1253 As a convenience for issuing XTerm ESC] sequences from a menubar (or 1521 As a convenience for issuing XTerm ESC ] sequences from a menubar (or
1254 quick arrow), a BEL (^G) will be appended if needed. 1522 quick arrow), a BEL (^G) will be appended if needed.
1255 1523
1256 For example, 1524 For example,
1257 M-xapropos is equivalent to \Exapropos\r 1525 M-xapropos is equivalent to \Exapropos\r
1258 1526
… …
1558 XK_KP_8 8 ESC O x 1826 XK_KP_8 8 ESC O x
1559 XK_KP_9 9 ESC O y 1827 XK_KP_9 9 ESC O y
1560 1828
1561CONFIGURE OPTIONS 1829CONFIGURE OPTIONS
1562 General hint: if you get compile errors, then likely your configuration 1830 General hint: if you get compile errors, then likely your configuration
1563 hasn't been tested well. Either try with --enable-everything or use the 1831 hasn't been tested well. Either try with "--enable-everything" or use
1564 ./reconf script as a base for experiments. ./reconf is used by myself, 1832 the ./reconf script as a base for experiments. ./reconf is used by
1565 so it should generally be a working config. Of course, you should always 1833 myself, so it should generally be a working config. Of course, you
1566 report when a combination doesn't work, so it can be fixed. Marc Lehmann 1834 should always report when a combination doesn't work, so it can be
1567 <rxvt@schmorp.de>. 1835 fixed. Marc Lehmann <rxvt@schmorp.de>.
1836
1837 All
1568 1838
1569 --enable-everything 1839 --enable-everything
1570 Add support for all non-multichoice options listed in "./configure 1840 Add (or remove) support for all non-multichoice options listed in
1571 --help". Note that unlike other enable options this is order 1841 "./configure --help".
1572 dependant. You can specify this and then disable options which this
1573 enables by *following* this with the appropriate commands.
1574 1842
1575 --enable-xft 1843 You can specify this and then disable options you do not like by
1844 *following* this with the appropriate "--disable-..." arguments, or
1845 you can start with a minimal configuration by specifying
1846 "--disable-everything" and than adding just the "--enable-..."
1847 arguments you want.
1848
1849 --enable-xft (default: enabled)
1576 Add support for Xft (anti-aliases, among others) fonts. Xft fonts 1850 Add support for Xft (anti-aliases, among others) fonts. Xft fonts
1577 are slower and require lots of memory, but as long as you don't use 1851 are slower and require lots of memory, but as long as you don't use
1578 them, you don't pay for them. 1852 them, you don't pay for them.
1579 1853
1580 --enable-font-styles 1854 --enable-font-styles (default: on)
1581 Add support for bold, *italic* and *bold italic* font styles. The 1855 Add support for bold, *italic* and *bold italic* font styles. The
1582 fonts can be set manually or automatically. 1856 fonts can be set manually or automatically.
1583 1857
1584 --with-codesets=NAME,... 1858 --with-codesets=NAME,... (default: all)
1585 Compile in support for additional codeset (encoding) groups (eu, vn 1859 Compile in support for additional codeset (encoding) groups ("eu",
1586 are always compiled in, which includes most 8-bit character sets). 1860 "vn" are always compiled in, which includes most 8-bit character
1587 These codeset tables are currently only used for driving X11 core 1861 sets). These codeset tables are used for driving X11 core fonts,
1588 fonts, they are not required for Xft fonts. Compiling them in will 1862 they are not required for Xft fonts, although having them compiled
1589 make your binary bigger (together about 700kB), but it doesn't 1863 in lets rxvt-unicode choose replacement fonts more intelligently.
1590 increase memory usage unless you use an X11 font requiring one of 1864 Compiling them in will make your binary bigger (all of together cost
1591 these encodings. 1865 about 700kB), but it doesn't increase memory usage unless you use a
1866 font requiring one of these encodings.
1592 1867
1593 all all available codeset groups 1868 all all available codeset groups
1594 zh common chinese encodings 1869 zh common chinese encodings
1595 zh_ext rarely used but very big chinese encodigs 1870 zh_ext rarely used but very big chinese encodigs
1596 jp common japanese encodings 1871 jp common japanese encodings
1597 jp_ext rarely used but big japanese encodings 1872 jp_ext rarely used but big japanese encodings
1598 kr korean encodings 1873 kr korean encodings
1599 1874
1600 --enable-xim 1875 --enable-xim (default: on)
1601 Add support for XIM (X Input Method) protocol. This allows using 1876 Add support for XIM (X Input Method) protocol. This allows using
1602 alternative input methods (e.g. kinput2) and will also correctly set 1877 alternative input methods (e.g. kinput2) and will also correctly set
1603 up the input for people using dead keys or compose keys. 1878 up the input for people using dead keys or compose keys.
1604 1879
1605 --enable-unicode3 1880 --enable-unicode3 (default: off)
1606 Enable direct support for displaying unicode codepoints above 65535 1881 Enable direct support for displaying unicode codepoints above 65535
1607 (the basic multilingual page). This increases storage requirements 1882 (the basic multilingual page). This increases storage requirements
1608 per character from 2 to 4 bytes. X11 fonts do not yet support these 1883 per character from 2 to 4 bytes. X11 fonts do not yet support these
1609 extra characters, but Xft does. 1884 extra characters, but Xft does.
1610 1885
… …
1612 even without this flag, but the number of such characters is limited 1887 even without this flag, but the number of such characters is limited
1613 to a view thousand (shared with combining characters, see next 1888 to a view thousand (shared with combining characters, see next
1614 switch), and right now rxvt-unicode cannot display them 1889 switch), and right now rxvt-unicode cannot display them
1615 (input/output and cut&paste still work, though). 1890 (input/output and cut&paste still work, though).
1616 1891
1617 --enable-combining 1892 --enable-combining (default: on)
1618 Enable automatic composition of combining characters into composite 1893 Enable automatic composition of combining characters into composite
1619 characters. This is required for proper viewing of text where 1894 characters. This is required for proper viewing of text where
1620 accents are encoded as seperate unicode characters. This is done by 1895 accents are encoded as seperate unicode characters. This is done by
1621 using precomposited characters when available or creating new 1896 using precomposited characters when available or creating new
1622 pseudo-characters when no precomposed form exists. 1897 pseudo-characters when no precomposed form exists.
1623 1898
1624 Without --enable-unicode3, the number of additional precomposed 1899 Without --enable-unicode3, the number of additional precomposed
1625 characters is rather limited (2048, if this is full, rxvt will use 1900 characters is rather limited (2048, if this is full, rxvt-unicode
1626 the private use area, extending the number of combinations to 8448). 1901 will use the private use area, extending the number of combinations
1627 With --enable-unicode3, no practical limit exists. This will also 1902 to 8448). With --enable-unicode3, no practical limit exists.
1628 enable storage of characters >65535. 1903
1904 This option will also enable storage (but not display) of characters
1905 beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1629 1906
1630 The combining table also contains entries for arabic presentation 1907 The combining table also contains entries for arabic presentation
1631 forms, but these are not currently used. Bug me if you want these to 1908 forms, but these are not currently used. Bug me if you want these to
1632 be used. 1909 be used (and tell me how these are to be used...).
1633 1910
1634 --enable-fallback(=CLASS) 1911 --enable-fallback(=CLASS) (default: Rxvt)
1635 When reading resource settings, also read settings for class CLASS 1912 When reading resource settings, also read settings for class CLASS.
1636 (default: Rxvt). To disable resource fallback use 1913 To disable resource fallback use --disable-fallback.
1637 --disable-fallback.
1638 1914
1639 --with-res-name=NAME 1915 --with-res-name=NAME (default: urxvt)
1640 Use the given name (default: urxvt) as default application name when 1916 Use the given name as default application name when reading
1641 reading resources. Specify --with-res-name=rxvt to replace rxvt. 1917 resources. Specify --with-res-name=rxvt to replace rxvt.
1642 1918
1643 --with-res-class=CLASS 1919 --with-res-class=CLASS /default: URxvt)
1644 Use the given class (default: URxvt) as default application class 1920 Use the given class as default application class when reading
1645 when reading resources. Specify --with-res-class=Rxvt to replace 1921 resources. Specify --with-res-class=Rxvt to replace rxvt.
1646 rxvt.
1647 1922
1648 --enable-utmp 1923 --enable-utmp (default: on)
1649 Write user and tty to utmp file (used by programs like w) at start 1924 Write user and tty to utmp file (used by programs like w) at start
1650 of rxvt execution and delete information when rxvt exits. 1925 of rxvt execution and delete information when rxvt exits.
1651 1926
1652 --enable-wtmp 1927 --enable-wtmp (default: on)
1653 Write user and tty to wtmp file (used by programs like last) at 1928 Write user and tty to wtmp file (used by programs like last) at
1654 start of rxvt execution and write logout when rxvt exits. This 1929 start of rxvt execution and write logout when rxvt exits. This
1655 option requires --enable-utmp to also be specified. 1930 option requires --enable-utmp to also be specified.
1656 1931
1657 --enable-lastlog 1932 --enable-lastlog (default: on)
1658 Write user and tty to lastlog file (used by programs like lastlogin) 1933 Write user and tty to lastlog file (used by programs like lastlogin)
1659 at start of rxvt execution. This option requires --enable-utmp to 1934 at start of rxvt execution. This option requires --enable-utmp to
1660 also be specified. 1935 also be specified.
1661 1936
1662 --enable-xpm-background 1937 --enable-xpm-background (default: on)
1663 Add support for XPM background pixmaps. 1938 Add support for XPM background pixmaps.
1664 1939
1665 --enable-transparency 1940 --enable-transparency (default: on)
1666 Add support for inheriting parent backgrounds thus giving a fake 1941 Add support for inheriting parent backgrounds thus giving a fake
1667 transparency to the term. 1942 transparency to the term.
1668 1943
1669 --enable-fading 1944 --enable-fading (default: on)
1670 Add support for fading the text when focus is lost. 1945 Add support for fading the text when focus is lost (requires
1946 "--enable-transparency").
1671 1947
1672 --enable-tinting 1948 --enable-tinting (default: on)
1673 Add support for tinting of transparent backgrounds. 1949 Add support for tinting of transparent backgrounds (requires
1950 "--enable-transparency").
1674 1951
1675 --enable-menubar 1952 --enable-menubar (default: off) [DEPRECATED]
1676 Add support for our menu bar system (this interacts badly with 1953 Add support for our menu bar system (this interacts badly with
1677 dynamic locale switching currently). 1954 dynamic locale switching currently). This option is DEPRECATED and
1955 will be removed in the future.
1678 1956
1679 --enable-rxvt-scroll 1957 --enable-rxvt-scroll (default: on)
1680 Add support for the original rxvt scrollbar. 1958 Add support for the original rxvt scrollbar.
1681 1959
1682 --enable-next-scroll 1960 --enable-next-scroll (default: on)
1683 Add support for a NeXT-like scrollbar. 1961 Add support for a NeXT-like scrollbar.
1684 1962
1685 --enable-xterm-scroll 1963 --enable-xterm-scroll (default: on)
1686 Add support for an Xterm-like scrollbar. 1964 Add support for an Xterm-like scrollbar.
1687 1965
1688 --enable-plain-scroll 1966 --enable-plain-scroll (default: on)
1689 Add support for a very unobtrusive, plain-looking scrollbar that is 1967 Add support for a very unobtrusive, plain-looking scrollbar that is
1690 the favourite of the rxvt-unicode author, having used it for many 1968 the favourite of the rxvt-unicode author, having used it for many
1691 years. 1969 years.
1692 1970
1693 --enable-half-shadow 1971 --enable-half-shadow (default: off)
1694 Make shadows on the scrollbar only half the normal width & height. 1972 Make shadows on the scrollbar only half the normal width & height.
1695 only applicable to rxvt scrollbars. 1973 only applicable to rxvt scrollbars.
1696 1974
1697 --enable-ttygid 1975 --enable-ttygid (default: off)
1698 Change tty device setting to group "tty" - only use this if your 1976 Change tty device setting to group "tty" - only use this if your
1699 system uses this type of security. 1977 system uses this type of security.
1700 1978
1701 --disable-backspace-key 1979 --disable-backspace-key
1702 Disable any handling of the backspace key by us - let the X server 1980 Removes any handling of the backspace key by us - let the X server
1703 do it. 1981 do it.
1704 1982
1705 --disable-delete-key 1983 --disable-delete-key
1706 Disable any handling of the delete key by us - let the X server do 1984 Removes any handling of the delete key by us - let the X server do
1707 it. 1985 it.
1708 1986
1709 --disable-resources 1987 --disable-resources
1710 Remove all resources checking. 1988 Removes any support for resource checking.
1711 1989
1712 --enable-xgetdefault 1990 --enable-strings (default: off)
1713 Make resources checking via XGetDefault() instead of our small
1714 version which only checks ~/.Xdefaults, or if that doesn't exist
1715 then ~/.Xresources.
1716
1717 --enable-strings
1718 Add support for our possibly faster memset() function and other 1991 Add support for our possibly faster memset() function and other
1719 various routines, overriding your system's versions which may have 1992 various routines, overriding your system's versions which may have
1720 been hand-crafted in assembly or may require extra libraries to link 1993 been hand-crafted in assembly or may require extra libraries to link
1721 in. (this breaks ANSI-C rules and has problems on many GNU/Linux 1994 in. (this breaks ANSI-C rules and has problems on many GNU/Linux
1722 systems). 1995 systems).
1723 1996
1724 --disable-swapscreen 1997 --disable-swapscreen
1725 Remove support for swap screen. 1998 Remove support for secondary/swap screen.
1726 1999
1727 --enable-frills 2000 --enable-frills (default: on)
1728 Add support for many small features that are not essential but nice 2001 Add support for many small features that are not essential but nice
1729 to have. Normally you want this, but for very small binaries you may 2002 to have. Normally you want this, but for very small binaries you may
1730 want to disable this. 2003 want to disable this.
1731 2004
2005 A non-exhaustive list of features enabled by "--enable-frills"
2006 (possibly in combination with other switches) is:
2007
2008 MWM-hints
2009 EWMH-hints (pid, utf8 names) and protocols (ping)
2010 seperate underline colour (-underlineColor)
2011 settable border widths and borderless switch (-w, -b, -bl)
2012 settable extra linespacing /-lsp)
2013 iso-14755-2 and -3, and visual feedback
2014 backindex and forwardindex escape sequence
2015 window op and some xterm/OSC escape sequences
2016 tripleclickwords (-tcw)
2017 settable insecure mode (-insecure)
2018 keysym remapping support
2019 cursor blinking and underline cursor (-cb, -uc)
2020 XEmbed support (-embed)
2021 user-pty (-pty-fd)
2022 hold on exit (-hold)
2023 skip builtin block graphics (-sbg)
2024 sgr modes 90..97 and 100..107
2025
1732 --enable-iso14755 2026 --enable-iso14755 (default: on)
1733 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). 2027 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
1734 Basic support (section 5.1) is enabled by "--enable-frills", while 2028 Basic support (section 5.1) is enabled by "--enable-frills", while
1735 support for 5.2, 5.3 and 5.4 is enabled with this switch. 2029 support for 5.2, 5.3 and 5.4 is enabled with this switch.
1736 2030
1737 --enable-keepscrolling 2031 --enable-keepscrolling (default: on)
1738 Add support for continual scrolling of the display when you hold the 2032 Add support for continual scrolling of the display when you hold the
1739 mouse button down on a scrollbar arrow. 2033 mouse button down on a scrollbar arrow.
1740 2034
1741 --enable-mousewheel 2035 --enable-mousewheel (default: on)
1742 Add support for scrolling via mouse wheel or buttons 4 & 5. 2036 Add support for scrolling via mouse wheel or buttons 4 & 5.
1743 2037
1744 --enable-slipwheeling 2038 --enable-slipwheeling (default: on)
1745 Add support for continual scrolling (using the mouse wheel as an 2039 Add support for continual scrolling (using the mouse wheel as an
1746 accelerator) while the control key is held down. This option 2040 accelerator) while the control key is held down. This option
1747 requires --enable-mousewheel to also be specified. 2041 requires --enable-mousewheel to also be specified.
1748 2042
1749 --disable-new-selection 2043 --disable-new-selection
1750 Remove support for mouse selection style like that of xterm. 2044 Remove support for mouse selection style like that of xterm.
1751 2045
1752 --enable-dmalloc 2046 --enable-dmalloc (default: off)
1753 Use Gray Watson's malloc - which is good for debugging See 2047 Use Gray Watson's malloc - which is good for debugging See
1754 http://www.letters.com/dmalloc/ for details If you use either this 2048 http://www.letters.com/dmalloc/ for details If you use either this
1755 or the next option, you may need to edit src/Makefile after 2049 or the next option, you may need to edit src/Makefile after
1756 compiling to point DINCLUDE and DLIB to the right places. 2050 compiling to point DINCLUDE and DLIB to the right places.
1757 2051
1758 You can only use either this option and the following (should you 2052 You can only use either this option and the following (should you
1759 use either) . 2053 use either) .
1760 2054
1761 --enable-dlmalloc 2055 --enable-dlmalloc (default: off)
1762 Use Doug Lea's malloc - which is good for a production version See 2056 Use Doug Lea's malloc - which is good for a production version See
1763 <http://g.oswego.edu/dl/html/malloc.html> for details. 2057 <http://g.oswego.edu/dl/html/malloc.html> for details.
1764 2058
1765 --enable-smart-resize 2059 --enable-smart-resize (default: on)
1766 Add smart growth/shrink behaviour when changing font size via from 2060 Add smart growth/shrink behaviour when changing font size via hot
1767 hot keys. This should keep in a fixed position the rxvt corner which 2061 keys. This should keep the window corner which is closest to a
1768 is closest to a corner of the screen. 2062 corner of the screen in a fixed position.
1769 2063
1770 --enable-cursor-blink
1771 Add support for a blinking cursor.
1772
1773 --enable-pointer-blank 2064 --enable-pointer-blank (default: on)
1774 Add support to have the pointer disappear when typing or inactive. 2065 Add support to have the pointer disappear when typing or inactive.
1775 2066
1776 --with-name=NAME 2067 --enable-perl (default: off)
2068 Enable an embedded perl interpreter. See the rxvtperl(3) manpage
2069 (doc/rxvtperl.txt) for more info on this feature, or the files in
2070 src/perl-ext/ for the extensions that are installed by default. The
2071 perl interpreter that is used can be specified via the "PERL"
2072 environment variable when running configure.
2073
2074 --with-name=NAME (default: urxvt)
1777 Set the basename for the installed binaries (default: urxvt, 2075 Set the basename for the installed binaries, resulting in "urxvt",
1778 resulting in urxvt, urxvtd etc.). Specify --with-name=rxvt to 2076 "urxvtd" etc.). Specify "--with-name=rxvt" to replace with "rxvt".
1779 replace rxvt.
1780 2077
1781 --with-term=NAME 2078 --with-term=NAME (default: rxvt-unicode)
1782 Change the environmental variable for the terminal to NAME (default 2079 Change the environmental variable for the terminal to NAME.
1783 "rxvt")
1784 2080
1785 --with-terminfo=PATH 2081 --with-terminfo=PATH
1786 Change the environmental variable for the path to the terminfo tree 2082 Change the environmental variable for the path to the terminfo tree
1787 to PATH. 2083 to PATH.
1788 2084

Diff Legend

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