[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.34 by root, Thu Feb 3 10:24:10 2005 UTC vs.
Revision 1.78 by root, Thu Jan 12 05:37:34 2006 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	RXVT REFERENCE - FAQ, command sequences and other background information	3	RXVT REFERENCE - FAQ, command sequences and other background information
4		4
		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
		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
5	=head1 FREQUENTLY ASKED QUESTIONS	25	=head1 FREQUENTLY ASKED QUESTIONS
6		26
7	=over 4	27	=over 4
8		28
		29	=item I don't like the new selection/popups/hotkeys/perl, how do I
		30	change/disable it?
		31
		32	You can disable the perl extension completely by setting the
		33	B<perl-ext-common> resource to the empty string, which also keeps
		34	rxvt-unicode from initialising perl, saving memory.
		35
		36	If you only want to disable specific features, you first have to
		37	identify which perl extension is responsible. For this, read the section
		38	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For
		39	example, to disable the B<selection-popup> and B<option-popup>, specify
		40	this B<perl-ext-common> resource:
		41
		42	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		43
		44	This will keep the default extensions, but disable the two popup
		45	extensions. Some extensions can also be configured, for example,
		46	scrollback search mode is triggered by B<M-s>. You can move it to any
		47	other combination either by setting the B<searchable-scrollback> resource:
		48
		49	URxvt.searchable-scrollback: CM-s
		50
		51	=item Isn't rxvt supposed to be small? Don't all those features bloat?
		52
		53	I often get asked about this, and I think, no, they didn't cause extra
		54	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
		55	that the urxvt binary is larger (due to some encoding tables always being
		56	compiled in), but it actually uses less memory (RSS) after startup. Even
		57	with C<--disable-everything>, this comparison is a bit unfair, as many
		58	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		59	already in use in this mode.
		60
		61	text data bss drs rss filename
		62	98398 1664 24 15695 1824 rxvt --disable-everything
		63	188985 9048 66616 18222 1788 urxvt --disable-everything
		64
		65	When you C<--enable-everything> (which _is_ unfair, as this involves xft
		66	and full locale/XIM support which are quite bloaty inside libX11 and my
		67	libc), the two diverge, but not unreasnobaly so.
		68
		69	text data bss drs rss filename
		70	163431 2152 24 20123 2060 rxvt --enable-everything
		71	1035683 49680 66648 29096 3680 urxvt --enable-everything
		72
		73	The very large size of the text section is explained by the east-asian
		74	encoding tables, which, if unused, take up disk space but nothing else
		75	and can be compiled out unless you rely on X11 core fonts that use those
		76	encodings. The BSS size comes from the 64k emergency buffer that my c++
		77	compiler allocates (but of course doesn't use unless you are out of
		78	memory). Also, using an xft font instead of a core font immediately adds a
		79	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
		80	not used.
		81
		82	Of course, due to every character using two or four bytes instead of one,
		83	a large scrollback buffer will ultimately make rxvt-unicode use more
		84	memory.
		85
		86	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
		87	still fares rather well. And compared to some monsters like gnome-terminal
		88	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
		89	43180k in daemons that stay around after exit, plus half a minute of
		90	startup time, including the hundreds of warnings it spits out), it fares
		91	extremely well g.
		92
		93	=item Why C++, isn't that unportable/bloated/uncool?
		94
		95	Is this a question? :) It comes up very often. The simple answer is: I had
		96	to write it, and C++ allowed me to write and maintain it in a fraction
		97	of the time and effort (which is a scarce resource for me). Put even
		98	shorter: It simply wouldn't exist without C++.
		99
		100	My personal stance on this is that C++ is less portable than C, but in
		101	the case of rxvt-unicode this hardly matters, as its portability limits
		102	are defined by things like X11, pseudo terminals, locale support and unix
		103	domain sockets, which are all less portable than C++ itself.
		104
		105	Regarding the bloat, see the above question: It's easy to write programs
		106	in C that use gobs of memory, an certainly possible to write programs in
		107	C++ that don't. C++ also often comes with large libraries, but this is
		108	not necessarily the case with GCC. Here is what rxvt links against on my
		109	system with a minimal config:
		110
		111	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		112	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
		113	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
		114	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		115
		116	And here is rxvt-unicode:
		117
		118	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		119	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		120	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
		121	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
		122	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		123
		124	No large bloated libraries (of course, none were linked in statically),
		125	except maybe libX11 :)
		126
		127	=item Does it support tabs, can I have a tabbed rxvt-unicode?
		128
		129	rxvt-unicode does not directly support tabs. It will work fine with
		130	tabbing functionality of many window managers or similar tabbing programs,
		131	and its embedding-features allow it to be embedded into other programs,
		132	as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
		133	module, which features a tabbed urxvt (murxvt) terminal as an example
		134	embedding application.
		135
