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.27 by root, Thu Dec 22 16:44:10 2005 UTC vs.
Revision 1.72 by root, Wed Feb 22 10:42:49 2006 UTC

…		…
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="#synopsis">SYNOPSIS</a></li>	16	<li><a href="#synopsis">SYNOPSIS</a></li>
17	<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>	18	<li><a href="#rxvtunicode_urxvt_frequently_asked_questions">RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS</a></li>
19	<li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li>
20	<li><a href="#description">DESCRIPTION</a></li>
21	<li><a href="#definitions">Definitions</a></li>
22	<li><a href="#values">Values</a></li>
23	<li><a href="#escape_sequences">Escape Sequences</a></li>
24	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
25	<li><a href="#dec_private_modes">DEC Private Modes</a></li>
26	<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>
27	<li><a href="#menubar">menuBar</a></li>
28	<ul>	19	<ul>
29		20
30	<li><a href="#overview_of_menubar_operation">Overview of menuBar operation</a></li>	21	<li><a href="#meta__features___commandline_issues">Meta, Features &amp; Commandline Issues</a></li>
		22	<ul>
		23
		24	<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>
		25	<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>
		26	<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>
		27	<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>
		28	<li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li>
		29	<li><a href="#how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></li>
		30	<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>
		31	<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>
		32	<li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li>
		33	<li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li>
		34	<li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li>
		35	</ul>
		36
		37	<li><a href="#rendering__font___look_and_feel_issues">Rendering, Font &amp; Look and Feel Issues</a></li>
		38	<ul>
		39
		40	<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>
		41	<li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li>
		42	<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>
		43	<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>
		44	<li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li>
		45	<li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li>
		46	<li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li>
		47	<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>
		48	<li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li>
		49	<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>
		50	<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>
		51	<li><a href="#how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></li>
		52	<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>
		53	</ul>
		54
		55	<li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></li>
		56	<ul>
		57
		58	<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>
		59	<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>
		60	<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>
		61	<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>
		62	<li><a href="#my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></li>
		63	<li><a href="#my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></li>
		64	<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>
		65	<li><a href="#mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></li>
		66	<li><a href="#what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></li>
		67	<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>
		68	<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_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></li>
		69	</ul>
		70
		71	<li><a href="#terminal_configuration">Terminal Configuration</a></li>
		72	<ul>
		73
		74	<li><a href="#can_i_see_a_typical_configuration">Can I see a typical configuration?</a></li>
		75	<li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li>
		76	<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>
		77	<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>
		78	<li><a href="#bash_s_readline_does_not_work_correctly_under_urxvt_"><code>bash</code>'s readline does not work correctly under urxvt.</a></li>
		79	<li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li>
		80	<li><a href="#why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></li>
		81	<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>
		82	<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>
		83	<li><a href="#why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></li>
		84	</ul>
		85
		86	<li><a href="#encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></li>
		87	<ul>
		88
		89	<li><a href="#rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></li>
		90	<li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</a></li>
		91	<li><a href="#how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></li>
		92	<li><a href="#is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></li>
		93	<li><a href="#can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></li>
		94	<li><a href="#i_have_problems_getting_my_input_method_working_">I have problems getting my input method working.</a></li>
		95	<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>
		96	<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>
		97	</ul>
		98
		99	<li><a href="#operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></li>
		100	<ul>
		101
		102	<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>
		103	<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>
		104	<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>
		105	<li><a href="#on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></li>
		106	<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>
		107	<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>
		108	<li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li>
		109	</ul>
		110
		111	</ul>
		112
		113	<li><a href="#rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></li>
		114	<ul>
		115
		116	<li><a href="#definitions">Definitions</a></li>
31	<li><a href="#commands">Commands</a></li>	117	<li><a href="#values">Values</a></li>
32	<li><a href="#adding_and_accessing_menus">Adding and accessing menus</a></li>	118	<li><a href="#escape_sequences">Escape Sequences</a></li>
33	<li><a href="#removing_menus">Removing menus</a></li>	119	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
34	<li><a href="#quick_arrows">Quick Arrows</a></li>	120	<li><a href="#dec_private_modes">DEC Private Modes</a></li>
35	<li><a href="#command_summary">Command Summary</a></li>	121	<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>
36	</ul>	122	</ul>
37		123
38	<li><a href="#xpm">XPM</a></li>	124	<li><a href="#xpm">XPM</a></li>
39	<li><a href="#mouse_reporting">Mouse Reporting</a></li>	125	<li><a href="#mouse_reporting">Mouse Reporting</a></li>
40	<li><a href="#key_codes">Key Codes</a></li>	126	<li><a href="#key_codes">Key Codes</a></li>
…		…
65	</p>	151	</p>
66	<hr />	152	<hr />
67	<h1><a name="description">DESCRIPTION</a></h1>	153	<h1><a name="description">DESCRIPTION</a></h1>
68	<p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	154	<p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
69	all escape sequences, and other background information.</p>	155	all escape sequences, and other background information.</p>
70	<p>The newest version of this document is	156	<p>The newest version of this document is also available on the World Wide Web at
71	also available on the World Wide Web at
72	<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>	157	<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>
73	<p>	158	<p>
74	</p>	159	</p>
75	<hr />	160	<hr />
76	<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>	161	<h1><a name="rxvtunicode_urxvt_frequently_asked_questions">RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS</a></h1>
77	<dl>	162	<p>
		163	</p>
		164	<h2><a name="meta__features___commandline_issues">Meta, Features &amp; Commandline Issues</a></h2>
		165	<p>
		166	</p>
		167	<h3><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></h3>
		168	<p>Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>,
		169	channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be
		170	interested in learning about new and exciting problems (but not FAQs :).</p>
		171	<p>
		172	</p>
		173	<h3><a name="does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></h3>
		174	<p>Beginning with version 7.3, there is a perl extension that implements a
		175	simple tabbed terminal. It is installed by default, so any of these should
		176	give you tabs:</p>
		177	<pre>
		178	urxvt -pe tabbed</pre>
		179	<pre>
		180	URxvt.perl-ext-common: default,tabbed</pre>
		181	<p>It will also work fine with tabbing functionality of many window managers
		182	or similar tabbing programs, and its embedding-features allow it to be
		183	embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or
		184	the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt
		185	(murxvt) terminal as an example embedding application.</p>
		186	<p>
		187	</p>
