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

Diff Legend

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