9	=item How do I know which rxvt-unicode version I'm using?	136	=item How do I know which rxvt-unicode version I'm using?
10		137
11	The version number is displayed with the usage (-h). Also the escape	138	The version number is displayed with the usage (-h). Also the escape
12	sequence C<ESC[8n> sets the window title to the version number.	139	sequence C<ESC [ 8 n> sets the window title to the version number. When
		140	using the @@RXVT_NAME@@c client, the version displayed is that of the
		141	daemon.
		142
		143	=item I am using Debian GNU/Linux and have a problem...
		144
		145	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		146	patches that considerably change the behaviour of rxvt-unicode. Before
		147	reporting a bug to the original rxvt-unicode author please download and
		148	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
		149	and try to reproduce the problem. If you cannot, chances are that the
		150	problems are specific to Debian GNU/Linux, in which case it should be
		151	reported via the Debian Bug Tracking System (use C<reportbug> to report
		152	the bug).
		153
		154	For other problems that also affect the Debian package, you can and
		155	probably should use the Debian BTS, too, because, after all, it's also a
		156	bug in the Debian version and it serves as a reminder for other users that
		157	might encounter the same issue.
		158
		159	=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		160
		161	You should build one binary with the default options. F<configure>
		162	now enables most useful options, and the trend goes to making them
		163	runtime-switchable, too, so there is usually no drawback to enbaling them,
		164	except higher disk and possibly memory usage. The perl interpreter should
		165	be enabled, as important functionality (menus, selection, likely more in
		166	the future) depends on it.
		167
		168	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		169	system-wide (except maybe with C<defaults>). This will result in useful
		170	behaviour. If your distribution aims at low memory, add an empty
		171	C<perl-ext-common> resource to the app-defaults file. This will keep the
		172	perl interpreter disabled until the user enables it.
		173
		174	If you can/want build more binaries, I recommend building a minimal
		175	one with C<--disable-everything> (very useful) and a maximal one with
		176	C<--enable-everything> (less useful, it will be very big due to a lot of
		177	encodings built-in that increase download times and are rarely used).
		178
		179	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		180
		181	Likely not. While I honestly try to make it secure, and am probably not
		182	bad at it, I think it is simply unreasonable to expect all of freetype
		183	+ fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be
		184	secure. Also, rxvt-unicode disables some options when it detects that it
		185	runs setuid or setgid, which is not nice. Besides, with the embedded perl
		186	interpreter the possibility for security problems easily multiplies.
		187
		188	Elevated privileges are only required for utmp and pty operations on some
		189	systems (for example, GNU/Linux doesn't need any extra privileges for
		190	ptys, but some need it for utmp support). It is planned to mvoe this into
		191	a forked handler process, but this is not yet done.
		192
		193	So, while setuid/setgid operation is supported and not a problem on your
		194	typical single-user-no-other-logins unix desktop, always remember that
		195	its an awful lot of code, most of which isn't checked for security issues
		196	regularly.
13		197
14	=item When I log-in to another system it tells me about missing terminfo data?	198	=item When I log-in to another system it tells me about missing terminfo data?
15		199
16	The terminal description used by rxvt-unicode is not as widely available	200	The terminal description used by rxvt-unicode is not as widely available
17	as that for xterm, or even rxvt (for which the same problem often arises).	201	as that for xterm, or even rxvt (for which the same problem often arises).
28	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of	212	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
29	problems arising, which includes wrong keymapping, less and different	213	problems arising, which includes wrong keymapping, less and different
30	colours and some refresh errors in fullscreen applications. It's a nice	214	colours and some refresh errors in fullscreen applications. It's a nice
31	quick-and-dirty workaround for rare cases, though.	215	quick-and-dirty workaround for rare cases, though.
32		216
33	If you always want to do this you can either recompile rxvt-unicode with	217	If you always want to do this (and are fine with the consequences) you
34	the desired TERM value or use a resource to set it:	218	can either recompile rxvt-unicode with the desired TERM value or use a
		219	resource to set it:
35		220
36	URxvt.termName: rxvt	221	URxvt.termName: rxvt
37		222
38	If you don't plan to use B<rxvt> (quite common...) you could also replace	223	If you don't plan to use B<rxvt> (quite common...) you could also replace
39	the rxvt terminfo file with the rxvt-unicode one.	224	the rxvt terminfo file with the rxvt-unicode one.
40		225
		226	=item C<tic> outputs some error when compiling the terminfo entry.
		227
		228	Most likely it's the empty definition for C<enacs=>. Just replace it by
		229	C<enacs=\E[0@> and try again.
		230
		231	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
		232
41	=item I need a termcap file entry.	233	=item I need a termcap file entry.
		234
		235	One reason you might want this is that some distributions or operating
		236	systems still compile some programs using the long-obsoleted termcap
		237	library (Fedora Core's bash is one example) and rely on a termcap entry
		238	for C<rxvt-unicode>.
42		239
43	You could use rxvt's termcap entry with resonable results in many cases.	240	You could use rxvt's termcap entry with resonable results in many cases.
44	You can also create a termcap entry by using terminfo's infocmp program	241	You can also create a termcap entry by using terminfo's infocmp program
45	like this:	242	like this:
46		243
47	infocmp -C rxvt-unicode	244	infocmp -C rxvt-unicode
48		245
49	OR you could this termcap entry:	246	Or you could use this termcap entry, generated by the command above:
50		247
51	rxvt-unicode\|rxvt-unicode terminal (X Window System):\	248	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
52	:am:bw:eo:km:mi:ms:xn:xo:\	249	:am:bw:eo:km:mi:ms:xn:xo:\
53	:co#80:it#8:li#24:\	250	:co#80:it#8:li#24:lm#0:\
54	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	251	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
55	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\	252	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
56	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\	253	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
57	:as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\	254	:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
58	:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\	255	:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
59	:ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\	256	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
		257	:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
60	:im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\	258	:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
61	:k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\	259	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
62	:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\	260	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
63	:kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\	261	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
64	:ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\	262	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
65	:ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\	263	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
66	:nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\	264	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
67	:st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\	265	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
68	:up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	266	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
69	:vs=\E[?25h:	267	:vs=\E[?25h:
70		268
71	=item Why does C<ls> no longer have coloured output?	269	=item Why does C<ls> no longer have coloured output?
72		270
73	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	271	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
…		…
96	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	294	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
97	file, so you will need to install it on your own (See the question B<When	295	file, so you will need to install it on your own (See the question B<When
98	I log-in to another system it tells me about missing terminfo data?> on	296	I log-in to another system it tells me about missing terminfo data?> on
99	how to do this).	297	how to do this).
100		298
		299	=item My numerical keypad acts weird and generates differing output?
		300
		301	Some Debian GNUL/Linux users seem to have this problem, although no
		302	specific details were reported so far. It is possible that this is caused
		303	by the wrong C<TERM> setting, although the details of wether and how
		304	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		305	keymap. See the answer to the previous question, and please report if that
		306	helped.
		307
101	=item Rxvt-unicode does not seem to understand the selected encoding?	308	=item Rxvt-unicode does not seem to understand the selected encoding?
102		309
103	=item Unicode does not seem to work?	310	=item Unicode does not seem to work?
104		311
105	If you encounter strange problems like typing an accented character but	312	If you encounter strange problems like typing an accented character but
…		…
107	subtly garbled, then you should check your locale settings.	314	subtly garbled, then you should check your locale settings.
108		315
109	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	316	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
110	programs. Often rxvt-unicode is started in the C<C> locale, while the	317	programs. Often rxvt-unicode is started in the C<C> locale, while the
111	login script running within the rxvt-unicode window changes the locale to	318	login script running within the rxvt-unicode window changes the locale to
112	sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work.	319	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
113		320
114	The best thing is to fix your startup environment, as you will likely run	321	The best thing is to fix your startup environment, as you will likely run
115	into other problems. If nothing works you can try this in your .profile.	322	into other problems. If nothing works you can try this in your .profile.
116		323
117	printf '\e]701;%s\007' "$LC_CTYPE"	324	printf '\e]701;%s\007' "$LC_CTYPE"
118		325
119	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	326	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
120	supported on your systems. Some systems have a C<locale> command which	327	supported on your systems. Some systems have a C<locale> command which
121	displays this. If it displays sth. like:	328	displays this (also, C<perl -e0> can be used to check locale settings, as
		329	it will complain loudly if it cannot set the locale). If it displays something
		330	like:
122		331
123	locale: Cannot set LC_CTYPE to default locale: ...	332	locale: Cannot set LC_CTYPE to default locale: ...
124		333
125	Then the locale you specified is not supported on your system.	334	Then the locale you specified is not supported on your system.
126		335
…		…
137	your system/os) have specified does not cover all the characters you want	346	your system/os) have specified does not cover all the characters you want
138	to display.	347	to display.
139		348
140	B<rxvt-unicode> makes a best-effort try at finding a replacement	349	B<rxvt-unicode> makes a best-effort try at finding a replacement
141	font. Often the result is fine, but sometimes the chosen font looks	350	font. Often the result is fine, but sometimes the chosen font looks
142	bad. Many fonts have totally strange characters that don't resemble the	351	bad/ugly/wrong. Some fonts have totally strange characters that don't
143	correct glyph at all, and rxvt-unicode lacks the artificial intelligence	352	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
144	to detect that a specific glyph is wrong: it has to believe the font that	353	intelligence to detect that a specific glyph is wrong: it has to believe
145	the characters it contains indeed look correct.	354	the font that the characters it claims to contain indeed look correct.
146		355
147	In that case, select a font of your taste and add it to the font list,	356	In that case, select a font of your taste and add it to the font list,
148	e.g.:	357	e.g.:
149		358
150	@@RXVT_NAME@@ -fn basefont,font2,font3...	359	@@RXVT_NAME@@ -fn basefont,font2,font3...
…		…
152	When rxvt-unicode sees a character, it will first look at the base	361	When rxvt-unicode sees a character, it will first look at the base
153	font. If the base font does not contain the character, it will go to the	362	font. If the base font does not contain the character, it will go to the
154	next font, and so on. Specifying your own fonts will also speed up this	363	next font, and so on. Specifying your own fonts will also speed up this
155	search and use less resources within rxvt-unicode and the X-server.	364	search and use less resources within rxvt-unicode and the X-server.
156		365
157	The only limitation is that all the fonts must not be larger than the base	366	The only limitation is that none of the fonts may be larger than the base
158	font, as the base font defines the principal cell size, which must be the	367	font, as the base font defines the terminal character cell size, which
159	same due to the way terminals work.	368	must be the same due to the way terminals work.
160		369
161	=item Why do some chinese characters look so different than others?	370	=item Why do some chinese characters look so different than others?
162		371
163	This is because there is a difference between script and language --	372	This is because there is a difference between script and language --
164	rxvt-unicode does not know which language the text that is output	373	rxvt-unicode does not know which language the text that is output is,
165	is, as it only knows the unicode character codes. If rxvt-unicode	374	as it only knows the unicode character codes. If rxvt-unicode first
166	first sees a japanese character, it might choose a japanese font for	375	sees a japanese/chinese character, it might choose a japanese font for
167	it. Subsequent japanese characters will take that font. Now, many chinese	376	display. Subsequent japanese characters will use that font. Now, many
168	characters aren't represented in japanese fonts, so when the first	377	chinese characters aren't represented in japanese fonts, so when the first
169	non-japanese character comes up, rxvt-unicode will look for a chinese font	378	non-japanese character comes up, rxvt-unicode will look for a chinese font
170	-- unfortunately at this point, it will still use the japanese font for	379	-- unfortunately at this point, it will still use the japanese font for
171	japanese characters that are also chinese.	380	chinese characters that are also in the japanese font.
172		381
173	The workaround is easy: just tag a chinese font at the end of your font	382	The workaround is easy: just tag a chinese font at the end of your font
174	list (see the previous question). The key is to view the font list as	383	list (see the previous question). The key is to view the font list as
175	a preference list: If you expect more japanese, list a japanese font	384	a preference list: If you expect more japanese, list a japanese font
176	first. If you expect more chinese, put a chinese font first.	385	first. If you expect more chinese, put a chinese font first.
177		386
178	In the future it might be possible to switch preferences at runtime (the	387	In the future it might be possible to switch language preferences at
179	internal data structure has no problem with using different fonts for	388	runtime (the internal data structure has no problem with using different
180	the same character at the same time, but no interface for this has been	389	fonts for the same character at the same time, but no interface for this
181	designed yet).	390	has been designed yet).
		391
		392	Until then, you might get away with switching fonts at runtime (see L<Can
		393	I switch the fonts at runtime?> later in this document).
182		394
183	=item Why does rxvt-unicode sometimes leave pixel droppings?	395	=item Why does rxvt-unicode sometimes leave pixel droppings?
184		396
185	Most fonts were not designed for terminal use, which means that character	397	Most fonts were not designed for terminal use, which means that character
186	size varies a lot. A font that is otherwise fine for terminal use might	398	size varies a lot. A font that is otherwise fine for terminal use might
…		…
199	the C<-lsp> option to give the font more height. If that doesn't work, you	411	the C<-lsp> option to give the font more height. If that doesn't work, you
200	might be forced to use a different font.	412	might be forced to use a different font.
201		413
202	All of this is not a problem when using X11 core fonts, as their bounding	414	All of this is not a problem when using X11 core fonts, as their bounding
203	box data is correct.	415	box data is correct.
		416
		417	=item On Solaris 9, many line-drawing characters are too wide.
		418
		419	Seems to be a known bug, read
		420	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
		421	following ugly workaround to get non-double-wide-characters working:
		422
		423	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
204		424
205	=item My Compose (Multi_key) key is no longer working.	425	=item My Compose (Multi_key) key is no longer working.
206		426
207	The most common causes for this are that either your locale is not set	427	The most common causes for this are that either your locale is not set
208	correctly, or you specified a B<preeditStyle> that is not supported by	428	correctly, or you specified a B<preeditStyle> that is not supported by
…		…
222	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape	442	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
223	character and so on.	443	character and so on.
224		444
225	=item How can I keep rxvt-unicode from using reverse video so much?	445	=item How can I keep rxvt-unicode from using reverse video so much?
226		446
227	First of all, make sure you are running with the right terminfo	447	First of all, make sure you are running with the right terminal settings
228	(C<urxvt>), which will get rid of most of these effects. Then make sure	448	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
229	you have specified colours for italic and bold, as otherwise rxvt-unicode	449	make sure you have specified colours for italic and bold, as otherwise
230	might use reverse video to simulate the effect:	450	rxvt-unicode might use reverse video to simulate the effect:
231		451
232	URxvt*colorBD: white	452	URxvt.colorBD: white
233	URxvt*colorIT: green	453	URxvt.colorIT: green
234		454
235	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?	455	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
236		456
237	For some unexplainable reason, some programs (i.e. irssi) assume a very	457	For some unexplainable reason, some rare programs assume a very weird
238	weird colour palette when confronted with a terminal with more than the	458	colour palette when confronted with a terminal with more than the standard
239	standard 8 colours (rxvt-unicode supports 88). The right fix is, of	459	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
240	course, to fix these programs not to assume non-ISO colours without very	460	these programs not to assume non-ISO colours without very good reasons.
241	good reasons.
242		461
243	In the meantime, you can either edit your C<urxvt> terminfo definition to	462	In the meantime, you can either edit your C<rxvt-unicode> terminfo
244	only claim 8 colour support or use C<TERM=rxvt>, which will fix colours	463	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
245	but keep you from using other rxvt-unicode features.	464	fix colours but keep you from using other rxvt-unicode features.
246		465
247	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	466	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
248		467
249	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	468	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
250	in your compile environment, or an implementation that implements it,	469	in your compile environment, or an implementation that implements it,
251	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	470	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
252	B<wchar_t> is represented as unicode.	471	B<wchar_t> is represented as unicode.
253		472
254	As you might have guessed, FreeBSD does neither define this symobl nor	473	As you might have guessed, FreeBSD does neither define this symobl nor
255	does it support it. Instead, it uses it's own internal representation of	474	does it support it. Instead, it uses it's own internal representation of
256	B<wchar_t>. This is, of course, completely legal.	475	B<wchar_t>. This is, of course, completely fine with respect to standards.
257		476
		477	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
		478	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
		479
258	However, C<__STDC_ISO_10646__> is the only sane way to support	480	C<__STDC_ISO_10646__> is the only sane way to support multi-language
259	multi-language apps in an OS, as using a locale-dependent (and	481	apps in an OS, as using a locale-dependent (and non-standardized)
260	non-standardized) representation of B<wchar_t> makes it impossible to	482	representation of B<wchar_t> makes it impossible to convert between
261	convert between B<wchar_t> (as used by X11 and your applications) and any	483	B<wchar_t> (as used by X11 and your applications) and any other encoding
262	other encoding without implementing OS-specific-wrappers for each and	484	without implementing OS-specific-wrappers for each and every locale. There
263	every locale. There simply are no APIs to convert B<wchar_t> into anything	485	simply are no APIs to convert B<wchar_t> into anything except the current
264	except the current locale encoding.	486	locale encoding.
265		487
266	Some applications (such as the formidable B<mlterm>) work around this	488	Some applications (such as the formidable B<mlterm>) work around this
267	by carrying their own replacement functions for character set handling	489	by carrying their own replacement functions for character set handling
268	with them, and either implementing OS-dependent hacks or doing multiple	490	with them, and either implementing OS-dependent hacks or doing multiple
269	conversions (which is slow and unreliable in case the OS implements	491	conversions (which is slow and unreliable in case the OS implements
270	encodings slightly different than the terminal emulator).	492	encodings slightly different than the terminal emulator).
271		493
272	The rxvt-unicode author insists that the right way to fix this is in the	494	The rxvt-unicode author insists that the right way to fix this is in the
273	system libraries once and for all, instead of forcing every app to carry	495	system libraries once and for all, instead of forcing every app to carry
274	complete replacements.	496	complete replacements for them :)
		497
		498	=item I use Solaris 9 and it doesn't compile/work/etc.
		499
		500	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
		501	problems with C<wcwidth> and a compile problem.
		502
		503	=item How can I use rxvt-unicode under cygwin?
		504
		505	rxvt-unicode should compile and run out of the box on cygwin, using
		506	the X11 libraries that come with cygwin. libW11 emulation is no
		507	longer supported (and makes no sense, either, as it only supported a
		508	single font). I recommend starting the X-server in C<-multiwindow> or
		509	C<-rootless> mode instead, which will result in similar look&feel as the
		510	old libW11 emulation.
		511
		512	At the time of this writing, cygwin didn't seem to support any multi-byte
		513	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		514	to 8-bit encodings.
275		515
276	=item How does rxvt-unicode determine the encoding to use?	516	=item How does rxvt-unicode determine the encoding to use?
277		517
278	=item Is there an option to switch encodings?	518	=item Is there an option to switch encodings?
279		519
…		…
281	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about	521	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
282	UTF-8 or any other encodings with respect to terminal I/O.	522	UTF-8 or any other encodings with respect to terminal I/O.
283		523
284	The reasons is that there exists a perfectly fine mechanism for selecting	524	The reasons is that there exists a perfectly fine mechanism for selecting
285	the encoding, doing I/O and (most important) communicating this to all	525	the encoding, doing I/O and (most important) communicating this to all
286	applications so everybody agrees on character properties such as width and	526	applications so everybody agrees on character properties such as width
287	code number. This mechanism is the I<locale>.	527	and code number. This mechanism is the I<locale>. Applications not using
		528	that info will have problems (for example, C<xterm> gets the width of
		529	characters wrong as it uses it's own, locale-independent table under all
		530	locales).
288		531
289	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All	532	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
290	programs doing the same (that is, most) will automatically agree in the	533	programs doing the same (that is, most) will automatically agree in the
291	interpretation of characters.	534	interpretation of characters.
292		535
…		…
299	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms	542	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
300	(i.e. C<de> or C<german>) are also common.	543	(i.e. C<de> or C<german>) are also common.
301		544
302	Rxvt-unicode ignores all other locale categories, and except for	545	Rxvt-unicode ignores all other locale categories, and except for
303	the encoding, ignores country or language-specific settings,	546	the encoding, ignores country or language-specific settings,
304	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode.	547	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		548	rxvt-unicode.
305		549
306	If you want to use a specific encoding you have to make sure you start	550	If you want to use a specific encoding you have to make sure you start
307	rxvt-unicode with the correct C<LC_CTYPE> category.	551	rxvt-unicode with the correct C<LC_CTYPE> category.
308		552
309	=item Can I switch locales at runtime?	553	=item Can I switch locales at runtime?
310		554
311	Yes, using an escape sequence. Try sth. like this, which sets	555	Yes, using an escape sequence. Try something like this, which sets
312	rxvt-unicode's idea of C<LC_CTYPE>.	556	rxvt-unicode's idea of C<LC_CTYPE>.
313		557
314	printf '\e]701;%s\007' ja_JP.SJIS	558	printf '\e]701;%s\007' ja_JP.SJIS
315		559
316	See also the previous question.	560	See also the previous answer.
317		561
318	Sometimes this capability is rather handy when you want to work in one	562	Sometimes this capability is rather handy when you want to work in
319	locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For	563	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
320	example, I use this script to start C<xjdic>, which first switches to a	564	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
321	locale supported by xjdic and back later:	565	first switches to a locale supported by xjdic and back later:
322		566
323	printf '\e]701;%s\007' ja_JP.SJIS	567	printf '\e]701;%s\007' ja_JP.SJIS
324	xjdic -js	568	xjdic -js
325	printf '\e]701;%s\007' de_DE.UTF-8	569	printf '\e]701;%s\007' de_DE.UTF-8
326		570
		571	You can also use xterm's C<luit> program, which usually works fine, except
		572	for some locales where character width differs between program- and
		573	rxvt-unicode-locales.
		574
327	=item Can I switch the fonts at runtime?	575	=item Can I switch the fonts at runtime?
328		576
329	Yes, using an escape sequence. Try sth. like this, which has the same	577	Yes, using an escape sequence. Try something like this, which has the same
330	effect as using the C<-fn> switch, and takes effect immediately:	578	effect as using the C<-fn> switch, and takes effect immediately:
331		579
332	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	580	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
333		581
334	This is useful if you e.g. work primarily with japanese (and prefer a	582	This is useful if you e.g. work primarily with japanese (and prefer a
…		…
339		587
340	=item Why do italic characters look as if clipped?	588	=item Why do italic characters look as if clipped?
341		589
342	Many fonts have difficulties with italic characters and hinting. For	590	Many fonts have difficulties with italic characters and hinting. For
343	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans	591	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
344	Mono> completely fails in it's italic face. A workaround is to enable	592	Mono> completely fails in it's italic face. A workaround might be to
345	freetype autohinting, i.e. like this:	593	enable freetype autohinting, i.e. like this:
346		594
347	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	595	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
348	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	596	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
349		597
350	=item My input method wants <some encoding> but I want UTF-8, what can I do?	598	=item My input method wants <some encoding> but I want UTF-8, what can I do?
351		599
352	You can specify separate locales for the input method and the rest of the	600	You can specify separate locales for the input method and the rest of the
353	terminal, using the resource C<imlocale>:	601	terminal, using the resource C<imlocale>:
…		…
357	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still	605	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
358	use your input method. Please note, however, that you will not be able to	606	use your input method. Please note, however, that you will not be able to
359	input characters outside C<EUC-JP> in a normal way then, as your input	607	input characters outside C<EUC-JP> in a normal way then, as your input
360	method limits you.	608	method limits you.
361		609
		610	=item Rxvt-unicode crashes when the X Input Method changes or exits.
		611
		612	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		613	design. Applications can avoid some crashes at the expense of memory
		614	leaks, and Input Methods can avoid some crashes by careful ordering at
		615	exit time. B<kinput2> (and derived input methods) generally succeeds,
		616	while B<SCIM> (or similar input methods) fails. In the end, however,
		617	crashes cannot be completely avoided even if both sides cooperate.
		618
		619	So the only workaround is not to kill your Input Method Servers.
		620
362	=item Rxvt-unicode uses gobs of memory, how can I reduce that?	621	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
363		622
364	Rxvt-unicode tries to obey the rule of not charging you for sth. you	623	Rxvt-unicode tries to obey the rule of not charging you for something you
365	don't use. One thing you should try is to configure out all settings that	624	don't use. One thing you should try is to configure out all settings that
366	you don't need, for example, Xft support is a resource hog by design,	625	you don't need, for example, Xft support is a resource hog by design,
367	when used. Compiling it out ensures that no Xft font will be loaded	626	when used. Compiling it out ensures that no Xft font will be loaded
368	accidentally when rxvt-unicode tries to find a font for your characters.	627	accidentally when rxvt-unicode tries to find a font for your characters.
369		628
…		…
376		635
377	=item Can I speed up Xft rendering somehow?	636	=item Can I speed up Xft rendering somehow?
378		637
379	Yes, the most obvious way to speed it up is to avoid Xft entirely, as	638	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
380	it is simply slow. If you still want Xft fonts you might try to disable	639	it is simply slow. If you still want Xft fonts you might try to disable
381	antialiasing (by appending C<:antialiasing=false>), which saves lots of	640	antialiasing (by appending C<:antialias=false>), which saves lots of
382	memory and also speeds up rendering considerably.	641	memory and also speeds up rendering considerably.
383		642
384	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	643	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
385		644
386	Rxvt-unicode will use whatever you specify as a font. If it needs to	645	Rxvt-unicode will use whatever you specify as a font. If it needs to
…		…
422	resources (or as long-options).	681	resources (or as long-options).
423		682
424	Here are values that are supposed to resemble a VGA screen,	683	Here are values that are supposed to resemble a VGA screen,
425	including the murky brown that passes for low-intensity yellow:	684	including the murky brown that passes for low-intensity yellow:
426		685
427	URxvt*color0: #000000	686	URxvt.color0: #000000
428	URxvt*color1: #A80000	687	URxvt.color1: #A80000
429	URxvt*color2: #00A800	688	URxvt.color2: #00A800
430	URxvt*color3: #A8A800	689	URxvt.color3: #A8A800
431	URxvt*color4: #0000A8	690	URxvt.color4: #0000A8
432	URxvt*color5: #A800A8	691	URxvt.color5: #A800A8
433	URxvt*color6: #00A8A8	692	URxvt.color6: #00A8A8
434	URxvt*color7: #A8A8A8	693	URxvt.color7: #A8A8A8
435		694
436	URxvt*color8: #000054	695	URxvt.color8: #000054
437	URxvt*color9: #FF0054	696	URxvt.color9: #FF0054
438	URxvt*color10: #00FF54	697	URxvt.color10: #00FF54
439	URxvt*color11: #FFFF54	698	URxvt.color11: #FFFF54
440	URxvt*color12: #0000FF	699	URxvt.color12: #0000FF
441	URxvt*color13: #FF00FF	700	URxvt.color13: #FF00FF
442	URxvt*color14: #00FFFF	701	URxvt.color14: #00FFFF
443	URxvt*color15: #FFFFFF	702	URxvt.color15: #FFFFFF
444		703
445	And here is a more complete set of non-standard colors described as	704	And here is a more complete set of non-standard colors described (not by
446	"pretty girly":	705	me) as "pretty girly".
447		706
448	URxvt.cursorColor: #dc74d1	707	URxvt.cursorColor: #dc74d1
449	URxvt.pointerColor: #dc74d1	708	URxvt.pointerColor: #dc74d1
450	URxvt.background: #0e0e0e	709	URxvt.background: #0e0e0e
451	URxvt.foreground: #4ad5e1	710	URxvt.foreground: #4ad5e1
…		…
462	URxvt.color6: #73f7ff	721	URxvt.color6: #73f7ff
463	URxvt.color14: #73f7ff	722	URxvt.color14: #73f7ff
464	URxvt.color7: #e1dddd	723	URxvt.color7: #e1dddd
465	URxvt.color15: #e1dddd	724	URxvt.color15: #e1dddd
466		725
		726	=item How can I start @@RXVT_NAME@@d in a race-free way?
		727
		728	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
		729	display, create the listening socket and then fork.
		730
467	=item What's with the strange Backspace/Delete key behaviour?	731	=item What's with the strange Backspace/Delete key behaviour?
468		732
469	Assuming that the physical Backspace key corresponds to the	733	Assuming that the physical Backspace key corresponds to the
470	BackSpace keysym (not likely for Linux ... see the following	734	BackSpace keysym (not likely for Linux ... see the following
471	question) there are two standard values that can be used for	735	question) there are two standard values that can be used for
…		…
489		753
490	# use Backspace = ^?	754	# use Backspace = ^?
491	$ stty erase ^?	755	$ stty erase ^?
492	$ @@RXVT_NAME@@	756	$ @@RXVT_NAME@@
493		757
494	Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).	758	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
495		759
496	For an existing rxvt-unicode:	760	For an existing rxvt-unicode:
497		761
498	# use Backspace = ^H	762	# use Backspace = ^H
499	$ stty erase ^H	763	$ stty erase ^H
…		…
508	properly reflects that.	772	properly reflects that.
509		773
510	The Delete key is a another casualty of the ill-defined Backspace problem.	774	The Delete key is a another casualty of the ill-defined Backspace problem.
511	To avoid confusion between the Backspace and Delete keys, the Delete	775	To avoid confusion between the Backspace and Delete keys, the Delete
512	key has been assigned an escape sequence to match the vt100 for Execute	776	key has been assigned an escape sequence to match the vt100 for Execute
513	(ESC[3~) and is in the supplied termcap/terminfo.	777	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
514		778
515	Some other Backspace problems:	779	Some other Backspace problems:
516		780
517	some editors use termcap/terminfo,	781	some editors use termcap/terminfo,
518	some editors (vim I'm told) expect Backspace = ^H,	782	some editors (vim I'm told) expect Backspace = ^H,
…		…
524		788
525	There are some compile-time selections available via configure. Unless	789	There are some compile-time selections available via configure. Unless
526	you have run "configure" with the C<--disable-resources> option you can	790	you have run "configure" with the C<--disable-resources> option you can
527	use the `keysym' resource to alter the keystrings associated with keysyms.	791	use the `keysym' resource to alter the keystrings associated with keysyms.
528		792
529	Here's an example for a URxvt session started using `@@RXVT_NAME@@ -name URxvt'	793	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
530		794
531	URxvt.keysym.Home: \033[1~	795	URxvt.keysym.Home: \033[1~
532	URxvt.keysym.End: \033[4~	796	URxvt.keysym.End: \033[4~
533	URxvt.keysym.C-apostrophe: \033<C-'>	797	URxvt.keysym.C-apostrophe: \033<C-'>
534	URxvt.keysym.C-slash: \033<C-/>	798	URxvt.keysym.C-slash: \033<C-/>
…		…
564		828
565	Rather than have rxvt-unicode try to accommodate all the various possible	829	Rather than have rxvt-unicode try to accommodate all the various possible
566	keyboard mappings, it is better to use `xmodmap' to remap the keys as	830	keyboard mappings, it is better to use `xmodmap' to remap the keys as
567	required for your particular machine.	831	required for your particular machine.
568		832
569	=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?	833	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
570	I need this to decide about setting colors etc.	834	I need this to decide about setting colors etc.
571		835
572	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can	836	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
573	check and see if that is set. Note that several programs, JED, slrn,	837	check and see if that is set. Note that several programs, JED, slrn,
574	Midnight Commander automatically check this variable to decide whether or	838	Midnight Commander automatically check this variable to decide whether or
…		…
611	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be	875	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
612	interested in learning about new and exciting problems (but not FAQs :).	876	interested in learning about new and exciting problems (but not FAQs :).
613		877
614	=back	878	=back
615		879
616	=head1 SYNOPSIS	880	=head1 RXVT TECHNICAL REFERENCE
617
618	# set a new font set
619	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
620
621	# change the locale and tell rxvt-unicode about it
622	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
623
624	# set window title
625	printf '\33]2;%s\007' "new window title"
626		881
627	=head1 DESCRIPTION	882	=head1 DESCRIPTION
628		883
629	The rest of this document describes various technical aspects of	884	The rest of this document describes various technical aspects of
630	B<rxvt-unicode>. First the description of supported command sequences,	885	B<rxvt-unicode>. First the description of supported command sequences,
631	followed by menu and pixmap support and last by a description of all	886	followed by menu and pixmap support and last by a description of all
632	features selectable at C<configure> time.	887	features selectable at C<configure> time.
633		888
634	=head1 RXVT TECHNICAL REFERENCE
635
636	=head1 Definitions	889	=head1 Definitions
637		890
638	=over 4	891	=over 4
639		892
640	=item B<< C<c> >>	893	=item B<< C<c> >>
…		…
768	Single Shift Select of G3 Character Set (SS3): affects next character	1021	Single Shift Select of G3 Character Set (SS3): affects next character
769	only I<unimplemented>	1022	only I<unimplemented>
770		1023
771	=item B<< C<ESC Z> >>	1024	=item B<< C<ESC Z> >>
772		1025
773	Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option>	1026	Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option>
774		1027
775	=item B<< C<ESC c> >>	1028	=item B<< C<ESC c> >>
776		1029
777	Full reset (RIS)	1030	Full reset (RIS)
778		1031
…		…
782		1035
783	=item B<< C<ESC o> >>	1036	=item B<< C<ESC o> >>
784		1037
785	Invoke the G3 Character Set (LS3)	1038	Invoke the G3 Character Set (LS3)
786		1039
787	=item B<< C<ESC> ( C> >>	1040	=item B<< C<ESC ( C> >>
788		1041
789	Designate G0 Character Set (ISO 2022), see below for values of C<C>.	1042	Designate G0 Character Set (ISO 2022), see below for values of C<C>.
790		1043
791	=item B<< C<ESC> ) C> >>	1044	=item B<< C<ESC ) C> >>
792		1045
793	Designate G1 Character Set (ISO 2022), see below for values of C<C>.	1046	Designate G1 Character Set (ISO 2022), see below for values of C<C>.
794		1047
795	=item B<< C<ESC * C> >>	1048	=item B<< C<ESC * C> >>
796		1049
…		…
937		1190
938	=item B<< C<ESC [ Ps c> >>	1191	=item B<< C<ESC [ Ps c> >>
939		1192
940	Send Device Attributes (DA)	1193	Send Device Attributes (DA)
941	B<< C<Ps = 0> >> (or omitted): request attributes from terminal	1194	B<< C<Ps = 0> >> (or omitted): request attributes from terminal
942	returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video	1195	returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video
943	Option'')	1196	Option'')
944		1197
945	=item B<< C<ESC [ Ps d> >>	1198	=item B<< C<ESC [ Ps d> >>
946		1199
947	Cursor to Line B<< C<Ps> >> (VPA)	1200	Cursor to Line B<< C<Ps> >> (VPA)
…		…
1077	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels	1330	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
1078	B<< C<Ps = 5> >> Raise window	1331	B<< C<Ps = 5> >> Raise window
1079	B<< C<Ps = 6> >> Lower window	1332	B<< C<Ps = 6> >> Lower window
1080	B<< C<Ps = 7> >> Refresh screen once	1333	B<< C<Ps = 7> >> Refresh screen once
1081	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns	1334	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
1082	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>	1335	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
1083	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)	1336	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
1084	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)	1337	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
1085	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)	1338	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
1086	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>	1339	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
1087	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)	1340	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
…		…
1338		1591
1339	=begin table	1592	=begin table
1340		1593
1341	B<< C<h> >> Scroll to bottom when a key is pressed	1594	B<< C<h> >> Scroll to bottom when a key is pressed
1342	B<< C<l> >> Don't scroll to bottom when a key is pressed	1595	B<< C<l> >> Don't scroll to bottom when a key is pressed
		1596
		1597	=end table
		1598
		1599	=item B<< C<Ps = 1021> >> (B<rxvt>)
		1600
		1601	=begin table
		1602
		1603	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
		1604	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1343		1605
1344	=end table	1606	=end table
1345		1607
1346	=item B<< C<Ps = 1047> >>	1608	=item B<< C<Ps = 1047> >>
1347		1609
…		…
1396	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	1658	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>
1397	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	1659	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>
1398	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	1660	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1399	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1661	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1400	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1662	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1401	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1663	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1402	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1664	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1403	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1665	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
1404	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option>	1666	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1405	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1667	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1406	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>	1668	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1407	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> >>	1669	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> >>
1408	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1670	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1409	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)	1671	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).
1410	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)	1672	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).
1411	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1673	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1412	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>	1674	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
		1675	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		1676	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1413	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1677	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1414	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1678	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1415	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1679	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1416	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1680	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1681	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1682	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1683	B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1417		1684
1418	=end table	1685	=end table
1419		1686
1420	=back	1687	=back
1421		1688
…		…
1473		1740
1474	=item B<< [title:+I<string>] >>	1741	=item B<< [title:+I<string>] >>
1475		1742
1476	set the current menuBar's title to I<string>, which may contain the	1743	set the current menuBar's title to I<string>, which may contain the
1477	following format specifiers:	1744	following format specifiers:
1478	B<%%> : literal B<%> character	1745
1479	B<%n> : rxvt name (as per the B<-name> command-line option)	1746	B<%n> rxvt name (as per the B<-name> command-line option)
1480	B<%v> : rxvt version	1747	B<%v> rxvt version
		1748	B<%%> literal B<%> character
1481		1749
1482	=item B<[done]>	1750	=item B<[done]>
1483		1751
1484	set menuBar access as B<readonly>.	1752	set menuBar access as B<readonly>.
1485	End-of-file tag for B<< [read:+I<file>] >> operations.	1753	End-of-file tag for B<< [read:+I<file>] >> operations.
…		…
1631		1899
1632	As a convenience for the many Emacs-type editors, I<action> may start	1900	As a convenience for the many Emacs-type editors, I<action> may start
1633	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be	1901	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1634	appended if missed from B<M-x> commands.	1902	appended if missed from B<M-x> commands.
1635		1903
1636	As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or	1904	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1637	quick arrow), a B<BEL> (B<^G>) will be appended if needed.	1905	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1638		1906
1639	=over 4	1907	=over 4
1640		1908
1641	=item For example,	1909	=item For example,
…		…
2077	=end table	2345	=end table
2078		2346
2079	=head1 CONFIGURE OPTIONS	2347	=head1 CONFIGURE OPTIONS
2080		2348
2081	General hint: if you get compile errors, then likely your configuration	2349	General hint: if you get compile errors, then likely your configuration
2082	hasn't been tested well. Either try with --enable-everything or use the	2350	hasn't been tested well. Either try with C<--enable-everything> or use
2083	./reconf script as a base for experiments. ./reconf is used by myself,	2351	the F<./reconf> script as a base for experiments. F<./reconf> is used by
2084	so it should generally be a working config. Of course, you should always	2352	myself, so it should generally be a working config. Of course, you should
2085	report when a combination doesn't work, so it can be fixed. Marc Lehmann	2353	always report when a combination doesn't work, so it can be fixed. Marc
2086	<rxvt@schmorp.de>.	2354	Lehmann <rxvt@schmorp.de>.
		2355
		2356	All
2087		2357
2088	=over 4	2358	=over 4
2089		2359
2090	=item --enable-everything	2360	=item --enable-everything
2091		2361
2092	Add support for all non-multichoice options listed in "./configure	2362	Add (or remove) support for all non-multichoice options listed in "./configure
2093	--help". Note that unlike other enable options this is order dependant.	2363	--help".
		2364
2094	You can specify this and then disable options which this enables by	2365	You can specify this and then disable options you do not like by
2095	I<following> this with the appropriate commands.	2366	I<following> this with the appropriate C<--disable-...> arguments,
		2367	or you can start with a minimal configuration by specifying
		2368	C<--disable-everything> and than adding just the C<--enable-...> arguments
		2369	you want.
2096		2370
2097	=item --enable-xft	2371	=item --enable-xft (default: enabled)
2098		2372
2099	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2373	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2100	slower and require lots of memory, but as long as you don't use them, you	2374	slower and require lots of memory, but as long as you don't use them, you
2101	don't pay for them.	2375	don't pay for them.
2102		2376
2103	=item --enable-font-styles	2377	=item --enable-font-styles (default: on)
2104		2378
2105	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2379	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2106	styles. The fonts can be set manually or automatically.	2380	styles. The fonts can be set manually or automatically.
2107		2381
2108	=item --with-codesets=NAME,...	2382	=item --with-codesets=NAME,... (default: all)
2109		2383
2110	Compile in support for additional codeset (encoding) groups (eu, vn are	2384	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2111	always compiled in, which includes most 8-bit character sets). These	2385	are always compiled in, which includes most 8-bit character sets). These
2112	codeset tables are currently only used for driving X11 core fonts, they	2386	codeset tables are used for driving X11 core fonts, they are not required
2113	are not required for Xft fonts. Compiling them in will make your binary	2387	for Xft fonts, although having them compiled in lets rxvt-unicode choose
2114	bigger (together about 700kB), but it doesn't increase memory usage unless	2388	replacement fonts more intelligently. Compiling them in will make your
		2389	binary bigger (all of together cost about 700kB), but it doesn't increase
2115	you use an X11 font requiring one of these encodings.	2390	memory usage unless you use a font requiring one of these encodings.
2116		2391
2117	=begin table	2392	=begin table
2118		2393
2119	all all available codeset groups	2394	all all available codeset groups
2120	zh common chinese encodings	2395	zh common chinese encodings
…		…
2123	jp_ext rarely used but big japanese encodings	2398	jp_ext rarely used but big japanese encodings
2124	kr korean encodings	2399	kr korean encodings
2125		2400
2126	=end table	2401	=end table
2127		2402
2128	=item --enable-xim	2403	=item --enable-xim (default: on)
2129		2404
2130	Add support for XIM (X Input Method) protocol. This allows using	2405	Add support for XIM (X Input Method) protocol. This allows using
2131	alternative input methods (e.g. kinput2) and will also correctly	2406	alternative input methods (e.g. kinput2) and will also correctly
2132	set up the input for people using dead keys or compose keys.	2407	set up the input for people using dead keys or compose keys.
2133		2408
2134	=item --enable-unicode3	2409	=item --enable-unicode3 (default: off)
2135		2410
2136	Enable direct support for displaying unicode codepoints above	2411	Enable direct support for displaying unicode codepoints above
2137	65535 (the basic multilingual page). This increases storage	2412	65535 (the basic multilingual page). This increases storage
2138	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2413	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2139	support these extra characters, but Xft does.	2414	support these extra characters, but Xft does.
…		…
2142	even without this flag, but the number of such characters is	2417	even without this flag, but the number of such characters is
2143	limited to a view thousand (shared with combining characters,	2418	limited to a view thousand (shared with combining characters,
2144	see next switch), and right now rxvt-unicode cannot display them	2419	see next switch), and right now rxvt-unicode cannot display them
2145	(input/output and cut&paste still work, though).	2420	(input/output and cut&paste still work, though).
2146		2421
2147	=item --enable-combining	2422	=item --enable-combining (default: on)
2148		2423
2149	Enable automatic composition of combining characters into	2424	Enable automatic composition of combining characters into
2150	composite characters. This is required for proper viewing of text	2425	composite characters. This is required for proper viewing of text
2151	where accents are encoded as seperate unicode characters. This is	2426	where accents are encoded as seperate unicode characters. This is
2152	done by using precomposited characters when available or creating	2427	done by using precomposited characters when available or creating
2153	new pseudo-characters when no precomposed form exists.	2428	new pseudo-characters when no precomposed form exists.
2154		2429
2155	Without --enable-unicode3, the number of additional precomposed	2430	Without --enable-unicode3, the number of additional precomposed characters
2156	characters is rather limited (2048, if this is full, rxvt will use the	2431	is rather limited (2048, if this is full, rxvt-unicode will use the
2157	private use area, extending the number of combinations to 8448). With	2432	private use area, extending the number of combinations to 8448). With
2158	--enable-unicode3, no practical limit exists. This will also enable	2433	--enable-unicode3, no practical limit exists.
2159	storage of characters >65535.	2434
		2435	This option will also enable storage (but not display) of characters
		2436	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2160		2437
2161	The combining table also contains entries for arabic presentation forms,	2438	The combining table also contains entries for arabic presentation forms,
2162	but these are not currently used. Bug me if you want these to be used.	2439	but these are not currently used. Bug me if you want these to be used (and
		2440	tell me how these are to be used...).
2163		2441
2164	=item --enable-fallback(=CLASS)	2442	=item --enable-fallback(=CLASS) (default: Rxvt)
2165		2443
2166	When reading resource settings, also read settings for class CLASS	2444	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.
2167	(default: Rxvt). To disable resource fallback use --disable-fallback.
2168		2445
2169	=item --with-res-name=NAME	2446	=item --with-res-name=NAME (default: urxvt)
2170		2447
2171	Use the given name (default: urxvt) as default application name when	2448	Use the given name as default application name when
2172	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2449	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2173		2450
2174	=item --with-res-class=CLASS	2451	=item --with-res-class=CLASS /default: URxvt)
2175		2452
2176	Use the given class (default: URxvt) as default application class	2453	Use the given class as default application class
2177	when reading resources. Specify --with-res-class=Rxvt to replace	2454	when reading resources. Specify --with-res-class=Rxvt to replace
2178	rxvt.	2455	rxvt.
2179		2456
2180	=item --enable-utmp	2457	=item --enable-utmp (default: on)
2181		2458
2182	Write user and tty to utmp file (used by programs like F<w>) at	2459	Write user and tty to utmp file (used by programs like F<w>) at
2183	start of rxvt execution and delete information when rxvt exits.	2460	start of rxvt execution and delete information when rxvt exits.
2184		2461
2185	=item --enable-wtmp	2462	=item --enable-wtmp (default: on)
2186		2463
2187	Write user and tty to wtmp file (used by programs like F<last>) at	2464	Write user and tty to wtmp file (used by programs like F<last>) at
2188	start of rxvt execution and write logout when rxvt exits. This	2465	start of rxvt execution and write logout when rxvt exits. This
2189	option requires --enable-utmp to also be specified.	2466	option requires --enable-utmp to also be specified.
2190		2467
2191	=item --enable-lastlog	2468	=item --enable-lastlog (default: on)
2192		2469
2193	Write user and tty to lastlog file (used by programs like	2470	Write user and tty to lastlog file (used by programs like
2194	F<lastlogin>) at start of rxvt execution. This option requires	2471	F<lastlogin>) at start of rxvt execution. This option requires
2195	--enable-utmp to also be specified.	2472	--enable-utmp to also be specified.
2196		2473
2197	=item --enable-xpm-background	2474	=item --enable-xpm-background (default: on)
2198		2475
2199	Add support for XPM background pixmaps.	2476	Add support for XPM background pixmaps.
2200		2477
2201	=item --enable-transparency	2478	=item --enable-transparency (default: on)
2202		2479
2203	Add support for inheriting parent backgrounds thus giving a fake	2480	Add support for inheriting parent backgrounds thus giving a fake
2204	transparency to the term.	2481	transparency to the term.
2205		2482
2206	=item --enable-fading	2483	=item --enable-fading (default: on)
2207		2484
2208	Add support for fading the text when focus is lost.	2485	Add support for fading the text when focus is lost (requires C<--enable-transparency>).
2209		2486
2210	=item --enable-tinting	2487	=item --enable-tinting (default: on)
2211		2488
2212	Add support for tinting of transparent backgrounds.	2489	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2213		2490
2214	=item --enable-menubar	2491	=item --enable-menubar (default: off) [DEPRECATED]
2215		2492
2216	Add support for our menu bar system (this interacts badly with	2493	Add support for our menu bar system (this interacts badly with dynamic
2217	dynamic locale switching currently).	2494	locale switching currently). This option is DEPRECATED and will be removed
		2495	in the future.