78	<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 />	188	<h3><a name="how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></h3>
79	</dt>
80	<dd>
81	The version number is displayed with the usage (-h). Also the escape	189	<p>The version number is displayed with the usage (-h). Also the escape
82	sequence <code>ESC [ 8 n</code> sets the window title to the version number.	190	sequence <code>ESC [ 8 n</code> sets the window title to the version number. When
83	</dd>	191	using the urxvtc client, the version displayed is that of the
84	<p></p>	192	daemon.</p>
85	<dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br />	193	<p>
86	</dt>	194	</p>
87	<dd>	195	<h3><a name="rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></h3>
88	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	196	<p>Rxvt-unicode tries to obey the rule of not charging you for something you
89	patches that considerably change the behaviour of rxvt-unicode. Before	197	don't use. One thing you should try is to configure out all settings that
90	reporting a bug to the original rxvt-unicode author please download and	198	you don't need, for example, Xft support is a resource hog by design,
91	install the genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>)	199	when used. Compiling it out ensures that no Xft font will be loaded
92	and try to reproduce the problem. If you cannot, chances are that the	200	accidentally when rxvt-unicode tries to find a font for your characters.</p>
93	problems are specific to Debian GNU/Linux, in which case it should be	201	<p>Also, many people (me included) like large windows and even larger
94	reported via the Debian Bug Tracking System (use <code>reportbug</code> to report	202	scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use
95	the bug).	203	6 bytes per screen cell. For a 160x?? window this amounts to almost a
96	</dd>	204	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
97	<dd>	205	use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as
98	<p>For other problems that also affect the Debian package, you can and	206	rxvt-unicode then uses 8 bytes per screen cell.</p>
99	probably should use the Debian BTS, too, because, after all, it's also a	207	<p>
100	bug in the Debian version and it serves as a reminder for other users that	208	</p>
101	might encounter the same issue.</p>	209	<h3><a name="how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></h3>
102	</dd>	210	<p>Try <code>urxvtd -f -o</code>, which tells urxvtd to open the
103	<p></p>	211	display, create the listening socket and then fork.</p>
104	<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 />	212	<p>
105	</dt>	213	</p>
106	<dd>	214	<h3><a name="how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></h3>
		215	<p>If you want to start urxvtd automatically whenever you run
		216	urxvtc and the daemon isn't running yet, use this script:</p>
		217	<pre>
		218	#!/bin/sh
		219	urxvtc &quot;$@&quot;
		220	if [ $? -eq 2 ]; then
		221	urxvtd -q -o -f
		222	urxvtc &quot;$@&quot;
		223	fi</pre>
		224	<p>This tries to create a new terminal, and if fails with exit status 2,
		225	meaning it couldn't connect to the daemon, it will start the daemon and
		226	re-run the command. Subsequent invocations of the script will re-use the
		227	existing daemon.</p>
		228	<p>
		229	</p>
		230	<h3><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></h3>
		231	<p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'',
		232	so you can check and see if that is set. Note that several programs, JED,
		233	slrn, Midnight Commander automatically check this variable to decide
		234	whether or not to use color.</p>
		235	<p>
		236	</p>
		237	<h3><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></h3>
		238	<p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		239	insecure mode then it is possible to use the following shell script
		240	snippets to correctly set the display. If your version of rxvt-unicode
		241	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		242	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		243	regular xterm.</p>
		244	<p>Courtesy of Chuck Blake &lt;<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>&gt; with the following shell script
		245	snippets:</p>
		246	<pre>
		247	# Bourne/Korn/POSIX family of shells:
		248	[ ${TERM:-foo} = foo ] &amp;&amp; TERM=xterm # assume an xterm if we don't know
		249	if [ ${TERM:-foo} = xterm ]; then
		250	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		251	echo -n '^[Z'
		252	read term_id
		253	stty icanon echo
		254	if [ &quot;&quot;${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		255	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		256	read DISPLAY # set it in our local shell
		257	fi
		258	fi</pre>
		259	<p>
		260	</p>
		261	<h3><a name="how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></h3>
		262	<p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>,
		263	one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to
		264	the doc subdirectory and enter <code>make alldoc</code>.</p>
		265	<p>
		266	</p>
		267	<h3><a name="isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></h3>
		268	<p>I often get asked about this, and I think, no, they didn't cause extra
		269	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
		270	that the urxvt binary is larger (due to some encoding tables always being
		271	compiled in), but it actually uses less memory (RSS) after startup. Even
		272	with <code>--disable-everything</code>, this comparison is a bit unfair, as many
		273	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		274	already in use in this mode.</p>
		275	<pre>
		276	text data bss drs rss filename
		277	98398 1664 24 15695 1824 rxvt --disable-everything
		278	188985 9048 66616 18222 1788 urxvt --disable-everything</pre>
		279	<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which <em>is</em> unfair, as this involves xft
		280	and full locale/XIM support which are quite bloaty inside libX11 and my
		281	libc), the two diverge, but not unreasnobaly so.</p>
		282	<pre>
		283	text data bss drs rss filename
		284	163431 2152 24 20123 2060 rxvt --enable-everything
		285	1035683 49680 66648 29096 3680 urxvt --enable-everything</pre>
		286	<p>The very large size of the text section is explained by the east-asian
		287	encoding tables, which, if unused, take up disk space but nothing else
		288	and can be compiled out unless you rely on X11 core fonts that use those
		289	encodings. The BSS size comes from the 64k emergency buffer that my c++
		290	compiler allocates (but of course doesn't use unless you are out of
		291	memory). Also, using an xft font instead of a core font immediately adds a
		292	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
		293	not used.</p>
		294	<p>Of course, due to every character using two or four bytes instead of one,
		295	a large scrollback buffer will ultimately make rxvt-unicode use more
		296	memory.</p>
		297	<p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
		298	still fares rather well. And compared to some monsters like gnome-terminal
		299	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
		300	43180k in daemons that stay around after exit, plus half a minute of
		301	startup time, including the hundreds of warnings it spits out), it fares
		302	extremely well *g*.</p>
		303	<p>
		304	</p>
		305	<h3><a name="why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></h3>
		306	<p>Is this a question? :) It comes up very often. The simple answer is: I had
		307	to write it, and C++ allowed me to write and maintain it in a fraction
		308	of the time and effort (which is a scarce resource for me). Put even
		309	shorter: It simply wouldn't exist without C++.</p>
		310	<p>My personal stance on this is that C++ is less portable than C, but in
		311	the case of rxvt-unicode this hardly matters, as its portability limits
		312	are defined by things like X11, pseudo terminals, locale support and unix
		313	domain sockets, which are all less portable than C++ itself.</p>
		314	<p>Regarding the bloat, see the above question: It's easy to write programs
		315	in C that use gobs of memory, an certainly possible to write programs in
		316	C++ that don't. C++ also often comes with large libraries, but this is
		317	not necessarily the case with GCC. Here is what rxvt links against on my
		318	system with a minimal config:</p>
		319	<pre>
		320	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		321	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)
		322	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)
		323	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
		324	<p>And here is rxvt-unicode:</p>
		325	<pre>
		326	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		327	libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		328	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)
		329	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)
		330	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
		331	<p>No large bloated libraries (of course, none were linked in statically),
		332	except maybe libX11 :)</p>
		333	<p>
		334	</p>
		335	<h2><a name="rendering__font___look_and_feel_issues">Rendering, Font &amp; Look and Feel Issues</a></h2>
		336	<p>
		337	</p>
		338	<h3><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></h3>
		339	<p>First of all, transparency isn't officially supported in rxvt-unicode, so
		340	you are mostly on your own. Do not bug the author about it (but you may
		341	bug everybody else). Also, if you can't get it working consider it a rite
		342	of passage: ... and you failed.</p>
		343	<p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option
		344	descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p>
		345	<p>1. Use inheritPixmap:</p>
		346	<pre>
		347	Esetroot wallpaper.jpg
		348	urxvt -ip -tint red -sh 40</pre>
		349	<p>That works. If you think it doesn't, you lack transparency and tinting
		350	support, or you are unable to read.</p>
		351	<p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		352	to use effects other than tinting and shading: Just shade/tint/whatever
		353	your picture with gimp or any other tool:</p>
		354	<pre>
		355	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		356	urxvt -pixmap background.xpm -pe automove-background</pre>
		357	<p>That works. If you think it doesn't, you lack XPM and Perl support, or you
		358	are unable to read.</p>
		359	<p>3. Use an ARGB visual:</p>
		360	<pre>
		361	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>
		362	<p>This requires XFT support, and the support of your X-server. If that
		363	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		364	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		365	bugfixes and workarounds for Xft and Xlib to make it work, but that
		366	doesn't mean that your WM has the required kludges in place.</p>
		367	<p>4. Use xcompmgr and let it do the job:</p>
		368	<pre>
		369	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		370	-set _NET_WM_WINDOW_OPACITY 0xc0000000</pre>
		371	<p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code>
		372	by other values to change the degree of opacity. If it doesn't work and
		373	your server crashes, you got to keep the pieces.</p>
		374	<p>
		375	</p>
		376	<h3><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h3>
		377	<p>Most fonts were not designed for terminal use, which means that character
		378	size varies a lot. A font that is otherwise fine for terminal use might
		379	contain some characters that are simply too wide. Rxvt-unicode will avoid
		380	these characters. For characters that are just ``a bit'' too wide a special
		381	``careful'' rendering mode is used that redraws adjacent characters.</p>
		382	<p>All of this requires that fonts do not lie about character sizes,
		383	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		384	box, and rxvt-unicode has no way of detecting this (the correct way is to
		385	ask for the character bounding box, which unfortunately is wrong in these
		386	cases).</p>
		387	<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,
		388	or the respective font. If you encounter this problem you might try using
		389	the <code>-lsp</code> option to give the font more height. If that doesn't work, you
		390	might be forced to use a different font.</p>
		391	<p>All of this is not a problem when using X11 core fonts, as their bounding
		392	box data is correct.</p>
		393	<p>
		394	</p>
		395	<h3><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></h3>
		396	<p>First of all, make sure you are running with the right terminal settings
		397	(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
		398	make sure you have specified colours for italic and bold, as otherwise
		399	rxvt-unicode might use reverse video to simulate the effect:</p>
		400	<pre>
		401	URxvt.colorBD: white
		402	URxvt.colorIT: green</pre>
		403	<p>
		404	</p>
		405	<h3><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></h3>
		406	<p>For some unexplainable reason, some rare programs assume a very weird
		407	colour palette when confronted with a terminal with more than the standard
		408	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		409	these programs not to assume non-ISO colours without very good reasons.</p>
		410	<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
		411	definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
		412	fix colours but keep you from using other rxvt-unicode features.</p>
		413	<p>
		414	</p>
		415	<h3><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h3>
		416	<p>Yes, using an escape sequence. Try something like this, which has the same
		417	effect as using the <code>-fn</code> switch, and takes effect immediately:</p>
		418	<pre>
		419	printf '\33]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
		420	<p>This is useful if you e.g. work primarily with japanese (and prefer a
		421	japanese font), but you have to switch to chinese temporarily, where
		422	japanese fonts would only be in your way.</p>
		423	<p>You can think of this as a kind of manual ISO-2022 switching.</p>
		424	<p>
		425	</p>
		426	<h3><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h3>
		427	<p>Many fonts have difficulties with italic characters and hinting. For
		428	example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
		429	Mono</code> completely fails in it's italic face. A workaround might be to
		430	enable freetype autohinting, i.e. like this:</p>
		431	<pre>
		432	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		433	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
		434	<p>
		435	</p>
		436	<h3><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h3>
		437	<p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		438	it is simply slow. If you still want Xft fonts you might try to disable
		439	antialiasing (by appending <code>:antialias=false</code>), which saves lots of
		440	memory and also speeds up rendering considerably.</p>
		441	<p>
		442	</p>
		443	<h3><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></h3>
		444	<p>Rxvt-unicode will use whatever you specify as a font. If it needs to
		445	fall back to it's default font search list it will prefer X11 core
		446	fonts, because they are small and fast, and then use Xft fonts. It has
		447	antialiasing disabled for most of them, because the author thinks they
		448	look best that way.</p>
		449	<p>If you want antialiasing, you have to specify the fonts manually.</p>
		450	<p>
		451	</p>
		452	<h3><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h3>
		453	<p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
		454	standard foreground colour.</p>
		455	<p>For the standard background colour, blinking will actually make the
		456	text blink when compiled with <code>--enable-blinking</code>. with standard
		457	colours. Without <code>--enable-blinking</code>, the blink attribute will be
		458	ignored.</p>
		459	<p>On ANSI colours, bold/blink attributes are used to set high-intensity
		460	foreground/background colors.</p>
		461	<p>color0-7 are the low-intensity colors.</p>
		462	<p>color8-15 are the corresponding high-intensity colors.</p>
		463	<p>
		464	</p>
		465	<h3><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></h3>
		466	<p>You can change the screen colors at run-time using <em>~/.Xdefaults</em>
		467	resources (or as long-options).</p>
		468	<p>Here are values that are supposed to resemble a VGA screen,
		469	including the murky brown that passes for low-intensity yellow:</p>
		470	<pre>
		471	URxvt.color0: #000000
		472	URxvt.color1: #A80000
		473	URxvt.color2: #00A800
		474	URxvt.color3: #A8A800
		475	URxvt.color4: #0000A8
		476	URxvt.color5: #A800A8
		477	URxvt.color6: #00A8A8
		478	URxvt.color7: #A8A8A8</pre>
		479	<pre>
		480	URxvt.color8: #000054
		481	URxvt.color9: #FF0054
		482	URxvt.color10: #00FF54
		483	URxvt.color11: #FFFF54
		484	URxvt.color12: #0000FF
		485	URxvt.color13: #FF00FF
		486	URxvt.color14: #00FFFF
		487	URxvt.color15: #FFFFFF</pre>
		488	<p>And here is a more complete set of non-standard colors.</p>
		489	<pre>
		490	URxvt.cursorColor: #dc74d1
		491	URxvt.pointerColor: #dc74d1
		492	URxvt.background: #0e0e0e
		493	URxvt.foreground: #4ad5e1
		494	URxvt.color0: #000000
		495	URxvt.color8: #8b8f93
		496	URxvt.color1: #dc74d1
		497	URxvt.color9: #dc74d1
		498	URxvt.color2: #0eb8c7
		499	URxvt.color10: #0eb8c7
		500	URxvt.color3: #dfe37e
		501	URxvt.color11: #dfe37e
		502	URxvt.color5: #9e88f0
		503	URxvt.color13: #9e88f0
		504	URxvt.color6: #73f7ff
		505	URxvt.color14: #73f7ff
		506	URxvt.color7: #e1dddd
		507	URxvt.color15: #e1dddd</pre>
		508	<p>They have been described (not by me) as ``pretty girly''.</p>
		509	<p>
		510	</p>
		511	<h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3>
		512	<p>See next entry.</p>
		513	<p>
		514	</p>
		515	<h3><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h3>
		516	<p>Most fonts do not contain the full range of Unicode, which is
		517	fine. Chances are that the font you (or the admin/package maintainer of
		518	your system/os) have specified does not cover all the characters you want
		519	to display.</p>
		520	<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement
		521	font. Often the result is fine, but sometimes the chosen font looks
		522	bad/ugly/wrong. Some fonts have totally strange characters that don't
		523	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		524	intelligence to detect that a specific glyph is wrong: it has to believe
		525	the font that the characters it claims to contain indeed look correct.</p>
		526	<p>In that case, select a font of your taste and add it to the font list,
		527	e.g.:</p>
		528	<pre>
		529	urxvt -fn basefont,font2,font3...</pre>
		530	<p>When rxvt-unicode sees a character, it will first look at the base
		531	font. If the base font does not contain the character, it will go to the
		532	next font, and so on. Specifying your own fonts will also speed up this
		533	search and use less resources within rxvt-unicode and the X-server.</p>
		534	<p>The only limitation is that none of the fonts may be larger than the base
		535	font, as the base font defines the terminal character cell size, which
		536	must be the same due to the way terminals work.</p>
		537	<p>
		538	</p>
		539	<h3><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h3>
		540	<p>This is because there is a difference between script and language --
		541	rxvt-unicode does not know which language the text that is output is,
		542	as it only knows the unicode character codes. If rxvt-unicode first
		543	sees a japanese/chinese character, it might choose a japanese font for
		544	display. Subsequent japanese characters will use that font. Now, many
		545	chinese characters aren't represented in japanese fonts, so when the first
		546	non-japanese character comes up, rxvt-unicode will look for a chinese font
		547	-- unfortunately at this point, it will still use the japanese font for
		548	chinese characters that are also in the japanese font.</p>
		549	<p>The workaround is easy: just tag a chinese font at the end of your font
		550	list (see the previous question). The key is to view the font list as
		551	a preference list: If you expect more japanese, list a japanese font
		552	first. If you expect more chinese, put a chinese font first.</p>
		553	<p>In the future it might be possible to switch language preferences at
		554	runtime (the internal data structure has no problem with using different
		555	fonts for the same character at the same time, but no interface for this
		556	has been designed yet).</p>
		557	<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>
		558	<p>
		559	</p>
		560	<h2><a name="keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></h2>
		561	<p>
		562	</p>
		563	<h3><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></h3>
		564	<p>If you want to select e.g. alphanumeric words, you can use the following
		565	setting:</p>
		566	<pre>
		567	URxvt.selection.pattern-0: ([[:word:]]+)</pre>
		568	<p>If you click more than twice, the selection will be extended
		569	more and more.</p>
		570	<p>To get a selection that is very similar to the old code, try this pattern:</p>
		571	<pre>
		572	URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>
		573	<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also
		574	selects words like the old code.</p>
		575	<p>
		576	</p>
		577	<h3><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></h3>
		578	<p>You can disable the perl extension completely by setting the
		579	<strong>perl-ext-common</strong> resource to the empty string, which also keeps
		580	rxvt-unicode from initialising perl, saving memory.</p>
		581	<p>If you only want to disable specific features, you first have to
		582	identify which perl extension is responsible. For this, read the section
		583	<strong>PREPACKAGED EXTENSIONS</strong> in the <code>urxvtperl(3)</code> manpage. For
		584	example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify
		585	this <strong>perl-ext-common</strong> resource:</p>
		586	<pre>
		587	URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>
		588	<p>This will keep the default extensions, but disable the two popup
		589	extensions. Some extensions can also be configured, for example,
		590	scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any
		591	other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>
		592	<pre>
		593	URxvt.searchable-scrollback: CM-s</pre>
		594	<p>
		595	</p>
		596	<h3><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></h3>
		597	<p>See next entry.</p>
		598	<p>
		599	</p>
		600	<h3><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></h3>
		601	<p>These are caused by the <code>readline</code> perl extension. Under normal
		602	circumstances, it will move your cursor around when you click into the
		603	line that contains it. It tries hard not to do this at the wrong moment,
		604	but when running a program that doesn't parse cursor movements or in some
		605	cases during rlogin sessions, it fails to detect this properly.</p>
		606	<p>You can permamently switch this feature off by disabling the <code>readline</code>
		607	extension:</p>
		608	<pre>
		609	URxvt.perl-ext-common: default,-readline</pre>
		610	<p>
		611	</p>
		612	<h3><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h3>
		613	<p>Some Debian GNUL/Linux users seem to have this problem, although no
		614	specific details were reported so far. It is possible that this is caused
		615	by the wrong <code>TERM</code> setting, although the details of wether and how
		616	this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
		617	keymap. See the answer to the previous question, and please report if that
		618	helped.</p>
		619	<p>
		620	</p>
		621	<h3><a name="my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></h3>
		622	<p>The most common causes for this are that either your locale is not set
		623	correctly, or you specified a <strong>preeditStyle</strong> that is not supported by
		624	your input method. For example, if you specified <strong>OverTheSpot</strong> and
		625	your input method (e.g. the default input method handling Compose keys)
		626	does not support this (for instance because it is not visual), then
		627	rxvt-unicode will continue without an input method.</p>
		628	<p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than
		629	one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p>
		630	<p>
		631	</p>
		632	<h3><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></h3>
		633	<p>Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on
		634	international keyboards) or simply use ISO 14755 support to your
		635	advantage, typing &lt;Ctrl-Shift-0&gt; to get a ASCII NUL. This works for other
		636	codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape
		637	character and so on.</p>
		638	<p>
		639	</p>
		640	<h3><a name="mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></h3>
		641	<p>Make sure that mouse reporting is actually turned off since killing
		642	some editors prematurely may leave the mouse in mouse report mode. I've
		643	heard that tcsh may use mouse reporting unless it otherwise specified. A
		644	quick check is to see if cut/paste works when the Alt or Shift keys are
		645	depressed.</p>
		646	<p>
		647	</p>
		648	<h3><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h3>
		649	<p>Assuming that the physical Backspace key corresponds to the
		650	BackSpace keysym (not likely for Linux ... see the following
		651	question) there are two standard values that can be used for
		652	Backspace: <code>^H</code> and <code>^?</code>.</p>
		653	<p>Historically, either value is correct, but rxvt-unicode adopts the debian
		654	policy of using <code>^?</code> when unsure, because it's the one only only correct
		655	choice :).</p>
		656	<p>Rxvt-unicode tries to inherit the current stty settings and uses the value
		657	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		658	started from a terminal (say, from a menu or by remote shell), then the
		659	system value of `erase', which corresponds to CERASE in &lt;termios.h&gt;, will
		660	be used (which may not be the same as your stty setting).</p>
		661	<p>For starting a new rxvt-unicode:</p>
		662	<pre>
		663	# use Backspace = ^H
		664	$ stty erase ^H
		665	$ urxvt</pre>
		666	<pre>
		667	# use Backspace = ^?
		668	$ stty erase ^?
		669	$ urxvt</pre>
		670	<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p>
		671	<p>For an existing rxvt-unicode:</p>
		672	<pre>
		673	# use Backspace = ^H
		674	$ stty erase ^H
		675	$ echo -n &quot;^[[36h&quot;</pre>
		676	<pre>
		677	# use Backspace = ^?
		678	$ stty erase ^?
		679	$ echo -n &quot;^[[36l&quot;</pre>
		680	<p>This helps satisfy some of the Backspace discrepancies that occur, but
		681	if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value
		682	properly reflects that.</p>
		683	<p>The Delete key is a another casualty of the ill-defined Backspace problem.
		684	To avoid confusion between the Backspace and Delete keys, the Delete
		685	key has been assigned an escape sequence to match the vt100 for Execute
		686	(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
		687	<p>Some other Backspace problems:</p>
		688	<p>some editors use termcap/terminfo,
		689	some editors (vim I'm told) expect Backspace = ^H,
		690	GNU Emacs (and Emacs-like editors) use ^H for help.</p>
		691	<p>Perhaps someday this will all be resolved in a consistent manner.</p>
		692	<p>
		693	</p>
		694	<h3><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></h3>
		695	<p>There are some compile-time selections available via configure. Unless
		696	you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
		697	use the `keysym' resource to alter the keystrings associated with keysyms.</p>
		698	<p>Here's an example for a URxvt session started using <code>urxvt -name URxvt</code></p>
		699	<pre>
		700	URxvt.keysym.Home: \033[1~
		701	URxvt.keysym.End: \033[4~
		702	URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
		703	URxvt.keysym.C-slash: \033&lt;C-/&gt;
		704	URxvt.keysym.C-semicolon: \033&lt;C-;&gt;
		705	URxvt.keysym.C-grave: \033&lt;C-`&gt;
		706	URxvt.keysym.C-comma: \033&lt;C-,&gt;
		707	URxvt.keysym.C-period: \033&lt;C-.&gt;
		708	URxvt.keysym.C-0x60: \033&lt;C-`&gt;
		709	URxvt.keysym.C-Tab: \033&lt;C-Tab&gt;
		710	URxvt.keysym.C-Return: \033&lt;C-Return&gt;
		711	URxvt.keysym.S-Return: \033&lt;S-Return&gt;
		712	URxvt.keysym.S-space: \033&lt;S-Space&gt;
		713	URxvt.keysym.M-Up: \033&lt;M-Up&gt;
		714	URxvt.keysym.M-Down: \033&lt;M-Down&gt;
		715	URxvt.keysym.M-Left: \033&lt;M-Left&gt;
		716	URxvt.keysym.M-Right: \033&lt;M-Right&gt;
		717	URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
		718	URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
		719	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
		720	<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
		721	<p>
		722	</p>
		723	<h3><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_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></h3>
		724	<pre>
		725	KP_Insert == Insert
		726	F22 == Print
		727	F27 == Home
		728	F29 == Prior
		729	F33 == End
		730	F35 == Next</pre>
		731	<p>Rather than have rxvt-unicode try to accommodate all the various possible
		732	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		733	required for your particular machine.</p>
		734	<p>
		735	</p>
		736	<h2><a name="terminal_configuration">Terminal Configuration</a></h2>
		737	<p>
		738	</p>
		739	<h3><a name="can_i_see_a_typical_configuration">Can I see a typical configuration?</a></h3>
		740	<p>The default configuration tries to be xterm-like, which I don't like that
		741	much, but it's least surprise to regular users.</p>
		742	<p>As a rxvt or rxvt-unicode user, you are practically supposed to invest
		743	time into customising your terminal. To get you started, here is the
		744	author's .Xdefaults entries, with comments on what they do. It's certainly
		745	not <em>typical</em>, but what's typical...</p>
		746	<pre>
		747	URxvt.cutchars: &quot;()*,&lt;&gt;[]{}|'
		748	URxvt.print-pipe: cat &gt;/tmp/xxx</pre>
		749	<p>These are just for testing stuff.</p>
		750	<pre>
		751	URxvt.imLocale: ja_JP.UTF-8
		752	URxvt.preeditType: OnTheSpot,None</pre>
		753	<p>This tells rxvt-unicode to use a special locale when communicating with
		754	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		755	type, which requires the <code>xim-onthespot</code> perl extension but rewards me
		756	with correct-looking fonts.</p>
		757	<pre>
		758	URxvt.perl-lib: /root/lib/urxvt
		759	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		760	URxvt.selection.pattern-0: ( at .*? line \\d+)
		761	URxvt.selection.pattern-1: ^(/[^:]+):\
		762	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		763	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/</pre>
		764	<p>This is my perl configuration. The first two set the perl library
		765	directory and also tells urxvt to use a large number of extensions. I
		766	develop for myself mostly, so I actually use most of the extensions I
		767	write.</p>
		768	<p>The selection stuff mainly makes the selection perl-error-message aware
		769	and tells it to convert pelr error mssages into vi-commands to load the
		770	relevant file and go tot he error line number.</p>
		771	<pre>
		772	URxvt.scrollstyle: plain
		773	URxvt.secondaryScroll: true</pre>
		774	<p>As the documentation says: plain is the preferred scrollbar for the
		775	author. The <code>secondaryScroll</code> confgiures urxvt to scroll in full-screen
		776	apps, like screen, so lines scorlled out of screen end up in urxvt's
		777	scrollback buffer.</p>
		778	<pre>
		779	URxvt.background: #000000
		780	URxvt.foreground: gray90
		781	URxvt.color7: gray90
		782	URxvt.colorBD: #ffffff
		783	URxvt.cursorColor: #e0e080
		784	URxvt.throughColor: #8080f0
		785	URxvt.highlightColor: #f0f0f0</pre>
		786	<p>Some colours. Not sure which ones are being used or even non-defaults, but
		787	these are in my .Xdefaults. Most notably, they set foreground/background
		788	to light gray/black, and also make sure that the colour 7 matches the
		789	default foreground colour.</p>
		790	<pre>
		791	URxvt.underlineColor: yellow</pre>
		792	<p>Another colour, makes underline lines look different. Sometimes hurts, but
		793	is mostly a nice effect.</p>
		794	<pre>
		795	URxvt.geometry: 154x36
		796	URxvt.loginShell: false
		797	URxvt.meta: ignore
		798	URxvt.utmpInhibit: true</pre>
		799	<p>Uh, well, should be mostly self-explanatory. By specifying some defaults
		800	manually, I can quickly switch them for testing.</p>
		801	<pre>
		802	URxvt.saveLines: 8192</pre>
		803	<p>A large scrollback buffer is essential. Really.</p>
		804	<pre>
		805	URxvt.mapAlert: true</pre>
		806	<p>The only case I use it is for my IRC window, which I like to keep
		807	iconified till people msg me (which beeps).</p>
		808	<pre>
		809	URxvt.visualBell: true</pre>
		810	<p>The audible bell is often annoying, especially when in a crowd.</p>
		811	<pre>
		812	URxvt.insecure: true</pre>
		813	<p>Please don't hack my mutt! Ooops...</p>
		814	<pre>
		815	URxvt.pastableTabs: false</pre>
		816	<p>I once thought this is a great idea.</p>
		817	<pre>
		818	urxvt.font: 9x15bold,\
		819	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		820	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		821	[codeset=JISX0208]xft:Kochi Gothic, \
		822	xft:Bitstream Vera Sans Mono:autohint=true, \
		823	xft:Code2000:antialias=false
		824	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		825	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		826	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
		827	<p>I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		828	overwhelmed. A special note: the <code>9x15bold</code> mentioend above is actually
		829	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		830	font (different glyphs for <code>;</code> and many other harmless characters),
		831	while the second font is actually the <code>9x15bold</code> from XFree4/XOrg. The
		832	bold version has less chars than the medium version, so I use it for rare
		833	characters, too. Whene ditign sources with vim, I use italic for comments
		834	and other stuff, which looks quite good with Bitstream Vera anti-aliased.</p>
		835	<p>Terminus is a quite bad font (many very wrong glyphs), but for most of my
		836	purposes, it works, and gives a different look, as my normal (Non-bold)
		837	font is already bold, and I want to see a difference between bold and
		838	normal fonts.</p>
		839	<p>Please note that I used the <code>urxvt</code> instance name and not the <code>URxvt</code>
		840	class name. Thats because I use different configs for different purposes,
		841	for example, my IRC window is started with <code>-name IRC</code>, and uses these
		842	defaults:</p>
		843	<pre>
		844	IRC*title: IRC
		845	IRC*geometry: 87x12+535+542
		846	IRC*saveLines: 0
		847	IRC*mapAlert: true
		848	IRC*font: suxuseuro
		849	IRC*boldFont: suxuseuro
		850	IRC*colorBD: white
		851	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		852	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007</pre>
		853	<p><code>Alt-Shift-1</code> and <code>Alt-Shift-2</code> switch between two different font
		854	sizes. <code>suxuseuro</code> allows me to keep an eye (and actually read)
		855	stuff while keeping a very small window. If somebody pastes something
		856	complicated (e.g. japanese), I temporarily switch to a larger font.</p>
		857	<p>The above is all in my <code>.Xdefaults</code> (I don't use <code>.Xresources</code> nor
		858	<code>xrdb</code>). I also have some resources in a separate <code>.Xdefaults-hostname</code>
		859	file for different hosts, for example, on ym main desktop, I use:</p>
		860	<pre>
		861	URxvt.keysym.C-M-q: command:\033[3;5;5t
		862	URxvt.keysym.C-M-y: command:\033[3;5;606t
		863	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		864	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		865	URxvt.keysym.C-M-p: perl:test</pre>
		866	<p>The first for keysym definitions allow me to quickly bring some windows
		867	in the layout I like most. Ion users might start laughing but will stop
		868	immediately when I tell them that I use my own Fvwm2 module for much the
		869	same effect as Ion provides, and I only very rarely use the above key
		870	combinations :-&gt;</p>
		871	<p>
		872	</p>
		873	<h3><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h3>
		874	<p>Well, why, indeed? It does, in a way very similar to other X
		875	applications. Most importantly, this means that if you or your OS loads
		876	resources into the X display (the right way to do it), rxvt-unicode will
		877	ignore any resource files in your home directory. It will only read
		878	<em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p>
		879	<p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that
		880	resources are loaded into your X-server. In this case, you have to
		881	re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p>
		882	<p>Also consider the form resources have to use:</p>
		883	<pre>
		884	URxvt.resource: value</pre>
		885	<p>If you want to use another form (there are lots of different ways of
		886	specifying resources), make sure you understand wether and why it
		887	works. If unsure, use the form above.</p>
		888	<p>
		889	</p>
		890	<h3><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></h3>
107	The terminal description used by rxvt-unicode is not as widely available	891	<p>The terminal description used by rxvt-unicode is not as widely available
108	as that for xterm, or even rxvt (for which the same problem often arises).	892	as that for xterm, or even rxvt (for which the same problem often arises).</p>
109	</dd>
110	<dd>
111	<p>The correct solution for this problem is to install the terminfo, this can	893	<p>The correct solution for this problem is to install the terminfo, this can
112	be done like this (with ncurses' infocmp):</p>	894	be done like this (with ncurses' infocmp):</p>
113	</dd>
114	<dd>
115	<pre>	895	<pre>
116	REMOTE=remotesystem.domain	896	REMOTE=remotesystem.domain
117	infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre>	897	infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre>
118	</dd>
119	<dd>
120	<p>... or by installing rxvt-unicode normally on the remote system,</p>	898	<p>... or by installing rxvt-unicode normally on the remote system,</p>
121	</dd>
122	<dd>
123	<p>If you cannot or do not want to do this, then you can simply set	899	<p>If you cannot or do not want to do this, then you can simply set
124	<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of	900	<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of
125	problems arising, which includes wrong keymapping, less and different	901	problems arising, which includes wrong keymapping, less and different
126	colours and some refresh errors in fullscreen applications. It's a nice	902	colours and some refresh errors in fullscreen applications. It's a nice
127	quick-and-dirty workaround for rare cases, though.</p>	903	quick-and-dirty workaround for rare cases, though.</p>
128	</dd>
129	<dd>
130	<p>If you always want to do this (and are fine with the consequences) you	904	<p>If you always want to do this (and are fine with the consequences) you
131	can either recompile rxvt-unicode with the desired TERM value or use a	905	can either recompile rxvt-unicode with the desired TERM value or use a
132	resource to set it:</p>	906	resource to set it:</p>
133	</dd>
134	<dd>
135	<pre>	907	<pre>
136	URxvt.termName: rxvt</pre>	908	URxvt.termName: rxvt</pre>
137	</dd>
138	<dd>
139	<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace	909	<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace
140	the rxvt terminfo file with the rxvt-unicode one.</p>	910	the rxvt terminfo file with the rxvt-unicode one and use <code>TERM=rxvt</code>.</p>
141	</dd>	911	<p>
142	<p></p>	912	</p>
143	<dt><strong><a name="item_tic_outputs_some_error_when_compiling_the_terminfo"><code>tic</code> outputs some error when compiling the terminfo entry.</a></strong><br />	913	<h3><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h3>
144	</dt>
145	<dd>
146	Most likely it's the empty definition for <code>enacs=</code>. Just replace it by	914	<p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
147	<code>enacs=\E[0@</code> and try again.	915	<code>enacs=\E[0@</code> and try again.</p>
148	</dd>	916	<p>
149	<p></p>	917	</p>
150	<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br />	918	<h3><a name="bash_s_readline_does_not_work_correctly_under_urxvt_"><code>bash</code>'s readline does not work correctly under urxvt.</a></h3>
151	</dt>	919	<p>See next entry.</p>
		920	<p>
		921	</p>
152	<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />	922	<h3><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h3>
153	</dt>
154	<dd>
155	One reason you might want this is that some distributions or operating	923	<p>One reason you might want this is that some distributions or operating
156	systems still compile some programs using the long-obsoleted termcap	924	systems still compile some programs using the long-obsoleted termcap
157	library (Fedora Core's bash is one example) and rely on a termcap entry	925	library (Fedora Core's bash is one example) and rely on a termcap entry
158	for <code>rxvt-unicode</code>.	926	for <code>rxvt-unicode</code>.</p>
159	</dd>
160	<dd>
161	<p>You could use rxvt's termcap entry with resonable results in many cases.	927	<p>You could use rxvt's termcap entry with resonable results in many cases.
162	You can also create a termcap entry by using terminfo's infocmp program	928	You can also create a termcap entry by using terminfo's infocmp program
163	like this:</p>	929	like this:</p>
164	</dd>
165	<dd>
166	<pre>	930	<pre>
167	infocmp -C rxvt-unicode</pre>	931	infocmp -C rxvt-unicode</pre>
168	</dd>
169	<dd>
170	<p>Or you could use this termcap entry, generated by the command above:</p>	932	<p>Or you could use this termcap entry, generated by the command above:</p>
171	</dd>
172	<dd>
173	<pre>	933	<pre>
174	rxvt-unicode|rxvt-unicode terminal (X Window System):\	934	rxvt-unicode|rxvt-unicode terminal (X Window System):\
175	:am:bw:eo:km:mi:ms:xn:xo:\	935	:am:bw:eo:km:mi:ms:xn:xo:\
176	:co#80:it#8:li#24:lm#0:\	936	:co#80:it#8:li#24:lm#0:\
177	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	937	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
…		…
189	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\	949	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
190	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	950	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
191	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	951	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
192	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	952	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
193	:vs=\E[?25h:</pre>	953	:vs=\E[?25h:</pre>
194	</dd>	954	<p>
195	<p></p>	955	</p>
196	<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 />	956	<h3><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h3>
197	</dt>
198	<dd>
199	The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to	957	<p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to
200	decide wether a terminal has colour, but uses it's own configuration	958	decide wether a terminal has colour, but uses it's own configuration
201	file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among	959	file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among
202	with most other terminals supporting colour). Either add:	960	with most other terminals supporting colour). Either add:</p>
203	</dd>
204	<dd>
205	<pre>	961	<pre>
206	TERM rxvt-unicode</pre>	962	TERM rxvt-unicode</pre>
207	</dd>
208	<dd>
209	<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>	963	<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>
210	</dd>
211	<dd>
212	<pre>	964	<pre>
213	alias ls='ls --color=auto'</pre>	965	alias ls='ls --color=auto'</pre>
214	</dd>
215	<dd>
216	<p>to your <code>.profile</code> or <code>.bashrc</code>.</p>	966	<p>to your <code>.profile</code> or <code>.bashrc</code>.</p>
217	</dd>	967	<p>
218	<p></p>	968	</p>
219	<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 />	969	<h3><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></h3>
220	</dt>	970	<p>See next entry.</p>
		971	<p>
		972	</p>
221	<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 />	973	<h3><a name="why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></h3>
222	</dt>	974	<p>See next entry.</p>
		975	<p>
		976	</p>
223	<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 />	977	<h3><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h3>
224	</dt>
225	<dd>
226	Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged	978	<p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged
227	distributions (most notably Debian GNU/Linux) break rxvt-unicode	979	distributions (most notably Debian GNU/Linux) break rxvt-unicode
228	by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra	980	by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra
229	features. Unfortunately, some of these (most notably, again, Debian	981	features. Unfortunately, some of these (most notably, again, Debian
230	GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo	982	GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo
231	file, so you will need to install it on your own (See the question <strong>When	983	file, so you will need to install it on your own (See the question <strong>When
232	I log-in to another system it tells me about missing terminfo data?</strong> on	984	I log-in to another system it tells me about missing terminfo data?</strong> on
233	how to do this).	985	how to do this).</p>
234	</dd>	986	<p>
235	<p></p>	987	</p>
236	<dt><strong><a name="item_my_numerical_keypad_acts_weird_and_generates_diffe">My numerical keypad acts weird and generates differing output?</a></strong><br />	988	<h2><a name="encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></h2>
237	</dt>	989	<p>
238	<dd>	990	</p>
239	Some Debian GNUL/Linux users seem to have this problem, although no
240	specific details were reported so far. It is possible that this is caused
241	by the wrong <code>TERM</code> setting, although the details of wether and how
242	this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
243	keymap. See the answer to the previous question, and please report if that
244	helped.
245	</dd>
246	<p></p>
247	<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 />	991	<h3><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h3>
248	</dt>	992	<p>See next entry.</p>
		993	<p>
		994	</p>
249	<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br />	995	<h3><a name="unicode_does_not_seem_to_work">Unicode does not seem to work?</a></h3>
250	</dt>
251	<dd>
252	If you encounter strange problems like typing an accented character but	996	<p>If you encounter strange problems like typing an accented character but
253	getting two unrelated other characters or similar, or if program output is	997	getting two unrelated other characters or similar, or if program output is
254	subtly garbled, then you should check your locale settings.	998	subtly garbled, then you should check your locale settings.</p>
255	</dd>
256	<dd>
257	<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the	999	<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the
258	programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the	1000	programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the
259	login script running within the rxvt-unicode window changes the locale to	1001	login script running within the rxvt-unicode window changes the locale to
260	something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>	1002	something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>
261	</dd>
262	<dd>
263	<p>The best thing is to fix your startup environment, as you will likely run	1003	<p>The best thing is to fix your startup environment, as you will likely run
264	into other problems. If nothing works you can try this in your .profile.</p>	1004	into other problems. If nothing works you can try this in your .profile.</p>
265	</dd>
266	<dd>
267	<pre>	1005	<pre>
268	printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre>	1006	printf '\33]701;%s\007' &quot;$LC_CTYPE&quot;</pre>
269	</dd>
270	<dd>
271	<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not	1007	<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not
272	supported on your systems. Some systems have a <code>locale</code> command which	1008	supported on your systems. Some systems have a <code>locale</code> command which
273	displays this (also, <code>perl -e0</code> can be used to check locale settings, as	1009	displays this (also, <code>perl -e0</code> can be used to check locale settings, as
274	it will complain loudly if it cannot set the locale). If it displays something	1010	it will complain loudly if it cannot set the locale). If it displays something
275	like:</p>	1011	like:</p>
276	</dd>
277	<dd>
278	<pre>	1012	<pre>
279	locale: Cannot set LC_CTYPE to default locale: ...</pre>	1013	locale: Cannot set LC_CTYPE to default locale: ...</pre>
280	</dd>
281	<dd>
282	<p>Then the locale you specified is not supported on your system.</p>	1014	<p>Then the locale you specified is not supported on your system.</p>
283	</dd>
284	<dd>
285	<p>If nothing works and you are sure that everything is set correctly then	1015	<p>If nothing works and you are sure that everything is set correctly then
286	you will need to remember a little known fact: Some programs just don't	1016	you will need to remember a little known fact: Some programs just don't
287	support locales :(</p>	1017	support locales :(</p>
		1018	<p>
		1019	</p>
		1020	<h3><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h3>
		1021	<p>See next entry.</p>
		1022	<p>
		1023	</p>
		1024	<h3><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h3>
		1025	<p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		1026	specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about
		1027	UTF-8 or any other encodings with respect to terminal I/O.</p>
		1028	<p>The reasons is that there exists a perfectly fine mechanism for selecting
		1029	the encoding, doing I/O and (most important) communicating this to all
		1030	applications so everybody agrees on character properties such as width
		1031	and code number. This mechanism is the <em>locale</em>. Applications not using
		1032	that info will have problems (for example, <code>xterm</code> gets the width of
		1033	characters wrong as it uses it's own, locale-independent table under all
		1034	locales).</p>
		1035	<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
		1036	programs doing the same (that is, most) will automatically agree in the
		1037	interpretation of characters.</p>
		1038	<p>Unfortunately, there is no system-independent way to select locales, nor
		1039	is there a standard on how locale specifiers will look like.</p>
		1040	<p>On most systems, the content of the <code>LC_CTYPE</code> environment variable
		1041	contains an arbitrary string which corresponds to an already-installed
		1042	locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>,
		1043	<code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms
		1044	(i.e. <code>de</code> or <code>german</code>) are also common.</p>
		1045	<p>Rxvt-unicode ignores all other locale categories, and except for
		1046	the encoding, ignores country or language-specific settings,
		1047	i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
		1048	rxvt-unicode.</p>
		1049	<p>If you want to use a specific encoding you have to make sure you start
		1050	rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
		1051	<p>
		1052	</p>
		1053	<h3><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h3>
		1054	<p>Yes, using an escape sequence. Try something like this, which sets
		1055	rxvt-unicode's idea of <code>LC_CTYPE</code>.</p>
		1056	<pre>
		1057	printf '\33]701;%s\007' ja_JP.SJIS</pre>
		1058	<p>See also the previous answer.</p>
		1059	<p>Sometimes this capability is rather handy when you want to work in
		1060	one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
		1061	(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
		1062	first switches to a locale supported by xjdic and back later:</p>
		1063	<pre>
		1064	printf '\33]701;%s\007' ja_JP.SJIS
		1065	xjdic -js
		1066	printf '\33]701;%s\007' de_DE.UTF-8</pre>
		1067	<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
		1068	for some locales where character width differs between program- and
		1069	rxvt-unicode-locales.</p>
		1070	<p>
		1071	</p>
		1072	<h3><a name="i_have_problems_getting_my_input_method_working_">I have problems getting my input method working.</a></h3>
		1073	<p>Try a search engine, as this is slightly different for every input method server.</p>
		1074	<p>Here is a checklist:</p>
		1075	<dl>
		1076	<dt><strong><a name="item__2d_make_sure_your_locale_and_the_imlocale_are_sup">- Make sure your locale <em>and</em> the imLocale are supported on your OS.</a></strong><br />
		1077	</dt>
288	</dd>	1078	<dd>
289	<p></p>	1079	Try <code>locale -a</code> or check the documentation for your OS.
290	<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 />
291	</dt>
292	<dt><strong><a name="item_how_does_rxvt_2dunicode_choose_fonts_3f">How does rxvt-unicode choose fonts?</a></strong><br />
293	</dt>
294	<dd>	1080	</dd>
295	Most fonts do not contain the full range of Unicode, which is	1081	<p></p>
296	fine. Chances are that the font you (or the admin/package maintainer of	1082	<dt><strong><a name="item__2d_make_sure_your_locale_or_imlocale_matches_a_lo">- Make sure your locale or imLocale matches a locale supported by your XIM.</a></strong><br />
297	your system/os) have specified does not cover all the characters you want	1083	</dt>
298	to display.
299	</dd>	1084	<dd>
		1085	For example, <strong>kinput2</strong> does not support UTF-8 locales, you should use
		1086	<code>ja_JP.EUC-JP</code> or equivalent.
300	<dd>	1087	</dd>
301	<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement	1088	<p></p>
302	font. Often the result is fine, but sometimes the chosen font looks	1089	<dt><strong><a name="item__2d_make_sure_your_xim_server_is_actually_running_">- Make sure your XIM server is actually running.</a></strong><br />
303	bad/ugly/wrong. Some fonts have totally strange characters that don't	1090	</dt>
304	resemble the correct glyph at all, and rxvt-unicode lacks the artificial	1091	<dt><strong><a name="item__2d_make_sure_the_xmodifiers_environment_variable_">- Make sure the <code>XMODIFIERS</code> environment variable is set correctly when <em>starting</em> rxvt-unicode.</a></strong><br />
305	intelligence to detect that a specific glyph is wrong: it has to believe	1092	</dt>
306	the font that the characters it claims to contain indeed look correct.</p>
307	</dd>	1093	<dd>
		1094	When you want to use e.g. <strong>kinput2</strong>, it must be set to
		1095	<code>@im=kinput2</code>. For <strong>scim</strong>, use <code>@im=SCIM</code>. Youc an see what input
		1096	method servers are running with this command:
308	<dd>	1097	</dd>
309	<p>In that case, select a font of your taste and add it to the font list,
310	e.g.:</p>
311	</dd>	1098	<dd>
		1099	<pre>
		1100	xprop -root XIM_SERVERS</pre>
312	<dd>	1101	</dd>
313	<pre>	1102	<p></p>
314	rxvt -fn basefont,font2,font3...</pre>	1103	<dt></dt>
315	</dd>	1104	</dl>
316	<dd>	1105	<p>
317	<p>When rxvt-unicode sees a character, it will first look at the base	1106	</p>
318	font. If the base font does not contain the character, it will go to the	1107	<h3><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></h3>
319	next font, and so on. Specifying your own fonts will also speed up this	1108	<p>You can specify separate locales for the input method and the rest of the
320	search and use less resources within rxvt-unicode and the X-server.</p>	1109	terminal, using the resource <code>imlocale</code>:</p>
321	</dd>	1110	<pre>
322	<dd>	1111	URxvt.imlocale: ja_JP.EUC-JP</pre>
323	<p>The only limitation is that none of the fonts may be larger than the base	1112	<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
324	font, as the base font defines the terminal character cell size, which	1113	use your input method. Please note, however, that, depending on your Xlib
325	must be the same due to the way terminals work.</p>	1114	version, you may not be able to input characters outside <code>EUC-JP</code> in a
326	</dd>	1115	normal way then, as your input method limits you.</p>
327	<p></p>	1116	<p>
328	<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 />	1117	</p>
329	</dt>	1118	<h3><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h3>
330	<dd>	1119	<p>Unfortunately, this is unavoidable, as the XIM protocol is racy by
331	This is because there is a difference between script and language --	1120	design. Applications can avoid some crashes at the expense of memory
332	rxvt-unicode does not know which language the text that is output is,	1121	leaks, and Input Methods can avoid some crashes by careful ordering at
333	as it only knows the unicode character codes. If rxvt-unicode first	1122	exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
334	sees a japanese/chinese character, it might choose a japanese font for	1123	while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
335	display. Subsequent japanese characters will use that font. Now, many	1124	crashes cannot be completely avoided even if both sides cooperate.</p>
336	chinese characters aren't represented in japanese fonts, so when the first	1125	<p>So the only workaround is not to kill your Input Method Servers.</p>
337	non-japanese character comes up, rxvt-unicode will look for a chinese font	1126	<p>
338	-- unfortunately at this point, it will still use the japanese font for	1127	</p>
339	chinese characters that are also in the japanese font.	1128	<h2><a name="operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></h2>
340	</dd>	1129	<p>
341	<dd>	1130	</p>
342	<p>The workaround is easy: just tag a chinese font at the end of your font	1131	<h3><a name="i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></h3>
343	list (see the previous question). The key is to view the font list as	1132	<p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large
344	a preference list: If you expect more japanese, list a japanese font	1133	patches that considerably change the behaviour of rxvt-unicode (but
345	first. If you expect more chinese, put a chinese font first.</p>	1134	unfortunately this notice has been removed). Before reporting a bug to
346	</dd>	1135	the original rxvt-unicode author please download and install the genuine
347	<dd>	1136	version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce
348	<p>In the future it might be possible to switch language preferences at	1137	the problem. If you cannot, chances are that the problems are specific to
349	runtime (the internal data structure has no problem with using different	1138	Debian GNU/Linux, in which case it should be reported via the Debian Bug
350	fonts for the same character at the same time, but no interface for this	1139	Tracking System (use <code>reportbug</code> to report the bug).</p>
351	has been designed yet).</p>	1140	<p>For other problems that also affect the Debian package, you can and
352	</dd>	1141	probably should use the Debian BTS, too, because, after all, it's also a
353	<dd>	1142	bug in the Debian version and it serves as a reminder for other users that
354	<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>	1143	might encounter the same issue.</p>
355	</dd>	1144	<p>
356	<p></p>	1145	</p>
357	<dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br />	1146	<h3><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h3>
358	</dt>	1147	<p>You should build one binary with the default options. <em>configure</em>
359	<dd>	1148	now enables most useful options, and the trend goes to making them
360	Most fonts were not designed for terminal use, which means that character	1149	runtime-switchable, too, so there is usually no drawback to enbaling them,
361	size varies a lot. A font that is otherwise fine for terminal use might	1150	except higher disk and possibly memory usage. The perl interpreter should
362	contain some characters that are simply too wide. Rxvt-unicode will avoid	1151	be enabled, as important functionality (menus, selection, likely more in
363	these characters. For characters that are just ``a bit'' too wide a special	1152	the future) depends on it.</p>
364	``careful'' rendering mode is used that redraws adjacent characters.	1153	<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
365	</dd>	1154	system-wide (except maybe with <code>defaults</code>). This will result in useful
366	<dd>	1155	behaviour. If your distribution aims at low memory, add an empty
367	<p>All of this requires that fonts do not lie about character sizes,	1156	<code>perl-ext-common</code> resource to the app-defaults file. This will keep the
368	however: Xft fonts often draw glyphs larger than their acclaimed bounding	1157	perl interpreter disabled until the user enables it.</p>
369	box, and rxvt-unicode has no way of detecting this (the correct way is to	1158	<p>If you can/want build more binaries, I recommend building a minimal
370	ask for the character bounding box, which unfortunately is wrong in these	1159	one with <code>--disable-everything</code> (very useful) and a maximal one with
371	cases).</p>	1160	<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of
372	</dd>	1161	encodings built-in that increase download times and are rarely used).</p>
373	<dd>	1162	<p>
374	<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,	1163	</p>
375	or the respective font. If you encounter this problem you might try using	1164	<h3><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></h3>
376	the <code>-lsp</code> option to give the font more height. If that doesn't work, you	1165	<p>It should be, starting with release 7.1. You are encouraged to properly
377	might be forced to use a different font.</p>	1166	install urxvt with privileges necessary for your OS now.</p>
378	</dd>	1167	<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork
379	<dd>	1168	into a helper process for privileged operations (pty handling on some
380	<p>All of this is not a problem when using X11 core fonts, as their bounding	1169	systems, utmp/wtmp/lastlog handling on others) and drop privileges
381	box data is correct.</p>	1170	immediately. This is much safer than most other terminals that keep
382	</dd>	1171	privileges while running (but is more relevant to urxvt, as it contains
383	<p></p>	1172	things as perl interpreters, which might be ``helpful'' to attackers).</p>
		1173	<p>This forking is done as the very first within main(), which is very early
		1174	and reduces possible bugs to initialisation code run before main(), or
		1175	things like the dynamic loader of your system, which should result in very
		1176	little risk.</p>
		1177	<p>
		1178	</p>
384	<dt><strong><a name="item_on_solaris_9_2c_many_line_2ddrawing_characters_are">On Solaris 9, many line-drawing characters are too wide.</a></strong><br />	1179	<h3><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h3>
385	</dt>
386	<dd>
387	Seems to be a known bug, read	1180	<p>Seems to be a known bug, read
388	<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the	1181	<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the
389	following ugly workaround to get non-double-wide-characters working:	1182	following ugly workaround to get non-double-wide-characters working:</p>
390	</dd>
391	<dd>
392	<pre>	1183	<pre>
393	#define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>	1184	#define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>
394	</dd>
395	<p></p>
396	<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br />
397	</dt>
398	<dd>
399	The most common causes for this are that either your locale is not set
400	correctly, or you specified a <strong>preeditStyle</strong> that is not supported by
401	your input method. For example, if you specified <strong>OverTheSpot</strong> and
402	your input method (e.g. the default input method handling Compose keys)
403	does not support this (for instance because it is not visual), then
404	rxvt-unicode will continue without an input method.
405	</dd>
406	<dd>
407	<p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than
408	one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p>
409	</dd>
410	<p></p>
411	<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 />
412	</dt>
413	<dd>
414	Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on
415	international keyboards) or simply use ISO 14755 support to your
416	advantage, typing &lt;Ctrl-Shift-0&gt; to get a ASCII NUL. This works for other
417	codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape
418	character and so on.
419	</dd>
420	<p></p>
421	<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 />
422	</dt>
423	<dd>
424	First of all, make sure you are running with the right terminal settings
425	(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
426	make sure you have specified colours for italic and bold, as otherwise
427	rxvt-unicode might use reverse video to simulate the effect:
428	</dd>
429	<dd>
430	<pre>	1185	<p>
431	URxvt.colorBD: white	1186	</p>
432	URxvt.colorIT: green</pre>
433	</dd>
434	<p></p>
435	<dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br />
436	</dt>
437	<dd>
438	For some unexplainable reason, some rare programs assume a very weird
439	colour palette when confronted with a terminal with more than the standard
440	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
441	these programs not to assume non-ISO colours without very good reasons.
442	</dd>
443	<dd>
444	<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
445	definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
446	fix colours but keep you from using other rxvt-unicode features.</p>
447	</dd>
448	<p></p>
449	<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 />	1187	<h3><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></h3>
450	</dt>
451	<dd>
452	Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined	1188	<p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined
453	in your compile environment, or an implementation that implements it,	1189	in your compile environment, or an implementation that implements it,
454	wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that	1190	wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that
455	<strong>wchar_t</strong> is represented as unicode.	1191	<strong>wchar_t</strong> is represented as unicode.</p>
456	</dd>
457	<dd>
458	<p>As you might have guessed, FreeBSD does neither define this symobl nor	1192	<p>As you might have guessed, FreeBSD does neither define this symobl nor
459	does it support it. Instead, it uses it's own internal representation of	1193	does it support it. Instead, it uses it's own internal representation of
460	<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>	1194	<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
461	</dd>
462	<dd>
463	<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and	1195	<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
464	<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>	1196	<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
465	</dd>
466	<dd>
467	<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language	1197	<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
468	apps in an OS, as using a locale-dependent (and non-standardized)	1198	apps in an OS, as using a locale-dependent (and non-standardized)
469	representation of <strong>wchar_t</strong> makes it impossible to convert between	1199	representation of <strong>wchar_t</strong> makes it impossible to convert between
470	<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding	1200	<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding
471	without implementing OS-specific-wrappers for each and every locale. There	1201	without implementing OS-specific-wrappers for each and every locale. There
472	simply are no APIs to convert <strong>wchar_t</strong> into anything except the current	1202	simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
473	locale encoding.</p>	1203	locale encoding.</p>
474	</dd>
475	<dd>
476	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this	1204	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
477	by carrying their own replacement functions for character set handling	1205	by carrying their own replacement functions for character set handling
478	with them, and either implementing OS-dependent hacks or doing multiple	1206	with them, and either implementing OS-dependent hacks or doing multiple
479	conversions (which is slow and unreliable in case the OS implements	1207	conversions (which is slow and unreliable in case the OS implements
480	encodings slightly different than the terminal emulator).</p>	1208	encodings slightly different than the terminal emulator).</p>
481	</dd>
482	<dd>
483	<p>The rxvt-unicode author insists that the right way to fix this is in the	1209	<p>The rxvt-unicode author insists that the right way to fix this is in the
484	system libraries once and for all, instead of forcing every app to carry	1210	system libraries once and for all, instead of forcing every app to carry
485	complete replacements for them :)</p>	1211	complete replacements for them :)</p>
486	</dd>	1212	<p>
487	<p></p>	1213	</p>
488	<dt><strong><a name="item_i_use_solaris_9_and_it_doesn_27t_compile_2fwork_2f">I use Solaris 9 and it doesn't compile/work/etc.</a></strong><br />	1214	<h3><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></h3>
489	</dt>
490	<dd>
491	Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst	1215	<p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
492	problems with <code>wcwidth</code> and a compile problem.	1216	problems with <code>wcwidth</code> and a compile problem.</p>
493	</dd>	1217	<p>
494	<p></p>	1218	</p>
495	<dt><strong><a name="item_how_can_i_use_rxvt_2dunicode_under_cygwin_3f">How can I use rxvt-unicode under cygwin?</a></strong><br />	1219	<h3><a name="how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></h3>
496	</dt>
497	<dd>
498	rxvt-unicode should compile and run out of the box on cygwin, using	1220	<p>rxvt-unicode should compile and run out of the box on cygwin, using
499	the X11 libraries that come with cygwin. libW11 emulation is no	1221	the X11 libraries that come with cygwin. libW11 emulation is no
500	longer supported (and makes no sense, either, as it only supported a	1222	longer supported (and makes no sense, either, as it only supported a
501	single font). I recommend starting the X-server in <code>-multiwindow</code> or	1223	single font). I recommend starting the X-server in <code>-multiwindow</code> or
502	<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the	1224	<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
503	old libW11 emulation.	1225	old libW11 emulation.</p>
504	</dd>
505	<dd>
506	<p>At the time of this writing, cygwin didn't seem to support any multi-byte	1226	<p>At the time of this writing, cygwin didn't seem to support any multi-byte
507	encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited	1227	encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
508	to 8-bit encodings.</p>	1228	to 8-bit encodings.</p>
509	</dd>
510	<p></p>
511	<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 />
512	</dt>
513	<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />
514	</dt>
515	<dd>
516	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
517	specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about
518	UTF-8 or any other encodings with respect to terminal I/O.
519	</dd>
520	<dd>
521	<p>The reasons is that there exists a perfectly fine mechanism for selecting
522	the encoding, doing I/O and (most important) communicating this to all
523	applications so everybody agrees on character properties such as width
524	and code number. This mechanism is the <em>locale</em>. Applications not using
525	that info will have problems (for example, <code>xterm</code> gets the width of
526	characters wrong as it uses it's own, locale-independent table under all
527	locales).</p>
528	</dd>
529	<dd>
530	<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
531	programs doing the same (that is, most) will automatically agree in the
532	interpretation of characters.</p>
533	</dd>
534	<dd>
535	<p>Unfortunately, there is no system-independent way to select locales, nor
536	is there a standard on how locale specifiers will look like.</p>
537	</dd>
538	<dd>
539	<p>On most systems, the content of the <code>LC_CTYPE</code> environment variable
540	contains an arbitrary string which corresponds to an already-installed
541	locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>,
542	<code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms
543	(i.e. <code>de</code> or <code>german</code>) are also common.</p>
544	</dd>
545	<dd>
546	<p>Rxvt-unicode ignores all other locale categories, and except for
547	the encoding, ignores country or language-specific settings,
548	i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
549	rxvt-unicode.</p>
550	</dd>
551	<dd>
552	<p>If you want to use a specific encoding you have to make sure you start
553	rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
554	</dd>
555	<p></p>
556	<dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br />
557	</dt>
558	<dd>
559	Yes, using an escape sequence. Try something like this, which sets
560	rxvt-unicode's idea of <code>LC_CTYPE</code>.
561	</dd>
562	<dd>
563	<pre>
564	printf '\e]701;%s\007' ja_JP.SJIS</pre>
565	</dd>
566	<dd>
567	<p>See also the previous answer.</p>
568	</dd>
569	<dd>
570	<p>Sometimes this capability is rather handy when you want to work in
571	one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
572	(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
573	first switches to a locale supported by xjdic and back later:</p>
574	</dd>
575	<dd>
576	<pre>
577	printf '\e]701;%s\007' ja_JP.SJIS
578	xjdic -js
579	printf '\e]701;%s\007' de_DE.UTF-8</pre>
580	</dd>
581	<dd>
582	<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
583	for some locales where character width differs between program- and
584	rxvt-unicode-locales.</p>
585	</dd>
586	<p></p>
587	<dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br />
588	</dt>
589	<dd>
590	Yes, using an escape sequence. Try something like this, which has the same
591	effect as using the <code>-fn</code> switch, and takes effect immediately:
592	</dd>
593	<dd>
594	<pre>
595	printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
596	</dd>
597	<dd>
598	<p>This is useful if you e.g. work primarily with japanese (and prefer a
599	japanese font), but you have to switch to chinese temporarily, where
600	japanese fonts would only be in your way.</p>
601	</dd>
602	<dd>
603	<p>You can think of this as a kind of manual ISO-2022 switching.</p>
604	</dd>
605	<p></p>
606	<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 />
607	</dt>
608	<dd>
609	Many fonts have difficulties with italic characters and hinting. For
610	example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
611	Mono</code> completely fails in it's italic face. A workaround might be to
612	enable freetype autohinting, i.e. like this:
613	</dd>
614	<dd>
615	<pre>
616	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
617	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
618	</dd>
619	<p></p>
620	<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 />
621	</dt>
622	<dd>
623	You can specify separate locales for the input method and the rest of the
624	terminal, using the resource <code>imlocale</code>:
625	</dd>
626	<dd>
627	<pre>
628	URxvt*imlocale: ja_JP.EUC-JP</pre>
629	</dd>
630	<dd>
631	<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
632	use your input method. Please note, however, that you will not be able to
633	input characters outside <code>EUC-JP</code> in a normal way then, as your input
634	method limits you.</p>
635	</dd>
636	<p></p>
637	<dt><strong><a name="item_rxvt_2dunicode_crashes_when_the_x_input_method_cha">Rxvt-unicode crashes when the X Input Method changes or exits.</a></strong><br />
638	</dt>
639	<dd>
640	Unfortunately, this is unavoidable, as the XIM protocol is racy by
641	design. Applications can avoid some crashes at the expense of memory
642	leaks, and Input Methods can avoid some crashes by careful ordering at
643	exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
644	while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
645	crashes cannot be completely avoided even if both sides cooperate.
646	</dd>
647	<dd>
648	<p>So the only workaround is not to kill your Input Method Servers.</p>
649	</dd>
650	<p></p>
651	<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 />
652	</dt>
653	<dd>
654	Rxvt-unicode tries to obey the rule of not charging you for something you
655	don't use. One thing you should try is to configure out all settings that
656	you don't need, for example, Xft support is a resource hog by design,
657	when used. Compiling it out ensures that no Xft font will be loaded
658	accidentally when rxvt-unicode tries to find a font for your characters.
659	</dd>
660	<dd>
661	<p>Also, many people (me included) like large windows and even larger
662	scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use
663	6 bytes per screen cell. For a 160x?? window this amounts to almost a
664	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
665	use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as
666	rxvt-unicode then uses 8 bytes per screen cell.</p>
667	</dd>
668	<p></p>
669	<dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br />
670	</dt>
671	<dd>
672	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
673	it is simply slow. If you still want Xft fonts you might try to disable
674	antialiasing (by appending <code>:antialias=false</code>), which saves lots of
675	memory and also speeds up rendering considerably.
676	</dd>
677	<p></p>
678	<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 />
679	</dt>
680	<dd>
681	Rxvt-unicode will use whatever you specify as a font. If it needs to
682	fall back to it's default font search list it will prefer X11 core
683	fonts, because they are small and fast, and then use Xft fonts. It has
684	antialiasing disabled for most of them, because the author thinks they
685	look best that way.
686	</dd>
687	<dd>
688	<p>If you want antialiasing, you have to specify the fonts manually.</p>
689	</dd>
690	<p></p>
691	<dt><strong><a name="item_mouse_cut_2fpaste_suddenly_no_longer_works_2e">Mouse cut/paste suddenly no longer works.</a></strong><br />
692	</dt>
693	<dd>
694	Make sure that mouse reporting is actually turned off since killing
695	some editors prematurely may leave the mouse in mouse report mode. I've
696	heard that tcsh may use mouse reporting unless it otherwise specified. A
697	quick check is to see if cut/paste works when the Alt or Shift keys are
698	depressed. See <code>rxvt(7)</code>
699	</dd>
700	<p></p>
701	<dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br />
702	</dt>
703	<dd>
704	If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
705	standard foreground colour.
706	</dd>
707	<dd>
708	<p>For the standard background colour, blinking will actually make the
709	text blink when compiled with <code>--enable-blinking</code>. with standard
710	colours. Without <code>--enable-blinking</code>, the blink attribute will be
711	ignored.</p>
712	</dd>
713	<dd>
714	<p>On ANSI colours, bold/blink attributes are used to set high-intensity
715	foreground/background colors.</p>
716	</dd>
717	<dd>
718	<p>color0-7 are the low-intensity colors.</p>
719	</dd>
720	<dd>
721	<p>color8-15 are the corresponding high-intensity colors.</p>
722	</dd>
723	<p></p>
724	<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 />
725	</dt>
726	<dd>
727	You can change the screen colors at run-time using <em>~/.Xdefaults</em>
728	resources (or as long-options).
729	</dd>
730	<dd>
731	<p>Here are values that are supposed to resemble a VGA screen,
732	including the murky brown that passes for low-intensity yellow:</p>
733	</dd>
734	<dd>
735	<pre>
736	URxvt.color0: #000000
737	URxvt.color1: #A80000
738	URxvt.color2: #00A800
739	URxvt.color3: #A8A800
740	URxvt.color4: #0000A8
741	URxvt.color5: #A800A8
742	URxvt.color6: #00A8A8
743	URxvt.color7: #A8A8A8</pre>
744	</dd>
745	<dd>
746	<pre>
747	URxvt.color8: #000054
748	URxvt.color9: #FF0054
749	URxvt.color10: #00FF54
750	URxvt.color11: #FFFF54
751	URxvt.color12: #0000FF
752	URxvt.color13: #FF00FF
753	URxvt.color14: #00FFFF
754	URxvt.color15: #FFFFFF</pre>
755	</dd>
756	<dd>
757	<p>And here is a more complete set of non-standard colors described (not by
758	me) as ``pretty girly''.</p>
759	</dd>
760	<dd>
761	<pre>
762	URxvt.cursorColor: #dc74d1
763	URxvt.pointerColor: #dc74d1
764	URxvt.background: #0e0e0e
765	URxvt.foreground: #4ad5e1
766	URxvt.color0: #000000
767	URxvt.color8: #8b8f93
768	URxvt.color1: #dc74d1
769	URxvt.color9: #dc74d1
770	URxvt.color2: #0eb8c7
771	URxvt.color10: #0eb8c7
772	URxvt.color3: #dfe37e
773	URxvt.color11: #dfe37e
774	URxvt.color5: #9e88f0
775	URxvt.color13: #9e88f0
776	URxvt.color6: #73f7ff
777	URxvt.color14: #73f7ff
778	URxvt.color7: #e1dddd
779	URxvt.color15: #e1dddd</pre>
780	</dd>
781	<p></p>
782	<dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br />
783	</dt>
784	<dd>
785	Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
786	display, create the listening socket and then fork.
787	</dd>
788	<p></p>
789	<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 />
790	</dt>
791	<dd>
792	Assuming that the physical Backspace key corresponds to the
793	BackSpace keysym (not likely for Linux ... see the following
794	question) there are two standard values that can be used for
795	Backspace: <code>^H</code> and <code>^?</code>.
796	</dd>
797	<dd>
798	<p>Historically, either value is correct, but rxvt-unicode adopts the debian
799	policy of using <code>^?</code> when unsure, because it's the one only only correct
800	choice :).</p>
801	</dd>
802	<dd>
803	<p>Rxvt-unicode tries to inherit the current stty settings and uses the value
804	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
805	started from a terminal (say, from a menu or by remote shell), then the
806	system value of `erase', which corresponds to CERASE in &lt;termios.h&gt;, will
807	be used (which may not be the same as your stty setting).</p>
808	</dd>
809	<dd>
810	<p>For starting a new rxvt-unicode:</p>
811	</dd>
812	<dd>
813	<pre>
814	# use Backspace = ^H
815	$ stty erase ^H
816	$ rxvt</pre>
817	</dd>
818	<dd>
819	<pre>
820	# use Backspace = ^?
821	$ stty erase ^?
822	$ rxvt</pre>
823	</dd>
824	<dd>
825	<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in rxvt(7).</p>
826	</dd>
827	<dd>
828	<p>For an existing rxvt-unicode:</p>
829	</dd>
830	<dd>
831	<pre>
832	# use Backspace = ^H
833	$ stty erase ^H
834	$ echo -n &quot;^[[36h&quot;</pre>
835	</dd>
836	<dd>
837	<pre>
838	# use Backspace = ^?
839	$ stty erase ^?
840	$ echo -n &quot;^[[36l&quot;</pre>
841	</dd>
842	<dd>
843	<p>This helps satisfy some of the Backspace discrepancies that occur, but
844	if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value
845	properly reflects that.</p>
846	</dd>
847	<dd>
848	<p>The Delete key is a another casualty of the ill-defined Backspace problem.
849	To avoid confusion between the Backspace and Delete keys, the Delete
850	key has been assigned an escape sequence to match the vt100 for Execute
851	(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
852	</dd>
853	<dd>
854	<p>Some other Backspace problems:</p>
855	</dd>
856	<dd>
857	<p>some editors use termcap/terminfo,
858	some editors (vim I'm told) expect Backspace = ^H,
859	GNU Emacs (and Emacs-like editors) use ^H for help.</p>
860	</dd>
861	<dd>
862	<p>Perhaps someday this will all be resolved in a consistent manner.</p>
863	</dd>
864	<p></p>
865	<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 />
866	</dt>
867	<dd>
868	There are some compile-time selections available via configure. Unless
869	you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
870	use the `keysym' resource to alter the keystrings associated with keysyms.
871	</dd>
872	<dd>
873	<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p>
874	</dd>
875	<dd>
876	<pre>
877	URxvt.keysym.Home: \033[1~
878	URxvt.keysym.End: \033[4~
879	URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
880	URxvt.keysym.C-slash: \033&lt;C-/&gt;
881	URxvt.keysym.C-semicolon: \033&lt;C-;&gt;
882	URxvt.keysym.C-grave: \033&lt;C-`&gt;
883	URxvt.keysym.C-comma: \033&lt;C-,&gt;
884	URxvt.keysym.C-period: \033&lt;C-.&gt;
885	URxvt.keysym.C-0x60: \033&lt;C-`&gt;
886	URxvt.keysym.C-Tab: \033&lt;C-Tab&gt;
887	URxvt.keysym.C-Return: \033&lt;C-Return&gt;
888	URxvt.keysym.S-Return: \033&lt;S-Return&gt;
889	URxvt.keysym.S-space: \033&lt;S-Space&gt;
890	URxvt.keysym.M-Up: \033&lt;M-Up&gt;
891	URxvt.keysym.M-Down: \033&lt;M-Down&gt;
892	URxvt.keysym.M-Left: \033&lt;M-Left&gt;
893	URxvt.keysym.M-Right: \033&lt;M-Right&gt;
894	URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
895	URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
896	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
897	</dd>
898	<dd>
899	<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
900	</dd>
901	<p></p>
902	<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.
903	How do I make use of them? For example, the Sun Keyboard type 4
904	has the following mappings that rxvt-unicode doesn't recognize.</a></strong><br />
905	</dt>
906	<dd>
907	<pre>
908	KP_Insert == Insert
909	F22 == Print
910	F27 == Home
911	F29 == Prior
912	F33 == End
913	F35 == Next</pre>
914	</dd>
915	<dd>
916	<p>Rather than have rxvt-unicode try to accommodate all the various possible
917	keyboard mappings, it is better to use `xmodmap' to remap the keys as
918	required for your particular machine.</p>
919	</dd>
920	<dt><strong><a name="item_how_do_i_distinguish_wether_i_27m_running_rxvt_2du">How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
921	I need this to decide about setting colors etc.</a></strong><br />
922	</dt>
923	<dd>
924	rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can
925	check and see if that is set. Note that several programs, JED, slrn,
926	Midnight Commander automatically check this variable to decide whether or
927	not to use color.
928	</dd>
929	<p></p>
930	<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 />
931	</dt>
932	<dd>
933	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
934	insecure mode then it is possible to use the following shell script
935	snippets to correctly set the display. If your version of rxvt-unicode
936	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
937	the COLORTERM variable can be used to distinguish rxvt-unicode from a
938	regular xterm.
939	</dd>
940	<dd>
941	<p>Courtesy of Chuck Blake &lt;<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>&gt; with the following shell script
942	snippets:</p>
943	</dd>
944	<dd>
945	<pre>
946	# Bourne/Korn/POSIX family of shells:
947	[ ${TERM:-foo} = foo ] &amp;&amp; TERM=xterm # assume an xterm if we don't know
948	if [ ${TERM:-foo} = xterm ]; then
949	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
950	echo -n '^[Z'
951	read term_id
952	stty icanon echo
953	if [ &quot;&quot;${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
954	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
955	read DISPLAY # set it in our local shell
956	fi
957	fi</pre>
958	</dd>
959	<p></p>
960	<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 />
961	</dt>
962	<dd>
963	You need to have a recent version of perl installed as <em>/usr/bin/perl</em>,
964	one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to
965	the doc subdirectory and enter <code>make alldoc</code>.
966	</dd>
967	<p></p>
968	<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 />
969	</dt>
970	<dd>
971	Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>,
972	channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be
973	interested in learning about new and exciting problems (but not FAQs :).
974	</dd>
975	<p></p></dl>
976	<p>	1229	<p>
977	</p>	1230	</p>
978	<hr />	1231	<hr />
979	<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>	1232	<h1><a name="rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></h1>
980	<p>
981	</p>
982	<hr />
983	<h1><a name="description">DESCRIPTION</a></h1>
984	<p>The rest of this document describes various technical aspects of	1233	<p>The rest of this document describes various technical aspects of
985	<strong>rxvt-unicode</strong>. First the description of supported command sequences,	1234	<strong>rxvt-unicode</strong>. First the description of supported command sequences,
986	followed by menu and pixmap support and last by a description of all	1235	followed by pixmap support and last by a description of all features
987	features selectable at <code>configure</code> time.</p>	1236	selectable at <code>configure</code> time.</p>
988	<p>
989	</p>	1237	<p>
990	<hr />	1238	</p>
991	<h1><a name="definitions">Definitions</a></h1>	1239	<h2><a name="definitions">Definitions</a></h2>
992	<dl>	1240	<dl>
993	<dt><strong><a name="item_c"><strong><code>c</code> </strong>&gt;</a></strong><br />	1241	<dt><strong><a name="item_c"><strong><code>c</code> </strong>&gt;</a></strong><br />
994	</dt>	1242	</dt>
995	<dd>	1243	<dd>
996	The literal character c.	1244	The literal character c.
…		…
1022	A text parameter composed of printable characters.	1270	A text parameter composed of printable characters.
1023	</dd>	1271	</dd>
1024	<p></p></dl>	1272	<p></p></dl>
1025	<p>	1273	<p>
1026	</p>	1274	</p>
1027	<hr />
1028	<h1><a name="values">Values</a></h1>	1275	<h2><a name="values">Values</a></h2>
1029	<dl>	1276	<dl>
1030	<dt><strong><a name="item_enq"><strong><code>ENQ</code> </strong>&gt;</a></strong><br />	1277	<dt><strong><a name="item_enq"><strong><code>ENQ</code> </strong>&gt;</a></strong><br />
1031	</dt>	1278	</dt>
1032	<dd>	1279	<dd>
1033	Enquiry (Ctrl-E) = Send Device Attributes (DA)	1280	Enquiry (Ctrl-E) = Send Device Attributes (DA)
…		…
1096	Space Character	1343	Space Character
1097	</dd>	1344	</dd>
1098	<p></p></dl>	1345	<p></p></dl>
1099	<p>	1346	<p>
1100	</p>	1347	</p>
1101	<hr />
1102	<h1><a name="escape_sequences">Escape Sequences</a></h1>	1348	<h2><a name="escape_sequences">Escape Sequences</a></h2>
1103	<dl>	1349	<dl>
1104	<dt><strong><a name="item_esc__23_8"><strong><code>ESC # 8</code> </strong>&gt;</a></strong><br />	1350	<dt><strong><a name="item_esc__23_8"><strong><code>ESC # 8</code> </strong>&gt;</a></strong><br />
1105	</dt>	1351	</dt>
1106	<dd>	1352	<dd>
1107	DEC Screen Alignment Test (DECALN)	1353	DEC Screen Alignment Test (DECALN)
…		…
1240	<tr><td>C = K </td><td>German character set unimplemented</td></tr>	1486	<tr><td>C = K </td><td>German character set unimplemented</td></tr>
1241	</table><p></p></dl>	1487	</table><p></p></dl>
1242	<p></p>	1488	<p></p>
1243	<p>	1489	<p>
1244	</p>	1490	</p>
1245	<hr />
1246	<h1><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h1>	1491	<h2><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h2>
1247	<dl>	1492	<dl>
1248	<dt><strong><a name="item_esc__5b_ps__40"><strong><code>ESC [ Ps @</code> </strong>&gt;</a></strong><br />	1493	<dt><strong><a name="item_esc__5b_ps__40"><strong><code>ESC [ Ps @</code> </strong>&gt;</a></strong><br />
1249	</dt>	1494	</dt>
1250	<dd>	1495	<dd>
1251	Insert <strong><a href="#item_ps"><code>Ps</code></a> </strong>&gt; (Blank) <code>Character(s)</code> [default: 1] (ICH)	1496	Insert <strong><a href="#item_ps"><code>Ps</code></a> </strong>&gt; (Blank) <code>Character(s)</code> [default: 1] (ICH)
…		…
1547	</dd>	1792	</dd>
1548	<p></p></dl>	1793	<p></p></dl>
1549	<p></p>	1794	<p></p>
1550	<p>	1795	<p>
1551	</p>	1796	</p>
1552	<hr />
1553	<h1><a name="dec_private_modes">DEC Private Modes</a></h1>	1797	<h2><a name="dec_private_modes">DEC Private Modes</a></h2>
1554	<dl>	1798	<dl>
1555	<dt><strong><a name="item_esc__5b__3f_pm_h"><strong><code>ESC [ ? Pm h</code> </strong>&gt;</a></strong><br />	1799	<dt><strong><a name="item_esc__5b__3f_pm_h"><strong><code>ESC [ ? Pm h</code> </strong>&gt;</a></strong><br />
1556	</dt>	1800	</dt>
1557	<dd>	1801	<dd>
1558	DEC Private Mode Set (DECSET)	1802	DEC Private Mode Set (DECSET)
…		…
1625	</table><dt><strong><a name="item_ps__3d_9_x10_xterm"><strong><code>Ps = 9</code> </strong>&gt; X10 XTerm</a></strong><br />	1869	</table><dt><strong><a name="item_ps__3d_9_x10_xterm"><strong><code>Ps = 9</code> </strong>&gt; X10 XTerm</a></strong><br />
1626	</dt>	1870	</dt>
1627	<table>	1871	<table>
1628	<tr><td>h</td><td>Send Mouse X & Y on button press.</td></tr>	1872	<tr><td>h</td><td>Send Mouse X & Y on button press.</td></tr>
1629	<tr><td>l</td><td>No mouse reporting.</td></tr>	1873	<tr><td>l</td><td>No mouse reporting.</td></tr>
1630	</table><dt><strong><a name="item_10"><strong><code>Ps = 10</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
1631	</dt>
1632	<table>
1633	<tr><td>h</td><td>menuBar visible</td></tr>
1634	<tr><td>l</td><td>menuBar invisible</td></tr>
1635	</table><dt><strong><a name="item_ps__3d_25"><strong><code>Ps = 25</code> </strong>&gt;</a></strong><br />	1874	</table><dt><strong><a name="item_ps__3d_25"><strong><code>Ps = 25</code> </strong>&gt;</a></strong><br />
1636	</dt>	1875	</dt>
1637	<table>	1876	<table>
1638	<tr><td>h</td><td>Visible cursor {cnorm/cvvis}</td></tr>	1877	<tr><td>h</td><td>Visible cursor {cnorm/cvvis}</td></tr>
1639	<tr><td>l</td><td>Invisible cursor {civis}</td></tr>	1878	<tr><td>l</td><td>Invisible cursor {civis}</td></tr>
…		…
1704	</table><dt><strong><a name="item_1011"><strong><code>Ps = 1011</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />	1943	</table><dt><strong><a name="item_1011"><strong><code>Ps = 1011</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
1705	</dt>	1944	</dt>
1706	<table>	1945	<table>
1707	<tr><td>h</td><td>Scroll to bottom when a key is pressed</td></tr>	1946	<tr><td>h</td><td>Scroll to bottom when a key is pressed</td></tr>
1708	<tr><td>l</td><td>Don't scroll to bottom when a key is pressed</td></tr>	1947	<tr><td>l</td><td>Don't scroll to bottom when a key is pressed</td></tr>
		1948	</table><dt><strong><a name="item_1021"><strong><code>Ps = 1021</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
		1949	</dt>
		1950	<table>
		1951	<tr><td>h</td><td>Bold/italic implies high intensity (see option -is)</td></tr>
		1952	<tr><td>l</td><td>Font styles have no effect on intensity (Compile styles)</td></tr>
1709	</table><dt><strong><a name="item_ps__3d_1047"><strong><code>Ps = 1047</code> </strong>&gt;</a></strong><br />	1953	</table><dt><strong><a name="item_ps__3d_1047"><strong><code>Ps = 1047</code> </strong>&gt;</a></strong><br />
1710	</dt>	1954	</dt>
1711	<table>	1955	<table>
1712	<tr><td>h</td><td>Use Alternate Screen Buffer</td></tr>	1956	<tr><td>h</td><td>Use Alternate Screen Buffer</td></tr>
1713	<tr><td>l</td><td>Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it</td></tr>	1957	<tr><td>l</td><td>Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it</td></tr>
…		…
1724	</table></dl>	1968	</table></dl>
1725	</dl>	1969	</dl>
1726	<p></p>	1970	<p></p>
1727	<p>	1971	<p>
1728	</p>	1972	</p>
1729	<hr />
1730	<h1><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h1>	1973	<h2><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h2>
1731	<dl>	1974	<dl>
1732	<dt><strong><a name="item_esc__5d_ps_3bpt_st"><strong><code>ESC ] Ps;Pt ST</code> </strong>&gt;</a></strong><br />	1975	<dt><strong><a name="item_esc__5d_ps_3bpt_st"><strong><code>ESC ] Ps;Pt ST</code> </strong>&gt;</a></strong><br />
1733	</dt>	1976	</dt>
1734	<dd>	1977	<dd>
1735	Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b,	1978	Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b,
…		…
1745	<tr><td>Ps = 10</td><td>Change colour of text foreground to Pt (NB: may change in future)</td></tr>	1988	<tr><td>Ps = 10</td><td>Change colour of text foreground to Pt (NB: may change in future)</td></tr>
1746	<tr><td>Ps = 11</td><td>Change colour of text background to Pt (NB: may change in future)</td></tr>	1989	<tr><td>Ps = 11</td><td>Change colour of text background to Pt (NB: may change in future)</td></tr>
1747	<tr><td>Ps = 12</td><td>Change colour of text cursor foreground to Pt</td></tr>	1990	<tr><td>Ps = 12</td><td>Change colour of text cursor foreground to Pt</td></tr>
1748	<tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr>	1991	<tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr>
1749	<tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr>	1992	<tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr>
1750	<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt</td></tr>	1993	<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt [deprecated, see 706]</td></tr>
1751	<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt</td></tr>	1994	<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt [deprecated, see 707]</td></tr>
1752	<tr><td>Ps = 20</td><td>Change default background to Pt</td></tr>	1995	<tr><td>Ps = 20</td><td>Change background pixmap parameters (see section XPM) (Compile XPM).</td></tr>
1753	<tr><td>Ps = 39</td><td>Change default foreground colour to Pt.</td></tr>	1996	<tr><td>Ps = 39</td><td>Change default foreground colour to Pt.</td></tr>
1754	<tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr>	1997	<tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr>
1755	<tr><td>Ps = 49</td><td>Change default background colour to Pt.</td></tr>	1998	<tr><td>Ps = 49</td><td>Change default background colour to Pt.</td></tr>
1756	<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>	1999	<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>
1757	<tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr>	2000	<tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr>
1758	<tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).</td></tr>	2001	<tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).</td></tr>
1759	<tr><td>Ps = 703</td><td>Menubar command Pt (Compile menubar).</td></tr>	2002	<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>
1760	<tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr>	2003	<tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr>
1761	<tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt (Compile transparency).</td></tr>	2004	<tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt (Compile transparency).</td></tr>
		2005	<tr><td>Ps = 706</td><td>Change colour of bold characters to Pt</td></tr>
		2006	<tr><td>Ps = 707</td><td>Change colour of underlined characters to Pt</td></tr>
1762	<tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr>	2007	<tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr>
1763	<tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>	2008	<tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1764	<tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>	2009	<tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1765	<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>	2010	<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1766	<tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>	2011	<tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
1767	<tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>	2012	<tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
		2013	<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>
1768	</table><p></p></dl>	2014	</table><p></p></dl>
1769	<p></p>
1770	<p>
1771	</p>
1772	<hr />
1773	<h1><a name="menubar">menuBar</a></h1>
1774	<p><strong>The exact syntax used is <em>almost</em> solidified. </strong>&gt;
1775	In the menus, <strong>DON'T</strong> try to use menuBar commands that add or remove a
1776	menuBar.</p>
1777	<p>Note that in all of the commands, the <strong><em>/path/</em> </strong>&gt; <em>cannot</em> be
1778	omitted: use <strong>./</strong> to specify a menu relative to the current menu.</p>
1779	<p>
1780	</p>
1781	<h2><a name="overview_of_menubar_operation">Overview of menuBar operation</a></h2>
1782	<p>For the menuBar XTerm escape sequence <code>ESC ] 703 ; Pt ST</code>, the syntax
1783	of <a href="#item_pt"><code>Pt</code></a> can be used for a variety of tasks:</p>
1784	<p>At the top level is the current menuBar which is a member of a circular
1785	linked-list of other such menuBars.</p>
1786	<p>The menuBar acts as a parent for the various drop-down menus, which in
1787	turn, may have labels, separator lines, menuItems and subMenus.</p>
1788	<p>The menuItems are the useful bits: you can use them to mimic keyboard
1789	input or even to send text or escape sequences back to rxvt.</p>
1790	<p>The menuBar syntax is intended to provide a simple yet robust method of
1791	constructing and manipulating menus and navigating through the
1792	menuBars.</p>
1793	<p>The first step is to use the tag <strong>[menu:<em>name</em>] </strong>&gt; which creates
1794	the menuBar called <em>name</em> and allows access. You may now or menus,
1795	subMenus, and menuItems. Finally, use the tag <strong>[done]</strong> to set the
1796	menuBar access as <strong>readonly</strong> to prevent accidental corruption of the
1797	menus. To re-access the current menuBar for alterations, use the tag
1798	<strong>[menu]</strong>, make the alterations and then use <strong>[done]</strong></p>
1799	<p></p>
1800	<p>
1801	</p>
1802	<h2><a name="commands">Commands</a></h2>
1803	<dl>
1804	<dt><strong><a name="item__5bmenu_3a_2bname_5d"><strong>[menu:+<em>name</em>] </strong>&gt;</a></strong><br />
1805	</dt>
1806	<dd>
1807	access the named menuBar for creation or alteration. If a new menuBar
1808	is created, it is called <em>name</em> (max of 15 chars) and the current
1809	menuBar is pushed onto the stack
1810	</dd>
1811	<p></p>
1812	<dt><strong><a name="item__5bmenu_5d"><strong>[menu]</strong></a></strong><br />
1813	</dt>
1814	<dd>
1815	access the current menuBar for alteration
1816	</dd>
1817	<p></p>
1818	<dt><strong><a name="item__5btitle_3a_2bstring_5d"><strong>[title:+<em>string</em>] </strong>&gt;</a></strong><br />
1819	</dt>
1820	<dd>
1821	set the current menuBar's title to <em>string</em>, which may contain the
1822	following format specifiers:
1823	</dd>
1824	<dd>
1825	<pre>
1826	B&lt;%n&gt; rxvt name (as per the B&lt;-name&gt; command-line option)
1827	B&lt;%v&gt; rxvt version
1828	B&lt;%%&gt; literal B&lt;%&gt; character</pre>
1829	</dd>
1830	<p></p>
1831	<dt><strong><a name="item__5bdone_5d"><strong>[done]</strong></a></strong><br />
1832	</dt>
1833	<dd>
1834	set menuBar access as <strong>readonly</strong>.
1835	End-of-file tag for <strong>[read:+<em>file</em>] </strong>&gt; operations.
1836	</dd>
1837	<p></p>
1838	<dt><strong><a name="item__5bread_3a_2bfile_5d"><strong>[read:+<em>file</em>] </strong>&gt;</a></strong><br />
1839	</dt>
1840	<dd>
1841	read menu commands directly from <em>file</em> (extension ``.menu'' will be
1842	appended if required.) Start reading at a line with <strong>[menu]</strong> or <strong>&lt;
1843	[menu:+<em>name</em> </strong>&gt; and continuing until <strong>[done]</strong> is encountered.
1844	</dd>
1845	<dd>
1846	<p>Blank and comment lines (starting with <strong>#</strong>) are ignored. Actually,
1847	since any invalid menu commands are also ignored, almost anything could
1848	be construed as a comment line, but this may be tightened up in the
1849	future ... so don't count on it!.</p>
1850	</dd>
1851	<p></p>
1852	<dt><strong><a name="item__5bread_3a_2bfile_3b_2bname_5d"><strong>[read:+<em>file</em>;+<em>name</em>] </strong>&gt;</a></strong><br />
1853	</dt>
1854	<dd>
1855	The same as <strong>[read:+<em>file</em>] </strong>&gt;, but start reading at a line with
1856	<strong>[menu:+<em>name</em>] </strong>&gt; and continuing until <strong>[done:+<em>name</em>] </strong>&gt; or
1857	<strong>[done]</strong> is encountered.
1858	</dd>
1859	<p></p>
1860	<dt><strong><a name="item__5bdump_5d"><strong>[dump]</strong></a></strong><br />
1861	</dt>
1862	<dd>
1863	dump all menuBars to the file <strong>/tmp/rxvt-PID</strong> in a format suitable for
1864	later rereading.
1865	</dd>
1866	<p></p>
1867	<dt><strong><a name="item__5brm_3aname_5d"><strong>[rm:name]</strong></a></strong><br />
1868	</dt>
1869	<dd>
1870	remove the named menuBar
1871	</dd>
1872	<p></p>
1873	<dt><strong><a name="item__5brm_5d__5brm_3a_5d"><strong>[rm] [rm:]</strong></a></strong><br />
1874	</dt>
1875	<dd>
1876	remove the current menuBar
1877	</dd>
1878	<p></p>
1879	<dt><strong><a name="item__5brm_2a_5d__5brm_3a_2a_5d"><strong>[rm*] [rm:*]</strong></a></strong><br />
1880	</dt>
1881	<dd>
1882	remove all menuBars
1883	</dd>
1884	<p></p>
1885	<dt><strong><a name="item__5bswap_5d"><strong>[swap]</strong></a></strong><br />
1886	</dt>
1887	<dd>
1888	swap the top two menuBars
1889	</dd>
1890	<p></p>
1891	<dt><strong><a name="item__5bprev_5d"><strong>[prev]</strong></a></strong><br />
1892	</dt>
1893	<dd>
1894	access the previous menuBar
1895	</dd>
1896	<p></p>
1897	<dt><strong><a name="item__5bnext_5d"><strong>[next]</strong></a></strong><br />
1898	</dt>
1899	<dd>
1900	access the next menuBar
1901	</dd>
1902	<p></p>
1903	<dt><strong><a name="item__5bshow_5d"><strong>[show]</strong></a></strong><br />
1904	</dt>
1905	<dd>
1906	Enable display of the menuBar
1907	</dd>
1908	<p></p>
1909	<dt><strong><a name="item__5bhide_5d"><strong>[hide]</strong></a></strong><br />
1910	</dt>
1911	<dd>
1912	Disable display of the menuBar
1913	</dd>
1914	<p></p>
1915	<dt><strong><a name="item__5bpixmap_3a_2bname_5d"><strong>[pixmap:+<em>name</em>] </strong>&gt;</a></strong><br />
1916	</dt>
1917	<dt><strong><a name="item__5bpixmap_3a_2bname_3bscaling_5d"><strong>[pixmap:+<em>name</em>;<em>scaling</em>] </strong>&gt;</a></strong><br />
1918	</dt>
1919	<dd>
1920	(set the background pixmap globally
1921	</dd>
1922	<dd>
1923	<p><strong>A Future implementation <em>may</em> make this local to the menubar </strong>&gt;)</p>
1924	</dd>
1925	<p></p>
1926	<dt><strong><a name="item__5b_3a_2bcommand_3a_5d"><strong>[:+<em>command</em>:] </strong>&gt;</a></strong><br />
1927	</dt>
1928	<dd>
1929	ignore the menu readonly status and issue a <em>command</em> to or a menu or
1930	menuitem or change the ; a useful shortcut for setting the quick arrows
1931	from a menuBar.
1932	</dd>
1933	<p></p></dl>
1934	<p></p>
1935	<p>
1936	</p>
1937	<h2><a name="adding_and_accessing_menus">Adding and accessing menus</a></h2>
1938	<p>The following commands may also be <strong>+</strong> prefixed.</p>
1939	<dl>
1940	<dt><strong><a name="item__2f_2b"><strong>/+</strong></a></strong><br />
1941	</dt>
1942	<dd>
1943	access menuBar top level
1944	</dd>
1945	<p></p>
1946	<dt><strong><a name="item__2e_2f_2b"><strong>./+</strong></a></strong><br />
1947	</dt>
1948	<dd>
1949	access current menu level
1950	</dd>
1951	<p></p>
1952	<dt><strong><a name="item__2e_2e_2f_2b"><strong>../+</strong></a></strong><br />
1953	</dt>
1954	<dd>
1955	access parent menu (1 level up)
1956	</dd>
1957	<p></p>
1958	<dt><strong><a name="item__2e_2e_2f_2e_2e_2f"><strong>../../</strong></a></strong><br />
1959	</dt>
1960	<dd>
1961	access parent menu (multiple levels up)
1962	</dd>
1963	<p></p>
1964	<dt><strong><a name="item__2fpath_2fmenu"><strong><em>/path/</em>menu </strong>&gt;</a></strong><br />
1965	</dt>
1966	<dd>
1967	add/access menu
1968	</dd>
1969	<p></p>
1970	<dt><strong><a name="item__2fpath_2fmenu_2f_2a"><strong><em>/path/</em>menu/* </strong>&gt;</a></strong><br />
1971	</dt>
1972	<dd>
1973	add/access menu and clear it if it exists
1974	</dd>
1975	<p></p>
1976	<dt><strong><a name="item__2fpath_2f_7b_2d_7d"><strong><em>/path/</em>{-} </strong>&gt;</a></strong><br />
1977	</dt>
1978	<dd>
1979	add separator
1980	</dd>
1981	<p></p>
1982	<dt><strong><a name="item__2fpath_2f_7bitem_7d"><strong><em>/path/</em>{item} </strong>&gt;</a></strong><br />
1983	</dt>
1984	<dd>
1985	add <strong>item</strong> as a label
1986	</dd>
1987	<p></p>
1988	<dt><strong><a name="item__2fpath_2f_7bitem_7d_action"><strong><em>/path/</em>{item} action </strong>&gt;</a></strong><br />
1989	</dt>
1990	<dd>
1991	add/alter <em>menuitem</em> with an associated <em>action</em>
1992	</dd>
1993	<p></p>
1994	<dt><strong><a name="item__2fpath_2f_7bitem_7d_7bright_2dtext_7d"><strong><em>/path/</em>{item}{right-text} </strong>&gt;</a></strong><br />
1995	</dt>
1996	<dd>
1997	add/alter <em>menuitem</em> with <strong>right-text</strong> as the right-justified text
1998	and as the associated <em>action</em>
1999	</dd>
2000	<p></p>
2001	<dt><strong><a name="item__2fpath_2f_7bitem_7d_7brtext_7d_action"><strong><em>/path/</em>{item}{rtext} action </strong>&gt;</a></strong><br />
2002	</dt>
2003	<dd>
2004	add/alter <em>menuitem</em> with an associated <em>action</em> and with <strong>rtext</strong> as
2005	the right-justified text.
2006	</dd>
2007	<p></p></dl>
2008	<dl>
2009	<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 />
2010	</dt>
2011	<dd>
2012	<strong>\a \b \E \e \n \r \t \octal</strong>
2013	</dd>
2014	<p></p>
2015	<dt><strong><a name="item_or_in_control_2dcharacter_notation_3a">or in control-character notation:</a></strong><br />
2016	</dt>
2017	<dd>
2018	<strong>^@, ^A .. ^Z .. ^_, ^?</strong>
2019	</dd>
2020	<p></p></dl>
2021	<p>To send a string starting with a <strong>NUL</strong> (<strong>^@</strong>) character to the
2022	program, start <em>action</em> with a pair of <strong>NUL</strong> characters (<strong>^@^@</strong>),
2023	the first of which will be stripped off and the balance directed to the
2024	program. Otherwise if <em>action</em> begins with <strong>NUL</strong> followed by
2025	non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the
2026	balance is sent back to rxvt.</p>
2027	<p>As a convenience for the many Emacs-type editors, <em>action</em> may start
2028	with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be
2029	appended if missed from <strong>M-x</strong> commands.</p>
2030	<p>As a convenience for issuing XTerm <strong>ESC ]</strong> sequences from a menubar (or
2031	quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p>
2032	<dl>
2033	<dt><strong><a name="item_for_example_2c">For example,</a></strong><br />
2034	</dt>
2035	<dd>
2036	<strong>M-xapropos</strong> is equivalent to <strong>\Exapropos\r</strong>
2037	</dd>
2038	<p></p>
2039	<dt><strong><a name="item_and">and</a></strong><br />
2040	</dt>
2041	<dd>
2042	<strong>\E]703;mona;100</strong> is equivalent to <strong>\E]703;mona;100\a</strong>
2043	</dd>
2044	<p></p></dl>
2045	<p>The option <strong>{<em>right-rtext</em>} </strong>&gt; will be right-justified. In the
2046	absence of a specified action, this text will be used as the <em>action</em>
2047	as well.</p>
2048	<dl>
2049	<dt><strong>For example,</strong><br />
2050	</dt>
2051	<dd>
2052	<strong>/File/{Open}{^X^F}</strong> is equivalent to <strong>/File/{Open}{^X^F} ^X^F</strong>
2053	</dd>
2054	<p></p></dl>
2055	<p>The left label <em>is</em> necessary, since it's used for matching, but
2056	implicitly hiding the left label (by using same name for both left and
2057	right labels), or explicitly hiding the left label (by preceeding it
2058	with a dot), makes it possible to have right-justified text only.</p>
2059	<dl>
2060	<dt><strong>For example,</strong><br />
2061	</dt>
2062	<dd>
2063	<strong>/File/{Open}{Open} Open-File-Action</strong>
2064	</dd>
2065	<p></p>
2066	<dt><strong><a name="item_or_hiding_it">or hiding it</a></strong><br />
2067	</dt>
2068	<dd>
2069	<strong>/File/{.anylabel}{Open} Open-File-Action</strong>
2070	</dd>
2071	<p></p></dl>
2072	<p></p>
2073	<p>
2074	</p>
2075	<h2><a name="removing_menus">Removing menus</a></h2>
2076	<dl>
2077	<dt><strong><a name="item__2d_2f_2a_2b"><strong>-/*+ </strong>&gt;</a></strong><br />
2078	</dt>
2079	<dd>
2080	remove all menus from the menuBar, the same as <strong>[clear]</strong>
2081	</dd>
2082	<p></p>
2083	<dt><strong><a name="item__2d_2b_2fpathmenu_2b"><strong>-+<em>/path</em>menu+ </strong>&gt;</a></strong><br />
2084	</dt>
2085	<dd>
2086	remove menu
2087	</dd>
2088	<p></p>
2089	<dt><strong><a name="item__2d_2b_2fpath_7bitem_7d_2b"><strong>-+<em>/path</em>{item}+ </strong>&gt;</a></strong><br />
2090	</dt>
2091	<dd>
2092	remove item
2093	</dd>
2094	<p></p>
2095	<dt><strong><a name="item__2d_2b_2fpath_7b_2d_7d"><strong>-+<em>/path</em>{-} </strong>&gt;</a></strong><br />
2096	</dt>
2097	<dd>
2098	remove separator)
2099	</dd>
2100	<p></p>
2101	<dt><strong><a name="item__2d_2fpath_2fmenu_2f_2a"><strong>-/path/menu/*</strong></a></strong><br />
2102	</dt>
2103	<dd>
2104	remove all items, separators and submenus from menu
2105	</dd>
2106	<p></p></dl>
2107	<p></p>
2108	<p>
2109	</p>
2110	<h2><a name="quick_arrows">Quick Arrows</a></h2>
2111	<p>The menus also provide a hook for <em>quick arrows</em> to provide easier
2112	user access. If nothing has been explicitly set, the default is to
2113	emulate the curror keys. The syntax permits each arrow to be altered
2114	individually or all four at once without re-entering their common
2115	beginning/end text. For example, to explicitly associate cursor actions
2116	with the arrows, any of the following forms could be used:</p>
2117	<dl>
2118	<dt><strong><a name="item__3cr_3e_2bright"><strong>&lt;r</strong>+<em>Right</em> &gt;&gt;</a></strong><br />
2119	</dt>
2120	<dt><strong><a name="item__3cl_3e_2bleft"><strong>&lt;l</strong>+<em>Left</em> &gt;&gt;</a></strong><br />
2121	</dt>
2122	<dt><strong><a name="item__3cu_3e_2bup"><strong>&lt;u</strong>+<em>Up</em> &gt;&gt;</a></strong><br />
2123	</dt>
2124	<dt><strong><a name="item__3cd_3e_2bdown"><strong>&lt;d</strong>+<em>Down</em> &gt;&gt;</a></strong><br />
2125	</dt>
2126	<dd>
2127	Define actions for the respective arrow buttons
2128	</dd>
2129	<p></p>
2130	<dt><strong><a name="item__3cb_3e_2bbegin"><strong>&lt;b</strong>+<em>Begin</em> &gt;&gt;</a></strong><br />
2131	</dt>
2132	<dt><strong><a name="item__3ce_3e_2bend"><strong>&lt;e</strong>+<em>End</em> &gt;&gt;</a></strong><br />
2133	</dt>
2134	<dd>
2135	Define common beginning/end parts for <em>quick arrows</em> which used in
2136	conjunction with the above &lt;r&gt; &lt;l&gt; &lt;u&gt; &lt;d&gt; constructs
2137	</dd>
2138	<p></p></dl>
2139	<dl>
2140	<dt><strong><a name="item_for_example_2c_define_arrows_individually_2c">For example, define arrows individually,</a></strong><br />
2141	</dt>
2142	<dd>
2143	<pre>
2144	&lt;u&gt;\E[A</pre>
2145	</dd>
2146	<dd>
2147	<pre>
2148	&lt;d&gt;\E[B</pre>
2149	</dd>
2150	<dd>
2151	<pre>
2152	&lt;r&gt;\E[C</pre>
2153	</dd>
2154	<dd>
2155	<pre>
2156	&lt;l&gt;\E[D</pre>
2157	</dd>
2158	<dt><strong><a name="item_or_all_at_once">or all at once</a></strong><br />
2159	</dt>
2160	<dd>
2161	<pre>
2162	&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>
2163	</dd>
2164	<dt><strong><a name="item_compactly">or more compactly (factoring out common parts)</a></strong><br />
2165	</dt>
2166	<dd>
2167	<pre>
2168	&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>
2169	</dd>
2170	</dl>
2171	<p></p>
2172	<p>
2173	</p>
2174	<h2><a name="command_summary">Command Summary</a></h2>
2175	<p>A short summary of the most <em>common</em> commands:</p>
2176	<dl>
2177	<dt><strong><a name="item__5bmenu_3aname_5d">[menu:name]</a></strong><br />
2178	</dt>
2179	<dd>
2180	use an existing named menuBar or start a new one
2181	</dd>
2182	<p></p>
2183	<dt><strong>[menu]</strong><br />
2184	</dt>
2185	<dd>
2186	use the current menuBar
2187	</dd>
2188	<p></p>
2189	<dt><strong><a name="item__5btitle_3astring_5d">[title:string]</a></strong><br />
2190	</dt>
2191	<dd>
2192	set menuBar title
2193	</dd>
2194	<p></p>
2195	<dt><strong>[done]</strong><br />
2196	</dt>
2197	<dd>
2198	set menu access to readonly and, if reading from a file, signal EOF
2199	</dd>
2200	<p></p>
2201	<dt><strong><a name="item__5bdone_3aname_5d">[done:name]</a></strong><br />
2202	</dt>
2203	<dd>
2204	if reading from a file using [read:file;name] signal EOF
2205	</dd>
2206	<p></p>
2207	<dt><strong>[rm:name]</strong><br />
2208	</dt>
2209	<dd>
2210	remove named <code>menuBar(s)</code>
2211	</dd>
2212	<p></p>
2213	<dt><strong>[rm] [rm:]</strong><br />
2214	</dt>
2215	<dd>
2216	remove current menuBar
2217	</dd>
2218	<p></p>
2219	<dt><strong>[rm*] [rm:*]</strong><br />
2220	</dt>
2221	<dd>
2222	remove all <code>menuBar(s)</code>
2223	</dd>
2224	<p></p>
2225	<dt><strong>[swap]</strong><br />
2226	</dt>
2227	<dd>
2228	swap top two menuBars
2229	</dd>
2230	<p></p>
2231	<dt><strong>[prev]</strong><br />
2232	</dt>
2233	<dd>
2234	access the previous menuBar
2235	</dd>
2236	<p></p>
2237	<dt><strong>[next]</strong><br />
2238	</dt>
2239	<dd>
2240	access the next menuBar
2241	</dd>
2242	<p></p>
2243	<dt><strong>[show]</strong><br />
2244	</dt>
2245	<dd>
2246	map menuBar
2247	</dd>
2248	<p></p>
2249	<dt><strong>[hide]</strong><br />
2250	</dt>
2251	<dd>
2252	unmap menuBar
2253	</dd>
2254	<p></p>
2255	<dt><strong><a name="item__5bpixmap_3bfile_5d">[pixmap;file]</a></strong><br />
2256	</dt>
2257	<dt><strong><a name="item__5bpixmap_3bfile_3bscaling_5d">[pixmap;file;scaling]</a></strong><br />
2258	</dt>
2259	<dd>
2260	set a background pixmap
2261	</dd>
2262	<p></p>
2263	<dt><strong><a name="item__5bread_3afile_5d">[read:file]</a></strong><br />
2264	</dt>
2265	<dt><strong><a name="item__5bread_3afile_3bname_5d">[read:file;name]</a></strong><br />
2266	</dt>
2267	<dd>
2268	read in a menu from a file
2269	</dd>
2270	<p></p>
2271	<dt><strong>[dump]</strong><br />
2272	</dt>
2273	<dd>
2274	dump out all menuBars to /tmp/rxvt-PID
2275	</dd>
2276	<p></p>
2277	<dt><strong><a name="item__2f">/</a></strong><br />
2278	</dt>
2279	<dd>
2280	access menuBar top level
2281	</dd>
2282	<p></p>
2283	<dt><strong><a name="item__2e_2f">./</a></strong><br />
2284	</dt>
2285	<dt><strong><a name="item__2e_2e_2f">../</a></strong><br />
2286	</dt>
2287	<dt><strong>../../</strong><br />
2288	</dt>
2289	<dd>
2290	access current or parent menu level
2291	</dd>
2292	<p></p>
2293	<dt><strong>/path/menu</strong><br />
2294	</dt>
2295	<dd>
2296	add/access menu
2297	</dd>
2298	<p></p>
2299	<dt><strong>/path/{-}</strong><br />
2300	</dt>
2301	<dd>
2302	add separator
2303	</dd>
2304	<p></p>
2305	<dt><strong>/path/{item}{rtext} action</strong><br />
2306	</dt>
2307	<dd>
2308	add/alter menu item
2309	</dd>
2310	<p></p>
2311	<dt><strong><a name="item__2d_2f_2a">-/*</a></strong><br />
2312	</dt>
2313	<dd>
2314	remove all menus from the menuBar
2315	</dd>
2316	<p></p>
2317	<dt><strong><a name="item__2d_2fpath_2fmenu">-/path/menu</a></strong><br />
2318	</dt>
2319	<dd>
2320	remove menu items, separators and submenus from menu
2321	</dd>
2322	<p></p>
2323	<dt><strong>-/path/menu</strong><br />
2324	</dt>
2325	<dd>
2326	remove menu
2327	</dd>
2328	<p></p>
2329	<dt><strong><a name="item__2d_2fpath_2f_7bitem_7d">-/path/{item}</a></strong><br />
2330	</dt>
2331	<dd>
2332	remove item
2333	</dd>
2334	<p></p>
2335	<dt><strong><a name="item__2d_2fpath_2f_7b_2d_7d">-/path/{-}</a></strong><br />
2336	</dt>
2337	<dd>
2338	remove separator
2339	</dd>
2340	<p></p>
2341	<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 />
2342	</dt>
2343	<dd>
2344	menu quick arrows
2345	</dd>
2346	<p></p></dl>
2347	<p>	2015	<p>
2348	</p>	2016	</p>
2349	<hr />	2017	<hr />
2350	<h1><a name="xpm">XPM</a></h1>	2018	<h1><a name="xpm">XPM</a></h1>
2351	<p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value	2019	<p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value
…		…
2456	</dt>	2124	</dt>
2457	<table>	2125	<table>
2458	<tr><td>4</td><td>Shift</td></tr>	2126	<tr><td>4</td><td>Shift</td></tr>
2459	<tr><td>8</td><td>Meta</td></tr>	2127	<tr><td>8</td><td>Meta</td></tr>
2460	<tr><td>16</td><td>Control</td></tr>	2128	<tr><td>16</td><td>Control</td></tr>
2461	<tr><td>32</td><td>Double Click (Rxvt extension)</td></tr>	2129	<tr><td>32</td><td>Double Click (rxvt extension)</td></tr>
2462	</table><p>Col = <strong><code>&lt;x&gt; - SPACE</code> </strong>&gt;</p>	2130	</table><p>Col = <strong><code>&lt;x&gt; - SPACE</code> </strong>&gt;</p>
2463	<p>Row = <strong><code>&lt;y&gt; - SPACE</code> </strong>&gt;</p>	2131	<p>Row = <strong><code>&lt;y&gt; - SPACE</code> </strong>&gt;</p>
2464	</dl>	2132	</dl>
2465	<p>	2133	<p>
2466	</p>	2134	</p>
…		…
2600	</dd>	2268	</dd>
2601	<p></p>	2269	<p></p>
2602	<dt><strong><a name="item_unicode3">--enable-unicode3 (default: off)</a></strong><br />	2270	<dt><strong><a name="item_unicode3">--enable-unicode3 (default: off)</a></strong><br />
2603	</dt>	2271	</dt>
2604	<dd>	2272	<dd>
		2273	Recommended to stay off unless you really need non-BMP characters.
		2274	</dd>
		2275	<dd>
2605	Enable direct support for displaying unicode codepoints above	2276	<p>Enable direct support for displaying unicode codepoints above
2606	65535 (the basic multilingual page). This increases storage	2277	65535 (the basic multilingual page). This increases storage
2607	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2278	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2608	support these extra characters, but Xft does.	2279	support these extra characters, but Xft does.</p>
2609	</dd>	2280	</dd>
2610	<dd>	2281	<dd>
2611	<p>Please note that rxvt-unicode can store unicode code points &gt;65535	2282	<p>Please note that rxvt-unicode can store unicode code points &gt;65535
2612	even without this flag, but the number of such characters is	2283	even without this flag, but the number of such characters is
2613	limited to a view thousand (shared with combining characters,	2284	limited to a view thousand (shared with combining characters,
…		…
2623	where accents are encoded as seperate unicode characters. This is	2294	where accents are encoded as seperate unicode characters. This is
2624	done by using precomposited characters when available or creating	2295	done by using precomposited characters when available or creating
2625	new pseudo-characters when no precomposed form exists.	2296	new pseudo-characters when no precomposed form exists.
2626	</dd>	2297	</dd>
2627	<dd>	2298	<dd>
2628	<p>Without --enable-unicode3, the number of additional precomposed characters	2299	<p>Without --enable-unicode3, the number of additional precomposed
2629	is rather limited (2048, if this is full, rxvt-unicode will use the	2300	characters is somewhat limited (the 6400 private use characters will be
2630	private use area, extending the number of combinations to 8448). With
2631	--enable-unicode3, no practical limit exists.</p>	2301	(ab-)used). With --enable-unicode3, no practical limit exists.</p>
2632	</dd>	2302	</dd>
2633	<dd>	2303	<dd>
2634	<p>This option will also enable storage (but not display) of characters	2304	<p>This option will also enable storage (but not display) of characters
2635	beyond plane 0 (&gt;65535) when --enable-unicode3 was not specified.</p>	2305	beyond plane 0 (&gt;65535) when --enable-unicode3 was not specified.</p>
2636	</dd>	2306	</dd>
…		…
2641	</dd>	2311	</dd>
2642	<p></p>	2312	<p></p>
2643	<dt><strong><a name="item_fallback">--enable-fallback(=CLASS) (default: Rxvt)</a></strong><br />	2313	<dt><strong><a name="item_fallback">--enable-fallback(=CLASS) (default: Rxvt)</a></strong><br />
2644	</dt>	2314	</dt>
2645	<dd>	2315	<dd>
2646	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.	2316	When reading resource settings, also read settings for class CLASS. To
		2317	disable resource fallback use --disable-fallback.
2647	</dd>	2318	</dd>
2648	<p></p>	2319	<p></p>
2649	<dt><strong><a name="item_name">--with-res-name=NAME (default: urxvt)</a></strong><br />	2320	<dt><strong><a name="item_name">--with-res-name=NAME (default: urxvt)</a></strong><br />
2650	</dt>	2321	</dt>
2651	<dd>	2322	<dd>
…		…
2682	Write user and tty to lastlog file (used by programs like	2353	Write user and tty to lastlog file (used by programs like
2683	<em>lastlogin</em>) at start of rxvt execution. This option requires	2354	<em>lastlogin</em>) at start of rxvt execution. This option requires
2684	--enable-utmp to also be specified.	2355	--enable-utmp to also be specified.
2685	</dd>	2356	</dd>
2686	<p></p>	2357	<p></p>
2687	<dt><strong><a name="item_background">--enable-xpm-background (default: off)</a></strong><br />	2358	<dt><strong><a name="item_background">--enable-xpm-background (default: on)</a></strong><br />
2688	</dt>	2359	</dt>
2689	<dd>	2360	<dd>
2690	Add support for XPM background pixmaps.	2361	Add support for XPM background pixmaps.
2691	</dd>	2362	</dd>
2692	<p></p>	2363	<p></p>
2693	<dt><strong><a name="item_transparency">--enable-transparency (default: off)</a></strong><br />	2364	<dt><strong><a name="item_transparency">--enable-transparency (default: on)</a></strong><br />
2694	</dt>	2365	</dt>
2695	<dd>	2366	<dd>
2696	Add support for inheriting parent backgrounds thus giving a fake	2367	Add support for inheriting parent backgrounds thus giving a fake
2697	transparency to the term.	2368	transparency to the term.
2698	</dd>	2369	</dd>
…		…
2705	<p></p>	2376	<p></p>
2706	<dt><strong><a name="item_tinting">--enable-tinting (default: on)</a></strong><br />	2377	<dt><strong><a name="item_tinting">--enable-tinting (default: on)</a></strong><br />
2707	</dt>	2378	</dt>
2708	<dd>	2379	<dd>
2709	Add support for tinting of transparent backgrounds (requires <code>--enable-transparency</code>).	2380	Add support for tinting of transparent backgrounds (requires <code>--enable-transparency</code>).
2710	</dd>
2711	<p></p>
2712	<dt><strong><a name="item_menubar">--enable-menubar (default: off)</a></strong><br />
2713	</dt>
2714	<dd>
2715	Add support for our menu bar system (this interacts badly with
2716	dynamic locale switching currently).
2717	</dd>	2381	</dd>
2718	<p></p>	2382	<p></p>
2719	<dt><strong><a name="item_scroll">--enable-rxvt-scroll (default: on)</a></strong><br />	2383	<dt><strong><a name="item_scroll">--enable-rxvt-scroll (default: on)</a></strong><br />
2720	</dt>	2384	</dt>
2721	<dd>	2385	<dd>
…		…
2740	Add support for a very unobtrusive, plain-looking scrollbar that	2404	Add support for a very unobtrusive, plain-looking scrollbar that
2741	is the favourite of the rxvt-unicode author, having used it for	2405	is the favourite of the rxvt-unicode author, having used it for
2742	many years.	2406	many years.
2743	</dd>	2407	</dd>
2744	<p></p>	2408	<p></p>
2745	<dt><strong><a name="item_shadow">--enable-half-shadow (default: off)</a></strong><br />
2746	</dt>
2747	<dd>
2748	Make shadows on the scrollbar only half the normal width &amp; height.
2749	only applicable to rxvt scrollbars.
2750	</dd>
2751	<p></p>
2752	<dt><strong><a name="item_ttygid">--enable-ttygid (default: off)</a></strong><br />	2409	<dt><strong><a name="item_ttygid">--enable-ttygid (default: off)</a></strong><br />
2753	</dt>	2410	</dt>
2754	<dd>	2411	<dd>
2755	Change tty device setting to group ``tty'' - only use this if	2412	Change tty device setting to group ``tty'' - only use this if
2756	your system uses this type of security.	2413	your system uses this type of security.
…		…
2771	<p></p>	2428	<p></p>
2772	<dt><strong><a name="item__2d_2ddisable_2dresources">--disable-resources</a></strong><br />	2429	<dt><strong><a name="item__2d_2ddisable_2dresources">--disable-resources</a></strong><br />
2773	</dt>	2430	</dt>
2774	<dd>	2431	<dd>
2775	Removes any support for resource checking.	2432	Removes any support for resource checking.
2776	</dd>
2777	<p></p>
2778	<dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br />
2779	</dt>
2780	<dd>
2781	Make resources checking via <code>XGetDefault()</code> instead of our small
2782	version which only checks ~/.Xdefaults, or if that doesn't exist then
2783	~/.Xresources.
2784	</dd>
2785	<dd>
2786	<p>Please note that nowadays, things like XIM will automatically pull in and
2787	use the full X resource manager, so the overhead of using it might be very
2788	small, if nonexistant.</p>
2789	</dd>
2790	<p></p>
2791	<dt><strong><a name="item_strings">--enable-strings (default: off)</a></strong><br />
2792	</dt>
2793	<dd>
2794	Add support for our possibly faster <code>memset()</code> function and other
2795	various routines, overriding your system's versions which may
2796	have been hand-crafted in assembly or may require extra libraries
2797	to link in. (this breaks ANSI-C rules and has problems on many
2798	GNU/Linux systems).
2799	</dd>	2433	</dd>
2800	<p></p>	2434	<p></p>
2801	<dt><strong><a name="item__2d_2ddisable_2dswapscreen">--disable-swapscreen</a></strong><br />	2435	<dt><strong><a name="item__2d_2ddisable_2dswapscreen">--disable-swapscreen</a></strong><br />
2802	</dt>	2436	</dt>
2803	<dd>	2437	<dd>
…		…
2817	</dd>	2451	</dd>
2818	<dd>	2452	<dd>
2819	<pre>	2453	<pre>
2820	MWM-hints	2454	MWM-hints
2821	EWMH-hints (pid, utf8 names) and protocols (ping)	2455	EWMH-hints (pid, utf8 names) and protocols (ping)
2822	seperate underline colour	2456	seperate underline colour (-underlineColor)
2823	settable border widths and borderless switch	2457	settable border widths and borderless switch (-w, -b, -bl)
		2458	visual depth selection (-depth)
2824	settable extra linespacing	2459	settable extra linespacing /-lsp)
2825	iso-14755-2 and -3, and visual feedback	2460	iso-14755-2 and -3, and visual feedback
		2461	tripleclickwords (-tcw)
		2462	settable insecure mode (-insecure)
		2463	keysym remapping support
		2464	cursor blinking and underline cursor (-cb, -uc)
		2465	XEmbed support (-embed)
		2466	user-pty (-pty-fd)
		2467	hold on exit (-hold)
		2468	skip builtin block graphics (-sbg)</pre>
		2469	</dd>
		2470	<dd>
		2471	<p>It also enabled some non-essential features otherwise disabled, such as:</p>
		2472	</dd>
		2473	<dd>
		2474	<pre>
		2475	some round-trip time optimisations
		2476	nearest color allocation on pseudocolor screens
		2477	UTF8_STRING supporr for selection
		2478	sgr modes 90..97 and 100..107
2826	backindex and forwardindex escape sequence	2479	backindex and forwardindex escape sequences
		2480	view change/zero scorllback esacpe sequences
		2481	locale switching escape sequence
2827	window op and some xterm/OSC escape sequences	2482	window op and some xterm/OSC escape sequences
2828	tripleclickwords	2483	rectangular selections
2829	settable insecure mode	2484	trailing space removal for selections
2830	keysym remapping support	2485	verbose X error handling</pre>
2831	cursor blinking and underline cursor
2832	-embed, -pty-fd and -hold options</pre>
2833	</dd>	2486	</dd>
2834	<p></p>	2487	<p></p>
2835	<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />	2488	<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />
2836	</dt>	2489	</dt>
2837	<dd>	2490	<dd>
…		…
2898	<p></p>	2551	<p></p>
2899	<dt><strong><a name="item_blank">--enable-pointer-blank (default: on)</a></strong><br />	2552	<dt><strong><a name="item_blank">--enable-pointer-blank (default: on)</a></strong><br />
2900	</dt>	2553	</dt>
2901	<dd>	2554	<dd>
2902	Add support to have the pointer disappear when typing or inactive.	2555	Add support to have the pointer disappear when typing or inactive.
		2556	</dd>
		2557	<p></p>
		2558	<dt><strong><a name="item_perl">--enable-perl (default: on)</a></strong><br />
		2559	</dt>
		2560	<dd>
		2561	Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
		2562	manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files
		2563	in <em>src/perl-ext/</em> for the extensions that are installed by default. The
		2564	perl interpreter that is used can be specified via the <code>PERL</code> environment
		2565	variable when running configure.
2903	</dd>	2566	</dd>
2904	<p></p>	2567	<p></p>
2905	<dt><strong>--with-name=NAME (default: urxvt)</strong><br />	2568	<dt><strong>--with-name=NAME (default: urxvt)</strong><br />
2906	</dt>	2569	</dt>
2907	<dd>	2570	<dd>

Diff Legend

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