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