2218		2496
2219	=item --enable-rxvt-scroll	2497	=item --enable-rxvt-scroll (default: on)
2220		2498
2221	Add support for the original rxvt scrollbar.	2499	Add support for the original rxvt scrollbar.
2222		2500
2223	=item --enable-next-scroll	2501	=item --enable-next-scroll (default: on)
2224		2502
2225	Add support for a NeXT-like scrollbar.	2503	Add support for a NeXT-like scrollbar.
2226		2504
2227	=item --enable-xterm-scroll	2505	=item --enable-xterm-scroll (default: on)
2228		2506
2229	Add support for an Xterm-like scrollbar.	2507	Add support for an Xterm-like scrollbar.
2230		2508
2231	=item --enable-plain-scroll	2509	=item --enable-plain-scroll (default: on)
2232		2510
2233	Add support for a very unobtrusive, plain-looking scrollbar that	2511	Add support for a very unobtrusive, plain-looking scrollbar that
2234	is the favourite of the rxvt-unicode author, having used it for	2512	is the favourite of the rxvt-unicode author, having used it for
2235	many years.	2513	many years.
2236		2514
2237	=item --enable-half-shadow	2515	=item --enable-half-shadow (default: off)
2238		2516
2239	Make shadows on the scrollbar only half the normal width & height.	2517	Make shadows on the scrollbar only half the normal width & height.
2240	only applicable to rxvt scrollbars.	2518	only applicable to rxvt scrollbars.
2241		2519
2242	=item --enable-ttygid	2520	=item --enable-ttygid (default: off)
2243		2521
2244	Change tty device setting to group "tty" - only use this if	2522	Change tty device setting to group "tty" - only use this if
2245	your system uses this type of security.	2523	your system uses this type of security.
2246		2524
2247	=item --disable-backspace-key	2525	=item --disable-backspace-key
2248		2526
2249	Disable any handling of the backspace key by us - let the X server	2527	Removes any handling of the backspace key by us - let the X server do it.
		2528
		2529	=item --disable-delete-key
		2530
		2531	Removes any handling of the delete key by us - let the X server
2250	do it.	2532	do it.
2251		2533
2252	=item --disable-delete-key
2253
2254	Disable any handling of the delete key by us - let the X server
2255	do it.
2256
2257	=item --disable-resources	2534	=item --disable-resources
2258		2535
2259	Remove all resources checking.	2536	Removes any support for resource checking.
2260		2537
2261	=item --enable-xgetdefault	2538	=item --enable-strings (default: off)
2262
2263	Make resources checking via XGetDefault() instead of our small
2264	version which only checks ~/.Xdefaults, or if that doesn't exist
2265	then ~/.Xresources.
2266
2267	=item --enable-strings
2268		2539
2269	Add support for our possibly faster memset() function and other	2540	Add support for our possibly faster memset() function and other
2270	various routines, overriding your system's versions which may	2541	various routines, overriding your system's versions which may
2271	have been hand-crafted in assembly or may require extra libraries	2542	have been hand-crafted in assembly or may require extra libraries
2272	to link in. (this breaks ANSI-C rules and has problems on many	2543	to link in. (this breaks ANSI-C rules and has problems on many
2273	GNU/Linux systems).	2544	GNU/Linux systems).
2274		2545
2275	=item --disable-swapscreen	2546	=item --disable-swapscreen
2276		2547
2277	Remove support for swap screen.	2548	Remove support for secondary/swap screen.
2278		2549
2279	=item --enable-frills	2550	=item --enable-frills (default: on)
2280		2551
2281	Add support for many small features that are not essential but nice to	2552	Add support for many small features that are not essential but nice to
2282	have. Normally you want this, but for very small binaries you may want to	2553	have. Normally you want this, but for very small binaries you may want to
2283	disable this.	2554	disable this.
2284		2555
2285	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2556	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2286	in combination with other switches) is:	2557	in combination with other switches) is:
2287		2558
2288	MWM-hints	2559	MWM-hints
		2560	EWMH-hints (pid, utf8 names) and protocols (ping)
