ViewVC Help

View File | Revision Log | Show Annotations | Download File

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

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.3 by root, Mon Jan 17 01:44:51 2005 UTC vs.
Revision 1.52 by root, Sat Jan 28 22:16:58 2006 UTC

…		…
11	<!-- INDEX BEGIN -->	11	<!-- INDEX BEGIN -->
12		12
13	<ul>	13	<ul>
14		14
15	<li><a href="#name">NAME</a></li>	15	<li><a href="#name">NAME</a></li>
16	<li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li>
17	<li><a href="#synopsis">SYNOPSIS</a></li>	16	<li><a href="#synopsis">SYNOPSIS</a></li>
18	<li><a href="#description">DESCRIPTION</a></li>	17	<li><a href="#description">DESCRIPTION</a></li>
		18	<li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li>
19	<li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li>	19	<li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li>
		20	<li><a href="#description">DESCRIPTION</a></li>
20	<li><a href="#definitions">Definitions</a></li>	21	<li><a href="#definitions">Definitions</a></li>
21	<li><a href="#values">Values</a></li>	22	<li><a href="#values">Values</a></li>
22	<li><a href="#escape_sequences">Escape Sequences</a></li>	23	<li><a href="#escape_sequences">Escape Sequences</a></li>
23	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>	24	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
24	<li><a href="#dec_private_modes">DEC Private Modes</a></li>	25	<li><a href="#dec_private_modes">DEC Private Modes</a></li>
25	<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>	26	<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>
26	<li><a href="#menubar">menuBar</a></li>
27	<ul>
28
29	<li><a href="#overview_of_menubar_operation">Overview of menuBar operation</a></li>
30	<li><a href="#commands">Commands</a></li>
31	<li><a href="#adding_and_accessing_menus">Adding and accessing menus</a></li>
32	<li><a href="#removing_menus">Removing menus</a></li>
33	<li><a href="#quick_arrows">Quick Arrows</a></li>
34	<li><a href="#command_summary">Command Summary</a></li>
35	</ul>
36
37	<li><a href="#xpm">XPM</a></li>	27	<li><a href="#xpm">XPM</a></li>
38	<li><a href="#mouse_reporting">Mouse Reporting</a></li>	28	<li><a href="#mouse_reporting">Mouse Reporting</a></li>
39	<li><a href="#key_codes">Key Codes</a></li>	29	<li><a href="#key_codes">Key Codes</a></li>
40	<li><a href="#configure_options">CONFIGURE OPTIONS</a></li>	30	<li><a href="#configure_options">CONFIGURE OPTIONS</a></li>
41	<li><a href="#authors">AUTHORS</a></li>	31	<li><a href="#authors">AUTHORS</a></li>
…		…
48	<h1><a name="name">NAME</a></h1>	38	<h1><a name="name">NAME</a></h1>
49	<p>RXVT REFERENCE - FAQ, command sequences and other background information</p>	39	<p>RXVT REFERENCE - FAQ, command sequences and other background information</p>
50	<p>	40	<p>
51	</p>	41	</p>
52	<hr />	42	<hr />
		43	<h1><a name="synopsis">SYNOPSIS</a></h1>
		44	<pre>
		45	# set a new font set
		46	printf '\33]50;%s\007' 9x15,xft:Kochi&quot; Mincho&quot;</pre>
		47	<pre>
		48	# change the locale and tell rxvt-unicode about it
		49	export LC_CTYPE=ja_JP.EUC-JP; printf &quot;\33]701;$LC_CTYPE\007&quot;</pre>
		50	<pre>
		51	# set window title
		52	printf '\33]2;%s\007' &quot;new window title&quot;</pre>
		53	<p>
		54	</p>
		55	<hr />
		56	<h1><a name="description">DESCRIPTION</a></h1>
		57	<p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
		58	all escape sequences, and other background information.</p>
		59	<p>The newest version of this document is
		60	also available on the World Wide Web at
		61	<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
		62	<p>
		63	</p>
		64	<hr />
53	<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>	65	<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
54	<dl>	66	<dl>
		67	<dt><strong><a name="item_the_new_selection_selects_pieces_that_are_too_big_">The new selection selects pieces that are too big, how can I select
		68	single words?</a></strong><br />
		69	</dt>
		70	<dd>
		71	Yes. For example, if you want to select alphanumeric words, you can use
		72	the following resource:
		73	</dd>
		74	<dd>
		75	<pre>
		76	URxvt.selection.pattern-0: ([[:word:]]+)</pre>
		77	</dd>
		78	<dd>
		79	<p>If you click more than twice, the selection will be extended
		80	more and more.</p>
		81	</dd>
		82	<dd>
		83	<p>To get a selection that is very similar to the old code, try this pattern:</p>
		84	</dd>
		85	<dd>
		86	<pre>
		87	URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>
		88	</dd>
		89	<dd>
		90	<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also
		91	selects words like the old code.</p>
		92	</dd>
		93	<p></p>
		94	<dt><strong><a name="item_i_don_27t_like_the_new_selection_2fpopups_2fhotkey">I don't like the new selection/popups/hotkeys/perl, how do I
		95	change/disable it?</a></strong><br />
		96	</dt>
		97	<dd>
		98	You can disable the perl extension completely by setting the
		99	<strong>perl-ext-common</strong> resource to the empty string, which also keeps
		100	rxvt-unicode from initialising perl, saving memory.
		101	</dd>
		102	<dd>
		103	<p>If you only want to disable specific features, you first have to
		104	identify which perl extension is responsible. For this, read the section
		105	<strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For
		106	example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify
		107	this <strong>perl-ext-common</strong> resource:</p>
		108	</dd>
		109	<dd>
		110	<pre>
		111	URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>
		112	</dd>
		113	<dd>
		114	<p>This will keep the default extensions, but disable the two popup
		115	extensions. Some extensions can also be configured, for example,
		116	scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any
		117	other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>
		118	</dd>
		119	<dd>
		120	<pre>
		121	URxvt.searchable-scrollback: CM-s</pre>
		122	</dd>
		123	<p></p>
		124	<dt><strong><a name="item_isn_27t_rxvt_supposed_to_be_small_3f_don_27t_all_t">Isn't rxvt supposed to be small? Don't all those features bloat?</a></strong><br />
		125	</dt>
		126	<dd>
		127	I often get asked about this, and I think, no, they didn't cause extra
		128	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
		129	that the urxvt binary is larger (due to some encoding tables always being
		130	compiled in), but it actually uses less memory (RSS) after startup. Even
		131	with <code>--disable-everything</code>, this comparison is a bit unfair, as many
		132	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		133	already in use in this mode.
		134	</dd>
		135	<dd>
		136	<pre>
		137	text data bss drs rss filename
		138	98398 1664 24 15695 1824 rxvt --disable-everything
		139	188985 9048 66616 18222 1788 urxvt --disable-everything</pre>
		140	</dd>
		141	<dd>
		142	<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft
		143	and full locale/XIM support which are quite bloaty inside libX11 and my
		144	libc), the two diverge, but not unreasnobaly so.</p>
		145	</dd>
		146	<dd>
		147	<pre>
		148	text data bss drs rss filename
		149	163431 2152 24 20123 2060 rxvt --enable-everything
		150	1035683 49680 66648 29096 3680 urxvt --enable-everything</pre>
		151	</dd>
		152	<dd>
		153	<p>The very large size of the text section is explained by the east-asian
		154	encoding tables, which, if unused, take up disk space but nothing else
		155	and can be compiled out unless you rely on X11 core fonts that use those
		156	encodings. The BSS size comes from the 64k emergency buffer that my c++
		157	compiler allocates (but of course doesn't use unless you are out of
		158	memory). Also, using an xft font instead of a core font immediately adds a
		159	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
		160	not used.</p>
		161	</dd>
		162	<dd>
		163	<p>Of course, due to every character using two or four bytes instead of one,
		164	a large scrollback buffer will ultimately make rxvt-unicode use more
		165	memory.</p>
		166	</dd>
		167	<dd>
		168	<p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
		169	still fares rather well. And compared to some monsters like gnome-terminal
		170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
		171	43180k in daemons that stay around after exit, plus half a minute of
		172	startup time, including the hundreds of warnings it spits out), it fares
		173	extremely well *g*.</p>
		174	</dd>
		175	<p></p>
		176	<dt><strong><a name="item_why_c_2b_2b_2c_isn_27t_that_unportable_2fbloated_2">Why C++, isn't that unportable/bloated/uncool?</a></strong><br />
		177	</dt>
		178	<dd>
		179	Is this a question? :) It comes up very often. The simple answer is: I had
		180	to write it, and C++ allowed me to write and maintain it in a fraction
		181	of the time and effort (which is a scarce resource for me). Put even
		182	shorter: It simply wouldn't exist without C++.
		183	</dd>
		184	<dd>
		185	<p>My personal stance on this is that C++ is less portable than C, but in
		186	the case of rxvt-unicode this hardly matters, as its portability limits
		187	are defined by things like X11, pseudo terminals, locale support and unix
		188	domain sockets, which are all less portable than C++ itself.</p>
		189	</dd>
		190	<dd>
		191	<p>Regarding the bloat, see the above question: It's easy to write programs
		192	in C that use gobs of memory, an certainly possible to write programs in
		193	C++ that don't. C++ also often comes with large libraries, but this is
		194	not necessarily the case with GCC. Here is what rxvt links against on my
		195	system with a minimal config:</p>
		196	</dd>
		197	<dd>
		198	<pre>
		199	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		200	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)
		201	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)
		202	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
		203	</dd>
		204	<dd>
		205	<p>And here is rxvt-unicode:</p>
		206	</dd>
		207	<dd>
		208	<pre>
		209	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		210	libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		211	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)
		212	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)
		213	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
		214	</dd>
		215	<dd>
		216	<p>No large bloated libraries (of course, none were linked in statically),
		217	except maybe libX11 :)</p>
		218	</dd>
		219	<p></p>
		220	<dt><strong><a name="item_does_it_support_tabs_2c_can_i_have_a_tabbed_rxvt_2">Does it support tabs, can I have a tabbed rxvt-unicode?</a></strong><br />
		221	</dt>
		222	<dd>
		223	Beginning with version 7.3, there is a perl extension that implements a
		224	simple tabbed terminal. It is installed by default, so any of these should
		225	give you tabs:
		226	</dd>
		227	<dd>
		228	<pre>
		229	rxvt -pe tabbed</pre>
		230	</dd>
		231	<dd>
		232	<pre>
		233	URxvt.perl-ext-common: default,tabbed</pre>
		234	</dd>
		235	<dd>
		236	<p>It will also work fine with tabbing functionality of many window managers
		237	or similar tabbing programs, and its embedding-features allow it to be
		238	embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or
		239	the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt
		240	(murxvt) terminal as an example embedding application.</p>
		241	</dd>
		242	<p></p>
