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.14 by root, Mon Feb 14 18:47:54 2005 UTC

1NAME 1NAME
2 RXVT REFERENCE - FAQ, command sequences and other background information 2 RXVT REFERENCE - FAQ, command sequences and other background information
3
4SYNOPSIS
5 # set a new font set
6 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
7
8 # change the locale and tell rxvt-unicode about it
9 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
10
11 # set window title
12 printf '\33]2;%s\007' "new window title"
13
14DESCRIPTION
15 This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
16 all escape sequences, and other background information.
17
18 The newest version of this document is also available on the World Wide
19 Web at
20 <http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
3 21
4FREQUENTLY ASKED QUESTIONS 22FREQUENTLY ASKED QUESTIONS
5 How do I know which rxvt-unicode version I'm using? 23 How do I know which rxvt-unicode version I'm using?
6 The version number is displayed with the usage (-h). Also the escape 24 The version number is displayed with the usage (-h). Also the escape
7 sequence "ESC[8n" sets the window title to the version number. 25 sequence "ESC [ 8 n" sets the window title to the version number.
26
27 I am using Debian GNU/Linux and have a problem...
28 The Debian GNU/Linux package of rxvt-unicode 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=^O: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=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\
53 :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ 93 :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\
54 :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ 94 :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\
55 :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ 95 :im=\E[4h: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~:\ 96 :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~:\ 97 :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:\ 98 :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=:\ 99 :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:\ 100 :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:\ 101 :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:\ 102 :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:\ 103 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
64 :vs=\E[?25h: 104 :vs=\E[?25h:
65 105
66 Why does "ls" no longer have coloured output? 106 Why does "ls" no longer have coloured output?
67 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 107 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 108 decide wether a terminal has colour, but uses it's own configuration
… …
87 furthermore fail to even install the "rxvt-unicode" terminfo file, 127 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 128 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 129 log-in to another system it tells me about missing terminfo data? on
90 how to do this). 130 how to do this).
91 131
132 My numerical keypad acts weird and generates differing output?
133 Some Debian GNUL/Linux users seem to have this problem, although no
134 specific details were reported so far. It is possible that this is
135 caused by the wrong "TERM" setting, although the details of wether
136 and how this can happen are unknown, as "TERM=rxvt" should offer a
137 compatible keymap. See the answer to the previous question, and
138 please report if that helped.
139
92 Rxvt-unicode does not seem to understand the selected encoding? 140 Rxvt-unicode does not seem to understand the selected encoding?
93 Unicode does not seem to work? 141 Unicode does not seem to work?
94 If you encounter strange problems like typing an accented character 142 If you encounter strange problems like typing an accented character
95 but getting two unrelated other characters or similar, or if program 143 but getting two unrelated other characters or similar, or if program
96 output is subtly garbled, then you should check your locale 144 output is subtly garbled, then you should check your locale
97 settings. 145 settings.
98 146
99 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 147 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 148 programs. Often rxvt-unicode is started in the "C" locale, while the
101 login script running within the rxvt-unicode window changes the 149 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 150 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
103 not going to work. 151 is not going to work.
104 152
105 The best thing is to fix your startup environment, as you will 153 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 154 likely run into other problems. If nothing works you can try this in
107 your .profile. 155 your .profile.
108 156
109 printf '\e]701;%s\007' "$LC_CTYPE" 157 printf '\e]701;%s\007' "$LC_CTYPE"
110 158
111 If this doesn't work, then maybe you use a "LC_CTYPE" specification 159 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 160 not supported on your systems. Some systems have a "locale" command
113 which displays this. If it displays sth. like: 161 which displays this (also, "perl -e0" can be used to check locale
162 settings, as it will complain loudly if it cannot set the locale).
163 If it displays something like:
114 164
115 locale: Cannot set LC_CTYPE to default locale: ... 165 locale: Cannot set LC_CTYPE to default locale: ...
116 166
117 Then the locale you specified is not supported on your system. 167 Then the locale you specified is not supported on your system.
118 168
… …
126 Chances are that the font you (or the admin/package maintainer of 176 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 177 your system/os) have specified does not cover all the characters you
128 want to display. 178 want to display.
129 179
130 rxvt-unicode makes a best-effort try at finding a replacement font. 180 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. 181 Often the result is fine, but sometimes the chosen font looks
132 Many fonts have totally strange characters that don't resemble the 182 bad/ugly/wrong. Some fonts have totally strange characters that
133 correct glyph at all, and rxvt-unicode lacks the artificial 183 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 184 artificial intelligence to detect that a specific glyph is wrong: it
135 believe the font that the characters it contains indeed look 185 has to believe the font that the characters it claims to contain
136 correct. 186 indeed look correct.
137 187
138 In that case, select a font of your taste and add it to the font 188 In that case, select a font of your taste and add it to the font
139 list, e.g.: 189 list, e.g.:
140 190
141 rxvt -fn basefont,font2,font3... 191 rxvt -fn basefont,font2,font3...
… …
144 font. If the base font does not contain the character, it will go to 194 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 195 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 196 up this search and use less resources within rxvt-unicode and the
147 X-server. 197 X-server.
148 198
149 The only limitation is that all the fonts must not be larger than 199 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, 200 base font, as the base font defines the terminal character cell
151 which must be the same due to the way terminals work. 201 size, which must be the same due to the way terminals work.
152 202
153 Why do some chinese characters look so different than others? 203 Why do some chinese characters look so different than others?
154 This is because there is a difference between script and language -- 204 This is because there is a difference between script and language --
155 rxvt-unicode does not know which language the text that is output 205 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 206 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 207 first sees a japanese/chinese character, it might choose a japanese
158 it. Subsequent japanese characters will take that font. Now, many 208 font for display. Subsequent japanese characters will use that font.
159 chinese characters aren't represented in japanese fonts, so when the 209 Now, many chinese characters aren't represented in japanese fonts,
160 first non-japanese character comes up, rxvt-unicode will look for a 210 so when the first non-japanese character comes up, rxvt-unicode will
161 chinese font -- unfortunately at this point, it will still use the 211 look for a chinese font -- unfortunately at this point, it will
162 japanese font for japanese characters that are also chinese. 212 still use the japanese font for chinese characters that are also in
213 the japanese font.
163 214
164 The workaround is easy: just tag a chinese font at the end of your 215 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 216 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 217 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 218 japanese font first. If you expect more chinese, put a chinese font
168 first. 219 first.
169 220
170 In the future it might be possible to switch preferences at runtime 221 In the future it might be possible to switch language preferences at
171 (the internal data structure has no problem with using different 222 runtime (the internal data structure has no problem with using
172 fonts for the same character at the same time, but no interface for 223 different fonts for the same character at the same time, but no
173 this has been designed yet). 224 interface for this has been designed yet).
225
226 Until then, you might get away with switching fonts at runtime (see
227 "Can I switch the fonts at runtime?" later in this document).
174 228
175 Why does rxvt-unicode sometimes leave pixel droppings? 229 Why does rxvt-unicode sometimes leave pixel droppings?
176 Most fonts were not designed for terminal use, which means that 230 Most fonts were not designed for terminal use, which means that
177 character size varies a lot. A font that is otherwise fine for 231 character size varies a lot. A font that is otherwise fine for
178 terminal use might contain some characters that are simply too wide. 232 terminal use might contain some characters that are simply too wide.
… …
212 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for 266 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 267 other codes, too, such as "Ctrl-Shift-1-d" to type the default
214 telnet escape character and so on. 268 telnet escape character and so on.
215 269
216 How can I keep rxvt-unicode from using reverse video so much? 270 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 271 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 272 settings ("TERM=rxvt-unicode"), which will get rid of most of these
219 sure you have specified colours for italic and bold, as otherwise 273 effects. Then make sure you have specified colours for italic and
220 rxvt-unicode might use reverse video to simulate the effect: 274 bold, as otherwise rxvt-unicode might use reverse video to simulate
275 the effect:
221 276
222 URxvt*colorBD: white 277 URxvt.colorBD: white
223 URxvt*colorIT: green 278 URxvt.colorIT: green
224 279
225 Some programs assume totally weird colours (red instead of blue), how 280 Some programs assume totally weird colours (red instead of blue), how
226 can I fix that? 281 can I fix that?
227 For some unexplainable reason, some programs (i.e. irssi) assume a 282 For some unexplainable reason, some rare programs assume a very
228 very weird colour palette when confronted with a terminal with more 283 weird colour palette when confronted with a terminal with more than
229 than the standard 8 colours (rxvt-unicode supports 88). The right 284 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 285 of course, to fix these programs not to assume non-ISO colours
231 colours without very good reasons. 286 without very good reasons.
232 287
233 In the meantime, you can either edit your "urxvt" terminfo 288 In the meantime, you can either edit your "rxvt-unicode" terminfo
234 definition to only claim 8 colour support or use "TERM=rxvt", which 289 definition to only claim 8 colour support or use "TERM=rxvt", which
235 will fix colours but keep you from using other rxvt-unicode 290 will fix colours but keep you from using other rxvt-unicode
236 features. 291 features.
237 292
238 I am on FreeBSD and rxvt-unicode does not seem to work at all. 293 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__" 296 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
242 requires that wchar_t is represented as unicode. 297 requires that wchar_t is represented as unicode.
243 298
244 As you might have guessed, FreeBSD does neither define this symobl 299 As you might have guessed, FreeBSD does neither define this symobl
245 nor does it support it. Instead, it uses it's own internal 300 nor does it support it. Instead, it uses it's own internal
246 representation of wchar_t. This is, of course, completely legal. 301 representation of wchar_t. This is, of course, completely fine with
302 respect to standards.
247 303
248 However, "__STDC_ISO_10646__" is the only sane way to support 304 However, "__STDC_ISO_10646__" is the only sane way to support
249 multi-language apps in an OS, as using a locale-dependent (and 305 multi-language apps in an OS, as using a locale-dependent (and
250 non-standardized) representation of wchar_t makes it impossible to 306 non-standardized) representation of wchar_t makes it impossible to
251 convert between wchar_t (as used by X11 and your applications) and 307 convert between wchar_t (as used by X11 and your applications) and
… …
260 OS implements encodings slightly different than the terminal 316 OS implements encodings slightly different than the terminal
261 emulator). 317 emulator).
262 318
263 The rxvt-unicode author insists that the right way to fix this is in 319 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 320 the system libraries once and for all, instead of forcing every app
265 to carry complete replacements. 321 to carry complete replacements for them :)
266 322
267 How does rxvt-unicode determine the encoding to use? 323 How does rxvt-unicode determine the encoding to use?
268 Is there an option to switch encodings? 324 Is there an option to switch encodings?
269 Unlike some other terminals, rxvt-unicode has no encoding switch, 325 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 326 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
273 329
274 The reasons is that there exists a perfectly fine mechanism for 330 The reasons is that there exists a perfectly fine mechanism for
275 selecting the encoding, doing I/O and (most important) communicating 331 selecting the encoding, doing I/O and (most important) communicating
276 this to all applications so everybody agrees on character properties 332 this to all applications so everybody agrees on character properties
277 such as width and code number. This mechanism is the *locale*. 333 such as width and code number. This mechanism is the *locale*.
334 Applications not using that info will have problems (for example,
335 "xterm" gets the width of characters wrong as it uses it's own,
336 locale-independent table under all locales).
278 337
279 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 338 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
280 All programs doing the same (that is, most) will automatically agree 339 All programs doing the same (that is, most) will automatically agree
281 in the interpretation of characters. 340 in the interpretation of characters.
282 341
… …
290 "language_country.encoding", but other forms (i.e. "de" or "german") 349 "language_country.encoding", but other forms (i.e. "de" or "german")
291 are also common. 350 are also common.
292 351
293 Rxvt-unicode ignores all other locale categories, and except for the 352 Rxvt-unicode ignores all other locale categories, and except for the
294 encoding, ignores country or language-specific settings, i.e. 353 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. 354 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
355 rxvt-unicode.
296 356
297 If you want to use a specific encoding you have to make sure you 357 If you want to use a specific encoding you have to make sure you
298 start rxvt-unicode with the correct "LC_CTYPE" category. 358 start rxvt-unicode with the correct "LC_CTYPE" category.
299 359
300 Can I switch locales at runtime? 360 Can I switch locales at runtime?
301 Yes, using an escape sequence. Try sth. like this, which sets 361 Yes, using an escape sequence. Try something like this, which sets
302 rxvt-unicode's idea of "LC_CTYPE". 362 rxvt-unicode's idea of "LC_CTYPE".
303 363
304 printf '\e]701;%s\007' ja_JP.SJIS 364 printf '\e]701;%s\007' ja_JP.SJIS
305 365
306 See also the previous question. 366 See also the previous answer.
307 367
308 Sometimes this capability is rather handy when you want to work in 368 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 369 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 370 (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: 371 first switches to a locale supported by xjdic and back later:
312 372
313 printf '\e]701;%s\007' ja_JP.SJIS 373 printf '\e]701;%s\007' ja_JP.SJIS
314 xjdic -js 374 xjdic -js
315 printf '\e]701;%s\007' de_DE.UTF-8 375 printf '\e]701;%s\007' de_DE.UTF-8
316 376
377 You can also use xterm's "luit" program, which usually works fine,
378 except for some locales where character width differs between
379 program- and rxvt-unicode-locales.
380
317 Can I switch the fonts at runtime? 381 Can I switch the fonts at runtime?
318 Yes, using an escape sequence. Try sth. like this, which has the 382 Yes, using an escape sequence. Try something like this, which has
319 same effect as using the "-fn" switch, and takes effect immediately: 383 the same effect as using the "-fn" switch, and takes effect
384 immediately:
320 385
321 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 386 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
322 387
323 This is useful if you e.g. work primarily with japanese (and prefer 388 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, 389 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. 392 You can think of this as a kind of manual ISO-2022 switching.
328 393
329 Why do italic characters look as if clipped? 394 Why do italic characters look as if clipped?
330 Many fonts have difficulties with italic characters and hinting. For 395 Many fonts have difficulties with italic characters and hinting. For
331 example, the otherwise very nicely hinted font "xft:Bitstream Vera 396 example, the otherwise very nicely hinted font "xft:Bitstream Vera
332 Sans Mono" completely fails in it's italic face. A workaround is to 397 Sans Mono" completely fails in it's italic face. A workaround might
333 enable freetype autohinting, i.e. like this: 398 be to enable freetype autohinting, i.e. like this:
334 399
335 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 400 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
336 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 401 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
337 402
338 My input method wants <some encoding> but I want UTF-8, what can I do? 403 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 404 You can specify separate locales for the input method and the rest
340 of the terminal, using the resource "imlocale": 405 of the terminal, using the resource "imlocale":
341 406
… …
344 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 409 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 410 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, 411 be able to input characters outside "EUC-JP" in a normal way then,
347 as your input method limits you. 412 as your input method limits you.
348 413
414 Rxvt-unicode crashes when the X Input Method changes or exits.
415 Unfortunately, this is unavoidable, as the XIM protocol is racy by
416 design. Applications can avoid some crashes at the expense of memory
417 leaks, and Input Methods can avoid some crashes by careful ordering
418 at exit time. kinput2 (and derived input methods) generally
419 succeeds, while SCIM (or similar input methods) fails. In the end,
420 however, crashes cannot be completely avoided even if both sides
421 cooperate.
422
423 So the only workaround is not to kill your Input Method Servers.
424
349 Rxvt-unicode uses gobs of memory, how can I reduce that? 425 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 426 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 427 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 428 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 429 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 430 Xft font will be loaded accidentally when rxvt-unicode tries to find
355 characters. 431 a font for your characters.
356 432
357 Also, many people (me included) like large windows and even larger 433 Also, many people (me included) like large windows and even larger
358 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 434 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
359 use 6 bytes per screen cell. For a 160x?? window this amounts to 435 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 436 almost a kilobyte per line. A scrollback buffer of 10000 lines will
… …
404 resources (or as long-options). 480 resources (or as long-options).
405 481
406 Here are values that are supposed to resemble a VGA screen, 482 Here are values that are supposed to resemble a VGA screen,
407 including the murky brown that passes for low-intensity yellow: 483 including the murky brown that passes for low-intensity yellow:
408 484
409 URxvt*color0: #000000 485 URxvt.color0: #000000
410 URxvt*color1: #A80000 486 URxvt.color1: #A80000
411 URxvt*color2: #00A800 487 URxvt.color2: #00A800
412 URxvt*color3: #A8A800 488 URxvt.color3: #A8A800
413 URxvt*color4: #0000A8 489 URxvt.color4: #0000A8
414 URxvt*color5: #A800A8 490 URxvt.color5: #A800A8
415 URxvt*color6: #00A8A8 491 URxvt.color6: #00A8A8
416 URxvt*color7: #A8A8A8 492 URxvt.color7: #A8A8A8
417 493
418 URxvt*color8: #000054 494 URxvt.color8: #000054
419 URxvt*color9: #FF0054 495 URxvt.color9: #FF0054
420 URxvt*color10: #00FF54 496 URxvt.color10: #00FF54
421 URxvt*color11: #FFFF54 497 URxvt.color11: #FFFF54
422 URxvt*color12: #0000FF 498 URxvt.color12: #0000FF
423 URxvt*color13: #FF00FF 499 URxvt.color13: #FF00FF
424 URxvt*color14: #00FFFF 500 URxvt.color14: #00FFFF
425 URxvt*color15: #FFFFFF 501 URxvt.color15: #FFFFFF
426 502
427 And here is a more complete set of non-standard colors described as 503 And here is a more complete set of non-standard colors described
428 "pretty girly": 504 (not by me) as "pretty girly".
429 505
430 URxvt.cursorColor: #dc74d1 506 URxvt.cursorColor: #dc74d1
431 URxvt.pointerColor: #dc74d1 507 URxvt.pointerColor: #dc74d1
432 URxvt.background: #0e0e0e 508 URxvt.background: #0e0e0e
433 URxvt.foreground: #4ad5e1 509 URxvt.foreground: #4ad5e1
… …
444 URxvt.color6: #73f7ff 520 URxvt.color6: #73f7ff
445 URxvt.color14: #73f7ff 521 URxvt.color14: #73f7ff
446 URxvt.color7: #e1dddd 522 URxvt.color7: #e1dddd
447 URxvt.color15: #e1dddd 523 URxvt.color15: #e1dddd
448 524
525 How can I start rxvtd in a race-free way?
526 Despite it's name, rxvtd is not a real daemon, but more like a
527 server that answers rxvtc's requests, so it doesn't background
528 itself.
529
530 To ensure rxvtd is listening on it's socket, you can use the
531 following method to wait for the startup message before continuing:
532
533 { rxvtd & } | read
534
449 What's with the strange Backspace/Delete key behaviour? 535 What's with the strange Backspace/Delete key behaviour?
450 Assuming that the physical Backspace key corresponds to the 536 Assuming that the physical Backspace key corresponds to the
451 BackSpace keysym (not likely for Linux ... see the following 537 BackSpace keysym (not likely for Linux ... see the following
452 question) there are two standard values that can be used for 538 question) there are two standard values that can be used for
453 Backspace: "^H" and "^?". 539 Backspace: "^H" and "^?".
… …
471 557
472 # use Backspace = ^? 558 # use Backspace = ^?
473 $ stty erase ^? 559 $ stty erase ^?
474 $ rxvt 560 $ rxvt
475 561
476 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 562 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
477 563
478 For an existing rxvt-unicode: 564 For an existing rxvt-unicode:
479 565
480 # use Backspace = ^H 566 # use Backspace = ^H
481 $ stty erase ^H 567 $ stty erase ^H
… …
490 value properly reflects that. 576 value properly reflects that.
491 577
492 The Delete key is a another casualty of the ill-defined Backspace 578 The Delete key is a another casualty of the ill-defined Backspace
493 problem. To avoid confusion between the Backspace and Delete keys, 579 problem. To avoid confusion between the Backspace and Delete keys,
494 the Delete key has been assigned an escape sequence to match the 580 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. 581 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
582 termcap/terminfo.
496 583
497 Some other Backspace problems: 584 Some other Backspace problems:
498 585
499 some editors use termcap/terminfo, some editors (vim I'm told) 586 some editors use termcap/terminfo, some editors (vim I'm told)
500 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 587 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
506 There are some compile-time selections available via configure. 593 There are some compile-time selections available via configure.
507 Unless you have run "configure" with the "--disable-resources" 594 Unless you have run "configure" with the "--disable-resources"
508 option you can use the `keysym' resource to alter the keystrings 595 option you can use the `keysym' resource to alter the keystrings
509 associated with keysyms. 596 associated with keysyms.
510 597
511 Here's an example for a URxvt session started using `rxvt -name 598 Here's an example for a URxvt session started using "rxvt -name
512 URxvt' 599 URxvt"
513 600
514 URxvt*keysym.Home: \e[1~ 601 URxvt.keysym.Home: \033[1~
515 URxvt*keysym.End: \e[4~ 602 URxvt.keysym.End: \033[4~
516 URxvt*keysym.C-apostrophe: \e<C-'> 603 URxvt.keysym.C-apostrophe: \033<C-'>
517 URxvt*keysym.C-slash: \e<C-/> 604 URxvt.keysym.C-slash: \033<C-/>
518 URxvt*keysym.C-semicolon: \e<C-;> 605 URxvt.keysym.C-semicolon: \033<C-;>
519 URxvt*keysym.C-grave: \e<C-`> 606 URxvt.keysym.C-grave: \033<C-`>
520 URxvt*keysym.C-comma: \e<C-,> 607 URxvt.keysym.C-comma: \033<C-,>
521 URxvt*keysym.C-period: \e<C-.> 608 URxvt.keysym.C-period: \033<C-.>
522 URxvt*keysym.C-0x60: \e<C-`> 609 URxvt.keysym.C-0x60: \033<C-`>
523 URxvt*keysym.C-Tab: \e<C-Tab> 610 URxvt.keysym.C-Tab: \033<C-Tab>
524 URxvt*keysym.C-Return: \e<C-Return> 611 URxvt.keysym.C-Return: \033<C-Return>
525 URxvt*keysym.S-Return: \e<S-Return> 612 URxvt.keysym.S-Return: \033<S-Return>
526 URxvt*keysym.S-space: \e<S-Space> 613 URxvt.keysym.S-space: \033<S-Space>
527 URxvt*keysym.M-Up: \e<M-Up> 614 URxvt.keysym.M-Up: \033<M-Up>
528 URxvt*keysym.M-Down: \e<M-Down> 615 URxvt.keysym.M-Down: \033<M-Down>
529 URxvt*keysym.M-Left: \e<M-Left> 616 URxvt.keysym.M-Left: \033<M-Left>
530 URxvt*keysym.M-Right: \e<M-Right> 617 URxvt.keysym.M-Right: \033<M-Right>
531 URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.> 618 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
532 URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.> 619 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
533 URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007 620 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
621
622 See some more examples in the documentation for the keysym resource.
534 623
535 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 624 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 625 do I make use of them? For example, the Sun Keyboard type 4 has the
537 following mappings that rxvt-unicode doesn't recognize. 626 following mappings that rxvt-unicode doesn't recognize.
538 KP_Insert == Insert 627 KP_Insert == Insert
… …
544 633
545 Rather than have rxvt-unicode try to accommodate all the various 634 Rather than have rxvt-unicode try to accommodate all the various
546 possible keyboard mappings, it is better to use `xmodmap' to remap 635 possible keyboard mappings, it is better to use `xmodmap' to remap
547 the keys as required for your particular machine. 636 the keys as required for your particular machine.
548 637
549 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 638 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
550 need this to decide about setting colors etc. 639 I need this to decide about setting colors etc.
551 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 640 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, 641 can check and see if that is set. Note that several programs, JED,
553 slrn, Midnight Commander automatically check this variable to decide 642 slrn, Midnight Commander automatically check this variable to decide
554 whether or not to use color. 643 whether or not to use color.
555 644
… …
586 Before sending me mail, you could go to IRC: "irc.freenode.net", 675 Before sending me mail, you could go to IRC: "irc.freenode.net",
587 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might 676 channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might
588 be interested in learning about new and exciting problems (but not 677 be interested in learning about new and exciting problems (but not
589 FAQs :). 678 FAQs :).
590 679
591SYNOPSIS 680RXVT 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 681DESCRIPTION
602 The rest of this document describes various technical aspects of 682 The rest of this document describes various technical aspects of
603 rxvt-unicode. First the description of supported command sequences, 683 rxvt-unicode. First the description of supported command sequences,
604 followed by menu and pixmap support and last by a description of all 684 followed by menu and pixmap support and last by a description of all
605 features selectable at "configure" time. 685 features selectable at "configure" time.
606 686
607RXVT TECHNICAL REFERENCE
608Definitions 687Definitions
609 "c" The literal character c. 688 "c" The literal character c.
610 689
611 "C" A single (required) character. 690 "C" A single (required) character.
612 691
… …
697 "ESC O" 776 "ESC O"
698 Single Shift Select of G3 Character Set (SS3): affects next 777 Single Shift Select of G3 Character Set (SS3): affects next
699 character only *unimplemented* 778 character only *unimplemented*
700 779
701 "ESC Z" 780 "ESC Z"
702 Obsolete form of returns: "ESC[?1;2C" *rxvt-unicode compile-time 781 Obsolete form of returns: "ESC [ ? 1 ; 2 C" *rxvt-unicode
703 option* 782 compile-time option*
704 783
705 "ESC c" 784 "ESC c"
706 Full reset (RIS) 785 Full reset (RIS)
707 786
708 "ESC n" 787 "ESC n"
709 Invoke the G2 Character Set (LS2) 788 Invoke the G2 Character Set (LS2)
710 789
711 "ESC o" 790 "ESC o"
712 Invoke the G3 Character Set (LS3) 791 Invoke the G3 Character Set (LS3)
713 792
714 "ESC" ( C> 793 "ESC ( C"
715 Designate G0 Character Set (ISO 2022), see below for values of "C". 794 Designate G0 Character Set (ISO 2022), see below for values of "C".
716 795
717 "ESC" ) C> 796 "ESC ) C"
718 Designate G1 Character Set (ISO 2022), see below for values of "C". 797 Designate G1 Character Set (ISO 2022), see below for values of "C".
719 798
720 "ESC * C" 799 "ESC * C"
721 Designate G2 Character Set (ISO 2022), see below for values of "C". 800 Designate G2 Character Set (ISO 2022), see below for values of "C".
722 801
… …
815 "ESC [ Ps a" 894 "ESC [ Ps a"
816 See "ESC [ Ps C" 895 See "ESC [ Ps C"
817 896
818 "ESC [ Ps c" 897 "ESC [ Ps c"
819 Send Device Attributes (DA) "Ps = 0" (or omitted): request 898 Send Device Attributes (DA) "Ps = 0" (or omitted): request
820 attributes from terminal returns: "ESC[?1;2c" (``I am a VT100 with 899 attributes from terminal returns: "ESC [ ? 1 ; 2 c" (``I am a VT100
821 Advanced Video Option'') 900 with Advanced Video Option'')
822 901
823 "ESC [ Ps d" 902 "ESC [ Ps d"
824 Cursor to Line "Ps" (VPA) 903 Cursor to Line "Ps" (VPA)
825 904
826 "ESC [ Ps e" 905 "ESC [ Ps e"
… …
900 (CSR) 979 (CSR)
901 980
902 "ESC [ s" 981 "ESC [ s"
903 Save Cursor (SC) 982 Save Cursor (SC)
904 983
984 "ESC [ Ps;Pt t"
985 Window Operations
986
987 Ps = 1 Deiconify (map) window
988 Ps = 2 Iconify window
989 Ps = 3 ESC [ 3 ; X ; Y t Move window to (X|Y)
990 Ps = 4 ESC [ 4 ; H ; W t Resize to WxH pixels
991 Ps = 5 Raise window
992 Ps = 6 Lower window
993 Ps = 7 Refresh screen once
994 Ps = 8 ESC [ 8 ; R ; C t Resize to R rows and C columns
995 Ps = 11 Report window state (responds with Ps = 1 or Ps = 2)
996 Ps = 13 Report window position (responds with Ps = 3)
997 Ps = 14 Report window pixel size (responds with Ps = 4)
998 Ps = 18 Report window text size (responds with Ps = 7)
999 Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9
1000 Ps = 20 Reports icon label (ESC ] L NAME \234)
1001 Ps = 21 Reports window title (ESC ] l NAME \234)
1002 Ps = 24.. Set window height to Ps rows
1003
1004 "ESC [ u"
1005 Restore Cursor
1006
905 "ESC [ Ps x" 1007 "ESC [ Ps x"
906 Request Terminal Parameters (DECREQTPARM) 1008 Request Terminal Parameters (DECREQTPARM)
907
908 "ESC [ u"
909 Restore Cursor
910 1009
911 1010
912 1011
913DEC Private Modes 1012DEC Private Modes
914 "ESC [ ? Pm h" 1013 "ESC [ ? Pm h"
… …
1115 [menu] 1214 [menu]
1116 access the current menuBar for alteration 1215 access the current menuBar for alteration
1117 1216
1118 [title:+*string*] 1217 [title:+*string*]
1119 set the current menuBar's title to *string*, which may contain the 1218 set the current menuBar's title to *string*, which may contain the
1120 following format specifiers: %% : literal % character %n : rxvt name 1219 following format specifiers:
1121 (as per the -name command-line option) %v : rxvt version 1220
1221 B<%n> rxvt name (as per the B<-name> command-line option)
1222 B<%v> rxvt version
1223 B<%%> literal B<%> character
1122 1224
1123 [done] 1225 [done]
1124 set menuBar access as readonly. End-of-file tag for [read:+*file*] 1226 set menuBar access as readonly. End-of-file tag for [read:+*file*]
1125 operations. 1227 operations.
1126 1228
… …
1230 1332
1231 As a convenience for the many Emacs-type editors, *action* may start 1333 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 1334 with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if
1233 missed from M-x commands. 1335 missed from M-x commands.
1234 1336
1235 As a convenience for issuing XTerm ESC] sequences from a menubar (or 1337 As a convenience for issuing XTerm ESC ] sequences from a menubar (or
1236 quick arrow), a BEL (^G) will be appended if needed. 1338 quick arrow), a BEL (^G) will be appended if needed.
1237 1339
1238 For example, 1340 For example,
1239 M-xapropos is equivalent to \Exapropos\r 1341 M-xapropos is equivalent to \Exapropos\r
1240 1342
… …
1602 accents are encoded as seperate unicode characters. This is done by 1704 accents are encoded as seperate unicode characters. This is done by
1603 using precomposited characters when available or creating new 1705 using precomposited characters when available or creating new
1604 pseudo-characters when no precomposed form exists. 1706 pseudo-characters when no precomposed form exists.
1605 1707
1606 Without --enable-unicode3, the number of additional precomposed 1708 Without --enable-unicode3, the number of additional precomposed
1607 characters is rather limited (2048, if this is full, rxvt will use 1709 characters is rather limited (2048, if this is full, rxvt-unicode
1608 the private use area, extending the number of combinations to 8448). 1710 will use the private use area, extending the number of combinations
1609 With --enable-unicode3, no practical limit exists. This will also 1711 to 8448). With --enable-unicode3, no practical limit exists.
1610 enable storage of characters >65535. 1712
1713 This option will also enable storage (but not display) of characters
1714 beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1611 1715
1612 The combining table also contains entries for arabic presentation 1716 The combining table also contains entries for arabic presentation
1613 forms, but these are not currently used. Bug me if you want these to 1717 forms, but these are not currently used. Bug me if you want these to
1614 be used. 1718 be used (and tell me how these are to be used...).
1615 1719
1616 --enable-fallback(=CLASS) 1720 --enable-fallback(=CLASS)
1617 When reading resource settings, also read settings for class CLASS 1721 When reading resource settings, also read settings for class CLASS
1618 (default: Rxvt). To disable resource fallback use 1722 (default: Rxvt). To disable resource fallback use
1619 --disable-fallback. 1723 --disable-fallback.
… …
1693 1797
1694 --enable-xgetdefault 1798 --enable-xgetdefault
1695 Make resources checking via XGetDefault() instead of our small 1799 Make resources checking via XGetDefault() instead of our small
1696 version which only checks ~/.Xdefaults, or if that doesn't exist 1800 version which only checks ~/.Xdefaults, or if that doesn't exist
1697 then ~/.Xresources. 1801 then ~/.Xresources.
1802
1803 Please note that nowadays, things like XIM will automatically pull
1804 in and use the full X resource manager, so the overhead of using it
1805 might be very small, if nonexistant.
1698 1806
1699 --enable-strings 1807 --enable-strings
1700 Add support for our possibly faster memset() function and other 1808 Add support for our possibly faster memset() function and other
1701 various routines, overriding your system's versions which may have 1809 various routines, overriding your system's versions which may have
1702 been hand-crafted in assembly or may require extra libraries to link 1810 been hand-crafted in assembly or may require extra libraries to link
… …
1722 iso-14755-2 and -3, and visual feedback 1830 iso-14755-2 and -3, and visual feedback
1723 backindex and forwardindex escape sequence 1831 backindex and forwardindex escape sequence
1724 window op and locale change escape sequences 1832 window op and locale change escape sequences
1725 tripleclickwords 1833 tripleclickwords
1726 settable insecure mode 1834 settable insecure mode
1835 keysym remapping support
1727 1836
1728 --enable-iso14755 1837 --enable-iso14755
1729 Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). 1838 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 1839 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. 1840 support for 5.2, 5.3 and 5.4 is enabled with this switch.

Diff Legend

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