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