55	<dt><strong><a name="item_how_do_i_know_which_rxvt_2dunicode_version_i_27m_u">How do I know which rxvt-unicode version I'm using?</a></strong><br />	243	<dt><strong><a name="item_how_do_i_know_which_rxvt_2dunicode_version_i_27m_u">How do I know which rxvt-unicode version I'm using?</a></strong><br />
56	</dt>	244	</dt>
57	<dd>	245	<dd>
58	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
59	sequence <code>ESC[8n</code> sets the window title to the version number.	247	sequence <code>ESC [ 8 n</code> sets the window title to the version number. When
		248	using the rxvtc client, the version displayed is that of the
		249	daemon.
		250	</dd>
		251	<p></p>
		252	<dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br />
		253	</dt>
		254	<dd>
		255	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		256	patches that considerably change the behaviour of rxvt-unicode (but
		257	unfortunately this notice has been removed). Before reporting a bug to
		258	the original rxvt-unicode author please download and install the genuine
		259	version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce
		260	the problem. If you cannot, chances are that the problems are specific to
		261	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		262	Tracking System (use <code>reportbug</code> to report the bug).
		263	</dd>
		264	<dd>
		265	<p>For other problems that also affect the Debian package, you can and
		266	probably should use the Debian BTS, too, because, after all, it's also a
		267	bug in the Debian version and it serves as a reminder for other users that
		268	might encounter the same issue.</p>
		269	</dd>
		270	<p></p>
		271	<dt><strong><a name="item_i_am_maintaining_rxvt_2dunicode_for_distribution_2">I am maintaining rxvt-unicode for distribution/OS XXX, any
		272	recommendation?</a></strong><br />
		273	</dt>
		274	<dd>
		275	You should build one binary with the default options. <em>configure</em>
		276	now enables most useful options, and the trend goes to making them
		277	runtime-switchable, too, so there is usually no drawback to enbaling them,
		278	except higher disk and possibly memory usage. The perl interpreter should
		279	be enabled, as important functionality (menus, selection, likely more in
		280	the future) depends on it.
		281	</dd>
		282	<dd>
		283	<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
		284	system-wide (except maybe with <code>defaults</code>). This will result in useful
		285	behaviour. If your distribution aims at low memory, add an empty
		286	<code>perl-ext-common</code> resource to the app-defaults file. This will keep the
		287	perl interpreter disabled until the user enables it.</p>
		288	</dd>
		289	<dd>
		290	<p>If you can/want build more binaries, I recommend building a minimal
		291	one with <code>--disable-everything</code> (very useful) and a maximal one with
		292	<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of
		293	encodings built-in that increase download times and are rarely used).</p>
		294	</dd>
		295	<p></p>
		296	<dt><strong><a name="item_i_need_to_make_it_setuid_2fsetgid_to_support_utmp_">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></strong><br />
		297	</dt>
		298	<dd>
		299	It should be, starting with release 7.1. You are encouraged to properly
		300	install urxvt with privileges necessary for your OS now.
		301	</dd>
		302	<dd>
		303	<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork
		304	into a helper process for privileged operations (pty handling on some
		305	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		306	immediately. This is much safer than most other terminals that keep
		307	privileges while running (but is more relevant to urxvt, as it contains
		308	things as perl interpreters, which might be ``helpful'' to attackers).</p>
		309	</dd>
		310	<dd>
		311	<p>This forking is done as the very first within main(), which is very early
		312	and reduces possible bugs to initialisation code run before main(), or
		313	things like the dynamic loader of your system, which should result in very
		314	little risk.</p>
60	</dd>	315	</dd>
61	<p></p>	316	<p></p>
62	<dt><strong><a name="item_when_i_log_2din_to_another_system_it_tells_me_abou">When I log-in to another system it tells me about missing terminfo data?</a></strong><br />	317	<dt><strong><a name="item_when_i_log_2din_to_another_system_it_tells_me_abou">When I log-in to another system it tells me about missing terminfo data?</a></strong><br />
63	</dt>	318	</dt>
64	<dd>	319	<dd>
…		…
83	problems arising, which includes wrong keymapping, less and different	338	problems arising, which includes wrong keymapping, less and different
84	colours and some refresh errors in fullscreen applications. It's a nice	339	colours and some refresh errors in fullscreen applications. It's a nice
85	quick-and-dirty workaround for rare cases, though.</p>	340	quick-and-dirty workaround for rare cases, though.</p>
86	</dd>	341	</dd>
87	<dd>	342	<dd>
88	<p>If you always want to do this you can either recompile rxvt-unicode with	343	<p>If you always want to do this (and are fine with the consequences) you
89	the desired TERM value or use a resource to set it:</p>	344	can either recompile rxvt-unicode with the desired TERM value or use a
		345	resource to set it:</p>
90	</dd>	346	</dd>
91	<dd>	347	<dd>
92	<pre>	348	<pre>
93	URxvt.termName: rxvt</pre>	349	URxvt.termName: rxvt</pre>
94	</dd>	350	</dd>
95	<dd>	351	<dd>
96	<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace	352	<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace
97	the rxvt terminfo file with the rxvt-unicode one.</p>	353	the rxvt terminfo file with the rxvt-unicode one.</p>
98	</dd>	354	</dd>
99	<p></p>	355	<p></p>
		356	<dt><strong><a name="item_tic_outputs_some_error_when_compiling_the_terminfo"><code>tic</code> outputs some error when compiling the terminfo entry.</a></strong><br />
		357	</dt>
		358	<dd>
		359	Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
		360	<code>enacs=\E[0@</code> and try again.
		361	</dd>
		362	<p></p>
		363	<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br />
		364	</dt>
100	<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />	365	<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />
101	</dt>	366	</dt>
102	<dd>	367	<dd>
		368	One reason you might want this is that some distributions or operating
		369	systems still compile some programs using the long-obsoleted termcap
		370	library (Fedora Core's bash is one example) and rely on a termcap entry
		371	for <code>rxvt-unicode</code>.
		372	</dd>
		373	<dd>
103	You could use rxvt's termcap entry with resonable results in many cases.	374	<p>You could use rxvt's termcap entry with resonable results in many cases.
104	You can also create a termcap entry by using terminfo's infocmp program	375	You can also create a termcap entry by using terminfo's infocmp program
105	like this:	376	like this:</p>
106	</dd>	377	</dd>
107	<dd>	378	<dd>
108	<pre>	379	<pre>
109	infocmp -C rxvt-unicode</pre>	380	infocmp -C rxvt-unicode</pre>
110	</dd>	381	</dd>
111	<dd>	382	<dd>
112	<p>OR you could this termcap entry:</p>	383	<p>Or you could use this termcap entry, generated by the command above:</p>
113	</dd>	384	</dd>
114	<dd>	385	<dd>
115	<pre>	386	<pre>
116	rxvt-unicode|rxvt-unicode terminal (X Window System):\	387	rxvt-unicode|rxvt-unicode terminal (X Window System):\
117	:am:bw:eo:km:mi:ms:xn:xo:\	388	:am:bw:eo:km:mi:ms:xn:xo:\
118	:co#80:it#8:li#24:\	389	:co#80:it#8:li#24:lm#0:\
119	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	390	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
120	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\	391	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
121	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\	392	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
122	:as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\	393	:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
123	:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\	394	:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
124	:ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\	395	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
		396	:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
125	:im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\	397	:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
126	:k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\	398	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
127	:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\	399	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
128	:kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\	400	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E&gt;:\
129	:ke=\E[?1l\E&gt;:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\	401	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
130	:ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\	402	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
131	:nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\	403	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
132	:st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\	404	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
133	:up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	405	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
134	:vs=\E[?25h:</pre>	406	:vs=\E[?25h:</pre>
135	</dd>	407	</dd>
136	<p></p>	408	<p></p>
137	<dt><strong><a name="item_why_does_ls_no_longer_have_coloured_output_3f">Why does <code>ls</code> no longer have coloured output?</a></strong><br />	409	<dt><strong><a name="item_why_does_ls_no_longer_have_coloured_output_3f">Why does <code>ls</code> no longer have coloured output?</a></strong><br />
138	</dt>	410	</dt>
…		…
172	file, so you will need to install it on your own (See the question <strong>When	444	file, so you will need to install it on your own (See the question <strong>When
173	I log-in to another system it tells me about missing terminfo data?</strong> on	445	I log-in to another system it tells me about missing terminfo data?</strong> on
174	how to do this).	446	how to do this).
175	</dd>	447	</dd>
176	<p></p>	448	<p></p>
		449	<dt><strong><a name="item_my_numerical_keypad_acts_weird_and_generates_diffe">My numerical keypad acts weird and generates differing output?</a></strong><br />
		450	</dt>
		451	<dd>
		452	Some Debian GNUL/Linux users seem to have this problem, although no
		453	specific details were reported so far. It is possible that this is caused
		454	by the wrong <code>TERM</code> setting, although the details of wether and how
		455	this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
		456	keymap. See the answer to the previous question, and please report if that
		457	helped.
		458	</dd>
		459	<p></p>
177	<dt><strong><a name="item_rxvt_2dunicode_does_not_seem_to_understand_the_sel">Rxvt-unicode does not seem to understand the selected encoding?</a></strong><br />	460	<dt><strong><a name="item_rxvt_2dunicode_does_not_seem_to_understand_the_sel">Rxvt-unicode does not seem to understand the selected encoding?</a></strong><br />
178	</dt>	461	</dt>
179	<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br />	462	<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br />
180	</dt>	463	</dt>
181	<dd>	464	<dd>
…		…
185	</dd>	468	</dd>
186	<dd>	469	<dd>
187	<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the	470	<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the
188	programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the	471	programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the
189	login script running within the rxvt-unicode window changes the locale to	472	login script running within the rxvt-unicode window changes the locale to
190	sth. else, e.h. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>	473	something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>
191	</dd>	474	</dd>
192	<dd>	475	<dd>
193	<p>The best thing is to fix your startup environment, as you will likely run	476	<p>The best thing is to fix your startup environment, as you will likely run
194	into other problems. If nothing works you can try this in your .profile.</p>	477	into other problems. If nothing works you can try this in your .profile.</p>
195	</dd>	478	</dd>
…		…
198	printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre>	481	printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre>
199	</dd>	482	</dd>
200	<dd>	483	<dd>
201	<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not	484	<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not
202	supported on your systems. Some systems have a <code>locale</code> command which	485	supported on your systems. Some systems have a <code>locale</code> command which
203	displays this. If it displays sth. like:</p>	486	displays this (also, <code>perl -e0</code> can be used to check locale settings, as
		487	it will complain loudly if it cannot set the locale). If it displays something
		488	like:</p>
204	</dd>	489	</dd>
205	<dd>	490	<dd>
206	<pre>	491	<pre>
207	locale: Cannot set LC_CTYPE to default locale: ...</pre>	492	locale: Cannot set LC_CTYPE to default locale: ...</pre>
208	</dd>	493	</dd>
…		…
226	to display.	511	to display.
227	</dd>	512	</dd>
228	<dd>	513	<dd>
229	<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement	514	<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement
230	font. Often the result is fine, but sometimes the chosen font looks	515	font. Often the result is fine, but sometimes the chosen font looks
231	bad. Many fonts have totally strange characters that don't resemble the	516	bad/ugly/wrong. Some fonts have totally strange characters that don't
232	correct glyph at all, and rxvt-unicode lacks the artificial intelligence	517	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
233	to detect that a specific glyph is wrong: it has to believe the font that	518	intelligence to detect that a specific glyph is wrong: it has to believe
234	the characters it contains indeed look correct.</p>	519	the font that the characters it claims to contain indeed look correct.</p>
235	</dd>	520	</dd>
236	<dd>	521	<dd>
237	<p>In that case, select a font of your taste and add it to the font list,	522	<p>In that case, select a font of your taste and add it to the font list,
238	e.g.:</p>	523	e.g.:</p>
239	</dd>	524	</dd>
…		…
246	font. If the base font does not contain the character, it will go to the	531	font. If the base font does not contain the character, it will go to the
247	next font, and so on. Specifying your own fonts will also speed up this	532	next font, and so on. Specifying your own fonts will also speed up this
248	search and use less resources within rxvt-unicode and the X-server.</p>	533	search and use less resources within rxvt-unicode and the X-server.</p>
249	</dd>	534	</dd>
250	<dd>	535	<dd>
251	<p>The only limitation is that all the fonts must not be larger than the base	536	<p>The only limitation is that none of the fonts may be larger than the base
252	font, as the base font defines the principal cell size, which must be the	537	font, as the base font defines the terminal character cell size, which
253	same due to the way terminals work.</p>	538	must be the same due to the way terminals work.</p>
254	</dd>	539	</dd>
255	<p></p>	540	<p></p>
256	<dt><strong><a name="item_why_do_some_chinese_characters_look_so_different_t">Why do some chinese characters look so different than others?</a></strong><br />	541	<dt><strong><a name="item_why_do_some_chinese_characters_look_so_different_t">Why do some chinese characters look so different than others?</a></strong><br />
257	</dt>	542	</dt>
258	<dd>	543	<dd>
259	This is because there is a difference between script and language --	544	This is because there is a difference between script and language --
260	rxvt-unicode does not know which language the text that is output	545	rxvt-unicode does not know which language the text that is output is,
261	is, as it only knows the unicode character codes. If rxvt-unicode	546	as it only knows the unicode character codes. If rxvt-unicode first
262	first sees a japanese character, it might choose a japanese font for	547	sees a japanese/chinese character, it might choose a japanese font for
263	it. Subsequent japanese characters will take that font. Now, many chinese	548	display. Subsequent japanese characters will use that font. Now, many
264	characters aren't represented in japanese fonts, so when the first	549	chinese characters aren't represented in japanese fonts, so when the first
265	non-japanese character comes up, rxvt-unicode will look for a chinese font	550	non-japanese character comes up, rxvt-unicode will look for a chinese font
266	-- unfortunately at this point, it will still use the japanese font for	551	-- unfortunately at this point, it will still use the japanese font for
267	japanese characters that are also chinese.	552	chinese characters that are also in the japanese font.
268	</dd>	553	</dd>
269	<dd>	554	<dd>
270	<p>The workaround is easy: just tag a chinese font at the end of your font	555	<p>The workaround is easy: just tag a chinese font at the end of your font
271	list (see the previous question). The key is to view the font list as	556	list (see the previous question). The key is to view the font list as
272	a preference list: If you expect more japanese, list a japanese font	557	a preference list: If you expect more japanese, list a japanese font
273	first. If you expect more chinese, put a chinese font first.</p>	558	first. If you expect more chinese, put a chinese font first.</p>
274	</dd>	559	</dd>
275	<dd>	560	<dd>
276	<p>In the future it might be possible to switch preferences at runtime (the	561	<p>In the future it might be possible to switch language preferences at
277	internal data structure has no problem with using different fonts for	562	runtime (the internal data structure has no problem with using different
278	the same character at the same time, but no interface for this has been	563	fonts for the same character at the same time, but no interface for this
279	designed yet).</p>	564	has been designed yet).</p>
		565	</dd>
		566	<dd>
		567	<p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p>
280	</dd>	568	</dd>
281	<p></p>	569	<p></p>
282	<dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br />	570	<dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br />
283	</dt>	571	</dt>
284	<dd>	572	<dd>
…		…
302	might be forced to use a different font.</p>	590	might be forced to use a different font.</p>
303	</dd>	591	</dd>
304	<dd>	592	<dd>
305	<p>All of this is not a problem when using X11 core fonts, as their bounding	593	<p>All of this is not a problem when using X11 core fonts, as their bounding
306	box data is correct.</p>	594	box data is correct.</p>
		595	</dd>
		596	<p></p>
		597	<dt><strong><a name="item_on_solaris_9_2c_many_line_2ddrawing_characters_are">On Solaris 9, many line-drawing characters are too wide.</a></strong><br />
		598	</dt>
		599	<dd>
		600	Seems to be a known bug, read
		601	<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the
		602	following ugly workaround to get non-double-wide-characters working:
		603	</dd>
		604	<dd>
		605	<pre>
		606	#define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>
307	</dd>	607	</dd>
308	<p></p>	608	<p></p>
309	<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br />	609	<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br />
310	</dt>	610	</dt>
311	<dd>	611	<dd>
…		…
332	</dd>	632	</dd>
333	<p></p>	633	<p></p>
334	<dt><strong><a name="item_how_can_i_keep_rxvt_2dunicode_from_using_reverse_v">How can I keep rxvt-unicode from using reverse video so much?</a></strong><br />	634	<dt><strong><a name="item_how_can_i_keep_rxvt_2dunicode_from_using_reverse_v">How can I keep rxvt-unicode from using reverse video so much?</a></strong><br />
335	</dt>	635	</dt>
336	<dd>	636	<dd>
337	First of all, make sure you are running with the right terminfo	637	First of all, make sure you are running with the right terminal settings
338	(<code>urxvt</code>), which will get rid of most of these effects. Then make sure	638	(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
339	you have specified colours for italic and bold, as otherwise rxvt-unicode	639	make sure you have specified colours for italic and bold, as otherwise
340	might use reverse video to simulate the effect:	640	rxvt-unicode might use reverse video to simulate the effect:
341	</dd>
342	<dd>	641	</dd>
		642	<dd>
343	<pre>	643	<pre>
344	URxvt*colorBD: white	644	URxvt.colorBD: white
345	URxvt*colorIT: green</pre>	645	URxvt.colorIT: green</pre>
346	</dd>	646	</dd>
347	<p></p>	647	<p></p>
348	<dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br />	648	<dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br />
349	</dt>	649	</dt>
350	<dd>	650	<dd>
351	For some unexplainable reason, some programs (i.e. irssi) assume a very	651	For some unexplainable reason, some rare programs assume a very weird
352	weird colour palette when confronted with a terminal with more than the	652	colour palette when confronted with a terminal with more than the standard
353	standard 8 colours (rxvt-unicode supports 88). The right fix is, of	653	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
354	course, to fix these programs not to assume non-ISO colours without very	654	these programs not to assume non-ISO colours without very good reasons.
355	good reasons.
356	</dd>
357	<dd>	655	</dd>
		656	<dd>
358	<p>In the meantime, you can either edit your <code>urxvt</code> terminfo definition to	657	<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
359	only claim 8 colour support or use <code>TERM=rxvt</code>, which will fix colours	658	definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
360	but keep you from using other rxvt-unicode features.</p>	659	fix colours but keep you from using other rxvt-unicode features.</p>
361	</dd>	660	</dd>
362	<p></p>	661	<p></p>
363	<dt><strong><a name="item_i_am_on_freebsd_and_rxvt_2dunicode_does_not_seem_t">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></strong><br />	662	<dt><strong><a name="item_i_am_on_freebsd_and_rxvt_2dunicode_does_not_seem_t">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></strong><br />
364	</dt>	663	</dt>
365	<dd>	664	<dd>
…		…
369	<strong>wchar_t</strong> is represented as unicode.	668	<strong>wchar_t</strong> is represented as unicode.
370	</dd>	669	</dd>
371	<dd>	670	<dd>
372	<p>As you might have guessed, FreeBSD does neither define this symobl nor	671	<p>As you might have guessed, FreeBSD does neither define this symobl nor
373	does it support it. Instead, it uses it's own internal representation of	672	does it support it. Instead, it uses it's own internal representation of
374	<strong>wchar_t</strong>. This is, of course, completely legal.</p>	673	<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
375	</dd>
376	<dd>	674	</dd>
		675	<dd>
		676	<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
		677	<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
		678	</dd>
		679	<dd>
377	<p>However, <code>__STDC_ISO_10646__</code> is the only sane way to support	680	<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
378	multi-language apps in an OS, as using a locale-dependent (and	681	apps in an OS, as using a locale-dependent (and non-standardized)
379	non-standardized) representation of <strong>wchar_t</strong> makes it impossible to	682	representation of <strong>wchar_t</strong> makes it impossible to convert between
380	convert between <strong>wchar_t</strong> (as used by X11 and your applications) and any	683	<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding
381	other encoding without implementing OS-specific-wrappers for each and	684	without implementing OS-specific-wrappers for each and every locale. There
382	every locale. There simply are no APIs to convert <strong>wchar_t</strong> into anything	685	simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
383	except the current locale encoding.</p>	686	locale encoding.</p>
384	</dd>	687	</dd>
385	<dd>	688	<dd>
386	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this	689	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
387	by carrying their own replacement functions for character set handling	690	by carrying their own replacement functions for character set handling
388	with them, and either implementing OS-dependent hacks or doing multiple	691	with them, and either implementing OS-dependent hacks or doing multiple
…		…
390	encodings slightly different than the terminal emulator).</p>	693	encodings slightly different than the terminal emulator).</p>
391	</dd>	694	</dd>
392	<dd>	695	<dd>
393	<p>The rxvt-unicode author insists that the right way to fix this is in the	696	<p>The rxvt-unicode author insists that the right way to fix this is in the
394	system libraries once and for all, instead of forcing every app to carry	697	system libraries once and for all, instead of forcing every app to carry
395	complete replacements.</p>	698	complete replacements for them :)</p>
		699	</dd>
		700	<p></p>
		701	<dt><strong><a name="item_i_use_solaris_9_and_it_doesn_27t_compile_2fwork_2f">I use Solaris 9 and it doesn't compile/work/etc.</a></strong><br />
		702	</dt>
		703	<dd>
		704	Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
		705	problems with <code>wcwidth</code> and a compile problem.
		706	</dd>
		707	<p></p>
		708	<dt><strong><a name="item_how_can_i_use_rxvt_2dunicode_under_cygwin_3f">How can I use rxvt-unicode under cygwin?</a></strong><br />
		709	</dt>
		710	<dd>
		711	rxvt-unicode should compile and run out of the box on cygwin, using
		712	the X11 libraries that come with cygwin. libW11 emulation is no
		713	longer supported (and makes no sense, either, as it only supported a
		714	single font). I recommend starting the X-server in <code>-multiwindow</code> or
		715	<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
		716	old libW11 emulation.
		717	</dd>
		718	<dd>
		719	<p>At the time of this writing, cygwin didn't seem to support any multi-byte
		720	encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
		721	to 8-bit encodings.</p>
396	</dd>	722	</dd>
397	<p></p>	723	<p></p>
398	<dt><strong><a name="item_how_does_rxvt_2dunicode_determine_the_encoding_to_">How does rxvt-unicode determine the encoding to use?</a></strong><br />	724	<dt><strong><a name="item_how_does_rxvt_2dunicode_determine_the_encoding_to_">How does rxvt-unicode determine the encoding to use?</a></strong><br />
399	</dt>	725	</dt>
400	<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />	726	<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />
…		…
405	UTF-8 or any other encodings with respect to terminal I/O.	731	UTF-8 or any other encodings with respect to terminal I/O.
406	</dd>	732	</dd>
407	<dd>	733	<dd>
408	<p>The reasons is that there exists a perfectly fine mechanism for selecting	734	<p>The reasons is that there exists a perfectly fine mechanism for selecting
409	the encoding, doing I/O and (most important) communicating this to all	735	the encoding, doing I/O and (most important) communicating this to all
410	applications so everybody agrees on character properties such as width and	736	applications so everybody agrees on character properties such as width
411	code number. This mechanism is the <em>locale</em>.</p>	737	and code number. This mechanism is the <em>locale</em>. Applications not using
		738	that info will have problems (for example, <code>xterm</code> gets the width of
		739	characters wrong as it uses it's own, locale-independent table under all
		740	locales).</p>
412	</dd>	741	</dd>
413	<dd>	742	<dd>
414	<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All	743	<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
415	programs doing the same (that is, most) will automatically agree in the	744	programs doing the same (that is, most) will automatically agree in the
416	interpretation of characters.</p>	745	interpretation of characters.</p>
…		…
427	(i.e. <code>de</code> or <code>german</code>) are also common.</p>	756	(i.e. <code>de</code> or <code>german</code>) are also common.</p>
428	</dd>	757	</dd>
429	<dd>	758	<dd>
430	<p>Rxvt-unicode ignores all other locale categories, and except for	759	<p>Rxvt-unicode ignores all other locale categories, and except for
431	the encoding, ignores country or language-specific settings,	760	the encoding, ignores country or language-specific settings,
432	i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the same for rxvt-unicode.</p>	761	i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
		762	rxvt-unicode.</p>
433	</dd>	763	</dd>
434	<dd>	764	<dd>
435	<p>If you want to use a specific encoding you have to make sure you start	765	<p>If you want to use a specific encoding you have to make sure you start
436	rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>	766	rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
437	</dd>	767	</dd>
438	<p></p>	768	<p></p>
439	<dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br />	769	<dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br />
440	</dt>	770	</dt>
441	<dd>	771	<dd>
442	Yes, using an escape sequence. Try sth. like this, which sets	772	Yes, using an escape sequence. Try something like this, which sets
443	rxvt-unicode's idea of <code>LC_CTYPE</code>.	773	rxvt-unicode's idea of <code>LC_CTYPE</code>.
444	</dd>	774	</dd>
445	<dd>	775	<dd>
446	<pre>	776	<pre>
447	printf '\e]701;%s\007' ja_JP.SJIS</pre>	777	printf '\e]701;%s\007' ja_JP.SJIS</pre>
448	</dd>	778	</dd>
449	<dd>	779	<dd>
450	<p>See also the previous question.</p>	780	<p>See also the previous answer.</p>
451	</dd>
452	<dd>	781	</dd>
		782	<dd>
453	<p>Sometimes this capability is rather handy when you want to work in one	783	<p>Sometimes this capability is rather handy when you want to work in
454	locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support UTF-8. For	784	one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
455	example, I use this script to start <code>xjdic</code>, which first switches to a	785	(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
456	locale supported by xjdic and back later:</p>	786	first switches to a locale supported by xjdic and back later:</p>
457	</dd>	787	</dd>
458	<dd>	788	<dd>
459	<pre>	789	<pre>
460	printf '\e]701;%s\007' ja_JP.SJIS	790	printf '\e]701;%s\007' ja_JP.SJIS
461	xjdic -js	791	xjdic -js
462	printf '\e]701;%s\007' de_DE.UTF-8</pre>	792	printf '\e]701;%s\007' de_DE.UTF-8</pre>
463	</dd>	793	</dd>
		794	<dd>
		795	<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
		796	for some locales where character width differs between program- and
		797	rxvt-unicode-locales.</p>
		798	</dd>
464	<p></p>	799	<p></p>
465	<dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br />	800	<dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br />
466	</dt>	801	</dt>
467	<dd>	802	<dd>
468	Yes, using an escape sequence. Try sth. like this, which has the same	803	Yes, using an escape sequence. Try something like this, which has the same
469	effect as using the <code>-fn</code> switch, and takes effect immediately:	804	effect as using the <code>-fn</code> switch, and takes effect immediately:
470	</dd>	805	</dd>
471	<dd>	806	<dd>
472	<pre>	807	<pre>
473	printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>	808	printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
…		…
484	<dt><strong><a name="item_why_do_italic_characters_look_as_if_clipped_3f">Why do italic characters look as if clipped?</a></strong><br />	819	<dt><strong><a name="item_why_do_italic_characters_look_as_if_clipped_3f">Why do italic characters look as if clipped?</a></strong><br />
485	</dt>	820	</dt>
486	<dd>	821	<dd>
487	Many fonts have difficulties with italic characters and hinting. For	822	Many fonts have difficulties with italic characters and hinting. For
488	example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans	823	example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
489	Mono</code> completely fails in it's italic face. A workaround is to enable	824	Mono</code> completely fails in it's italic face. A workaround might be to
490	freetype autohinting, i.e. like this:	825	enable freetype autohinting, i.e. like this:
491	</dd>
492	<dd>	826	</dd>
		827	<dd>
493	<pre>	828	<pre>
494	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	829	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
495	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>	830	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
496	</dd>	831	</dd>
497	<p></p>	832	<p></p>
498	<dt><strong><a name="item_my_input_method_wants__3csome_encoding_3e_but_i_wa">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></strong><br />	833	<dt><strong><a name="item_my_input_method_wants__3csome_encoding_3e_but_i_wa">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></strong><br />
499	</dt>	834	</dt>
500	<dd>	835	<dd>
501	You can specify separate locales for the input method and the rest of the	836	You can specify separate locales for the input method and the rest of the
502	terminal, using the resource <code>imlocale</code>:	837	terminal, using the resource <code>imlocale</code>:
503	</dd>	838	</dd>
504	<dd>	839	<dd>
505	<pre>	840	<pre>
506	URxvt*imlocale: ja_JP.EUC-JP</pre>	841	URxvt.imlocale: ja_JP.EUC-JP</pre>
507	</dd>	842	</dd>
508	<dd>	843	<dd>
509	<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still	844	<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
510	use your input method. Please note, however, that you will not be able to	845	use your input method. Please note, however, that you will not be able to
511	input characters outside <code>EUC-JP</code> in a normal way then, as your input	846	input characters outside <code>EUC-JP</code> in a normal way then, as your input
512	method limits you.</p>	847	method limits you.</p>
513	</dd>	848	</dd>
514	<p></p>	849	<p></p>
		850	<dt><strong><a name="item_rxvt_2dunicode_crashes_when_the_x_input_method_cha">Rxvt-unicode crashes when the X Input Method changes or exits.</a></strong><br />
		851	</dt>
		852	<dd>
		853	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		854	design. Applications can avoid some crashes at the expense of memory
		855	leaks, and Input Methods can avoid some crashes by careful ordering at
		856	exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
		857	while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
		858	crashes cannot be completely avoided even if both sides cooperate.
		859	</dd>
		860	<dd>
		861	<p>So the only workaround is not to kill your Input Method Servers.</p>
		862	</dd>
		863	<p></p>
515	<dt><strong><a name="item_rxvt_2dunicode_uses_gobs_of_memory_2c_how_can_i_re">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></strong><br />	864	<dt><strong><a name="item_rxvt_2dunicode_uses_gobs_of_memory_2c_how_can_i_re">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></strong><br />
516	</dt>	865	</dt>
517	<dd>	866	<dd>
518	Rxvt-unicode tries to obey the rule of not charging you for sth. you	867	Rxvt-unicode tries to obey the rule of not charging you for something you
519	don't use. One thing you should try is to configure out all settings that	868	don't use. One thing you should try is to configure out all settings that
520	you don't need, for example, Xft support is a resource hog by design,	869	you don't need, for example, Xft support is a resource hog by design,
521	when used. Compiling it out ensures that no Xft font will be loaded	870	when used. Compiling it out ensures that no Xft font will be loaded
522	accidentally when rxvt-unicode tries to find a font for your characters.	871	accidentally when rxvt-unicode tries to find a font for your characters.
523	</dd>	872	</dd>
524	<dd>	873	<dd>
525	<p>Also, many people (me included) like large windows and even larger	874	<p>Also, many people (me included) like large windows and even larger
526	scrollback buffers: Without <a href="#item__2d_2denable_2dunicode3"><code>--enable-unicode3</code></a>, rxvt-unicode will use	875	scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use
527	6 bytes per screen cell. For a 160x?? window this amounts to almost a	876	6 bytes per screen cell. For a 160x?? window this amounts to almost a
528	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)	877	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
529	use 10 Megabytes of memory. With <a href="#item__2d_2denable_2dunicode3"><code>--enable-unicode3</code></a> it gets worse, as	878	use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as
530	rxvt-unicode then uses 8 bytes per screen cell.</p>	879	rxvt-unicode then uses 8 bytes per screen cell.</p>
531	</dd>	880	</dd>
532	<p></p>	881	<p></p>
533	<dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br />	882	<dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br />
534	</dt>	883	</dt>
535	<dd>	884	<dd>
536	Yes, the most obvious way to speed it up is to avoid Xft entirely, as	885	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
537	it is simply slow. If you still want Xft fonts you might try to disable	886	it is simply slow. If you still want Xft fonts you might try to disable
538	antialiasing (by appending <code>:antialiasing=false</code>), which saves lots of	887	antialiasing (by appending <code>:antialias=false</code>), which saves lots of
539	memory and also speeds up rendering considerably.	888	memory and also speeds up rendering considerably.
540	</dd>	889	</dd>
541	<p></p>	890	<p></p>
542	<dt><strong><a name="item_rxvt_2dunicode_doesn_27t_seem_to_anti_2dalias_its_">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></strong><br />	891	<dt><strong><a name="item_rxvt_2dunicode_doesn_27t_seem_to_anti_2dalias_its_">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></strong><br />
543	</dt>	892	</dt>
…		…
557	<dd>	906	<dd>
558	Make sure that mouse reporting is actually turned off since killing	907	Make sure that mouse reporting is actually turned off since killing
559	some editors prematurely may leave the mouse in mouse report mode. I've	908	some editors prematurely may leave the mouse in mouse report mode. I've
560	heard that tcsh may use mouse reporting unless it otherwise specified. A	909	heard that tcsh may use mouse reporting unless it otherwise specified. A
561	quick check is to see if cut/paste works when the Alt or Shift keys are	910	quick check is to see if cut/paste works when the Alt or Shift keys are
562	depressed. See <code>rxvt(7)</code>	911	depressed.
563	</dd>	912	</dd>
564	<p></p>	913	<p></p>
565	<dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br />	914	<dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br />
566	</dt>	915	</dt>
567	<dd>	916	<dd>
…		…
595	<p>Here are values that are supposed to resemble a VGA screen,	944	<p>Here are values that are supposed to resemble a VGA screen,
596	including the murky brown that passes for low-intensity yellow:</p>	945	including the murky brown that passes for low-intensity yellow:</p>
597	</dd>	946	</dd>
598	<dd>	947	<dd>
599	<pre>	948	<pre>
600	URxvt*color0: #000000	949	URxvt.color0: #000000
601	URxvt*color1: #A80000	950	URxvt.color1: #A80000
602	URxvt*color2: #00A800	951	URxvt.color2: #00A800
603	URxvt*color3: #A8A800	952	URxvt.color3: #A8A800
604	URxvt*color4: #0000A8	953	URxvt.color4: #0000A8
605	URxvt*color5: #A800A8	954	URxvt.color5: #A800A8
606	URxvt*color6: #00A8A8	955	URxvt.color6: #00A8A8
607	URxvt*color7: #A8A8A8</pre>	956	URxvt.color7: #A8A8A8</pre>
608	</dd>
609	<dd>	957	</dd>
		958	<dd>
610	<pre>	959	<pre>
611	URxvt*color8: #000054	960	URxvt.color8: #000054
612	URxvt*color9: #FF0054	961	URxvt.color9: #FF0054
613	URxvt*color10: #00FF54	962	URxvt.color10: #00FF54
614	URxvt*color11: #FFFF54	963	URxvt.color11: #FFFF54
615	URxvt*color12: #0000FF	964	URxvt.color12: #0000FF
616	URxvt*color13: #FF00FF	965	URxvt.color13: #FF00FF
617	URxvt*color14: #00FFFF	966	URxvt.color14: #00FFFF
618	URxvt*color15: #FFFFFF</pre>	967	URxvt.color15: #FFFFFF</pre>
619	</dd>
620	<dd>	968	</dd>
		969	<dd>
621	<p>And here is a more complete set of non-standard colors described as	970	<p>And here is a more complete set of non-standard colors described (not by
622	``pretty girly'':</p>	971	me) as ``pretty girly''.</p>
623	</dd>	972	</dd>
624	<dd>	973	<dd>
625	<pre>	974	<pre>
626	URxvt.cursorColor: #dc74d1	975	URxvt.cursorColor: #dc74d1
627	URxvt.pointerColor: #dc74d1	976	URxvt.pointerColor: #dc74d1
…		…
641	URxvt.color14: #73f7ff	990	URxvt.color14: #73f7ff
642	URxvt.color7: #e1dddd	991	URxvt.color7: #e1dddd
643	URxvt.color15: #e1dddd</pre>	992	URxvt.color15: #e1dddd</pre>
644	</dd>	993	</dd>
645	<p></p>	994	<p></p>
		995	<dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br />
		996	</dt>
		997	<dd>
		998	Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
		999	display, create the listening socket and then fork.
		1000	</dd>
		1001	<p></p>
646	<dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br />	1002	<dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br />
647	</dt>	1003	</dt>
648	<dd>	1004	<dd>
649	Assuming that the physical Backspace key corresponds to the	1005	Assuming that the physical Backspace key corresponds to the
650	BackSpace keysym (not likely for Linux ... see the following	1006	BackSpace keysym (not likely for Linux ... see the following
…		…
677	# use Backspace = ^?	1033	# use Backspace = ^?
678	$ stty erase ^?	1034	$ stty erase ^?
679	$ rxvt</pre>	1035	$ rxvt</pre>
680	</dd>	1036	</dd>
681	<dd>	1037	<dd>
682	<p>Toggle with ``ESC[36h'' / ``ESC[36l'' as documented in rxvt(7).</p>	1038	<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p>
683	</dd>	1039	</dd>
684	<dd>	1040	<dd>
685	<p>For an existing rxvt-unicode:</p>	1041	<p>For an existing rxvt-unicode:</p>
686	</dd>	1042	</dd>
687	<dd>	1043	<dd>
…		…
703	</dd>	1059	</dd>
704	<dd>	1060	<dd>
705	<p>The Delete key is a another casualty of the ill-defined Backspace problem.	1061	<p>The Delete key is a another casualty of the ill-defined Backspace problem.
706	To avoid confusion between the Backspace and Delete keys, the Delete	1062	To avoid confusion between the Backspace and Delete keys, the Delete
707	key has been assigned an escape sequence to match the vt100 for Execute	1063	key has been assigned an escape sequence to match the vt100 for Execute
708	(ESC[3~) and is in the supplied termcap/terminfo.</p>	1064	(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
709	</dd>	1065	</dd>
710	<dd>	1066	<dd>
711	<p>Some other Backspace problems:</p>	1067	<p>Some other Backspace problems:</p>
712	</dd>	1068	</dd>
713	<dd>	1069	<dd>
…		…
725	There are some compile-time selections available via configure. Unless	1081	There are some compile-time selections available via configure. Unless
726	you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can	1082	you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
727	use the `keysym' resource to alter the keystrings associated with keysyms.	1083	use the `keysym' resource to alter the keystrings associated with keysyms.
728	</dd>	1084	</dd>
729	<dd>	1085	<dd>
730	<p>Here's an example for a URxvt session started using `rxvt -name URxvt'</p>	1086	<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p>
731	</dd>
732	<dd>	1087	</dd>
		1088	<dd>
733	<pre>	1089	<pre>
734	URxvt*keysym.Home: \e[1~	1090	URxvt.keysym.Home: \033[1~
735	URxvt*keysym.End: \e[4~	1091	URxvt.keysym.End: \033[4~
736	URxvt*keysym.C-apostrophe: \e&lt;C-'&gt;	1092	URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
737	URxvt*keysym.C-slash: \e&lt;C-/&gt;	1093	URxvt.keysym.C-slash: \033&lt;C-/&gt;
738	URxvt*keysym.C-semicolon: \e&lt;C-;&gt;	1094	URxvt.keysym.C-semicolon: \033&lt;C-;&gt;
739	URxvt*keysym.C-grave: \e&lt;C-`&gt;	1095	URxvt.keysym.C-grave: \033&lt;C-`&gt;
740	URxvt*keysym.C-comma: \e&lt;C-,&gt;	1096	URxvt.keysym.C-comma: \033&lt;C-,&gt;
741	URxvt*keysym.C-period: \e&lt;C-.&gt;	1097	URxvt.keysym.C-period: \033&lt;C-.&gt;
742	URxvt*keysym.C-0x60: \e&lt;C-`&gt;	1098	URxvt.keysym.C-0x60: \033&lt;C-`&gt;
743	URxvt*keysym.C-Tab: \e&lt;C-Tab&gt;	1099	URxvt.keysym.C-Tab: \033&lt;C-Tab&gt;
744	URxvt*keysym.C-Return: \e&lt;C-Return&gt;	1100	URxvt.keysym.C-Return: \033&lt;C-Return&gt;
745	URxvt*keysym.S-Return: \e&lt;S-Return&gt;	1101	URxvt.keysym.S-Return: \033&lt;S-Return&gt;
746	URxvt*keysym.S-space: \e&lt;S-Space&gt;	1102	URxvt.keysym.S-space: \033&lt;S-Space&gt;
747	URxvt*keysym.M-Up: \e&lt;M-Up&gt;	1103	URxvt.keysym.M-Up: \033&lt;M-Up&gt;
748	URxvt*keysym.M-Down: \e&lt;M-Down&gt;	1104	URxvt.keysym.M-Down: \033&lt;M-Down&gt;
749	URxvt*keysym.M-Left: \e&lt;M-Left&gt;	1105	URxvt.keysym.M-Left: \033&lt;M-Left&gt;
750	URxvt*keysym.M-Right: \e&lt;M-Right&gt;	1106	URxvt.keysym.M-Right: \033&lt;M-Right&gt;
751	URxvt*keysym.M-C-0: list.0123456789.\e&lt;M-C-.&gt;	1107	URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
752	URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033&lt;M-C-.&gt;	1108	URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
753	URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007</pre>	1109	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
		1110	</dd>
		1111	<dd>
		1112	<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
754	</dd>	1113	</dd>
755	<p></p>	1114	<p></p>
756	<dt><strong><a name="item_i_27m_using_keyboard_model_xxx_that_has_extra_prio">I'm using keyboard model XXX that has extra Prior/Next/Insert keys.	1115	<dt><strong><a name="item_i_27m_using_keyboard_model_xxx_that_has_extra_prio">I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
757	How do I make use of them? For example, the Sun Keyboard type 4	1116	How do I make use of them? For example, the Sun Keyboard type 4
758	has the following mappings that rxvt-unicode doesn't recognize.</a></strong><br />	1117	has the following mappings that rxvt-unicode doesn't recognize.</a></strong><br />
…		…
765	F29 == Prior	1124	F29 == Prior
766	F33 == End	1125	F33 == End
767	F35 == Next</pre>	1126	F35 == Next</pre>
768	</dd>	1127	</dd>
769	<dd>	1128	<dd>
770	<p>Rather than have rxvt-unicode try to accommodate all the various possible keyboard	1129	<p>Rather than have rxvt-unicode try to accommodate all the various possible
771	mappings, it is better to use `xmodmap' to remap the keys as required for	1130	keyboard mappings, it is better to use `xmodmap' to remap the keys as
772	your particular machine.</p>	1131	required for your particular machine.</p>
773	</dd>	1132	</dd>
774	<dt><strong><a name="item_how_do_i_distinguish_if_i_27m_running_rxvt_2dunico">How do I distinguish if I'm running rxvt-unicode or a regular xterm?	1133	<dt><strong><a name="item_how_do_i_distinguish_wether_i_27m_running_rxvt_2du">How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
775	I need this to decide about setting colors etc.</a></strong><br />	1134	I need this to decide about setting colors etc.</a></strong><br />
776	</dt>	1135	</dt>
777	<dd>	1136	<dd>
778	rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can	1137	rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can
779	check and see if that is set. Note that several programs, JED, slrn,	1138	check and see if that is set. Note that several programs, JED, slrn,
…		…
828	</dd>	1187	</dd>
829	<p></p></dl>	1188	<p></p></dl>
830	<p>	1189	<p>
831	</p>	1190	</p>
832	<hr />	1191	<hr />
833	<h1><a name="synopsis">SYNOPSIS</a></h1>	1192	<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>
834	<pre>
835	# set a new font set
836	printf '\33]50;%s\007' 9x15,xft:Kochi&quot; Mincho&quot;</pre>
837	<pre>
838	# change the locale and tell rxvt-unicode about it
839	export LC_CTYPE=ja_JP.EUC-JP; printf &quot;\33]701;$LC_CTYPE\007&quot;</pre>
840	<pre>
841	# set window title
842	printf '\33]2;%s\007' &quot;new window title&quot;</pre>
843	<p>	1193	<p>
844	</p>	1194	</p>
845	<hr />	1195	<hr />
846	<h1><a name="description">DESCRIPTION</a></h1>	1196	<h1><a name="description">DESCRIPTION</a></h1>
847	<p>The rest of this document describes various technical aspects of	1197	<p>The rest of this document describes various technical aspects of
848	<strong>rxvt-unicode</strong>. First the description of supported command sequences,	1198	<strong>rxvt-unicode</strong>. First the description of supported command sequences,
849	followed by menu and pixmap support and last by a description of all	1199	followed by pixmap support and last by a description of all features
850	features selectable at <code>configure</code> time.</p>	1200	selectable at <code>configure</code> time.</p>
851	<p>
852	</p>
853	<hr />
854	<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>
855	<p>	1201	<p>
856	</p>	1202	</p>
857	<hr />	1203	<hr />
858	<h1><a name="definitions">Definitions</a></h1>	1204	<h1><a name="definitions">Definitions</a></h1>
859	<dl>	1205	<dl>
…		…
1042	</dd>	1388	</dd>
1043	<p></p>	1389	<p></p>
1044	<dt><strong><a name="item_esc_z"><strong><code>ESC Z</code> </strong>&gt;</a></strong><br />	1390	<dt><strong><a name="item_esc_z"><strong><code>ESC Z</code> </strong>&gt;</a></strong><br />
1045	</dt>	1391	</dt>
1046	<dd>	1392	<dd>
1047	Obsolete form of returns: <strong><code>ESC[?1;2C</code> </strong>&gt; <em>rxvt-unicode compile-time option</em>	1393	Obsolete form of returns: <strong><code>ESC [ ? 1 ; 2 C</code> </strong>&gt; <em>rxvt-unicode compile-time option</em>
1048	</dd>	1394	</dd>
1049	<p></p>	1395	<p></p>
1050	<dt><strong><a name="item_esc_c"><strong><code>ESC c</code> </strong>&gt;</a></strong><br />	1396	<dt><strong><a name="item_esc_c"><strong><code>ESC c</code> </strong>&gt;</a></strong><br />
1051	</dt>	1397	</dt>
1052	<dd>	1398	<dd>
…		…
1063	</dt>	1409	</dt>
1064	<dd>	1410	<dd>
1065	Invoke the G3 Character Set (LS3)	1411	Invoke the G3 Character Set (LS3)
1066	</dd>	1412	</dd>
1067	<p></p>	1413	<p></p>
1068	<dt><strong><strong><code>ESC</code> ( C</strong> &gt;&gt;</strong><br />	1414	<dt><strong><strong><code>ESC ( C</code> </strong>&gt;</strong><br />
1069	</dt>	1415	</dt>
1070	<dd>	1416	<dd>
1071	Designate G0 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>.	1417	Designate G0 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>.
1072	</dd>	1418	</dd>
1073	<p></p>	1419	<p></p>
1074	<dt><strong><a name="item_esc__29_c_3e"><strong><a href="#item_esc"><code>ESC</code></a> ) C</strong> &gt;&gt;</a></strong><br />	1420	<dt><strong><a name="item_esc__29_c"><strong><code>ESC ) C</code> </strong>&gt;</a></strong><br />
1075	</dt>	1421	</dt>
1076	<dd>	1422	<dd>
1077	Designate G1 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>.	1423	Designate G1 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>.
1078	</dd>	1424	</dd>
1079	<p></p>	1425	<p></p>
…		…
1254	<dt><strong><a name="item_esc__5b_ps_c"><strong><code>ESC [ Ps c</code> </strong>&gt;</a></strong><br />	1600	<dt><strong><a name="item_esc__5b_ps_c"><strong><code>ESC [ Ps c</code> </strong>&gt;</a></strong><br />
1255	</dt>	1601	</dt>
1256	<dd>	1602	<dd>
1257	Send Device Attributes (DA)	1603	Send Device Attributes (DA)
1258	<strong><code>Ps = 0</code> </strong>&gt; (or omitted): request attributes from terminal	1604	<strong><code>Ps = 0</code> </strong>&gt; (or omitted): request attributes from terminal
1259	returns: <strong><code>ESC[?1;2c</code> </strong>&gt; (``I am a VT100 with Advanced Video	1605	returns: <strong><code>ESC [ ? 1 ; 2 c</code> </strong>&gt; (``I am a VT100 with Advanced Video
1260	Option'')	1606	Option'')
1261	</dd>	1607	</dd>
1262	<p></p>	1608	<p></p>
1263	<dt><strong><a name="item_esc__5b_ps_d"><strong><code>ESC [ Ps d</code> </strong>&gt;</a></strong><br />	1609	<dt><strong><a name="item_esc__5b_ps_d"><strong><code>ESC [ Ps d</code> </strong>&gt;</a></strong><br />
1264	</dt>	1610	</dt>
…		…
1376	</dt>	1722	</dt>
1377	<dd>	1723	<dd>
1378	Save Cursor (SC)	1724	Save Cursor (SC)
1379	</dd>	1725	</dd>
1380	<p></p>	1726	<p></p>
		1727	<dt><strong><a name="item_esc__5b_ps_3bpt_t"><strong><code>ESC [ Ps;Pt t</code> </strong>&gt;</a></strong><br />
		1728	</dt>
		1729	<dd>
		1730	Window Operations
		1731	</dd>
		1732	<table>
		1733	<tr><td>Ps = 1</td><td>Deiconify (map) window</td></tr>
		1734	<tr><td>Ps = 2</td><td>Iconify window</td></tr>
		1735	<tr><td>Ps = 3</td><td>ESC [ 3 ; X ; Y t Move window to (X|Y)</td></tr>
		1736	<tr><td>Ps = 4</td><td>ESC [ 4 ; H ; W t Resize to WxH pixels</td></tr>
		1737	<tr><td>Ps = 5</td><td>Raise window</td></tr>
		1738	<tr><td>Ps = 6</td><td>Lower window</td></tr>
		1739	<tr><td>Ps = 7</td><td>Refresh screen once</td></tr>
		1740	<tr><td>Ps = 8</td><td>ESC [ 8 ; R ; C t Resize to R rows and C columns</td></tr>
		1741	<tr><td>Ps = 11</td><td>Report window state (responds with Ps = 1 or Ps = 2)</td></tr>
		1742	<tr><td>Ps = 13</td><td>Report window position (responds with Ps = 3)</td></tr>
		1743	<tr><td>Ps = 14</td><td>Report window pixel size (responds with Ps = 4)</td></tr>
		1744	<tr><td>Ps = 18</td><td>Report window text size (responds with Ps = 7)</td></tr>
		1745	<tr><td>Ps = 19</td><td>Currently the same as Ps = 18, but responds with Ps = 9</td></tr>
		1746	<tr><td>Ps = 20</td><td>Reports icon label (ESC ] L NAME \234)</td></tr>
		1747	<tr><td>Ps = 21</td><td>Reports window title (ESC ] l NAME \234)</td></tr>
		1748	<tr><td>Ps = 24..</td><td>Set window height to Ps rows</td></tr>
		1749	</table><p></p>
		1750	<dt><strong><a name="item_esc__5b_u"><strong><code>ESC [ u</code> </strong>&gt;</a></strong><br />
		1751	</dt>
		1752	<dd>
		1753	Restore Cursor
		1754	</dd>
		1755	<p></p>
1381	<dt><strong><a name="item_esc__5b_ps_x"><strong><code>ESC [ Ps x</code> </strong>&gt;</a></strong><br />	1756	<dt><strong><a name="item_esc__5b_ps_x"><strong><code>ESC [ Ps x</code> </strong>&gt;</a></strong><br />
1382	</dt>	1757	</dt>
1383	<dd>	1758	<dd>
1384	Request Terminal Parameters (DECREQTPARM)	1759	Request Terminal Parameters (DECREQTPARM)
1385	</dd>
1386	<p></p>
1387	<dt><strong><a name="item_esc__5b_u"><strong><code>ESC [ u</code> </strong>&gt;</a></strong><br />
1388	</dt>
1389	<dd>
1390	Restore Cursor
1391	</dd>	1760	</dd>
1392	<p></p></dl>	1761	<p></p></dl>
1393	<p></p>	1762	<p></p>
1394	<p>	1763	<p>
1395	</p>	1764	</p>
…		…
1469	</table><dt><strong><a name="item_ps__3d_9_x10_xterm"><strong><code>Ps = 9</code> </strong>&gt; X10 XTerm</a></strong><br />	1838	</table><dt><strong><a name="item_ps__3d_9_x10_xterm"><strong><code>Ps = 9</code> </strong>&gt; X10 XTerm</a></strong><br />
1470	</dt>	1839	</dt>
1471	<table>	1840	<table>
1472	<tr><td>h</td><td>Send Mouse X & Y on button press.</td></tr>	1841	<tr><td>h</td><td>Send Mouse X & Y on button press.</td></tr>
1473	<tr><td>l</td><td>No mouse reporting.</td></tr>	1842	<tr><td>l</td><td>No mouse reporting.</td></tr>
1474	</table><dt><strong><a name="item_10"><strong><code>Ps = 10</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
1475	</dt>
1476	<table>
1477	<tr><td>h</td><td>menuBar visible</td></tr>
1478	<tr><td>l</td><td>menuBar invisible</td></tr>
1479	</table><dt><strong><a name="item_ps__3d_25"><strong><code>Ps = 25</code> </strong>&gt;</a></strong><br />	1843	</table><dt><strong><a name="item_ps__3d_25"><strong><code>Ps = 25</code> </strong>&gt;</a></strong><br />
1480	</dt>	1844	</dt>
1481	<table>	1845	<table>
1482	<tr><td>h</td><td>Visible cursor {cnorm/cvvis}</td></tr>	1846	<tr><td>h</td><td>Visible cursor {cnorm/cvvis}</td></tr>
1483	<tr><td>l</td><td>Invisible cursor {civis}</td></tr>	1847	<tr><td>l</td><td>Invisible cursor {civis}</td></tr>
…		…
1548	</table><dt><strong><a name="item_1011"><strong><code>Ps = 1011</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />	1912	</table><dt><strong><a name="item_1011"><strong><code>Ps = 1011</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
1549	</dt>	1913	</dt>
1550	<table>	1914	<table>
1551	<tr><td>h</td><td>Scroll to bottom when a key is pressed</td></tr>	1915	<tr><td>h</td><td>Scroll to bottom when a key is pressed</td></tr>
1552	<tr><td>l</td><td>Don't scroll to bottom when a key is pressed</td></tr>	1916	<tr><td>l</td><td>Don't scroll to bottom when a key is pressed</td></tr>
		1917	</table><dt><strong><a name="item_1021"><strong><code>Ps = 1021</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
		1918	</dt>
		1919	<table>
		1920	<tr><td>h</td><td>Bold/italic implies high intensity (see option -is)</td></tr>
		1921	<tr><td>l</td><td>Font styles have no effect on intensity (Compile styles)</td></tr>
1553	</table><dt><strong><a name="item_ps__3d_1047"><strong><code>Ps = 1047</code> </strong>&gt;</a></strong><br />	1922	</table><dt><strong><a name="item_ps__3d_1047"><strong><code>Ps = 1047</code> </strong>&gt;</a></strong><br />
1554	</dt>	1923	</dt>
1555	<table>	1924	<table>
1556	<tr><td>h</td><td>Use Alternate Screen Buffer</td></tr>	1925	<tr><td>h</td><td>Use Alternate Screen Buffer</td></tr>
1557	<tr><td>l</td><td>Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it</td></tr>	1926	<tr><td>l</td><td>Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it</td></tr>
…		…
1589	<tr><td>Ps = 10</td><td>Change colour of text foreground to Pt (NB: may change in future)</td></tr>	1958	<tr><td>Ps = 10</td><td>Change colour of text foreground to Pt (NB: may change in future)</td></tr>
1590	<tr><td>Ps = 11</td><td>Change colour of text background to Pt (NB: may change in future)</td></tr>	1959	<tr><td>Ps = 11</td><td>Change colour of text background to Pt (NB: may change in future)</td></tr>
1591	<tr><td>Ps = 12</td><td>Change colour of text cursor foreground to Pt</td></tr>	1960	<tr><td>Ps = 12</td><td>Change colour of text cursor foreground to Pt</td></tr>
1592	<tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr>	1961	<tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr>
1593	<tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr>	1962	<tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr>
1594	<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt</td></tr>	1963	<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt [deprecated, see 706]</td></tr>
1595	<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt</td></tr>	1964	<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt [deprecated, see 707]</td></tr>
		1965	<tr><td>Ps = 20</td><td>Change background pixmap parameters (see section XPM) (Compile XPM).</td></tr>
1596	<tr><td>Ps = 20</td><td>Change default background to Pt</td></tr>	1966	<tr><td>Ps = 39</td><td>Change default foreground colour to Pt.</td></tr>
1597	<tr><td>Ps = 39</td><td>Change default foreground colour to Pt rxvt compile-time option</td></tr>
1598	<tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr>	1967	<tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr>
1599	<tr><td>Ps = 49</td><td>Change default background colour to Pt rxvt compile-time option</td></tr>	1968	<tr><td>Ps = 49</td><td>Change default background colour to Pt.</td></tr>
1600	<tr><td>Ps = 50</td><td>Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n</td></tr>	1969	<tr><td>Ps = 50</td><td>Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n</td></tr>
1601	<tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr>	1970	<tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr>
1602	<tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (rxvt extension)</td></tr>	1971	<tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).</td></tr>
1603	<tr><td>Ps = 703</td><td>Menubar command Pt rxvt compile-time option (rxvt-unicode extension)</td></tr>	1972	<tr><td>Ps = 702</td><td>Request version if Pt is ?, returning rxvt-unicode, the resource name, the major and minor version numbers, e.g. ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST.</td></tr>
1604	<tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr>	1973	<tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr>
1605	<tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt</td></tr>	1974	<tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt (Compile transparency).</td></tr>
		1975	<tr><td>Ps = 706</td><td>Change colour of bold characters to Pt</td></tr>
		1976	<tr><td>Ps = 707</td><td>Change colour of underlined characters to Pt</td></tr>
1606	<tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr>	1977	<tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr>
1607	<tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50.</td></tr>	1978	<tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1608	<tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50.</td></tr>	1979	<tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1609	<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50.</td></tr>	1980	<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
		1981	<tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
		1982	<tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
		1983	<tr><td>Ps = 777</td><td>Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).</td></tr>
1610	</table><p></p></dl>	1984	</table><p></p></dl>
1611	<p></p>	1985	<p></p>
1612	<p>
1613	</p>
1614	<hr />
1615	<h1><a name="menubar">menuBar</a></h1>
1616	<p><strong>The exact syntax used is <em>almost</em> solidified. </strong>&gt;
1617	In the menus, <strong>DON'T</strong> try to use menuBar commands that add or remove a
1618	menuBar.</p>
1619	<p>Note that in all of the commands, the <strong><em>/path/</em> </strong>&gt; <em>cannot</em> be
1620	omitted: use <strong>./</strong> to specify a menu relative to the current menu.</p>
1621	<p>
1622	</p>
1623	<h2><a name="overview_of_menubar_operation">Overview of menuBar operation</a></h2>
1624	<p>For the menuBar XTerm escape sequence <code>ESC ] 703 ; Pt ST</code>, the syntax
1625	of <a href="#item_pt"><code>Pt</code></a> can be used for a variety of tasks:</p>
1626	<p>At the top level is the current menuBar which is a member of a circular
1627	linked-list of other such menuBars.</p>
1628	<p>The menuBar acts as a parent for the various drop-down menus, which in
1629	turn, may have labels, separator lines, menuItems and subMenus.</p>
1630	<p>The menuItems are the useful bits: you can use them to mimic keyboard
1631	input or even to send text or escape sequences back to rxvt.</p>
1632	<p>The menuBar syntax is intended to provide a simple yet robust method of
1633	constructing and manipulating menus and navigating through the
1634	menuBars.</p>
1635	<p>The first step is to use the tag <strong>[menu:<em>name</em>] </strong>&gt; which creates
1636	the menuBar called <em>name</em> and allows access. You may now or menus,
1637	subMenus, and menuItems. Finally, use the tag <strong>[done]</strong> to set the
1638	menuBar access as <strong>readonly</strong> to prevent accidental corruption of the
1639	menus. To re-access the current menuBar for alterations, use the tag
1640	<strong>[menu]</strong>, make the alterations and then use <strong>[done]</strong></p>
1641	<p></p>
1642	<p>
1643	</p>
1644	<h2><a name="commands">Commands</a></h2>
1645	<dl>
1646	<dt><strong><a name="item__5bmenu_3a_2bname_5d"><strong>[menu:+<em>name</em>] </strong>&gt;</a></strong><br />
1647	</dt>
1648	<dd>
1649	access the named menuBar for creation or alteration. If a new menuBar
1650	is created, it is called <em>name</em> (max of 15 chars) and the current
1651	menuBar is pushed onto the stack
1652	</dd>
1653	<p></p>
1654	<dt><strong><a name="item__5bmenu_5d"><strong>[menu]</strong></a></strong><br />
1655	</dt>
1656	<dd>
1657	access the current menuBar for alteration
1658	</dd>
1659	<p></p>
1660	<dt><strong><a name="item__5btitle_3a_2bstring_5d"><strong>[title:+<em>string</em>] </strong>&gt;</a></strong><br />
1661	</dt>
1662	<dd>
1663	set the current menuBar's title to <em>string</em>, which may contain the
1664	following format specifiers:
1665	<strong>%%</strong> : literal <strong>%</strong> character
1666	<strong>%n</strong> : rxvt name (as per the <strong>-name</strong> command-line option)
1667	<strong>%v</strong> : rxvt version
1668	</dd>
1669	<p></p>
1670	<dt><strong><a name="item__5bdone_5d"><strong>[done]</strong></a></strong><br />
1671	</dt>
1672	<dd>
1673	set menuBar access as <strong>readonly</strong>.
1674	End-of-file tag for <strong>[read:+<em>file</em>] </strong>&gt; operations.
1675	</dd>
1676	<p></p>
1677	<dt><strong><a name="item__5bread_3a_2bfile_5d"><strong>[read:+<em>file</em>] </strong>&gt;</a></strong><br />
1678	</dt>
1679	<dd>
1680	read menu commands directly from <em>file</em> (extension ``.menu'' will be
1681	appended if required.) Start reading at a line with <strong>[menu]</strong> or <strong>&lt;
1682	[menu:+<em>name</em> </strong>&gt; and continuing until <strong>[done]</strong> is encountered.
1683	</dd>
1684	<dd>
1685	<p>Blank and comment lines (starting with <strong>#</strong>) are ignored. Actually,
1686	since any invalid menu commands are also ignored, almost anything could
1687	be construed as a comment line, but this may be tightened up in the
1688	future ... so don't count on it!.</p>
1689	</dd>
1690	<p></p>
1691	<dt><strong><a name="item__5bread_3a_2bfile_3b_2bname_5d"><strong>[read:+<em>file</em>;+<em>name</em>] </strong>&gt;</a></strong><br />
1692	</dt>
1693	<dd>
1694	The same as <strong>[read:+<em>file</em>] </strong>&gt;, but start reading at a line with
1695	<strong>[menu:+<em>name</em>] </strong>&gt; and continuing until <strong>[done:+<em>name</em>] </strong>&gt; or
1696	<strong>[done]</strong> is encountered.
1697	</dd>
1698	<p></p>
1699	<dt><strong><a name="item__5bdump_5d"><strong>[dump]</strong></a></strong><br />
1700	</dt>
1701	<dd>
1702	dump all menuBars to the file <strong>/tmp/rxvt-PID</strong> in a format suitable for
1703	later rereading.
1704	</dd>
1705	<p></p>
1706	<dt><strong><a name="item__5brm_3aname_5d"><strong>[rm:name]</strong></a></strong><br />
1707	</dt>
1708	<dd>
1709	remove the named menuBar
1710	</dd>
1711	<p></p>
1712	<dt><strong><a name="item__5brm_5d__5brm_3a_5d"><strong>[rm] [rm:]</strong></a></strong><br />
1713	</dt>
1714	<dd>
1715	remove the current menuBar
1716	</dd>
1717	<p></p>
1718	<dt><strong><a name="item__5brm_2a_5d__5brm_3a_2a_5d"><strong>[rm*] [rm:*]</strong></a></strong><br />
1719	</dt>
1720	<dd>
1721	remove all menuBars
1722	</dd>
1723	<p></p>
1724	<dt><strong><a name="item__5bswap_5d"><strong>[swap]</strong></a></strong><br />
1725	</dt>
1726	<dd>
1727	swap the top two menuBars
1728	</dd>
1729	<p></p>
1730	<dt><strong><a name="item__5bprev_5d"><strong>[prev]</strong></a></strong><br />
1731	</dt>
1732	<dd>
1733	access the previous menuBar
1734	</dd>
1735	<p></p>
1736	<dt><strong><a name="item__5bnext_5d"><strong>[next]</strong></a></strong><br />
1737	</dt>
1738	<dd>
1739	access the next menuBar
1740	</dd>
1741	<p></p>
1742	<dt><strong><a name="item__5bshow_5d"><strong>[show]</strong></a></strong><br />
1743	</dt>
1744	<dd>
1745	Enable display of the menuBar
1746	</dd>
1747	<p></p>
1748	<dt><strong><a name="item__5bhide_5d"><strong>[hide]</strong></a></strong><br />
1749	</dt>
1750	<dd>
1751	Disable display of the menuBar
1752	</dd>
1753	<p></p>
1754	<dt><strong><a name="item__5bpixmap_3a_2bname_5d"><strong>[pixmap:+<em>name</em>] </strong>&gt;</a></strong><br />
1755	</dt>
1756	<dt><strong><a name="item__5bpixmap_3a_2bname_3bscaling_5d"><strong>[pixmap:+<em>name</em>;<em>scaling</em>] </strong>&gt;</a></strong><br />
1757	</dt>
1758	<dd>
1759	(set the background pixmap globally
1760	</dd>
1761	<dd>
1762	<p><strong>A Future implementation <em>may</em> make this local to the menubar </strong>&gt;)</p>
1763	</dd>
1764	<p></p>
1765	<dt><strong><a name="item__5b_3a_2bcommand_3a_5d"><strong>[:+<em>command</em>:] </strong>&gt;</a></strong><br />
1766	</dt>
1767	<dd>
1768	ignore the menu readonly status and issue a <em>command</em> to or a menu or
1769	menuitem or change the ; a useful shortcut for setting the quick arrows
1770	from a menuBar.
1771	</dd>
1772	<p></p></dl>
1773	<p></p>
1774	<p>
1775	</p>
1776	<h2><a name="adding_and_accessing_menus">Adding and accessing menus</a></h2>
1777	<p>The following commands may also be <strong>+</strong> prefixed.</p>
1778	<dl>
1779	<dt><strong><a name="item__2f_2b"><strong>/+</strong></a></strong><br />
1780	</dt>
1781	<dd>
1782	access menuBar top level
1783	</dd>
1784	<p></p>
1785	<dt><strong><a name="item__2e_2f_2b"><strong>./+</strong></a></strong><br />
1786	</dt>
1787	<dd>
1788	access current menu level
1789	</dd>
1790	<p></p>
1791	<dt><strong><a name="item__2e_2e_2f_2b"><strong>../+</strong></a></strong><br />
1792	</dt>
1793	<dd>
1794	access parent menu (1 level up)
1795	</dd>
1796	<p></p>
1797	<dt><strong><a name="item__2e_2e_2f_2e_2e_2f"><strong>../../</strong></a></strong><br />
1798	</dt>
1799	<dd>
1800	access parent menu (multiple levels up)
1801	</dd>
1802	<p></p>
1803	<dt><strong><a name="item__2fpath_2fmenu"><strong><em>/path/</em>menu </strong>&gt;</a></strong><br />
1804	</dt>
1805	<dd>
1806	add/access menu
1807	</dd>
1808	<p></p>
1809	<dt><strong><a name="item__2fpath_2fmenu_2f_2a"><strong><em>/path/</em>menu/* </strong>&gt;</a></strong><br />
1810	</dt>
1811	<dd>
1812	add/access menu and clear it if it exists
1813	</dd>
1814	<p></p>
1815	<dt><strong><a name="item__2fpath_2f_7b_2d_7d"><strong><em>/path/</em>{-} </strong>&gt;</a></strong><br />
1816	</dt>
1817	<dd>
1818	add separator
1819	</dd>
1820	<p></p>
1821	<dt><strong><a name="item__2fpath_2f_7bitem_7d"><strong><em>/path/</em>{item} </strong>&gt;</a></strong><br />
1822	</dt>
1823	<dd>
1824	add <strong>item</strong> as a label
1825	</dd>
1826	<p></p>
1827	<dt><strong><a name="item__2fpath_2f_7bitem_7d_action"><strong><em>/path/</em>{item} action </strong>&gt;</a></strong><br />
1828	</dt>
1829	<dd>
1830	add/alter <em>menuitem</em> with an associated <em>action</em>
1831	</dd>
1832	<p></p>
1833	<dt><strong><a name="item__2fpath_2f_7bitem_7d_7bright_2dtext_7d"><strong><em>/path/</em>{item}{right-text} </strong>&gt;</a></strong><br />
1834	</dt>
1835	<dd>
1836	add/alter <em>menuitem</em> with <strong>right-text</strong> as the right-justified text
1837	and as the associated <em>action</em>
1838	</dd>
1839	<p></p>
1840	<dt><strong><a name="item__2fpath_2f_7bitem_7d_7brtext_7d_action"><strong><em>/path/</em>{item}{rtext} action </strong>&gt;</a></strong><br />
1841	</dt>
1842	<dd>
1843	add/alter <em>menuitem</em> with an associated <em>action</em> and with <strong>rtext</strong> as
1844	the right-justified text.
1845	</dd>
1846	<p></p></dl>
1847	<dl>
1848	<dt><strong><a name="item_special_characters_in_action_must_be_backslash_2de">Special characters in <em>action</em> must be backslash-escaped:</a></strong><br />
1849	</dt>
1850	<dd>
1851	<strong>\a \b \E \e \n \r \t \octal</strong>
1852	</dd>
1853	<p></p>
1854	<dt><strong><a name="item_or_in_control_2dcharacter_notation_3a">or in control-character notation:</a></strong><br />
1855	</dt>
1856	<dd>
1857	<strong>^@, ^A .. ^Z .. ^_, ^?</strong>
1858	</dd>
1859	<p></p></dl>
1860	<p>To send a string starting with a <strong>NUL</strong> (<strong>^@</strong>) character to the
1861	program, start <em>action</em> with a pair of <strong>NUL</strong> characters (<strong>^@^@</strong>),
1862	the first of which will be stripped off and the balance directed to the
1863	program. Otherwise if <em>action</em> begins with <strong>NUL</strong> followed by
1864	non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the
1865	balance is sent back to rxvt.</p>
1866	<p>As a convenience for the many Emacs-type editors, <em>action</em> may start
1867	with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be
1868	appended if missed from <strong>M-x</strong> commands.</p>
1869	<p>As a convenience for issuing XTerm <strong>ESC]</strong> sequences from a menubar (or
1870	quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p>
1871	<dl>
1872	<dt><strong><a name="item_for_example_2c">For example,</a></strong><br />
1873	</dt>
1874	<dd>
1875	<strong>M-xapropos</strong> is equivalent to <strong>\Exapropos\r</strong>
1876	</dd>
1877	<p></p>
1878	<dt><strong><a name="item_and">and</a></strong><br />
1879	</dt>
1880	<dd>
1881	<strong>\E]703;mona;100</strong> is equivalent to <strong>\E]703;mona;100\a</strong>
1882	</dd>
1883	<p></p></dl>
1884	<p>The option <strong>{<em>right-rtext</em>} </strong>&gt; will be right-justified. In the
1885	absence of a specified action, this text will be used as the <em>action</em>
1886	as well.</p>
1887	<dl>
1888	<dt><strong>For example,</strong><br />
1889	</dt>
1890	<dd>
1891	<strong>/File/{Open}{^X^F}</strong> is equivalent to <strong>/File/{Open}{^X^F} ^X^F</strong>
1892	</dd>
1893	<p></p></dl>
1894	<p>The left label <em>is</em> necessary, since it's used for matching, but
1895	implicitly hiding the left label (by using same name for both left and
1896	right labels), or explicitly hiding the left label (by preceeding it
1897	with a dot), makes it possible to have right-justified text only.</p>
1898	<dl>
1899	<dt><strong>For example,</strong><br />
1900	</dt>
1901	<dd>
1902	<strong>/File/{Open}{Open} Open-File-Action</strong>
1903	</dd>
1904	<p></p>
1905	<dt><strong><a name="item_or_hiding_it">or hiding it</a></strong><br />
1906	</dt>
1907	<dd>
1908	<strong>/File/{.anylabel}{Open} Open-File-Action</strong>
1909	</dd>
1910	<p></p></dl>
1911	<p></p>
1912	<p>
1913	</p>
1914	<h2><a name="removing_menus">Removing menus</a></h2>
1915	<dl>
1916	<dt><strong><a name="item__2d_2f_2a_2b"><strong>-/*+ </strong>&gt;</a></strong><br />
1917	</dt>
1918	<dd>
1919	remove all menus from the menuBar, the same as <strong>[clear]</strong>
1920	</dd>
1921	<p></p>
1922	<dt><strong><a name="item__2d_2b_2fpathmenu_2b"><strong>-+<em>/path</em>menu+ </strong>&gt;</a></strong><br />
1923	</dt>
1924	<dd>
1925	remove menu
1926	</dd>
1927	<p></p>
1928	<dt><strong><a name="item__2d_2b_2fpath_7bitem_7d_2b"><strong>-+<em>/path</em>{item}+ </strong>&gt;</a></strong><br />
1929	</dt>
1930	<dd>
1931	remove item
1932	</dd>
1933	<p></p>
1934	<dt><strong><a name="item__2d_2b_2fpath_7b_2d_7d"><strong>-+<em>/path</em>{-} </strong>&gt;</a></strong><br />
1935	</dt>
1936	<dd>
1937	remove separator)
1938	</dd>
1939	<p></p>
1940	<dt><strong><a name="item__2d_2fpath_2fmenu_2f_2a"><strong>-/path/menu/*</strong></a></strong><br />
1941	</dt>
1942	<dd>
1943	remove all items, separators and submenus from menu
1944	</dd>
1945	<p></p></dl>
1946	<p></p>
1947	<p>
1948	</p>
1949	<h2><a name="quick_arrows">Quick Arrows</a></h2>
1950	<p>The menus also provide a hook for <em>quick arrows</em> to provide easier
1951	user access. If nothing has been explicitly set, the default is to
1952	emulate the curror keys. The syntax permits each arrow to be altered
1953	individually or all four at once without re-entering their common
1954	beginning/end text. For example, to explicitly associate cursor actions
1955	with the arrows, any of the following forms could be used:</p>
1956	<dl>
1957	<dt><strong><a name="item__3cr_3e_2bright"><strong>&lt;r</strong>+<em>Right</em> &gt;&gt;</a></strong><br />
1958	</dt>
1959	<dt><strong><a name="item__3cl_3e_2bleft"><strong>&lt;l</strong>+<em>Left</em> &gt;&gt;</a></strong><br />
1960	</dt>
1961	<dt><strong><a name="item__3cu_3e_2bup"><strong>&lt;u</strong>+<em>Up</em> &gt;&gt;</a></strong><br />
1962	</dt>
1963	<dt><strong><a name="item__3cd_3e_2bdown"><strong>&lt;d</strong>+<em>Down</em> &gt;&gt;</a></strong><br />
1964	</dt>
1965	<dd>
1966	Define actions for the respective arrow buttons
1967	</dd>
1968	<p></p>
1969	<dt><strong><a name="item__3cb_3e_2bbegin"><strong>&lt;b</strong>+<em>Begin</em> &gt;&gt;</a></strong><br />
1970	</dt>
1971	<dt><strong><a name="item__3ce_3e_2bend"><strong>&lt;e</strong>+<em>End</em> &gt;&gt;</a></strong><br />
1972	</dt>
1973	<dd>
1974	Define common beginning/end parts for <em>quick arrows</em> which used in
1975	conjunction with the above &lt;r&gt; &lt;l&gt; &lt;u&gt; &lt;d&gt; constructs
1976	</dd>
1977	<p></p></dl>
1978	<dl>
1979	<dt><strong><a name="item_for_example_2c_define_arrows_individually_2c">For example, define arrows individually,</a></strong><br />
1980	</dt>
1981	<dd>
1982	<pre>
1983	&lt;u&gt;\E[A</pre>
1984	</dd>
1985	<dd>
1986	<pre>
1987	&lt;d&gt;\E[B</pre>
1988	</dd>
1989	<dd>
1990	<pre>
1991	&lt;r&gt;\E[C</pre>
1992	</dd>
1993	<dd>
1994	<pre>
1995	&lt;l&gt;\E[D</pre>
1996	</dd>
1997	<dt><strong><a name="item_or_all_at_once">or all at once</a></strong><br />
1998	</dt>
1999	<dd>
2000	<pre>
2001	&lt;u&gt;\E[AZ&lt;&gt;&lt;d&gt;\E[BZ&lt;&gt;&lt;r&gt;\E[CZ&lt;&gt;&lt;l&gt;\E[D</pre>
2002	</dd>
2003	<dt><strong><a name="item_compactly">or more compactly (factoring out common parts)</a></strong><br />
2004	</dt>
2005	<dd>
2006	<pre>
2007	&lt;b&gt;\E[&lt;u&gt;AZ&lt;&gt;&lt;d&gt;BZ&lt;&gt;&lt;r&gt;CZ&lt;&gt;&lt;l&gt;D</pre>
2008	</dd>
2009	</dl>
2010	<p></p>
2011	<p>
2012	</p>
2013	<h2><a name="command_summary">Command Summary</a></h2>
2014	<p>A short summary of the most <em>common</em> commands:</p>
2015	<dl>
2016	<dt><strong><a name="item__5bmenu_3aname_5d">[menu:name]</a></strong><br />
2017	</dt>
2018	<dd>
2019	use an existing named menuBar or start a new one
2020	</dd>
2021	<p></p>
2022	<dt><strong>[menu]</strong><br />
2023	</dt>
2024	<dd>
2025	use the current menuBar
2026	</dd>
2027	<p></p>
2028	<dt><strong><a name="item__5btitle_3astring_5d">[title:string]</a></strong><br />
2029	</dt>
2030	<dd>
2031	set menuBar title
2032	</dd>
2033	<p></p>
2034	<dt><strong>[done]</strong><br />
2035	</dt>
2036	<dd>
2037	set menu access to readonly and, if reading from a file, signal EOF
2038	</dd>
2039	<p></p>
2040	<dt><strong><a name="item__5bdone_3aname_5d">[done:name]</a></strong><br />
2041	</dt>
2042	<dd>
2043	if reading from a file using [read:file;name] signal EOF
2044	</dd>
2045	<p></p>
2046	<dt><strong>[rm:name]</strong><br />
2047	</dt>
2048	<dd>
2049	remove named <code>menuBar(s)</code>
2050	</dd>
2051	<p></p>
2052	<dt><strong>[rm] [rm:]</strong><br />
2053	</dt>
2054	<dd>
2055	remove current menuBar
2056	</dd>
2057	<p></p>
2058	<dt><strong>[rm*] [rm:*]</strong><br />
2059	</dt>
2060	<dd>
2061	remove all <code>menuBar(s)</code>
2062	</dd>
2063	<p></p>
2064	<dt><strong>[swap]</strong><br />
2065	</dt>
2066	<dd>
2067	swap top two menuBars
2068	</dd>
2069	<p></p>
2070	<dt><strong>[prev]</strong><br />
2071	</dt>
2072	<dd>
2073	access the previous menuBar
2074	</dd>
2075	<p></p>
2076	<dt><strong>[next]</strong><br />
2077	</dt>
2078	<dd>
2079	access the next menuBar
2080	</dd>
2081	<p></p>
2082	<dt><strong>[show]</strong><br />
2083	</dt>
2084	<dd>
2085	map menuBar
2086	</dd>
2087	<p></p>
2088	<dt><strong>[hide]</strong><br />
2089	</dt>
2090	<dd>
2091	unmap menuBar
2092	</dd>
2093	<p></p>
2094	<dt><strong><a name="item__5bpixmap_3bfile_5d">[pixmap;file]</a></strong><br />
2095	</dt>
2096	<dt><strong><a name="item__5bpixmap_3bfile_3bscaling_5d">[pixmap;file;scaling]</a></strong><br />
2097	</dt>
2098	<dd>
2099	set a background pixmap
2100	</dd>
2101	<p></p>
2102	<dt><strong><a name="item__5bread_3afile_5d">[read:file]</a></strong><br />
2103	</dt>
2104	<dt><strong><a name="item__5bread_3afile_3bname_5d">[read:file;name]</a></strong><br />
2105	</dt>
2106	<dd>
2107	read in a menu from a file
2108	</dd>
2109	<p></p>
2110	<dt><strong>[dump]</strong><br />
2111	</dt>
2112	<dd>
2113	dump out all menuBars to /tmp/rxvt-PID
2114	</dd>
2115	<p></p>
2116	<dt><strong><a name="item__2f">/</a></strong><br />
2117	</dt>
2118	<dd>
2119	access menuBar top level
2120	</dd>
2121	<p></p>
2122	<dt><strong><a name="item__2e_2f">./</a></strong><br />
2123	</dt>
2124	<dt><strong><a name="item__2e_2e_2f">../</a></strong><br />
2125	</dt>
2126	<dt><strong>../../</strong><br />
2127	</dt>
2128	<dd>
2129	access current or parent menu level
2130	</dd>
2131	<p></p>
2132	<dt><strong>/path/menu</strong><br />
2133	</dt>
2134	<dd>
2135	add/access menu
2136	</dd>
2137	<p></p>
2138	<dt><strong>/path/{-}</strong><br />
2139	</dt>
2140	<dd>
2141	add separator
2142	</dd>
2143	<p></p>
2144	<dt><strong>/path/{item}{rtext} action</strong><br />
2145	</dt>
2146	<dd>
2147	add/alter menu item
2148	</dd>
2149	<p></p>
2150	<dt><strong><a name="item__2d_2f_2a">-/*</a></strong><br />
2151	</dt>
2152	<dd>
2153	remove all menus from the menuBar
2154	</dd>
2155	<p></p>
2156	<dt><strong><a name="item__2d_2fpath_2fmenu">-/path/menu</a></strong><br />
2157	</dt>
2158	<dd>
2159	remove menu items, separators and submenus from menu
2160	</dd>
2161	<p></p>
2162	<dt><strong>-/path/menu</strong><br />
2163	</dt>
2164	<dd>
2165	remove menu
2166	</dd>
2167	<p></p>
2168	<dt><strong><a name="item__2d_2fpath_2f_7bitem_7d">-/path/{item}</a></strong><br />
2169	</dt>
2170	<dd>
2171	remove item
2172	</dd>
2173	<p></p>
2174	<dt><strong><a name="item__2d_2fpath_2f_7b_2d_7d">-/path/{-}</a></strong><br />
2175	</dt>
2176	<dd>
2177	remove separator
2178	</dd>
2179	<p></p>
2180	<dt><strong><a name="item__3cb_3ebegin_3cr_3eright_3cl_3eleft_3cu_3eup_3cd_3">&lt;b&gt;Begin&lt;r&gt;Right&lt;l&gt;Left&lt;u&gt;Up&lt;d&gt;Down&lt;e&gt;End</a></strong><br />
2181	</dt>
2182	<dd>
2183	menu quick arrows
2184	</dd>
2185	<p></p></dl>
2186	<p>	1986	<p>
2187	</p>	1987	</p>
2188	<hr />	1988	<hr />
2189	<h1><a name="xpm">XPM</a></h1>	1989	<h1><a name="xpm">XPM</a></h1>
2190	<p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value	1990	<p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value
…		…
2373	</table><p>	2173	</table><p>
2374	</p>	2174	</p>
2375	<hr />	2175	<hr />
2376	<h1><a name="configure_options">CONFIGURE OPTIONS</a></h1>	2176	<h1><a name="configure_options">CONFIGURE OPTIONS</a></h1>
2377	<p>General hint: if you get compile errors, then likely your configuration	2177	<p>General hint: if you get compile errors, then likely your configuration
2378	hasn't been tested well. Either try with --enable-everything or use the	2178	hasn't been tested well. Either try with <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> or use
2379	./reconf script as a base for experiments. ./reconf is used by myself,	2179	the <em>./reconf</em> script as a base for experiments. <em>./reconf</em> is used by
2380	so it should generally be a working config. Of course, you should always	2180	myself, so it should generally be a working config. Of course, you should
2381	report when a combination doesn't work, so it can be fixed. Marc Lehmann	2181	always report when a combination doesn't work, so it can be fixed. Marc
2382	&lt;<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>&gt;.</p>	2182	Lehmann &lt;<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>&gt;.</p>
		2183	<p>All</p>
2383	<dl>	2184	<dl>
2384	<dt><strong><a name="item__2d_2denable_2deverything">--enable-everything</a></strong><br />	2185	<dt><strong><a name="item__2d_2denable_2deverything">--enable-everything</a></strong><br />
2385	</dt>	2186	</dt>
2386	<dd>	2187	<dd>
2387	Add support for all non-multichoice options listed in ``./configure	2188	Add (or remove) support for all non-multichoice options listed in ``./configure
2388	--help''. Note that unlike other enable options this is order dependant.	2189	--help''.
2389	You can specify this and then disable options which this enables by	2190	</dd>
2390	<em>following</em> this with the appropriate commands.
2391	</dd>	2191	<dd>
		2192	<p>You can specify this and then disable options you do not like by
		2193	<em>following</em> this with the appropriate <code>--disable-...</code> arguments,
		2194	or you can start with a minimal configuration by specifying
		2195	<code>--disable-everything</code> and than adding just the <code>--enable-...</code> arguments
		2196	you want.</p>
		2197	</dd>
2392	<p></p>	2198	<p></p>
2393	<dt><strong><a name="item__2d_2denable_2dxft">--enable-xft</a></strong><br />	2199	<dt><strong><a name="item_xft">--enable-xft (default: enabled)</a></strong><br />
2394	</dt>	2200	</dt>
2395	<dd>	2201	<dd>
2396	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2202	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2397	slower and require lots of memory, but as long as you don't use them, you	2203	slower and require lots of memory, but as long as you don't use them, you
2398	don't pay for them.	2204	don't pay for them.
2399	</dd>	2205	</dd>
2400	<p></p>	2206	<p></p>
2401	<dt><strong><a name="item__2d_2denable_2dfont_2dstyles">--enable-font-styles</a></strong><br />	2207	<dt><strong><a name="item_styles">--enable-font-styles (default: on)</a></strong><br />
2402	</dt>	2208	</dt>
2403	<dd>	2209	<dd>
2404	Add support for <strong>bold</strong>, <em>italic</em> and <strong><em>bold italic</em> </strong>&gt; font	2210	Add support for <strong>bold</strong>, <em>italic</em> and <strong><em>bold italic</em> </strong>&gt; font
2405	styles. The fonts can be set manually or automatically.	2211	styles. The fonts can be set manually or automatically.
2406	</dd>	2212	</dd>
2407	<p></p>	2213	<p></p>
2408	<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br />	2214	<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e__28defaul">--with-codesets=NAME,... (default: all)</a></strong><br />
2409	</dt>	2215	</dt>
2410	<dd>	2216	<dd>
2411	Compile in support for additional codeset (encoding) groups (eu, vn are	2217	Compile in support for additional codeset (encoding) groups (<code>eu</code>, <code>vn</code>
2412	always compiled in, which includes most 8-bit character sets). These	2218	are always compiled in, which includes most 8-bit character sets). These
2413	codeset tables are currently only used for driving X11 core fonts, they	2219	codeset tables are used for driving X11 core fonts, they are not required
2414	are not required for Xft fonts. Compiling them in will make your binary	2220	for Xft fonts, although having them compiled in lets rxvt-unicode choose
2415	bigger (together about 700kB), but it doesn't increase memory usage unless	2221	replacement fonts more intelligently. Compiling them in will make your
		2222	binary bigger (all of together cost about 700kB), but it doesn't increase
2416	you use an X11 font requiring one of these encodings.	2223	memory usage unless you use a font requiring one of these encodings.
2417	</dd>	2224	</dd>
2418	<table>	2225	<table>
2419	<tr><td>all</td><td>all available codeset groups</td></tr>	2226	<tr><td>all</td><td>all available codeset groups</td></tr>
2420	<tr><td>zh</td><td>common chinese encodings</td></tr>	2227	<tr><td>zh</td><td>common chinese encodings</td></tr>
2421	<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr>	2228	<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr>
2422	<tr><td>jp</td><td>common japanese encodings</td></tr>	2229	<tr><td>jp</td><td>common japanese encodings</td></tr>
2423	<tr><td>jp_ext</td><td>rarely used but big japanese encodings</td></tr>	2230	<tr><td>jp_ext</td><td>rarely used but big japanese encodings</td></tr>
2424	<tr><td>kr</td><td>korean encodings</td></tr>	2231	<tr><td>kr</td><td>korean encodings</td></tr>
2425	</table><p></p>	2232	</table><p></p>
2426	<dt><strong><a name="item__2d_2denable_2dxim">--enable-xim</a></strong><br />	2233	<dt><strong><a name="item_xim">--enable-xim (default: on)</a></strong><br />
2427	</dt>	2234	</dt>
2428	<dd>	2235	<dd>
2429	Add support for XIM (X Input Method) protocol. This allows using	2236	Add support for XIM (X Input Method) protocol. This allows using
2430	alternative input methods (e.g. kinput2) and will also correctly	2237	alternative input methods (e.g. kinput2) and will also correctly
2431	set up the input for people using dead keys or compose keys.	2238	set up the input for people using dead keys or compose keys.
2432	</dd>	2239	</dd>
2433	<p></p>	2240	<p></p>
2434	<dt><strong><a name="item__2d_2denable_2dunicode3">--enable-unicode3</a></strong><br />	2241	<dt><strong><a name="item_unicode3">--enable-unicode3 (default: off)</a></strong><br />
2435	</dt>	2242	</dt>
		2243	<dd>
		2244	Recommended to stay off unless you really need non-BMP characters.
2436	<dd>	2245	</dd>
		2246	<dd>
2437	Enable direct support for displaying unicode codepoints above	2247	<p>Enable direct support for displaying unicode codepoints above
2438	65535 (the basic multilingual page). This increases storage	2248	65535 (the basic multilingual page). This increases storage
2439	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2249	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2440	support these extra characters, but Xft does.	2250	support these extra characters, but Xft does.</p>
2441	</dd>	2251	</dd>
2442	<dd>	2252	<dd>
2443	<p>Please note that rxvt-unicode can store unicode code points &gt;65535	2253	<p>Please note that rxvt-unicode can store unicode code points &gt;65535
2444	even without this flag, but the number of such characters is	2254	even without this flag, but the number of such characters is
2445	limited to a view thousand (shared with combining characters,	2255	limited to a view thousand (shared with combining characters,
2446	see next switch), and right now rxvt-unicode cannot display them	2256	see next switch), and right now rxvt-unicode cannot display them
2447	(input/output and cut&amp;paste still work, though).</p>	2257	(input/output and cut&amp;paste still work, though).</p>
2448	</dd>	2258	</dd>
2449	<p></p>	2259	<p></p>
2450	<dt><strong><a name="item__2d_2denable_2dcombining">--enable-combining</a></strong><br />	2260	<dt><strong><a name="item_combining">--enable-combining (default: on)</a></strong><br />
2451	</dt>	2261	</dt>
2452	<dd>	2262	<dd>
2453	Enable automatic composition of combining characters into	2263	Enable automatic composition of combining characters into
2454	composite characters. This is required for proper viewing of text	2264	composite characters. This is required for proper viewing of text
2455	where accents are encoded as seperate unicode characters. This is	2265	where accents are encoded as seperate unicode characters. This is
2456	done by using precomposited characters when available or creating	2266	done by using precomposited characters when available or creating
2457	new pseudo-characters when no precomposed form exists.	2267	new pseudo-characters when no precomposed form exists.
2458	</dd>	2268	</dd>
2459	<dd>	2269	<dd>
2460	<p>Without --enable-unicode3, the number of additional precomposed	2270	<p>Without --enable-unicode3, the number of additional precomposed
2461	characters is rather limited (2048, if this is full, rxvt will use the	2271	characters is somewhat limited (the 6400 private use characters will be
2462	private use area, extending the number of combinations to 8448). With	2272	(ab-)used). With --enable-unicode3, no practical limit exists.</p>
2463	--enable-unicode3, no practical limit exists. This will also enable	2273	</dd>
2464	storage of characters &gt;65535.</p>	2274	<dd>
		2275	<p>This option will also enable storage (but not display) of characters
		2276	beyond plane 0 (&gt;65535) when --enable-unicode3 was not specified.</p>
2465	</dd>	2277	</dd>
2466	<dd>	2278	<dd>
2467	<p>The combining table also contains entries for arabic presentation forms,	2279	<p>The combining table also contains entries for arabic presentation forms,
2468	but these are not currently used. Bug me if you want these to be used.</p>	2280	but these are not currently used. Bug me if you want these to be used (and
		2281	tell me how these are to be used...).</p>
2469	</dd>	2282	</dd>
2470	<p></p>	2283	<p></p>
2471	<dt><strong><a name="item_fallback">--enable-fallback(=CLASS)</a></strong><br />	2284	<dt><strong><a name="item_fallback">--enable-fallback(=CLASS) (default: Rxvt)</a></strong><br />
2472	</dt>	2285	</dt>
2473	<dd>	2286	<dd>
2474	When reading resource settings, also read settings for class CLASS	2287	When reading resource settings, also read settings for class CLASS. To
2475	(default: Rxvt). To disable resource fallback use --disable-fallback.	2288	disable resource fallback use --disable-fallback.
2476	</dd>
2477	<p></p>
2478	<dt><strong><a name="item__2d_2dwith_2dres_2dname_3dname">--with-res-name=NAME</a></strong><br />
2479	</dt>
2480	<dd>	2289	</dd>
		2290	<p></p>
		2291	<dt><strong><a name="item_name">--with-res-name=NAME (default: urxvt)</a></strong><br />
		2292	</dt>
		2293	<dd>
2481	Use the given name (default: urxvt) as default application name when	2294	Use the given name as default application name when
2482	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2295	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2483	</dd>	2296	</dd>
2484	<p></p>	2297	<p></p>
2485	<dt><strong><a name="item__2d_2dwith_2dres_2dclass_3dclass">--with-res-class=CLASS</a></strong><br />	2298	<dt><strong><a name="item__2d_2dwith_2dres_2dclass_3dclass__2fdefault_3a_urx">--with-res-class=CLASS /default: URxvt)</a></strong><br />
2486	</dt>	2299	</dt>
2487	<dd>	2300	<dd>
2488	Use the given class (default: URxvt) as default application class	2301	Use the given class as default application class
2489	when reading resources. Specify --with-res-class=Rxvt to replace	2302	when reading resources. Specify --with-res-class=Rxvt to replace
2490	rxvt.	2303	rxvt.
2491	</dd>	2304	</dd>
2492	<p></p>	2305	<p></p>
2493	<dt><strong><a name="item__2d_2denable_2dutmp">--enable-utmp</a></strong><br />	2306	<dt><strong><a name="item_utmp">--enable-utmp (default: on)</a></strong><br />
2494	</dt>	2307	</dt>
2495	<dd>	2308	<dd>
2496	Write user and tty to utmp file (used by programs like <em>w</em>) at	2309	Write user and tty to utmp file (used by programs like <em>w</em>) at
2497	start of rxvt execution and delete information when rxvt exits.	2310	start of rxvt execution and delete information when rxvt exits.
2498	</dd>	2311	</dd>
2499	<p></p>	2312	<p></p>
2500	<dt><strong><a name="item__2d_2denable_2dwtmp">--enable-wtmp</a></strong><br />	2313	<dt><strong><a name="item_wtmp">--enable-wtmp (default: on)</a></strong><br />
2501	</dt>	2314	</dt>
2502	<dd>	2315	<dd>
2503	Write user and tty to wtmp file (used by programs like <em>last</em>) at	2316	Write user and tty to wtmp file (used by programs like <em>last</em>) at
2504	start of rxvt execution and write logout when rxvt exits. This	2317	start of rxvt execution and write logout when rxvt exits. This
2505	option requires --enable-utmp to also be specified.	2318	option requires --enable-utmp to also be specified.
2506	</dd>	2319	</dd>
2507	<p></p>	2320	<p></p>
2508	<dt><strong><a name="item__2d_2denable_2dlastlog">--enable-lastlog</a></strong><br />	2321	<dt><strong><a name="item_lastlog">--enable-lastlog (default: on)</a></strong><br />
2509	</dt>	2322	</dt>
2510	<dd>	2323	<dd>
2511	Write user and tty to lastlog file (used by programs like	2324	Write user and tty to lastlog file (used by programs like
2512	<em>lastlogin</em>) at start of rxvt execution. This option requires	2325	<em>lastlogin</em>) at start of rxvt execution. This option requires
2513	--enable-utmp to also be specified.	2326	--enable-utmp to also be specified.
2514	</dd>	2327	</dd>
2515	<p></p>	2328	<p></p>
2516	<dt><strong><a name="item__2d_2denable_2dxpm_2dbackground">--enable-xpm-background</a></strong><br />	2329	<dt><strong><a name="item_background">--enable-xpm-background (default: on)</a></strong><br />
2517	</dt>	2330	</dt>
2518	<dd>	2331	<dd>
2519	Add support for XPM background pixmaps.	2332	Add support for XPM background pixmaps.
2520	</dd>	2333	</dd>
2521	<p></p>	2334	<p></p>
2522	<dt><strong><a name="item__2d_2denable_2dtransparency">--enable-transparency</a></strong><br />	2335	<dt><strong><a name="item_transparency">--enable-transparency (default: on)</a></strong><br />
2523	</dt>	2336	</dt>
2524	<dd>	2337	<dd>
2525	Add support for inheriting parent backgrounds thus giving a fake	2338	Add support for inheriting parent backgrounds thus giving a fake
2526	transparency to the term.	2339	transparency to the term.
2527	</dd>	2340	</dd>
2528	<p></p>	2341	<p></p>
2529	<dt><strong><a name="item__2d_2denable_2dfading">--enable-fading</a></strong><br />	2342	<dt><strong><a name="item_fading">--enable-fading (default: on)</a></strong><br />
2530	</dt>	2343	</dt>
2531	<dd>
2532	Add support for fading the text when focus is lost.
2533	</dd>	2344	<dd>
2534	<p></p>	2345	Add support for fading the text when focus is lost (requires <code>--enable-transparency</code>).
2535	<dt><strong><a name="item__2d_2denable_2dtinting">--enable-tinting</a></strong><br />
2536	</dt>
2537	<dd>	2346	</dd>
2538	Add support for tinting of transparent backgrounds.	2347	<p></p>
		2348	<dt><strong><a name="item_tinting">--enable-tinting (default: on)</a></strong><br />
		2349	</dt>
2539	</dd>	2350	<dd>
2540	<p></p>	2351	Add support for tinting of transparent backgrounds (requires <code>--enable-transparency</code>).
2541	<dt><strong><a name="item__2d_2denable_2dmenubar">--enable-menubar</a></strong><br />
2542	</dt>
2543	<dd>	2352	</dd>
2544	Add support for our menu bar system (this interacts badly with
2545	dynamic locale switching currently).
2546	</dd>
2547	<p></p>	2353	<p></p>
2548	<dt><strong><a name="item__2d_2denable_2drxvt_2dscroll">--enable-rxvt-scroll</a></strong><br />	2354	<dt><strong><a name="item_scroll">--enable-rxvt-scroll (default: on)</a></strong><br />
2549	</dt>	2355	</dt>
2550	<dd>	2356	<dd>
2551	Add support for the original rxvt scrollbar.	2357	Add support for the original rxvt scrollbar.
2552	</dd>	2358	</dd>
2553	<p></p>	2359	<p></p>
2554	<dt><strong><a name="item__2d_2denable_2dnext_2dscroll">--enable-next-scroll</a></strong><br />	2360	<dt><strong>--enable-next-scroll (default: on)</strong><br />
2555	</dt>	2361	</dt>
2556	<dd>	2362	<dd>
2557	Add support for a NeXT-like scrollbar.	2363	Add support for a NeXT-like scrollbar.
2558	</dd>	2364	</dd>
2559	<p></p>	2365	<p></p>
2560	<dt><strong><a name="item__2d_2denable_2dxterm_2dscroll">--enable-xterm-scroll</a></strong><br />	2366	<dt><strong>--enable-xterm-scroll (default: on)</strong><br />
2561	</dt>	2367	</dt>
2562	<dd>	2368	<dd>
2563	Add support for an Xterm-like scrollbar.	2369	Add support for an Xterm-like scrollbar.
2564	</dd>	2370	</dd>
2565	<p></p>	2371	<p></p>
2566	<dt><strong><a name="item__2d_2denable_2dplain_2dscroll">--enable-plain-scroll</a></strong><br />	2372	<dt><strong>--enable-plain-scroll (default: on)</strong><br />
2567	</dt>	2373	</dt>
2568	<dd>	2374	<dd>
2569	Add support for a very unobtrusive, plain-looking scrollbar that	2375	Add support for a very unobtrusive, plain-looking scrollbar that
2570	is the favourite of the rxvt-unicode author, having used it for	2376	is the favourite of the rxvt-unicode author, having used it for
2571	many years.	2377	many years.
2572	</dd>	2378	</dd>
2573	<p></p>	2379	<p></p>
2574	<dt><strong><a name="item__2d_2denable_2dhalf_2dshadow">--enable-half-shadow</a></strong><br />
2575	</dt>
2576	<dd>
2577	Make shadows on the scrollbar only half the normal width &amp; height.
2578	only applicable to rxvt scrollbars.
2579	</dd>
2580	<p></p>
2581	<dt><strong><a name="item__2d_2denable_2dttygid">--enable-ttygid</a></strong><br />	2380	<dt><strong><a name="item_ttygid">--enable-ttygid (default: off)</a></strong><br />
2582	</dt>	2381	</dt>
2583	<dd>	2382	<dd>
2584	Change tty device setting to group ``tty'' - only use this if	2383	Change tty device setting to group ``tty'' - only use this if
2585	your system uses this type of security.	2384	your system uses this type of security.
2586	</dd>	2385	</dd>
2587	<p></p>	2386	<p></p>
2588	<dt><strong><a name="item__2d_2ddisable_2dbackspace_2dkey">--disable-backspace-key</a></strong><br />	2387	<dt><strong><a name="item__2d_2ddisable_2dbackspace_2dkey">--disable-backspace-key</a></strong><br />
2589	</dt>	2388	</dt>
2590	<dd>	2389	<dd>
2591	Disable any handling of the backspace key by us - let the X server	2390	Removes any handling of the backspace key by us - let the X server do it.
		2391	</dd>
		2392	<p></p>
		2393	<dt><strong><a name="item__2d_2ddisable_2ddelete_2dkey">--disable-delete-key</a></strong><br />
		2394	</dt>
		2395	<dd>
		2396	Removes any handling of the delete key by us - let the X server
2592	do it.	2397	do it.
2593	</dd>	2398	</dd>
2594	<p></p>	2399	<p></p>
2595	<dt><strong><a name="item__2d_2ddisable_2ddelete_2dkey">--disable-delete-key</a></strong><br />
2596	</dt>
2597	<dd>
2598	Disable any handling of the delete key by us - let the X server
2599	do it.
2600	</dd>
2601	<p></p>
2602	<dt><strong><a name="item__2d_2ddisable_2dresources">--disable-resources</a></strong><br />	2400	<dt><strong><a name="item__2d_2ddisable_2dresources">--disable-resources</a></strong><br />
2603	</dt>	2401	</dt>
2604	<dd>	2402	<dd>
2605	Remove all resources checking.	2403	Removes any support for resource checking.
2606	</dd>
2607	<p></p>
2608	<dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br />
2609	</dt>
2610	<dd>
2611	Make resources checking via <code>XGetDefault()</code> instead of our small
2612	version which only checks ~/.Xdefaults, or if that doesn't exist
2613	then ~/.Xresources.
2614	</dd>
2615	<p></p>
2616	<dt><strong><a name="item__2d_2denable_2dstrings">--enable-strings</a></strong><br />
2617	</dt>
2618	<dd>
2619	Add support for our possibly faster <code>memset()</code> function and other
2620	various routines, overriding your system's versions which may
2621	have been hand-crafted in assembly or may require extra libraries
2622	to link in. (this breaks ANSI-C rules and has problems on many
2623	GNU/Linux systems).
2624	</dd>	2404	</dd>
2625	<p></p>	2405	<p></p>
2626	<dt><strong><a name="item__2d_2ddisable_2dswapscreen">--disable-swapscreen</a></strong><br />	2406	<dt><strong><a name="item__2d_2ddisable_2dswapscreen">--disable-swapscreen</a></strong><br />
2627	</dt>	2407	</dt>
2628	<dd>	2408	<dd>
2629	Remove support for swap screen.	2409	Remove support for secondary/swap screen.
2630	</dd>	2410	</dd>
2631	<p></p>	2411	<p></p>
2632	<dt><strong><a name="item__2d_2denable_2dfrills">--enable-frills</a></strong><br />	2412	<dt><strong><a name="item_frills">--enable-frills (default: on)</a></strong><br />
2633	</dt>	2413	</dt>
2634	<dd>	2414	<dd>
2635	Add support for many small features that are not essential but nice to	2415	Add support for many small features that are not essential but nice to
2636	have. Normally you want this, but for very small binaries you may want to	2416	have. Normally you want this, but for very small binaries you may want to
2637	disable this.	2417	disable this.
2638	</dd>	2418	</dd>
2639	<dd>	2419	<dd>
2640	<p>A non-exhaustive list of features enabled by <a href="#item__2d_2denable_2dfrills"><code>--enable-frills</code></a> (possibly	2420	<p>A non-exhaustive list of features enabled by <code>--enable-frills</code> (possibly
2641	in combination with other switches) is:</p>	2421	in combination with other switches) is:</p>
2642	</dd>	2422	</dd>
2643	<dd>	2423	<dd>
2644	<pre>	2424	<pre>
2645	MWM-hints	2425	MWM-hints
		2426	EWMH-hints (pid, utf8 names) and protocols (ping)
2646	seperate underline colour	2427	seperate underline colour (-underlineColor)
2647	settable border widths and borderless switch	2428	settable border widths and borderless switch (-w, -b, -bl)
		2429	visual selection (-depth)
2648	settable extra linespacing	2430	settable extra linespacing /-lsp)
2649	extra window properties (e.g. UTF-8 window names and PID)
2650	iso-14755-2 and -3, and visual feedback	2431	iso-14755-2 and -3, and visual feedback
2651	backindex and forwardindex escape sequence	2432	backindex and forwardindex escape sequence
2652	window op and locale change escape sequences	2433	window op and some xterm/OSC escape sequences
2653	tripleclickwords	2434	tripleclickwords (-tcw)
2654	settable insecure mode</pre>	2435	settable insecure mode (-insecure)
		2436	keysym remapping support
		2437	cursor blinking and underline cursor (-cb, -uc)
		2438	XEmbed support (-embed)
		2439	user-pty (-pty-fd)
		2440	hold on exit (-hold)
		2441	skip builtin block graphics (-sbg)
		2442	sgr modes 90..97 and 100..107</pre>
2655	</dd>	2443	</dd>
2656	<p></p>	2444	<p></p>
2657	<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br />	2445	<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />
2658	</dt>	2446	</dt>
2659	<dd>	2447	<dd>
2660	Enable extended ISO 14755 support (see rxvt(1), or	2448	Enable extended ISO 14755 support (see rxvt(1), or
2661	<em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by	2449	<em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by
2662	<a href="#item__2d_2denable_2dfrills"><code>--enable-frills</code></a>, while support for 5.2, 5.3 and 5.4 is enabled with	2450	<code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with
2663	this switch.	2451	this switch.
2664	</dd>	2452	</dd>
2665	<p></p>	2453	<p></p>
2666	<dt><strong><a name="item__2d_2denable_2dkeepscrolling">--enable-keepscrolling</a></strong><br />	2454	<dt><strong><a name="item_keepscrolling">--enable-keepscrolling (default: on)</a></strong><br />
2667	</dt>	2455	</dt>
2668	<dd>	2456	<dd>
2669	Add support for continual scrolling of the display when you hold	2457	Add support for continual scrolling of the display when you hold
2670	the mouse button down on a scrollbar arrow.	2458	the mouse button down on a scrollbar arrow.
2671	</dd>	2459	</dd>
2672	<p></p>	2460	<p></p>
2673	<dt><strong><a name="item__2d_2denable_2dmousewheel">--enable-mousewheel</a></strong><br />	2461	<dt><strong><a name="item_mousewheel">--enable-mousewheel (default: on)</a></strong><br />
2674	</dt>	2462	</dt>
2675	<dd>	2463	<dd>
2676	Add support for scrolling via mouse wheel or buttons 4 &amp; 5.	2464	Add support for scrolling via mouse wheel or buttons 4 &amp; 5.
2677	</dd>	2465	</dd>
2678	<p></p>	2466	<p></p>
2679	<dt><strong><a name="item__2d_2denable_2dslipwheeling">--enable-slipwheeling</a></strong><br />	2467	<dt><strong><a name="item_slipwheeling">--enable-slipwheeling (default: on)</a></strong><br />
2680	</dt>	2468	</dt>
2681	<dd>	2469	<dd>
2682	Add support for continual scrolling (using the mouse wheel as an	2470	Add support for continual scrolling (using the mouse wheel as an
2683	accelerator) while the control key is held down. This option	2471	accelerator) while the control key is held down. This option
2684	requires --enable-mousewheel to also be specified.	2472	requires --enable-mousewheel to also be specified.
…		…
2688	</dt>	2476	</dt>
2689	<dd>	2477	<dd>
2690	Remove support for mouse selection style like that of xterm.	2478	Remove support for mouse selection style like that of xterm.
2691	</dd>	2479	</dd>
2692	<p></p>	2480	<p></p>
2693	<dt><strong><a name="item__2d_2denable_2ddmalloc">--enable-dmalloc</a></strong><br />	2481	<dt><strong><a name="item_dmalloc">--enable-dmalloc (default: off)</a></strong><br />
2694	</dt>	2482	</dt>
2695	<dd>	2483	<dd>
2696	Use Gray Watson's malloc - which is good for debugging See	2484	Use Gray Watson's malloc - which is good for debugging See
2697	<a href="http://www.letters.com/dmalloc/">http://www.letters.com/dmalloc/</a> for details If you use either this or the	2485	<a href="http://www.letters.com/dmalloc/">http://www.letters.com/dmalloc/</a> for details If you use either this or the
2698	next option, you may need to edit src/Makefile after compiling to point	2486	next option, you may need to edit src/Makefile after compiling to point
…		…
2701	<dd>	2489	<dd>
2702	<p>You can only use either this option and the following (should	2490	<p>You can only use either this option and the following (should
2703	you use either) .</p>	2491	you use either) .</p>
2704	</dd>	2492	</dd>
2705	<p></p>	2493	<p></p>
2706	<dt><strong><a name="item__2d_2denable_2ddlmalloc">--enable-dlmalloc</a></strong><br />	2494	<dt><strong><a name="item_dlmalloc">--enable-dlmalloc (default: off)</a></strong><br />
2707	</dt>	2495	</dt>
2708	<dd>	2496	<dd>
2709	Use Doug Lea's malloc - which is good for a production version	2497	Use Doug Lea's malloc - which is good for a production version
2710	See <a href="http://g.oswego.edu/dl/html/malloc.html">http://g.oswego.edu/dl/html/malloc.html</a> for details.	2498	See <a href="http://g.oswego.edu/dl/html/malloc.html">http://g.oswego.edu/dl/html/malloc.html</a> for details.
2711	</dd>	2499	</dd>
2712	<p></p>	2500	<p></p>
2713	<dt><strong><a name="item__2d_2denable_2dsmart_2dresize">--enable-smart-resize</a></strong><br />	2501	<dt><strong><a name="item_resize">--enable-smart-resize (default: on)</a></strong><br />
2714	</dt>	2502	</dt>
2715	<dd>	2503	<dd>
2716	Add smart growth/shrink behaviour when changing font size via from hot	2504	Add smart growth/shrink behaviour when changing font size via hot
2717	keys. This should keep in a fixed position the rxvt corner which is	2505	keys. This should keep the window corner which is closest to a corner of
2718	closest to a corner of the screen.	2506	the screen in a fixed position.
2719	</dd>
2720	<p></p>
2721	<dt><strong><a name="item__2d_2denable_2dcursor_2dblink">--enable-cursor-blink</a></strong><br />
2722	</dt>
2723	<dd>	2507	</dd>
2724	Add support for a blinking cursor.
2725	</dd>
2726	<p></p>	2508	<p></p>
2727	<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br />	2509	<dt><strong><a name="item_blank">--enable-pointer-blank (default: on)</a></strong><br />
2728	</dt>	2510	</dt>
2729	<dd>	2511	<dd>
2730	Add support to have the pointer disappear when typing or inactive.	2512	Add support to have the pointer disappear when typing or inactive.
2731	</dd>	2513	</dd>
2732	<p></p>	2514	<p></p>
2733	<dt><strong><a name="item__2d_2dwith_2dname_3dname">--with-name=NAME</a></strong><br />	2515	<dt><strong><a name="item_perl">--enable-perl (default: on)</a></strong><br />
2734	</dt>	2516	</dt>
		2517	<dd>
		2518	Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
		2519	manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files
		2520	in <em>src/perl-ext/</em> for the extensions that are installed by default. The
		2521	perl interpreter that is used can be specified via the <code>PERL</code> environment
		2522	variable when running configure.
2735	<dd>	2523	</dd>
		2524	<p></p>
		2525	<dt><strong>--with-name=NAME (default: urxvt)</strong><br />
		2526	</dt>
		2527	<dd>
2736	Set the basename for the installed binaries (default: <code>urxvt</code>, resulting	2528	Set the basename for the installed binaries, resulting
2737	in <code>urxvt</code>, <code>urxvtd</code> etc.). Specify <code>--with-name=rxvt</code> to replace with	2529	in <code>urxvt</code>, <code>urxvtd</code> etc.). Specify <code>--with-name=rxvt</code> to replace with
2738	<code>rxvt</code>.	2530	<code>rxvt</code>.
2739	</dd>	2531	</dd>
2740	<p></p>	2532	<p></p>
2741	<dt><strong><a name="item__2d_2dwith_2dterm_3dname">--with-term=NAME</a></strong><br />	2533	<dt><strong>--with-term=NAME (default: rxvt-unicode)</strong><br />
2742	</dt>	2534	</dt>
2743	<dd>	2535	<dd>
2744	Change the environmental variable for the terminal to NAME (default	2536	Change the environmental variable for the terminal to NAME.
2745	<code>rxvt-unicode</code>)
2746	</dd>	2537	</dd>
2747	<p></p>	2538	<p></p>
2748	<dt><strong><a name="item__2d_2dwith_2dterminfo_3dpath">--with-terminfo=PATH</a></strong><br />	2539	<dt><strong><a name="item__2d_2dwith_2dterminfo_3dpath">--with-terminfo=PATH</a></strong><br />
2749	</dt>	2540	</dt>
2750	<dd>	2541	<dd>

Diff Legend

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