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

Diff Legend

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