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

Diff Legend

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