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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.2 by root, Thu Aug 12 21:30:14 2004 UTC vs.
Revision 1.29 by root, Wed Dec 29 19:17:18 2004 UTC

1=head1 NAME
2
3RXVT REFERENCE - FAQ, command sequences and other background information
4
5=head1 FREQUENTLY ASKED QUESTIONS
6
7=over 4
8
9=item How do I know which rxvt-unicode version I'm using?
10
11The version number is displayed with the usage (-h). Also the escape
12sequence C<ESC[8n> sets the window title to the version number.
13
14=item When I log-in to another system it tells me about missing terminfo data?
15
16The terminal description used by rxvt-unicode is not as widely available
17as that for xterm, or even rxvt (for which the same problem often arises).
18
19The correct solution for this problem is to install the terminfo, this can
20be done like this (with ncurses' infocmp):
21
22 REMOTE=remotesystem.domain
23 infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
24
25... or by installing rxvt-unicode normally on the remote system,
26
27If you cannot or do not want to do this, then you can simply set
28C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
29problems arising, which includes wrong keymapping, less and different
30colours and some refresh errors in fullscreen applications. It's a nice
31quick-and-dirty workaround for rare cases, though.
32
33If you always want to do this you can either recompile rxvt-unicode with
34the desired TERM value or use a resource to set it:
35
36 URxvt.termName: rxvt
37
38If you don't plan to use B<rxvt> (quite common...) you could also replace
39the rxvt terminfo file with the rxvt-unicode one.
40
41=item I need a termcap file entry.
42
43You could use rxvt's termcap entry with resonable results in many cases.
44You can also create a termcap entry by using terminfo's infocmp program
45like this:
46
47 infocmp -C rxvt-unicode
48
49OR you could this termcap entry:
50
51 rxvt-unicode|rxvt-unicode terminal (X Window System):\
52 :am:bw:eo:km:mi:ms:xn:xo:\
53 :co#80:it#8:li#24:\
54 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
55 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
56 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\
57 :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\
58 :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\
59 :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\
60 :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
61 :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\
62 :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\
63 :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\
64 :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\
65 :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\
66 :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\
67 :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\
68 :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
69 :vs=\E[?25h:
70
71=item How can I configure rxvt-unicode so that it looks similar to the original rxvt?
72
73Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode
74behave similar to the original rxvt:
75
76 URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
77 URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1
78
79=item Rxvt-unicode does not seem to understand the selected encoding?
80
81=item Unicode does not seem to work?
82
83If you encounter strange problems like typing an accented character but
84getting two unrelated other characters or similar, or if program output is
85subtly garbled, then you should check your locale settings.
86
87Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
88programs. Often rxvt-unicode is started in the C<C> locale, while the
89login script running within the rxvt-unicode window changes the locale to
90sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work.
91
92The best thing is to fix your startup environment, as you will likely run
93into other problems. If nothing works you can try this in your .profile.
94
95 printf '\e]701;%s\007' "$LC_CTYPE"
96
97If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
98supported on your systems. Some systems have a C<locale> command which
99displays this. If it displays sth. like:
100
101 locale: Cannot set LC_CTYPE to default locale: ...
102
103Then the locale you specified is not supported on your system.
104
105If nothing works and you are sure that everything is set correctly then
106you will need to remember a little known fact: Some programs just don't
107support locales :(
108
109=item Why do some characters look so much different than others?
110
111=item How does rxvt-unicode choose fonts?
112
113Most fonts do not contain the full range of Unicode, which is
114fine. Chances are that the font you (or the admin/package maintainer of
115your system/os) have specified does not cover all the characters you want
116to display.
117
118B<rxvt-unicode> makes a best-effort try at finding a replacement
119font. Often the result is fine, but sometimes the chosen font looks
120bad. Many fonts have totally strange characters that don't resemble the
121correct glyph at all, and rxvt-unicode lacks the artificial intelligence
122to detect that a specific glyph is wrong: it has to believe the font that
123the characters it contains indeed look correct.
124
125In that case, select a font of your taste and add it to the font list,
126e.g.:
127
128 @@RXVT_NAME@@ -fn basefont,font2,font3...
129
130When rxvt-unicode sees a character, it will first look at the base
131font. If the base font does not contain the character, it will go to the
132next font, and so on. Specifying your own fonts will also speed up this
133search and use less resources within rxvt-unicode and the X-server.
134
135The only limitation is that all the fonts must not be larger than the base
136font, as the base font defines the principal cell size, which must be the
137same due to the way terminals work.
138
139=item Why do some chinese characters look so different than others?
140
141This is because there is a difference between script and language --
142rxvt-unicode does not know which language the text that is output
143is, as it only knows the unicode character codes. If rxvt-unicode
144first sees a japanese character, it might choose a japanese font for
145it. Subsequent japanese characters will take that font. Now, many chinese
146characters aren't represented in japanese fonts, so when the first
147non-japanese character comes up, rxvt-unicode will look for a chinese font
148-- unfortunately at this point, it will still use the japanese font for
149japanese characters that are also chinese.
150
151The workaround is easy: just tag a chinese font at the end of your font
152list (see the previous question). The key is to view the font list as
153a preference list: If you expect more japanese, list a japanese font
154first. If you expect more chinese, put a chinese font first.
155
156In the future it might be possible to switch preferences at runtime (the
157internal data structure has no problem with using different fonts for
158the same character at the same time, but no interface for this has been
159designed yet).
160
161=item Why does rxvt-unicode sometimes leave pixel droppings?
162
163Most fonts were not designed for terminal use, which means that character
164size varies a lot. A font that is otherwise fine for terminal use might
165contain some characters that are simply too wide. Rxvt-unicode will avoid
166these characters. For characters that are just "a bit" too wide a special
167"careful" rendering mode is used that redraws adjacent characters.
168
169All of this requires that fonts do not lie about character sizes,
170however: Xft fonts often draw glyphs larger than their acclaimed bounding
171box, and rxvt-unicode has no way of detecting this (the correct way is to
172ask for the character bounding box, which unfortunately is wrong in these
173cases).
174
175It's not clear (to me at least), wether this is a bug in Xft, freetype, or
176the respective font. If you encounter this problem there is no way to work
177around this except by using a different font.
178
179All of this is not a problem when using X11 core fonts, as their bounding
180box data is correct.
181
182=item My Compose (Multi_key) key is no longer working.
183
184The most common causes for this are that either your locale is not set
185correctly, or you specified a B<preeditStyle> that is not supported by
186your input method. For example, if you specified B<OverTheSpot> and
187your input method (e.g. the default input method handling Compose keys)
188does not support this (for instance because it is not visual), then
189rxvt-unicode will continue without an input method.
190
191In this case either do not specify a B<preeditStyle> or specify more than
192one pre-edit style, such as B<OverTheSpot,Root,None>.
193
194=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
195
196Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
197international keyboards) or simply use ISO 14755 support to your
198advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
199codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
200character and so on.
201
202=item How can I keep rxvt-unicode from using reverse video so much?
203
204First of all, make sure you are running with the right terminfo
205(C<urxvt>), which will get rid of most of these effects. Then make sure
206you have specified colours for italic and bold, as otherwise rxvt-unicode
207might use reverse video to simulate the effect:
208
209 URxvt*colorBD: white
210 URxvt*colorIT: green
211
212=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
213
214For some unexplainable reason, some programs (i.e. irssi) assume a very
215weird colour palette when confronted with a terminal with more than the
216standard 8 colours (rxvt-unicode supports 88). The right fix is, of
217course, to fix these programs not to assume non-ISO colours without very
218good reasons.
219
220In the meantime, you can either edit your C<urxvt> terminfo definition to
221only claim 8 colour support or use C<TERM=rxvt>, which will fix colours
222but keep you from using other rxvt-unicode features.
223
224=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
225
226Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
227in your compile environment, or an implementation that implements it,
228wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
229B<wchar_t> is represented as unicode.
230
231As you might have guessed, FreeBSD does neither define this symobl nor
232does it support it. Instead, it uses it's own internal representation of
233B<wchar_t>. This is, of course, completely legal.
234
235However, C<__STDC_ISO_10646__> is the only sane way to support
236multi-language apps in an OS, as using a locale-dependent (and
237non-standardized) representation of B<wchar_t> makes it impossible to
238convert between B<wchar_t> (as used by X11 and your applications) and any
239other encoding without implementing OS-specific-wrappers for each and
240every locale. There simply are no APIs to convert B<wchar_t> into anything
241except the current locale encoding.
242
243Some applications (such as the formidable B<mlterm>) work around this
244by carrying their own replacement functions for character set handling
245with them, and either implementing OS-dependent hacks or doing multiple
246conversions (which is slow and unreliable in case the OS implements
247encodings slightly different than the terminal emulator).
248
249The rxvt-unicode author insists that the right way to fix this is in the
250system libraries once and for all, instead of forcing every app to carry
251complete replacements.
252
253=item How does rxvt-unicode determine the encoding to use?
254
255=item Is there an option to switch encodings?
256
257Unlike some other terminals, rxvt-unicode has no encoding switch, and no
258specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
259UTF-8 or any other encodings with respect to terminal I/O.
260
261The reasons is that there exists a perfectly fine mechanism for selecting
262the encoding, doing I/O and (most important) communicating this to all
263applications so everybody agrees on character properties such as width and
264code number. This mechanism is the I<locale>.
265
266Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
267programs doing the same (that is, most) will automatically agree in the
268interpretation of characters.
269
270Unfortunately, there is no system-independent way to select locales, nor
271is there a standard on how locale specifiers will look like.
272
273On most systems, the content of the C<LC_CTYPE> environment variable
274contains an arbitrary string which corresponds to an already-installed
275locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
276C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
277(i.e. C<de> or C<german>) are also common.
278
279Rxvt-unicode ignores all other locale categories, and except for
280the encoding, ignores country or language-specific settings,
281i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode.
282
283If you want to use a specific encoding you have to make sure you start
284rxvt-unicode with the correct C<LC_CTYPE> category.
285
286=item Can I switch locales at runtime?
287
288Yes, using an escape sequence. Try sth. like this, which sets
289rxvt-unicode's idea of C<LC_CTYPE>.
290
291 printf '\e]701;%s\007' ja_JP.SJIS
292
293See also the previous question.
294
295Sometimes this capability is rather handy when you want to work in one
296locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For
297example, I use this script to start C<xjdic>, which first switches to a
298locale supported by xjdic and back later:
299
300 printf '\e]701;%s\007' ja_JP.SJIS
301 xjdic -js
302 printf '\e]701;%s\007' de_DE.UTF-8
303
304=item Can I switch the fonts at runtime?
305
306Yes, using an escape sequence. Try sth. like this, which has the same
307effect as using the C<-fn> switch, and takes effect immediately:
308
309 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
310
311This is useful if you e.g. work primarily with japanese (and prefer a
312japanese font), but you have to switch to chinese temporarily, where
313japanese fonts would only be in your way.
314
315You can think of this as a kind of manual ISO-2022 switching.
316
317=item Why do italic characters look as if clipped?
318
319Many fonts have difficulties with italic characters and hinting. For
320example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
321Mono> completely fails in it's italic face. A workaround is to enable
322freetype autohinting, i.e. like this:
323
324 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
325 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
326
327=item My input method wants <some encoding> but I want UTF-8, what can I do?
328
329You can specify separate locales for the input method and the rest of the
330terminal, using the resource C<imlocale>:
331
332 URxvt*imlocale: ja_JP.EUC-JP
333
334Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
335use your input method. Please note, however, that you will not be able to
336input characters outside C<EUC-JP> in a normal way then, as your input
337method limits you.
338
339=item Rxvt-unicode uses gobs of memory, how can I reduce that?
340
341Rxvt-unicode tries to obey the rule of not charging you for sth. you
342don't use. One thing you should try is to configure out all settings that
343you don't need, for example, Xft support is a resource hog by design,
344when used. Compiling it out ensures that no Xft font will be loaded
345accidentally when rxvt-unicode tries to find a font for your characters.
346
347Also, many people (me included) like large windows and even larger
348scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
3496 bytes per screen cell. For a 160x?? window this amounts to almost a
350kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
351use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
352rxvt-unicode then uses 8 bytes per screen cell.
353
354=item Can I speed up Xft rendering somehow?
355
356Yes, the most obvious way to speed it up is to avoid Xft entirely, as
357it is simply slow. If you still want Xft fonts you might try to disable
358antialiasing (by appending C<:antialiasing=false>), which saves lots of
359memory and also speeds up rendering considerably.
360
361=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
362
363Rxvt-unicode will use whatever you specify as a font. If it needs to
364fall back to it's default font search list it will prefer X11 core
365fonts, because they are small and fast, and then use Xft fonts. It has
366antialiasing disabled for most of them, because the author thinks they
367look best that way.
368
369If you want antialiasing, you have to specify the fonts manually.
370
371=item Mouse cut/paste suddenly no longer works.
372
373Make sure that mouse reporting is actually turned off since killing
374some editors prematurely may leave the mouse in mouse report mode. I've
375heard that tcsh may use mouse reporting unless it otherwise specified. A
376quick check is to see if cut/paste works when the Alt or Shift keys are
377depressed. See @@RXVT_NAME@@(7)
378
379=item What's with this bold/blink stuff?
380
381If no bold colour is set via C<colorBD:>, bold will invert text using the
382standard foreground colour.
383
384For the standard background colour, blinking will actually make the
385text blink when compiled with C<--enable-blinking>. with standard
386colours. Without C<--enable-blinking>, the blink attribute will be
387ignored.
388
389On ANSI colours, bold/blink attributes are used to set high-intensity
390foreground/background colors.
391
392color0-7 are the low-intensity colors.
393
394color8-15 are the corresponding high-intensity colors.
395
396=item I don't like the screen colors. How do I change them?
397
398You can change the screen colors at run-time using F<~/.Xdefaults>
399resources (or as long-options).
400
401Here are values that are supposed to resemble a VGA screen,
402including the murky brown that passes for low-intensity yellow:
403
404 URxvt*color0: #000000
405 URxvt*color1: #A80000
406 URxvt*color2: #00A800
407 URxvt*color3: #A8A800
408 URxvt*color4: #0000A8
409 URxvt*color5: #A800A8
410 URxvt*color6: #00A8A8
411 URxvt*color7: #A8A8A8
412
413 URxvt*color8: #000054
414 URxvt*color9: #FF0054
415 URxvt*color10: #00FF54
416 URxvt*color11: #FFFF54
417 URxvt*color12: #0000FF
418 URxvt*color13: #FF00FF
419 URxvt*color14: #00FFFF
420 URxvt*color15: #FFFFFF
421
422And here is a more complete set of non-standard colors described as
423"pretty girly":
424
425 URxvt.cursorColor: #dc74d1
426 URxvt.pointerColor: #dc74d1
427 URxvt.background: #0e0e0e
428 URxvt.foreground: #4ad5e1
429 URxvt.color0: #000000
430 URxvt.color8: #8b8f93
431 URxvt.color1: #dc74d1
432 URxvt.color9: #dc74d1
433 URxvt.color2: #0eb8c7
434 URxvt.color10: #0eb8c7
435 URxvt.color3: #dfe37e
436 URxvt.color11: #dfe37e
437 URxvt.color5: #9e88f0
438 URxvt.color13: #9e88f0
439 URxvt.color6: #73f7ff
440 URxvt.color14: #73f7ff
441 URxvt.color7: #e1dddd
442 URxvt.color15: #e1dddd
443
444=item What's with the strange Backspace/Delete key behaviour?
445
446Assuming that the physical Backspace key corresponds to the
447BackSpace keysym (not likely for Linux ... see the following
448question) there are two standard values that can be used for
449Backspace: C<^H> and C<^?>.
450
451Historically, either value is correct, but rxvt-unicode adopts the debian
452policy of using C<^?> when unsure, because it's the one only only correct
453choice :).
454
455Rxvt-unicode tries to inherit the current stty settings and uses the value
456of `erase' to guess the value for backspace. If rxvt-unicode wasn't
457started from a terminal (say, from a menu or by remote shell), then the
458system value of `erase', which corresponds to CERASE in <termios.h>, will
459be used (which may not be the same as your stty setting).
460
461For starting a new rxvt-unicode:
462
463 # use Backspace = ^H
464 $ stty erase ^H
465 $ @@RXVT_NAME@@
466
467 # use Backspace = ^?
468 $ stty erase ^?
469 $ @@RXVT_NAME@@
470
471Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).
472
473For an existing rxvt-unicode:
474
475 # use Backspace = ^H
476 $ stty erase ^H
477 $ echo -n "^[[36h"
478
479 # use Backspace = ^?
480 $ stty erase ^?
481 $ echo -n "^[[36l"
482
483This helps satisfy some of the Backspace discrepancies that occur, but
484if you use Backspace = C<^H>, make sure that the termcap/terminfo value
485properly reflects that.
486
487The Delete key is a another casualty of the ill-defined Backspace problem.
488To avoid confusion between the Backspace and Delete keys, the Delete
489key has been assigned an escape sequence to match the vt100 for Execute
490(ESC[3~) and is in the supplied termcap/terminfo.
491
492Some other Backspace problems:
493
494some editors use termcap/terminfo,
495some editors (vim I'm told) expect Backspace = ^H,
496GNU Emacs (and Emacs-like editors) use ^H for help.
497
498Perhaps someday this will all be resolved in a consistent manner.
499
500=item I don't like the key-bindings. How do I change them?
501
502There are some compile-time selections available via configure. Unless
503you have run "configure" with the C<--disable-resources> option you can
504use the `keysym' resource to alter the keystrings associated with keysym
5050xFF00 - 0xFFFF (function, cursor keys, etc).
506
507Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270'
508
509 !# ----- special uses ------:
510 ! tn3270 login, remap function and arrow keys.
511 tn3270*font: *clean-bold-*-*--15-*
512
513 ! keysym - used by rxvt only
514 ! Delete - ^D
515 tn3270*keysym.0xFFFF: \004
516
517 ! Home - ^A
518 tn3270*keysym.0xFF50: \001
519 ! Left - ^B
520 tn3270*keysym.0xFF51: \002
521 ! Up - ^P
522 tn3270*keysym.0xFF52: \020
523 ! Right - ^F
524 tn3270*keysym.0xFF53: \006
525 ! Down - ^N
526 tn3270*keysym.0xFF54: \016
527 ! End - ^E
528 tn3270*keysym.0xFF57: \005
529
530 ! F1 - F12
531 tn3270*keysym.0xFFBE: \e1
532 tn3270*keysym.0xFFBF: \e2
533 tn3270*keysym.0xFFC0: \e3
534 tn3270*keysym.0xFFC1: \e4
535 tn3270*keysym.0xFFC2: \e5
536 tn3270*keysym.0xFFC3: \e6
537 tn3270*keysym.0xFFC4: \e7
538 tn3270*keysym.0xFFC5: \e8
539 tn3270*keysym.0xFFC6: \e9
540 tn3270*keysym.0xFFC7: \e0
541 tn3270*keysym.0xFFC8: \e-
542 tn3270*keysym.0xFFC9: \e=
543
544 ! map Prior/Next to F7/F8
545 tn3270*keysym.0xFF55: \e7
546 tn3270*keysym.0xFF56: \e8
547
548=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
549How do I make use of them? For example, the Sun Keyboard type 4
550has the following mappings that rxvt-unicode doesn't recognize.
551
552 KP_Insert == Insert
553 F22 == Print
554 F27 == Home
555 F29 == Prior
556 F33 == End
557 F35 == Next
558
559Rather than have rxvt-unicode try to accommodate all the various possible keyboard
560mappings, it is better to use `xmodmap' to remap the keys as required for
561your particular machine.
562
563=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?
564I need this to decide about setting colors etc.
565
566rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
567check and see if that is set. Note that several programs, JED, slrn,
568Midnight Commander automatically check this variable to decide whether or
569not to use color.
570
571=item How do I set the correct, full IP address for the DISPLAY variable?
572
573If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
574insecure mode then it is possible to use the following shell script
575snippets to correctly set the display. If your version of rxvt-unicode
576wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
577the COLORTERM variable can be used to distinguish rxvt-unicode from a
578regular xterm.
579
580Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
581snippets:
582
583 # Bourne/Korn/POSIX family of shells:
584 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
585 if [ ${TERM:-foo} = xterm ]; then
586 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
587 echo -n '^[Z'
588 read term_id
589 stty icanon echo
590 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
591 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
592 read DISPLAY # set it in our local shell
593 fi
594 fi
595
596=item How do I compile the manual pages for myself?
597
598You need to have a recent version of perl installed as F</usr/bin/perl>,
599one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
600the doc subdirectory and enter C<make alldoc>.
601
602=item My question isn't answered here, can I ask a human?
603
604Before sending me mail, you could go to IRC: C<irc.freenode.net>,
605channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
606interested in learning about new and exciting problems (but not FAQs :).
607
608=back
609
610=head1 SYNOPSIS
611
612 # set a new font set
613 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
614
615 # change the locale and tell rxvt-unicode about it
616 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
617
618 # set window title
619 printf '\33]2;%s\007' "new window title"
620
621=head1 DESCRIPTION
622
623The rest of this document describes various technical aspects of
624B<rxvt-unicode>. First the description of supported command sequences,
625followed by menu and pixmap support and last by a description of all
626features selectable at C<configure> time.
627
1=head1 RXVT TECHNICAL REFERENCE 628=head1 RXVT TECHNICAL REFERENCE
2 629
3=head1 Definitions 630=head1 Definitions
4 631
5=over 4 632=over 4
135Single Shift Select of G3 Character Set (SS3): affects next character 762Single Shift Select of G3 Character Set (SS3): affects next character
136only I<unimplemented> 763only I<unimplemented>
137 764
138=item B<< C<ESC Z> >> 765=item B<< C<ESC Z> >>
139 766
140Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt compile-time option> 767Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option>
141 768
142=item B<< C<ESC c> >> 769=item B<< C<ESC c> >>
143 770
144Full reset (RIS) 771Full reset (RIS)
145 772
149 776
150=item B<< C<ESC o> >> 777=item B<< C<ESC o> >>
151 778
152Invoke the G3 Character Set (LS3) 779Invoke the G3 Character Set (LS3)
153 780
154=item B<< C<ESC>(C<C> >> 781=item B<< C<ESC> ( C> >>
155 782
156Designate G0 Character Set (ISO 2022), see below for values of C<C>. 783Designate G0 Character Set (ISO 2022), see below for values of C<C>.
157 784
158=item B<< C<ESC>)C<C> >> 785=item B<< C<ESC> ) C> >>
159 786
160Designate G1 Character Set (ISO 2022), see below for values of C<C>. 787Designate G1 Character Set (ISO 2022), see below for values of C<C>.
161 788
162=item B<< C<ESC * C> >> 789=item B<< C<ESC * C> >>
163 790
187 814
188=back 815=back
189 816
190X<CSI> 817X<CSI>
191 818
192=head1 CSI (Code Sequence Introducer) Sequences 819=head1 CSI (Command Sequence Introducer) Sequences
193 820
194=over 4 821=over 4
195 822
196=item B<< C<ESC [ Ps @> >> 823=item B<< C<ESC [ Ps @> >>
197 824
330 B<< C<Ps = 0> >> Clear Current Column (default) 957 B<< C<Ps = 0> >> Clear Current Column (default)
331 B<< C<Ps = 3> >> Clear All (TBC) 958 B<< C<Ps = 3> >> Clear All (TBC)
332 959
333=end table 960=end table
334 961
962=item B<< C<ESC [ Pm h> >>
963
964Set Mode (SM). See B<< C<ESC [ Pm l> >> sequence for description of C<Pm>.
965
335=item B<< C<ESC [ Ps i> >> 966=item B<< C<ESC [ Ps i> >>
336 967
337Printing 968Printing. See also the C<print-pipe> resource.
338 969
339=begin table 970=begin table
340 971
972 B<< C<Ps = 0> >> print screen (MC0)
341 B<< C<Ps = 4> >> disable transparent print mode (MC4) 973 B<< C<Ps = 4> >> disable transparent print mode (MC4)
342 B<< C<Ps = 5> >> enable transparent print mode (MC5) I<unimplemented> 974 B<< C<Ps = 5> >> enable transparent print mode (MC5)
343 975
344=end table 976=end table
345
346=item B<< C<ESC [ Pm h> >>
347
348Set Mode (SM). See next sequence for description of C<Pm>.
349 977
350=item B<< C<ESC [ Pm l> >> 978=item B<< C<ESC [ Pm l> >>
351 979
352Reset Mode (RM) 980Reset Mode (RM)
353 981
360 B<< C<h> >> Insert Mode (SMIR) 988 B<< C<h> >> Insert Mode (SMIR)
361 B<< C<l> >> Replace Mode (RMIR) 989 B<< C<l> >> Replace Mode (RMIR)
362 990
363=end table 991=end table
364 992
365=item B<< C<Ps = 20> >> I<unimplemented> 993=item B<< C<Ps = 20> >> (partially implemented)
366 994
367=begin table 995=begin table
368 996
369 B<< C<h> >> Automatic Newline (LNM) 997 B<< C<h> >> Automatic Newline (LNM)
370 B<< C<h> >> Normal Linefeed (LNM) 998 B<< C<l> >> Normal Linefeed (LNM)
371 999
372=end table 1000=end table
373 1001
374=back 1002=back
375 1003
378Character Attributes (SGR) 1006Character Attributes (SGR)
379 1007
380=begin table 1008=begin table
381 1009
382 B<< C<Ps = 0> >> Normal (default) 1010 B<< C<Ps = 0> >> Normal (default)
383 B<< C<Ps = 1 / 22> >> On / Off Bold (bright fg) 1011 B<< C<Ps = 1 / 21> >> On / Off Bold (bright fg)
1012 B<< C<Ps = 3 / 23> >> On / Off Italic
384 B<< C<Ps = 4 / 24> >> On / Off Underline 1013 B<< C<Ps = 4 / 24> >> On / Off Underline
385 B<< C<Ps = 5 / 25> >> On / Off Blink (bright bg) 1014 B<< C<Ps = 5 / 25> >> On / Off Slow Blink (bright bg)
1015 B<< C<Ps = 6 / 26> >> On / Off Rapid Blink (bright bg)
386 B<< C<Ps = 7 / 27> >> On / Off Inverse 1016 B<< C<Ps = 7 / 27> >> On / Off Inverse
1017 B<< C<Ps = 8 / 27> >> On / Off Invisible (NYI)
387 B<< C<Ps = 30 / 40> >> fg/bg Black 1018 B<< C<Ps = 30 / 40> >> fg/bg Black
388 B<< C<Ps = 31 / 41> >> fg/bg Red 1019 B<< C<Ps = 31 / 41> >> fg/bg Red
389 B<< C<Ps = 32 / 42> >> fg/bg Green 1020 B<< C<Ps = 32 / 42> >> fg/bg Green
390 B<< C<Ps = 33 / 43> >> fg/bg Yellow 1021 B<< C<Ps = 33 / 43> >> fg/bg Yellow
391 B<< C<Ps = 34 / 44> >> fg/bg Blue 1022 B<< C<Ps = 34 / 44> >> fg/bg Blue
392 B<< C<Ps = 35 / 45> >> fg/bg Magenta 1023 B<< C<Ps = 35 / 45> >> fg/bg Magenta
393 B<< C<Ps = 36 / 46> >> fg/bg Cyan 1024 B<< C<Ps = 36 / 46> >> fg/bg Cyan
1025 B<< C<Ps = 38;5 / 48;5> >> set fg/bg to color #m (ISO 8613-6)
394 B<< C<Ps = 37 / 47> >> fg/bg White 1026 B<< C<Ps = 37 / 47> >> fg/bg White
395 B<< C<Ps = 39 / 49> >> fg/bg Default 1027 B<< C<Ps = 39 / 49> >> fg/bg Default
1028 B<< C<Ps = 90 / 100> >> fg/bg Bright Black
1029 B<< C<Ps = 91 / 101> >> fg/bg Bright Red
1030 B<< C<Ps = 92 / 102> >> fg/bg Bright Green
1031 B<< C<Ps = 93 / 103> >> fg/bg Bright Yellow
1032 B<< C<Ps = 94 / 104> >> fg/bg Bright Blue
1033 B<< C<Ps = 95 / 105> >> fg/bg Bright Magenta
1034 B<< C<Ps = 96 / 106> >> fg/bg Bright Cyan
1035 B<< C<Ps = 97 / 107> >> fg/bg Bright White
1036 B<< C<Ps = 99 / 109> >> fg/bg Bright Default
396 1037
397=end table 1038=end table
398 1039
399=item B<< C<ESC [ Ps n> >> 1040=item B<< C<ESC [ Ps n> >>
400 1041
535 B<< C<h> >> Send Mouse X & Y on button press. 1176 B<< C<h> >> Send Mouse X & Y on button press.
536 B<< C<l> >> No mouse reporting. 1177 B<< C<l> >> No mouse reporting.
537 1178
538=end table 1179=end table
539 1180
540)X<Priv10>
541
542=item B<< C<Ps = 10> >> (B<rxvt>) 1181=item B<< C<Ps = 10> >> (B<rxvt>)
543 1182
544=begin table 1183=begin table
545 1184
546 B<< C<h> >> visible 1185 B<< C<h> >> menuBar visible
547 B<< C<l> >> invisible 1186 B<< C<l> >> menuBar invisible
548 1187
549=end table 1188=end table
550 1189
551=item B<< C<Ps = 25> >> 1190=item B<< C<Ps = 25> >>
552 1191
653 B<< C<h> >> Use Hilite Mouse Tracking. 1292 B<< C<h> >> Use Hilite Mouse Tracking.
654 B<< C<l> >> No mouse reporting. 1293 B<< C<l> >> No mouse reporting.
655 1294
656=end table 1295=end table
657 1296
658=item B<< C<Ps = 1010> >> 1297=item B<< C<Ps = 1010> >> (B<rxvt>)
659 1298
660=begin table 1299=begin table
661 1300
662 B<< C<h> >> Don't scroll to bottom on TTY output 1301 B<< C<h> >> Don't scroll to bottom on TTY output
663 B<< C<l> >> Scroll to bottom on TTY output 1302 B<< C<l> >> Scroll to bottom on TTY output
664 1303
665=end table 1304=end table
666 1305
667=item B<< C<Ps = 1011> >> 1306=item B<< C<Ps = 1011> >> (B<rxvt>)
668 1307
669=begin table 1308=begin table
670 1309
671 B<< C<h> >> Scroll to bottom when a key is pressed 1310 B<< C<h> >> Scroll to bottom when a key is pressed
672 B<< C<l> >> Don't scroll to bottom when a key is pressed 1311 B<< C<l> >> Don't scroll to bottom when a key is pressed
686 1325
687=begin table 1326=begin table
688 1327
689 B<< C<h> >> Save cursor position 1328 B<< C<h> >> Save cursor position
690 B<< C<l> >> Restore cursor position 1329 B<< C<l> >> Restore cursor position
1330
1331=end table
1332
1333=item B<< C<Ps = 1049> >>
1334
1335=begin table
1336
1337 B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1338 B<< C<l> >> Use Normal Screen Buffer
691 1339
692=end table 1340=end table
693 1341
694=back 1342=back
695 1343
726 B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> 1374 B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
727 B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option> 1375 B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>
728 B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >> 1376 B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>
729 B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> 1377 B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
730 B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (@@RXVT_NAME@@ extension) 1378 B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (@@RXVT_NAME@@ extension)
731 B<< C<Ps = 702> >> find font for character, used for debugging (@@RXVT_NAME@@ extension)
732 B<< C<Ps = 703> >> command B<< C<Pt> >> I<rxvt compile-time option> (@@RXVT_NAME@@ extension) 1379 B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)
1380 B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1381 B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>
1382 B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1383 B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
1384 B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
1385 B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
733 1386
734=end table 1387=end table
735 1388
736=back 1389=back
737 1390
1390 XK_KP_8 8 ESC O x 2043 XK_KP_8 8 ESC O x
1391 XK_KP_9 9 ESC O y 2044 XK_KP_9 9 ESC O y
1392 2045
1393=end table 2046=end table
1394 2047
2048=head1 CONFIGURE OPTIONS
2049
2050General hint: if you get compile errors, then likely your configuration
2051hasn't been tested well. Either try with --enable-everything or use the
2052./reconf script as a base for experiments. ./reconf is used by myself,
2053so it should generally be a working config. Of course, you should always
2054report when a combination doesn't work, so it can be fixed. Marc Lehmann
2055<rxvt@schmorp.de>.
2056
2057=over 4
2058
2059=item --enable-everything
2060
2061Add support for all non-multichoice options listed in "./configure
2062--help". Note that unlike other enable options this is order dependant.
2063You can specify this and then disable options which this enables by
2064I<following> this with the appropriate commands.
2065
2066=item --enable-xft
2067
2068Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2069slower and require lots of memory, but as long as you don't use them, you
2070don't pay for them.
2071
2072=item --enable-font-styles
2073
2074Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2075styles. The fonts can be set manually or automatically.
2076
2077=item --with-codesets=NAME,...
2078
2079Compile in support for additional codeset (encoding) groups (eu, vn are
2080always compiled in, which includes most 8-bit character sets). These
2081codeset tables are currently only used for driving X11 core fonts, they
2082are not required for Xft fonts. Compiling them in will make your binary
2083bigger (together about 700kB), but it doesn't increase memory usage unless
2084you use an X11 font requiring one of these encodings.
2085
2086=begin table
2087
2088 all all available codeset groups
2089 zh common chinese encodings
2090 zh_ext rarely used but very big chinese encodigs
2091 jp common japanese encodings
2092 jp_ext rarely used but big japanese encodings
2093 kr korean encodings
2094
2095=end table
2096
2097=item --enable-xim
2098
2099Add support for XIM (X Input Method) protocol. This allows using
2100alternative input methods (e.g. kinput2) and will also correctly
2101set up the input for people using dead keys or compose keys.
2102
2103=item --enable-unicode3
2104
2105Enable direct support for displaying unicode codepoints above
210665535 (the basic multilingual page). This increases storage
2107requirements per character from 2 to 4 bytes. X11 fonts do not yet
2108support these extra characters, but Xft does.
2109
2110Please note that rxvt-unicode can store unicode code points >65535
2111even without this flag, but the number of such characters is
2112limited to a view thousand (shared with combining characters,
2113see next switch), and right now rxvt-unicode cannot display them
2114(input/output and cut&paste still work, though).
2115
2116=item --enable-combining
2117
2118Enable automatic composition of combining characters into
2119composite characters. This is required for proper viewing of text
2120where accents are encoded as seperate unicode characters. This is
2121done by using precomposited characters when available or creating
2122new pseudo-characters when no precomposed form exists.
2123
2124Without --enable-unicode3, the number of additional precomposed
2125characters is rather limited (2048, if this is full, rxvt will use the
2126private use area, extending the number of combinations to 8448). With
2127--enable-unicode3, no practical limit exists. This will also enable
2128storage of characters >65535.
2129
2130The combining table also contains entries for arabic presentation forms,
2131but these are not currently used. Bug me if you want these to be used.
2132
2133=item --enable-fallback(=CLASS)
2134
2135When reading resource settings, also read settings for class CLASS
2136(default: Rxvt). To disable resource fallback use --disable-fallback.
2137
2138=item --with-res-name=NAME
2139
2140Use the given name (default: urxvt) as default application name when
2141reading resources. Specify --with-res-name=rxvt to replace rxvt.
2142
2143=item --with-res-class=CLASS
2144
2145Use the given class (default: URxvt) as default application class
2146when reading resources. Specify --with-res-class=Rxvt to replace
2147rxvt.
2148
2149=item --enable-utmp
2150
2151Write user and tty to utmp file (used by programs like F<w>) at
2152start of rxvt execution and delete information when rxvt exits.
2153
2154=item --enable-wtmp
2155
2156Write user and tty to wtmp file (used by programs like F<last>) at
2157start of rxvt execution and write logout when rxvt exits. This
2158option requires --enable-utmp to also be specified.
2159
2160=item --enable-lastlog
2161
2162Write user and tty to lastlog file (used by programs like
2163F<lastlogin>) at start of rxvt execution. This option requires
2164--enable-utmp to also be specified.
2165
2166=item --enable-xpm-background
2167
2168Add support for XPM background pixmaps.
2169
2170=item --enable-transparency
2171
2172Add support for inheriting parent backgrounds thus giving a fake
2173transparency to the term.
2174
2175=item --enable-fading
2176
2177Add support for fading the text when focus is lost.
2178
2179=item --enable-tinting
2180
2181Add support for tinting of transparent backgrounds.
2182
2183=item --enable-menubar
2184
2185Add support for our menu bar system (this interacts badly with
2186dynamic locale switching currently).
2187
2188=item --enable-rxvt-scroll
2189
2190Add support for the original rxvt scrollbar.
2191
2192=item --enable-next-scroll
2193
2194Add support for a NeXT-like scrollbar.
2195
2196=item --enable-xterm-scroll
2197
2198Add support for an Xterm-like scrollbar.
2199
2200=item --enable-plain-scroll
2201
2202Add support for a very unobtrusive, plain-looking scrollbar that
2203is the favourite of the rxvt-unicode author, having used it for
2204many years.
2205
2206=item --enable-half-shadow
2207
2208Make shadows on the scrollbar only half the normal width & height.
2209only applicable to rxvt scrollbars.
2210
2211=item --enable-ttygid
2212
2213Change tty device setting to group "tty" - only use this if
2214your system uses this type of security.
2215
2216=item --disable-backspace-key
2217
2218Disable any handling of the backspace key by us - let the X server
2219do it.
2220
2221=item --disable-delete-key
2222
2223Disable any handling of the delete key by us - let the X server
2224do it.
2225
2226=item --disable-resources
2227
2228Remove all resources checking.
2229
2230=item --enable-xgetdefault
2231
2232Make resources checking via XGetDefault() instead of our small
2233version which only checks ~/.Xdefaults, or if that doesn't exist
2234then ~/.Xresources.
2235
2236=item --enable-strings
2237
2238Add support for our possibly faster memset() function and other
2239various routines, overriding your system's versions which may
2240have been hand-crafted in assembly or may require extra libraries
2241to link in. (this breaks ANSI-C rules and has problems on many
2242GNU/Linux systems).
2243
2244=item --disable-swapscreen
2245
2246Remove support for swap screen.
2247
2248=item --enable-frills
2249
2250Add support for many small features that are not essential but nice to
2251have. Normally you want this, but for very small binaries you may want to
2252disable this.
2253
2254=item --enable-iso14755
2255
2256Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2257F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
2258C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2259this switch.
2260
2261=item --enable-linespace
2262
2263Add support to provide user specified line spacing between text rows.
2264
2265=item --enable-keepscrolling
2266
2267Add support for continual scrolling of the display when you hold
2268the mouse button down on a scrollbar arrow.
2269
2270=item --enable-mousewheel
2271
2272Add support for scrolling via mouse wheel or buttons 4 & 5.
2273
2274=item --enable-slipwheeling
2275
2276Add support for continual scrolling (using the mouse wheel as an
2277accelerator) while the control key is held down. This option
2278requires --enable-mousewheel to also be specified.
2279
2280=item --disable-new-selection
2281
2282Remove support for mouse selection style like that of xterm.
2283
2284=item --enable-dmalloc
2285
2286Use Gray Watson's malloc - which is good for debugging See
2287http://www.letters.com/dmalloc/ for details If you use either this or the
2288next option, you may need to edit src/Makefile after compiling to point
2289DINCLUDE and DLIB to the right places.
2290
2291You can only use either this option and the following (should
2292you use either) .
2293
2294=item --enable-dlmalloc
2295
2296Use Doug Lea's malloc - which is good for a production version
2297See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2298
2299=item --enable-smart-resize
2300
2301Add smart growth/shrink behaviour when changing font size via from hot
2302keys. This should keep in a fixed position the rxvt corner which is
2303closest to a corner of the screen.
2304
2305=item --enable-cursor-blink
2306
2307Add support for a blinking cursor.
2308
2309=item --enable-pointer-blank
2310
2311Add support to have the pointer disappear when typing or inactive.
2312
2313=item --with-name=NAME
2314
2315Set the basename for the installed binaries (default: urxvt, resulting in
2316urxvt, urxvtd etc.). Specify --with-name=rxvt to replace rxvt.
2317
2318=item --with-term=NAME
2319
2320Change the environmental variable for the terminal to NAME (default
2321"rxvt")
2322
2323=item --with-terminfo=PATH
2324
2325Change the environmental variable for the path to the terminfo tree to
2326PATH.
2327
2328=item --with-x
2329
2330Use the X Window System (pretty much default, eh?).
2331
2332=item --with-xpm-includes=DIR
2333
2334Look for the XPM includes in DIR.
2335
2336=item --with-xpm-library=DIR
2337
2338Look for the XPM library in DIR.
2339
2340=item --with-xpm
2341
2342Not needed - define via --enable-xpm-background.
2343
2344=back
2345
1395=head1 AUTHORS 2346=head1 AUTHORS
1396 2347
1397Marc Lehmann <rxvt@schmorp.de>, converted this document to pod and 2348Marc Lehmann <rxvt@schmorp.de> converted this document to pod and
1398reworked it from the original Rxvt documentation, which was done by Geoff 2349reworked it from the original Rxvt documentation, which was done by Geoff
1399Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other 2350Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other
1400sources. 2351sources.
1401 2352

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines