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.1 by root, Thu Aug 12 20:42:12 2004 UTC vs.
Revision 1.82 by root, Mon Jan 16 09:28:45 2006 UTC

1=head1 Rxvt Technical Reference 1=head1 NAME
2 2
3Marc Lehmann <rxvt@schmorp.de>, converted to pod and reworked from the 3RXVT REFERENCE - FAQ, command sequences and other background information
4original Rxvt documentation by Geoff Wing <gcw@pobox.com>, who in turn used 4
5the XTerm documentation and other sources. 5=head1 SYNOPSIS
6
7 # set a new font set
8 printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
9
10 # change the locale and tell rxvt-unicode about it
11 export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
12
13 # set window title
14 printf '\33]2;%s\007' "new window title"
15
16=head1 DESCRIPTION
17
18This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19all escape sequences, and other background information.
20
21The newest version of this document is
22also available on the World Wide Web at
23L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
24
25=head1 FREQUENTLY ASKED QUESTIONS
26
27=over 4
28
29=item The new selection selects pieces that are too big, how can I select
30single words?
31
32Yes. For example, if you want to select alphanumeric words, you can use
33the following resource:
34
35 URxvt.selection.pattern-0: ([[:word:]]+)
36
37If you click more than twice, the selection will be extended
38more and more.
39
40To get a selection that is very similar to the old code, try this pattern:
41
42 URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
43
44Please also note that the I<LeftClick Shift-LeftClik> combination also
45selects words like the old code.
46
47=item I don't like the new selection/popups/hotkeys/perl, how do I
48change/disable it?
49
50You can disable the perl extension completely by setting the
51B<perl-ext-common> resource to the empty string, which also keeps
52rxvt-unicode from initialising perl, saving memory.
53
54If you only want to disable specific features, you first have to
55identify which perl extension is responsible. For this, read the section
56B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For
57example, to disable the B<selection-popup> and B<option-popup>, specify
58this B<perl-ext-common> resource:
59
60 URxvt.perl-ext-common: default,-selection-popup,-option-popup
61
62This will keep the default extensions, but disable the two popup
63extensions. Some extensions can also be configured, for example,
64scrollback search mode is triggered by B<M-s>. You can move it to any
65other combination either by setting the B<searchable-scrollback> resource:
66
67 URxvt.searchable-scrollback: CM-s
68
69=item Isn't rxvt supposed to be small? Don't all those features bloat?
70
71I often get asked about this, and I think, no, they didn't cause extra
72bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
73that the urxvt binary is larger (due to some encoding tables always being
74compiled in), but it actually uses less memory (RSS) after startup. Even
75with C<--disable-everything>, this comparison is a bit unfair, as many
76features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
77already in use in this mode.
78
79 text data bss drs rss filename
80 98398 1664 24 15695 1824 rxvt --disable-everything
81 188985 9048 66616 18222 1788 urxvt --disable-everything
82
83When you C<--enable-everything> (which _is_ unfair, as this involves xft
84and full locale/XIM support which are quite bloaty inside libX11 and my
85libc), the two diverge, but not unreasnobaly so.
86
87 text data bss drs rss filename
88 163431 2152 24 20123 2060 rxvt --enable-everything
89 1035683 49680 66648 29096 3680 urxvt --enable-everything
90
91The very large size of the text section is explained by the east-asian
92encoding tables, which, if unused, take up disk space but nothing else
93and can be compiled out unless you rely on X11 core fonts that use those
94encodings. The BSS size comes from the 64k emergency buffer that my c++
95compiler allocates (but of course doesn't use unless you are out of
96memory). Also, using an xft font instead of a core font immediately adds a
97few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
98not used.
99
100Of course, due to every character using two or four bytes instead of one,
101a large scrollback buffer will ultimately make rxvt-unicode use more
102memory.
103
104Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
105still fares rather well. And compared to some monsters like gnome-terminal
106(21152k + extra 4204k in separate processes) or konsole (22200k + extra
10743180k in daemons that stay around after exit, plus half a minute of
108startup time, including the hundreds of warnings it spits out), it fares
109extremely well *g*.
110
111=item Why C++, isn't that unportable/bloated/uncool?
112
113Is this a question? :) It comes up very often. The simple answer is: I had
114to write it, and C++ allowed me to write and maintain it in a fraction
115of the time and effort (which is a scarce resource for me). Put even
116shorter: It simply wouldn't exist without C++.
117
118My personal stance on this is that C++ is less portable than C, but in
119the case of rxvt-unicode this hardly matters, as its portability limits
120are defined by things like X11, pseudo terminals, locale support and unix
121domain sockets, which are all less portable than C++ itself.
122
123Regarding the bloat, see the above question: It's easy to write programs
124in C that use gobs of memory, an certainly possible to write programs in
125C++ that don't. C++ also often comes with large libraries, but this is
126not necessarily the case with GCC. Here is what rxvt links against on my
127system with a minimal config:
128
129 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
130 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
131 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
132 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
133
134And here is rxvt-unicode:
135
136 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
137 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
138 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
139 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
140 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
141
142No large bloated libraries (of course, none were linked in statically),
143except maybe libX11 :)
144
145=item Does it support tabs, can I have a tabbed rxvt-unicode?
146
147rxvt-unicode does not directly support tabs. It will work fine with
148tabbing functionality of many window managers or similar tabbing programs,
149and its embedding-features allow it to be embedded into other programs,
150as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
151module, which features a tabbed urxvt (murxvt) terminal as an example
152embedding application.
153
154=item How do I know which rxvt-unicode version I'm using?
155
156The version number is displayed with the usage (-h). Also the escape
157sequence C<ESC [ 8 n> sets the window title to the version number. When
158using the @@RXVT_NAME@@c client, the version displayed is that of the
159daemon.
160
161=item I am using Debian GNU/Linux and have a problem...
162
163The Debian GNU/Linux package of rxvt-unicode in sarge contains large
164patches that considerably change the behaviour of rxvt-unicode. Before
165reporting a bug to the original rxvt-unicode author please download and
166install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
167and try to reproduce the problem. If you cannot, chances are that the
168problems are specific to Debian GNU/Linux, in which case it should be
169reported via the Debian Bug Tracking System (use C<reportbug> to report
170the bug).
171
172For other problems that also affect the Debian package, you can and
173probably should use the Debian BTS, too, because, after all, it's also a
174bug in the Debian version and it serves as a reminder for other users that
175might encounter the same issue.
176
177=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
178
179You should build one binary with the default options. F<configure>
180now enables most useful options, and the trend goes to making them
181runtime-switchable, too, so there is usually no drawback to enbaling them,
182except higher disk and possibly memory usage. The perl interpreter should
183be enabled, as important functionality (menus, selection, likely more in
184the future) depends on it.
185
186You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
187system-wide (except maybe with C<defaults>). This will result in useful
188behaviour. If your distribution aims at low memory, add an empty
189C<perl-ext-common> resource to the app-defaults file. This will keep the
190perl interpreter disabled until the user enables it.
191
192If you can/want build more binaries, I recommend building a minimal
193one with C<--disable-everything> (very useful) and a maximal one with
194C<--enable-everything> (less useful, it will be very big due to a lot of
195encodings built-in that increase download times and are rarely used).
196
197=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
198
199Likely not. While I honestly try to make it secure, and am probably not
200bad at it, I think it is simply unreasonable to expect all of freetype
201+ fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be
202secure. Also, rxvt-unicode disables some options when it detects that it
203runs setuid or setgid, which is not nice. Besides, with the embedded perl
204interpreter the possibility for security problems easily multiplies.
205
206Elevated privileges are only required for utmp and pty operations on some
207systems (for example, GNU/Linux doesn't need any extra privileges for
208ptys, but some need it for utmp support). It is planned to mvoe this into
209a forked handler process, but this is not yet done.
210
211So, while setuid/setgid operation is supported and not a problem on your
212typical single-user-no-other-logins unix desktop, always remember that
213its an awful lot of code, most of which isn't checked for security issues
214regularly.
215
216=item When I log-in to another system it tells me about missing terminfo data?
217
218The terminal description used by rxvt-unicode is not as widely available
219as that for xterm, or even rxvt (for which the same problem often arises).
220
221The correct solution for this problem is to install the terminfo, this can
222be done like this (with ncurses' infocmp):
223
224 REMOTE=remotesystem.domain
225 infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
226
227... or by installing rxvt-unicode normally on the remote system,
228
229If you cannot or do not want to do this, then you can simply set
230C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
231problems arising, which includes wrong keymapping, less and different
232colours and some refresh errors in fullscreen applications. It's a nice
233quick-and-dirty workaround for rare cases, though.
234
235If you always want to do this (and are fine with the consequences) you
236can either recompile rxvt-unicode with the desired TERM value or use a
237resource to set it:
238
239 URxvt.termName: rxvt
240
241If you don't plan to use B<rxvt> (quite common...) you could also replace
242the rxvt terminfo file with the rxvt-unicode one.
243
244=item C<tic> outputs some error when compiling the terminfo entry.
245
246Most likely it's the empty definition for C<enacs=>. Just replace it by
247C<enacs=\E[0@> and try again.
248
249=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
250
251=item I need a termcap file entry.
252
253One reason you might want this is that some distributions or operating
254systems still compile some programs using the long-obsoleted termcap
255library (Fedora Core's bash is one example) and rely on a termcap entry
256for C<rxvt-unicode>.
257
258You could use rxvt's termcap entry with resonable results in many cases.
259You can also create a termcap entry by using terminfo's infocmp program
260like this:
261
262 infocmp -C rxvt-unicode
263
264Or you could use this termcap entry, generated by the command above:
265
266 rxvt-unicode|rxvt-unicode terminal (X Window System):\
267 :am:bw:eo:km:mi:ms:xn:xo:\
268 :co#80:it#8:li#24:lm#0:\
269 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
270 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
271 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
272 :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
273 :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
274 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
275 :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
276 :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
277 :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
278 :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
279 :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
280 :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
281 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
282 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
283 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
284 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
285 :vs=\E[?25h:
286
287=item Why does C<ls> no longer have coloured output?
288
289The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
290decide wether a terminal has colour, but uses it's own configuration
291file. Needless to say, C<rxvt-unicode> is not in it's default file (among
292with most other terminals supporting colour). Either add:
293
294 TERM rxvt-unicode
295
296to C</etc/DIR_COLORS> or simply add:
297
298 alias ls='ls --color=auto'
299
300to your C<.profile> or C<.bashrc>.
301
302=item Why doesn't vim/emacs etc. use the 88 colour mode?
303
304=item Why doesn't vim/emacs etc. make use of italic?
305
306=item Why are the secondary screen-related options not working properly?
307
308Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
309distributions (most notably Debian GNU/Linux) break rxvt-unicode
310by setting C<TERM> to C<rxvt>, which doesn't have these extra
311features. Unfortunately, some of these (most notably, again, Debian
312GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
313file, so you will need to install it on your own (See the question B<When
314I log-in to another system it tells me about missing terminfo data?> on
315how to do this).
316
317=item My numerical keypad acts weird and generates differing output?
318
319Some Debian GNUL/Linux users seem to have this problem, although no
320specific details were reported so far. It is possible that this is caused
321by the wrong C<TERM> setting, although the details of wether and how
322this can happen are unknown, as C<TERM=rxvt> should offer a compatible
323keymap. See the answer to the previous question, and please report if that
324helped.
325
326=item Rxvt-unicode does not seem to understand the selected encoding?
327
328=item Unicode does not seem to work?
329
330If you encounter strange problems like typing an accented character but
331getting two unrelated other characters or similar, or if program output is
332subtly garbled, then you should check your locale settings.
333
334Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
335programs. Often rxvt-unicode is started in the C<C> locale, while the
336login script running within the rxvt-unicode window changes the locale to
337something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
338
339The best thing is to fix your startup environment, as you will likely run
340into other problems. If nothing works you can try this in your .profile.
341
342 printf '\e]701;%s\007' "$LC_CTYPE"
343
344If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
345supported on your systems. Some systems have a C<locale> command which
346displays this (also, C<perl -e0> can be used to check locale settings, as
347it will complain loudly if it cannot set the locale). If it displays something
348like:
349
350 locale: Cannot set LC_CTYPE to default locale: ...
351
352Then the locale you specified is not supported on your system.
353
354If nothing works and you are sure that everything is set correctly then
355you will need to remember a little known fact: Some programs just don't
356support locales :(
357
358=item Why do some characters look so much different than others?
359
360=item How does rxvt-unicode choose fonts?
361
362Most fonts do not contain the full range of Unicode, which is
363fine. Chances are that the font you (or the admin/package maintainer of
364your system/os) have specified does not cover all the characters you want
365to display.
366
367B<rxvt-unicode> makes a best-effort try at finding a replacement
368font. Often the result is fine, but sometimes the chosen font looks
369bad/ugly/wrong. Some fonts have totally strange characters that don't
370resemble the correct glyph at all, and rxvt-unicode lacks the artificial
371intelligence to detect that a specific glyph is wrong: it has to believe
372the font that the characters it claims to contain indeed look correct.
373
374In that case, select a font of your taste and add it to the font list,
375e.g.:
376
377 @@RXVT_NAME@@ -fn basefont,font2,font3...
378
379When rxvt-unicode sees a character, it will first look at the base
380font. If the base font does not contain the character, it will go to the
381next font, and so on. Specifying your own fonts will also speed up this
382search and use less resources within rxvt-unicode and the X-server.
383
384The only limitation is that none of the fonts may be larger than the base
385font, as the base font defines the terminal character cell size, which
386must be the same due to the way terminals work.
387
388=item Why do some chinese characters look so different than others?
389
390This is because there is a difference between script and language --
391rxvt-unicode does not know which language the text that is output is,
392as it only knows the unicode character codes. If rxvt-unicode first
393sees a japanese/chinese character, it might choose a japanese font for
394display. Subsequent japanese characters will use that font. Now, many
395chinese characters aren't represented in japanese fonts, so when the first
396non-japanese character comes up, rxvt-unicode will look for a chinese font
397-- unfortunately at this point, it will still use the japanese font for
398chinese characters that are also in the japanese font.
399
400The workaround is easy: just tag a chinese font at the end of your font
401list (see the previous question). The key is to view the font list as
402a preference list: If you expect more japanese, list a japanese font
403first. If you expect more chinese, put a chinese font first.
404
405In the future it might be possible to switch language preferences at
406runtime (the internal data structure has no problem with using different
407fonts for the same character at the same time, but no interface for this
408has been designed yet).
409
410Until then, you might get away with switching fonts at runtime (see L<Can
411I switch the fonts at runtime?> later in this document).
412
413=item Why does rxvt-unicode sometimes leave pixel droppings?
414
415Most fonts were not designed for terminal use, which means that character
416size varies a lot. A font that is otherwise fine for terminal use might
417contain some characters that are simply too wide. Rxvt-unicode will avoid
418these characters. For characters that are just "a bit" too wide a special
419"careful" rendering mode is used that redraws adjacent characters.
420
421All of this requires that fonts do not lie about character sizes,
422however: Xft fonts often draw glyphs larger than their acclaimed bounding
423box, and rxvt-unicode has no way of detecting this (the correct way is to
424ask for the character bounding box, which unfortunately is wrong in these
425cases).
426
427It's not clear (to me at least), wether this is a bug in Xft, freetype,
428or the respective font. If you encounter this problem you might try using
429the C<-lsp> option to give the font more height. If that doesn't work, you
430might be forced to use a different font.
431
432All of this is not a problem when using X11 core fonts, as their bounding
433box data is correct.
434
435=item On Solaris 9, many line-drawing characters are too wide.
436
437Seems to be a known bug, read
438L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
439following ugly workaround to get non-double-wide-characters working:
440
441 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
442
443=item My Compose (Multi_key) key is no longer working.
444
445The most common causes for this are that either your locale is not set
446correctly, or you specified a B<preeditStyle> that is not supported by
447your input method. For example, if you specified B<OverTheSpot> and
448your input method (e.g. the default input method handling Compose keys)
449does not support this (for instance because it is not visual), then
450rxvt-unicode will continue without an input method.
451
452In this case either do not specify a B<preeditStyle> or specify more than
453one pre-edit style, such as B<OverTheSpot,Root,None>.
454
455=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
456
457Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
458international keyboards) or simply use ISO 14755 support to your
459advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
460codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
461character and so on.
462
463=item How can I keep rxvt-unicode from using reverse video so much?
464
465First of all, make sure you are running with the right terminal settings
466(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
467make sure you have specified colours for italic and bold, as otherwise
468rxvt-unicode might use reverse video to simulate the effect:
469
470 URxvt.colorBD: white
471 URxvt.colorIT: green
472
473=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
474
475For some unexplainable reason, some rare programs assume a very weird
476colour palette when confronted with a terminal with more than the standard
4778 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
478these programs not to assume non-ISO colours without very good reasons.
479
480In the meantime, you can either edit your C<rxvt-unicode> terminfo
481definition to only claim 8 colour support or use C<TERM=rxvt>, which will
482fix colours but keep you from using other rxvt-unicode features.
483
484=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
485
486Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
487in your compile environment, or an implementation that implements it,
488wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
489B<wchar_t> is represented as unicode.
490
491As you might have guessed, FreeBSD does neither define this symobl nor
492does it support it. Instead, it uses it's own internal representation of
493B<wchar_t>. This is, of course, completely fine with respect to standards.
494
495However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
496C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
497
498C<__STDC_ISO_10646__> is the only sane way to support multi-language
499apps in an OS, as using a locale-dependent (and non-standardized)
500representation of B<wchar_t> makes it impossible to convert between
501B<wchar_t> (as used by X11 and your applications) and any other encoding
502without implementing OS-specific-wrappers for each and every locale. There
503simply are no APIs to convert B<wchar_t> into anything except the current
504locale encoding.
505
506Some applications (such as the formidable B<mlterm>) work around this
507by carrying their own replacement functions for character set handling
508with them, and either implementing OS-dependent hacks or doing multiple
509conversions (which is slow and unreliable in case the OS implements
510encodings slightly different than the terminal emulator).
511
512The rxvt-unicode author insists that the right way to fix this is in the
513system libraries once and for all, instead of forcing every app to carry
514complete replacements for them :)
515
516=item I use Solaris 9 and it doesn't compile/work/etc.
517
518Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
519problems with C<wcwidth> and a compile problem.
520
521=item How can I use rxvt-unicode under cygwin?
522
523rxvt-unicode should compile and run out of the box on cygwin, using
524the X11 libraries that come with cygwin. libW11 emulation is no
525longer supported (and makes no sense, either, as it only supported a
526single font). I recommend starting the X-server in C<-multiwindow> or
527C<-rootless> mode instead, which will result in similar look&feel as the
528old libW11 emulation.
529
530At the time of this writing, cygwin didn't seem to support any multi-byte
531encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
532to 8-bit encodings.
533
534=item How does rxvt-unicode determine the encoding to use?
535
536=item Is there an option to switch encodings?
537
538Unlike some other terminals, rxvt-unicode has no encoding switch, and no
539specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
540UTF-8 or any other encodings with respect to terminal I/O.
541
542The reasons is that there exists a perfectly fine mechanism for selecting
543the encoding, doing I/O and (most important) communicating this to all
544applications so everybody agrees on character properties such as width
545and code number. This mechanism is the I<locale>. Applications not using
546that info will have problems (for example, C<xterm> gets the width of
547characters wrong as it uses it's own, locale-independent table under all
548locales).
549
550Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
551programs doing the same (that is, most) will automatically agree in the
552interpretation of characters.
553
554Unfortunately, there is no system-independent way to select locales, nor
555is there a standard on how locale specifiers will look like.
556
557On most systems, the content of the C<LC_CTYPE> environment variable
558contains an arbitrary string which corresponds to an already-installed
559locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
560C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
561(i.e. C<de> or C<german>) are also common.
562
563Rxvt-unicode ignores all other locale categories, and except for
564the encoding, ignores country or language-specific settings,
565i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
566rxvt-unicode.
567
568If you want to use a specific encoding you have to make sure you start
569rxvt-unicode with the correct C<LC_CTYPE> category.
570
571=item Can I switch locales at runtime?
572
573Yes, using an escape sequence. Try something like this, which sets
574rxvt-unicode's idea of C<LC_CTYPE>.
575
576 printf '\e]701;%s\007' ja_JP.SJIS
577
578See also the previous answer.
579
580Sometimes this capability is rather handy when you want to work in
581one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
582(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
583first switches to a locale supported by xjdic and back later:
584
585 printf '\e]701;%s\007' ja_JP.SJIS
586 xjdic -js
587 printf '\e]701;%s\007' de_DE.UTF-8
588
589You can also use xterm's C<luit> program, which usually works fine, except
590for some locales where character width differs between program- and
591rxvt-unicode-locales.
592
593=item Can I switch the fonts at runtime?
594
595Yes, using an escape sequence. Try something like this, which has the same
596effect as using the C<-fn> switch, and takes effect immediately:
597
598 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
599
600This is useful if you e.g. work primarily with japanese (and prefer a
601japanese font), but you have to switch to chinese temporarily, where
602japanese fonts would only be in your way.
603
604You can think of this as a kind of manual ISO-2022 switching.
605
606=item Why do italic characters look as if clipped?
607
608Many fonts have difficulties with italic characters and hinting. For
609example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
610Mono> completely fails in it's italic face. A workaround might be to
611enable freetype autohinting, i.e. like this:
612
613 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
614 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
615
616=item My input method wants <some encoding> but I want UTF-8, what can I do?
617
618You can specify separate locales for the input method and the rest of the
619terminal, using the resource C<imlocale>:
620
621 URxvt*imlocale: ja_JP.EUC-JP
622
623Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
624use your input method. Please note, however, that you will not be able to
625input characters outside C<EUC-JP> in a normal way then, as your input
626method limits you.
627
628=item Rxvt-unicode crashes when the X Input Method changes or exits.
629
630Unfortunately, this is unavoidable, as the XIM protocol is racy by
631design. Applications can avoid some crashes at the expense of memory
632leaks, and Input Methods can avoid some crashes by careful ordering at
633exit time. B<kinput2> (and derived input methods) generally succeeds,
634while B<SCIM> (or similar input methods) fails. In the end, however,
635crashes cannot be completely avoided even if both sides cooperate.
636
637So the only workaround is not to kill your Input Method Servers.
638
639=item Rxvt-unicode uses gobs of memory, how can I reduce that?
640
641Rxvt-unicode tries to obey the rule of not charging you for something you
642don't use. One thing you should try is to configure out all settings that
643you don't need, for example, Xft support is a resource hog by design,
644when used. Compiling it out ensures that no Xft font will be loaded
645accidentally when rxvt-unicode tries to find a font for your characters.
646
647Also, many people (me included) like large windows and even larger
648scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
6496 bytes per screen cell. For a 160x?? window this amounts to almost a
650kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
651use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
652rxvt-unicode then uses 8 bytes per screen cell.
653
654=item Can I speed up Xft rendering somehow?
655
656Yes, the most obvious way to speed it up is to avoid Xft entirely, as
657it is simply slow. If you still want Xft fonts you might try to disable
658antialiasing (by appending C<:antialias=false>), which saves lots of
659memory and also speeds up rendering considerably.
660
661=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
662
663Rxvt-unicode will use whatever you specify as a font. If it needs to
664fall back to it's default font search list it will prefer X11 core
665fonts, because they are small and fast, and then use Xft fonts. It has
666antialiasing disabled for most of them, because the author thinks they
667look best that way.
668
669If you want antialiasing, you have to specify the fonts manually.
670
671=item Mouse cut/paste suddenly no longer works.
672
673Make sure that mouse reporting is actually turned off since killing
674some editors prematurely may leave the mouse in mouse report mode. I've
675heard that tcsh may use mouse reporting unless it otherwise specified. A
676quick check is to see if cut/paste works when the Alt or Shift keys are
677depressed.
678
679=item What's with this bold/blink stuff?
680
681If no bold colour is set via C<colorBD:>, bold will invert text using the
682standard foreground colour.
683
684For the standard background colour, blinking will actually make the
685text blink when compiled with C<--enable-blinking>. with standard
686colours. Without C<--enable-blinking>, the blink attribute will be
687ignored.
688
689On ANSI colours, bold/blink attributes are used to set high-intensity
690foreground/background colors.
691
692color0-7 are the low-intensity colors.
693
694color8-15 are the corresponding high-intensity colors.
695
696=item I don't like the screen colors. How do I change them?
697
698You can change the screen colors at run-time using F<~/.Xdefaults>
699resources (or as long-options).
700
701Here are values that are supposed to resemble a VGA screen,
702including the murky brown that passes for low-intensity yellow:
703
704 URxvt.color0: #000000
705 URxvt.color1: #A80000
706 URxvt.color2: #00A800
707 URxvt.color3: #A8A800
708 URxvt.color4: #0000A8
709 URxvt.color5: #A800A8
710 URxvt.color6: #00A8A8
711 URxvt.color7: #A8A8A8
712
713 URxvt.color8: #000054
714 URxvt.color9: #FF0054
715 URxvt.color10: #00FF54
716 URxvt.color11: #FFFF54
717 URxvt.color12: #0000FF
718 URxvt.color13: #FF00FF
719 URxvt.color14: #00FFFF
720 URxvt.color15: #FFFFFF
721
722And here is a more complete set of non-standard colors described (not by
723me) as "pretty girly".
724
725 URxvt.cursorColor: #dc74d1
726 URxvt.pointerColor: #dc74d1
727 URxvt.background: #0e0e0e
728 URxvt.foreground: #4ad5e1
729 URxvt.color0: #000000
730 URxvt.color8: #8b8f93
731 URxvt.color1: #dc74d1
732 URxvt.color9: #dc74d1
733 URxvt.color2: #0eb8c7
734 URxvt.color10: #0eb8c7
735 URxvt.color3: #dfe37e
736 URxvt.color11: #dfe37e
737 URxvt.color5: #9e88f0
738 URxvt.color13: #9e88f0
739 URxvt.color6: #73f7ff
740 URxvt.color14: #73f7ff
741 URxvt.color7: #e1dddd
742 URxvt.color15: #e1dddd
743
744=item How can I start @@RXVT_NAME@@d in a race-free way?
745
746Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
747display, create the listening socket and then fork.
748
749=item What's with the strange Backspace/Delete key behaviour?
750
751Assuming that the physical Backspace key corresponds to the
752BackSpace keysym (not likely for Linux ... see the following
753question) there are two standard values that can be used for
754Backspace: C<^H> and C<^?>.
755
756Historically, either value is correct, but rxvt-unicode adopts the debian
757policy of using C<^?> when unsure, because it's the one only only correct
758choice :).
759
760Rxvt-unicode tries to inherit the current stty settings and uses the value
761of `erase' to guess the value for backspace. If rxvt-unicode wasn't
762started from a terminal (say, from a menu or by remote shell), then the
763system value of `erase', which corresponds to CERASE in <termios.h>, will
764be used (which may not be the same as your stty setting).
765
766For starting a new rxvt-unicode:
767
768 # use Backspace = ^H
769 $ stty erase ^H
770 $ @@RXVT_NAME@@
771
772 # use Backspace = ^?
773 $ stty erase ^?
774 $ @@RXVT_NAME@@
775
776Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
777
778For an existing rxvt-unicode:
779
780 # use Backspace = ^H
781 $ stty erase ^H
782 $ echo -n "^[[36h"
783
784 # use Backspace = ^?
785 $ stty erase ^?
786 $ echo -n "^[[36l"
787
788This helps satisfy some of the Backspace discrepancies that occur, but
789if you use Backspace = C<^H>, make sure that the termcap/terminfo value
790properly reflects that.
791
792The Delete key is a another casualty of the ill-defined Backspace problem.
793To avoid confusion between the Backspace and Delete keys, the Delete
794key has been assigned an escape sequence to match the vt100 for Execute
795(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
796
797Some other Backspace problems:
798
799some editors use termcap/terminfo,
800some editors (vim I'm told) expect Backspace = ^H,
801GNU Emacs (and Emacs-like editors) use ^H for help.
802
803Perhaps someday this will all be resolved in a consistent manner.
804
805=item I don't like the key-bindings. How do I change them?
806
807There are some compile-time selections available via configure. Unless
808you have run "configure" with the C<--disable-resources> option you can
809use the `keysym' resource to alter the keystrings associated with keysyms.
810
811Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
812
813 URxvt.keysym.Home: \033[1~
814 URxvt.keysym.End: \033[4~
815 URxvt.keysym.C-apostrophe: \033<C-'>
816 URxvt.keysym.C-slash: \033<C-/>
817 URxvt.keysym.C-semicolon: \033<C-;>
818 URxvt.keysym.C-grave: \033<C-`>
819 URxvt.keysym.C-comma: \033<C-,>
820 URxvt.keysym.C-period: \033<C-.>
821 URxvt.keysym.C-0x60: \033<C-`>
822 URxvt.keysym.C-Tab: \033<C-Tab>
823 URxvt.keysym.C-Return: \033<C-Return>
824 URxvt.keysym.S-Return: \033<S-Return>
825 URxvt.keysym.S-space: \033<S-Space>
826 URxvt.keysym.M-Up: \033<M-Up>
827 URxvt.keysym.M-Down: \033<M-Down>
828 URxvt.keysym.M-Left: \033<M-Left>
829 URxvt.keysym.M-Right: \033<M-Right>
830 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
831 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
832 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
833
834See some more examples in the documentation for the B<keysym> resource.
835
836=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
837How do I make use of them? For example, the Sun Keyboard type 4
838has the following mappings that rxvt-unicode doesn't recognize.
839
840 KP_Insert == Insert
841 F22 == Print
842 F27 == Home
843 F29 == Prior
844 F33 == End
845 F35 == Next
846
847Rather than have rxvt-unicode try to accommodate all the various possible
848keyboard mappings, it is better to use `xmodmap' to remap the keys as
849required for your particular machine.
850
851=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
852I need this to decide about setting colors etc.
853
854rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
855check and see if that is set. Note that several programs, JED, slrn,
856Midnight Commander automatically check this variable to decide whether or
857not to use color.
858
859=item How do I set the correct, full IP address for the DISPLAY variable?
860
861If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
862insecure mode then it is possible to use the following shell script
863snippets to correctly set the display. If your version of rxvt-unicode
864wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
865the COLORTERM variable can be used to distinguish rxvt-unicode from a
866regular xterm.
867
868Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
869snippets:
870
871 # Bourne/Korn/POSIX family of shells:
872 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
873 if [ ${TERM:-foo} = xterm ]; then
874 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
875 echo -n '^[Z'
876 read term_id
877 stty icanon echo
878 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
879 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
880 read DISPLAY # set it in our local shell
881 fi
882 fi
883
884=item How do I compile the manual pages for myself?
885
886You need to have a recent version of perl installed as F</usr/bin/perl>,
887one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
888the doc subdirectory and enter C<make alldoc>.
889
890=item My question isn't answered here, can I ask a human?
891
892Before sending me mail, you could go to IRC: C<irc.freenode.net>,
893channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
894interested in learning about new and exciting problems (but not FAQs :).
895
896=back
897
898=head1 RXVT TECHNICAL REFERENCE
899
900=head1 DESCRIPTION
901
902The rest of this document describes various technical aspects of
903B<rxvt-unicode>. First the description of supported command sequences,
904followed by menu and pixmap support and last by a description of all
905features selectable at C<configure> time.
6 906
7=head1 Definitions 907=head1 Definitions
8 908
9=over 4 909=over 4
10 910
37=over 4 937=over 4
38 938
39=item B<< C<ENQ> >> 939=item B<< C<ENQ> >>
40 940
41Enquiry (Ctrl-E) = Send Device Attributes (DA) 941Enquiry (Ctrl-E) = Send Device Attributes (DA)
42request attributes from terminal == 942request attributes from terminal. See B<< C<ESC [ Ps c> >>.
43 943
44=item B<< C<BEL> >> 944=item B<< C<BEL> >>
45 945
46Bell (Ctrl-G) 946Bell (Ctrl-G)
47 947
139Single Shift Select of G3 Character Set (SS3): affects next character 1039Single Shift Select of G3 Character Set (SS3): affects next character
140only I<unimplemented> 1040only I<unimplemented>
141 1041
142=item B<< C<ESC Z> >> 1042=item B<< C<ESC Z> >>
143 1043
144Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt compile-time option> 1044Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option>
145 1045
146=item B<< C<ESC c> >> 1046=item B<< C<ESC c> >>
147 1047
148Full reset (RIS) 1048Full reset (RIS)
149 1049
153 1053
154=item B<< C<ESC o> >> 1054=item B<< C<ESC o> >>
155 1055
156Invoke the G3 Character Set (LS3) 1056Invoke the G3 Character Set (LS3)
157 1057
158=item B<< C<ESC>(C<C> >> 1058=item B<< C<ESC ( C> >>
159 1059
160Designate G0 Character Set (ISO 2022), see below for values of C<C>. 1060Designate G0 Character Set (ISO 2022), see below for values of C<C>.
161 1061
162=item B<< C<ESC>)C<C> >> 1062=item B<< C<ESC ) C> >>
163 1063
164Designate G1 Character Set (ISO 2022), see below for values of C<C>. 1064Designate G1 Character Set (ISO 2022), see below for values of C<C>.
165 1065
166=item B<< C<ESC * C> >> 1066=item B<< C<ESC * C> >>
167 1067
191 1091
192=back 1092=back
193 1093
194X<CSI> 1094X<CSI>
195 1095
196=head1 CSI (Code Sequence Introducer) Sequences 1096=head1 CSI (Command Sequence Introducer) Sequences
197 1097
198=over 4 1098=over 4
199 1099
200=item B<< C<ESC [ Ps @> >> 1100=item B<< C<ESC [ Ps @> >>
201 1101
298 1198
299Move backward B<< C<Ps> >> [default: 1] tab stops 1199Move backward B<< C<Ps> >> [default: 1] tab stops
300 1200
301=item B<< C<ESC [ Ps '> >> 1201=item B<< C<ESC [ Ps '> >>
302 1202
303== 1203See B<< C<ESC [ Ps G> >>
304 1204
305=item B<< C<ESC [ Ps a> >> 1205=item B<< C<ESC [ Ps a> >>
306 1206
307==X<ESCOBPsc> 1207See B<< C<ESC [ Ps C> >>
308 1208
309=item B<< C<ESC [ Ps c> >> 1209=item B<< C<ESC [ Ps c> >>
310 1210
311Send Device Attributes (DA) 1211Send Device Attributes (DA)
312B<< C<Ps = 0> >> (or omitted): request attributes from terminal 1212B<< C<Ps = 0> >> (or omitted): request attributes from terminal
313returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video 1213returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video
314Option'') 1214Option'')
315 1215
316=item B<< C<ESC [ Ps d> >> 1216=item B<< C<ESC [ Ps d> >>
317 1217
318Cursor to Line B<< C<Ps> >> (VPA) 1218Cursor to Line B<< C<Ps> >> (VPA)
319 1219
320=item B<< C<ESC [ Ps e> >> 1220=item B<< C<ESC [ Ps e> >>
321 1221
322== 1222See B<< C<ESC [ Ps A> >>
323 1223
324=item B<< C<ESC [ Ps;Ps f> >> 1224=item B<< C<ESC [ Ps;Ps f> >>
325 1225
326Horizontal and Vertical Position [row;column] (HVP) [default: 1;1] 1226Horizontal and Vertical Position [row;column] (HVP) [default: 1;1]
327 1227
334 B<< C<Ps = 0> >> Clear Current Column (default) 1234 B<< C<Ps = 0> >> Clear Current Column (default)
335 B<< C<Ps = 3> >> Clear All (TBC) 1235 B<< C<Ps = 3> >> Clear All (TBC)
336 1236
337=end table 1237=end table
338 1238
1239=item B<< C<ESC [ Pm h> >>
1240
1241Set Mode (SM). See B<< C<ESC [ Pm l> >> sequence for description of C<Pm>.
1242
339=item B<< C<ESC [ Ps i> >> 1243=item B<< C<ESC [ Ps i> >>
340 1244
341Printing 1245Printing. See also the C<print-pipe> resource.
342 1246
343=begin table 1247=begin table
344 1248
1249 B<< C<Ps = 0> >> print screen (MC0)
345 B<< C<Ps = 4> >> disable transparent print mode (MC4) 1250 B<< C<Ps = 4> >> disable transparent print mode (MC4)
346 B<< C<Ps = 5> >> enable transparent print mode (MC5) I<unimplemented> 1251 B<< C<Ps = 5> >> enable transparent print mode (MC5)
347 1252
348=end table 1253=end table
349
350=item B<< C<ESC [ Pm h> >>
351
352Set Mode (SM). See next sequence for description of C<Pm>.
353 1254
354=item B<< C<ESC [ Pm l> >> 1255=item B<< C<ESC [ Pm l> >>
355 1256
356Reset Mode (RM) 1257Reset Mode (RM)
357 1258
364 B<< C<h> >> Insert Mode (SMIR) 1265 B<< C<h> >> Insert Mode (SMIR)
365 B<< C<l> >> Replace Mode (RMIR) 1266 B<< C<l> >> Replace Mode (RMIR)
366 1267
367=end table 1268=end table
368 1269
369=item B<< C<Ps = 20> >> I<unimplemented> 1270=item B<< C<Ps = 20> >> (partially implemented)
370 1271
371=begin table 1272=begin table
372 1273
373 B<< C<h> >> Automatic Newline (LNM) 1274 B<< C<h> >> Automatic Newline (LNM)
374 B<< C<h> >> Normal Linefeed (LNM) 1275 B<< C<l> >> Normal Linefeed (LNM)
375 1276
376=end table 1277=end table
377 1278
378=back 1279=back
379 1280
382Character Attributes (SGR) 1283Character Attributes (SGR)
383 1284
384=begin table 1285=begin table
385 1286
386 B<< C<Ps = 0> >> Normal (default) 1287 B<< C<Ps = 0> >> Normal (default)
387 B<< C<Ps = 1 / 22> >> On / Off Bold (bright fg) 1288 B<< C<Ps = 1 / 21> >> On / Off Bold (bright fg)
1289 B<< C<Ps = 3 / 23> >> On / Off Italic
388 B<< C<Ps = 4 / 24> >> On / Off Underline 1290 B<< C<Ps = 4 / 24> >> On / Off Underline
389 B<< C<Ps = 5 / 25> >> On / Off Blink (bright bg) 1291 B<< C<Ps = 5 / 25> >> On / Off Slow Blink (bright bg)
1292 B<< C<Ps = 6 / 26> >> On / Off Rapid Blink (bright bg)
390 B<< C<Ps = 7 / 27> >> On / Off Inverse 1293 B<< C<Ps = 7 / 27> >> On / Off Inverse
1294 B<< C<Ps = 8 / 27> >> On / Off Invisible (NYI)
391 B<< C<Ps = 30 / 40> >> fg/bg Black 1295 B<< C<Ps = 30 / 40> >> fg/bg Black
392 B<< C<Ps = 31 / 41> >> fg/bg Red 1296 B<< C<Ps = 31 / 41> >> fg/bg Red
393 B<< C<Ps = 32 / 42> >> fg/bg Green 1297 B<< C<Ps = 32 / 42> >> fg/bg Green
394 B<< C<Ps = 33 / 43> >> fg/bg Yellow 1298 B<< C<Ps = 33 / 43> >> fg/bg Yellow
395 B<< C<Ps = 34 / 44> >> fg/bg Blue 1299 B<< C<Ps = 34 / 44> >> fg/bg Blue
396 B<< C<Ps = 35 / 45> >> fg/bg Magenta 1300 B<< C<Ps = 35 / 45> >> fg/bg Magenta
397 B<< C<Ps = 36 / 46> >> fg/bg Cyan 1301 B<< C<Ps = 36 / 46> >> fg/bg Cyan
1302 B<< C<Ps = 38;5 / 48;5> >> set fg/bg to color #m (ISO 8613-6)
398 B<< C<Ps = 37 / 47> >> fg/bg White 1303 B<< C<Ps = 37 / 47> >> fg/bg White
399 B<< C<Ps = 39 / 49> >> fg/bg Default 1304 B<< C<Ps = 39 / 49> >> fg/bg Default
1305 B<< C<Ps = 90 / 100> >> fg/bg Bright Black
1306 B<< C<Ps = 91 / 101> >> fg/bg Bright Red
1307 B<< C<Ps = 92 / 102> >> fg/bg Bright Green
1308 B<< C<Ps = 93 / 103> >> fg/bg Bright Yellow
1309 B<< C<Ps = 94 / 104> >> fg/bg Bright Blue
1310 B<< C<Ps = 95 / 105> >> fg/bg Bright Magenta
1311 B<< C<Ps = 96 / 106> >> fg/bg Bright Cyan
1312 B<< C<Ps = 97 / 107> >> fg/bg Bright White
1313 B<< C<Ps = 99 / 109> >> fg/bg Bright Default
400 1314
401=end table 1315=end table
402 1316
403=item B<< C<ESC [ Ps n> >> 1317=item B<< C<ESC [ Ps n> >>
404 1318
420 1334
421=item B<< C<ESC [ s> >> 1335=item B<< C<ESC [ s> >>
422 1336
423Save Cursor (SC) 1337Save Cursor (SC)
424 1338
1339=item B<< C<ESC [ Ps;Pt t> >>
1340
1341Window Operations
1342
1343=begin table
1344
1345 B<< C<Ps = 1> >> Deiconify (map) window
1346 B<< C<Ps = 2> >> Iconify window
1347 B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X|Y)
1348 B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
1349 B<< C<Ps = 5> >> Raise window
1350 B<< C<Ps = 6> >> Lower window
1351 B<< C<Ps = 7> >> Refresh screen once
1352 B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
1353 B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
1354 B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
1355 B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
1356 B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
1357 B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
1358 B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
1359 B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>)
1360 B<< C<Ps = 24..> >> Set window height to C<Ps> rows
1361
1362=end table
1363
1364=item B<< C<ESC [ u> >>
1365
1366Restore Cursor
1367
425=item B<< C<ESC [ Ps x> >> 1368=item B<< C<ESC [ Ps x> >>
426 1369
427Request Terminal Parameters (DECREQTPARM) 1370Request Terminal Parameters (DECREQTPARM)
428
429=item B<< C<ESC [ u> >>
430
431Restore Cursor
432 1371
433=back 1372=back
434 1373
435X<PrivateModes> 1374X<PrivateModes>
436 1375
539 B<< C<h> >> Send Mouse X & Y on button press. 1478 B<< C<h> >> Send Mouse X & Y on button press.
540 B<< C<l> >> No mouse reporting. 1479 B<< C<l> >> No mouse reporting.
541 1480
542=end table 1481=end table
543 1482
544)X<Priv10>
545
546=item B<< C<Ps = 10> >> (B<rxvt>) 1483=item B<< C<Ps = 10> >> (B<rxvt>)
547 1484
548=begin table 1485=begin table
549 1486
550 B<< C<h> >> visible 1487 B<< C<h> >> menuBar visible
551 B<< C<l> >> invisible 1488 B<< C<l> >> menuBar invisible
552 1489
553=end table 1490=end table
554 1491
555=item B<< C<Ps = 25> >> 1492=item B<< C<Ps = 25> >>
556 1493
625 1562
626=item B<< C<Ps = 66> >> 1563=item B<< C<Ps = 66> >>
627 1564
628=begin table 1565=begin table
629 1566
630 B<< C<h> >> Application Keypad (DECPAM) == 1567 B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
631 B<< C<l> >> Normal Keypad (DECPNM) == 1568 B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
632 1569
633=end table 1570=end table
634 1571
635=item B<< C<Ps = 67> >> 1572=item B<< C<Ps = 67> >>
636 1573
657 B<< C<h> >> Use Hilite Mouse Tracking. 1594 B<< C<h> >> Use Hilite Mouse Tracking.
658 B<< C<l> >> No mouse reporting. 1595 B<< C<l> >> No mouse reporting.
659 1596
660=end table 1597=end table
661 1598
662=item B<< C<Ps = 1010> >> 1599=item B<< C<Ps = 1010> >> (B<rxvt>)
663 1600
664=begin table 1601=begin table
665 1602
666 B<< C<h> >> Don't scroll to bottom on TTY output 1603 B<< C<h> >> Don't scroll to bottom on TTY output
667 B<< C<l> >> Scroll to bottom on TTY output 1604 B<< C<l> >> Scroll to bottom on TTY output
668 1605
669=end table 1606=end table
670 1607
671=item B<< C<Ps = 1011> >> 1608=item B<< C<Ps = 1011> >> (B<rxvt>)
672 1609
673=begin table 1610=begin table
674 1611
675 B<< C<h> >> Scroll to bottom when a key is pressed 1612 B<< C<h> >> Scroll to bottom when a key is pressed
676 B<< C<l> >> Don't scroll to bottom when a key is pressed 1613 B<< C<l> >> Don't scroll to bottom when a key is pressed
677 1614
678=end table 1615=end table
679 1616
1617=item B<< C<Ps = 1021> >> (B<rxvt>)
1618
1619=begin table
1620
1621 B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
1622 B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1623
1624=end table
1625
680=item B<< C<Ps = 1047> >> 1626=item B<< C<Ps = 1047> >>
681 1627
682=begin table 1628=begin table
683 1629
684 B<< C<h> >> Use Alternate Screen Buffer 1630 B<< C<h> >> Use Alternate Screen Buffer
690 1636
691=begin table 1637=begin table
692 1638
693 B<< C<h> >> Save cursor position 1639 B<< C<h> >> Save cursor position
694 B<< C<l> >> Restore cursor position 1640 B<< C<l> >> Restore cursor position
1641
1642=end table
1643
1644=item B<< C<Ps = 1049> >>
1645
1646=begin table
1647
1648 B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1649 B<< C<l> >> Use Normal Screen Buffer
695 1650
696=end table 1651=end table
697 1652
698=back 1653=back
699 1654
721 B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)> 1676 B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>
722 B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)> 1677 B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>
723 B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >> 1678 B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
724 B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> 1679 B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
725 B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >> 1680 B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
726 B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> 1681 B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
727 B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> 1682 B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
728 B<< C<Ps = 20> >> Change default background to B<< C<Pt> >> 1683 B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
729 B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option> 1684 B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
730 B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> 1685 B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
731 B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option> 1686 B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
732 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> >> 1687 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> >>
733 B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> 1688 B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
734 B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (@@RXVTNAME@@ extension) 1689 B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).
735 B<< C<Ps = 702> >> find font for character, used for debugging (@@RXVTNAME@@ extension) 1690 B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).
736 B<< C<Ps = 703> >> command B<< C<Pt> >> I<rxvt compile-time option> (@@RXVTNAME@@ extension) 1691 B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1692 B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1693 B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
1694 B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1695 B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1696 B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1697 B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1698 B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1699 B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1700 B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1701 B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
737 1702
738=end table 1703=end table
739 1704
740=back 1705=back
741 1706
793 1758
794=item B<< [title:+I<string>] >> 1759=item B<< [title:+I<string>] >>
795 1760
796set the current menuBar's title to I<string>, which may contain the 1761set the current menuBar's title to I<string>, which may contain the
797following format specifiers: 1762following format specifiers:
798B<%%> : literal B<%> character 1763
799B<%n> : rxvt name (as per the B<-name> command-line option) 1764 B<%n> rxvt name (as per the B<-name> command-line option)
800B<%v> : rxvt version 1765 B<%v> rxvt version
1766 B<%%> literal B<%> character
801 1767
802=item B<[done]> 1768=item B<[done]>
803 1769
804set menuBar access as B<readonly>. 1770set menuBar access as B<readonly>.
805End-of-file tag for B<< [read:+I<file>] >> operations. 1771End-of-file tag for B<< [read:+I<file>] >> operations.
951 1917
952As a convenience for the many Emacs-type editors, I<action> may start 1918As a convenience for the many Emacs-type editors, I<action> may start
953with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be 1919with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
954appended if missed from B<M-x> commands. 1920appended if missed from B<M-x> commands.
955 1921
956As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or 1922As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
957quick arrow), a B<BEL> (B<^G>) will be appended if needed. 1923quick arrow), a B<BEL> (B<^G>) will be appended if needed.
958 1924
959=over 4 1925=over 4
960 1926
961=item For example, 1927=item For example,
1320 2286
1321Row = B<< C<< <y> - SPACE >> >> 2287Row = B<< C<< <y> - SPACE >> >>
1322 2288
1323=back 2289=back
1324X<KeyCodes> 2290X<KeyCodes>
1325
1326=head1 ISO 14755 support
1327
1328Partial ISO 14755-support is implemented. that means that pressing
1329
1330section 5.1: Control and Shift together enters unicode input
1331mode. Entering hex digits composes a Unicode character, pressing space or
1332releasing the modifiers commits the keycode and every other key cancels
1333the current input character.
1334
1335section 5.2: Pressing and immediately releasing Control and Shift together
1336enters keycap entry mode for the next key: pressing a function key (tab,
1337return etc..) will enter the unicode character corresponding to the given
1338key.
1339 2291
1340=head1 Key Codes 2292=head1 Key Codes
1341 2293
1342Note: B<Shift> + B<F1>-B<F10> generates B<F11>-B<F20> 2294Note: B<Shift> + B<F1>-B<F10> generates B<F11>-B<F20>
1343 2295
1408 XK_KP_8 8 ESC O x 2360 XK_KP_8 8 ESC O x
1409 XK_KP_9 9 ESC O y 2361 XK_KP_9 9 ESC O y
1410 2362
1411=end table 2363=end table
1412 2364
2365=head1 CONFIGURE OPTIONS
2366
2367General hint: if you get compile errors, then likely your configuration
2368hasn't been tested well. Either try with C<--enable-everything> or use
2369the F<./reconf> script as a base for experiments. F<./reconf> is used by
2370myself, so it should generally be a working config. Of course, you should
2371always report when a combination doesn't work, so it can be fixed. Marc
2372Lehmann <rxvt@schmorp.de>.
2373
2374All
2375
2376=over 4
2377
2378=item --enable-everything
2379
2380Add (or remove) support for all non-multichoice options listed in "./configure
2381--help".
2382
2383You can specify this and then disable options you do not like by
2384I<following> this with the appropriate C<--disable-...> arguments,
2385or you can start with a minimal configuration by specifying
2386C<--disable-everything> and than adding just the C<--enable-...> arguments
2387you want.
2388
2389=item --enable-xft (default: enabled)
2390
2391Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2392slower and require lots of memory, but as long as you don't use them, you
2393don't pay for them.
2394
2395=item --enable-font-styles (default: on)
2396
2397Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2398styles. The fonts can be set manually or automatically.
2399
2400=item --with-codesets=NAME,... (default: all)
2401
2402Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2403are always compiled in, which includes most 8-bit character sets). These
2404codeset tables are used for driving X11 core fonts, they are not required
2405for Xft fonts, although having them compiled in lets rxvt-unicode choose
2406replacement fonts more intelligently. Compiling them in will make your
2407binary bigger (all of together cost about 700kB), but it doesn't increase
2408memory usage unless you use a font requiring one of these encodings.
2409
2410=begin table
2411
2412 all all available codeset groups
2413 zh common chinese encodings
2414 zh_ext rarely used but very big chinese encodigs
2415 jp common japanese encodings
2416 jp_ext rarely used but big japanese encodings
2417 kr korean encodings
2418
2419=end table
2420
2421=item --enable-xim (default: on)
2422
2423Add support for XIM (X Input Method) protocol. This allows using
2424alternative input methods (e.g. kinput2) and will also correctly
2425set up the input for people using dead keys or compose keys.
2426
2427=item --enable-unicode3 (default: off)
2428
2429Enable direct support for displaying unicode codepoints above
243065535 (the basic multilingual page). This increases storage
2431requirements per character from 2 to 4 bytes. X11 fonts do not yet
2432support these extra characters, but Xft does.
2433
2434Please note that rxvt-unicode can store unicode code points >65535
2435even without this flag, but the number of such characters is
2436limited to a view thousand (shared with combining characters,
2437see next switch), and right now rxvt-unicode cannot display them
2438(input/output and cut&paste still work, though).
2439
2440=item --enable-combining (default: on)
2441
2442Enable automatic composition of combining characters into
2443composite characters. This is required for proper viewing of text
2444where accents are encoded as seperate unicode characters. This is
2445done by using precomposited characters when available or creating
2446new pseudo-characters when no precomposed form exists.
2447
2448Without --enable-unicode3, the number of additional precomposed characters
2449is rather limited (2048, if this is full, rxvt-unicode will use the
2450private use area, extending the number of combinations to 8448). With
2451--enable-unicode3, no practical limit exists.
2452
2453This option will also enable storage (but not display) of characters
2454beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2455
2456The combining table also contains entries for arabic presentation forms,
2457but these are not currently used. Bug me if you want these to be used (and
2458tell me how these are to be used...).
2459
2460=item --enable-fallback(=CLASS) (default: Rxvt)
2461
2462When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.
2463
2464=item --with-res-name=NAME (default: urxvt)
2465
2466Use the given name as default application name when
2467reading resources. Specify --with-res-name=rxvt to replace rxvt.
2468
2469=item --with-res-class=CLASS /default: URxvt)
2470
2471Use the given class as default application class
2472when reading resources. Specify --with-res-class=Rxvt to replace
2473rxvt.
2474
2475=item --enable-utmp (default: on)
2476
2477Write user and tty to utmp file (used by programs like F<w>) at
2478start of rxvt execution and delete information when rxvt exits.
2479
2480=item --enable-wtmp (default: on)
2481
2482Write user and tty to wtmp file (used by programs like F<last>) at
2483start of rxvt execution and write logout when rxvt exits. This
2484option requires --enable-utmp to also be specified.
2485
2486=item --enable-lastlog (default: on)
2487
2488Write user and tty to lastlog file (used by programs like
2489F<lastlogin>) at start of rxvt execution. This option requires
2490--enable-utmp to also be specified.
2491
2492=item --enable-xpm-background (default: on)
2493
2494Add support for XPM background pixmaps.
2495
2496=item --enable-transparency (default: on)
2497
2498Add support for inheriting parent backgrounds thus giving a fake
2499transparency to the term.
2500
2501=item --enable-fading (default: on)
2502
2503Add support for fading the text when focus is lost (requires C<--enable-transparency>).
2504
2505=item --enable-tinting (default: on)
2506
2507Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2508
2509=item --enable-menubar (default: off) [DEPRECATED]
2510
2511Add support for our menu bar system (this interacts badly with dynamic
2512locale switching currently). This option is DEPRECATED and will be removed
2513in the future.
2514
2515=item --enable-rxvt-scroll (default: on)
2516
2517Add support for the original rxvt scrollbar.
2518
2519=item --enable-next-scroll (default: on)
2520
2521Add support for a NeXT-like scrollbar.
2522
2523=item --enable-xterm-scroll (default: on)
2524
2525Add support for an Xterm-like scrollbar.
2526
2527=item --enable-plain-scroll (default: on)
2528
2529Add support for a very unobtrusive, plain-looking scrollbar that
2530is the favourite of the rxvt-unicode author, having used it for
2531many years.
2532
2533=item --enable-half-shadow (default: off)
2534
2535Make shadows on the scrollbar only half the normal width & height.
2536only applicable to rxvt scrollbars.
2537
2538=item --enable-ttygid (default: off)
2539
2540Change tty device setting to group "tty" - only use this if
2541your system uses this type of security.
2542
2543=item --disable-backspace-key
2544
2545Removes any handling of the backspace key by us - let the X server do it.
2546
2547=item --disable-delete-key
2548
2549Removes any handling of the delete key by us - let the X server
2550do it.
2551
2552=item --disable-resources
2553
2554Removes any support for resource checking.
2555
2556=item --disable-swapscreen
2557
2558Remove support for secondary/swap screen.
2559
2560=item --enable-frills (default: on)
2561
2562Add support for many small features that are not essential but nice to
2563have. Normally you want this, but for very small binaries you may want to
2564disable this.
2565
2566A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2567in combination with other switches) is:
2568
2569 MWM-hints
2570 EWMH-hints (pid, utf8 names) and protocols (ping)
2571 seperate underline colour (-underlineColor)
2572 settable border widths and borderless switch (-w, -b, -bl)
2573 settable extra linespacing /-lsp)
2574 iso-14755-2 and -3, and visual feedback
2575 backindex and forwardindex escape sequence
2576 window op and some xterm/OSC escape sequences
2577 tripleclickwords (-tcw)
2578 settable insecure mode (-insecure)
2579 keysym remapping support
2580 cursor blinking and underline cursor (-cb, -uc)
2581 XEmbed support (-embed)
2582 user-pty (-pty-fd)
2583 hold on exit (-hold)
2584 skip builtin block graphics (-sbg)
2585 sgr modes 90..97 and 100..107
2586
2587=item --enable-iso14755 (default: on)
2588
2589Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2590F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
2591C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2592this switch.
2593
2594=item --enable-keepscrolling (default: on)
2595
2596Add support for continual scrolling of the display when you hold
2597the mouse button down on a scrollbar arrow.
2598
2599=item --enable-mousewheel (default: on)
2600
2601Add support for scrolling via mouse wheel or buttons 4 & 5.
2602
2603=item --enable-slipwheeling (default: on)
2604
2605Add support for continual scrolling (using the mouse wheel as an
2606accelerator) while the control key is held down. This option
2607requires --enable-mousewheel to also be specified.
2608
2609=item --disable-new-selection
2610
2611Remove support for mouse selection style like that of xterm.
2612
2613=item --enable-dmalloc (default: off)
2614
2615Use Gray Watson's malloc - which is good for debugging See
2616http://www.letters.com/dmalloc/ for details If you use either this or the
2617next option, you may need to edit src/Makefile after compiling to point
2618DINCLUDE and DLIB to the right places.
2619
2620You can only use either this option and the following (should
2621you use either) .
2622
2623=item --enable-dlmalloc (default: off)
2624
2625Use Doug Lea's malloc - which is good for a production version
2626See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2627
2628=item --enable-smart-resize (default: on)
2629
2630Add smart growth/shrink behaviour when changing font size via hot
2631keys. This should keep the window corner which is closest to a corner of
2632the screen in a fixed position.
2633
2634=item --enable-pointer-blank (default: on)
2635
2636Add support to have the pointer disappear when typing or inactive.
2637
2638=item --enable-perl (default: off)
2639
2640Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2641manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
2642in F<src/perl-ext/> for the extensions that are installed by default. The
2643perl interpreter that is used can be specified via the C<PERL> environment
2644variable when running configure.
2645
2646=item --with-name=NAME (default: urxvt)
2647
2648Set the basename for the installed binaries, resulting
2649in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
2650C<rxvt>.
2651
2652=item --with-term=NAME (default: rxvt-unicode)
2653
2654Change the environmental variable for the terminal to NAME.
2655
2656=item --with-terminfo=PATH
2657
2658Change the environmental variable for the path to the terminfo tree to
2659PATH.
2660
2661=item --with-x
2662
2663Use the X Window System (pretty much default, eh?).
2664
2665=item --with-xpm-includes=DIR
2666
2667Look for the XPM includes in DIR.
2668
2669=item --with-xpm-library=DIR
2670
2671Look for the XPM library in DIR.
2672
2673=item --with-xpm
2674
2675Not needed - define via --enable-xpm-background.
2676
2677=back
2678
2679=head1 AUTHORS
2680
2681Marc Lehmann <rxvt@schmorp.de> converted this document to pod and
2682reworked it from the original Rxvt documentation, which was done by Geoff
2683Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other
2684sources.
2685

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines