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

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents):
Revision 1.3 by root, Mon Jan 17 01:44:51 2005 UTC vs.
Revision 1.20 by root, Thu Jun 30 14:00:49 2005 UTC

1NAME 1NAME
2 RXVT REFERENCE - FAQ, command sequences and other background information 2 RXVT REFERENCE - FAQ, command sequences and other background information
3
4SYNOPSIS
5 # set a new font set
6 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
7
8 # change the locale and tell rxvt-unicode about it
9 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
10
11 # set window title
12 printf '\33]2;%s\007' "new window title"
13
14DESCRIPTION
15 This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
16 all escape sequences, and other background information.
17
18 The newest version of this document is also available on the World Wide
19 Web at
20 <http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
3 21
4FREQUENTLY ASKED QUESTIONS 22FREQUENTLY ASKED QUESTIONS
5 How do I know which rxvt-unicode version I'm using? 23 How do I know which rxvt-unicode version I'm using?
6 The version number is displayed with the usage (-h). Also the escape 24 The version number is displayed with the usage (-h). Also the escape
7 sequence "ESC[8n" sets the window title to the version number. 25 sequence "ESC [ 8 n" sets the window title to the version number.
26
27 I am using Debian GNU/Linux and have a problem...
28 The Debian GNU/Linux package of rxvt-unicode contains large patches
29 that considerably change the behaviour of rxvt-unicode. Before
30 reporting a bug to the original rxvt-unicode author please download
31 and install the genuine version
32 (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
33 problem. If you cannot, chances are that the problems are specific
34 to Debian GNU/Linux, in which case it should be reported via the
35 Debian Bug Tracking System (use "reportbug" to report the bug).
36
37 For other problems that also affect the Debian package, you can and
38 probably should use the Debian BTS, too, because, after all, it's
39 also a bug in the Debian version and it serves as a reminder for
40 other users that might encounter the same issue.
8 41
9 When I log-in to another system it tells me about missing terminfo data? 42 When I log-in to another system it tells me about missing terminfo data?
10 The terminal description used by rxvt-unicode is not as widely 43 The terminal description used by rxvt-unicode is not as widely
11 available as that for xterm, or even rxvt (for which the same 44 available as that for xterm, or even rxvt (for which the same
12 problem often arises). 45 problem often arises).
… …
24 problems arising, which includes wrong keymapping, less and 57 problems arising, which includes wrong keymapping, less and
25 different colours and some refresh errors in fullscreen 58 different colours and some refresh errors in fullscreen
26 applications. It's a nice quick-and-dirty workaround for rare cases, 59 applications. It's a nice quick-and-dirty workaround for rare cases,
27 though. 60 though.
28 61
29 If you always want to do this you can either recompile rxvt-unicode 62 If you always want to do this (and are fine with the consequences)
30 with the desired TERM value or use a resource to set it: 63 you can either recompile rxvt-unicode with the desired TERM value or
64 use a resource to set it:
31 65
32 URxvt.termName: rxvt 66 URxvt.termName: rxvt
33 67
34 If you don't plan to use rxvt (quite common...) you could also 68 If you don't plan to use rxvt (quite common...) you could also
35 replace the rxvt terminfo file with the rxvt-unicode one. 69 replace the rxvt terminfo file with the rxvt-unicode one.
36 70
71 "bash"'s readline does not work correctly under rxvt.
37 I need a termcap file entry. 72 I need a termcap file entry.
73 One reason you might want this is that some distributions or
74 operating systems still compile some programs using the
75 long-obsoleted termcap library (Fedora Core's bash is one example)
76 and rely on a termcap entry for "rxvt-unicode".
77
38 You could use rxvt's termcap entry with resonable results in many 78 You could use rxvt's termcap entry with resonable results in many
39 cases. You can also create a termcap entry by using terminfo's 79 cases. You can also create a termcap entry by using terminfo's
40 infocmp program like this: 80 infocmp program like this:
41 81
42 infocmp -C rxvt-unicode 82 infocmp -C rxvt-unicode
43 83
44 OR you could this termcap entry: 84 Or you could use this termcap entry, generated by the command above:
45 85
46 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 86 rxvt-unicode|rxvt-unicode terminal (X Window System):\
47 :am:bw:eo:km:mi:ms:xn:xo:\ 87 :am:bw:eo:km:mi:ms:xn:xo:\
48 :co#80:it#8:li#24:\ 88 :co#80:it#8:li#24:lm#0:\
49 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 89 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
50 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ 90 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
51 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ 91 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
52 :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ 92 :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
53 :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ 93 :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
54 :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ 94 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
95 :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
55 :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ 96 :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
56 :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ 97 :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
57 :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ 98 :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
58 :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ 99 :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
59 :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ 100 :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
60 :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ 101 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
61 :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ 102 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
62 :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ 103 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
63 :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 104 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
64 :vs=\E[?25h: 105 :vs=\E[?25h:
65 106
66 Why does "ls" no longer have coloured output? 107 Why does "ls" no longer have coloured output?
67 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 108 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
68 decide wether a terminal has colour, but uses it's own configuration 109 decide wether a terminal has colour, but uses it's own configuration
… …
87 furthermore fail to even install the "rxvt-unicode" terminfo file, 128 furthermore fail to even install the "rxvt-unicode" terminfo file,
88 so you will need to install it on your own (See the question When I 129 so you will need to install it on your own (See the question When I
89 log-in to another system it tells me about missing terminfo data? on 130 log-in to another system it tells me about missing terminfo data? on
90 how to do this). 131 how to do this).
91 132
133 My numerical keypad acts weird and generates differing output?
134 Some Debian GNUL/Linux users seem to have this problem, although no
135 specific details were reported so far. It is possible that this is
136 caused by the wrong "TERM" setting, although the details of wether
137 and how this can happen are unknown, as "TERM=rxvt" should offer a
138 compatible keymap. See the answer to the previous question, and
139 please report if that helped.
140
92 Rxvt-unicode does not seem to understand the selected encoding? 141 Rxvt-unicode does not seem to understand the selected encoding?
93 Unicode does not seem to work? 142 Unicode does not seem to work?
94 If you encounter strange problems like typing an accented character 143 If you encounter strange problems like typing an accented character
95 but getting two unrelated other characters or similar, or if program 144 but getting two unrelated other characters or similar, or if program
96 output is subtly garbled, then you should check your locale 145 output is subtly garbled, then you should check your locale
97 settings. 146 settings.
98 147
99 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 148 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the
100 programs. Often rxvt-unicode is started in the "C" locale, while the 149 programs. Often rxvt-unicode is started in the "C" locale, while the
101 login script running within the rxvt-unicode window changes the 150 login script running within the rxvt-unicode window changes the
102 locale to sth. else, e.h. "en_GB.UTF-8". Needless to say, this is 151 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
103 not going to work. 152 is not going to work.
104 153
105 The best thing is to fix your startup environment, as you will 154 The best thing is to fix your startup environment, as you will
106 likely run into other problems. If nothing works you can try this in 155 likely run into other problems. If nothing works you can try this in
107 your .profile. 156 your .profile.
108 157
109 printf '\e]701;%s\007' "$LC_CTYPE" 158 printf '\e]701;%s\007' "$LC_CTYPE"
110 159
111 If this doesn't work, then maybe you use a "LC_CTYPE" specification 160 If this doesn't work, then maybe you use a "LC_CTYPE" specification
112 not supported on your systems. Some systems have a "locale" command 161 not supported on your systems. Some systems have a "locale" command
113 which displays this. If it displays sth. like: 162 which displays this (also, "perl -e0" can be used to check locale
163 settings, as it will complain loudly if it cannot set the locale).
164 If it displays something like:
114 165
115 locale: Cannot set LC_CTYPE to default locale: ... 166 locale: Cannot set LC_CTYPE to default locale: ...
116 167
117 Then the locale you specified is not supported on your system. 168 Then the locale you specified is not supported on your system.
118 169
… …
126 Chances are that the font you (or the admin/package maintainer of 177 Chances are that the font you (or the admin/package maintainer of
127 your system/os) have specified does not cover all the characters you 178 your system/os) have specified does not cover all the characters you
128 want to display. 179 want to display.
129 180
130 rxvt-unicode makes a best-effort try at finding a replacement font. 181 rxvt-unicode makes a best-effort try at finding a replacement font.
131 Often the result is fine, but sometimes the chosen font looks bad. 182 Often the result is fine, but sometimes the chosen font looks
132 Many fonts have totally strange characters that don't resemble the 183 bad/ugly/wrong. Some fonts have totally strange characters that
133 correct glyph at all, and rxvt-unicode lacks the artificial 184 don't resemble the correct glyph at all, and rxvt-unicode lacks the
134 intelligence to detect that a specific glyph is wrong: it has to 185 artificial intelligence to detect that a specific glyph is wrong: it
135 believe the font that the characters it contains indeed look 186 has to believe the font that the characters it claims to contain
136 correct. 187 indeed look correct.
137 188
138 In that case, select a font of your taste and add it to the font 189 In that case, select a font of your taste and add it to the font
139 list, e.g.: 190 list, e.g.:
140 191
141 rxvt -fn basefont,font2,font3... 192 rxvt -fn basefont,font2,font3...
… …
144 font. If the base font does not contain the character, it will go to 195 font. If the base font does not contain the character, it will go to
145 the next font, and so on. Specifying your own fonts will also speed 196 the next font, and so on. Specifying your own fonts will also speed
146 up this search and use less resources within rxvt-unicode and the 197 up this search and use less resources within rxvt-unicode and the
147 X-server. 198 X-server.
148 199
149 The only limitation is that all the fonts must not be larger than 200 The only limitation is that none of the fonts may be larger than the
150 the base font, as the base font defines the principal cell size, 201 base font, as the base font defines the terminal character cell
151 which must be the same due to the way terminals work. 202 size, which must be the same due to the way terminals work.
152 203
153 Why do some chinese characters look so different than others? 204 Why do some chinese characters look so different than others?
154 This is because there is a difference between script and language -- 205 This is because there is a difference between script and language --
155 rxvt-unicode does not know which language the text that is output 206 rxvt-unicode does not know which language the text that is output
156 is, as it only knows the unicode character codes. If rxvt-unicode 207 is, as it only knows the unicode character codes. If rxvt-unicode
157 first sees a japanese character, it might choose a japanese font for 208 first sees a japanese/chinese character, it might choose a japanese
158 it. Subsequent japanese characters will take that font. Now, many 209 font for display. Subsequent japanese characters will use that font.
159 chinese characters aren't represented in japanese fonts, so when the 210 Now, many chinese characters aren't represented in japanese fonts,
160 first non-japanese character comes up, rxvt-unicode will look for a 211 so when the first non-japanese character comes up, rxvt-unicode will
161 chinese font -- unfortunately at this point, it will still use the 212 look for a chinese font -- unfortunately at this point, it will
162 japanese font for japanese characters that are also chinese. 213 still use the japanese font for chinese characters that are also in
214 the japanese font.
163 215
164 The workaround is easy: just tag a chinese font at the end of your 216 The workaround is easy: just tag a chinese font at the end of your
165 font list (see the previous question). The key is to view the font 217 font list (see the previous question). The key is to view the font
166 list as a preference list: If you expect more japanese, list a 218 list as a preference list: If you expect more japanese, list a
167 japanese font first. If you expect more chinese, put a chinese font 219 japanese font first. If you expect more chinese, put a chinese font
168 first. 220 first.
169 221
170 In the future it might be possible to switch preferences at runtime 222 In the future it might be possible to switch language preferences at
171 (the internal data structure has no problem with using different 223 runtime (the internal data structure has no problem with using
172 fonts for the same character at the same time, but no interface for 224 different fonts for the same character at the same time, but no
173 this has been designed yet). 225 interface for this has been designed yet).
226
227 Until then, you might get away with switching fonts at runtime (see
228 "Can I switch the fonts at runtime?" later in this document).
174 229
175 Why does rxvt-unicode sometimes leave pixel droppings? 230 Why does rxvt-unicode sometimes leave pixel droppings?
176 Most fonts were not designed for terminal use, which means that 231 Most fonts were not designed for terminal use, which means that
177 character size varies a lot. A font that is otherwise fine for 232 character size varies a lot. A font that is otherwise fine for
178 terminal use might contain some characters that are simply too wide. 233 terminal use might contain some characters that are simply too wide.
… …
192 that doesn't work, you might be forced to use a different font. 247 that doesn't work, you might be forced to use a different font.
193 248
194 All of this is not a problem when using X11 core fonts, as their 249 All of this is not a problem when using X11 core fonts, as their
195 bounding box data is correct. 250 bounding box data is correct.
196 251
252 On Solaris 9, many line-drawing characters are too wide.
253 Seems to be a known bug, read
254 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
255 following ugly workaround to get non-double-wide-characters working:
256
257 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
258
197 My Compose (Multi_key) key is no longer working. 259 My Compose (Multi_key) key is no longer working.
198 The most common causes for this are that either your locale is not 260 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 261 set correctly, or you specified a preeditStyle that is not supported
200 by your input method. For example, if you specified OverTheSpot and 262 by your input method. For example, if you specified OverTheSpot and
201 your input method (e.g. the default input method handling Compose 263 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 274 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 275 other codes, too, such as "Ctrl-Shift-1-d" to type the default
214 telnet escape character and so on. 276 telnet escape character and so on.
215 277
216 How can I keep rxvt-unicode from using reverse video so much? 278 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 279 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 280 settings ("TERM=rxvt-unicode"), which will get rid of most of these
219 sure you have specified colours for italic and bold, as otherwise 281 effects. Then make sure you have specified colours for italic and
220 rxvt-unicode might use reverse video to simulate the effect: 282 bold, as otherwise rxvt-unicode might use reverse video to simulate
283 the effect:
221 284
222 URxvt*colorBD: white 285 URxvt.colorBD: white
223 URxvt*colorIT: green 286 URxvt.colorIT: green
224 287
225 Some programs assume totally weird colours (red instead of blue), how 288 Some programs assume totally weird colours (red instead of blue), how
226 can I fix that? 289 can I fix that?
227 For some unexplainable reason, some programs (i.e. irssi) assume a 290 For some unexplainable reason, some rare programs assume a very
228 very weird colour palette when confronted with a terminal with more 291 weird colour palette when confronted with a terminal with more than
229 than the standard 8 colours (rxvt-unicode supports 88). The right 292 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 293 of course, to fix these programs not to assume non-ISO colours
231 colours without very good reasons. 294 without very good reasons.
232 295
233 In the meantime, you can either edit your "urxvt" terminfo 296 In the meantime, you can either edit your "rxvt-unicode" terminfo
234 definition to only claim 8 colour support or use "TERM=rxvt", which 297 definition to only claim 8 colour support or use "TERM=rxvt", which
235 will fix colours but keep you from using other rxvt-unicode 298 will fix colours but keep you from using other rxvt-unicode
236 features. 299 features.
237 300
238 I am on FreeBSD and rxvt-unicode does not seem to work at all. 301 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__" 304 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
242 requires that wchar_t is represented as unicode. 305 requires that wchar_t is represented as unicode.
243 306
244 As you might have guessed, FreeBSD does neither define this symobl 307 As you might have guessed, FreeBSD does neither define this symobl
245 nor does it support it. Instead, it uses it's own internal 308 nor does it support it. Instead, it uses it's own internal
246 representation of wchar_t. This is, of course, completely legal. 309 representation of wchar_t. This is, of course, completely fine with
310 respect to standards.
247 311
312 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
313 and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
314
248 However, "__STDC_ISO_10646__" is the only sane way to support 315 "__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 316 apps in an OS, as using a locale-dependent (and non-standardized)
250 non-standardized) representation of wchar_t makes it impossible to 317 representation of wchar_t makes it impossible to convert between
251 convert between wchar_t (as used by X11 and your applications) and 318 wchar_t (as used by X11 and your applications) and any other
252 any other encoding without implementing OS-specific-wrappers for 319 encoding without implementing OS-specific-wrappers for each and
253 each and every locale. There simply are no APIs to convert wchar_t 320 every locale. There simply are no APIs to convert wchar_t into
254 into anything except the current locale encoding. 321 anything except the current locale encoding.
255 322
256 Some applications (such as the formidable mlterm) work around this 323 Some applications (such as the formidable mlterm) work around this
257 by carrying their own replacement functions for character set 324 by carrying their own replacement functions for character set
258 handling with them, and either implementing OS-dependent hacks or 325 handling with them, and either implementing OS-dependent hacks or
259 doing multiple conversions (which is slow and unreliable in case the 326 doing multiple conversions (which is slow and unreliable in case the
260 OS implements encodings slightly different than the terminal 327 OS implements encodings slightly different than the terminal
261 emulator). 328 emulator).
262 329
263 The rxvt-unicode author insists that the right way to fix this is in 330 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 331 the system libraries once and for all, instead of forcing every app
265 to carry complete replacements. 332 to carry complete replacements for them :)
333
334 I use Solaris 9 and it doesn't compile/work/etc.
335 Try the diff in doc/solaris9.patch as a base. It fixes the worst
336 problems with "wcwidth" and a compile problem.
266 337
267 How does rxvt-unicode determine the encoding to use? 338 How does rxvt-unicode determine the encoding to use?
268 Is there an option to switch encodings? 339 Is there an option to switch encodings?
269 Unlike some other terminals, rxvt-unicode has no encoding switch, 340 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 341 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
273 344
274 The reasons is that there exists a perfectly fine mechanism for 345 The reasons is that there exists a perfectly fine mechanism for
275 selecting the encoding, doing I/O and (most important) communicating 346 selecting the encoding, doing I/O and (most important) communicating
276 this to all applications so everybody agrees on character properties 347 this to all applications so everybody agrees on character properties
277 such as width and code number. This mechanism is the *locale*. 348 such as width and code number. This mechanism is the *locale*.
349 Applications not using that info will have problems (for example,
350 "xterm" gets the width of characters wrong as it uses it's own,
351 locale-independent table under all locales).
278 352
279 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 353 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
280 All programs doing the same (that is, most) will automatically agree 354 All programs doing the same (that is, most) will automatically agree
281 in the interpretation of characters. 355 in the interpretation of characters.
282 356
… …
290 "language_country.encoding", but other forms (i.e. "de" or "german") 364 "language_country.encoding", but other forms (i.e. "de" or "german")
291 are also common. 365 are also common.
292 366
293 Rxvt-unicode ignores all other locale categories, and except for the 367 Rxvt-unicode ignores all other locale categories, and except for the
294 encoding, ignores country or language-specific settings, i.e. 368 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. 369 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
370 rxvt-unicode.
296 371
297 If you want to use a specific encoding you have to make sure you 372 If you want to use a specific encoding you have to make sure you
298 start rxvt-unicode with the correct "LC_CTYPE" category. 373 start rxvt-unicode with the correct "LC_CTYPE" category.
299 374
300 Can I switch locales at runtime? 375 Can I switch locales at runtime?
301 Yes, using an escape sequence. Try sth. like this, which sets 376 Yes, using an escape sequence. Try something like this, which sets
302 rxvt-unicode's idea of "LC_CTYPE". 377 rxvt-unicode's idea of "LC_CTYPE".
303 378
304 printf '\e]701;%s\007' ja_JP.SJIS 379 printf '\e]701;%s\007' ja_JP.SJIS
305 380
306 See also the previous question. 381 See also the previous answer.
307 382
308 Sometimes this capability is rather handy when you want to work in 383 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 384 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 385 (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: 386 first switches to a locale supported by xjdic and back later:
312 387
313 printf '\e]701;%s\007' ja_JP.SJIS 388 printf '\e]701;%s\007' ja_JP.SJIS
314 xjdic -js 389 xjdic -js
315 printf '\e]701;%s\007' de_DE.UTF-8 390 printf '\e]701;%s\007' de_DE.UTF-8
316 391
392 You can also use xterm's "luit" program, which usually works fine,
393 except for some locales where character width differs between
394 program- and rxvt-unicode-locales.
395
317 Can I switch the fonts at runtime? 396 Can I switch the fonts at runtime?
318 Yes, using an escape sequence. Try sth. like this, which has the 397 Yes, using an escape sequence. Try something like this, which has
319 same effect as using the "-fn" switch, and takes effect immediately: 398 the same effect as using the "-fn" switch, and takes effect
399 immediately:
320 400
321 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 401 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
322 402
323 This is useful if you e.g. work primarily with japanese (and prefer 403 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, 404 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. 407 You can think of this as a kind of manual ISO-2022 switching.
328 408
329 Why do italic characters look as if clipped? 409 Why do italic characters look as if clipped?
330 Many fonts have difficulties with italic characters and hinting. For 410 Many fonts have difficulties with italic characters and hinting. For
331 example, the otherwise very nicely hinted font "xft:Bitstream Vera 411 example, the otherwise very nicely hinted font "xft:Bitstream Vera
332 Sans Mono" completely fails in it's italic face. A workaround is to 412 Sans Mono" completely fails in it's italic face. A workaround might
333 enable freetype autohinting, i.e. like this: 413 be to enable freetype autohinting, i.e. like this:
334 414
335 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 415 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
336 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 416 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
337 417
338 My input method wants <some encoding> but I want UTF-8, what can I do? 418 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 419 You can specify separate locales for the input method and the rest
340 of the terminal, using the resource "imlocale": 420 of the terminal, using the resource "imlocale":
341 421
… …
344 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 424 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 425 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, 426 be able to input characters outside "EUC-JP" in a normal way then,
347 as your input method limits you. 427 as your input method limits you.
348 428
429 Rxvt-unicode crashes when the X Input Method changes or exits.
430 Unfortunately, this is unavoidable, as the XIM protocol is racy by
431 design. Applications can avoid some crashes at the expense of memory
432 leaks, and Input Methods can avoid some crashes by careful ordering
433 at exit time. kinput2 (and derived input methods) generally
434 succeeds, while SCIM (or similar input methods) fails. In the end,
435 however, crashes cannot be completely avoided even if both sides
436 cooperate.
437
438 So the only workaround is not to kill your Input Method Servers.
439
349 Rxvt-unicode uses gobs of memory, how can I reduce that? 440 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 441 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 442 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 443 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 444 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 445 Xft font will be loaded accidentally when rxvt-unicode tries to find
355 characters. 446 a font for your characters.
356 447
357 Also, many people (me included) like large windows and even larger 448 Also, many people (me included) like large windows and even larger
358 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 449 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
359 use 6 bytes per screen cell. For a 160x?? window this amounts to 450 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 451 almost a kilobyte per line. A scrollback buffer of 10000 lines will
… …
404 resources (or as long-options). 495 resources (or as long-options).
405 496
406 Here are values that are supposed to resemble a VGA screen, 497 Here are values that are supposed to resemble a VGA screen,
407 including the murky brown that passes for low-intensity yellow: 498 including the murky brown that passes for low-intensity yellow:
408 499
409 URxvt*color0: #000000 500 URxvt.color0: #000000
410 URxvt*color1: #A80000 501 URxvt.color1: #A80000
411 URxvt*color2: #00A800 502 URxvt.color2: #00A800
412 URxvt*color3: #A8A800 503 URxvt.color3: #A8A800
413 URxvt*color4: #0000A8 504 URxvt.color4: #0000A8
414 URxvt*color5: #A800A8 505 URxvt.color5: #A800A8
415 URxvt*color6: #00A8A8 506 URxvt.color6: #00A8A8
416 URxvt*color7: #A8A8A8 507 URxvt.color7: #A8A8A8
417 508
418 URxvt*color8: #000054 509 URxvt.color8: #000054
419 URxvt*color9: #FF0054 510 URxvt.color9: #FF0054
420 URxvt*color10: #00FF54 511 URxvt.color10: #00FF54
421 URxvt*color11: #FFFF54 512 URxvt.color11: #FFFF54
422 URxvt*color12: #0000FF 513 URxvt.color12: #0000FF
423 URxvt*color13: #FF00FF 514 URxvt.color13: #FF00FF
424 URxvt*color14: #00FFFF 515 URxvt.color14: #00FFFF
425 URxvt*color15: #FFFFFF 516 URxvt.color15: #FFFFFF
426 517
427 And here is a more complete set of non-standard colors described as 518 And here is a more complete set of non-standard colors described
428 "pretty girly": 519 (not by me) as "pretty girly".
429 520
430 URxvt.cursorColor: #dc74d1 521 URxvt.cursorColor: #dc74d1
431 URxvt.pointerColor: #dc74d1 522 URxvt.pointerColor: #dc74d1
432 URxvt.background: #0e0e0e 523 URxvt.background: #0e0e0e
433 URxvt.foreground: #4ad5e1 524 URxvt.foreground: #4ad5e1
… …
444 URxvt.color6: #73f7ff 535 URxvt.color6: #73f7ff
445 URxvt.color14: #73f7ff 536 URxvt.color14: #73f7ff
446 URxvt.color7: #e1dddd 537 URxvt.color7: #e1dddd
447 URxvt.color15: #e1dddd 538 URxvt.color15: #e1dddd
448 539
540 How can I start rxvtd in a race-free way?
541 Despite it's name, rxvtd is not a real daemon, but more like a
542 server that answers rxvtc's requests, so it doesn't background
543 itself.
544
545 To ensure rxvtd is listening on it's socket, you can use the
546 following method to wait for the startup message before continuing:
547
548 { rxvtd & } | read
549
449 What's with the strange Backspace/Delete key behaviour? 550 What's with the strange Backspace/Delete key behaviour?
450 Assuming that the physical Backspace key corresponds to the 551 Assuming that the physical Backspace key corresponds to the
451 BackSpace keysym (not likely for Linux ... see the following 552 BackSpace keysym (not likely for Linux ... see the following
452 question) there are two standard values that can be used for 553 question) there are two standard values that can be used for
453 Backspace: "^H" and "^?". 554 Backspace: "^H" and "^?".
… …
471 572
472 # use Backspace = ^? 573 # use Backspace = ^?
473 $ stty erase ^? 574 $ stty erase ^?
474 $ rxvt 575 $ rxvt
475 576
476 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 577 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
477 578
478 For an existing rxvt-unicode: 579 For an existing rxvt-unicode:
479 580
480 # use Backspace = ^H 581 # use Backspace = ^H
481 $ stty erase ^H 582 $ stty erase ^H
… …
490 value properly reflects that. 591 value properly reflects that.
491 592
492 The Delete key is a another casualty of the ill-defined Backspace 593 The Delete key is a another casualty of the ill-defined Backspace
493 problem. To avoid confusion between the Backspace and Delete keys, 594 problem. To avoid confusion between the Backspace and Delete keys,
494 the Delete key has been assigned an escape sequence to match the 595 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. 596 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
597 termcap/terminfo.
496 598
497 Some other Backspace problems: 599 Some other Backspace problems:
498 600
499 some editors use termcap/terminfo, some editors (vim I'm told) 601 some editors use termcap/terminfo, some editors (vim I'm told)
500 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 602 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
506 There are some compile-time selections available via configure. 608 There are some compile-time selections available via configure.
507 Unless you have run "configure" with the "--disable-resources" 609 Unless you have run "configure" with the "--disable-resources"
508 option you can use the `keysym' resource to alter the keystrings 610 option you can use the `keysym' resource to alter the keystrings
509 associated with keysyms. 611 associated with keysyms.
510 612
511 Here's an example for a URxvt session started using `rxvt -name 613 Here's an example for a URxvt session started using "rxvt -name
512 URxvt' 614 URxvt"
513 615
514 URxvt*keysym.Home: \e[1~ 616 URxvt.keysym.Home: \033[1~
515 URxvt*keysym.End: \e[4~ 617 URxvt.keysym.End: \033[4~
516 URxvt*keysym.C-apostrophe: \e<C-'> 618 URxvt.keysym.C-apostrophe: \033<C-'>
517 URxvt*keysym.C-slash: \e<C-/> 619 URxvt.keysym.C-slash: \033<C-/>
518 URxvt*keysym.C-semicolon: \e<C-;> 620 URxvt.keysym.C-semicolon: \033<C-;>
519 URxvt*keysym.C-grave: \e<C-`> 621 URxvt.keysym.C-grave: \033<C-`>
520 URxvt*keysym.C-comma: \e<C-,> 622 URxvt.keysym.C-comma: \033<C-,>
521 URxvt*keysym.C-period: \e<C-.> 623 URxvt.keysym.C-period: \033<C-.>
522 URxvt*keysym.C-0x60: \e<C-`> 624 URxvt.keysym.C-0x60: \033<C-`>
523 URxvt*keysym.C-Tab: \e<C-Tab> 625 URxvt.keysym.C-Tab: \033<C-Tab>
524 URxvt*keysym.C-Return: \e<C-Return> 626 URxvt.keysym.C-Return: \033<C-Return>
525 URxvt*keysym.S-Return: \e<S-Return> 627 URxvt.keysym.S-Return: \033<S-Return>
526 URxvt*keysym.S-space: \e<S-Space> 628 URxvt.keysym.S-space: \033<S-Space>
527 URxvt*keysym.M-Up: \e<M-Up> 629 URxvt.keysym.M-Up: \033<M-Up>
528 URxvt*keysym.M-Down: \e<M-Down> 630 URxvt.keysym.M-Down: \033<M-Down>
529 URxvt*keysym.M-Left: \e<M-Left> 631 URxvt.keysym.M-Left: \033<M-Left>
530 URxvt*keysym.M-Right: \e<M-Right> 632 URxvt.keysym.M-Right: \033<M-Right>
531 URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.> 633 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
532 URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.> 634 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
533 URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007 635 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
636
637 See some more examples in the documentation for the keysym resource.
534 638
535 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 639 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 640 do I make use of them? For example, the Sun Keyboard type 4 has the
537 following mappings that rxvt-unicode doesn't recognize. 641 following mappings that rxvt-unicode doesn't recognize.
538 KP_Insert == Insert 642 KP_Insert == Insert
… …
544 648
545 Rather than have rxvt-unicode try to accommodate all the various 649 Rather than have rxvt-unicode try to accommodate all the various
546 possible keyboard mappings, it is better to use `xmodmap' to remap 650 possible keyboard mappings, it is better to use `xmodmap' to remap
547 the keys as required for your particular machine. 651 the keys as required for your particular machine.
548 652
549 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 653 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
550 need this to decide about setting colors etc. 654 I need this to decide about setting colors etc.
551 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 655 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, 656 can check and see if that is set. Note that several programs, JED,
553 slrn, Midnight Commander automatically check this variable to decide 657 slrn, Midnight Commander automatically check this variable to decide
554 whether or not to use color. 658 whether or not to use color.
555 659
… …
586 Before sending me mail, you could go to IRC: "irc.freenode.net", 690 Before sending me mail, you could go to IRC: "irc.freenode.net",
587 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might 691 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might
588 be interested in learning about new and exciting problems (but not 692 be interested in learning about new and exciting problems (but not
589 FAQs :). 693 FAQs :).
590 694
591SYNOPSIS 695RXVT 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 696DESCRIPTION
602 The rest of this document describes various technical aspects of 697 The rest of this document describes various technical aspects of
603 rxvt-unicode. First the description of supported command sequences, 698 rxvt-unicode. First the description of supported command sequences,
604 followed by menu and pixmap support and last by a description of all 699 followed by menu and pixmap support and last by a description of all
605 features selectable at "configure" time. 700 features selectable at "configure" time.
606 701
607RXVT TECHNICAL REFERENCE
608Definitions 702Definitions
609 "c" The literal character c. 703 "c" The literal character c.
610 704
611 "C" A single (required) character. 705 "C" A single (required) character.
612 706
… …
697 "ESC O" 791 "ESC O"
698 Single Shift Select of G3 Character Set (SS3): affects next 792 Single Shift Select of G3 Character Set (SS3): affects next
699 character only *unimplemented* 793 character only *unimplemented*
700 794
701 "ESC Z" 795 "ESC Z"
702 Obsolete form of returns: "ESC[?1;2C" *rxvt-unicode compile-time 796 Obsolete form of returns: "ESC [ ? 1 ; 2 C" *rxvt-unicode
703 option* 797 compile-time option*
704 798
705 "ESC c" 799 "ESC c"
706 Full reset (RIS) 800 Full reset (RIS)
707 801
708 "ESC n" 802 "ESC n"
709 Invoke the G2 Character Set (LS2) 803 Invoke the G2 Character Set (LS2)
710 804
711 "ESC o" 805 "ESC o"
712 Invoke the G3 Character Set (LS3) 806 Invoke the G3 Character Set (LS3)
713 807
714 "ESC" ( C> 808 "ESC ( C"
715 Designate G0 Character Set (ISO 2022), see below for values of "C". 809 Designate G0 Character Set (ISO 2022), see below for values of "C".
716 810
717 "ESC" ) C> 811 "ESC ) C"
718 Designate G1 Character Set (ISO 2022), see below for values of "C". 812 Designate G1 Character Set (ISO 2022), see below for values of "C".
719 813
720 "ESC * C" 814 "ESC * C"
721 Designate G2 Character Set (ISO 2022), see below for values of "C". 815 Designate G2 Character Set (ISO 2022), see below for values of "C".
722 816
… …
815 "ESC [ Ps a" 909 "ESC [ Ps a"
816 See "ESC [ Ps C" 910 See "ESC [ Ps C"
817 911
818 "ESC [ Ps c" 912 "ESC [ Ps c"
819 Send Device Attributes (DA) "Ps = 0" (or omitted): request 913 Send Device Attributes (DA) "Ps = 0" (or omitted): request
820 attributes from terminal returns: "ESC[?1;2c" (``I am a VT100 with 914 attributes from terminal returns: "ESC [ ? 1 ; 2 c" (``I am a VT100
821 Advanced Video Option'') 915 with Advanced Video Option'')
822 916
823 "ESC [ Ps d" 917 "ESC [ Ps d"
824 Cursor to Line "Ps" (VPA) 918 Cursor to Line "Ps" (VPA)
825 919
826 "ESC [ Ps e" 920 "ESC [ Ps e"
… …
900 (CSR) 994 (CSR)
901 995
902 "ESC [ s" 996 "ESC [ s"
903 Save Cursor (SC) 997 Save Cursor (SC)
904 998
999 "ESC [ Ps;Pt t"
1000 Window Operations
1001
1002 Ps = 1 Deiconify (map) window
1003 Ps = 2 Iconify window
1004 Ps = 3 ESC [ 3 ; X ; Y t Move window to (X|Y)
1005 Ps = 4 ESC [ 4 ; H ; W t Resize to WxH pixels
1006 Ps = 5 Raise window
1007 Ps = 6 Lower window
1008 Ps = 7 Refresh screen once
1009 Ps = 8 ESC [ 8 ; R ; C t Resize to R rows and C columns
1010 Ps = 11 Report window state (responds with Ps = 1 or Ps = 2)
1011 Ps = 13 Report window position (responds with Ps = 3)
1012 Ps = 14 Report window pixel size (responds with Ps = 4)
1013 Ps = 18 Report window text size (responds with Ps = 7)
1014 Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9
1015 Ps = 20 Reports icon label (ESC ] L NAME \234)
1016 Ps = 21 Reports window title (ESC ] l NAME \234)
1017 Ps = 24.. Set window height to Ps rows
1018
1019 "ESC [ u"
1020 Restore Cursor
1021
905 "ESC [ Ps x" 1022 "ESC [ Ps x"
906 Request Terminal Parameters (DECREQTPARM) 1023 Request Terminal Parameters (DECREQTPARM)
907
908 "ESC [ u"
909 Restore Cursor
910 1024
911 1025
912 1026
913DEC Private Modes 1027DEC Private Modes
914 "ESC [ ? Pm h" 1028 "ESC [ ? Pm h"
… …
1056 Ps = 13 Change colour of mouse foreground to Pt 1170 Ps = 13 Change colour of mouse foreground to Pt
1057 Ps = 17 Change colour of highlight characters to Pt 1171 Ps = 17 Change colour of highlight characters to Pt
1058 Ps = 18 Change colour of bold characters to Pt 1172 Ps = 18 Change colour of bold characters to Pt
1059 Ps = 19 Change colour of underlined characters to Pt 1173 Ps = 19 Change colour of underlined characters to Pt
1060 Ps = 20 Change default background to Pt 1174 Ps = 20 Change default background to Pt
1061 Ps = 39 Change default foreground colour to Pt rxvt compile-time option 1175 Ps = 39 Change default foreground colour to Pt.
1062 Ps = 46 Change Log File to Pt unimplemented 1176 Ps = 46 Change Log File to Pt unimplemented
1063 Ps = 49 Change default background colour to Pt rxvt compile-time option 1177 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 1178 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 1179 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) 1180 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) 1181 Ps = 703 Menubar command Pt (Compile menubar).
1068 Ps = 704 Change colour of italic characters to Pt 1182 Ps = 704 Change colour of italic characters to Pt
1069 Ps = 705 Change background pixmap tint colour to Pt 1183 Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1070 Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1184 Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
1071 Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. 1185 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. 1186 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. 1187 Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1188 Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1189 Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1074 1190
1075 1191
1076 1192
1077menuBar 1193menuBar
1078 The exact syntax used is *almost* solidified. In the menus, DON'T try to 1194 The exact syntax used is *almost* solidified. In the menus, DON'T try to
… …
1115 [menu] 1231 [menu]
1116 access the current menuBar for alteration 1232 access the current menuBar for alteration
1117 1233
1118 [title:+*string*] 1234 [title:+*string*]
1119 set the current menuBar's title to *string*, which may contain the 1235 set the current menuBar's title to *string*, which may contain the
1120 following format specifiers: %% : literal % character %n : rxvt name 1236 following format specifiers:
1121 (as per the -name command-line option) %v : rxvt version 1237
1238 B<%n> rxvt name (as per the B<-name> command-line option)
1239 B<%v> rxvt version
1240 B<%%> literal B<%> character
1122 1241
1123 [done] 1242 [done]
1124 set menuBar access as readonly. End-of-file tag for [read:+*file*] 1243 set menuBar access as readonly. End-of-file tag for [read:+*file*]
1125 operations. 1244 operations.
1126 1245
… …
1230 1349
1231 As a convenience for the many Emacs-type editors, *action* may start 1350 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 1351 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if
1233 missed from M-x commands. 1352 missed from M-x commands.
1234 1353
1235 As a convenience for issuing XTerm ESC] sequences from a menubar (or 1354 As a convenience for issuing XTerm ESC ] sequences from a menubar (or
1236 quick arrow), a BEL (^G) will be appended if needed. 1355 quick arrow), a BEL (^G) will be appended if needed.
1237 1356
1238 For example, 1357 For example,
1239 M-xapropos is equivalent to \Exapropos\r 1358 M-xapropos is equivalent to \Exapropos\r
1240 1359
… …
1562 --enable-font-styles 1681 --enable-font-styles
1563 Add support for bold, *italic* and *bold italic* font styles. The 1682 Add support for bold, *italic* and *bold italic* font styles. The
1564 fonts can be set manually or automatically. 1683 fonts can be set manually or automatically.
1565 1684
1566 --with-codesets=NAME,... 1685 --with-codesets=NAME,...
1567 Compile in support for additional codeset (encoding) groups (eu, vn 1686 Compile in support for additional codeset (encoding) groups ("eu",
1568 are always compiled in, which includes most 8-bit character sets). 1687 "vn" are always compiled in, which includes most 8-bit character
1569 These codeset tables are currently only used for driving X11 core 1688 sets). These codeset tables are used for driving X11 core fonts,
1570 fonts, they are not required for Xft fonts. Compiling them in will 1689 they are not required for Xft fonts, although having them compiled
1571 make your binary bigger (together about 700kB), but it doesn't 1690 in lets rxvt-unicode choose replacement fonts more intelligently.
1572 increase memory usage unless you use an X11 font requiring one of 1691 Compiling them in will make your binary bigger (all of together cost
1573 these encodings. 1692 about 700kB), but it doesn't increase memory usage unless you use a
1693 font requiring one of these encodings.
1574 1694
1575 all all available codeset groups 1695 all all available codeset groups
1576 zh common chinese encodings 1696 zh common chinese encodings
1577 zh_ext rarely used but very big chinese encodigs 1697 zh_ext rarely used but very big chinese encodigs
1578 jp common japanese encodings 1698 jp common japanese encodings
… …
1602 accents are encoded as seperate unicode characters. This is done by 1722 accents are encoded as seperate unicode characters. This is done by
1603 using precomposited characters when available or creating new 1723 using precomposited characters when available or creating new
1604 pseudo-characters when no precomposed form exists. 1724 pseudo-characters when no precomposed form exists.
1605 1725
1606 Without --enable-unicode3, the number of additional precomposed 1726 Without --enable-unicode3, the number of additional precomposed
1607 characters is rather limited (2048, if this is full, rxvt will use 1727 characters is rather limited (2048, if this is full, rxvt-unicode
1608 the private use area, extending the number of combinations to 8448). 1728 will use the private use area, extending the number of combinations
1609 With --enable-unicode3, no practical limit exists. This will also 1729 to 8448). With --enable-unicode3, no practical limit exists.
1610 enable storage of characters >65535. 1730
1731 This option will also enable storage (but not display) of characters
1732 beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1611 1733
1612 The combining table also contains entries for arabic presentation 1734 The combining table also contains entries for arabic presentation
1613 forms, but these are not currently used. Bug me if you want these to 1735 forms, but these are not currently used. Bug me if you want these to
1614 be used. 1736 be used (and tell me how these are to be used...).
1615 1737
1616 --enable-fallback(=CLASS) 1738 --enable-fallback(=CLASS)
1617 When reading resource settings, also read settings for class CLASS 1739 When reading resource settings, also read settings for class CLASS
1618 (default: Rxvt). To disable resource fallback use 1740 (default: Rxvt). To disable resource fallback use
1619 --disable-fallback. 1741 --disable-fallback.
… …
1693 1815
1694 --enable-xgetdefault 1816 --enable-xgetdefault
1695 Make resources checking via XGetDefault() instead of our small 1817 Make resources checking via XGetDefault() instead of our small
1696 version which only checks ~/.Xdefaults, or if that doesn't exist 1818 version which only checks ~/.Xdefaults, or if that doesn't exist
1697 then ~/.Xresources. 1819 then ~/.Xresources.
1820
1821 Please note that nowadays, things like XIM will automatically pull
1822 in and use the full X resource manager, so the overhead of using it
1823 might be very small, if nonexistant.
1698 1824
1699 --enable-strings 1825 --enable-strings
1700 Add support for our possibly faster memset() function and other 1826 Add support for our possibly faster memset() function and other
1701 various routines, overriding your system's versions which may have 1827 various routines, overriding your system's versions which may have
1702 been hand-crafted in assembly or may require extra libraries to link 1828 been hand-crafted in assembly or may require extra libraries to link
… …
1713 1839
1714 A non-exhaustive list of features enabled by "--enable-frills" 1840 A non-exhaustive list of features enabled by "--enable-frills"
1715 (possibly in combination with other switches) is: 1841 (possibly in combination with other switches) is:
1716 1842
1717 MWM-hints 1843 MWM-hints
1844 EWMH-hints (pid, utf8 names) and protocols (ping)
1718 seperate underline colour 1845 seperate underline colour
1719 settable border widths and borderless switch 1846 settable border widths and borderless switch
1720 settable extra linespacing 1847 settable extra linespacing
1721 extra window properties (e.g. UTF-8 window names and PID)
1722 iso-14755-2 and -3, and visual feedback 1848 iso-14755-2 and -3, and visual feedback
1723 backindex and forwardindex escape sequence 1849 backindex and forwardindex escape sequence
1724 window op and locale change escape sequences 1850 window op and some xterm/OSC escape sequences
1725 tripleclickwords 1851 tripleclickwords
1726 settable insecure mode 1852 settable insecure mode
1853 keysym remapping support
1854 cursor blinking and underline cursor
1855 -embed and -pty-fd options
1727 1856
1728 --enable-iso14755 1857 --enable-iso14755
1729 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). 1858 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
1730 Basic support (section 5.1) is enabled by "--enable-frills", while 1859 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. 1860 support for 5.2, 5.3 and 5.4 is enabled with this switch.
… …
1761 --enable-smart-resize 1890 --enable-smart-resize
1762 Add smart growth/shrink behaviour when changing font size via from 1891 Add smart growth/shrink behaviour when changing font size via from
1763 hot keys. This should keep in a fixed position the rxvt corner which 1892 hot keys. This should keep in a fixed position the rxvt corner which
1764 is closest to a corner of the screen. 1893 is closest to a corner of the screen.
1765 1894
1766 --enable-cursor-blink
1767 Add support for a blinking cursor.
1768
1769 --enable-pointer-blank 1895 --enable-pointer-blank
1770 Add support to have the pointer disappear when typing or inactive. 1896 Add support to have the pointer disappear when typing or inactive.
1771 1897
1772 --with-name=NAME 1898 --with-name=NAME
1773 Set the basename for the installed binaries (default: "urxvt", 1899 Set the basename for the installed binaries (default: "urxvt",

Diff Legend

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