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.52 by root, Sat Jan 28 22:16:58 2006 UTC vs.
Revision 1.72 by root, Wed Feb 22 10:42:49 2006 UTC

…		…
13	<ul>	13	<ul>
14		14
15	<li><a href="#name">NAME</a></li>	15	<li><a href="#name">NAME</a></li>
16	<li><a href="#synopsis">SYNOPSIS</a></li>	16	<li><a href="#synopsis">SYNOPSIS</a></li>
17	<li><a href="#description">DESCRIPTION</a></li>	17	<li><a href="#description">DESCRIPTION</a></li>
18	<li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li>	18	<li><a href="#rxvtunicode_urxvt_frequently_asked_questions">RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS</a></li>
		19	<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_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li>
		29	<li><a href="#how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></li>
		30	<li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li>
		31	<li><a href="#how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></li>
		32	<li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li>
		33	<li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li>
		34	<li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li>
		35	</ul>
		36
		37	<li><a href="#rendering__font___look_and_feel_issues">Rendering, Font &amp; Look and Feel Issues</a></li>
		38	<ul>
		39
		40	<li><a href="#i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></li>
		41	<li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li>
		42	<li><a href="#how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></li>
		43	<li><a href="#some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></li>
		44	<li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li>
		45	<li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li>
		46	<li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li>
		47	<li><a href="#rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></li>
		48	<li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li>
		49	<li><a href="#i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></li>
		50	<li><a href="#why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></li>
		51	<li><a href="#how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></li>
		52	<li><a href="#why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></li>
		53	</ul>
		54
		55	<li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></li>
		56	<ul>
		57
		58	<li><a href="#the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></li>
		59	<li><a href="#i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></li>
		60	<li><a href="#the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></li>
		61	<li><a href="#during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></li>
		62	<li><a href="#my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></li>
		63	<li><a href="#my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></li>
		64	<li><a href="#i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></li>
		65	<li><a href="#mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></li>
		66	<li><a href="#what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></li>
		67	<li><a href="#i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></li>
		68	<li><a href="#i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></li>
		69	</ul>
		70
		71	<li><a href="#terminal_configuration">Terminal Configuration</a></li>
		72	<ul>
		73
		74	<li><a href="#can_i_see_a_typical_configuration">Can I see a typical configuration?</a></li>
		75	<li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li>
		76	<li><a href="#when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></li>
		77	<li><a href="#tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></li>
		78	<li><a href="#bash_s_readline_does_not_work_correctly_under_urxvt_"><code>bash</code>'s readline does not work correctly under urxvt.</a></li>
		79	<li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li>
		80	<li><a href="#why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></li>
		81	<li><a href="#why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></li>
		82	<li><a href="#why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></li>
		83	<li><a href="#why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></li>
		84	</ul>
		85
		86	<li><a href="#encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></li>
		87	<ul>
		88
		89	<li><a href="#rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></li>
		90	<li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</a></li>
		91	<li><a href="#how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></li>
		92	<li><a href="#is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></li>
		93	<li><a href="#can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></li>
		94	<li><a href="#i_have_problems_getting_my_input_method_working_">I have problems getting my input method working.</a></li>
		95	<li><a href="#my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></li>
		96	<li><a href="#rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></li>
		97	</ul>
		98
		99	<li><a href="#operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></li>
		100	<ul>
		101
		102	<li><a href="#i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></li>
		103	<li><a href="#i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></li>
		104	<li><a href="#i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></li>
		105	<li><a href="#on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></li>
		106	<li><a href="#i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></li>
		107	<li><a href="#i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></li>
		108	<li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li>
		109	</ul>
		110
		111	</ul>
		112
19	<li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li>	113	<li><a href="#rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></li>
20	<li><a href="#description">DESCRIPTION</a></li>	114	<ul>
		115
21	<li><a href="#definitions">Definitions</a></li>	116	<li><a href="#definitions">Definitions</a></li>
22	<li><a href="#values">Values</a></li>	117	<li><a href="#values">Values</a></li>
23	<li><a href="#escape_sequences">Escape Sequences</a></li>	118	<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>	119	<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>	120	<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>	121	<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>
		122	</ul>
		123
27	<li><a href="#xpm">XPM</a></li>	124	<li><a href="#xpm">XPM</a></li>
28	<li><a href="#mouse_reporting">Mouse Reporting</a></li>	125	<li><a href="#mouse_reporting">Mouse Reporting</a></li>
29	<li><a href="#key_codes">Key Codes</a></li>	126	<li><a href="#key_codes">Key Codes</a></li>
30	<li><a href="#configure_options">CONFIGURE OPTIONS</a></li>	127	<li><a href="#configure_options">CONFIGURE OPTIONS</a></li>
31	<li><a href="#authors">AUTHORS</a></li>	128	<li><a href="#authors">AUTHORS</a></li>
…		…
54	</p>	151	</p>
55	<hr />	152	<hr />
56	<h1><a name="description">DESCRIPTION</a></h1>	153	<h1><a name="description">DESCRIPTION</a></h1>
57	<p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	154	<p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
58	all escape sequences, and other background information.</p>	155	all escape sequences, and other background information.</p>
59	<p>The newest version of this document is	156	<p>The newest version of this document is also available on the World Wide Web at
60	also available on the World Wide Web at
61	<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>	157	<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
62	<p>	158	<p>
63	</p>	159	</p>
64	<hr />	160	<hr />
65	<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>	161	<h1><a name="rxvtunicode_urxvt_frequently_asked_questions">RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS</a></h1>
66	<dl>
67	<dt><strong><a name="item_the_new_selection_selects_pieces_that_are_too_big_">The new selection selects pieces that are too big, how can I select
68	single words?</a></strong><br />
69	</dt>
70	<dd>
71	Yes. For example, if you want to select alphanumeric words, you can use
72	the following resource:
73	</dd>
74	<dd>
75	<pre>	162	<p>
76	URxvt.selection.pattern-0: ([[:word:]]+)</pre>	163	</p>
77	</dd>	164	<h2><a name="meta__features___commandline_issues">Meta, Features &amp; Commandline Issues</a></h2>
78	<dd>
79	<p>If you click more than twice, the selection will be extended
80	more and more.</p>
81	</dd>
82	<dd>
83	<p>To get a selection that is very similar to the old code, try this pattern:</p>
84	</dd>
85	<dd>
86	<pre>	165	<p>
87	URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>	166	</p>
88	</dd>	167	<h3><a name="my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></h3>
89	<dd>	168	<p>Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>,
90	<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also	169	channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be
91	selects words like the old code.</p>	170	interested in learning about new and exciting problems (but not FAQs :).</p>
92	</dd>
93	<p></p>
94	<dt><strong><a name="item_i_don_27t_like_the_new_selection_2fpopups_2fhotkey">I don't like the new selection/popups/hotkeys/perl, how do I
95	change/disable it?</a></strong><br />
96	</dt>
97	<dd>
98	You can disable the perl extension completely by setting the
99	<strong>perl-ext-common</strong> resource to the empty string, which also keeps
100	rxvt-unicode from initialising perl, saving memory.
101	</dd>
102	<dd>
103	<p>If you only want to disable specific features, you first have to
104	identify which perl extension is responsible. For this, read the section
105	<strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For
106	example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify
107	this <strong>perl-ext-common</strong> resource:</p>
108	</dd>
109	<dd>
110	<pre>	171	<p>
111	URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>	172	</p>
112	</dd>	173	<h3><a name="does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></h3>
113	<dd>	174	<p>Beginning with version 7.3, there is a perl extension that implements a
114	<p>This will keep the default extensions, but disable the two popup	175	simple tabbed terminal. It is installed by default, so any of these should
115	extensions. Some extensions can also be configured, for example,	176	give you tabs:</p>
116	scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any	177	<pre>
117	other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>	178	urxvt -pe tabbed</pre>
118	</dd>	179	<pre>
119	<dd>	180	URxvt.perl-ext-common: default,tabbed</pre>
		181	<p>It will also work fine with tabbing functionality of many window managers
		182	or similar tabbing programs, and its embedding-features allow it to be
		183	embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or
		184	the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt
		185	(murxvt) terminal as an example embedding application.</p>
