ViewVC Help

View File | Revision Log | Show Annotations | Download File

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.47 by root, Mon Feb 14 10:48:44 2005 UTC vs.
Revision 1.109 by root, Tue Jan 31 21:06:26 2006 UTC

…		…
16	=head1 DESCRIPTION	16	=head1 DESCRIPTION
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is	21	The newest version of this document is also available on the World Wide Web at
22	also available on the World Wide Web at
23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
24		23
25	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		25
27	=over 4
28		26
		27	=head2 Meta, Features & Commandline Issues
		28
		29	=head3 My question isn't answered here, can I ask a human?
		30
		31	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		32	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		33	interested in learning about new and exciting problems (but not FAQs :).
		34
		35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
		36
		37	Beginning with version 7.3, there is a perl extension that implements a
		38	simple tabbed terminal. It is installed by default, so any of these should
		39	give you tabs:
		40
		41	@@URXVT_NAME@@ -pe tabbed
		42
		43	URxvt.perl-ext-common: default,tabbed
		44
		45	It will also work fine with tabbing functionality of many window managers
		46	or similar tabbing programs, and its embedding-features allow it to be
		47	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		48	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		49	(murxvt) terminal as an example embedding application.
		50
29	=item How do I know which rxvt-unicode version I'm using?	51	=head3 How do I know which rxvt-unicode version I'm using?
30		52
31	The version number is displayed with the usage (-h). Also the escape	53	The version number is displayed with the usage (-h). Also the escape
32	sequence C<ESC [ 8 n> sets the window title to the version number.	54	sequence C<ESC [ 8 n> sets the window title to the version number. When
		55	using the @@URXVT_NAME@@c client, the version displayed is that of the
		56	daemon.
33		57
34	=item I am using Debian GNU/Linux and have a problem...	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
35		59
36	The Debian GNU/Linux package of rxvt-unicode contains large patches that	60	Rxvt-unicode tries to obey the rule of not charging you for something you
37	considerably change the behaviour of rxvt-unicode. Before reporting a	61	don't use. One thing you should try is to configure out all settings that
38	bug to the original rxvt-unicode author please download and install the	62	you don't need, for example, Xft support is a resource hog by design,
39	genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to	63	when used. Compiling it out ensures that no Xft font will be loaded
40	reproduce the problem. If you cannot, chances are that the problems are	64	accidentally when rxvt-unicode tries to find a font for your characters.
41	specific to Debian GNU/Linux, in which case it should be reported via the
42	Debian Bug Tracking System (use C<reportbug> to report the bug).
43		65
44	For other problems that also affect the Debian package, you can and	66	Also, many people (me included) like large windows and even larger
45	probably should use the Debian BTS, too, because, after all, it's also a	67	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
46	bug in the Debian version and it serves as a reminder for other users that	68	6 bytes per screen cell. For a 160x?? window this amounts to almost a
47	might encounter the same issue.	69	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		70	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		71	rxvt-unicode then uses 8 bytes per screen cell.
48		72
49	=item When I log-in to another system it tells me about missing terminfo data?	73	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
50		74
51	The terminal description used by rxvt-unicode is not as widely available	75	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
52	as that for xterm, or even rxvt (for which the same problem often arises).	76	display, create the listening socket and then fork.
53		77
54	The correct solution for this problem is to install the terminfo, this can	78	=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
55	be done like this (with ncurses' infocmp):
56		79
57	REMOTE=remotesystem.domain	80	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
58	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	81	so you can check and see if that is set. Note that several programs, JED,
		82	slrn, Midnight Commander automatically check this variable to decide
		83	whether or not to use color.
59		84
60	... or by installing rxvt-unicode normally on the remote system,	85	=head3 How do I set the correct, full IP address for the DISPLAY variable?
61		86
62	If you cannot or do not want to do this, then you can simply set	87	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
63	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of	88	insecure mode then it is possible to use the following shell script
64	problems arising, which includes wrong keymapping, less and different	89	snippets to correctly set the display. If your version of rxvt-unicode
65	colours and some refresh errors in fullscreen applications. It's a nice	90	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
66	quick-and-dirty workaround for rare cases, though.	91	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		92	regular xterm.
67		93
68	If you always want to do this (and are fine with the consequences) you	94	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
69	can either recompile rxvt-unicode with the desired TERM value or use a	95	snippets:
70	resource to set it:
71		96
72	URxvt.termName: rxvt	97	# Bourne/Korn/POSIX family of shells:
		98	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		99	if [ ${TERM:-foo} = xterm ]; then
		100	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		101	echo -n '^[Z'
		102	read term_id
		103	stty icanon echo
		104	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		105	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		106	read DISPLAY # set it in our local shell
		107	fi
		108	fi
73		109
74	If you don't plan to use B<rxvt> (quite common...) you could also replace	110	=head3 How do I compile the manual pages on my own?
75	the rxvt terminfo file with the rxvt-unicode one.
76		111
77	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	112	You need to have a recent version of perl installed as F</usr/bin/perl>,
		113	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		114	the doc subdirectory and enter C<make alldoc>.
78		115
79	=item I need a termcap file entry.	116	=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
80		117
81	One reason you might want this is that some distributions or operating	118	I often get asked about this, and I think, no, they didn't cause extra
82	systems still compile some programs using the long-obsoleted termcap	119	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
83	library (Fedora Core's bash is one example) and rely on a termcap entry	120	that the urxvt binary is larger (due to some encoding tables always being
84	for C<rxvt-unicode>.	121	compiled in), but it actually uses less memory (RSS) after startup. Even
		122	with C<--disable-everything>, this comparison is a bit unfair, as many
		123	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		124	already in use in this mode.
85		125
86	You could use rxvt's termcap entry with resonable results in many cases.	126	text data bss drs rss filename
87	You can also create a termcap entry by using terminfo's infocmp program	127	98398 1664 24 15695 1824 rxvt --disable-everything
88	like this:	128	188985 9048 66616 18222 1788 urxvt --disable-everything
89		129
90	infocmp -C rxvt-unicode	130	When you C<--enable-everything> (which I<is> unfair, as this involves xft
		131	and full locale/XIM support which are quite bloaty inside libX11 and my
		132	libc), the two diverge, but not unreasnobaly so.
91		133
92	Or you could use this termcap entry, generated by the command above:	134	text data bss drs rss filename
		135	163431 2152 24 20123 2060 rxvt --enable-everything
		136	1035683 49680 66648 29096 3680 urxvt --enable-everything
93		137
94	rxvt-unicode|rxvt-unicode terminal (X Window System):\	138	The very large size of the text section is explained by the east-asian
95	:am:bw:eo:km:mi:ms:xn:xo:\	139	encoding tables, which, if unused, take up disk space but nothing else
96	:co#80:it#8:li#24:lm#0:\	140	and can be compiled out unless you rely on X11 core fonts that use those
97	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	141	encodings. The BSS size comes from the 64k emergency buffer that my c++
98	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\	142	compiler allocates (but of course doesn't use unless you are out of
99	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\	143	memory). Also, using an xft font instead of a core font immediately adds a
100	:as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\	144	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
101	:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\	145	not used.
102	:ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\
103	:im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
104	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
105	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
106	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
107	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
108	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
109	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
110	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
111	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
112	:vs=\E[?25h:
113		146
114	=item Why does C<ls> no longer have coloured output?	147	Of course, due to every character using two or four bytes instead of one,
		148	a large scrollback buffer will ultimately make rxvt-unicode use more
		149	memory.
115		150
116	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	151	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
117	decide wether a terminal has colour, but uses it's own configuration	152	still fares rather well. And compared to some monsters like gnome-terminal
118	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	153	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
119	with most other terminals supporting colour). Either add:	154	43180k in daemons that stay around after exit, plus half a minute of
		155	startup time, including the hundreds of warnings it spits out), it fares
		156	extremely well *g*.
120		157
121	TERM rxvt-unicode	158	=head3 Why C++, isn't that unportable/bloated/uncool?
122		159
123	to C</etc/DIR_COLORS> or simply add:	160	Is this a question? :) It comes up very often. The simple answer is: I had
		161	to write it, and C++ allowed me to write and maintain it in a fraction
		162	of the time and effort (which is a scarce resource for me). Put even
		163	shorter: It simply wouldn't exist without C++.
124		164
125	alias ls='ls --color=auto'	165	My personal stance on this is that C++ is less portable than C, but in
		166	the case of rxvt-unicode this hardly matters, as its portability limits
		167	are defined by things like X11, pseudo terminals, locale support and unix
		168	domain sockets, which are all less portable than C++ itself.
126		169
127	to your C<.profile> or C<.bashrc>.	170	Regarding the bloat, see the above question: It's easy to write programs
		171	in C that use gobs of memory, an certainly possible to write programs in
		172	C++ that don't. C++ also often comes with large libraries, but this is
		173	not necessarily the case with GCC. Here is what rxvt links against on my
		174	system with a minimal config:
128		175
129	=item Why doesn't vim/emacs etc. use the 88 colour mode?	176	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		177	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
		178	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
		179	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
130		180
131	=item Why doesn't vim/emacs etc. make use of italic?	181	And here is rxvt-unicode:
132		182
133	=item Why are the secondary screen-related options not working properly?	183	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		184	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		185	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
		186	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
		187	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
134		188
135	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	189	No large bloated libraries (of course, none were linked in statically),
136	distributions (most notably Debian GNU/Linux) break rxvt-unicode	190	except maybe libX11 :)
137	by setting C<TERM> to C<rxvt>, which doesn't have these extra
138	features. Unfortunately, some of these (most notably, again, Debian
139	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
140	file, so you will need to install it on your own (See the question B<When
141	I log-in to another system it tells me about missing terminfo data?> on
142	how to do this).
143		191
144	=item My numerical keypad acts weird and generates differing output?
145		192
146	Some Debian GNUL/Linux users seem to have this problem, although no	193	=head2 Rendering, Font & Look and Feel Issues
147	specific details were reported so far. It is possible that this is caused
148	by the wrong C<TERM> setting, although the details of wether and how
149	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
150	keymap. See the answer to the previous question, and please report if that
151	helped.
152		194
153	=item Rxvt-unicode does not seem to understand the selected encoding?	195	=head3 I can't get transparency working, what am I doing wrong?
154		196
155	=item Unicode does not seem to work?	197	First of all, transparency isn't officially supported in rxvt-unicode, so
		198	you are mostly on your own. Do not bug the author about it (but you may
		199	bug everybody else). Also, if you can't get it working consider it a rite
		200	of passage: ... and you failed.
156		201
157	If you encounter strange problems like typing an accented character but	202	Here are four ways to get transparency. B<Do> read the manpage and option
158	getting two unrelated other characters or similar, or if program output is	203	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
159	subtly garbled, then you should check your locale settings.
160		204
161	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	205	1. Use inheritPixmap:
162	programs. Often rxvt-unicode is started in the C<C> locale, while the
163	login script running within the rxvt-unicode window changes the locale to
164	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
165		206
166	The best thing is to fix your startup environment, as you will likely run	207	Esetroot wallpaper.jpg
167	into other problems. If nothing works you can try this in your .profile.	208	@@URXVT_NAME@@ -ip -tint red -sh 40
168		209
169	printf '\e]701;%s\007' "$LC_CTYPE"	210	That works. If you think it doesn't, you lack transparency and tinting
		211	support, or you are unable to read.
170		212
171	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	213	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
172	supported on your systems. Some systems have a C<locale> command which	214	to use effects other than tinting and shading: Just shade/tint/whatever
173	displays this (also, C<perl -e0> can be used to check locale settings, as	215	your picture with gimp or any other tool:
174	it will complain loudly if it cannot set the locale). If it displays something
175	like:
176		216
177	locale: Cannot set LC_CTYPE to default locale: ...	217	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		218	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
178		219
179	Then the locale you specified is not supported on your system.	220	That works. If you think it doesn't, you lack XPM and Perl support, or you
		221	are unable to read.
180		222
181	If nothing works and you are sure that everything is set correctly then	223	3. Use an ARGB visual:
182	you will need to remember a little known fact: Some programs just don't
183	support locales :(
184		224
185	=item Why do some characters look so much different than others?	225	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
186		226
187	=item How does rxvt-unicode choose fonts?	227	This requires XFT support, and the support of your X-server. If that
		228	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		229	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		230	bugfixes and workarounds for Xft and Xlib to make it work, but that
		231	doesn't mean that your WM has the required kludges in place.
188		232
189	Most fonts do not contain the full range of Unicode, which is	233	4. Use xcompmgr and let it do the job:
190	fine. Chances are that the font you (or the admin/package maintainer of
191	your system/os) have specified does not cover all the characters you want
192	to display.
193		234
194	B<rxvt-unicode> makes a best-effort try at finding a replacement	235	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
195	font. Often the result is fine, but sometimes the chosen font looks	236	-set _NET_WM_WINDOW_OPACITY 0xc0000000
196	bad/ugly/wrong. Some fonts have totally strange characters that don't
197	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
198	intelligence to detect that a specific glyph is wrong: it has to believe
199	the font that the characters it claims to contain indeed look correct.
200		237
201	In that case, select a font of your taste and add it to the font list,	238	Then click on a window you want to make transparent. Replace C<0xc0000000>
202	e.g.:	239	by other values to change the degree of opacity. If it doesn't work and
		240	your server crashes, you got to keep the pieces.
203		241
204	@@RXVT_NAME@@ -fn basefont,font2,font3...
205
206	When rxvt-unicode sees a character, it will first look at the base
207	font. If the base font does not contain the character, it will go to the
208	next font, and so on. Specifying your own fonts will also speed up this
209	search and use less resources within rxvt-unicode and the X-server.
210
211	The only limitation is that none of the fonts may be larger than the base
212	font, as the base font defines the terminal character cell size, which
213	must be the same due to the way terminals work.
214
215	=item Why do some chinese characters look so different than others?	242	=head3 Why do some chinese characters look so different than others?
216		243
217	This is because there is a difference between script and language --	244	This is because there is a difference between script and language --
218	rxvt-unicode does not know which language the text that is output is,	245	rxvt-unicode does not know which language the text that is output is,
219	as it only knows the unicode character codes. If rxvt-unicode first	246	as it only knows the unicode character codes. If rxvt-unicode first
220	sees a japanese/chinese character, it might choose a japanese font for	247	sees a japanese/chinese character, it might choose a japanese font for
…		…
235	has been designed yet).	262	has been designed yet).
236		263
237	Until then, you might get away with switching fonts at runtime (see L<Can	264	Until then, you might get away with switching fonts at runtime (see L<Can
238	I switch the fonts at runtime?> later in this document).	265	I switch the fonts at runtime?> later in this document).
239		266
240	=item Why does rxvt-unicode sometimes leave pixel droppings?	267	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
241		268
242	Most fonts were not designed for terminal use, which means that character	269	Most fonts were not designed for terminal use, which means that character
243	size varies a lot. A font that is otherwise fine for terminal use might	270	size varies a lot. A font that is otherwise fine for terminal use might
244	contain some characters that are simply too wide. Rxvt-unicode will avoid	271	contain some characters that are simply too wide. Rxvt-unicode will avoid
245	these characters. For characters that are just "a bit" too wide a special	272	these characters. For characters that are just "a bit" too wide a special
…		…
257	might be forced to use a different font.	284	might be forced to use a different font.
258		285
259	All of this is not a problem when using X11 core fonts, as their bounding	286	All of this is not a problem when using X11 core fonts, as their bounding
260	box data is correct.	287	box data is correct.
261		288
262	=item My Compose (Multi_key) key is no longer working.
263
264	The most common causes for this are that either your locale is not set
265	correctly, or you specified a B<preeditStyle> that is not supported by
266	your input method. For example, if you specified B<OverTheSpot> and
267	your input method (e.g. the default input method handling Compose keys)
268	does not support this (for instance because it is not visual), then
269	rxvt-unicode will continue without an input method.
270
271	In this case either do not specify a B<preeditStyle> or specify more than
272	one pre-edit style, such as B<OverTheSpot,Root,None>.
273
274	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
275
276	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
277	international keyboards) or simply use ISO 14755 support to your
278	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
279	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
280	character and so on.
281
282	=item How can I keep rxvt-unicode from using reverse video so much?	289	=head3 How can I keep rxvt-unicode from using reverse video so much?
283		290
284	First of all, make sure you are running with the right terminal settings	291	First of all, make sure you are running with the right terminal settings
285	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then	292	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
286	make sure you have specified colours for italic and bold, as otherwise	293	make sure you have specified colours for italic and bold, as otherwise
287	rxvt-unicode might use reverse video to simulate the effect:	294	rxvt-unicode might use reverse video to simulate the effect:
288		295
289	URxvt.colorBD: white	296	URxvt.colorBD: white
290	URxvt.colorIT: green	297	URxvt.colorIT: green
291		298
292	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?	299	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
293		300
294	For some unexplainable reason, some rare programs assume a very weird	301	For some unexplainable reason, some rare programs assume a very weird
295	colour palette when confronted with a terminal with more than the standard	302	colour palette when confronted with a terminal with more than the standard
296	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix	303	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
297	these programs not to assume non-ISO colours without very good reasons.	304	these programs not to assume non-ISO colours without very good reasons.
298		305
299	In the meantime, you can either edit your C<rxvt-unicode> terminfo	306	In the meantime, you can either edit your C<rxvt-unicode> terminfo
300	definition to only claim 8 colour support or use C<TERM=rxvt>, which will	307	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
301	fix colours but keep you from using other rxvt-unicode features.	308	fix colours but keep you from using other rxvt-unicode features.
302		309
303	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
304
305	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
306	in your compile environment, or an implementation that implements it,
307	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
308	B<wchar_t> is represented as unicode.
309
310	As you might have guessed, FreeBSD does neither define this symobl nor
311	does it support it. Instead, it uses it's own internal representation of
312	B<wchar_t>. This is, of course, completely fine with respect to standards.
313
314	However, C<__STDC_ISO_10646__> is the only sane way to support
315	multi-language apps in an OS, as using a locale-dependent (and
316	non-standardized) representation of B<wchar_t> makes it impossible to
317	convert between B<wchar_t> (as used by X11 and your applications) and any
318	other encoding without implementing OS-specific-wrappers for each and
319	every locale. There simply are no APIs to convert B<wchar_t> into anything
320	except the current locale encoding.
321
322	Some applications (such as the formidable B<mlterm>) work around this
323	by carrying their own replacement functions for character set handling
324	with them, and either implementing OS-dependent hacks or doing multiple
325	conversions (which is slow and unreliable in case the OS implements
326	encodings slightly different than the terminal emulator).
327
328	The rxvt-unicode author insists that the right way to fix this is in the
329	system libraries once and for all, instead of forcing every app to carry
330	complete replacements for them :)
331
332	=item How does rxvt-unicode determine the encoding to use?
333
334	=item Is there an option to switch encodings?
335
336	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
337	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
338	UTF-8 or any other encodings with respect to terminal I/O.
339
340	The reasons is that there exists a perfectly fine mechanism for selecting
341	the encoding, doing I/O and (most important) communicating this to all
342	applications so everybody agrees on character properties such as width
343	and code number. This mechanism is the I<locale>. Applications not using
344	that info will have problems (for example, C<xterm> gets the width of
345	characters wrong as it uses it's own, locale-independent table under all
346	locales).
347
348	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
349	programs doing the same (that is, most) will automatically agree in the
350	interpretation of characters.
351
352	Unfortunately, there is no system-independent way to select locales, nor
353	is there a standard on how locale specifiers will look like.
354
355	On most systems, the content of the C<LC_CTYPE> environment variable
356	contains an arbitrary string which corresponds to an already-installed
357	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
358	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
359	(i.e. C<de> or C<german>) are also common.
360
361	Rxvt-unicode ignores all other locale categories, and except for
362	the encoding, ignores country or language-specific settings,
363	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
364	rxvt-unicode.
365
366	If you want to use a specific encoding you have to make sure you start
367	rxvt-unicode with the correct C<LC_CTYPE> category.
368
369	=item Can I switch locales at runtime?
370
371	Yes, using an escape sequence. Try something like this, which sets
372	rxvt-unicode's idea of C<LC_CTYPE>.
373
374	printf '\e]701;%s\007' ja_JP.SJIS
375
376	See also the previous answer.
377
378	Sometimes this capability is rather handy when you want to work in
379	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
380	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
381	first switches to a locale supported by xjdic and back later:
382
383	printf '\e]701;%s\007' ja_JP.SJIS
384	xjdic -js
385	printf '\e]701;%s\007' de_DE.UTF-8
386
387	You can also use xterm's C<luit> program, which usually works fine, except
388	for some locales where character width differs between program- and
389	rxvt-unicode-locales.
390
391	=item Can I switch the fonts at runtime?	310	=head3 Can I switch the fonts at runtime?
392		311
393	Yes, using an escape sequence. Try something like this, which has the same	312	Yes, using an escape sequence. Try something like this, which has the same
394	effect as using the C<-fn> switch, and takes effect immediately:	313	effect as using the C<-fn> switch, and takes effect immediately:
395		314
396	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	315	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
…		…
399	japanese font), but you have to switch to chinese temporarily, where	318	japanese font), but you have to switch to chinese temporarily, where
400	japanese fonts would only be in your way.	319	japanese fonts would only be in your way.
401		320
402	You can think of this as a kind of manual ISO-2022 switching.	321	You can think of this as a kind of manual ISO-2022 switching.
403		322
404	=item Why do italic characters look as if clipped?	323	=head3 Why do italic characters look as if clipped?
405		324
406	Many fonts have difficulties with italic characters and hinting. For	325	Many fonts have difficulties with italic characters and hinting. For
407	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans	326	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
408	Mono> completely fails in it's italic face. A workaround might be to	327	Mono> completely fails in it's italic face. A workaround might be to
409	enable freetype autohinting, i.e. like this:	328	enable freetype autohinting, i.e. like this:
410		329
411	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	330	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
412	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	331	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
413		332
414	=item My input method wants <some encoding> but I want UTF-8, what can I do?
415
416	You can specify separate locales for the input method and the rest of the
417	terminal, using the resource C<imlocale>:
418
419	URxvt*imlocale: ja_JP.EUC-JP
420
421	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
422	use your input method. Please note, however, that you will not be able to
423	input characters outside C<EUC-JP> in a normal way then, as your input
424	method limits you.
425
426	=item Rxvt-unicode crashes when the X Input Method changes or exits.
427
428	Unfortunately, this is unavoidable, as the XIM protocol is racy by
429	design. Applications can avoid some crashes at the expense of memory
430	leaks, and Input Methods can avoid some crashes by careful ordering at
431	exit time. B<kinput2> (and derived input methods) generally succeeds,
432	while B<SCIM> (or similar input methods) fails. In the end, however,
433	crashes cannot be completely avoided even if both sides cooperate.
434
435	So the only workaround is not to kill your Input Method Servers.
436
437	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
438
439	Rxvt-unicode tries to obey the rule of not charging you for something you
440	don't use. One thing you should try is to configure out all settings that
441	you don't need, for example, Xft support is a resource hog by design,
442	when used. Compiling it out ensures that no Xft font will be loaded
443	accidentally when rxvt-unicode tries to find a font for your characters.
444
445	Also, many people (me included) like large windows and even larger
446	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
447	6 bytes per screen cell. For a 160x?? window this amounts to almost a
448	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
449	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
450	rxvt-unicode then uses 8 bytes per screen cell.
451
452	=item Can I speed up Xft rendering somehow?	333	=head3 Can I speed up Xft rendering somehow?
453		334
454	Yes, the most obvious way to speed it up is to avoid Xft entirely, as	335	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
455	it is simply slow. If you still want Xft fonts you might try to disable	336	it is simply slow. If you still want Xft fonts you might try to disable
456	antialiasing (by appending C<:antialiasing=false>), which saves lots of	337	antialiasing (by appending C<:antialias=false>), which saves lots of
457	memory and also speeds up rendering considerably.	338	memory and also speeds up rendering considerably.
458		339
459	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	340	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
460		341
461	Rxvt-unicode will use whatever you specify as a font. If it needs to	342	Rxvt-unicode will use whatever you specify as a font. If it needs to
462	fall back to it's default font search list it will prefer X11 core	343	fall back to it's default font search list it will prefer X11 core
463	fonts, because they are small and fast, and then use Xft fonts. It has	344	fonts, because they are small and fast, and then use Xft fonts. It has
464	antialiasing disabled for most of them, because the author thinks they	345	antialiasing disabled for most of them, because the author thinks they
465	look best that way.	346	look best that way.
466		347
467	If you want antialiasing, you have to specify the fonts manually.	348	If you want antialiasing, you have to specify the fonts manually.
468		349
469	=item Mouse cut/paste suddenly no longer works.
470
471	Make sure that mouse reporting is actually turned off since killing
472	some editors prematurely may leave the mouse in mouse report mode. I've
473	heard that tcsh may use mouse reporting unless it otherwise specified. A
474	quick check is to see if cut/paste works when the Alt or Shift keys are
475	depressed. See @@RXVT_NAME@@(7)
476
477	=item What's with this bold/blink stuff?	350	=head3 What's with this bold/blink stuff?
478		351
479	If no bold colour is set via C<colorBD:>, bold will invert text using the	352	If no bold colour is set via C<colorBD:>, bold will invert text using the
480	standard foreground colour.	353	standard foreground colour.
481		354
482	For the standard background colour, blinking will actually make the	355	For the standard background colour, blinking will actually make the
…		…
489		362
490	color0-7 are the low-intensity colors.	363	color0-7 are the low-intensity colors.
491		364
492	color8-15 are the corresponding high-intensity colors.	365	color8-15 are the corresponding high-intensity colors.
493		366
494	=item I don't like the screen colors. How do I change them?	367	=head3 I don't like the screen colors. How do I change them?
495		368
496	You can change the screen colors at run-time using F<~/.Xdefaults>	369	You can change the screen colors at run-time using F<~/.Xdefaults>
497	resources (or as long-options).	370	resources (or as long-options).
498		371
499	Here are values that are supposed to resemble a VGA screen,	372	Here are values that are supposed to resemble a VGA screen,
…		…
515	URxvt.color12: #0000FF	388	URxvt.color12: #0000FF
516	URxvt.color13: #FF00FF	389	URxvt.color13: #FF00FF
517	URxvt.color14: #00FFFF	390	URxvt.color14: #00FFFF
518	URxvt.color15: #FFFFFF	391	URxvt.color15: #FFFFFF
519		392
520	And here is a more complete set of non-standard colors described (not by	393	And here is a more complete set of non-standard colors.
521	me) as "pretty girly".
522		394
523	URxvt.cursorColor: #dc74d1	395	URxvt.cursorColor: #dc74d1
524	URxvt.pointerColor: #dc74d1	396	URxvt.pointerColor: #dc74d1
525	URxvt.background: #0e0e0e	397	URxvt.background: #0e0e0e
526	URxvt.foreground: #4ad5e1	398	URxvt.foreground: #4ad5e1
…		…
537	URxvt.color6: #73f7ff	409	URxvt.color6: #73f7ff
538	URxvt.color14: #73f7ff	410	URxvt.color14: #73f7ff
539	URxvt.color7: #e1dddd	411	URxvt.color7: #e1dddd
540	URxvt.color15: #e1dddd	412	URxvt.color15: #e1dddd
541		413
542	=item How can I start @@RXVT_NAME@@d in a race-free way?	414	They have been described (not by me) as "pretty girly".
543		415
544	Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a	416	=head3 Why do some characters look so much different than others?
545	server that answers @@RXVT_NAME@@c's requests, so it doesn't background	417
546	itself.	418	See next entry.
		419
		420	=head3 How does rxvt-unicode choose fonts?
		421
		422	Most fonts do not contain the full range of Unicode, which is
		423	fine. Chances are that the font you (or the admin/package maintainer of
		424	your system/os) have specified does not cover all the characters you want
		425	to display.
		426
		427	B<rxvt-unicode> makes a best-effort try at finding a replacement
		428	font. Often the result is fine, but sometimes the chosen font looks
		429	bad/ugly/wrong. Some fonts have totally strange characters that don't
		430	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		431	intelligence to detect that a specific glyph is wrong: it has to believe
		432	the font that the characters it claims to contain indeed look correct.
		433
		434	In that case, select a font of your taste and add it to the font list,
		435	e.g.:
		436
		437	@@URXVT_NAME@@ -fn basefont,font2,font3...
		438
		439	When rxvt-unicode sees a character, it will first look at the base
		440	font. If the base font does not contain the character, it will go to the
		441	next font, and so on. Specifying your own fonts will also speed up this
		442	search and use less resources within rxvt-unicode and the X-server.
		443
		444	The only limitation is that none of the fonts may be larger than the base
		445	font, as the base font defines the terminal character cell size, which
		446	must be the same due to the way terminals work.
547		447
548	To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the	448	=head2 Keyboard, Mouse & User Interaction
549	following method to wait for the startup message before continuing:
550		449
551	{ @@RXVT_NAME@@d & } | read	450	=head3 The new selection selects pieces that are too big, how can I select single words?
552		451
		452	If you want to select e.g. alphanumeric words, you can use the following
		453	setting:
		454
		455	URxvt.selection.pattern-0: ([[:word:]]+)
		456
		457	If you click more than twice, the selection will be extended
		458	more and more.
		459
		460	To get a selection that is very similar to the old code, try this pattern:
		461
		462	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		463
		464	Please also note that the I<LeftClick Shift-LeftClik> combination also
		465	selects words like the old code.
		466
		467	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		468
		469	You can disable the perl extension completely by setting the
		470	B<perl-ext-common> resource to the empty string, which also keeps
		471	rxvt-unicode from initialising perl, saving memory.
		472
		473	If you only want to disable specific features, you first have to
		474	identify which perl extension is responsible. For this, read the section
		475	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		476	example, to disable the B<selection-popup> and B<option-popup>, specify
		477	this B<perl-ext-common> resource:
		478
		479	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		480
		481	This will keep the default extensions, but disable the two popup
		482	extensions. Some extensions can also be configured, for example,
		483	scrollback search mode is triggered by B<M-s>. You can move it to any
		484	other combination either by setting the B<searchable-scrollback> resource:
		485
		486	URxvt.searchable-scrollback: CM-s
		487
		488	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		489
		490	See next entry.
		491
		492	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		493
		494	These are caused by the C<readline> perl extension. Under normal
		495	circumstances, it will move your cursor around when you click into the
		496	line that contains it. It tries hard not to do this at the wrong moment,
		497	but when running a program that doesn't parse cursor movements or in some
		498	cases during rlogin sessions, it fails to detect this properly.
		499
		500	You can permamently switch this feature off by disabling the C<readline>
		501	extension:
		502
		503	URxvt.perl-ext-common: default,-readline
		504
		505	=head3 My numerical keypad acts weird and generates differing output?
		506
		507	Some Debian GNUL/Linux users seem to have this problem, although no
		508	specific details were reported so far. It is possible that this is caused
		509	by the wrong C<TERM> setting, although the details of wether and how
		510	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		511	keymap. See the answer to the previous question, and please report if that
		512	helped.
		513
		514	=head3 My Compose (Multi_key) key is no longer working.
		515
		516	The most common causes for this are that either your locale is not set
		517	correctly, or you specified a B<preeditStyle> that is not supported by
		518	your input method. For example, if you specified B<OverTheSpot> and
		519	your input method (e.g. the default input method handling Compose keys)
		520	does not support this (for instance because it is not visual), then
		521	rxvt-unicode will continue without an input method.
		522
		523	In this case either do not specify a B<preeditStyle> or specify more than
		524	one pre-edit style, such as B<OverTheSpot,Root,None>.
		525
		526	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		527
		528	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		529	international keyboards) or simply use ISO 14755 support to your
		530	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		531	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		532	character and so on.
		533
		534	=head3 Mouse cut/paste suddenly no longer works.
		535
		536	Make sure that mouse reporting is actually turned off since killing
		537	some editors prematurely may leave the mouse in mouse report mode. I've
		538	heard that tcsh may use mouse reporting unless it otherwise specified. A
		539	quick check is to see if cut/paste works when the Alt or Shift keys are
		540	depressed.
		541
553	=item What's with the strange Backspace/Delete key behaviour?	542	=head3 What's with the strange Backspace/Delete key behaviour?
554		543
555	Assuming that the physical Backspace key corresponds to the	544	Assuming that the physical Backspace key corresponds to the
556	BackSpace keysym (not likely for Linux ... see the following	545	BackSpace keysym (not likely for Linux ... see the following
557	question) there are two standard values that can be used for	546	question) there are two standard values that can be used for
558	Backspace: C<^H> and C<^?>.	547	Backspace: C<^H> and C<^?>.
…		…
569		558
570	For starting a new rxvt-unicode:	559	For starting a new rxvt-unicode:
571		560
572	# use Backspace = ^H	561	# use Backspace = ^H
573	$ stty erase ^H	562	$ stty erase ^H
574	$ @@RXVT_NAME@@	563	$ @@URXVT_NAME@@
575		564
576	# use Backspace = ^?	565	# use Backspace = ^?
577	$ stty erase ^?	566	$ stty erase ^?
578	$ @@RXVT_NAME@@	567	$ @@URXVT_NAME@@
579		568
580	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).	569	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
581		570
582	For an existing rxvt-unicode:	571	For an existing rxvt-unicode:
583		572
584	# use Backspace = ^H	573	# use Backspace = ^H
585	$ stty erase ^H	574	$ stty erase ^H
…		…
598	key has been assigned an escape sequence to match the vt100 for Execute	587	key has been assigned an escape sequence to match the vt100 for Execute
599	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.	588	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
600		589
601	Some other Backspace problems:	590	Some other Backspace problems:
602		591
603	some editors use termcap/terminfo,	592	some editors use termcap/terminfo,
604	some editors (vim I'm told) expect Backspace = ^H,	593	some editors (vim I'm told) expect Backspace = ^H,
605	GNU Emacs (and Emacs-like editors) use ^H for help.	594	GNU Emacs (and Emacs-like editors) use ^H for help.
606		595
607	Perhaps someday this will all be resolved in a consistent manner.	596	Perhaps someday this will all be resolved in a consistent manner.
608		597
609	=item I don't like the key-bindings. How do I change them?	598	=head3 I don't like the key-bindings. How do I change them?
610		599
611	There are some compile-time selections available via configure. Unless	600	There are some compile-time selections available via configure. Unless
612	you have run "configure" with the C<--disable-resources> option you can	601	you have run "configure" with the C<--disable-resources> option you can
613	use the `keysym' resource to alter the keystrings associated with keysyms.	602	use the `keysym' resource to alter the keystrings associated with keysyms.
614		603
615	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>	604	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
616		605
617	URxvt.keysym.Home: \033[1~	606	URxvt.keysym.Home: \033[1~
618	URxvt.keysym.End: \033[4~	607	URxvt.keysym.End: \033[4~
619	URxvt.keysym.C-apostrophe: \033<C-'>	608	URxvt.keysym.C-apostrophe: \033<C-'>
620	URxvt.keysym.C-slash: \033<C-/>	609	URxvt.keysym.C-slash: \033<C-/>
…		…
635	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >	624	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
636	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007	625	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
637		626
638	See some more examples in the documentation for the B<keysym> resource.	627	See some more examples in the documentation for the B<keysym> resource.
639		628
640	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.	629	=head3 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map
641	How do I make use of them? For example, the Sun Keyboard type 4
642	has the following mappings that rxvt-unicode doesn't recognize.
643		630
644	KP_Insert == Insert	631	KP_Insert == Insert
645	F22 == Print	632	F22 == Print
646	F27 == Home	633	F27 == Home
647	F29 == Prior	634	F29 == Prior
…		…
650		637
651	Rather than have rxvt-unicode try to accommodate all the various possible	638	Rather than have rxvt-unicode try to accommodate all the various possible
652	keyboard mappings, it is better to use `xmodmap' to remap the keys as	639	keyboard mappings, it is better to use `xmodmap' to remap the keys as
653	required for your particular machine.	640	required for your particular machine.
654		641
655	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
656	I need this to decide about setting colors etc.
657		642
658	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
659	check and see if that is set. Note that several programs, JED, slrn,
660	Midnight Commander automatically check this variable to decide whether or
661	not to use color.
662		643
663	=item How do I set the correct, full IP address for the DISPLAY variable?	644	=head2 Terminal Configuration
664		645
665	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled	646	=head3 Why doesn't rxvt-unicode read my resources?
666	insecure mode then it is possible to use the following shell script
667	snippets to correctly set the display. If your version of rxvt-unicode
668	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
669	the COLORTERM variable can be used to distinguish rxvt-unicode from a
670	regular xterm.
671		647
672	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script	648	Well, why, indeed? It does, in a way very similar to other X
673	snippets:	649	applications. Most importantly, this means that if you or your OS loads
		650	resources into the X display (the right way to do it), rxvt-unicode will
		651	ignore any resource files in your home directory. It will only read
		652	F<$HOME/.Xdefaults> when no resources are attached to the display.
674		653
675	# Bourne/Korn/POSIX family of shells:	654	If you have or use an F<$HOME/.Xresources> file, chances are that
676	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know	655	resources are loaded into your X-server. In this case, you have to
677	if [ ${TERM:-foo} = xterm ]; then	656	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
678	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
679	echo -n '^[Z'
680	read term_id
681	stty icanon echo
682	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
683	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
684	read DISPLAY # set it in our local shell
685	fi
686	fi
687		657
688	=item How do I compile the manual pages for myself?	658	Also consider the form resources have to use:
689		659
690	You need to have a recent version of perl installed as F</usr/bin/perl>,	660	URxvt.resource: value
691	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
692	the doc subdirectory and enter C<make alldoc>.
693		661
694	=item My question isn't answered here, can I ask a human?	662	If you want to use another form (there are lots of different ways of
		663	specifying resources), make sure you understand wether and why it
		664	works. If unsure, use the form above.
695		665
696	Before sending me mail, you could go to IRC: C<irc.freenode.net>,	666	=head3 When I log-in to another system it tells me about missing terminfo data?
697	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
698	interested in learning about new and exciting problems (but not FAQs :).
699		667
700	=back	668	The terminal description used by rxvt-unicode is not as widely available
		669	as that for xterm, or even rxvt (for which the same problem often arises).
701		670
		671	The correct solution for this problem is to install the terminfo, this can
		672	be done like this (with ncurses' infocmp):
		673
		674	REMOTE=remotesystem.domain
		675	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
		676
		677	... or by installing rxvt-unicode normally on the remote system,
		678
		679	If you cannot or do not want to do this, then you can simply set
		680	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
		681	problems arising, which includes wrong keymapping, less and different
		682	colours and some refresh errors in fullscreen applications. It's a nice
		683	quick-and-dirty workaround for rare cases, though.
		684
		685	If you always want to do this (and are fine with the consequences) you
		686	can either recompile rxvt-unicode with the desired TERM value or use a
		687	resource to set it:
		688
		689	URxvt.termName: rxvt
		690
		691	If you don't plan to use B<rxvt> (quite common...) you could also replace
		692	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
		693
		694	=head3 C<tic> outputs some error when compiling the terminfo entry.
		695
		696	Most likely it's the empty definition for C<enacs=>. Just replace it by
		697	C<enacs=\E[0@> and try again.
		698
		699	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
		700
		701	See next entry.
		702
		703	=head3 I need a termcap file entry.
		704
		705	One reason you might want this is that some distributions or operating
		706	systems still compile some programs using the long-obsoleted termcap
		707	library (Fedora Core's bash is one example) and rely on a termcap entry
		708	for C<rxvt-unicode>.
		709
		710	You could use rxvt's termcap entry with resonable results in many cases.
		711	You can also create a termcap entry by using terminfo's infocmp program
		712	like this:
		713
		714	infocmp -C rxvt-unicode
		715
		716	Or you could use this termcap entry, generated by the command above:
		717
		718	rxvt-unicode|rxvt-unicode terminal (X Window System):\
		719	:am:bw:eo:km:mi:ms:xn:xo:\
		720	:co#80:it#8:li#24:lm#0:\
		721	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
		722	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
		723	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
		724	:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
		725	:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
		726	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
		727	:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
		728	:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
		729	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
		730	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
		731	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
		732	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
		733	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
		734	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
		735	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
		736	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
		737	:vs=\E[?25h:
		738
		739	=head3 Why does C<ls> no longer have coloured output?
		740
		741	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
		742	decide wether a terminal has colour, but uses it's own configuration
		743	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
		744	with most other terminals supporting colour). Either add:
		745
		746	TERM rxvt-unicode
		747
		748	to C</etc/DIR_COLORS> or simply add:
		749
		750	alias ls='ls --color=auto'
		751
		752	to your C<.profile> or C<.bashrc>.
		753
		754	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
		755
		756	See next entry.
		757
		758	=head3 Why doesn't vim/emacs etc. make use of italic?
		759
		760	See next entry.
		761
		762	=head3 Why are the secondary screen-related options not working properly?
		763
		764	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
		765	distributions (most notably Debian GNU/Linux) break rxvt-unicode
		766	by setting C<TERM> to C<rxvt>, which doesn't have these extra
		767	features. Unfortunately, some of these (most notably, again, Debian
		768	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
		769	file, so you will need to install it on your own (See the question B<When
		770	I log-in to another system it tells me about missing terminfo data?> on
		771	how to do this).
		772
		773
		774	=head2 Encoding / Locale / Input Method Issues
		775
		776	=head3 Rxvt-unicode does not seem to understand the selected encoding?
		777
		778	See next entry.
		779
		780	=head3 Unicode does not seem to work?
		781
		782	If you encounter strange problems like typing an accented character but
		783	getting two unrelated other characters or similar, or if program output is
		784	subtly garbled, then you should check your locale settings.
		785
		786	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
		787	programs. Often rxvt-unicode is started in the C<C> locale, while the
		788	login script running within the rxvt-unicode window changes the locale to
		789	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
		790
		791	The best thing is to fix your startup environment, as you will likely run
		792	into other problems. If nothing works you can try this in your .profile.
		793
		794	printf '\e]701;%s\007' "$LC_CTYPE"
		795
		796	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
		797	supported on your systems. Some systems have a C<locale> command which
		798	displays this (also, C<perl -e0> can be used to check locale settings, as
		799	it will complain loudly if it cannot set the locale). If it displays something
		800	like:
		801
		802	locale: Cannot set LC_CTYPE to default locale: ...
		803
		804	Then the locale you specified is not supported on your system.
		805
		806	If nothing works and you are sure that everything is set correctly then
		807	you will need to remember a little known fact: Some programs just don't
		808	support locales :(
		809
		810	=head3 How does rxvt-unicode determine the encoding to use?
		811
		812	See next entry.
		813
		814	=head3 Is there an option to switch encodings?
		815
		816	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		817	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
		818	UTF-8 or any other encodings with respect to terminal I/O.
		819
		820	The reasons is that there exists a perfectly fine mechanism for selecting
		821	the encoding, doing I/O and (most important) communicating this to all
		822	applications so everybody agrees on character properties such as width
		823	and code number. This mechanism is the I<locale>. Applications not using
		824	that info will have problems (for example, C<xterm> gets the width of
		825	characters wrong as it uses it's own, locale-independent table under all
		826	locales).
		827
		828	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
		829	programs doing the same (that is, most) will automatically agree in the
		830	interpretation of characters.
		831
		832	Unfortunately, there is no system-independent way to select locales, nor
		833	is there a standard on how locale specifiers will look like.
		834
		835	On most systems, the content of the C<LC_CTYPE> environment variable
		836	contains an arbitrary string which corresponds to an already-installed
		837	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		838	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		839	(i.e. C<de> or C<german>) are also common.
		840
		841	Rxvt-unicode ignores all other locale categories, and except for
		842	the encoding, ignores country or language-specific settings,
		843	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		844	rxvt-unicode.
		845
		846	If you want to use a specific encoding you have to make sure you start
		847	rxvt-unicode with the correct C<LC_CTYPE> category.
		848
		849	=head3 Can I switch locales at runtime?
		850
		851	Yes, using an escape sequence. Try something like this, which sets
		852	rxvt-unicode's idea of C<LC_CTYPE>.
		853
		854	printf '\e]701;%s\007' ja_JP.SJIS
		855
		856	See also the previous answer.
		857
		858	Sometimes this capability is rather handy when you want to work in
		859	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		860	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		861	first switches to a locale supported by xjdic and back later:
		862
		863	printf '\e]701;%s\007' ja_JP.SJIS
		864	xjdic -js
		865	printf '\e]701;%s\007' de_DE.UTF-8
		866
		867	You can also use xterm's C<luit> program, which usually works fine, except
		868	for some locales where character width differs between program- and
		869	rxvt-unicode-locales.
		870
		871	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		872
		873	You can specify separate locales for the input method and the rest of the
		874	terminal, using the resource C<imlocale>:
		875
		876	URxvt.imlocale: ja_JP.EUC-JP
		877
		878	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		879	use your input method. Please note, however, that you will not be able to
		880	input characters outside C<EUC-JP> in a normal way then, as your input
		881	method limits you.
		882
		883	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		884
		885	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		886	design. Applications can avoid some crashes at the expense of memory
		887	leaks, and Input Methods can avoid some crashes by careful ordering at
		888	exit time. B<kinput2> (and derived input methods) generally succeeds,
		889	while B<SCIM> (or similar input methods) fails. In the end, however,
		890	crashes cannot be completely avoided even if both sides cooperate.
		891
		892	So the only workaround is not to kill your Input Method Servers.
		893
		894
		895	=head2 Operating Systems / Package Maintaining
		896
		897	=head3 I am using Debian GNU/Linux and have a problem...
		898
		899	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		900	patches that considerably change the behaviour of rxvt-unicode (but
		901	unfortunately this notice has been removed). Before reporting a bug to
		902	the original rxvt-unicode author please download and install the genuine
		903	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		904	the problem. If you cannot, chances are that the problems are specific to
		905	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		906	Tracking System (use C<reportbug> to report the bug).
		907
		908	For other problems that also affect the Debian package, you can and
		909	probably should use the Debian BTS, too, because, after all, it's also a
		910	bug in the Debian version and it serves as a reminder for other users that
		911	might encounter the same issue.
		912
		913	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		914
		915	You should build one binary with the default options. F<configure>
		916	now enables most useful options, and the trend goes to making them
		917	runtime-switchable, too, so there is usually no drawback to enbaling them,
		918	except higher disk and possibly memory usage. The perl interpreter should
		919	be enabled, as important functionality (menus, selection, likely more in
		920	the future) depends on it.
		921
		922	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		923	system-wide (except maybe with C<defaults>). This will result in useful
		924	behaviour. If your distribution aims at low memory, add an empty
		925	C<perl-ext-common> resource to the app-defaults file. This will keep the
		926	perl interpreter disabled until the user enables it.
		927
		928	If you can/want build more binaries, I recommend building a minimal
		929	one with C<--disable-everything> (very useful) and a maximal one with
		930	C<--enable-everything> (less useful, it will be very big due to a lot of
		931	encodings built-in that increase download times and are rarely used).
		932
		933	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		934
		935	It should be, starting with release 7.1. You are encouraged to properly
		936	install urxvt with privileges necessary for your OS now.
		937
		938	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		939	into a helper process for privileged operations (pty handling on some
		940	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		941	immediately. This is much safer than most other terminals that keep
		942	privileges while running (but is more relevant to urxvt, as it contains
		943	things as perl interpreters, which might be "helpful" to attackers).
		944
		945	This forking is done as the very first within main(), which is very early
		946	and reduces possible bugs to initialisation code run before main(), or
		947	things like the dynamic loader of your system, which should result in very
		948	little risk.
		949
		950	=head3 On Solaris 9, many line-drawing characters are too wide.
		951
		952	Seems to be a known bug, read
		953	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
		954	following ugly workaround to get non-double-wide-characters working:
		955
		956	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
		957
		958	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
		959
		960	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
		961	in your compile environment, or an implementation that implements it,
		962	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
		963	B<wchar_t> is represented as unicode.
		964
		965	As you might have guessed, FreeBSD does neither define this symobl nor
		966	does it support it. Instead, it uses it's own internal representation of
		967	B<wchar_t>. This is, of course, completely fine with respect to standards.
		968
		969	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
		970	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
		971
		972	C<__STDC_ISO_10646__> is the only sane way to support multi-language
		973	apps in an OS, as using a locale-dependent (and non-standardized)
		974	representation of B<wchar_t> makes it impossible to convert between
		975	B<wchar_t> (as used by X11 and your applications) and any other encoding
		976	without implementing OS-specific-wrappers for each and every locale. There
		977	simply are no APIs to convert B<wchar_t> into anything except the current
		978	locale encoding.
		979
		980	Some applications (such as the formidable B<mlterm>) work around this
		981	by carrying their own replacement functions for character set handling
		982	with them, and either implementing OS-dependent hacks or doing multiple
		983	conversions (which is slow and unreliable in case the OS implements
		984	encodings slightly different than the terminal emulator).
		985
		986	The rxvt-unicode author insists that the right way to fix this is in the
		987	system libraries once and for all, instead of forcing every app to carry
		988	complete replacements for them :)
		989
		990	=head3 I use Solaris 9 and it doesn't compile/work/etc.
		991
		992	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
		993	problems with C<wcwidth> and a compile problem.
		994
		995	=head3 How can I use rxvt-unicode under cygwin?
		996
		997	rxvt-unicode should compile and run out of the box on cygwin, using
		998	the X11 libraries that come with cygwin. libW11 emulation is no
		999	longer supported (and makes no sense, either, as it only supported a
		1000	single font). I recommend starting the X-server in C<-multiwindow> or
		1001	C<-rootless> mode instead, which will result in similar look&feel as the
		1002	old libW11 emulation.
		1003
		1004	At the time of this writing, cygwin didn't seem to support any multi-byte
		1005	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		1006	to 8-bit encodings.
		1007
702	=head1 RXVT TECHNICAL REFERENCE	1008	=head1 RXVT-UNICODE TECHNICAL REFERENCE
703		1009
704	=head1 DESCRIPTION	1010	=head1 DESCRIPTION
705		1011
706	The rest of this document describes various technical aspects of	1012	The rest of this document describes various technical aspects of
707	B<rxvt-unicode>. First the description of supported command sequences,	1013	B<rxvt-unicode>. First the description of supported command sequences,
708	followed by menu and pixmap support and last by a description of all	1014	followed by pixmap support and last by a description of all features
709	features selectable at C<configure> time.	1015	selectable at C<configure> time.
710		1016
711	=head1 Definitions	1017	=head1 Definitions
712		1018
713	=over 4	1019	=over 4
714		1020
…		…
1282	B<< C<h> >> Send Mouse X & Y on button press.	1588	B<< C<h> >> Send Mouse X & Y on button press.
1283	B<< C<l> >> No mouse reporting.	1589	B<< C<l> >> No mouse reporting.
1284		1590
1285	=end table	1591	=end table
1286		1592
1287	=item B<< C<Ps = 10> >> (B<rxvt>)
1288
1289	=begin table
1290
1291	B<< C<h> >> menuBar visible
1292	B<< C<l> >> menuBar invisible
1293
1294	=end table
1295
1296	=item B<< C<Ps = 25> >>	1593	=item B<< C<Ps = 25> >>
1297		1594
1298	=begin table	1595	=begin table
1299		1596
1300	B<< C<h> >> Visible cursor {cnorm/cvvis}	1597	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
1413		1710
1414	=begin table	1711	=begin table
1415		1712
1416	B<< C<h> >> Scroll to bottom when a key is pressed	1713	B<< C<h> >> Scroll to bottom when a key is pressed
1417	B<< C<l> >> Don't scroll to bottom when a key is pressed	1714	B<< C<l> >> Don't scroll to bottom when a key is pressed
		1715
		1716	=end table
		1717
		1718	=item B<< C<Ps = 1021> >> (B<rxvt>)
		1719
		1720	=begin table
		1721
		1722	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
		1723	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1418		1724
1419	=end table	1725	=end table
1420		1726
1421	=item B<< C<Ps = 1047> >>	1727	=item B<< C<Ps = 1047> >>
1422		1728
…		…
1471	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	1777	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>
1472	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	1778	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>
1473	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	1779	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1474	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1780	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1475	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1781	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1476	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1782	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1477	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1783	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
		1784	B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM).
1478	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1785	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1479	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option>
1480	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1786	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1481	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>	1787	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1482	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> >>	1788	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> >>
1483	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1789	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1484	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)	1790	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).
1485	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)	1791	B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>.
1486	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1792	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1487	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>	1793	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
		1794	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		1795	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1488	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1796	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1489	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1797	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1490	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1798	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1491	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1799	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1800	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1801	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1802	B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1492		1803
1493	=end table	1804	=end table
1494		1805
1495	=back	1806	=back
1496		1807
1497	X<menuBar>
1498
1499	=head1 menuBar
1500
1501	B<< The exact syntax used is I<almost> solidified. >>
1502	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1503	menuBar.
1504
1505	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1506	omitted: use B<./> to specify a menu relative to the current menu.
1507
1508	=head2 Overview of menuBar operation
1509
1510	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1511	of C<Pt> can be used for a variety of tasks:
1512
1513	At the top level is the current menuBar which is a member of a circular
1514	linked-list of other such menuBars.
1515
1516	The menuBar acts as a parent for the various drop-down menus, which in
1517	turn, may have labels, separator lines, menuItems and subMenus.
1518
1519	The menuItems are the useful bits: you can use them to mimic keyboard
1520	input or even to send text or escape sequences back to rxvt.
1521
1522	The menuBar syntax is intended to provide a simple yet robust method of
1523	constructing and manipulating menus and navigating through the
1524	menuBars.
1525
1526	The first step is to use the tag B<< [menu:I<name>] >> which creates
1527	the menuBar called I<name> and allows access. You may now or menus,
1528	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1529	menuBar access as B<readonly> to prevent accidental corruption of the
1530	menus. To re-access the current menuBar for alterations, use the tag
1531	B<[menu]>, make the alterations and then use B<[done]>
1532
1533	X<menuBarCommands>
1534
1535	=head2 Commands
1536
1537	=over 4
1538
1539	=item B<< [menu:+I<name>] >>
1540
1541	access the named menuBar for creation or alteration. If a new menuBar
1542	is created, it is called I<name> (max of 15 chars) and the current
1543	menuBar is pushed onto the stack
1544
1545	=item B<[menu]>
1546
1547	access the current menuBar for alteration
1548
1549	=item B<< [title:+I<string>] >>
1550
1551	set the current menuBar's title to I<string>, which may contain the
1552	following format specifiers:
1553
1554	B<%n> rxvt name (as per the B<-name> command-line option)
1555	B<%v> rxvt version
1556	B<%%> literal B<%> character
1557
1558	=item B<[done]>
1559
1560	set menuBar access as B<readonly>.
1561	End-of-file tag for B<< [read:+I<file>] >> operations.
1562
1563	=item B<< [read:+I<file>] >>
1564
1565	read menu commands directly from I<file> (extension ".menu" will be
1566	appended if required.) Start reading at a line with B<[menu]> or B<<
1567	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1568
1569	Blank and comment lines (starting with B<#>) are ignored. Actually,
1570	since any invalid menu commands are also ignored, almost anything could
1571	be construed as a comment line, but this may be tightened up in the
1572	future ... so don't count on it!.
1573
1574	=item B<< [read:+I<file>;+I<name>] >>
1575
1576	The same as B<< [read:+I<file>] >>, but start reading at a line with
1577	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1578	B<[done]> is encountered.
1579
1580	=item B<[dump]>
1581
1582	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1583	later rereading.
1584
1585	=item B<[rm:name]>
1586
1587	remove the named menuBar
1588
1589	=item B<[rm] [rm:]>
1590
1591	remove the current menuBar
1592
1593	=item B<[rm*] [rm:*]>
1594
1595	remove all menuBars
1596
1597	=item B<[swap]>
1598
1599	swap the top two menuBars
1600
1601	=item B<[prev]>
1602
1603	access the previous menuBar
1604
1605	=item B<[next]>
1606
1607	access the next menuBar
1608
1609	=item B<[show]>
1610
1611	Enable display of the menuBar
1612
1613	=item B<[hide]>
1614
1615	Disable display of the menuBar
1616
1617	=item B<< [pixmap:+I<name>] >>
1618
1619	=item B<< [pixmap:+I<name>;I<scaling>] >>
1620
1621	(set the background pixmap globally
1622
1623	B<< A Future implementation I<may> make this local to the menubar >>)
1624
1625	=item B<< [:+I<command>:] >>
1626
1627	ignore the menu readonly status and issue a I<command> to or a menu or
1628	menuitem or change the ; a useful shortcut for setting the quick arrows
1629	from a menuBar.
1630
1631	=back
1632
1633	X<menuBarAdd>
1634
1635	=head2 Adding and accessing menus
1636
1637	The following commands may also be B<+> prefixed.
1638
1639	=over 4
1640
1641	=item B</+>
1642
1643	access menuBar top level
1644
1645	=item B<./+>
1646
1647	access current menu level
1648
1649	=item B<../+>
1650
1651	access parent menu (1 level up)
1652
1653	=item B<../../>
1654
1655	access parent menu (multiple levels up)
1656
1657	=item B<< I</path/>menu >>
1658
1659	add/access menu
1660
1661	=item B<< I</path/>menu/* >>
1662
1663	add/access menu and clear it if it exists
1664
1665	=item B<< I</path/>{-} >>
1666
1667	add separator
1668
1669	=item B<< I</path/>{item} >>
1670
1671	add B<item> as a label
1672
1673	=item B<< I</path/>{item} action >>
1674
1675	add/alter I<menuitem> with an associated I<action>
1676
1677	=item B<< I</path/>{item}{right-text} >>
1678
1679	add/alter I<menuitem> with B<right-text> as the right-justified text
1680	and as the associated I<action>
1681
1682	=item B<< I</path/>{item}{rtext} action >>
1683
1684	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1685	the right-justified text.
1686
1687	=back
1688
1689	=over 4
1690
1691	=item Special characters in I<action> must be backslash-escaped:
1692
1693	B<\a \b \E \e \n \r \t \octal>
1694
1695	=item or in control-character notation:
1696
1697	B<^@, ^A .. ^Z .. ^_, ^?>
1698
1699	=back
1700
1701	To send a string starting with a B<NUL> (B<^@>) character to the
1702	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1703	the first of which will be stripped off and the balance directed to the
1704	program. Otherwise if I<action> begins with B<NUL> followed by
1705	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1706	balance is sent back to rxvt.
1707
1708	As a convenience for the many Emacs-type editors, I<action> may start
1709	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1710	appended if missed from B<M-x> commands.
1711
1712	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1713	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1714
1715	=over 4
1716
1717	=item For example,
1718
1719	B<M-xapropos> is equivalent to B<\Exapropos\r>
1720
1721	=item and
1722
1723	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1724
1725	=back
1726
1727	The option B<< {I<right-rtext>} >> will be right-justified. In the
1728	absence of a specified action, this text will be used as the I<action>
1729	as well.
1730
1731	=over 4
1732
1733	=item For example,
1734
1735	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1736
1737	=back
1738
1739	The left label I<is> necessary, since it's used for matching, but
1740	implicitly hiding the left label (by using same name for both left and
1741	right labels), or explicitly hiding the left label (by preceeding it
1742	with a dot), makes it possible to have right-justified text only.
1743
1744	=over 4
1745
1746	=item For example,
1747
1748	B</File/{Open}{Open} Open-File-Action>
1749
1750	=item or hiding it
1751
1752	B</File/{.anylabel}{Open} Open-File-Action>
1753
1754	=back
1755
1756	X<menuBarRemove>
1757
1758	=head2 Removing menus
1759
1760	=over 4
1761
1762	=item B<< -/*+ >>
1763
1764	remove all menus from the menuBar, the same as B<[clear]>
1765
1766	=item B<< -+I</path>menu+ >>
1767
1768	remove menu
1769
1770	=item B<< -+I</path>{item}+ >>
1771
1772	remove item
1773
1774	=item B<< -+I</path>{-} >>
1775
1776	remove separator)
1777
1778	=item B<-/path/menu/*>
1779
1780	remove all items, separators and submenus from menu
1781
1782	=back
1783
1784	X<menuBarArrows>
1785
1786	=head2 Quick Arrows
1787
1788	The menus also provide a hook for I<quick arrows> to provide easier
1789	user access. If nothing has been explicitly set, the default is to
1790	emulate the curror keys. The syntax permits each arrow to be altered
1791	individually or all four at once without re-entering their common
1792	beginning/end text. For example, to explicitly associate cursor actions
1793	with the arrows, any of the following forms could be used:
1794
1795	=over 4
1796
1797	=item B<< <r>+I<Right> >>
1798
1799	=item B<< <l>+I<Left> >>
1800
1801	=item B<< <u>+I<Up> >>
1802
1803	=item B<< <d>+I<Down> >>
1804
1805	Define actions for the respective arrow buttons
1806
1807	=item B<< <b>+I<Begin> >>
1808
1809	=item B<< <e>+I<End> >>
1810
1811	Define common beginning/end parts for I<quick arrows> which used in
1812	conjunction with the above <r> <l> <u> <d> constructs
1813
1814	=back
1815
1816	=over 4
1817
1818	=item For example, define arrows individually,
1819
1820	<u>\E[A
1821
1822	<d>\E[B
1823
1824	<r>\E[C
1825
1826	<l>\E[D
1827
1828	=item or all at once
1829
1830	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
1831
1832	=item or more compactly (factoring out common parts)
1833
1834	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
1835
1836	=back
1837
1838	X<menuBarSummary>
1839
1840	=head2 Command Summary
1841
1842	A short summary of the most I<common> commands:
1843
1844	=over 4
1845
1846	=item [menu:name]
1847
1848	use an existing named menuBar or start a new one
1849
1850	=item [menu]
1851
1852	use the current menuBar
1853
1854	=item [title:string]
1855
1856	set menuBar title
1857
1858	=item [done]
1859
1860	set menu access to readonly and, if reading from a file, signal EOF
1861
1862	=item [done:name]
1863
1864	if reading from a file using [read:file;name] signal EOF
1865
1866	=item [rm:name]
1867
1868	remove named menuBar(s)
1869
1870	=item [rm] [rm:]
1871
1872	remove current menuBar
1873
1874	=item [rm*] [rm:*]
1875
1876	remove all menuBar(s)
1877
1878	=item [swap]
1879
1880	swap top two menuBars
1881
1882	=item [prev]
1883
1884	access the previous menuBar
1885
1886	=item [next]
1887
1888	access the next menuBar
1889
1890	=item [show]
1891
1892	map menuBar
1893
1894	=item [hide]
1895
1896	unmap menuBar
1897
1898	=item [pixmap;file]
1899
1900	=item [pixmap;file;scaling]
1901
1902	set a background pixmap
1903
1904	=item [read:file]
1905
1906	=item [read:file;name]
1907
1908	read in a menu from a file
1909
1910	=item [dump]
1911
1912	dump out all menuBars to /tmp/rxvt-PID
1913
1914	=item /
1915
1916	access menuBar top level
1917
1918	=item ./
1919
1920	=item ../
1921
1922	=item ../../
1923
1924	access current or parent menu level
1925
1926	=item /path/menu
1927
1928	add/access menu
1929
1930	=item /path/{-}
1931
1932	add separator
1933
1934	=item /path/{item}{rtext} action
1935
1936	add/alter menu item
1937
1938	=item -/*
1939
1940	remove all menus from the menuBar
1941
1942	=item -/path/menu
1943
1944	remove menu items, separators and submenus from menu
1945
1946	=item -/path/menu
1947
1948	remove menu
1949
1950	=item -/path/{item}
1951
1952	remove item
1953
1954	=item -/path/{-}
1955
1956	remove separator
1957
1958	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
1959
1960	menu quick arrows
1961
1962	=back
1963	X<XPM>	1808	X<XPM>
1964		1809
1965	=head1 XPM	1810	=head1 XPM
1966		1811
1967	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1812	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
…		…
2066	=begin table	1911	=begin table
2067		1912
2068	4 Shift	1913	4 Shift
2069	8 Meta	1914	8 Meta
2070	16 Control	1915	16 Control
2071	32 Double Click I<(Rxvt extension)>	1916	32 Double Click I<(rxvt extension)>
2072		1917
2073	=end table	1918	=end table
2074		1919
2075	Col = B<< C<< <x> - SPACE >> >>	1920	Col = B<< C<< <x> - SPACE >> >>
2076		1921
…		…
2153	=end table	1998	=end table
2154		1999
2155	=head1 CONFIGURE OPTIONS	2000	=head1 CONFIGURE OPTIONS
2156		2001
2157	General hint: if you get compile errors, then likely your configuration	2002	General hint: if you get compile errors, then likely your configuration
2158	hasn't been tested well. Either try with --enable-everything or use the	2003	hasn't been tested well. Either try with C<--enable-everything> or use
2159	./reconf script as a base for experiments. ./reconf is used by myself,	2004	the F<./reconf> script as a base for experiments. F<./reconf> is used by
2160	so it should generally be a working config. Of course, you should always	2005	myself, so it should generally be a working config. Of course, you should
2161	report when a combination doesn't work, so it can be fixed. Marc Lehmann	2006	always report when a combination doesn't work, so it can be fixed. Marc
2162	<rxvt@schmorp.de>.	2007	Lehmann <rxvt@schmorp.de>.
		2008
		2009	All
2163		2010
2164	=over 4	2011	=over 4
2165		2012
2166	=item --enable-everything	2013	=item --enable-everything
2167		2014
2168	Add support for all non-multichoice options listed in "./configure	2015	Add (or remove) support for all non-multichoice options listed in "./configure
2169	--help". Note that unlike other enable options this is order dependant.	2016	--help".
		2017
2170	You can specify this and then disable options which this enables by	2018	You can specify this and then disable options you do not like by
2171	I<following> this with the appropriate commands.	2019	I<following> this with the appropriate C<--disable-...> arguments,
		2020	or you can start with a minimal configuration by specifying
		2021	C<--disable-everything> and than adding just the C<--enable-...> arguments
		2022	you want.
2172		2023
2173	=item --enable-xft	2024	=item --enable-xft (default: enabled)
2174		2025
2175	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2026	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2176	slower and require lots of memory, but as long as you don't use them, you	2027	slower and require lots of memory, but as long as you don't use them, you
2177	don't pay for them.	2028	don't pay for them.
2178		2029
2179	=item --enable-font-styles	2030	=item --enable-font-styles (default: on)
2180		2031
2181	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2032	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2182	styles. The fonts can be set manually or automatically.	2033	styles. The fonts can be set manually or automatically.
2183		2034
2184	=item --with-codesets=NAME,...	2035	=item --with-codesets=NAME,... (default: all)
2185		2036
2186	Compile in support for additional codeset (encoding) groups (eu, vn are	2037	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2187	always compiled in, which includes most 8-bit character sets). These	2038	are always compiled in, which includes most 8-bit character sets). These
2188	codeset tables are currently only used for driving X11 core fonts, they	2039	codeset tables are used for driving X11 core fonts, they are not required
2189	are not required for Xft fonts. Compiling them in will make your binary	2040	for Xft fonts, although having them compiled in lets rxvt-unicode choose
2190	bigger (together about 700kB), but it doesn't increase memory usage unless	2041	replacement fonts more intelligently. Compiling them in will make your
		2042	binary bigger (all of together cost about 700kB), but it doesn't increase
2191	you use an X11 font requiring one of these encodings.	2043	memory usage unless you use a font requiring one of these encodings.
2192		2044
2193	=begin table	2045	=begin table
2194		2046
2195	all all available codeset groups	2047	all all available codeset groups
2196	zh common chinese encodings	2048	zh common chinese encodings
…		…
2199	jp_ext rarely used but big japanese encodings	2051	jp_ext rarely used but big japanese encodings
2200	kr korean encodings	2052	kr korean encodings
2201		2053
2202	=end table	2054	=end table
2203		2055
2204	=item --enable-xim	2056	=item --enable-xim (default: on)
2205		2057
2206	Add support for XIM (X Input Method) protocol. This allows using	2058	Add support for XIM (X Input Method) protocol. This allows using
2207	alternative input methods (e.g. kinput2) and will also correctly	2059	alternative input methods (e.g. kinput2) and will also correctly
2208	set up the input for people using dead keys or compose keys.	2060	set up the input for people using dead keys or compose keys.
2209		2061
2210	=item --enable-unicode3	2062	=item --enable-unicode3 (default: off)
		2063
		2064	Recommended to stay off unless you really need non-BMP characters.
2211		2065
2212	Enable direct support for displaying unicode codepoints above	2066	Enable direct support for displaying unicode codepoints above
2213	65535 (the basic multilingual page). This increases storage	2067	65535 (the basic multilingual page). This increases storage
2214	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2068	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2215	support these extra characters, but Xft does.	2069	support these extra characters, but Xft does.
…		…
2218	even without this flag, but the number of such characters is	2072	even without this flag, but the number of such characters is
2219	limited to a view thousand (shared with combining characters,	2073	limited to a view thousand (shared with combining characters,
2220	see next switch), and right now rxvt-unicode cannot display them	2074	see next switch), and right now rxvt-unicode cannot display them
2221	(input/output and cut&paste still work, though).	2075	(input/output and cut&paste still work, though).
2222		2076
2223	=item --enable-combining	2077	=item --enable-combining (default: on)
2224		2078
2225	Enable automatic composition of combining characters into	2079	Enable automatic composition of combining characters into
2226	composite characters. This is required for proper viewing of text	2080	composite characters. This is required for proper viewing of text
2227	where accents are encoded as seperate unicode characters. This is	2081	where accents are encoded as seperate unicode characters. This is
2228	done by using precomposited characters when available or creating	2082	done by using precomposited characters when available or creating
2229	new pseudo-characters when no precomposed form exists.	2083	new pseudo-characters when no precomposed form exists.
2230		2084
2231	Without --enable-unicode3, the number of additional precomposed characters	2085	Without --enable-unicode3, the number of additional precomposed
2232	is rather limited (2048, if this is full, rxvt-unicode will use the	2086	characters is somewhat limited (the 6400 private use characters will be
2233	private use area, extending the number of combinations to 8448). With
2234	--enable-unicode3, no practical limit exists.	2087	(ab-)used). With --enable-unicode3, no practical limit exists.
2235		2088
2236	This option will also enable storage (but not display) of characters	2089	This option will also enable storage (but not display) of characters
2237	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2090	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2238		2091
2239	The combining table also contains entries for arabic presentation forms,	2092	The combining table also contains entries for arabic presentation forms,
2240	but these are not currently used. Bug me if you want these to be used (and	2093	but these are not currently used. Bug me if you want these to be used (and
2241	tell me how these are to be used...).	2094	tell me how these are to be used...).
2242		2095
2243	=item --enable-fallback(=CLASS)	2096	=item --enable-fallback(=CLASS) (default: Rxvt)
2244		2097
2245	When reading resource settings, also read settings for class CLASS	2098	When reading resource settings, also read settings for class CLASS. To
2246	(default: Rxvt). To disable resource fallback use --disable-fallback.	2099	disable resource fallback use --disable-fallback.
2247		2100
2248	=item --with-res-name=NAME	2101	=item --with-res-name=NAME (default: urxvt)
2249		2102
2250	Use the given name (default: urxvt) as default application name when	2103	Use the given name as default application name when
2251	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2104	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2252		2105
2253	=item --with-res-class=CLASS	2106	=item --with-res-class=CLASS /default: URxvt)
2254		2107
2255	Use the given class (default: URxvt) as default application class	2108	Use the given class as default application class
2256	when reading resources. Specify --with-res-class=Rxvt to replace	2109	when reading resources. Specify --with-res-class=Rxvt to replace
2257	rxvt.	2110	rxvt.
2258		2111
2259	=item --enable-utmp	2112	=item --enable-utmp (default: on)
2260		2113
2261	Write user and tty to utmp file (used by programs like F<w>) at	2114	Write user and tty to utmp file (used by programs like F<w>) at
2262	start of rxvt execution and delete information when rxvt exits.	2115	start of rxvt execution and delete information when rxvt exits.
2263		2116
2264	=item --enable-wtmp	2117	=item --enable-wtmp (default: on)
2265		2118
2266	Write user and tty to wtmp file (used by programs like F<last>) at	2119	Write user and tty to wtmp file (used by programs like F<last>) at
2267	start of rxvt execution and write logout when rxvt exits. This	2120	start of rxvt execution and write logout when rxvt exits. This
2268	option requires --enable-utmp to also be specified.	2121	option requires --enable-utmp to also be specified.
2269		2122
2270	=item --enable-lastlog	2123	=item --enable-lastlog (default: on)
2271		2124
2272	Write user and tty to lastlog file (used by programs like	2125	Write user and tty to lastlog file (used by programs like
2273	F<lastlogin>) at start of rxvt execution. This option requires	2126	F<lastlogin>) at start of rxvt execution. This option requires
2274	--enable-utmp to also be specified.	2127	--enable-utmp to also be specified.
2275		2128
2276	=item --enable-xpm-background	2129	=item --enable-xpm-background (default: on)
2277		2130
2278	Add support for XPM background pixmaps.	2131	Add support for XPM background pixmaps.
2279		2132
2280	=item --enable-transparency	2133	=item --enable-transparency (default: on)
2281		2134
2282	Add support for inheriting parent backgrounds thus giving a fake	2135	Add support for inheriting parent backgrounds thus giving a fake
2283	transparency to the term.	2136	transparency to the term.
2284		2137
2285	=item --enable-fading	2138	=item --enable-fading (default: on)
2286		2139
2287	Add support for fading the text when focus is lost.	2140	Add support for fading the text when focus is lost (requires C<--enable-transparency>).
2288		2141
2289	=item --enable-tinting	2142	=item --enable-tinting (default: on)
2290		2143
2291	Add support for tinting of transparent backgrounds.	2144	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2292		2145
2293	=item --enable-menubar
2294
2295	Add support for our menu bar system (this interacts badly with
2296	dynamic locale switching currently).
2297
2298	=item --enable-rxvt-scroll	2146	=item --enable-rxvt-scroll (default: on)
2299		2147
2300	Add support for the original rxvt scrollbar.	2148	Add support for the original rxvt scrollbar.
2301		2149
2302	=item --enable-next-scroll	2150	=item --enable-next-scroll (default: on)
2303		2151
2304	Add support for a NeXT-like scrollbar.	2152	Add support for a NeXT-like scrollbar.
2305		2153
2306	=item --enable-xterm-scroll	2154	=item --enable-xterm-scroll (default: on)
2307		2155
2308	Add support for an Xterm-like scrollbar.	2156	Add support for an Xterm-like scrollbar.
2309		2157
2310	=item --enable-plain-scroll	2158	=item --enable-plain-scroll (default: on)
2311		2159
2312	Add support for a very unobtrusive, plain-looking scrollbar that	2160	Add support for a very unobtrusive, plain-looking scrollbar that
2313	is the favourite of the rxvt-unicode author, having used it for	2161	is the favourite of the rxvt-unicode author, having used it for
2314	many years.	2162	many years.
2315		2163
2316	=item --enable-half-shadow	2164	=item --enable-ttygid (default: off)
2317
2318	Make shadows on the scrollbar only half the normal width & height.
2319	only applicable to rxvt scrollbars.
2320
2321	=item --enable-ttygid
2322		2165
2323	Change tty device setting to group "tty" - only use this if	2166	Change tty device setting to group "tty" - only use this if
2324	your system uses this type of security.	2167	your system uses this type of security.
2325		2168
2326	=item --disable-backspace-key	2169	=item --disable-backspace-key
2327		2170
2328	Disable any handling of the backspace key by us - let the X server	2171	Removes any handling of the backspace key by us - let the X server do it.
		2172
		2173	=item --disable-delete-key
		2174
		2175	Removes any handling of the delete key by us - let the X server
2329	do it.	2176	do it.
2330		2177
2331	=item --disable-delete-key
2332
2333	Disable any handling of the delete key by us - let the X server
2334	do it.
2335
2336	=item --disable-resources	2178	=item --disable-resources
2337		2179
2338	Remove all resources checking.	2180	Removes any support for resource checking.
2339
2340	=item --enable-xgetdefault
2341
2342	Make resources checking via XGetDefault() instead of our small
2343	version which only checks ~/.Xdefaults, or if that doesn't exist then
2344	~/.Xresources.
2345
2346	Please note that nowadays, things like XIM will automatically pull in and
2347	use the full X resource manager, so the overhead of using it might be very
2348	small, if nonexistant.
2349
2350	=item --enable-strings
2351
2352	Add support for our possibly faster memset() function and other
2353	various routines, overriding your system's versions which may
2354	have been hand-crafted in assembly or may require extra libraries
2355	to link in. (this breaks ANSI-C rules and has problems on many
2356	GNU/Linux systems).
2357		2181
2358	=item --disable-swapscreen	2182	=item --disable-swapscreen
2359		2183
2360	Remove support for swap screen.	2184	Remove support for secondary/swap screen.
2361		2185
2362	=item --enable-frills	2186	=item --enable-frills (default: on)
2363		2187
2364	Add support for many small features that are not essential but nice to	2188	Add support for many small features that are not essential but nice to
2365	have. Normally you want this, but for very small binaries you may want to	2189	have. Normally you want this, but for very small binaries you may want to
2366	disable this.	2190	disable this.
2367		2191
2368	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2192	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2369	in combination with other switches) is:	2193	in combination with other switches) is:
2370		2194
2371	MWM-hints	2195	MWM-hints
		2196	EWMH-hints (pid, utf8 names) and protocols (ping)
2372	seperate underline colour	2197	seperate underline colour (-underlineColor)
2373	settable border widths and borderless switch	2198	settable border widths and borderless switch (-w, -b, -bl)
		2199	visual depth selection (-depth)
2374	settable extra linespacing	2200	settable extra linespacing /-lsp)
2375	extra window properties (e.g. UTF-8 window names and PID)
2376	iso-14755-2 and -3, and visual feedback	2201	iso-14755-2 and -3, and visual feedback
2377	backindex and forwardindex escape sequence
2378	window op and locale change escape sequences
2379	tripleclickwords	2202	tripleclickwords (-tcw)
2380	settable insecure mode	2203	settable insecure mode (-insecure)
2381	keysym remapping support	2204	keysym remapping support
		2205	cursor blinking and underline cursor (-cb, -uc)
		2206	XEmbed support (-embed)
		2207	user-pty (-pty-fd)
		2208	hold on exit (-hold)
		2209	skip builtin block graphics (-sbg)
2382		2210
		2211	It also enabled some non-essential features otherwise disabled, such as:
		2212
		2213	some round-trip time optimisations
		2214	nearest color allocation on pseudocolor screens
		2215	UTF8_STRING supporr for selection
		2216	sgr modes 90..97 and 100..107
		2217	backindex and forwardindex escape sequences
		2218	view change/zero scorllback esacpe sequences
		2219	locale switching escape sequence
		2220	window op and some xterm/OSC escape sequences
		2221	rectangular selections
		2222	trailing space removal for selections
		2223	verbose X error handling
		2224
2383	=item --enable-iso14755	2225	=item --enable-iso14755 (default: on)
2384		2226
2385	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2227	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2386	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2228	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
2387	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with	2229	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2388	this switch.	2230	this switch.
2389		2231
2390	=item --enable-keepscrolling	2232	=item --enable-keepscrolling (default: on)
2391		2233
2392	Add support for continual scrolling of the display when you hold	2234	Add support for continual scrolling of the display when you hold
2393	the mouse button down on a scrollbar arrow.	2235	the mouse button down on a scrollbar arrow.
2394		2236
2395	=item --enable-mousewheel	2237	=item --enable-mousewheel (default: on)
2396		2238
2397	Add support for scrolling via mouse wheel or buttons 4 & 5.	2239	Add support for scrolling via mouse wheel or buttons 4 & 5.
2398		2240
2399	=item --enable-slipwheeling	2241	=item --enable-slipwheeling (default: on)
2400		2242
2401	Add support for continual scrolling (using the mouse wheel as an	2243	Add support for continual scrolling (using the mouse wheel as an
2402	accelerator) while the control key is held down. This option	2244	accelerator) while the control key is held down. This option
2403	requires --enable-mousewheel to also be specified.	2245	requires --enable-mousewheel to also be specified.
2404		2246
2405	=item --disable-new-selection	2247	=item --disable-new-selection
2406		2248
2407	Remove support for mouse selection style like that of xterm.	2249	Remove support for mouse selection style like that of xterm.
2408		2250
2409	=item --enable-dmalloc	2251	=item --enable-dmalloc (default: off)
2410		2252
2411	Use Gray Watson's malloc - which is good for debugging See	2253	Use Gray Watson's malloc - which is good for debugging See
2412	http://www.letters.com/dmalloc/ for details If you use either this or the	2254	http://www.letters.com/dmalloc/ for details If you use either this or the
2413	next option, you may need to edit src/Makefile after compiling to point	2255	next option, you may need to edit src/Makefile after compiling to point
2414	DINCLUDE and DLIB to the right places.	2256	DINCLUDE and DLIB to the right places.
2415		2257
2416	You can only use either this option and the following (should	2258	You can only use either this option and the following (should
2417	you use either) .	2259	you use either) .
2418		2260
2419	=item --enable-dlmalloc	2261	=item --enable-dlmalloc (default: off)
2420		2262
2421	Use Doug Lea's malloc - which is good for a production version	2263	Use Doug Lea's malloc - which is good for a production version
2422	See L<http://g.oswego.edu/dl/html/malloc.html> for details.	2264	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2423		2265
2424	=item --enable-smart-resize	2266	=item --enable-smart-resize (default: on)
2425		2267
2426	Add smart growth/shrink behaviour when changing font size via from hot	2268	Add smart growth/shrink behaviour when changing font size via hot
2427	keys. This should keep in a fixed position the rxvt corner which is	2269	keys. This should keep the window corner which is closest to a corner of
2428	closest to a corner of the screen.	2270	the screen in a fixed position.
2429		2271
2430	=item --enable-cursor-blink
2431
2432	Add support for a blinking cursor.
2433
2434	=item --enable-pointer-blank	2272	=item --enable-pointer-blank (default: on)
2435		2273
2436	Add support to have the pointer disappear when typing or inactive.	2274	Add support to have the pointer disappear when typing or inactive.
2437		2275
2438	=item --with-name=NAME	2276	=item --enable-perl (default: on)
2439		2277
		2278	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
		2279	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
		2280	in F<src/perl-ext/> for the extensions that are installed by default. The
		2281	perl interpreter that is used can be specified via the C<PERL> environment
		2282	variable when running configure.
		2283
		2284	=item --with-name=NAME (default: urxvt)
		2285
2440	Set the basename for the installed binaries (default: C<urxvt>, resulting	2286	Set the basename for the installed binaries, resulting
2441	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2287	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
2442	C<rxvt>.	2288	C<rxvt>.
2443		2289
2444	=item --with-term=NAME	2290	=item --with-term=NAME (default: rxvt-unicode)
2445		2291
2446	Change the environmental variable for the terminal to NAME (default	2292	Change the environmental variable for the terminal to NAME.
2447	C<rxvt-unicode>)
2448		2293
2449	=item --with-terminfo=PATH	2294	=item --with-terminfo=PATH
2450		2295
2451	Change the environmental variable for the path to the terminfo tree to	2296	Change the environmental variable for the path to the terminfo tree to
2452	PATH.	2297	PATH.

Diff Legend

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