ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.23 by root, Wed Aug 25 03:47:20 2004 UTC vs.
Revision 1.74 by root, Mon Jan 9 07:24:43 2006 UTC

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

Diff Legend

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