120	<pre>	186	<p>
121	URxvt.searchable-scrollback: CM-s</pre>	187	</p>
122	</dd>	188	<h3><a name="how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></h3>
123	<p></p>	189	<p>The version number is displayed with the usage (-h). Also the escape
		190	sequence <code>ESC [ 8 n</code> sets the window title to the version number. When
		191	using the urxvtc client, the version displayed is that of the
		192	daemon.</p>
		193	<p>
		194	</p>
		195	<h3><a name="rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></h3>
		196	<p>Rxvt-unicode tries to obey the rule of not charging you for something you
		197	don't use. One thing you should try is to configure out all settings that
		198	you don't need, for example, Xft support is a resource hog by design,
		199	when used. Compiling it out ensures that no Xft font will be loaded
		200	accidentally when rxvt-unicode tries to find a font for your characters.</p>
		201	<p>Also, many people (me included) like large windows and even larger
		202	scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use
		203	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		204	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		205	use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as
		206	rxvt-unicode then uses 8 bytes per screen cell.</p>
		207	<p>
		208	</p>
		209	<h3><a name="how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></h3>
		210	<p>Try <code>urxvtd -f -o</code>, which tells urxvtd to open the
		211	display, create the listening socket and then fork.</p>
		212	<p>
		213	</p>
		214	<h3><a name="how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></h3>
		215	<p>If you want to start urxvtd automatically whenever you run
		216	urxvtc and the daemon isn't running yet, use this script:</p>
		217	<pre>
		218	#!/bin/sh
		219	urxvtc &quot;$@&quot;
		220	if [ $? -eq 2 ]; then
		221	urxvtd -q -o -f
		222	urxvtc &quot;$@&quot;
		223	fi</pre>
		224	<p>This tries to create a new terminal, and if fails with exit status 2,
		225	meaning it couldn't connect to the daemon, it will start the daemon and
		226	re-run the command. Subsequent invocations of the script will re-use the
		227	existing daemon.</p>
		228	<p>
		229	</p>
		230	<h3><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3>
		231	<p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'',
		232	so you can check and see if that is set. Note that several programs, JED,
		233	slrn, Midnight Commander automatically check this variable to decide
		234	whether or not to use color.</p>
		235	<p>
		236	</p>
		237	<h3><a name="how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></h3>
		238	<p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		239	insecure mode then it is possible to use the following shell script
		240	snippets to correctly set the display. If your version of rxvt-unicode
		241	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		242	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		243	regular xterm.</p>
		244	<p>Courtesy of Chuck Blake &lt;<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>&gt; with the following shell script
		245	snippets:</p>
		246	<pre>
		247	# Bourne/Korn/POSIX family of shells:
		248	[ ${TERM:-foo} = foo ] &amp;&amp; TERM=xterm # assume an xterm if we don't know
		249	if [ ${TERM:-foo} = xterm ]; then
		250	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		251	echo -n '^[Z'
		252	read term_id
		253	stty icanon echo
		254	if [ &quot;&quot;${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		255	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		256	read DISPLAY # set it in our local shell
		257	fi
		258	fi</pre>
		259	<p>
		260	</p>
		261	<h3><a name="how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></h3>
		262	<p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>,
		263	one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to
		264	the doc subdirectory and enter <code>make alldoc</code>.</p>
		265	<p>
		266	</p>
124	<dt><strong><a name="item_isn_27t_rxvt_supposed_to_be_small_3f_don_27t_all_t">Isn't rxvt supposed to be small? Don't all those features bloat?</a></strong><br />	267	<h3><a name="isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></h3>
125	</dt>
126	<dd>
127	I often get asked about this, and I think, no, they didn't cause extra	268	<p>I often get asked about this, and I think, no, they didn't cause extra
128	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see	269	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
129	that the urxvt binary is larger (due to some encoding tables always being	270	that the urxvt binary is larger (due to some encoding tables always being
130	compiled in), but it actually uses less memory (RSS) after startup. Even	271	compiled in), but it actually uses less memory (RSS) after startup. Even
131	with <code>--disable-everything</code>, this comparison is a bit unfair, as many	272	with <code>--disable-everything</code>, this comparison is a bit unfair, as many
132	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are	273	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
133	already in use in this mode.	274	already in use in this mode.</p>
134	</dd>
135	<dd>
136	<pre>	275	<pre>
137	text data bss drs rss filename	276	text data bss drs rss filename
138	98398 1664 24 15695 1824 rxvt --disable-everything	277	98398 1664 24 15695 1824 rxvt --disable-everything
139	188985 9048 66616 18222 1788 urxvt --disable-everything</pre>	278	188985 9048 66616 18222 1788 urxvt --disable-everything</pre>
140	</dd>
141	<dd>
142	<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft	279	<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which <em>is</em> unfair, as this involves xft
143	and full locale/XIM support which are quite bloaty inside libX11 and my	280	and full locale/XIM support which are quite bloaty inside libX11 and my
144	libc), the two diverge, but not unreasnobaly so.</p>	281	libc), the two diverge, but not unreasnobaly so.</p>
145	</dd>
146	<dd>
147	<pre>	282	<pre>
148	text data bss drs rss filename	283	text data bss drs rss filename
149	163431 2152 24 20123 2060 rxvt --enable-everything	284	163431 2152 24 20123 2060 rxvt --enable-everything
150	1035683 49680 66648 29096 3680 urxvt --enable-everything</pre>	285	1035683 49680 66648 29096 3680 urxvt --enable-everything</pre>
151	</dd>
152	<dd>
153	<p>The very large size of the text section is explained by the east-asian	286	<p>The very large size of the text section is explained by the east-asian
154	encoding tables, which, if unused, take up disk space but nothing else	287	encoding tables, which, if unused, take up disk space but nothing else
155	and can be compiled out unless you rely on X11 core fonts that use those	288	and can be compiled out unless you rely on X11 core fonts that use those
156	encodings. The BSS size comes from the 64k emergency buffer that my c++	289	encodings. The BSS size comes from the 64k emergency buffer that my c++
157	compiler allocates (but of course doesn't use unless you are out of	290	compiler allocates (but of course doesn't use unless you are out of
158	memory). Also, using an xft font instead of a core font immediately adds a	291	memory). Also, using an xft font instead of a core font immediately adds a
159	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when	292	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
160	not used.</p>	293	not used.</p>
161	</dd>
162	<dd>
163	<p>Of course, due to every character using two or four bytes instead of one,	294	<p>Of course, due to every character using two or four bytes instead of one,
164	a large scrollback buffer will ultimately make rxvt-unicode use more	295	a large scrollback buffer will ultimately make rxvt-unicode use more
165	memory.</p>	296	memory.</p>
166	</dd>
167	<dd>
168	<p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this	297	<p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
169	still fares rather well. And compared to some monsters like gnome-terminal	298	still fares rather well. And compared to some monsters like gnome-terminal
170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	299	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
171	43180k in daemons that stay around after exit, plus half a minute of	300	43180k in daemons that stay around after exit, plus half a minute of
172	startup time, including the hundreds of warnings it spits out), it fares	301	startup time, including the hundreds of warnings it spits out), it fares
173	extremely well *g*.</p>	302	extremely well *g*.</p>
174	</dd>	303	<p>
175	<p></p>	304	</p>
176	<dt><strong><a name="item_why_c_2b_2b_2c_isn_27t_that_unportable_2fbloated_2">Why C++, isn't that unportable/bloated/uncool?</a></strong><br />	305	<h3><a name="why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></h3>
177	</dt>
178	<dd>
179	Is this a question? :) It comes up very often. The simple answer is: I had	306	<p>Is this a question? :) It comes up very often. The simple answer is: I had
180	to write it, and C++ allowed me to write and maintain it in a fraction	307	to write it, and C++ allowed me to write and maintain it in a fraction
181	of the time and effort (which is a scarce resource for me). Put even	308	of the time and effort (which is a scarce resource for me). Put even
182	shorter: It simply wouldn't exist without C++.	309	shorter: It simply wouldn't exist without C++.</p>
183	</dd>
184	<dd>
185	<p>My personal stance on this is that C++ is less portable than C, but in	310	<p>My personal stance on this is that C++ is less portable than C, but in
186	the case of rxvt-unicode this hardly matters, as its portability limits	311	the case of rxvt-unicode this hardly matters, as its portability limits
187	are defined by things like X11, pseudo terminals, locale support and unix	312	are defined by things like X11, pseudo terminals, locale support and unix
188	domain sockets, which are all less portable than C++ itself.</p>	313	domain sockets, which are all less portable than C++ itself.</p>
189	</dd>
190	<dd>
191	<p>Regarding the bloat, see the above question: It's easy to write programs	314	<p>Regarding the bloat, see the above question: It's easy to write programs
192	in C that use gobs of memory, an certainly possible to write programs in	315	in C that use gobs of memory, an certainly possible to write programs in
193	C++ that don't. C++ also often comes with large libraries, but this is	316	C++ that don't. C++ also often comes with large libraries, but this is
194	not necessarily the case with GCC. Here is what rxvt links against on my	317	not necessarily the case with GCC. Here is what rxvt links against on my
195	system with a minimal config:</p>	318	system with a minimal config:</p>
196	</dd>
197	<dd>
198	<pre>	319	<pre>
199	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	320	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
200	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)	321	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)
201	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)	322	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)
202	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>	323	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
203	</dd>
204	<dd>
205	<p>And here is rxvt-unicode:</p>	324	<p>And here is rxvt-unicode:</p>
206	</dd>
207	<dd>
208	<pre>	325	<pre>
209	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	326	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
210	libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)	327	libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)
211	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)	328	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)
212	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)	329	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)
213	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>	330	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
214	</dd>
215	<dd>
216	<p>No large bloated libraries (of course, none were linked in statically),	331	<p>No large bloated libraries (of course, none were linked in statically),
217	except maybe libX11 :)</p>	332	except maybe libX11 :)</p>
218	</dd>
219	<p></p>
220	<dt><strong><a name="item_does_it_support_tabs_2c_can_i_have_a_tabbed_rxvt_2">Does it support tabs, can I have a tabbed rxvt-unicode?</a></strong><br />
221	</dt>
222	<dd>
223	Beginning with version 7.3, there is a perl extension that implements a
224	simple tabbed terminal. It is installed by default, so any of these should
225	give you tabs:
226	</dd>
227	<dd>
228	<pre>	333	<p>
229	rxvt -pe tabbed</pre>	334	</p>
230	</dd>	335	<h2><a name="rendering__font___look_and_feel_issues">Rendering, Font &amp; Look and Feel Issues</a></h2>
231	<dd>
232	<pre>	336	<p>
		337	</p>
		338	<h3><a name="i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></h3>
		339	<p>First of all, transparency isn't officially supported in rxvt-unicode, so
		340	you are mostly on your own. Do not bug the author about it (but you may
		341	bug everybody else). Also, if you can't get it working consider it a rite
		342	of passage: ... and you failed.</p>
		343	<p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option
		344	descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p>
		345	<p>1. Use inheritPixmap:</p>
		346	<pre>
		347	Esetroot wallpaper.jpg
		348	urxvt -ip -tint red -sh 40</pre>
		349	<p>That works. If you think it doesn't, you lack transparency and tinting
		350	support, or you are unable to read.</p>
		351	<p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		352	to use effects other than tinting and shading: Just shade/tint/whatever
		353	your picture with gimp or any other tool:</p>
		354	<pre>
		355	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		356	urxvt -pixmap background.xpm -pe automove-background</pre>
		357	<p>That works. If you think it doesn't, you lack XPM and Perl support, or you
		358	are unable to read.</p>
		359	<p>3. Use an ARGB visual:</p>
		360	<pre>
		361	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>
		362	<p>This requires XFT support, and the support of your X-server. If that
		363	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		364	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		365	bugfixes and workarounds for Xft and Xlib to make it work, but that
		366	doesn't mean that your WM has the required kludges in place.</p>
		367	<p>4. Use xcompmgr and let it do the job:</p>
		368	<pre>
		369	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		370	-set _NET_WM_WINDOW_OPACITY 0xc0000000</pre>
		371	<p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code>
		372	by other values to change the degree of opacity. If it doesn't work and
		373	your server crashes, you got to keep the pieces.</p>
		374	<p>
		375	</p>
		376	<h3><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h3>
		377	<p>Most fonts were not designed for terminal use, which means that character
		378	size varies a lot. A font that is otherwise fine for terminal use might
		379	contain some characters that are simply too wide. Rxvt-unicode will avoid
		380	these characters. For characters that are just ``a bit'' too wide a special
		381	``careful'' rendering mode is used that redraws adjacent characters.</p>
		382	<p>All of this requires that fonts do not lie about character sizes,
		383	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		384	box, and rxvt-unicode has no way of detecting this (the correct way is to
		385	ask for the character bounding box, which unfortunately is wrong in these
		386	cases).</p>
		387	<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,
		388	or the respective font. If you encounter this problem you might try using
		389	the <code>-lsp</code> option to give the font more height. If that doesn't work, you
		390	might be forced to use a different font.</p>
		391	<p>All of this is not a problem when using X11 core fonts, as their bounding
		392	box data is correct.</p>
		393	<p>
		394	</p>
		395	<h3><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h3>
		396	<p>First of all, make sure you are running with the right terminal settings
		397	(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
		398	make sure you have specified colours for italic and bold, as otherwise
		399	rxvt-unicode might use reverse video to simulate the effect:</p>
		400	<pre>
		401	URxvt.colorBD: white
		402	URxvt.colorIT: green</pre>
		403	<p>
		404	</p>
		405	<h3><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h3>
		406	<p>For some unexplainable reason, some rare programs assume a very weird
		407	colour palette when confronted with a terminal with more than the standard
		408	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		409	these programs not to assume non-ISO colours without very good reasons.</p>
		410	<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
		411	definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
		412	fix colours but keep you from using other rxvt-unicode features.</p>
		413	<p>
		414	</p>
		415	<h3><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h3>
		416	<p>Yes, using an escape sequence. Try something like this, which has the same
		417	effect as using the <code>-fn</code> switch, and takes effect immediately:</p>
		418	<pre>
		419	printf '\33]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
		420	<p>This is useful if you e.g. work primarily with japanese (and prefer a
		421	japanese font), but you have to switch to chinese temporarily, where
		422	japanese fonts would only be in your way.</p>
		423	<p>You can think of this as a kind of manual ISO-2022 switching.</p>
		424	<p>
		425	</p>
		426	<h3><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h3>
		427	<p>Many fonts have difficulties with italic characters and hinting. For
		428	example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
		429	Mono</code> completely fails in it's italic face. A workaround might be to
		430	enable freetype autohinting, i.e. like this:</p>
		431	<pre>
		432	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		433	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
		434	<p>
		435	</p>
		436	<h3><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h3>
		437	<p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		438	it is simply slow. If you still want Xft fonts you might try to disable
		439	antialiasing (by appending <code>:antialias=false</code>), which saves lots of
		440	memory and also speeds up rendering considerably.</p>
		441	<p>
		442	</p>
		443	<h3><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h3>
		444	<p>Rxvt-unicode will use whatever you specify as a font. If it needs to
		445	fall back to it's default font search list it will prefer X11 core
		446	fonts, because they are small and fast, and then use Xft fonts. It has
		447	antialiasing disabled for most of them, because the author thinks they
		448	look best that way.</p>
		449	<p>If you want antialiasing, you have to specify the fonts manually.</p>
		450	<p>
		451	</p>
		452	<h3><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h3>
		453	<p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
		454	standard foreground colour.</p>
		455	<p>For the standard background colour, blinking will actually make the
		456	text blink when compiled with <code>--enable-blinking</code>. with standard
		457	colours. Without <code>--enable-blinking</code>, the blink attribute will be
		458	ignored.</p>
		459	<p>On ANSI colours, bold/blink attributes are used to set high-intensity
		460	foreground/background colors.</p>
		461	<p>color0-7 are the low-intensity colors.</p>
		462	<p>color8-15 are the corresponding high-intensity colors.</p>
		463	<p>
		464	</p>
		465	<h3><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></h3>
		466	<p>You can change the screen colors at run-time using <em>~/.Xdefaults</em>
		467	resources (or as long-options).</p>
		468	<p>Here are values that are supposed to resemble a VGA screen,
		469	including the murky brown that passes for low-intensity yellow:</p>
		470	<pre>
		471	URxvt.color0: #000000
		472	URxvt.color1: #A80000
		473	URxvt.color2: #00A800
		474	URxvt.color3: #A8A800
		475	URxvt.color4: #0000A8
		476	URxvt.color5: #A800A8
		477	URxvt.color6: #00A8A8
		478	URxvt.color7: #A8A8A8</pre>
		479	<pre>
		480	URxvt.color8: #000054
		481	URxvt.color9: #FF0054
		482	URxvt.color10: #00FF54
		483	URxvt.color11: #FFFF54
		484	URxvt.color12: #0000FF
		485	URxvt.color13: #FF00FF
		486	URxvt.color14: #00FFFF
		487	URxvt.color15: #FFFFFF</pre>
		488	<p>And here is a more complete set of non-standard colors.</p>
		489	<pre>
		490	URxvt.cursorColor: #dc74d1
		491	URxvt.pointerColor: #dc74d1
		492	URxvt.background: #0e0e0e
		493	URxvt.foreground: #4ad5e1
		494	URxvt.color0: #000000
		495	URxvt.color8: #8b8f93
		496	URxvt.color1: #dc74d1
		497	URxvt.color9: #dc74d1
		498	URxvt.color2: #0eb8c7
		499	URxvt.color10: #0eb8c7
		500	URxvt.color3: #dfe37e
		501	URxvt.color11: #dfe37e
		502	URxvt.color5: #9e88f0
		503	URxvt.color13: #9e88f0
		504	URxvt.color6: #73f7ff
		505	URxvt.color14: #73f7ff
		506	URxvt.color7: #e1dddd
		507	URxvt.color15: #e1dddd</pre>
		508	<p>They have been described (not by me) as ``pretty girly''.</p>
		509	<p>
		510	</p>
		511	<h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3>
		512	<p>See next entry.</p>
		513	<p>
		514	</p>
		515	<h3><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h3>
		516	<p>Most fonts do not contain the full range of Unicode, which is
		517	fine. Chances are that the font you (or the admin/package maintainer of
		518	your system/os) have specified does not cover all the characters you want
		519	to display.</p>
		520	<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement
		521	font. Often the result is fine, but sometimes the chosen font looks
		522	bad/ugly/wrong. Some fonts have totally strange characters that don't
		523	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		524	intelligence to detect that a specific glyph is wrong: it has to believe
		525	the font that the characters it claims to contain indeed look correct.</p>
		526	<p>In that case, select a font of your taste and add it to the font list,
		527	e.g.:</p>
		528	<pre>
		529	urxvt -fn basefont,font2,font3...</pre>
		530	<p>When rxvt-unicode sees a character, it will first look at the base
		531	font. If the base font does not contain the character, it will go to the
		532	next font, and so on. Specifying your own fonts will also speed up this
		533	search and use less resources within rxvt-unicode and the X-server.</p>
		534	<p>The only limitation is that none of the fonts may be larger than the base
		535	font, as the base font defines the terminal character cell size, which
		536	must be the same due to the way terminals work.</p>
		537	<p>
		538	</p>
		539	<h3><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h3>
		540	<p>This is because there is a difference between script and language --
		541	rxvt-unicode does not know which language the text that is output is,
		542	as it only knows the unicode character codes. If rxvt-unicode first
		543	sees a japanese/chinese character, it might choose a japanese font for
		544	display. Subsequent japanese characters will use that font. Now, many
		545	chinese characters aren't represented in japanese fonts, so when the first
		546	non-japanese character comes up, rxvt-unicode will look for a chinese font
		547	-- unfortunately at this point, it will still use the japanese font for
		548	chinese characters that are also in the japanese font.</p>
		549	<p>The workaround is easy: just tag a chinese font at the end of your font
		550	list (see the previous question). The key is to view the font list as
		551	a preference list: If you expect more japanese, list a japanese font
		552	first. If you expect more chinese, put a chinese font first.</p>
		553	<p>In the future it might be possible to switch language preferences at
		554	runtime (the internal data structure has no problem with using different
		555	fonts for the same character at the same time, but no interface for this
		556	has been designed yet).</p>
		557	<p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p>
		558	<p>
		559	</p>
		560	<h2><a name="keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></h2>
		561	<p>
		562	</p>
		563	<h3><a name="the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></h3>
		564	<p>If you want to select e.g. alphanumeric words, you can use the following
		565	setting:</p>
		566	<pre>
		567	URxvt.selection.pattern-0: ([[:word:]]+)</pre>
		568	<p>If you click more than twice, the selection will be extended
		569	more and more.</p>
		570	<p>To get a selection that is very similar to the old code, try this pattern:</p>
		571	<pre>
		572	URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>
		573	<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also
		574	selects words like the old code.</p>
		575	<p>
		576	</p>
		577	<h3><a name="i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></h3>
		578	<p>You can disable the perl extension completely by setting the
		579	<strong>perl-ext-common</strong> resource to the empty string, which also keeps
		580	rxvt-unicode from initialising perl, saving memory.</p>
		581	<p>If you only want to disable specific features, you first have to
		582	identify which perl extension is responsible. For this, read the section
		583	<strong>PREPACKAGED EXTENSIONS</strong> in the <code>urxvtperl(3)</code> manpage. For
		584	example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify
		585	this <strong>perl-ext-common</strong> resource:</p>
		586	<pre>
		587	URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>
		588	<p>This will keep the default extensions, but disable the two popup
		589	extensions. Some extensions can also be configured, for example,
		590	scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any
		591	other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>
		592	<pre>
		593	URxvt.searchable-scrollback: CM-s</pre>
		594	<p>
		595	</p>
		596	<h3><a name="the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></h3>
		597	<p>See next entry.</p>
		598	<p>
		599	</p>
		600	<h3><a name="during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></h3>
		601	<p>These are caused by the <code>readline</code> perl extension. Under normal
		602	circumstances, it will move your cursor around when you click into the
		603	line that contains it. It tries hard not to do this at the wrong moment,
		604	but when running a program that doesn't parse cursor movements or in some
		605	cases during rlogin sessions, it fails to detect this properly.</p>
		606	<p>You can permamently switch this feature off by disabling the <code>readline</code>
		607	extension:</p>
		608	<pre>
233	URxvt.perl-ext-common: default,tabbed</pre>	609	URxvt.perl-ext-common: default,-readline</pre>
234	</dd>	610	<p>
235	<dd>	611	</p>
236	<p>It will also work fine with tabbing functionality of many window managers	612	<h3><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h3>
237	or similar tabbing programs, and its embedding-features allow it to be	613	<p>Some Debian GNUL/Linux users seem to have this problem, although no
238	embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or	614	specific details were reported so far. It is possible that this is caused
239	the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt	615	by the wrong <code>TERM</code> setting, although the details of wether and how
240	(murxvt) terminal as an example embedding application.</p>	616	this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
241	</dd>	617	keymap. See the answer to the previous question, and please report if that
242	<p></p>	618	helped.</p>
243	<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 />	619	<p>
244	</dt>	620	</p>
245	<dd>	621	<h3><a name="my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></h3>
246	The version number is displayed with the usage (-h). Also the escape	622	<p>The most common causes for this are that either your locale is not set
247	sequence <code>ESC [ 8 n</code> sets the window title to the version number. When	623	correctly, or you specified a <strong>preeditStyle</strong> that is not supported by
248	using the rxvtc client, the version displayed is that of the	624	your input method. For example, if you specified <strong>OverTheSpot</strong> and
249	daemon.	625	your input method (e.g. the default input method handling Compose keys)
250	</dd>	626	does not support this (for instance because it is not visual), then
251	<p></p>	627	rxvt-unicode will continue without an input method.</p>
252	<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 />	628	<p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than
253	</dt>	629	one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p>
254	<dd>	630	<p>
255	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	631	</p>
256	patches that considerably change the behaviour of rxvt-unicode (but	632	<h3><a name="i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></h3>
257	unfortunately this notice has been removed). Before reporting a bug to	633	<p>Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on
258	the original rxvt-unicode author please download and install the genuine	634	international keyboards) or simply use ISO 14755 support to your
259	version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce	635	advantage, typing &lt;Ctrl-Shift-0&gt; to get a ASCII NUL. This works for other
260	the problem. If you cannot, chances are that the problems are specific to	636	codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape
261	Debian GNU/Linux, in which case it should be reported via the Debian Bug	637	character and so on.</p>
262	Tracking System (use <code>reportbug</code> to report the bug).	638	<p>
263	</dd>	639	</p>
264	<dd>	640	<h3><a name="mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></h3>
265	<p>For other problems that also affect the Debian package, you can and	641	<p>Make sure that mouse reporting is actually turned off since killing
266	probably should use the Debian BTS, too, because, after all, it's also a	642	some editors prematurely may leave the mouse in mouse report mode. I've
267	bug in the Debian version and it serves as a reminder for other users that	643	heard that tcsh may use mouse reporting unless it otherwise specified. A
268	might encounter the same issue.</p>	644	quick check is to see if cut/paste works when the Alt or Shift keys are
269	</dd>	645	depressed.</p>
270	<p></p>	646	<p>
271	<dt><strong><a name="item_i_am_maintaining_rxvt_2dunicode_for_distribution_2">I am maintaining rxvt-unicode for distribution/OS XXX, any	647	</p>
272	recommendation?</a></strong><br />	648	<h3><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h3>
273	</dt>	649	<p>Assuming that the physical Backspace key corresponds to the
274	<dd>	650	BackSpace keysym (not likely for Linux ... see the following
275	You should build one binary with the default options. <em>configure</em>	651	question) there are two standard values that can be used for
276	now enables most useful options, and the trend goes to making them	652	Backspace: <code>^H</code> and <code>^?</code>.</p>
277	runtime-switchable, too, so there is usually no drawback to enbaling them,	653	<p>Historically, either value is correct, but rxvt-unicode adopts the debian
278	except higher disk and possibly memory usage. The perl interpreter should	654	policy of using <code>^?</code> when unsure, because it's the one only only correct
279	be enabled, as important functionality (menus, selection, likely more in	655	choice :).</p>
280	the future) depends on it.	656	<p>Rxvt-unicode tries to inherit the current stty settings and uses the value
281	</dd>	657	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
282	<dd>	658	started from a terminal (say, from a menu or by remote shell), then the
283	<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources	659	system value of `erase', which corresponds to CERASE in &lt;termios.h&gt;, will
284	system-wide (except maybe with <code>defaults</code>). This will result in useful	660	be used (which may not be the same as your stty setting).</p>
285	behaviour. If your distribution aims at low memory, add an empty	661	<p>For starting a new rxvt-unicode:</p>
286	<code>perl-ext-common</code> resource to the app-defaults file. This will keep the	662	<pre>
287	perl interpreter disabled until the user enables it.</p>	663	# use Backspace = ^H
288	</dd>	664	$ stty erase ^H
289	<dd>	665	$ urxvt</pre>
290	<p>If you can/want build more binaries, I recommend building a minimal	666	<pre>
291	one with <code>--disable-everything</code> (very useful) and a maximal one with	667	# use Backspace = ^?
292	<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of	668	$ stty erase ^?
293	encodings built-in that increase download times and are rarely used).</p>	669	$ urxvt</pre>
294	</dd>	670	<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p>
295	<p></p>	671	<p>For an existing rxvt-unicode:</p>
296	<dt><strong><a name="item_i_need_to_make_it_setuid_2fsetgid_to_support_utmp_">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></strong><br />	672	<pre>
297	</dt>	673	# use Backspace = ^H
298	<dd>	674	$ stty erase ^H
299	It should be, starting with release 7.1. You are encouraged to properly	675	$ echo -n &quot;^[[36h&quot;</pre>
300	install urxvt with privileges necessary for your OS now.	676	<pre>
301	</dd>	677	# use Backspace = ^?
302	<dd>	678	$ stty erase ^?
303	<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork	679	$ echo -n &quot;^[[36l&quot;</pre>
304	into a helper process for privileged operations (pty handling on some	680	<p>This helps satisfy some of the Backspace discrepancies that occur, but
305	systems, utmp/wtmp/lastlog handling on others) and drop privileges	681	if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value
306	immediately. This is much safer than most other terminals that keep	682	properly reflects that.</p>
307	privileges while running (but is more relevant to urxvt, as it contains	683	<p>The Delete key is a another casualty of the ill-defined Backspace problem.
308	things as perl interpreters, which might be ``helpful'' to attackers).</p>	684	To avoid confusion between the Backspace and Delete keys, the Delete
309	</dd>	685	key has been assigned an escape sequence to match the vt100 for Execute
310	<dd>	686	(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
311	<p>This forking is done as the very first within main(), which is very early	687	<p>Some other Backspace problems:</p>
312	and reduces possible bugs to initialisation code run before main(), or	688	<p>some editors use termcap/terminfo,
313	things like the dynamic loader of your system, which should result in very	689	some editors (vim I'm told) expect Backspace = ^H,
314	little risk.</p>	690	GNU Emacs (and Emacs-like editors) use ^H for help.</p>
315	</dd>	691	<p>Perhaps someday this will all be resolved in a consistent manner.</p>
316	<p></p>	692	<p>
317	<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 />	693	</p>
318	</dt>	694	<h3><a name="i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></h3>
319	<dd>	695	<p>There are some compile-time selections available via configure. Unless
		696	you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
		697	use the `keysym' resource to alter the keystrings associated with keysyms.</p>
		698	<p>Here's an example for a URxvt session started using <code>urxvt -name URxvt</code></p>
		699	<pre>
		700	URxvt.keysym.Home: \033[1~
		701	URxvt.keysym.End: \033[4~
		702	URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
		703	URxvt.keysym.C-slash: \033&lt;C-/&gt;
		704	URxvt.keysym.C-semicolon: \033&lt;C-;&gt;
		705	URxvt.keysym.C-grave: \033&lt;C-`&gt;
		706	URxvt.keysym.C-comma: \033&lt;C-,&gt;
		707	URxvt.keysym.C-period: \033&lt;C-.&gt;
		708	URxvt.keysym.C-0x60: \033&lt;C-`&gt;
		709	URxvt.keysym.C-Tab: \033&lt;C-Tab&gt;
		710	URxvt.keysym.C-Return: \033&lt;C-Return&gt;
		711	URxvt.keysym.S-Return: \033&lt;S-Return&gt;
		712	URxvt.keysym.S-space: \033&lt;S-Space&gt;
		713	URxvt.keysym.M-Up: \033&lt;M-Up&gt;
		714	URxvt.keysym.M-Down: \033&lt;M-Down&gt;
		715	URxvt.keysym.M-Left: \033&lt;M-Left&gt;
		716	URxvt.keysym.M-Right: \033&lt;M-Right&gt;
		717	URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
		718	URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
		719	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
		720	<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
		721	<p>
		722	</p>
		723	<h3><a name="i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></h3>
		724	<pre>
		725	KP_Insert == Insert
		726	F22 == Print
		727	F27 == Home
		728	F29 == Prior
		729	F33 == End
		730	F35 == Next</pre>
		731	<p>Rather than have rxvt-unicode try to accommodate all the various possible
		732	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		733	required for your particular machine.</p>
		734	<p>
		735	</p>
		736	<h2><a name="terminal_configuration">Terminal Configuration</a></h2>
		737	<p>
		738	</p>
		739	<h3><a name="can_i_see_a_typical_configuration">Can I see a typical configuration?</a></h3>
		740	<p>The default configuration tries to be xterm-like, which I don't like that
		741	much, but it's least surprise to regular users.</p>
		742	<p>As a rxvt or rxvt-unicode user, you are practically supposed to invest
		743	time into customising your terminal. To get you started, here is the
		744	author's .Xdefaults entries, with comments on what they do. It's certainly
		745	not <em>typical</em>, but what's typical...</p>
		746	<pre>
		747	URxvt.cutchars: &quot;()*,&lt;&gt;[]{}|'
		748	URxvt.print-pipe: cat &gt;/tmp/xxx</pre>
		749	<p>These are just for testing stuff.</p>
		750	<pre>
		751	URxvt.imLocale: ja_JP.UTF-8
		752	URxvt.preeditType: OnTheSpot,None</pre>
		753	<p>This tells rxvt-unicode to use a special locale when communicating with
		754	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		755	type, which requires the <code>xim-onthespot</code> perl extension but rewards me
		756	with correct-looking fonts.</p>
		757	<pre>
		758	URxvt.perl-lib: /root/lib/urxvt
		759	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		760	URxvt.selection.pattern-0: ( at .*? line \\d+)
		761	URxvt.selection.pattern-1: ^(/[^:]+):\
		762	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		763	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/</pre>
		764	<p>This is my perl configuration. The first two set the perl library
		765	directory and also tells urxvt to use a large number of extensions. I
		766	develop for myself mostly, so I actually use most of the extensions I
		767	write.</p>
		768	<p>The selection stuff mainly makes the selection perl-error-message aware
		769	and tells it to convert pelr error mssages into vi-commands to load the
		770	relevant file and go tot he error line number.</p>
		771	<pre>
		772	URxvt.scrollstyle: plain
		773	URxvt.secondaryScroll: true</pre>
		774	<p>As the documentation says: plain is the preferred scrollbar for the
		775	author. The <code>secondaryScroll</code> confgiures urxvt to scroll in full-screen
		776	apps, like screen, so lines scorlled out of screen end up in urxvt's
		777	scrollback buffer.</p>
		778	<pre>
		779	URxvt.background: #000000
		780	URxvt.foreground: gray90
		781	URxvt.color7: gray90
		782	URxvt.colorBD: #ffffff
		783	URxvt.cursorColor: #e0e080
		784	URxvt.throughColor: #8080f0
		785	URxvt.highlightColor: #f0f0f0</pre>
		786	<p>Some colours. Not sure which ones are being used or even non-defaults, but
		787	these are in my .Xdefaults. Most notably, they set foreground/background
		788	to light gray/black, and also make sure that the colour 7 matches the
		789	default foreground colour.</p>
		790	<pre>
		791	URxvt.underlineColor: yellow</pre>
		792	<p>Another colour, makes underline lines look different. Sometimes hurts, but
		793	is mostly a nice effect.</p>
		794	<pre>
		795	URxvt.geometry: 154x36
		796	URxvt.loginShell: false
		797	URxvt.meta: ignore
		798	URxvt.utmpInhibit: true</pre>
		799	<p>Uh, well, should be mostly self-explanatory. By specifying some defaults
		800	manually, I can quickly switch them for testing.</p>
		801	<pre>
		802	URxvt.saveLines: 8192</pre>
		803	<p>A large scrollback buffer is essential. Really.</p>
		804	<pre>
		805	URxvt.mapAlert: true</pre>
		806	<p>The only case I use it is for my IRC window, which I like to keep
		807	iconified till people msg me (which beeps).</p>
		808	<pre>
		809	URxvt.visualBell: true</pre>
		810	<p>The audible bell is often annoying, especially when in a crowd.</p>
		811	<pre>
		812	URxvt.insecure: true</pre>
		813	<p>Please don't hack my mutt! Ooops...</p>
		814	<pre>
		815	URxvt.pastableTabs: false</pre>
		816	<p>I once thought this is a great idea.</p>
		817	<pre>
		818	urxvt.font: 9x15bold,\
		819	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		820	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		821	[codeset=JISX0208]xft:Kochi Gothic, \
		822	xft:Bitstream Vera Sans Mono:autohint=true, \
		823	xft:Code2000:antialias=false
		824	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		825	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		826	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
		827	<p>I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		828	overwhelmed. A special note: the <code>9x15bold</code> mentioend above is actually
		829	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		830	font (different glyphs for <code>;</code> and many other harmless characters),
		831	while the second font is actually the <code>9x15bold</code> from XFree4/XOrg. The
		832	bold version has less chars than the medium version, so I use it for rare
		833	characters, too. Whene ditign sources with vim, I use italic for comments
		834	and other stuff, which looks quite good with Bitstream Vera anti-aliased.</p>
		835	<p>Terminus is a quite bad font (many very wrong glyphs), but for most of my
		836	purposes, it works, and gives a different look, as my normal (Non-bold)
		837	font is already bold, and I want to see a difference between bold and
		838	normal fonts.</p>
		839	<p>Please note that I used the <code>urxvt</code> instance name and not the <code>URxvt</code>
		840	class name. Thats because I use different configs for different purposes,
		841	for example, my IRC window is started with <code>-name IRC</code>, and uses these
		842	defaults:</p>
		843	<pre>
		844	IRC*title: IRC
		845	IRC*geometry: 87x12+535+542
		846	IRC*saveLines: 0
		847	IRC*mapAlert: true
		848	IRC*font: suxuseuro
		849	IRC*boldFont: suxuseuro
		850	IRC*colorBD: white
		851	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		852	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007</pre>
		853	<p><code>Alt-Shift-1</code> and <code>Alt-Shift-2</code> switch between two different font
		854	sizes. <code>suxuseuro</code> allows me to keep an eye (and actually read)
		855	stuff while keeping a very small window. If somebody pastes something
		856	complicated (e.g. japanese), I temporarily switch to a larger font.</p>
		857	<p>The above is all in my <code>.Xdefaults</code> (I don't use <code>.Xresources</code> nor
		858	<code>xrdb</code>). I also have some resources in a separate <code>.Xdefaults-hostname</code>
		859	file for different hosts, for example, on ym main desktop, I use:</p>
		860	<pre>
		861	URxvt.keysym.C-M-q: command:\033[3;5;5t
		862	URxvt.keysym.C-M-y: command:\033[3;5;606t
		863	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		864	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		865	URxvt.keysym.C-M-p: perl:test</pre>
		866	<p>The first for keysym definitions allow me to quickly bring some windows
		867	in the layout I like most. Ion users might start laughing but will stop
		868	immediately when I tell them that I use my own Fvwm2 module for much the
		869	same effect as Ion provides, and I only very rarely use the above key
		870	combinations :-&gt;</p>
		871	<p>
		872	</p>
		873	<h3><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h3>
		874	<p>Well, why, indeed? It does, in a way very similar to other X
		875	applications. Most importantly, this means that if you or your OS loads
		876	resources into the X display (the right way to do it), rxvt-unicode will
		877	ignore any resource files in your home directory. It will only read
		878	<em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p>
		879	<p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that
		880	resources are loaded into your X-server. In this case, you have to
		881	re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p>
		882	<p>Also consider the form resources have to use:</p>
		883	<pre>
		884	URxvt.resource: value</pre>
		885	<p>If you want to use another form (there are lots of different ways of
		886	specifying resources), make sure you understand wether and why it
		887	works. If unsure, use the form above.</p>
		888	<p>
		889	</p>
		890	<h3><a name="when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></h3>
320	The terminal description used by rxvt-unicode is not as widely available	891	<p>The terminal description used by rxvt-unicode is not as widely available
321	as that for xterm, or even rxvt (for which the same problem often arises).	892	as that for xterm, or even rxvt (for which the same problem often arises).</p>
322	</dd>
323	<dd>
324	<p>The correct solution for this problem is to install the terminfo, this can	893	<p>The correct solution for this problem is to install the terminfo, this can
325	be done like this (with ncurses' infocmp):</p>	894	be done like this (with ncurses' infocmp):</p>
326	</dd>
327	<dd>
328	<pre>	895	<pre>
329	REMOTE=remotesystem.domain	896	REMOTE=remotesystem.domain
330	infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre>	897	infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre>
331	</dd>
332	<dd>
333	<p>... or by installing rxvt-unicode normally on the remote system,</p>	898	<p>... or by installing rxvt-unicode normally on the remote system,</p>
334	</dd>
335	<dd>
336	<p>If you cannot or do not want to do this, then you can simply set	899	<p>If you cannot or do not want to do this, then you can simply set
337	<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of	900	<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of
338	problems arising, which includes wrong keymapping, less and different	901	problems arising, which includes wrong keymapping, less and different
339	colours and some refresh errors in fullscreen applications. It's a nice	902	colours and some refresh errors in fullscreen applications. It's a nice
340	quick-and-dirty workaround for rare cases, though.</p>	903	quick-and-dirty workaround for rare cases, though.</p>
341	</dd>
342	<dd>
343	<p>If you always want to do this (and are fine with the consequences) you	904	<p>If you always want to do this (and are fine with the consequences) you
344	can either recompile rxvt-unicode with the desired TERM value or use a	905	can either recompile rxvt-unicode with the desired TERM value or use a
345	resource to set it:</p>	906	resource to set it:</p>
346	</dd>
347	<dd>
348	<pre>	907	<pre>
349	URxvt.termName: rxvt</pre>	908	URxvt.termName: rxvt</pre>
350	</dd>
351	<dd>
352	<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace	909	<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace
353	the rxvt terminfo file with the rxvt-unicode one.</p>	910	the rxvt terminfo file with the rxvt-unicode one and use <code>TERM=rxvt</code>.</p>
354	</dd>	911	<p>
355	<p></p>	912	</p>
356	<dt><strong><a name="item_tic_outputs_some_error_when_compiling_the_terminfo"><code>tic</code> outputs some error when compiling the terminfo entry.</a></strong><br />	913	<h3><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h3>
357	</dt>
358	<dd>
359	Most likely it's the empty definition for <code>enacs=</code>. Just replace it by	914	<p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
360	<code>enacs=\E[0@</code> and try again.	915	<code>enacs=\E[0@</code> and try again.</p>
361	</dd>	916	<p>
362	<p></p>	917	</p>
363	<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br />	918	<h3><a name="bash_s_readline_does_not_work_correctly_under_urxvt_"><code>bash</code>'s readline does not work correctly under urxvt.</a></h3>
364	</dt>	919	<p>See next entry.</p>
		920	<p>
		921	</p>
365	<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />	922	<h3><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h3>
366	</dt>
367	<dd>
368	One reason you might want this is that some distributions or operating	923	<p>One reason you might want this is that some distributions or operating
369	systems still compile some programs using the long-obsoleted termcap	924	systems still compile some programs using the long-obsoleted termcap
370	library (Fedora Core's bash is one example) and rely on a termcap entry	925	library (Fedora Core's bash is one example) and rely on a termcap entry
371	for <code>rxvt-unicode</code>.	926	for <code>rxvt-unicode</code>.</p>
372	</dd>
373	<dd>
374	<p>You could use rxvt's termcap entry with resonable results in many cases.	927	<p>You could use rxvt's termcap entry with resonable results in many cases.
375	You can also create a termcap entry by using terminfo's infocmp program	928	You can also create a termcap entry by using terminfo's infocmp program
376	like this:</p>	929	like this:</p>
377	</dd>
378	<dd>
379	<pre>	930	<pre>
380	infocmp -C rxvt-unicode</pre>	931	infocmp -C rxvt-unicode</pre>
381	</dd>
382	<dd>
383	<p>Or you could use this termcap entry, generated by the command above:</p>	932	<p>Or you could use this termcap entry, generated by the command above:</p>
384	</dd>
385	<dd>
386	<pre>	933	<pre>
387	rxvt-unicode|rxvt-unicode terminal (X Window System):\	934	rxvt-unicode|rxvt-unicode terminal (X Window System):\
388	:am:bw:eo:km:mi:ms:xn:xo:\	935	:am:bw:eo:km:mi:ms:xn:xo:\
389	:co#80:it#8:li#24:lm#0:\	936	:co#80:it#8:li#24:lm#0:\
390	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	937	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
…		…
402	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\	949	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
403	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	950	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
404	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	951	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
405	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	952	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
406	:vs=\E[?25h:</pre>	953	:vs=\E[?25h:</pre>
407	</dd>	954	<p>
408	<p></p>	955	</p>
409	<dt><strong><a name="item_why_does_ls_no_longer_have_coloured_output_3f">Why does <code>ls</code> no longer have coloured output?</a></strong><br />	956	<h3><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h3>
410	</dt>
411	<dd>
412	The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to	957	<p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to
413	decide wether a terminal has colour, but uses it's own configuration	958	decide wether a terminal has colour, but uses it's own configuration
414	file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among	959	file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among
415	with most other terminals supporting colour). Either add:	960	with most other terminals supporting colour). Either add:</p>
416	</dd>
417	<dd>
418	<pre>	961	<pre>
419	TERM rxvt-unicode</pre>	962	TERM rxvt-unicode</pre>
420	</dd>
421	<dd>
422	<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>	963	<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>
423	</dd>
424	<dd>
425	<pre>	964	<pre>
426	alias ls='ls --color=auto'</pre>	965	alias ls='ls --color=auto'</pre>
427	</dd>
428	<dd>
429	<p>to your <code>.profile</code> or <code>.bashrc</code>.</p>	966	<p>to your <code>.profile</code> or <code>.bashrc</code>.</p>
430	</dd>	967	<p>
431	<p></p>	968	</p>
432	<dt><strong><a name="item_why_doesn_27t_vim_2femacs_etc_2e_use_the_88_colour">Why doesn't vim/emacs etc. use the 88 colour mode?</a></strong><br />	969	<h3><a name="why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></h3>
433	</dt>	970	<p>See next entry.</p>
		971	<p>
		972	</p>
434	<dt><strong><a name="item_why_doesn_27t_vim_2femacs_etc_2e_make_use_of_itali">Why doesn't vim/emacs etc. make use of italic?</a></strong><br />	973	<h3><a name="why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></h3>
435	</dt>	974	<p>See next entry.</p>
		975	<p>
		976	</p>
436	<dt><strong><a name="item_why_are_the_secondary_screen_2drelated_options_not">Why are the secondary screen-related options not working properly?</a></strong><br />	977	<h3><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h3>
437	</dt>
438	<dd>
439	Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged	978	<p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged
440	distributions (most notably Debian GNU/Linux) break rxvt-unicode	979	distributions (most notably Debian GNU/Linux) break rxvt-unicode
441	by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra	980	by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra
442	features. Unfortunately, some of these (most notably, again, Debian	981	features. Unfortunately, some of these (most notably, again, Debian
443	GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo	982	GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo
444	file, so you will need to install it on your own (See the question <strong>When	983	file, so you will need to install it on your own (See the question <strong>When
445	I log-in to another system it tells me about missing terminfo data?</strong> on	984	I log-in to another system it tells me about missing terminfo data?</strong> on
446	how to do this).	985	how to do this).</p>
447	</dd>	986	<p>
448	<p></p>	987	</p>
449	<dt><strong><a name="item_my_numerical_keypad_acts_weird_and_generates_diffe">My numerical keypad acts weird and generates differing output?</a></strong><br />	988	<h2><a name="encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></h2>
450	</dt>	989	<p>
451	<dd>	990	</p>
452	Some Debian GNUL/Linux users seem to have this problem, although no
453	specific details were reported so far. It is possible that this is caused
454	by the wrong <code>TERM</code> setting, although the details of wether and how
455	this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
456	keymap. See the answer to the previous question, and please report if that
457	helped.
458	</dd>
459	<p></p>
460	<dt><strong><a name="item_rxvt_2dunicode_does_not_seem_to_understand_the_sel">Rxvt-unicode does not seem to understand the selected encoding?</a></strong><br />	991	<h3><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h3>
461	</dt>	992	<p>See next entry.</p>
		993	<p>
		994	</p>
462	<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br />	995	<h3><a name="unicode_does_not_seem_to_work">Unicode does not seem to work?</a></h3>
463	</dt>
464	<dd>
465	If you encounter strange problems like typing an accented character but	996	<p>If you encounter strange problems like typing an accented character but
466	getting two unrelated other characters or similar, or if program output is	997	getting two unrelated other characters or similar, or if program output is
467	subtly garbled, then you should check your locale settings.	998	subtly garbled, then you should check your locale settings.</p>
468	</dd>
469	<dd>
470	<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the	999	<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the
471	programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the	1000	programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the
472	login script running within the rxvt-unicode window changes the locale to	1001	login script running within the rxvt-unicode window changes the locale to
473	something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>	1002	something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>
474	</dd>
475	<dd>
476	<p>The best thing is to fix your startup environment, as you will likely run	1003	<p>The best thing is to fix your startup environment, as you will likely run
477	into other problems. If nothing works you can try this in your .profile.</p>	1004	into other problems. If nothing works you can try this in your .profile.</p>
478	</dd>
479	<dd>
480	<pre>	1005	<pre>
481	printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre>	1006	printf '\33]701;%s\007' &quot;$LC_CTYPE&quot;</pre>
482	</dd>
483	<dd>
484	<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not	1007	<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not
485	supported on your systems. Some systems have a <code>locale</code> command which	1008	supported on your systems. Some systems have a <code>locale</code> command which
486	displays this (also, <code>perl -e0</code> can be used to check locale settings, as	1009	displays this (also, <code>perl -e0</code> can be used to check locale settings, as
487	it will complain loudly if it cannot set the locale). If it displays something	1010	it will complain loudly if it cannot set the locale). If it displays something
488	like:</p>	1011	like:</p>
489	</dd>
490	<dd>
491	<pre>	1012	<pre>
492	locale: Cannot set LC_CTYPE to default locale: ...</pre>	1013	locale: Cannot set LC_CTYPE to default locale: ...</pre>
493	</dd>
494	<dd>
495	<p>Then the locale you specified is not supported on your system.</p>	1014	<p>Then the locale you specified is not supported on your system.</p>
496	</dd>
497	<dd>
498	<p>If nothing works and you are sure that everything is set correctly then	1015	<p>If nothing works and you are sure that everything is set correctly then
499	you will need to remember a little known fact: Some programs just don't	1016	you will need to remember a little known fact: Some programs just don't
500	support locales :(</p>	1017	support locales :(</p>
		1018	<p>
		1019	</p>
		1020	<h3><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h3>
		1021	<p>See next entry.</p>
		1022	<p>
		1023	</p>
		1024	<h3><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h3>
		1025	<p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		1026	specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about
		1027	UTF-8 or any other encodings with respect to terminal I/O.</p>
		1028	<p>The reasons is that there exists a perfectly fine mechanism for selecting
		1029	the encoding, doing I/O and (most important) communicating this to all
		1030	applications so everybody agrees on character properties such as width
		1031	and code number. This mechanism is the <em>locale</em>. Applications not using
		1032	that info will have problems (for example, <code>xterm</code> gets the width of
		1033	characters wrong as it uses it's own, locale-independent table under all
		1034	locales).</p>
		1035	<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
		1036	programs doing the same (that is, most) will automatically agree in the
		1037	interpretation of characters.</p>
		1038	<p>Unfortunately, there is no system-independent way to select locales, nor
		1039	is there a standard on how locale specifiers will look like.</p>
		1040	<p>On most systems, the content of the <code>LC_CTYPE</code> environment variable
		1041	contains an arbitrary string which corresponds to an already-installed
		1042	locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>,
		1043	<code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms
		1044	(i.e. <code>de</code> or <code>german</code>) are also common.</p>
		1045	<p>Rxvt-unicode ignores all other locale categories, and except for
		1046	the encoding, ignores country or language-specific settings,
		1047	i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
		1048	rxvt-unicode.</p>
		1049	<p>If you want to use a specific encoding you have to make sure you start
		1050	rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
		1051	<p>
		1052	</p>
		1053	<h3><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h3>
		1054	<p>Yes, using an escape sequence. Try something like this, which sets
		1055	rxvt-unicode's idea of <code>LC_CTYPE</code>.</p>
		1056	<pre>
		1057	printf '\33]701;%s\007' ja_JP.SJIS</pre>
		1058	<p>See also the previous answer.</p>
		1059	<p>Sometimes this capability is rather handy when you want to work in
		1060	one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
		1061	(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
		1062	first switches to a locale supported by xjdic and back later:</p>
		1063	<pre>
		1064	printf '\33]701;%s\007' ja_JP.SJIS
		1065	xjdic -js
		1066	printf '\33]701;%s\007' de_DE.UTF-8</pre>
		1067	<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
		1068	for some locales where character width differs between program- and
		1069	rxvt-unicode-locales.</p>
		1070	<p>
		1071	</p>
		1072	<h3><a name="i_have_problems_getting_my_input_method_working_">I have problems getting my input method working.</a></h3>
		1073	<p>Try a search engine, as this is slightly different for every input method server.</p>
		1074	<p>Here is a checklist:</p>
		1075	<dl>
		1076	<dt><strong><a name="item__2d_make_sure_your_locale_and_the_imlocale_are_sup">- Make sure your locale <em>and</em> the imLocale are supported on your OS.</a></strong><br />
		1077	</dt>
501	</dd>	1078	<dd>
502	<p></p>	1079	Try <code>locale -a</code> or check the documentation for your OS.
503	<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 />
504	</dt>
505	<dt><strong><a name="item_how_does_rxvt_2dunicode_choose_fonts_3f">How does rxvt-unicode choose fonts?</a></strong><br />
506	</dt>
507	<dd>	1080	</dd>
508	Most fonts do not contain the full range of Unicode, which is	1081	<p></p>
509	fine. Chances are that the font you (or the admin/package maintainer of	1082	<dt><strong><a name="item__2d_make_sure_your_locale_or_imlocale_matches_a_lo">- Make sure your locale or imLocale matches a locale supported by your XIM.</a></strong><br />
510	your system/os) have specified does not cover all the characters you want	1083	</dt>
511	to display.
512	</dd>	1084	<dd>
		1085	For example, <strong>kinput2</strong> does not support UTF-8 locales, you should use
		1086	<code>ja_JP.EUC-JP</code> or equivalent.
513	<dd>	1087	</dd>
514	<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement	1088	<p></p>
515	font. Often the result is fine, but sometimes the chosen font looks	1089	<dt><strong><a name="item__2d_make_sure_your_xim_server_is_actually_running_">- Make sure your XIM server is actually running.</a></strong><br />
516	bad/ugly/wrong. Some fonts have totally strange characters that don't	1090	</dt>
517	resemble the correct glyph at all, and rxvt-unicode lacks the artificial	1091	<dt><strong><a name="item__2d_make_sure_the_xmodifiers_environment_variable_">- Make sure the <code>XMODIFIERS</code> environment variable is set correctly when <em>starting</em> rxvt-unicode.</a></strong><br />
518	intelligence to detect that a specific glyph is wrong: it has to believe	1092	</dt>
519	the font that the characters it claims to contain indeed look correct.</p>
520	</dd>	1093	<dd>
		1094	When you want to use e.g. <strong>kinput2</strong>, it must be set to
		1095	<code>@im=kinput2</code>. For <strong>scim</strong>, use <code>@im=SCIM</code>. Youc an see what input
		1096	method servers are running with this command:
521	<dd>	1097	</dd>
522	<p>In that case, select a font of your taste and add it to the font list,
523	e.g.:</p>
524	</dd>	1098	<dd>
		1099	<pre>
		1100	xprop -root XIM_SERVERS</pre>
525	<dd>	1101	</dd>
526	<pre>	1102	<p></p>
527	rxvt -fn basefont,font2,font3...</pre>	1103	<dt></dt>
528	</dd>	1104	</dl>
529	<dd>	1105	<p>
530	<p>When rxvt-unicode sees a character, it will first look at the base	1106	</p>
531	font. If the base font does not contain the character, it will go to the	1107	<h3><a name="my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></h3>
532	next font, and so on. Specifying your own fonts will also speed up this	1108	<p>You can specify separate locales for the input method and the rest of the
533	search and use less resources within rxvt-unicode and the X-server.</p>	1109	terminal, using the resource <code>imlocale</code>:</p>
534	</dd>	1110	<pre>
535	<dd>	1111	URxvt.imlocale: ja_JP.EUC-JP</pre>
536	<p>The only limitation is that none of the fonts may be larger than the base	1112	<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
537	font, as the base font defines the terminal character cell size, which	1113	use your input method. Please note, however, that, depending on your Xlib
538	must be the same due to the way terminals work.</p>	1114	version, you may not be able to input characters outside <code>EUC-JP</code> in a
539	</dd>	1115	normal way then, as your input method limits you.</p>
540	<p></p>	1116	<p>
541	<dt><strong><a name="item_why_do_some_chinese_characters_look_so_different_t">Why do some chinese characters look so different than others?</a></strong><br />	1117	</p>
542	</dt>	1118	<h3><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h3>
543	<dd>	1119	<p>Unfortunately, this is unavoidable, as the XIM protocol is racy by
544	This is because there is a difference between script and language --	1120	design. Applications can avoid some crashes at the expense of memory
545	rxvt-unicode does not know which language the text that is output is,	1121	leaks, and Input Methods can avoid some crashes by careful ordering at
546	as it only knows the unicode character codes. If rxvt-unicode first	1122	exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
547	sees a japanese/chinese character, it might choose a japanese font for	1123	while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
548	display. Subsequent japanese characters will use that font. Now, many	1124	crashes cannot be completely avoided even if both sides cooperate.</p>
549	chinese characters aren't represented in japanese fonts, so when the first	1125	<p>So the only workaround is not to kill your Input Method Servers.</p>
550	non-japanese character comes up, rxvt-unicode will look for a chinese font	1126	<p>
551	-- unfortunately at this point, it will still use the japanese font for	1127	</p>
552	chinese characters that are also in the japanese font.	1128	<h2><a name="operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></h2>
553	</dd>	1129	<p>
554	<dd>	1130	</p>
555	<p>The workaround is easy: just tag a chinese font at the end of your font	1131	<h3><a name="i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></h3>
556	list (see the previous question). The key is to view the font list as	1132	<p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large
557	a preference list: If you expect more japanese, list a japanese font	1133	patches that considerably change the behaviour of rxvt-unicode (but
558	first. If you expect more chinese, put a chinese font first.</p>	1134	unfortunately this notice has been removed). Before reporting a bug to
559	</dd>	1135	the original rxvt-unicode author please download and install the genuine
560	<dd>	1136	version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce
561	<p>In the future it might be possible to switch language preferences at	1137	the problem. If you cannot, chances are that the problems are specific to
562	runtime (the internal data structure has no problem with using different	1138	Debian GNU/Linux, in which case it should be reported via the Debian Bug
563	fonts for the same character at the same time, but no interface for this	1139	Tracking System (use <code>reportbug</code> to report the bug).</p>
564	has been designed yet).</p>	1140	<p>For other problems that also affect the Debian package, you can and
565	</dd>	1141	probably should use the Debian BTS, too, because, after all, it's also a
566	<dd>	1142	bug in the Debian version and it serves as a reminder for other users that
567	<p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p>	1143	might encounter the same issue.</p>
568	</dd>	1144	<p>
569	<p></p>	1145	</p>
570	<dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br />	1146	<h3><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h3>
571	</dt>	1147	<p>You should build one binary with the default options. <em>configure</em>
572	<dd>	1148	now enables most useful options, and the trend goes to making them
573	Most fonts were not designed for terminal use, which means that character	1149	runtime-switchable, too, so there is usually no drawback to enbaling them,
574	size varies a lot. A font that is otherwise fine for terminal use might	1150	except higher disk and possibly memory usage. The perl interpreter should
575	contain some characters that are simply too wide. Rxvt-unicode will avoid	1151	be enabled, as important functionality (menus, selection, likely more in
576	these characters. For characters that are just ``a bit'' too wide a special	1152	the future) depends on it.</p>
577	``careful'' rendering mode is used that redraws adjacent characters.	1153	<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
578	</dd>	1154	system-wide (except maybe with <code>defaults</code>). This will result in useful
579	<dd>	1155	behaviour. If your distribution aims at low memory, add an empty
580	<p>All of this requires that fonts do not lie about character sizes,	1156	<code>perl-ext-common</code> resource to the app-defaults file. This will keep the
581	however: Xft fonts often draw glyphs larger than their acclaimed bounding	1157	perl interpreter disabled until the user enables it.</p>
582	box, and rxvt-unicode has no way of detecting this (the correct way is to	1158	<p>If you can/want build more binaries, I recommend building a minimal
583	ask for the character bounding box, which unfortunately is wrong in these	1159	one with <code>--disable-everything</code> (very useful) and a maximal one with
584	cases).</p>	1160	<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of
585	</dd>	1161	encodings built-in that increase download times and are rarely used).</p>
586	<dd>	1162	<p>
587	<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,	1163	</p>
588	or the respective font. If you encounter this problem you might try using	1164	<h3><a name="i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></h3>
589	the <code>-lsp</code> option to give the font more height. If that doesn't work, you	1165	<p>It should be, starting with release 7.1. You are encouraged to properly
590	might be forced to use a different font.</p>	1166	install urxvt with privileges necessary for your OS now.</p>
591	</dd>	1167	<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork
592	<dd>	1168	into a helper process for privileged operations (pty handling on some
593	<p>All of this is not a problem when using X11 core fonts, as their bounding	1169	systems, utmp/wtmp/lastlog handling on others) and drop privileges
594	box data is correct.</p>	1170	immediately. This is much safer than most other terminals that keep
595	</dd>	1171	privileges while running (but is more relevant to urxvt, as it contains
596	<p></p>	1172	things as perl interpreters, which might be ``helpful'' to attackers).</p>
		1173	<p>This forking is done as the very first within main(), which is very early
		1174	and reduces possible bugs to initialisation code run before main(), or
		1175	things like the dynamic loader of your system, which should result in very
		1176	little risk.</p>
		1177	<p>
		1178	</p>
597	<dt><strong><a name="item_on_solaris_9_2c_many_line_2ddrawing_characters_are">On Solaris 9, many line-drawing characters are too wide.</a></strong><br />	1179	<h3><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h3>
598	</dt>
599	<dd>
600	Seems to be a known bug, read	1180	<p>Seems to be a known bug, read
601	<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the	1181	<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the
602	following ugly workaround to get non-double-wide-characters working:	1182	following ugly workaround to get non-double-wide-characters working:</p>
603	</dd>
604	<dd>
605	<pre>	1183	<pre>
606	#define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>	1184	#define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>
607	</dd>
608	<p></p>
609	<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br />
610	</dt>
611	<dd>
612	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.
618	</dd>
619	<dd>
620	<p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than
621	one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p>
622	</dd>
623	<p></p>
624	<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 />
625	</dt>
626	<dd>
627	Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on
628	international keyboards) or simply use ISO 14755 support to your
629	advantage, typing &lt;Ctrl-Shift-0&gt; to get a ASCII NUL. This works for other
630	codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape
631	character and so on.
632	</dd>
633	<p></p>
634	<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 />
635	</dt>
636	<dd>
637	First of all, make sure you are running with the right terminal settings
638	(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
639	make sure you have specified colours for italic and bold, as otherwise
640	rxvt-unicode might use reverse video to simulate the effect:
641	</dd>
642	<dd>
643	<pre>	1185	<p>
644	URxvt.colorBD: white	1186	</p>
645	URxvt.colorIT: green</pre>
646	</dd>
647	<p></p>
648	<dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br />
649	</dt>
650	<dd>
651	For some unexplainable reason, some rare programs assume a very weird
652	colour palette when confronted with a terminal with more than the standard
653	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
654	these programs not to assume non-ISO colours without very good reasons.
655	</dd>
656	<dd>
657	<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
658	definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
659	fix colours but keep you from using other rxvt-unicode features.</p>
660	</dd>
661	<p></p>
662	<dt><strong><a name="item_i_am_on_freebsd_and_rxvt_2dunicode_does_not_seem_t">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></strong><br />	1187	<h3><a name="i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></h3>
663	</dt>
664	<dd>
665	Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined	1188	<p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined
666	in your compile environment, or an implementation that implements it,	1189	in your compile environment, or an implementation that implements it,
667	wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that	1190	wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that
668	<strong>wchar_t</strong> is represented as unicode.	1191	<strong>wchar_t</strong> is represented as unicode.</p>
669	</dd>
670	<dd>
671	<p>As you might have guessed, FreeBSD does neither define this symobl nor	1192	<p>As you might have guessed, FreeBSD does neither define this symobl nor
672	does it support it. Instead, it uses it's own internal representation of	1193	does it support it. Instead, it uses it's own internal representation of
673	<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>	1194	<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
674	</dd>
675	<dd>
676	<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and	1195	<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
677	<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>	1196	<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
678	</dd>
679	<dd>
680	<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language	1197	<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
681	apps in an OS, as using a locale-dependent (and non-standardized)	1198	apps in an OS, as using a locale-dependent (and non-standardized)
682	representation of <strong>wchar_t</strong> makes it impossible to convert between	1199	representation of <strong>wchar_t</strong> makes it impossible to convert between
683	<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding	1200	<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding
684	without implementing OS-specific-wrappers for each and every locale. There	1201	without implementing OS-specific-wrappers for each and every locale. There
685	simply are no APIs to convert <strong>wchar_t</strong> into anything except the current	1202	simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
686	locale encoding.</p>	1203	locale encoding.</p>
687	</dd>
688	<dd>
689	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this	1204	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
690	by carrying their own replacement functions for character set handling	1205	by carrying their own replacement functions for character set handling
691	with them, and either implementing OS-dependent hacks or doing multiple	1206	with them, and either implementing OS-dependent hacks or doing multiple
692	conversions (which is slow and unreliable in case the OS implements	1207	conversions (which is slow and unreliable in case the OS implements
693	encodings slightly different than the terminal emulator).</p>	1208	encodings slightly different than the terminal emulator).</p>
694	</dd>
695	<dd>
696	<p>The rxvt-unicode author insists that the right way to fix this is in the	1209	<p>The rxvt-unicode author insists that the right way to fix this is in the
697	system libraries once and for all, instead of forcing every app to carry	1210	system libraries once and for all, instead of forcing every app to carry
698	complete replacements for them :)</p>	1211	complete replacements for them :)</p>
699	</dd>	1212	<p>
700	<p></p>	1213	</p>
701	<dt><strong><a name="item_i_use_solaris_9_and_it_doesn_27t_compile_2fwork_2f">I use Solaris 9 and it doesn't compile/work/etc.</a></strong><br />	1214	<h3><a name="i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></h3>
702	</dt>
703	<dd>
704	Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst	1215	<p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
705	problems with <code>wcwidth</code> and a compile problem.	1216	problems with <code>wcwidth</code> and a compile problem.</p>
706	</dd>	1217	<p>
707	<p></p>	1218	</p>
708	<dt><strong><a name="item_how_can_i_use_rxvt_2dunicode_under_cygwin_3f">How can I use rxvt-unicode under cygwin?</a></strong><br />	1219	<h3><a name="how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></h3>
709	</dt>
710	<dd>
711	rxvt-unicode should compile and run out of the box on cygwin, using	1220	<p>rxvt-unicode should compile and run out of the box on cygwin, using
712	the X11 libraries that come with cygwin. libW11 emulation is no	1221	the X11 libraries that come with cygwin. libW11 emulation is no
713	longer supported (and makes no sense, either, as it only supported a	1222	longer supported (and makes no sense, either, as it only supported a
714	single font). I recommend starting the X-server in <code>-multiwindow</code> or	1223	single font). I recommend starting the X-server in <code>-multiwindow</code> or
715	<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the	1224	<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
716	old libW11 emulation.	1225	old libW11 emulation.</p>
717	</dd>
718	<dd>
719	<p>At the time of this writing, cygwin didn't seem to support any multi-byte	1226	<p>At the time of this writing, cygwin didn't seem to support any multi-byte
720	encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited	1227	encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
721	to 8-bit encodings.</p>	1228	to 8-bit encodings.</p>
722	</dd>
723	<p></p>
724	<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 />
725	</dt>
726	<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />
727	</dt>
728	<dd>
729	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
730	specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about
731	UTF-8 or any other encodings with respect to terminal I/O.
732	</dd>
733	<dd>
734	<p>The reasons is that there exists a perfectly fine mechanism for selecting
735	the encoding, doing I/O and (most important) communicating this to all
736	applications so everybody agrees on character properties such as width
737	and code number. This mechanism is the <em>locale</em>. Applications not using
738	that info will have problems (for example, <code>xterm</code> gets the width of
739	characters wrong as it uses it's own, locale-independent table under all
740	locales).</p>
741	</dd>
742	<dd>
743	<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
744	programs doing the same (that is, most) will automatically agree in the
745	interpretation of characters.</p>
746	</dd>
747	<dd>
748	<p>Unfortunately, there is no system-independent way to select locales, nor
749	is there a standard on how locale specifiers will look like.</p>
750	</dd>
751	<dd>
752	<p>On most systems, the content of the <code>LC_CTYPE</code> environment variable
753	contains an arbitrary string which corresponds to an already-installed
754	locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>,
755	<code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms
756	(i.e. <code>de</code> or <code>german</code>) are also common.</p>
757	</dd>
758	<dd>
759	<p>Rxvt-unicode ignores all other locale categories, and except for
760	the encoding, ignores country or language-specific settings,
761	i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
762	rxvt-unicode.</p>
763	</dd>
764	<dd>
765	<p>If you want to use a specific encoding you have to make sure you start
766	rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
767	</dd>
768	<p></p>
769	<dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br />
770	</dt>
771	<dd>
772	Yes, using an escape sequence. Try something like this, which sets
773	rxvt-unicode's idea of <code>LC_CTYPE</code>.
774	</dd>
775	<dd>
776	<pre>
777	printf '\e]701;%s\007' ja_JP.SJIS</pre>
778	</dd>
779	<dd>
780	<p>See also the previous answer.</p>
781	</dd>
782	<dd>
783	<p>Sometimes this capability is rather handy when you want to work in
784	one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
785	(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
786	first switches to a locale supported by xjdic and back later:</p>
787	</dd>
788	<dd>
789	<pre>
790	printf '\e]701;%s\007' ja_JP.SJIS
791	xjdic -js
792	printf '\e]701;%s\007' de_DE.UTF-8</pre>
793	</dd>
794	<dd>
795	<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
796	for some locales where character width differs between program- and
797	rxvt-unicode-locales.</p>
798	</dd>
799	<p></p>
800	<dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br />
801	</dt>
802	<dd>
803	Yes, using an escape sequence. Try something like this, which has the same
804	effect as using the <code>-fn</code> switch, and takes effect immediately:
805	</dd>
806	<dd>
807	<pre>
808	printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
809	</dd>
810	<dd>
811	<p>This is useful if you e.g. work primarily with japanese (and prefer a
812	japanese font), but you have to switch to chinese temporarily, where
813	japanese fonts would only be in your way.</p>
814	</dd>
815	<dd>
816	<p>You can think of this as a kind of manual ISO-2022 switching.</p>
817	</dd>
818	<p></p>
819	<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 />
820	</dt>
821	<dd>
822	Many fonts have difficulties with italic characters and hinting. For
823	example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
824	Mono</code> completely fails in it's italic face. A workaround might be to
825	enable freetype autohinting, i.e. like this:
826	</dd>
827	<dd>
828	<pre>
829	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
830	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
831	</dd>
832	<p></p>
833	<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 />
834	</dt>
835	<dd>
836	You can specify separate locales for the input method and the rest of the
837	terminal, using the resource <code>imlocale</code>:
838	</dd>
839	<dd>
840	<pre>
841	URxvt.imlocale: ja_JP.EUC-JP</pre>
842	</dd>
843	<dd>
844	<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
845	use your input method. Please note, however, that you will not be able to
846	input characters outside <code>EUC-JP</code> in a normal way then, as your input
847	method limits you.</p>
848	</dd>
849	<p></p>
850	<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 />
851	</dt>
852	<dd>
853	Unfortunately, this is unavoidable, as the XIM protocol is racy by
854	design. Applications can avoid some crashes at the expense of memory
855	leaks, and Input Methods can avoid some crashes by careful ordering at
856	exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
857	while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
858	crashes cannot be completely avoided even if both sides cooperate.
859	</dd>
860	<dd>
861	<p>So the only workaround is not to kill your Input Method Servers.</p>
862	</dd>
863	<p></p>
864	<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 />
865	</dt>
866	<dd>
867	Rxvt-unicode tries to obey the rule of not charging you for something you
868	don't use. One thing you should try is to configure out all settings that
869	you don't need, for example, Xft support is a resource hog by design,
870	when used. Compiling it out ensures that no Xft font will be loaded
871	accidentally when rxvt-unicode tries to find a font for your characters.
872	</dd>
873	<dd>
874	<p>Also, many people (me included) like large windows and even larger
875	scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use
876	6 bytes per screen cell. For a 160x?? window this amounts to almost a
877	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
878	use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as
879	rxvt-unicode then uses 8 bytes per screen cell.</p>
880	</dd>
881	<p></p>
882	<dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br />
883	</dt>
884	<dd>
885	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
886	it is simply slow. If you still want Xft fonts you might try to disable
887	antialiasing (by appending <code>:antialias=false</code>), which saves lots of
888	memory and also speeds up rendering considerably.
889	</dd>
890	<p></p>
891	<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 />
892	</dt>
893	<dd>
894	Rxvt-unicode will use whatever you specify as a font. If it needs to
895	fall back to it's default font search list it will prefer X11 core
896	fonts, because they are small and fast, and then use Xft fonts. It has
897	antialiasing disabled for most of them, because the author thinks they
898	look best that way.
899	</dd>
900	<dd>
901	<p>If you want antialiasing, you have to specify the fonts manually.</p>
902	</dd>
903	<p></p>
904	<dt><strong><a name="item_mouse_cut_2fpaste_suddenly_no_longer_works_2e">Mouse cut/paste suddenly no longer works.</a></strong><br />
905	</dt>
906	<dd>
907	Make sure that mouse reporting is actually turned off since killing
908	some editors prematurely may leave the mouse in mouse report mode. I've
909	heard that tcsh may use mouse reporting unless it otherwise specified. A
910	quick check is to see if cut/paste works when the Alt or Shift keys are
911	depressed.
912	</dd>
913	<p></p>
914	<dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br />
915	</dt>
916	<dd>
917	If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
918	standard foreground colour.
919	</dd>
920	<dd>
921	<p>For the standard background colour, blinking will actually make the
922	text blink when compiled with <code>--enable-blinking</code>. with standard
923	colours. Without <code>--enable-blinking</code>, the blink attribute will be
924	ignored.</p>
925	</dd>
926	<dd>
927	<p>On ANSI colours, bold/blink attributes are used to set high-intensity
928	foreground/background colors.</p>
929	</dd>
930	<dd>
931	<p>color0-7 are the low-intensity colors.</p>
932	</dd>
933	<dd>
934	<p>color8-15 are the corresponding high-intensity colors.</p>
935	</dd>
936	<p></p>
937	<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 />
938	</dt>
939	<dd>
940	You can change the screen colors at run-time using <em>~/.Xdefaults</em>
941	resources (or as long-options).
942	</dd>
943	<dd>
944	<p>Here are values that are supposed to resemble a VGA screen,
945	including the murky brown that passes for low-intensity yellow:</p>
946	</dd>
947	<dd>
948	<pre>
949	URxvt.color0: #000000
950	URxvt.color1: #A80000
951	URxvt.color2: #00A800
952	URxvt.color3: #A8A800
953	URxvt.color4: #0000A8
954	URxvt.color5: #A800A8
955	URxvt.color6: #00A8A8
956	URxvt.color7: #A8A8A8</pre>
957	</dd>
958	<dd>
959	<pre>
960	URxvt.color8: #000054
961	URxvt.color9: #FF0054
962	URxvt.color10: #00FF54
963	URxvt.color11: #FFFF54
964	URxvt.color12: #0000FF
965	URxvt.color13: #FF00FF
966	URxvt.color14: #00FFFF
967	URxvt.color15: #FFFFFF</pre>
968	</dd>
969	<dd>
970	<p>And here is a more complete set of non-standard colors described (not by
971	me) as ``pretty girly''.</p>
972	</dd>
973	<dd>
974	<pre>
975	URxvt.cursorColor: #dc74d1
976	URxvt.pointerColor: #dc74d1
977	URxvt.background: #0e0e0e
978	URxvt.foreground: #4ad5e1
979	URxvt.color0: #000000
980	URxvt.color8: #8b8f93
981	URxvt.color1: #dc74d1
982	URxvt.color9: #dc74d1
983	URxvt.color2: #0eb8c7
984	URxvt.color10: #0eb8c7
985	URxvt.color3: #dfe37e
986	URxvt.color11: #dfe37e
987	URxvt.color5: #9e88f0
988	URxvt.color13: #9e88f0
989	URxvt.color6: #73f7ff
990	URxvt.color14: #73f7ff
991	URxvt.color7: #e1dddd
992	URxvt.color15: #e1dddd</pre>
993	</dd>
994	<p></p>
995	<dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br />
996	</dt>
997	<dd>
998	Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
999	display, create the listening socket and then fork.
1000	</dd>
1001	<p></p>
1002	<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 />
1003	</dt>
1004	<dd>
1005	Assuming that the physical Backspace key corresponds to the
1006	BackSpace keysym (not likely for Linux ... see the following
1007	question) there are two standard values that can be used for
1008	Backspace: <code>^H</code> and <code>^?</code>.
1009	</dd>
1010	<dd>
1011	<p>Historically, either value is correct, but rxvt-unicode adopts the debian
1012	policy of using <code>^?</code> when unsure, because it's the one only only correct
1013	choice :).</p>
1014	</dd>
1015	<dd>
1016	<p>Rxvt-unicode tries to inherit the current stty settings and uses the value
1017	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
1018	started from a terminal (say, from a menu or by remote shell), then the
1019	system value of `erase', which corresponds to CERASE in &lt;termios.h&gt;, will
1020	be used (which may not be the same as your stty setting).</p>
1021	</dd>
1022	<dd>
1023	<p>For starting a new rxvt-unicode:</p>
1024	</dd>
1025	<dd>
1026	<pre>
1027	# use Backspace = ^H
1028	$ stty erase ^H
1029	$ rxvt</pre>
1030	</dd>
1031	<dd>
1032	<pre>
1033	# use Backspace = ^?
1034	$ stty erase ^?
1035	$ rxvt</pre>
1036	</dd>
1037	<dd>
1038	<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p>
1039	</dd>
1040	<dd>
1041	<p>For an existing rxvt-unicode:</p>
1042	</dd>
1043	<dd>
1044	<pre>
1045	# use Backspace = ^H
1046	$ stty erase ^H
1047	$ echo -n &quot;^[[36h&quot;</pre>
1048	</dd>
1049	<dd>
1050	<pre>
1051	# use Backspace = ^?
1052	$ stty erase ^?
1053	$ echo -n &quot;^[[36l&quot;</pre>
1054	</dd>
1055	<dd>
1056	<p>This helps satisfy some of the Backspace discrepancies that occur, but
1057	if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value
1058	properly reflects that.</p>
1059	</dd>
1060	<dd>
1061	<p>The Delete key is a another casualty of the ill-defined Backspace problem.
1062	To avoid confusion between the Backspace and Delete keys, the Delete
1063	key has been assigned an escape sequence to match the vt100 for Execute
1064	(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
1065	</dd>
1066	<dd>
1067	<p>Some other Backspace problems:</p>
1068	</dd>
1069	<dd>
1070	<p>some editors use termcap/terminfo,
1071	some editors (vim I'm told) expect Backspace = ^H,
1072	GNU Emacs (and Emacs-like editors) use ^H for help.</p>
1073	</dd>
1074	<dd>
1075	<p>Perhaps someday this will all be resolved in a consistent manner.</p>
1076	</dd>
1077	<p></p>
1078	<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 />
1079	</dt>
1080	<dd>
1081	There are some compile-time selections available via configure. Unless
1082	you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
1083	use the `keysym' resource to alter the keystrings associated with keysyms.
1084	</dd>
1085	<dd>
1086	<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p>
1087	</dd>
1088	<dd>
1089	<pre>
1090	URxvt.keysym.Home: \033[1~
1091	URxvt.keysym.End: \033[4~
1092	URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
1093	URxvt.keysym.C-slash: \033&lt;C-/&gt;
1094	URxvt.keysym.C-semicolon: \033&lt;C-;&gt;
1095	URxvt.keysym.C-grave: \033&lt;C-`&gt;
1096	URxvt.keysym.C-comma: \033&lt;C-,&gt;
1097	URxvt.keysym.C-period: \033&lt;C-.&gt;
1098	URxvt.keysym.C-0x60: \033&lt;C-`&gt;
1099	URxvt.keysym.C-Tab: \033&lt;C-Tab&gt;
1100	URxvt.keysym.C-Return: \033&lt;C-Return&gt;
1101	URxvt.keysym.S-Return: \033&lt;S-Return&gt;
1102	URxvt.keysym.S-space: \033&lt;S-Space&gt;
1103	URxvt.keysym.M-Up: \033&lt;M-Up&gt;
1104	URxvt.keysym.M-Down: \033&lt;M-Down&gt;
1105	URxvt.keysym.M-Left: \033&lt;M-Left&gt;
1106	URxvt.keysym.M-Right: \033&lt;M-Right&gt;
1107	URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
1108	URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
1109	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
1110	</dd>
1111	<dd>
1112	<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
1113	</dd>
1114	<p></p>
1115	<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.
1116	How do I make use of them? For example, the Sun Keyboard type 4
1117	has the following mappings that rxvt-unicode doesn't recognize.</a></strong><br />
1118	</dt>
1119	<dd>
1120	<pre>
1121	KP_Insert == Insert
1122	F22 == Print
1123	F27 == Home
1124	F29 == Prior
1125	F33 == End
1126	F35 == Next</pre>
1127	</dd>
1128	<dd>
1129	<p>Rather than have rxvt-unicode try to accommodate all the various possible
1130	keyboard mappings, it is better to use `xmodmap' to remap the keys as
1131	required for your particular machine.</p>
1132	</dd>
1133	<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?
1134	I need this to decide about setting colors etc.</a></strong><br />
1135	</dt>
1136	<dd>
1137	rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can
1138	check and see if that is set. Note that several programs, JED, slrn,
1139	Midnight Commander automatically check this variable to decide whether or
1140	not to use color.
1141	</dd>
1142	<p></p>
1143	<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 />
1144	</dt>
1145	<dd>
1146	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
1147	insecure mode then it is possible to use the following shell script
1148	snippets to correctly set the display. If your version of rxvt-unicode
1149	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
1150	the COLORTERM variable can be used to distinguish rxvt-unicode from a
1151	regular xterm.
1152	</dd>
1153	<dd>
1154	<p>Courtesy of Chuck Blake &lt;<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>&gt; with the following shell script
1155	snippets:</p>
1156	</dd>
1157	<dd>
1158	<pre>
1159	# Bourne/Korn/POSIX family of shells:
1160	[ ${TERM:-foo} = foo ] &amp;&amp; TERM=xterm # assume an xterm if we don't know
1161	if [ ${TERM:-foo} = xterm ]; then
1162	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
1163	echo -n '^[Z'
1164	read term_id
1165	stty icanon echo
1166	if [ &quot;&quot;${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
1167	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
1168	read DISPLAY # set it in our local shell
1169	fi
1170	fi</pre>
1171	</dd>
1172	<p></p>
1173	<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 />
1174	</dt>
1175	<dd>
1176	You need to have a recent version of perl installed as <em>/usr/bin/perl</em>,
1177	one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to
1178	the doc subdirectory and enter <code>make alldoc</code>.
1179	</dd>
1180	<p></p>
1181	<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 />
1182	</dt>
1183	<dd>
1184	Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>,
1185	channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be
1186	interested in learning about new and exciting problems (but not FAQs :).
1187	</dd>
1188	<p></p></dl>
1189	<p>	1229	<p>
1190	</p>	1230	</p>
1191	<hr />	1231	<hr />
1192	<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>	1232	<h1><a name="rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></h1>
1193	<p>
1194	</p>
1195	<hr />
1196	<h1><a name="description">DESCRIPTION</a></h1>
1197	<p>The rest of this document describes various technical aspects of	1233	<p>The rest of this document describes various technical aspects of
1198	<strong>rxvt-unicode</strong>. First the description of supported command sequences,	1234	<strong>rxvt-unicode</strong>. First the description of supported command sequences,
1199	followed by pixmap support and last by a description of all features	1235	followed by pixmap support and last by a description of all features
1200	selectable at <code>configure</code> time.</p>	1236	selectable at <code>configure</code> time.</p>
1201	<p>	1237	<p>
1202	</p>	1238	</p>
1203	<hr />
1204	<h1><a name="definitions">Definitions</a></h1>	1239	<h2><a name="definitions">Definitions</a></h2>
1205	<dl>	1240	<dl>
1206	<dt><strong><a name="item_c"><strong><code>c</code> </strong>&gt;</a></strong><br />	1241	<dt><strong><a name="item_c"><strong><code>c</code> </strong>&gt;</a></strong><br />
1207	</dt>	1242	</dt>
1208	<dd>	1243	<dd>
1209	The literal character c.	1244	The literal character c.
…		…
1235	A text parameter composed of printable characters.	1270	A text parameter composed of printable characters.
1236	</dd>	1271	</dd>
1237	<p></p></dl>	1272	<p></p></dl>
1238	<p>	1273	<p>
1239	</p>	1274	</p>
1240	<hr />
1241	<h1><a name="values">Values</a></h1>	1275	<h2><a name="values">Values</a></h2>
1242	<dl>	1276	<dl>
1243	<dt><strong><a name="item_enq"><strong><code>ENQ</code> </strong>&gt;</a></strong><br />	1277	<dt><strong><a name="item_enq"><strong><code>ENQ</code> </strong>&gt;</a></strong><br />
1244	</dt>	1278	</dt>
1245	<dd>	1279	<dd>
1246	Enquiry (Ctrl-E) = Send Device Attributes (DA)	1280	Enquiry (Ctrl-E) = Send Device Attributes (DA)
…		…
1309	Space Character	1343	Space Character
1310	</dd>	1344	</dd>
1311	<p></p></dl>	1345	<p></p></dl>
1312	<p>	1346	<p>
1313	</p>	1347	</p>
1314	<hr />
1315	<h1><a name="escape_sequences">Escape Sequences</a></h1>	1348	<h2><a name="escape_sequences">Escape Sequences</a></h2>
1316	<dl>	1349	<dl>
1317	<dt><strong><a name="item_esc__23_8"><strong><code>ESC # 8</code> </strong>&gt;</a></strong><br />	1350	<dt><strong><a name="item_esc__23_8"><strong><code>ESC # 8</code> </strong>&gt;</a></strong><br />
1318	</dt>	1351	</dt>
1319	<dd>	1352	<dd>
1320	DEC Screen Alignment Test (DECALN)	1353	DEC Screen Alignment Test (DECALN)
…		…
1453	<tr><td>C = K </td><td>German character set unimplemented</td></tr>	1486	<tr><td>C = K </td><td>German character set unimplemented</td></tr>
1454	</table><p></p></dl>	1487	</table><p></p></dl>
1455	<p></p>	1488	<p></p>
1456	<p>	1489	<p>
1457	</p>	1490	</p>
1458	<hr />
1459	<h1><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h1>	1491	<h2><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h2>
1460	<dl>	1492	<dl>
1461	<dt><strong><a name="item_esc__5b_ps__40"><strong><code>ESC [ Ps @</code> </strong>&gt;</a></strong><br />	1493	<dt><strong><a name="item_esc__5b_ps__40"><strong><code>ESC [ Ps @</code> </strong>&gt;</a></strong><br />
1462	</dt>	1494	</dt>
1463	<dd>	1495	<dd>
1464	Insert <strong><a href="#item_ps"><code>Ps</code></a> </strong>&gt; (Blank) <code>Character(s)</code> [default: 1] (ICH)	1496	Insert <strong><a href="#item_ps"><code>Ps</code></a> </strong>&gt; (Blank) <code>Character(s)</code> [default: 1] (ICH)
…		…
1760	</dd>	1792	</dd>
1761	<p></p></dl>	1793	<p></p></dl>
1762	<p></p>	1794	<p></p>
1763	<p>	1795	<p>
1764	</p>	1796	</p>
1765	<hr />
1766	<h1><a name="dec_private_modes">DEC Private Modes</a></h1>	1797	<h2><a name="dec_private_modes">DEC Private Modes</a></h2>
1767	<dl>	1798	<dl>
1768	<dt><strong><a name="item_esc__5b__3f_pm_h"><strong><code>ESC [ ? Pm h</code> </strong>&gt;</a></strong><br />	1799	<dt><strong><a name="item_esc__5b__3f_pm_h"><strong><code>ESC [ ? Pm h</code> </strong>&gt;</a></strong><br />
1769	</dt>	1800	</dt>
1770	<dd>	1801	<dd>
1771	DEC Private Mode Set (DECSET)	1802	DEC Private Mode Set (DECSET)
…		…
1937	</table></dl>	1968	</table></dl>
1938	</dl>	1969	</dl>
1939	<p></p>	1970	<p></p>
1940	<p>	1971	<p>
1941	</p>	1972	</p>
1942	<hr />
1943	<h1><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h1>	1973	<h2><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h2>
1944	<dl>	1974	<dl>
1945	<dt><strong><a name="item_esc__5d_ps_3bpt_st"><strong><code>ESC ] Ps;Pt ST</code> </strong>&gt;</a></strong><br />	1975	<dt><strong><a name="item_esc__5d_ps_3bpt_st"><strong><code>ESC ] Ps;Pt ST</code> </strong>&gt;</a></strong><br />
1946	</dt>	1976	</dt>
1947	<dd>	1977	<dd>
1948	Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b,	1978	Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b,
…		…
1980	<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>	2010	<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1981	<tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>	2011	<tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
1982	<tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>	2012	<tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
1983	<tr><td>Ps = 777</td><td>Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).</td></tr>	2013	<tr><td>Ps = 777</td><td>Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).</td></tr>
1984	</table><p></p></dl>	2014	</table><p></p></dl>
1985	<p></p>
1986	<p>	2015	<p>
1987	</p>	2016	</p>
1988	<hr />	2017	<hr />
1989	<h1><a name="xpm">XPM</a></h1>	2018	<h1><a name="xpm">XPM</a></h1>
1990	<p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value	2019	<p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value
…		…
2095	</dt>	2124	</dt>
2096	<table>	2125	<table>
2097	<tr><td>4</td><td>Shift</td></tr>	2126	<tr><td>4</td><td>Shift</td></tr>
2098	<tr><td>8</td><td>Meta</td></tr>	2127	<tr><td>8</td><td>Meta</td></tr>
2099	<tr><td>16</td><td>Control</td></tr>	2128	<tr><td>16</td><td>Control</td></tr>
2100	<tr><td>32</td><td>Double Click (Rxvt extension)</td></tr>	2129	<tr><td>32</td><td>Double Click (rxvt extension)</td></tr>
2101	</table><p>Col = <strong><code>&lt;x&gt; - SPACE</code> </strong>&gt;</p>	2130	</table><p>Col = <strong><code>&lt;x&gt; - SPACE</code> </strong>&gt;</p>
2102	<p>Row = <strong><code>&lt;y&gt; - SPACE</code> </strong>&gt;</p>	2131	<p>Row = <strong><code>&lt;y&gt; - SPACE</code> </strong>&gt;</p>
2103	</dl>	2132	</dl>
2104	<p>	2133	<p>
2105	</p>	2134	</p>
…		…
2424	<pre>	2453	<pre>
2425	MWM-hints	2454	MWM-hints
2426	EWMH-hints (pid, utf8 names) and protocols (ping)	2455	EWMH-hints (pid, utf8 names) and protocols (ping)
2427	seperate underline colour (-underlineColor)	2456	seperate underline colour (-underlineColor)
2428	settable border widths and borderless switch (-w, -b, -bl)	2457	settable border widths and borderless switch (-w, -b, -bl)
2429	visual selection (-depth)	2458	visual depth selection (-depth)
2430	settable extra linespacing /-lsp)	2459	settable extra linespacing /-lsp)
2431	iso-14755-2 and -3, and visual feedback	2460	iso-14755-2 and -3, and visual feedback
2432	backindex and forwardindex escape sequence
2433	window op and some xterm/OSC escape sequences
2434	tripleclickwords (-tcw)	2461	tripleclickwords (-tcw)
2435	settable insecure mode (-insecure)	2462	settable insecure mode (-insecure)
2436	keysym remapping support	2463	keysym remapping support
2437	cursor blinking and underline cursor (-cb, -uc)	2464	cursor blinking and underline cursor (-cb, -uc)
2438	XEmbed support (-embed)	2465	XEmbed support (-embed)
2439	user-pty (-pty-fd)	2466	user-pty (-pty-fd)
2440	hold on exit (-hold)	2467	hold on exit (-hold)
2441	skip builtin block graphics (-sbg)	2468	skip builtin block graphics (-sbg)</pre>
		2469	</dd>
		2470	<dd>
		2471	<p>It also enabled some non-essential features otherwise disabled, such as:</p>
		2472	</dd>
		2473	<dd>
		2474	<pre>
		2475	some round-trip time optimisations
		2476	nearest color allocation on pseudocolor screens
		2477	UTF8_STRING supporr for selection
2442	sgr modes 90..97 and 100..107</pre>	2478	sgr modes 90..97 and 100..107
		2479	backindex and forwardindex escape sequences
		2480	view change/zero scorllback esacpe sequences
		2481	locale switching escape sequence
		2482	window op and some xterm/OSC escape sequences
		2483	rectangular selections
		2484	trailing space removal for selections
		2485	verbose X error handling</pre>
2443	</dd>	2486	</dd>
2444	<p></p>	2487	<p></p>
2445	<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />	2488	<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />
2446	</dt>	2489	</dt>
2447	<dd>	2490	<dd>

Diff Legend

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