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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.29 by root, Wed Dec 29 19:17:18 2004 UTC vs.
Revision 1.64 by root, Sat Dec 24 12:55:17 2005 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 Isn't rxvt supposed to be small? Don't all those features bloat?
		30
		31	I often get asked about this, and I think, no, they didn't cause extra
		32	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
		33	that the urxvt binary is larger (due to some encoding tables always being
		34	compiled in), but it actually uses less memory (RSS) after startup. Even
		35	with C<--disable-everything>, this comparison is a bit unfair, as many
		36	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		37	already in use in this mode.
		38
		39	text data bss drs rss filename
		40	98398 1664 24 15695 1824 rxvt --disable-everything
		41	188985 9048 66616 18222 1788 urxvt --disable-everything
		42
		43	When you C<--enable-everything> (which _is_ unfair, as this involves xft
		44	and full locale/XIM support which are quite bloaty inside libX11 and my
		45	libc), the two diverge, but not unreasnobaly so.
		46
		47	text data bss drs rss filename
		48	163431 2152 24 20123 2060 rxvt --enable-everything
		49	1035683 49680 66648 29096 3680 urxvt --enable-everything
		50
		51	The very large size of the text section is explained by the east-asian
		52	encoding tables, which, if unused, take up disk space but nothing else
		53	and can be compiled out unless you rely on X11 core fonts that use those
		54	encodings. The BSS size comes from the 64k emergency buffer that my c++
		55	compiler allocates (but of course doesn't use unless you are out of
		56	memory). Also, using an xft font instead of a core font immediately adds a
		57	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
		58	not used.
		59
		60	Of course, due to every character using two or four bytes instead of one,
		61	a large scrollback buffer will ultimately make rxvt-unicode use more
		62	memory.
		63
		64	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
		65	still fares rather well. And compared to some monsters like gnome-terminal
		66	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
		67	43180k in daemons that stay around after exit, plus half aminute of
		68	startup time, including the hundreds of warnings it spits out), it fares
		69	extremely well g.
		70
		71	=item Why C++, isn't that unportable/bloated/uncool?
		72
		73	Is this a question? :) It comes up very often. The simple answer is: I had
		74	to write it, and C++ allowed me to write and maintain it in a fraction
		75	of the time and effort (which is a scarce resource for me). Put even
		76	shorter: It simply wouldn't exist without C++.
		77
		78	My personal stance on this is that C++ is less portable than C, but in
		79	the case of rxvt-unicode this hardly matters, as its portability limits
		80	are defined by things like X11, pseudo terminals, locale support and unix
		81	domain sockets, which are all less portable than C++ itself.
		82
		83	Regarding the bloat, see the above question: It's easy to write programs
		84	in C that use gobs of memory, an certainly possible to write programs in
		85	C++ that don't. C++ also often comes with large libraries, but this is
		86	not necessarily the case with GCC. Here is what rxvt links against on my
		87	system with a minimal config:
		88
		89	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		90	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
		91	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
		92	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		93
		94	And here is rxvt-unicode:
		95
		96	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		97	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		98	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
		99	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
		100	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		101
		102	No large bloated libraries (of course, none were linked in statically),
		103	except maybe libX11 :)
		104
		105	=item Does it support tabs, can I have a tabbed rxvt-unicode?
		106
		107	rxvt-unicode does not directly support tabs. It will work fine with
		108	tabbing functionality of many window managers or similar tabbing programs,
		109	and its embedding-features allow it to be embedded into other programs,
		110	as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
		111	module, which features a tabbed urxvt (murxvt) terminal as an example
		112	embedding application.
		113
9	=item How do I know which rxvt-unicode version I'm using?	114	=item How do I know which rxvt-unicode version I'm using?
10		115
11	The version number is displayed with the usage (-h). Also the escape	116	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.	117	sequence C<ESC [ 8 n> sets the window title to the version number. When
		118	using the @@RXVT_NAME@@c client, the version displayed is that of the
		119	daemon.
		120
		121	=item I am using Debian GNU/Linux and have a problem...
		122
		123	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		124	patches that considerably change the behaviour of rxvt-unicode. Before
		125	reporting a bug to the original rxvt-unicode author please download and
		126	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
		127	and try to reproduce the problem. If you cannot, chances are that the
		128	problems are specific to Debian GNU/Linux, in which case it should be
		129	reported via the Debian Bug Tracking System (use C<reportbug> to report
		130	the bug).
		131
		132	For other problems that also affect the Debian package, you can and
		133	probably should use the Debian BTS, too, because, after all, it's also a
		134	bug in the Debian version and it serves as a reminder for other users that
		135	might encounter the same issue.
13		136
14	=item When I log-in to another system it tells me about missing terminfo data?	137	=item When I log-in to another system it tells me about missing terminfo data?
15		138
16	The terminal description used by rxvt-unicode is not as widely available	139	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).	140	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	151	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	152	problems arising, which includes wrong keymapping, less and different
30	colours and some refresh errors in fullscreen applications. It's a nice	153	colours and some refresh errors in fullscreen applications. It's a nice
31	quick-and-dirty workaround for rare cases, though.	154	quick-and-dirty workaround for rare cases, though.
32		155
33	If you always want to do this you can either recompile rxvt-unicode with	156	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:	157	can either recompile rxvt-unicode with the desired TERM value or use a
		158	resource to set it:
35		159
36	URxvt.termName: rxvt	160	URxvt.termName: rxvt
37		161
38	If you don't plan to use B<rxvt> (quite common...) you could also replace	162	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.	163	the rxvt terminfo file with the rxvt-unicode one.
40		164
		165	=item C<tic> outputs some error when compiling the terminfo entry.
		166
		167	Most likely it's the empty definition for C<enacs=>. Just replace it by
		168	C<enacs=\E[0@> and try again.
		169
		170	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
		171
41	=item I need a termcap file entry.	172	=item I need a termcap file entry.
		173
		174	One reason you might want this is that some distributions or operating
		175	systems still compile some programs using the long-obsoleted termcap
		176	library (Fedora Core's bash is one example) and rely on a termcap entry
		177	for C<rxvt-unicode>.
42		178
43	You could use rxvt's termcap entry with resonable results in many cases.	179	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	180	You can also create a termcap entry by using terminfo's infocmp program
45	like this:	181	like this:
46		182
47	infocmp -C rxvt-unicode	183	infocmp -C rxvt-unicode
48		184
49	OR you could this termcap entry:	185	Or you could use this termcap entry, generated by the command above:
50		186
51	rxvt-unicode\|rxvt-unicode terminal (X Window System):\	187	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
52	:am:bw:eo:km:mi:ms:xn:xo:\	188	:am:bw:eo:km:mi:ms:xn:xo:\
53	:co#80:it#8:li#24:\	189	:co#80:it#8:li#24:lm#0:\
54	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	190	: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:\	191	: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:\	192	: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:\	193	: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:\	194	: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[@:\	195	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
		196	: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:\	197	: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~:\	198	: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~:\	199	: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:\	200	: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=:\	201	: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:\	202	: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:\	203	: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:\	204	: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:\	205	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
69	:vs=\E[?25h:	206	:vs=\E[?25h:
70		207
71	=item How can I configure rxvt-unicode so that it looks similar to the original rxvt?	208	=item Why does C<ls> no longer have coloured output?
72		209
73	Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode	210	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
74	behave similar to the original rxvt:	211	decide wether a terminal has colour, but uses it's own configuration
		212	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
		213	with most other terminals supporting colour). Either add:
75		214
76	URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1	215	TERM rxvt-unicode
77	URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1	216
		217	to C</etc/DIR_COLORS> or simply add:
		218
		219	alias ls='ls --color=auto'
		220
		221	to your C<.profile> or C<.bashrc>.
		222
		223	=item Why doesn't vim/emacs etc. use the 88 colour mode?
		224
		225	=item Why doesn't vim/emacs etc. make use of italic?
		226
		227	=item Why are the secondary screen-related options not working properly?
		228
		229	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
		230	distributions (most notably Debian GNU/Linux) break rxvt-unicode
		231	by setting C<TERM> to C<rxvt>, which doesn't have these extra
		232	features. Unfortunately, some of these (most notably, again, Debian
		233	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
		234	file, so you will need to install it on your own (See the question B<When
		235	I log-in to another system it tells me about missing terminfo data?> on
		236	how to do this).
		237
		238	=item My numerical keypad acts weird and generates differing output?
		239
		240	Some Debian GNUL/Linux users seem to have this problem, although no
		241	specific details were reported so far. It is possible that this is caused
		242	by the wrong C<TERM> setting, although the details of wether and how
		243	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		244	keymap. See the answer to the previous question, and please report if that
		245	helped.
78		246
79	=item Rxvt-unicode does not seem to understand the selected encoding?	247	=item Rxvt-unicode does not seem to understand the selected encoding?
80		248
81	=item Unicode does not seem to work?	249	=item Unicode does not seem to work?
82		250
…		…
85	subtly garbled, then you should check your locale settings.	253	subtly garbled, then you should check your locale settings.
86		254
87	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	255	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
88	programs. Often rxvt-unicode is started in the C<C> locale, while the	256	programs. Often rxvt-unicode is started in the C<C> locale, while the
89	login script running within the rxvt-unicode window changes the locale to	257	login script running within the rxvt-unicode window changes the locale to
90	sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work.	258	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
91		259
92	The best thing is to fix your startup environment, as you will likely run	260	The best thing is to fix your startup environment, as you will likely run
93	into other problems. If nothing works you can try this in your .profile.	261	into other problems. If nothing works you can try this in your .profile.
94		262
95	printf '\e]701;%s\007' "$LC_CTYPE"	263	printf '\e]701;%s\007' "$LC_CTYPE"
96		264
97	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	265	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
98	supported on your systems. Some systems have a C<locale> command which	266	supported on your systems. Some systems have a C<locale> command which
99	displays this. If it displays sth. like:	267	displays this (also, C<perl -e0> can be used to check locale settings, as
		268	it will complain loudly if it cannot set the locale). If it displays something
		269	like:
100		270
101	locale: Cannot set LC_CTYPE to default locale: ...	271	locale: Cannot set LC_CTYPE to default locale: ...
102		272
103	Then the locale you specified is not supported on your system.	273	Then the locale you specified is not supported on your system.
104		274
…		…
115	your system/os) have specified does not cover all the characters you want	285	your system/os) have specified does not cover all the characters you want
116	to display.	286	to display.
117		287
118	B<rxvt-unicode> makes a best-effort try at finding a replacement	288	B<rxvt-unicode> makes a best-effort try at finding a replacement
119	font. Often the result is fine, but sometimes the chosen font looks	289	font. Often the result is fine, but sometimes the chosen font looks
120	bad. Many fonts have totally strange characters that don't resemble the	290	bad/ugly/wrong. Some fonts have totally strange characters that don't
121	correct glyph at all, and rxvt-unicode lacks the artificial intelligence	291	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
122	to detect that a specific glyph is wrong: it has to believe the font that	292	intelligence to detect that a specific glyph is wrong: it has to believe
123	the characters it contains indeed look correct.	293	the font that the characters it claims to contain indeed look correct.
124		294
125	In that case, select a font of your taste and add it to the font list,	295	In that case, select a font of your taste and add it to the font list,
126	e.g.:	296	e.g.:
127		297
128	@@RXVT_NAME@@ -fn basefont,font2,font3...	298	@@RXVT_NAME@@ -fn basefont,font2,font3...
…		…
130	When rxvt-unicode sees a character, it will first look at the base	300	When rxvt-unicode sees a character, it will first look at the base
131	font. If the base font does not contain the character, it will go to the	301	font. If the base font does not contain the character, it will go to the
132	next font, and so on. Specifying your own fonts will also speed up this	302	next font, and so on. Specifying your own fonts will also speed up this
133	search and use less resources within rxvt-unicode and the X-server.	303	search and use less resources within rxvt-unicode and the X-server.
134		304
135	The only limitation is that all the fonts must not be larger than the base	305	The only limitation is that none of the fonts may be larger than the base
136	font, as the base font defines the principal cell size, which must be the	306	font, as the base font defines the terminal character cell size, which
137	same due to the way terminals work.	307	must be the same due to the way terminals work.
138		308
139	=item Why do some chinese characters look so different than others?	309	=item Why do some chinese characters look so different than others?
140		310
141	This is because there is a difference between script and language --	311	This is because there is a difference between script and language --
142	rxvt-unicode does not know which language the text that is output	312	rxvt-unicode does not know which language the text that is output is,
143	is, as it only knows the unicode character codes. If rxvt-unicode	313	as it only knows the unicode character codes. If rxvt-unicode first
144	first sees a japanese character, it might choose a japanese font for	314	sees a japanese/chinese character, it might choose a japanese font for
145	it. Subsequent japanese characters will take that font. Now, many chinese	315	display. Subsequent japanese characters will use that font. Now, many
146	characters aren't represented in japanese fonts, so when the first	316	chinese characters aren't represented in japanese fonts, so when the first
147	non-japanese character comes up, rxvt-unicode will look for a chinese font	317	non-japanese character comes up, rxvt-unicode will look for a chinese font
148	-- unfortunately at this point, it will still use the japanese font for	318	-- unfortunately at this point, it will still use the japanese font for
149	japanese characters that are also chinese.	319	chinese characters that are also in the japanese font.
150		320
151	The workaround is easy: just tag a chinese font at the end of your font	321	The workaround is easy: just tag a chinese font at the end of your font
152	list (see the previous question). The key is to view the font list as	322	list (see the previous question). The key is to view the font list as
153	a preference list: If you expect more japanese, list a japanese font	323	a preference list: If you expect more japanese, list a japanese font
154	first. If you expect more chinese, put a chinese font first.	324	first. If you expect more chinese, put a chinese font first.
155		325
156	In the future it might be possible to switch preferences at runtime (the	326	In the future it might be possible to switch language preferences at
157	internal data structure has no problem with using different fonts for	327	runtime (the internal data structure has no problem with using different
158	the same character at the same time, but no interface for this has been	328	fonts for the same character at the same time, but no interface for this
159	designed yet).	329	has been designed yet).
		330
		331	Until then, you might get away with switching fonts at runtime (see L<Can
		332	I switch the fonts at runtime?> later in this document).
160		333
161	=item Why does rxvt-unicode sometimes leave pixel droppings?	334	=item Why does rxvt-unicode sometimes leave pixel droppings?
162		335
163	Most fonts were not designed for terminal use, which means that character	336	Most fonts were not designed for terminal use, which means that character
164	size varies a lot. A font that is otherwise fine for terminal use might	337	size varies a lot. A font that is otherwise fine for terminal use might
…		…
170	however: Xft fonts often draw glyphs larger than their acclaimed bounding	343	however: Xft fonts often draw glyphs larger than their acclaimed bounding
171	box, and rxvt-unicode has no way of detecting this (the correct way is to	344	box, and rxvt-unicode has no way of detecting this (the correct way is to
172	ask for the character bounding box, which unfortunately is wrong in these	345	ask for the character bounding box, which unfortunately is wrong in these
173	cases).	346	cases).
174		347
175	It's not clear (to me at least), wether this is a bug in Xft, freetype, or	348	It's not clear (to me at least), wether this is a bug in Xft, freetype,
176	the respective font. If you encounter this problem there is no way to work	349	or the respective font. If you encounter this problem you might try using
177	around this except by using a different font.	350	the C<-lsp> option to give the font more height. If that doesn't work, you
		351	might be forced to use a different font.
178		352
179	All of this is not a problem when using X11 core fonts, as their bounding	353	All of this is not a problem when using X11 core fonts, as their bounding
180	box data is correct.	354	box data is correct.
		355
		356	=item On Solaris 9, many line-drawing characters are too wide.
		357
		358	Seems to be a known bug, read
		359	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
		360	following ugly workaround to get non-double-wide-characters working:
		361
		362	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
181		363
182	=item My Compose (Multi_key) key is no longer working.	364	=item My Compose (Multi_key) key is no longer working.
183		365
184	The most common causes for this are that either your locale is not set	366	The most common causes for this are that either your locale is not set
185	correctly, or you specified a B<preeditStyle> that is not supported by	367	correctly, or you specified a B<preeditStyle> that is not supported by
…		…
199	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape	381	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
200	character and so on.	382	character and so on.
201		383
202	=item How can I keep rxvt-unicode from using reverse video so much?	384	=item How can I keep rxvt-unicode from using reverse video so much?
203		385
204	First of all, make sure you are running with the right terminfo	386	First of all, make sure you are running with the right terminal settings
205	(C<urxvt>), which will get rid of most of these effects. Then make sure	387	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
206	you have specified colours for italic and bold, as otherwise rxvt-unicode	388	make sure you have specified colours for italic and bold, as otherwise
207	might use reverse video to simulate the effect:	389	rxvt-unicode might use reverse video to simulate the effect:
208		390
209	URxvt*colorBD: white	391	URxvt.colorBD: white
210	URxvt*colorIT: green	392	URxvt.colorIT: green
211		393
212	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?	394	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
213		395
214	For some unexplainable reason, some programs (i.e. irssi) assume a very	396	For some unexplainable reason, some rare programs assume a very weird
215	weird colour palette when confronted with a terminal with more than the	397	colour palette when confronted with a terminal with more than the standard
216	standard 8 colours (rxvt-unicode supports 88). The right fix is, of	398	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
217	course, to fix these programs not to assume non-ISO colours without very	399	these programs not to assume non-ISO colours without very good reasons.
218	good reasons.
219		400
220	In the meantime, you can either edit your C<urxvt> terminfo definition to	401	In the meantime, you can either edit your C<rxvt-unicode> terminfo
221	only claim 8 colour support or use C<TERM=rxvt>, which will fix colours	402	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
222	but keep you from using other rxvt-unicode features.	403	fix colours but keep you from using other rxvt-unicode features.
223		404
224	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	405	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
225		406
226	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	407	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
227	in your compile environment, or an implementation that implements it,	408	in your compile environment, or an implementation that implements it,
228	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	409	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
229	B<wchar_t> is represented as unicode.	410	B<wchar_t> is represented as unicode.
230		411
231	As you might have guessed, FreeBSD does neither define this symobl nor	412	As you might have guessed, FreeBSD does neither define this symobl nor
232	does it support it. Instead, it uses it's own internal representation of	413	does it support it. Instead, it uses it's own internal representation of
233	B<wchar_t>. This is, of course, completely legal.	414	B<wchar_t>. This is, of course, completely fine with respect to standards.
234		415
		416	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
		417	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
		418
235	However, C<__STDC_ISO_10646__> is the only sane way to support	419	C<__STDC_ISO_10646__> is the only sane way to support multi-language
236	multi-language apps in an OS, as using a locale-dependent (and	420	apps in an OS, as using a locale-dependent (and non-standardized)
237	non-standardized) representation of B<wchar_t> makes it impossible to	421	representation of B<wchar_t> makes it impossible to convert between
238	convert between B<wchar_t> (as used by X11 and your applications) and any	422	B<wchar_t> (as used by X11 and your applications) and any other encoding
239	other encoding without implementing OS-specific-wrappers for each and	423	without implementing OS-specific-wrappers for each and every locale. There
240	every locale. There simply are no APIs to convert B<wchar_t> into anything	424	simply are no APIs to convert B<wchar_t> into anything except the current
241	except the current locale encoding.	425	locale encoding.
242		426
243	Some applications (such as the formidable B<mlterm>) work around this	427	Some applications (such as the formidable B<mlterm>) work around this
244	by carrying their own replacement functions for character set handling	428	by carrying their own replacement functions for character set handling
245	with them, and either implementing OS-dependent hacks or doing multiple	429	with them, and either implementing OS-dependent hacks or doing multiple
246	conversions (which is slow and unreliable in case the OS implements	430	conversions (which is slow and unreliable in case the OS implements
247	encodings slightly different than the terminal emulator).	431	encodings slightly different than the terminal emulator).
248		432
249	The rxvt-unicode author insists that the right way to fix this is in the	433	The rxvt-unicode author insists that the right way to fix this is in the
250	system libraries once and for all, instead of forcing every app to carry	434	system libraries once and for all, instead of forcing every app to carry
251	complete replacements.	435	complete replacements for them :)
		436
		437	=item I use Solaris 9 and it doesn't compile/work/etc.
		438
		439	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
		440	problems with C<wcwidth> and a compile problem.
		441
		442	=item How can I use rxvt-unicode under cygwin?
		443
		444	rxvt-unicode should compile and run out of the box on cygwin, using
		445	the X11 libraries that come with cygwin. libW11 emulation is no
		446	longer supported (and makes no sense, either, as it only supported a
		447	single font). I recommend starting the X-server in C<-multiwindow> or
		448	C<-rootless> mode instead, which will result in similar look&feel as the
		449	old libW11 emulation.
		450
		451	At the time of this writing, cygwin didn't seem to support any multi-byte
		452	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		453	to 8-bit encodings.
252		454
253	=item How does rxvt-unicode determine the encoding to use?	455	=item How does rxvt-unicode determine the encoding to use?
254		456
255	=item Is there an option to switch encodings?	457	=item Is there an option to switch encodings?
256		458
…		…
258	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about	460	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
259	UTF-8 or any other encodings with respect to terminal I/O.	461	UTF-8 or any other encodings with respect to terminal I/O.
260		462
261	The reasons is that there exists a perfectly fine mechanism for selecting	463	The reasons is that there exists a perfectly fine mechanism for selecting
262	the encoding, doing I/O and (most important) communicating this to all	464	the encoding, doing I/O and (most important) communicating this to all
263	applications so everybody agrees on character properties such as width and	465	applications so everybody agrees on character properties such as width
264	code number. This mechanism is the I<locale>.	466	and code number. This mechanism is the I<locale>. Applications not using
		467	that info will have problems (for example, C<xterm> gets the width of
		468	characters wrong as it uses it's own, locale-independent table under all
		469	locales).
265		470
266	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All	471	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
267	programs doing the same (that is, most) will automatically agree in the	472	programs doing the same (that is, most) will automatically agree in the
268	interpretation of characters.	473	interpretation of characters.
269		474
…		…
276	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms	481	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
277	(i.e. C<de> or C<german>) are also common.	482	(i.e. C<de> or C<german>) are also common.
278		483
279	Rxvt-unicode ignores all other locale categories, and except for	484	Rxvt-unicode ignores all other locale categories, and except for
280	the encoding, ignores country or language-specific settings,	485	the encoding, ignores country or language-specific settings,
281	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode.	486	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		487	rxvt-unicode.
282		488
283	If you want to use a specific encoding you have to make sure you start	489	If you want to use a specific encoding you have to make sure you start
284	rxvt-unicode with the correct C<LC_CTYPE> category.	490	rxvt-unicode with the correct C<LC_CTYPE> category.
285		491
286	=item Can I switch locales at runtime?	492	=item Can I switch locales at runtime?
287		493
288	Yes, using an escape sequence. Try sth. like this, which sets	494	Yes, using an escape sequence. Try something like this, which sets
289	rxvt-unicode's idea of C<LC_CTYPE>.	495	rxvt-unicode's idea of C<LC_CTYPE>.
290		496
291	printf '\e]701;%s\007' ja_JP.SJIS	497	printf '\e]701;%s\007' ja_JP.SJIS
292		498
293	See also the previous question.	499	See also the previous answer.
294		500
295	Sometimes this capability is rather handy when you want to work in one	501	Sometimes this capability is rather handy when you want to work in
296	locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For	502	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
297	example, I use this script to start C<xjdic>, which first switches to a	503	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
298	locale supported by xjdic and back later:	504	first switches to a locale supported by xjdic and back later:
299		505
300	printf '\e]701;%s\007' ja_JP.SJIS	506	printf '\e]701;%s\007' ja_JP.SJIS
301	xjdic -js	507	xjdic -js
302	printf '\e]701;%s\007' de_DE.UTF-8	508	printf '\e]701;%s\007' de_DE.UTF-8
303		509
		510	You can also use xterm's C<luit> program, which usually works fine, except
		511	for some locales where character width differs between program- and
		512	rxvt-unicode-locales.
		513
304	=item Can I switch the fonts at runtime?	514	=item Can I switch the fonts at runtime?
305		515
306	Yes, using an escape sequence. Try sth. like this, which has the same	516	Yes, using an escape sequence. Try something like this, which has the same
307	effect as using the C<-fn> switch, and takes effect immediately:	517	effect as using the C<-fn> switch, and takes effect immediately:
308		518
309	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	519	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
310		520
311	This is useful if you e.g. work primarily with japanese (and prefer a	521	This is useful if you e.g. work primarily with japanese (and prefer a
…		…
316		526
317	=item Why do italic characters look as if clipped?	527	=item Why do italic characters look as if clipped?
318		528
319	Many fonts have difficulties with italic characters and hinting. For	529	Many fonts have difficulties with italic characters and hinting. For
320	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans	530	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
321	Mono> completely fails in it's italic face. A workaround is to enable	531	Mono> completely fails in it's italic face. A workaround might be to
322	freetype autohinting, i.e. like this:	532	enable freetype autohinting, i.e. like this:
323		533
324	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	534	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
325	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	535	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
326		536
327	=item My input method wants <some encoding> but I want UTF-8, what can I do?	537	=item My input method wants <some encoding> but I want UTF-8, what can I do?
328		538
329	You can specify separate locales for the input method and the rest of the	539	You can specify separate locales for the input method and the rest of the
330	terminal, using the resource C<imlocale>:	540	terminal, using the resource C<imlocale>:
…		…
334	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still	544	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
335	use your input method. Please note, however, that you will not be able to	545	use your input method. Please note, however, that you will not be able to
336	input characters outside C<EUC-JP> in a normal way then, as your input	546	input characters outside C<EUC-JP> in a normal way then, as your input
337	method limits you.	547	method limits you.
338		548
		549	=item Rxvt-unicode crashes when the X Input Method changes or exits.
		550
		551	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		552	design. Applications can avoid some crashes at the expense of memory
		553	leaks, and Input Methods can avoid some crashes by careful ordering at
		554	exit time. B<kinput2> (and derived input methods) generally succeeds,
		555	while B<SCIM> (or similar input methods) fails. In the end, however,
		556	crashes cannot be completely avoided even if both sides cooperate.
		557
		558	So the only workaround is not to kill your Input Method Servers.
		559
339	=item Rxvt-unicode uses gobs of memory, how can I reduce that?	560	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
340		561
341	Rxvt-unicode tries to obey the rule of not charging you for sth. you	562	Rxvt-unicode tries to obey the rule of not charging you for something you
342	don't use. One thing you should try is to configure out all settings that	563	don't use. One thing you should try is to configure out all settings that
343	you don't need, for example, Xft support is a resource hog by design,	564	you don't need, for example, Xft support is a resource hog by design,
344	when used. Compiling it out ensures that no Xft font will be loaded	565	when used. Compiling it out ensures that no Xft font will be loaded
345	accidentally when rxvt-unicode tries to find a font for your characters.	566	accidentally when rxvt-unicode tries to find a font for your characters.
346		567
…		…
353		574
354	=item Can I speed up Xft rendering somehow?	575	=item Can I speed up Xft rendering somehow?
355		576
356	Yes, the most obvious way to speed it up is to avoid Xft entirely, as	577	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
357	it is simply slow. If you still want Xft fonts you might try to disable	578	it is simply slow. If you still want Xft fonts you might try to disable
358	antialiasing (by appending C<:antialiasing=false>), which saves lots of	579	antialiasing (by appending C<:antialias=false>), which saves lots of
359	memory and also speeds up rendering considerably.	580	memory and also speeds up rendering considerably.
360		581
361	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	582	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
362		583
363	Rxvt-unicode will use whatever you specify as a font. If it needs to	584	Rxvt-unicode will use whatever you specify as a font. If it needs to
…		…
399	resources (or as long-options).	620	resources (or as long-options).
400		621
401	Here are values that are supposed to resemble a VGA screen,	622	Here are values that are supposed to resemble a VGA screen,
402	including the murky brown that passes for low-intensity yellow:	623	including the murky brown that passes for low-intensity yellow:
403		624
404	URxvt*color0: #000000	625	URxvt.color0: #000000
405	URxvt*color1: #A80000	626	URxvt.color1: #A80000
406	URxvt*color2: #00A800	627	URxvt.color2: #00A800
407	URxvt*color3: #A8A800	628	URxvt.color3: #A8A800
408	URxvt*color4: #0000A8	629	URxvt.color4: #0000A8
409	URxvt*color5: #A800A8	630	URxvt.color5: #A800A8
410	URxvt*color6: #00A8A8	631	URxvt.color6: #00A8A8
411	URxvt*color7: #A8A8A8	632	URxvt.color7: #A8A8A8
412		633
413	URxvt*color8: #000054	634	URxvt.color8: #000054
414	URxvt*color9: #FF0054	635	URxvt.color9: #FF0054
415	URxvt*color10: #00FF54	636	URxvt.color10: #00FF54
416	URxvt*color11: #FFFF54	637	URxvt.color11: #FFFF54
417	URxvt*color12: #0000FF	638	URxvt.color12: #0000FF
418	URxvt*color13: #FF00FF	639	URxvt.color13: #FF00FF
419	URxvt*color14: #00FFFF	640	URxvt.color14: #00FFFF
420	URxvt*color15: #FFFFFF	641	URxvt.color15: #FFFFFF
421		642
422	And here is a more complete set of non-standard colors described as	643	And here is a more complete set of non-standard colors described (not by
423	"pretty girly":	644	me) as "pretty girly".
424		645
425	URxvt.cursorColor: #dc74d1	646	URxvt.cursorColor: #dc74d1
426	URxvt.pointerColor: #dc74d1	647	URxvt.pointerColor: #dc74d1
427	URxvt.background: #0e0e0e	648	URxvt.background: #0e0e0e
428	URxvt.foreground: #4ad5e1	649	URxvt.foreground: #4ad5e1
…		…
439	URxvt.color6: #73f7ff	660	URxvt.color6: #73f7ff
440	URxvt.color14: #73f7ff	661	URxvt.color14: #73f7ff
441	URxvt.color7: #e1dddd	662	URxvt.color7: #e1dddd
442	URxvt.color15: #e1dddd	663	URxvt.color15: #e1dddd
443		664
		665	=item How can I start @@RXVT_NAME@@d in a race-free way?
		666
		667	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
		668	display, create the listening socket and then fork.
		669
444	=item What's with the strange Backspace/Delete key behaviour?	670	=item What's with the strange Backspace/Delete key behaviour?
445		671
446	Assuming that the physical Backspace key corresponds to the	672	Assuming that the physical Backspace key corresponds to the
447	BackSpace keysym (not likely for Linux ... see the following	673	BackSpace keysym (not likely for Linux ... see the following
448	question) there are two standard values that can be used for	674	question) there are two standard values that can be used for
…		…
466		692
467	# use Backspace = ^?	693	# use Backspace = ^?
468	$ stty erase ^?	694	$ stty erase ^?
469	$ @@RXVT_NAME@@	695	$ @@RXVT_NAME@@
470		696
471	Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).	697	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
472		698
473	For an existing rxvt-unicode:	699	For an existing rxvt-unicode:
474		700
475	# use Backspace = ^H	701	# use Backspace = ^H
476	$ stty erase ^H	702	$ stty erase ^H
…		…
485	properly reflects that.	711	properly reflects that.
486		712
487	The Delete key is a another casualty of the ill-defined Backspace problem.	713	The Delete key is a another casualty of the ill-defined Backspace problem.
488	To avoid confusion between the Backspace and Delete keys, the Delete	714	To avoid confusion between the Backspace and Delete keys, the Delete
489	key has been assigned an escape sequence to match the vt100 for Execute	715	key has been assigned an escape sequence to match the vt100 for Execute
490	(ESC[3~) and is in the supplied termcap/terminfo.	716	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
491		717
492	Some other Backspace problems:	718	Some other Backspace problems:
493		719
494	some editors use termcap/terminfo,	720	some editors use termcap/terminfo,
495	some editors (vim I'm told) expect Backspace = ^H,	721	some editors (vim I'm told) expect Backspace = ^H,
…		…
499		725
500	=item I don't like the key-bindings. How do I change them?	726	=item I don't like the key-bindings. How do I change them?
501		727
502	There are some compile-time selections available via configure. Unless	728	There are some compile-time selections available via configure. Unless
503	you have run "configure" with the C<--disable-resources> option you can	729	you have run "configure" with the C<--disable-resources> option you can
504	use the `keysym' resource to alter the keystrings associated with keysym	730	use the `keysym' resource to alter the keystrings associated with keysyms.
505	0xFF00 - 0xFFFF (function, cursor keys, etc).
506		731
507	Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270'	732	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
508		733
509	!# ----- special uses ------:	734	URxvt.keysym.Home: \033[1~
510	! tn3270 login, remap function and arrow keys.	735	URxvt.keysym.End: \033[4~
511	tn3270font: clean-bold----15-*	736	URxvt.keysym.C-apostrophe: \033<C-'>
		737	URxvt.keysym.C-slash: \033<C-/>
		738	URxvt.keysym.C-semicolon: \033<C-;>
		739	URxvt.keysym.C-grave: \033<C-`>
		740	URxvt.keysym.C-comma: \033<C-,>
		741	URxvt.keysym.C-period: \033<C-.>
		742	URxvt.keysym.C-0x60: \033<C-`>
		743	URxvt.keysym.C-Tab: \033<C-Tab>
		744	URxvt.keysym.C-Return: \033<C-Return>
		745	URxvt.keysym.S-Return: \033<S-Return>
		746	URxvt.keysym.S-space: \033<S-Space>
		747	URxvt.keysym.M-Up: \033<M-Up>
		748	URxvt.keysym.M-Down: \033<M-Down>
		749	URxvt.keysym.M-Left: \033<M-Left>
		750	URxvt.keysym.M-Right: \033<M-Right>
		751	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		752	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		753	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
512		754
513	! keysym - used by rxvt only	755	See some more examples in the documentation for the B<keysym> resource.
514	! Delete - ^D
515	tn3270*keysym.0xFFFF: \004
516
517	! Home - ^A
518	tn3270*keysym.0xFF50: \001
519	! Left - ^B
520	tn3270*keysym.0xFF51: \002
521	! Up - ^P
522	tn3270*keysym.0xFF52: \020
523	! Right - ^F
524	tn3270*keysym.0xFF53: \006
525	! Down - ^N
526	tn3270*keysym.0xFF54: \016
527	! End - ^E
528	tn3270*keysym.0xFF57: \005
529
530	! F1 - F12
531	tn3270*keysym.0xFFBE: \e1
532	tn3270*keysym.0xFFBF: \e2
533	tn3270*keysym.0xFFC0: \e3
534	tn3270*keysym.0xFFC1: \e4
535	tn3270*keysym.0xFFC2: \e5
536	tn3270*keysym.0xFFC3: \e6
537	tn3270*keysym.0xFFC4: \e7
538	tn3270*keysym.0xFFC5: \e8
539	tn3270*keysym.0xFFC6: \e9
540	tn3270*keysym.0xFFC7: \e0
541	tn3270*keysym.0xFFC8: \e-
542	tn3270*keysym.0xFFC9: \e=
543
544	! map Prior/Next to F7/F8
545	tn3270*keysym.0xFF55: \e7
546	tn3270*keysym.0xFF56: \e8
547		756
548	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.	757	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
549	How do I make use of them? For example, the Sun Keyboard type 4	758	How do I make use of them? For example, the Sun Keyboard type 4
550	has the following mappings that rxvt-unicode doesn't recognize.	759	has the following mappings that rxvt-unicode doesn't recognize.
551		760
…		…
554	F27 == Home	763	F27 == Home
555	F29 == Prior	764	F29 == Prior
556	F33 == End	765	F33 == End
557	F35 == Next	766	F35 == Next
558		767
559	Rather than have rxvt-unicode try to accommodate all the various possible keyboard	768	Rather than have rxvt-unicode try to accommodate all the various possible
560	mappings, it is better to use `xmodmap' to remap the keys as required for	769	keyboard mappings, it is better to use `xmodmap' to remap the keys as
561	your particular machine.	770	required for your particular machine.
562		771
563	=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?	772	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
564	I need this to decide about setting colors etc.	773	I need this to decide about setting colors etc.
565		774
566	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can	775	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
567	check and see if that is set. Note that several programs, JED, slrn,	776	check and see if that is set. Note that several programs, JED, slrn,
568	Midnight Commander automatically check this variable to decide whether or	777	Midnight Commander automatically check this variable to decide whether or
…		…
605	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be	814	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
606	interested in learning about new and exciting problems (but not FAQs :).	815	interested in learning about new and exciting problems (but not FAQs :).
607		816
608	=back	817	=back
609		818
610	=head1 SYNOPSIS	819	=head1 RXVT TECHNICAL REFERENCE
611
612	# set a new font set
613	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
614
615	# change the locale and tell rxvt-unicode about it
616	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
617
618	# set window title
619	printf '\33]2;%s\007' "new window title"
620		820
621	=head1 DESCRIPTION	821	=head1 DESCRIPTION
622		822
623	The rest of this document describes various technical aspects of	823	The rest of this document describes various technical aspects of
624	B<rxvt-unicode>. First the description of supported command sequences,	824	B<rxvt-unicode>. First the description of supported command sequences,
625	followed by menu and pixmap support and last by a description of all	825	followed by menu and pixmap support and last by a description of all
626	features selectable at C<configure> time.	826	features selectable at C<configure> time.
627		827
628	=head1 RXVT TECHNICAL REFERENCE
629
630	=head1 Definitions	828	=head1 Definitions
631		829
632	=over 4	830	=over 4
633		831
634	=item B<< C<c> >>	832	=item B<< C<c> >>
…		…
762	Single Shift Select of G3 Character Set (SS3): affects next character	960	Single Shift Select of G3 Character Set (SS3): affects next character
763	only I<unimplemented>	961	only I<unimplemented>
764		962
765	=item B<< C<ESC Z> >>	963	=item B<< C<ESC Z> >>
766		964
767	Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option>	965	Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option>
768		966
769	=item B<< C<ESC c> >>	967	=item B<< C<ESC c> >>
770		968
771	Full reset (RIS)	969	Full reset (RIS)
772		970
…		…
776		974
777	=item B<< C<ESC o> >>	975	=item B<< C<ESC o> >>
778		976
779	Invoke the G3 Character Set (LS3)	977	Invoke the G3 Character Set (LS3)
780		978
781	=item B<< C<ESC> ( C> >>	979	=item B<< C<ESC ( C> >>
782		980
783	Designate G0 Character Set (ISO 2022), see below for values of C<C>.	981	Designate G0 Character Set (ISO 2022), see below for values of C<C>.
784		982
785	=item B<< C<ESC> ) C> >>	983	=item B<< C<ESC ) C> >>
786		984
787	Designate G1 Character Set (ISO 2022), see below for values of C<C>.	985	Designate G1 Character Set (ISO 2022), see below for values of C<C>.
788		986
789	=item B<< C<ESC * C> >>	987	=item B<< C<ESC * C> >>
790		988
…		…
931		1129
932	=item B<< C<ESC [ Ps c> >>	1130	=item B<< C<ESC [ Ps c> >>
933		1131
934	Send Device Attributes (DA)	1132	Send Device Attributes (DA)
935	B<< C<Ps = 0> >> (or omitted): request attributes from terminal	1133	B<< C<Ps = 0> >> (or omitted): request attributes from terminal
936	returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video	1134	returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video
937	Option'')	1135	Option'')
938		1136
939	=item B<< C<ESC [ Ps d> >>	1137	=item B<< C<ESC [ Ps d> >>
940		1138
941	Cursor to Line B<< C<Ps> >> (VPA)	1139	Cursor to Line B<< C<Ps> >> (VPA)
…		…
1057		1255
1058	=item B<< C<ESC [ s> >>	1256	=item B<< C<ESC [ s> >>
1059		1257
1060	Save Cursor (SC)	1258	Save Cursor (SC)
1061		1259
		1260	=item B<< C<ESC [ Ps;Pt t> >>
		1261
		1262	Window Operations
		1263
		1264	=begin table
		1265
		1266	B<< C<Ps = 1> >> Deiconify (map) window
		1267	B<< C<Ps = 2> >> Iconify window
		1268	B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X\|Y)
		1269	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
		1270	B<< C<Ps = 5> >> Raise window
		1271	B<< C<Ps = 6> >> Lower window
		1272	B<< C<Ps = 7> >> Refresh screen once
		1273	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
		1274	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
		1275	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
		1276	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
		1277	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
		1278	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
		1279	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
		1280	B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>)
		1281	B<< C<Ps = 24..> >> Set window height to C<Ps> rows
		1282
		1283	=end table
		1284
		1285	=item B<< C<ESC [ u> >>
		1286
		1287	Restore Cursor
		1288
1062	=item B<< C<ESC [ Ps x> >>	1289	=item B<< C<ESC [ Ps x> >>
1063		1290
1064	Request Terminal Parameters (DECREQTPARM)	1291	Request Terminal Parameters (DECREQTPARM)
1065
1066	=item B<< C<ESC [ u> >>
1067
1068	Restore Cursor
1069		1292
1070	=back	1293	=back
1071		1294
1072	X<PrivateModes>	1295	X<PrivateModes>
1073		1296
…		…
1368	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1591	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1369	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1592	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1370	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1593	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>
1371	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1594	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>
1372	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1595	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
1373	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option>	1596	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1374	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1597	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1375	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>	1598	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1376	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> >>	1599	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> >>
1377	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1600	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1378	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)	1601	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).
1379	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)	1602	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).
1380	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1603	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1381	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>	1604	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1382	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1605	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1383	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1606	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1384	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1607	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1385	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1608	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1609	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1610	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1386		1611
1387	=end table	1612	=end table
1388		1613
1389	=back	1614	=back
1390		1615
…		…
1442		1667
1443	=item B<< [title:+I<string>] >>	1668	=item B<< [title:+I<string>] >>
1444		1669
1445	set the current menuBar's title to I<string>, which may contain the	1670	set the current menuBar's title to I<string>, which may contain the
1446	following format specifiers:	1671	following format specifiers:
1447	B<%%> : literal B<%> character	1672
1448	B<%n> : rxvt name (as per the B<-name> command-line option)	1673	B<%n> rxvt name (as per the B<-name> command-line option)
1449	B<%v> : rxvt version	1674	B<%v> rxvt version
		1675	B<%%> literal B<%> character
1450		1676
1451	=item B<[done]>	1677	=item B<[done]>
1452		1678
1453	set menuBar access as B<readonly>.	1679	set menuBar access as B<readonly>.
1454	End-of-file tag for B<< [read:+I<file>] >> operations.	1680	End-of-file tag for B<< [read:+I<file>] >> operations.
…		…
1600		1826
1601	As a convenience for the many Emacs-type editors, I<action> may start	1827	As a convenience for the many Emacs-type editors, I<action> may start
1602	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be	1828	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1603	appended if missed from B<M-x> commands.	1829	appended if missed from B<M-x> commands.
1604		1830
1605	As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or	1831	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1606	quick arrow), a B<BEL> (B<^G>) will be appended if needed.	1832	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1607		1833
1608	=over 4	1834	=over 4
1609		1835
1610	=item For example,	1836	=item For example,
…		…
2046	=end table	2272	=end table
2047		2273
2048	=head1 CONFIGURE OPTIONS	2274	=head1 CONFIGURE OPTIONS
2049		2275
2050	General hint: if you get compile errors, then likely your configuration	2276	General hint: if you get compile errors, then likely your configuration
2051	hasn't been tested well. Either try with --enable-everything or use the	2277	hasn't been tested well. Either try with C<--enable-everything> or use
2052	./reconf script as a base for experiments. ./reconf is used by myself,	2278	the F<./reconf> script as a base for experiments. F<./reconf> is used by
2053	so it should generally be a working config. Of course, you should always	2279	myself, so it should generally be a working config. Of course, you should
2054	report when a combination doesn't work, so it can be fixed. Marc Lehmann	2280	always report when a combination doesn't work, so it can be fixed. Marc
2055	<rxvt@schmorp.de>.	2281	Lehmann <rxvt@schmorp.de>.
		2282
		2283	All
2056		2284
2057	=over 4	2285	=over 4
2058		2286
2059	=item --enable-everything	2287	=item --enable-everything
2060		2288
2061	Add support for all non-multichoice options listed in "./configure	2289	Add (or remove) support for all non-multichoice options listed in "./configure
2062	--help". Note that unlike other enable options this is order dependant.	2290	--help".
		2291
2063	You can specify this and then disable options which this enables by	2292	You can specify this and then disable options you do not like by
2064	I<following> this with the appropriate commands.	2293	I<following> this with the appropriate C<--disable-...> arguments,
		2294	or you can start with a minimal configuration by specifying
		2295	C<--disable-everything> and than adding just the C<--enable-...> arguments
		2296	you want.
2065		2297
2066	=item --enable-xft	2298	=item --enable-xft (default: enabled)
2067		2299
2068	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2300	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2069	slower and require lots of memory, but as long as you don't use them, you	2301	slower and require lots of memory, but as long as you don't use them, you
2070	don't pay for them.	2302	don't pay for them.
2071		2303
2072	=item --enable-font-styles	2304	=item --enable-font-styles (default: on)
2073		2305
2074	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2306	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2075	styles. The fonts can be set manually or automatically.	2307	styles. The fonts can be set manually or automatically.
2076		2308
2077	=item --with-codesets=NAME,...	2309	=item --with-codesets=NAME,... (default: all)
2078		2310
2079	Compile in support for additional codeset (encoding) groups (eu, vn are	2311	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2080	always compiled in, which includes most 8-bit character sets). These	2312	are always compiled in, which includes most 8-bit character sets). These
2081	codeset tables are currently only used for driving X11 core fonts, they	2313	codeset tables are used for driving X11 core fonts, they are not required
2082	are not required for Xft fonts. Compiling them in will make your binary	2314	for Xft fonts, although having them compiled in lets rxvt-unicode choose
2083	bigger (together about 700kB), but it doesn't increase memory usage unless	2315	replacement fonts more intelligently. Compiling them in will make your
		2316	binary bigger (all of together cost about 700kB), but it doesn't increase
2084	you use an X11 font requiring one of these encodings.	2317	memory usage unless you use a font requiring one of these encodings.
2085		2318
2086	=begin table	2319	=begin table
2087		2320
2088	all all available codeset groups	2321	all all available codeset groups
2089	zh common chinese encodings	2322	zh common chinese encodings
…		…
2092	jp_ext rarely used but big japanese encodings	2325	jp_ext rarely used but big japanese encodings
2093	kr korean encodings	2326	kr korean encodings
2094		2327
2095	=end table	2328	=end table
2096		2329
2097	=item --enable-xim	2330	=item --enable-xim (default: on)
2098		2331
2099	Add support for XIM (X Input Method) protocol. This allows using	2332	Add support for XIM (X Input Method) protocol. This allows using
2100	alternative input methods (e.g. kinput2) and will also correctly	2333	alternative input methods (e.g. kinput2) and will also correctly
2101	set up the input for people using dead keys or compose keys.	2334	set up the input for people using dead keys or compose keys.
2102		2335
2103	=item --enable-unicode3	2336	=item --enable-unicode3 (default: off)
2104		2337
2105	Enable direct support for displaying unicode codepoints above	2338	Enable direct support for displaying unicode codepoints above
2106	65535 (the basic multilingual page). This increases storage	2339	65535 (the basic multilingual page). This increases storage
2107	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2340	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2108	support these extra characters, but Xft does.	2341	support these extra characters, but Xft does.
…		…
2111	even without this flag, but the number of such characters is	2344	even without this flag, but the number of such characters is
2112	limited to a view thousand (shared with combining characters,	2345	limited to a view thousand (shared with combining characters,
2113	see next switch), and right now rxvt-unicode cannot display them	2346	see next switch), and right now rxvt-unicode cannot display them
2114	(input/output and cut&paste still work, though).	2347	(input/output and cut&paste still work, though).
2115		2348
2116	=item --enable-combining	2349	=item --enable-combining (default: on)
2117		2350
2118	Enable automatic composition of combining characters into	2351	Enable automatic composition of combining characters into
2119	composite characters. This is required for proper viewing of text	2352	composite characters. This is required for proper viewing of text
2120	where accents are encoded as seperate unicode characters. This is	2353	where accents are encoded as seperate unicode characters. This is
2121	done by using precomposited characters when available or creating	2354	done by using precomposited characters when available or creating
2122	new pseudo-characters when no precomposed form exists.	2355	new pseudo-characters when no precomposed form exists.
2123		2356
2124	Without --enable-unicode3, the number of additional precomposed	2357	Without --enable-unicode3, the number of additional precomposed characters
2125	characters is rather limited (2048, if this is full, rxvt will use the	2358	is rather limited (2048, if this is full, rxvt-unicode will use the
2126	private use area, extending the number of combinations to 8448). With	2359	private use area, extending the number of combinations to 8448). With
2127	--enable-unicode3, no practical limit exists. This will also enable	2360	--enable-unicode3, no practical limit exists.
2128	storage of characters >65535.	2361
		2362	This option will also enable storage (but not display) of characters
		2363	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2129		2364
2130	The combining table also contains entries for arabic presentation forms,	2365	The combining table also contains entries for arabic presentation forms,
2131	but these are not currently used. Bug me if you want these to be used.	2366	but these are not currently used. Bug me if you want these to be used (and
		2367	tell me how these are to be used...).
2132		2368
2133	=item --enable-fallback(=CLASS)	2369	=item --enable-fallback(=CLASS) (default: Rxvt)
2134		2370
2135	When reading resource settings, also read settings for class CLASS	2371	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.
2136	(default: Rxvt). To disable resource fallback use --disable-fallback.
2137		2372
2138	=item --with-res-name=NAME	2373	=item --with-res-name=NAME (default: urxvt)
2139		2374
2140	Use the given name (default: urxvt) as default application name when	2375	Use the given name as default application name when
2141	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2376	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2142		2377
2143	=item --with-res-class=CLASS	2378	=item --with-res-class=CLASS /default: URxvt)
2144		2379
2145	Use the given class (default: URxvt) as default application class	2380	Use the given class as default application class
2146	when reading resources. Specify --with-res-class=Rxvt to replace	2381	when reading resources. Specify --with-res-class=Rxvt to replace
2147	rxvt.	2382	rxvt.
2148		2383
2149	=item --enable-utmp	2384	=item --enable-utmp (default: on)
2150		2385
2151	Write user and tty to utmp file (used by programs like F<w>) at	2386	Write user and tty to utmp file (used by programs like F<w>) at
2152	start of rxvt execution and delete information when rxvt exits.	2387	start of rxvt execution and delete information when rxvt exits.
2153		2388
2154	=item --enable-wtmp	2389	=item --enable-wtmp (default: on)
2155		2390
2156	Write user and tty to wtmp file (used by programs like F<last>) at	2391	Write user and tty to wtmp file (used by programs like F<last>) at
2157	start of rxvt execution and write logout when rxvt exits. This	2392	start of rxvt execution and write logout when rxvt exits. This
2158	option requires --enable-utmp to also be specified.	2393	option requires --enable-utmp to also be specified.
2159		2394
2160	=item --enable-lastlog	2395	=item --enable-lastlog (default: on)
2161		2396
2162	Write user and tty to lastlog file (used by programs like	2397	Write user and tty to lastlog file (used by programs like
2163	F<lastlogin>) at start of rxvt execution. This option requires	2398	F<lastlogin>) at start of rxvt execution. This option requires
2164	--enable-utmp to also be specified.	2399	--enable-utmp to also be specified.
2165		2400
2166	=item --enable-xpm-background	2401	=item --enable-xpm-background (default: off)
2167		2402
2168	Add support for XPM background pixmaps.	2403	Add support for XPM background pixmaps.
2169		2404
2170	=item --enable-transparency	2405	=item --enable-transparency (default: off)
2171		2406
2172	Add support for inheriting parent backgrounds thus giving a fake	2407	Add support for inheriting parent backgrounds thus giving a fake
2173	transparency to the term.	2408	transparency to the term.
2174		2409
2175	=item --enable-fading	2410	=item --enable-fading (default: on)
2176		2411
2177	Add support for fading the text when focus is lost.	2412	Add support for fading the text when focus is lost (requires C<--enable-transparency>).
2178		2413
2179	=item --enable-tinting	2414	=item --enable-tinting (default: on)
2180		2415
2181	Add support for tinting of transparent backgrounds.	2416	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2182		2417
2183	=item --enable-menubar	2418	=item --enable-menubar (default: off)
2184		2419
2185	Add support for our menu bar system (this interacts badly with	2420	Add support for our menu bar system (this interacts badly with
2186	dynamic locale switching currently).	2421	dynamic locale switching currently).
2187		2422
2188	=item --enable-rxvt-scroll	2423	=item --enable-rxvt-scroll (default: on)
2189		2424
2190	Add support for the original rxvt scrollbar.	2425	Add support for the original rxvt scrollbar.
2191		2426
2192	=item --enable-next-scroll	2427	=item --enable-next-scroll (default: on)
2193		2428
2194	Add support for a NeXT-like scrollbar.	2429	Add support for a NeXT-like scrollbar.
2195		2430
2196	=item --enable-xterm-scroll	2431	=item --enable-xterm-scroll (default: on)
2197		2432
2198	Add support for an Xterm-like scrollbar.	2433	Add support for an Xterm-like scrollbar.
2199		2434
2200	=item --enable-plain-scroll	2435	=item --enable-plain-scroll (default: on)
2201		2436
2202	Add support for a very unobtrusive, plain-looking scrollbar that	2437	Add support for a very unobtrusive, plain-looking scrollbar that
2203	is the favourite of the rxvt-unicode author, having used it for	2438	is the favourite of the rxvt-unicode author, having used it for
2204	many years.	2439	many years.
2205		2440
2206	=item --enable-half-shadow	2441	=item --enable-half-shadow (default: off)
2207		2442
2208	Make shadows on the scrollbar only half the normal width & height.	2443	Make shadows on the scrollbar only half the normal width & height.
2209	only applicable to rxvt scrollbars.	2444	only applicable to rxvt scrollbars.
2210		2445
2211	=item --enable-ttygid	2446	=item --enable-ttygid (default: off)
2212		2447
2213	Change tty device setting to group "tty" - only use this if	2448	Change tty device setting to group "tty" - only use this if
2214	your system uses this type of security.	2449	your system uses this type of security.
2215		2450
2216	=item --disable-backspace-key	2451	=item --disable-backspace-key
2217		2452
2218	Disable any handling of the backspace key by us - let the X server	2453	Removes any handling of the backspace key by us - let the X server do it.
		2454
		2455	=item --disable-delete-key
		2456
		2457	Removes any handling of the delete key by us - let the X server
2219	do it.	2458	do it.
2220		2459
2221	=item --disable-delete-key
2222
2223	Disable any handling of the delete key by us - let the X server
2224	do it.
2225
2226	=item --disable-resources	2460	=item --disable-resources
2227		2461
2228	Remove all resources checking.	2462	Removes any support for resource checking.
2229		2463
2230	=item --enable-xgetdefault	2464	=item --enable-xgetdefault
2231		2465
2232	Make resources checking via XGetDefault() instead of our small	2466	Make resources checking via XGetDefault() instead of our small
2233	version which only checks ~/.Xdefaults, or if that doesn't exist	2467	version which only checks ~/.Xdefaults, or if that doesn't exist then
2234	then ~/.Xresources.	2468	~/.Xresources.
2235		2469
2236	=item --enable-strings	2470	Please note that nowadays, things like XIM will automatically pull in and
		2471	use the full X resource manager, so the overhead of using it might be very
		2472	small, if nonexistant.
		2473
		2474	=item --enable-strings (default: off)
2237		2475
2238	Add support for our possibly faster memset() function and other	2476	Add support for our possibly faster memset() function and other
2239	various routines, overriding your system's versions which may	2477	various routines, overriding your system's versions which may
2240	have been hand-crafted in assembly or may require extra libraries	2478	have been hand-crafted in assembly or may require extra libraries
2241	to link in. (this breaks ANSI-C rules and has problems on many	2479	to link in. (this breaks ANSI-C rules and has problems on many
2242	GNU/Linux systems).	2480	GNU/Linux systems).
2243		2481
2244	=item --disable-swapscreen	2482	=item --disable-swapscreen
2245		2483
2246	Remove support for swap screen.	2484	Remove support for secondary/swap screen.
2247		2485
2248	=item --enable-frills	2486	=item --enable-frills (default: on)
2249		2487
2250	Add support for many small features that are not essential but nice to	2488	Add support for many small features that are not essential but nice to
2251	have. Normally you want this, but for very small binaries you may want to	2489	have. Normally you want this, but for very small binaries you may want to
2252	disable this.	2490	disable this.
2253		2491
		2492	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
		2493	in combination with other switches) is:
		2494
		2495	MWM-hints
		2496	EWMH-hints (pid, utf8 names) and protocols (ping)
		2497	seperate underline colour
		2498	settable border widths and borderless switch
		2499	settable extra linespacing
		2500	iso-14755-2 and -3, and visual feedback
		2501	backindex and forwardindex escape sequence
		2502	window op and some xterm/OSC escape sequences
		2503	tripleclickwords
		2504	settable insecure mode
		2505	keysym remapping support
		2506	cursor blinking and underline cursor
		2507	-embed, -pty-fd and -hold options
		2508
2254	=item --enable-iso14755	2509	=item --enable-iso14755 (default: on)
2255		2510
2256	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2511	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2257	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2512	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
2258	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with	2513	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2259	this switch.	2514	this switch.
2260		2515
2261	=item --enable-linespace
2262
2263	Add support to provide user specified line spacing between text rows.
2264
2265	=item --enable-keepscrolling	2516	=item --enable-keepscrolling (default: on)
2266		2517
2267	Add support for continual scrolling of the display when you hold	2518	Add support for continual scrolling of the display when you hold
2268	the mouse button down on a scrollbar arrow.	2519	the mouse button down on a scrollbar arrow.
2269		2520
2270	=item --enable-mousewheel	2521	=item --enable-mousewheel (default: on)
2271		2522
2272	Add support for scrolling via mouse wheel or buttons 4 & 5.	2523	Add support for scrolling via mouse wheel or buttons 4 & 5.
2273		2524
2274	=item --enable-slipwheeling	2525	=item --enable-slipwheeling (default: on)
2275		2526
2276	Add support for continual scrolling (using the mouse wheel as an	2527	Add support for continual scrolling (using the mouse wheel as an
2277	accelerator) while the control key is held down. This option	2528	accelerator) while the control key is held down. This option
2278	requires --enable-mousewheel to also be specified.	2529	requires --enable-mousewheel to also be specified.
2279		2530
2280	=item --disable-new-selection	2531	=item --disable-new-selection
2281		2532
2282	Remove support for mouse selection style like that of xterm.	2533	Remove support for mouse selection style like that of xterm.
2283		2534
2284	=item --enable-dmalloc	2535	=item --enable-dmalloc (default: off)
2285		2536
2286	Use Gray Watson's malloc - which is good for debugging See	2537	Use Gray Watson's malloc - which is good for debugging See
2287	http://www.letters.com/dmalloc/ for details If you use either this or the	2538	http://www.letters.com/dmalloc/ for details If you use either this or the
2288	next option, you may need to edit src/Makefile after compiling to point	2539	next option, you may need to edit src/Makefile after compiling to point
2289	DINCLUDE and DLIB to the right places.	2540	DINCLUDE and DLIB to the right places.
2290		2541
2291	You can only use either this option and the following (should	2542	You can only use either this option and the following (should
2292	you use either) .	2543	you use either) .
2293		2544
2294	=item --enable-dlmalloc	2545	=item --enable-dlmalloc (default: off)
2295		2546
2296	Use Doug Lea's malloc - which is good for a production version	2547	Use Doug Lea's malloc - which is good for a production version
2297	See L<http://g.oswego.edu/dl/html/malloc.html> for details.	2548	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2298		2549
2299	=item --enable-smart-resize	2550	=item --enable-smart-resize (default: on)
2300		2551
2301	Add smart growth/shrink behaviour when changing font size via from hot	2552	Add smart growth/shrink behaviour when changing font size via hot
2302	keys. This should keep in a fixed position the rxvt corner which is	2553	keys. This should keep the window corner which is closest to a corner of
2303	closest to a corner of the screen.	2554	the screen in a fixed position.
2304		2555
2305	=item --enable-cursor-blink
2306
2307	Add support for a blinking cursor.
2308
2309	=item --enable-pointer-blank	2556	=item --enable-pointer-blank (default: on)
2310		2557
2311	Add support to have the pointer disappear when typing or inactive.	2558	Add support to have the pointer disappear when typing or inactive.
2312		2559
2313	=item --with-name=NAME	2560	=item --with-name=NAME (default: urxvt)
2314		2561
2315	Set the basename for the installed binaries (default: urxvt, resulting in	2562	Set the basename for the installed binaries, resulting
2316	urxvt, urxvtd etc.). Specify --with-name=rxvt to replace rxvt.	2563	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
		2564	C<rxvt>.
2317		2565
2318	=item --with-term=NAME	2566	=item --with-term=NAME (default: rxvt-unicode)
2319		2567
2320	Change the environmental variable for the terminal to NAME (default	2568	Change the environmental variable for the terminal to NAME.
2321	"rxvt")
2322		2569
2323	=item --with-terminfo=PATH	2570	=item --with-terminfo=PATH
2324		2571
2325	Change the environmental variable for the path to the terminfo tree to	2572	Change the environmental variable for the path to the terminfo tree to
2326	PATH.	2573	PATH.

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.29 by root, Wed Dec 29 19:17:18 2004 UTC vs. Revision 1.64 by root, Sat Dec 24 12:55:17 2005 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.29 by root, Wed Dec 29 19:17:18 2004 UTC vs.
Revision 1.64 by root, Sat Dec 24 12:55:17 2005 UTC