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.37 by root, Tue Jan 10 04:26:54 2006 UTC vs.
Revision 1.72 by root, Wed Feb 22 10:42:49 2006 UTC

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

Diff Legend

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