2289	seperate underline colour	2561	seperate underline colour (-underlineColor)
2290	settable border widths and borderless switch	2562	settable border widths and borderless switch (-w, -b, -bl)
2291	settable extra linespacing	2563	settable extra linespacing /-lsp)
2292	extra window properties (e.g. UTF-8 window names and PID)
2293	iso-14755-2 and -3, and visual feedback	2564	iso-14755-2 and -3, and visual feedback
2294	backindex and forwardindex escape sequence	2565	backindex and forwardindex escape sequence
2295	window op and locale change escape sequences	2566	window op and some xterm/OSC escape sequences
2296	tripleclickwords	2567	tripleclickwords (-tcw)
2297	settable insecure mode	2568	settable insecure mode (-insecure)
		2569	keysym remapping support
		2570	cursor blinking and underline cursor (-cb, -uc)
		2571	XEmbed support (-embed)
		2572	user-pty (-pty-fd)
		2573	hold on exit (-hold)
		2574	skip builtin block graphics (-sbg)
		2575	sgr modes 90..97 and 100..107
2298		2576
2299	=item --enable-iso14755	2577	=item --enable-iso14755 (default: on)
2300		2578
2301	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2579	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2302	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2580	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
2303	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with	2581	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2304	this switch.	2582	this switch.
2305		2583
2306	=item --enable-keepscrolling	2584	=item --enable-keepscrolling (default: on)
2307		2585
2308	Add support for continual scrolling of the display when you hold	2586	Add support for continual scrolling of the display when you hold
2309	the mouse button down on a scrollbar arrow.	2587	the mouse button down on a scrollbar arrow.
2310		2588
2311	=item --enable-mousewheel	2589	=item --enable-mousewheel (default: on)
2312		2590
2313	Add support for scrolling via mouse wheel or buttons 4 & 5.	2591	Add support for scrolling via mouse wheel or buttons 4 & 5.
2314		2592
2315	=item --enable-slipwheeling	2593	=item --enable-slipwheeling (default: on)
2316		2594
2317	Add support for continual scrolling (using the mouse wheel as an	2595	Add support for continual scrolling (using the mouse wheel as an
2318	accelerator) while the control key is held down. This option	2596	accelerator) while the control key is held down. This option
2319	requires --enable-mousewheel to also be specified.	2597	requires --enable-mousewheel to also be specified.
2320		2598
2321	=item --disable-new-selection	2599	=item --disable-new-selection
2322		2600
2323	Remove support for mouse selection style like that of xterm.	2601	Remove support for mouse selection style like that of xterm.
2324		2602
2325	=item --enable-dmalloc	2603	=item --enable-dmalloc (default: off)
2326		2604
2327	Use Gray Watson's malloc - which is good for debugging See	2605	Use Gray Watson's malloc - which is good for debugging See
2328	http://www.letters.com/dmalloc/ for details If you use either this or the	2606	http://www.letters.com/dmalloc/ for details If you use either this or the
2329	next option, you may need to edit src/Makefile after compiling to point	2607	next option, you may need to edit src/Makefile after compiling to point
2330	DINCLUDE and DLIB to the right places.	2608	DINCLUDE and DLIB to the right places.
2331		2609
2332	You can only use either this option and the following (should	2610	You can only use either this option and the following (should
2333	you use either) .	2611	you use either) .
2334		2612
2335	=item --enable-dlmalloc	2613	=item --enable-dlmalloc (default: off)
2336		2614
2337	Use Doug Lea's malloc - which is good for a production version	2615	Use Doug Lea's malloc - which is good for a production version
2338	See L<http://g.oswego.edu/dl/html/malloc.html> for details.	2616	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2339		2617
2340	=item --enable-smart-resize	2618	=item --enable-smart-resize (default: on)
2341		2619
2342	Add smart growth/shrink behaviour when changing font size via from hot	2620	Add smart growth/shrink behaviour when changing font size via hot
2343	keys. This should keep in a fixed position the rxvt corner which is	2621	keys. This should keep the window corner which is closest to a corner of
2344	closest to a corner of the screen.	2622	the screen in a fixed position.
2345		2623
2346	=item --enable-cursor-blink
2347
2348	Add support for a blinking cursor.
2349
2350	=item --enable-pointer-blank	2624	=item --enable-pointer-blank (default: on)
2351		2625
2352	Add support to have the pointer disappear when typing or inactive.	2626	Add support to have the pointer disappear when typing or inactive.
2353		2627
2354	=item --with-name=NAME	2628	=item --enable-perl (default: off)
2355		2629
		2630	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
		2631	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
		2632	in F<src/perl-ext/> for the extensions that are installed by default. The
		2633	perl interpreter that is used can be specified via the C<PERL> environment
		2634	variable when running configure.
		2635
		2636	=item --with-name=NAME (default: urxvt)
		2637
2356	Set the basename for the installed binaries (default: C<urxvt>, resulting	2638	Set the basename for the installed binaries, resulting
2357	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2639	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
2358	C<rxvt>.	2640	C<rxvt>.
2359		2641
2360	=item --with-term=NAME	2642	=item --with-term=NAME (default: rxvt-unicode)
2361		2643
2362	Change the environmental variable for the terminal to NAME (default	2644	Change the environmental variable for the terminal to NAME.
2363	C<rxvt-unicode>)
2364		2645
2365	=item --with-terminfo=PATH	2646	=item --with-terminfo=PATH
2366		2647
2367	Change the environmental variable for the path to the terminfo tree to	2648	Change the environmental variable for the path to the terminfo tree to
2368	PATH.	2649	PATH.

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.34 by root, Thu Feb 3 10:24:10 2005 UTC vs. Revision 1.78 by root, Thu Jan 12 05:37:34 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.34 by root, Thu Feb 3 10:24:10 2005 UTC vs.
Revision 1.78 by root, Thu Jan 12 05:37:34 2006 UTC