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.34 by root, Thu Feb 3 10:24:10 2005 UTC vs.
Revision 1.100 by root, Tue Jan 31 01:00:49 2006 UTC

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

Diff Legend

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