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.25 by root, Tue Nov 8 17:35:28 2005 UTC vs.
Revision 1.60 by root, Tue Jan 31 20:50:48 2006 UTC

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

Diff Legend

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