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.64 by root, Tue Jan 31 21:04:14 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_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li>
		30	<li><a href="#how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></li>
		31	<li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li>
		32	<li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li>
		33	<li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li>
		34	</ul>
		35
		36	<li><a href="#rendering__font___look_and_feel_issues">Rendering, Font &amp; Look and Feel Issues</a></li>
		37	<ul>
		38
		39	<li><a href="#i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></li>
		40	<li><a href="#why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></li>
		41	<li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li>
		42	<li><a href="#how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></li>
		43	<li><a href="#some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></li>
		44	<li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li>
		45	<li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li>
		46	<li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li>
		47	<li><a href="#rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></li>
		48	<li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li>
		49	<li><a href="#i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></li>
		50	<li><a href="#why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></li>
		51	</ul>
		52
		53	<li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></li>
		54	<ul>
		55
		56	<li><a href="#the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></li>
		57	<li><a href="#i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></li>
		58	<li><a href="#the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></li>
		59	<li><a href="#during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></li>
		60	<li><a href="#my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></li>
		61	<li><a href="#my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></li>
		62	<li><a href="#i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></li>
		63	<li><a href="#mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></li>
		64	<li><a href="#what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></li>
		65	<li><a href="#i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></li>
		66	<li><a href="#i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></li>
		67	</ul>
		68
		69	<li><a href="#terminal_configuration">Terminal Configuration</a></li>
		70	<ul>
		71
		72	<li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li>
		73	<li><a href="#when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></li>
		74	<li><a href="#tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></li>
		75	<li><a href="#bash_s_readline_does_not_work_correctly_under_urxvt_"><code>bash</code>'s readline does not work correctly under urxvt.</a></li>
		76	<li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li>
		77	<li><a href="#why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></li>
		78	<li><a href="#why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></li>
		79	<li><a href="#why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></li>
		80	<li><a href="#why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></li>
		81	</ul>
		82
		83	<li><a href="#encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></li>
		84	<ul>
		85
		86	<li><a href="#rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></li>
		87	<li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</a></li>
		88	<li><a href="#how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></li>
		89	<li><a href="#is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></li>
		90	<li><a href="#can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></li>
		91	<li><a href="#my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></li>
		92	<li><a href="#rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></li>
		93	</ul>
		94
		95	<li><a href="#operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></li>
		96	<ul>
		97
		98	<li><a href="#i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></li>
		99	<li><a href="#i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></li>
		100	<li><a href="#i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></li>
		101	<li><a href="#on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></li>
		102	<li><a href="#i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></li>
		103	<li><a href="#i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></li>
		104	<li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li>
		105	</ul>
		106
		107	</ul>
		108
19	<li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li>	109	<li><a href="#rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></li>
20	<li><a href="#description">DESCRIPTION</a></li>	110	<li><a href="#description">DESCRIPTION</a></li>
21	<li><a href="#definitions">Definitions</a></li>	111	<li><a href="#definitions">Definitions</a></li>
22	<li><a href="#values">Values</a></li>	112	<li><a href="#values">Values</a></li>
23	<li><a href="#escape_sequences">Escape Sequences</a></li>	113	<li><a href="#escape_sequences">Escape Sequences</a></li>
24	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>	114	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
…		…
59	<p>The newest version of this document is also available on the World Wide Web at	149	<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>	150	<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
61	<p>	151	<p>
62	</p>	152	</p>
63	<hr />	153	<hr />
64	<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>	154	<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>	155	<p>
75	URxvt.selection.pattern-0: ([[:word:]]+)</pre>	156	</p>
76	</dd>	157	<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>	158	<p>
86	URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>	159	</p>
87	</dd>	160	<h3><a name="my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></h3>
88	<dd>	161	<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	162	channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be
90	selects words like the old code.</p>	163	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>	164	<p>
110	URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>	165	</p>
111	</dd>	166	<h3><a name="does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></h3>
112	<dd>	167	<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	168	simple tabbed terminal. It is installed by default, so any of these should
114	extensions. Some extensions can also be configured, for example,	169	give you tabs:</p>
115	scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any	170	<pre>
116	other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>	171	urxvt -pe tabbed</pre>
117	</dd>	172	<pre>
118	<dd>	173	URxvt.perl-ext-common: default,tabbed</pre>
		174	<p>It will also work fine with tabbing functionality of many window managers
		175	or similar tabbing programs, and its embedding-features allow it to be
		176	embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or
		177	the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt
		178	(murxvt) terminal as an example embedding application.</p>
119	<pre>	179	<p>
120	URxvt.searchable-scrollback: CM-s</pre>	180	</p>
121	</dd>	181	<h3><a name="how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></h3>
122	<p></p>	182	<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 />	183	sequence <code>ESC [ 8 n</code> sets the window title to the version number. When
124	</dt>	184	using the urxvtc client, the version displayed is that of the
125	<dd>	185	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>	186	<p>
142	URxvt.resource: value</pre>	187	</p>
143	</dd>	188	<h3><a name="rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></h3>
144	<dd>	189	<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	190	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	191	you don't need, for example, Xft support is a resource hog by design,
147	works. If unsure, use the form above.</p>	192	when used. Compiling it out ensures that no Xft font will be loaded
148	</dd>	193	accidentally when rxvt-unicode tries to find a font for your characters.</p>
149	<p></p>	194	<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 />	195	scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use
151	</dt>	196	6 bytes per screen cell. For a 160x?? window this amounts to almost a
152	<dd>	197	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	198	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	199	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>	200	<p>
167	Esetroot wallpaper.jpg	201	</p>
168	rxvt -ip -tint red -sh 40</pre>	202	<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>	203	<p>Try <code>urxvtd -f -o</code>, which tells urxvtd to open the
170	<dd>	204	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>	205	<p>
181	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	206	</p>
182	rxvt -pixmap background.xpm -pe automove-background</pre>	207	<h3><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3>
183	</dd>	208	<p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'',
184	<dd>	209	so you can check and see if that is set. Note that several programs, JED,
185	<p>That works. If you think it doesn't, you lack XPM and Perl support, or you	210	slrn, Midnight Commander automatically check this variable to decide
186	are unable to read.</p>	211	whether or not to use color.</p>
187	</dd>
188	<dd>
189	<p>3. Use an ARGB visual:</p>
190	</dd>
191	<dd>
192	<pre>	212	<p>
193	rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>	213	</p>
194	</dd>	214	<h3><a name="how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></h3>
195	<dd>	215	<p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
196	<p>This requires XFT support, and the support of your X-server. If that	216	insecure mode then it is possible to use the following shell script
197	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't	217	snippets to correctly set the display. If your version of rxvt-unicode
198	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary	218	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
199	bugfixes and workarounds for Xft and Xlib to make it work, but that	219	the COLORTERM variable can be used to distinguish rxvt-unicode from a
200	doesn't mean that your WM has the required kludges in place.</p>	220	regular xterm.</p>
201	</dd>	221	<p>Courtesy of Chuck Blake &lt;<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>&gt; with the following shell script
202	<dd>	222	snippets:</p>
203	<p>4. Use xcompmgr and let it do the job:</p>	223	<pre>
204	</dd>	224	# Bourne/Korn/POSIX family of shells:
205	<dd>	225	[ ${TERM:-foo} = foo ] &amp;&amp; TERM=xterm # assume an xterm if we don't know
		226	if [ ${TERM:-foo} = xterm ]; then
		227	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		228	echo -n '^[Z'
		229	read term_id
		230	stty icanon echo
		231	if [ &quot;&quot;${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		232	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		233	read DISPLAY # set it in our local shell
		234	fi
		235	fi</pre>
206	<pre>	236	<p>
207	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \	237	</p>
208	-set _NET_WM_WINDOW_OPACITY 0xc0000000</pre>	238	<h3><a name="how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></h3>
209	</dd>	239	<p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>,
210	<dd>	240	one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to
211	<p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code>	241	the doc subdirectory and enter <code>make alldoc</code>.</p>
212	by other values to change the degree of opacity. If it doesn't work and	242	<p>
213	your server crashes, you got to keep the pieces.</p>	243	</p>
214	</dd>
215	<p></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 />	244	<h3><a name="isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></h3>
217	</dt>
218	<dd>
219	I often get asked about this, and I think, no, they didn't cause extra	245	<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	246	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	247	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	248	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	249	with <code>--disable-everything</code>, this comparison is a bit unfair, as many
224	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are	250	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
225	already in use in this mode.	251	already in use in this mode.</p>
226	</dd>
227	<dd>
228	<pre>	252	<pre>
229	text data bss drs rss filename	253	text data bss drs rss filename
230	98398 1664 24 15695 1824 rxvt --disable-everything	254	98398 1664 24 15695 1824 rxvt --disable-everything
231	188985 9048 66616 18222 1788 urxvt --disable-everything</pre>	255	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	256	<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	257	and full locale/XIM support which are quite bloaty inside libX11 and my
236	libc), the two diverge, but not unreasnobaly so.</p>	258	libc), the two diverge, but not unreasnobaly so.</p>
237	</dd>
238	<dd>
239	<pre>	259	<pre>
240	text data bss drs rss filename	260	text data bss drs rss filename
241	163431 2152 24 20123 2060 rxvt --enable-everything	261	163431 2152 24 20123 2060 rxvt --enable-everything
242	1035683 49680 66648 29096 3680 urxvt --enable-everything</pre>	262	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	263	<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	264	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	265	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++	266	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	267	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	268	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	269	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
252	not used.</p>	270	not used.</p>
253	</dd>
254	<dd>
255	<p>Of course, due to every character using two or four bytes instead of one,	271	<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	272	a large scrollback buffer will ultimately make rxvt-unicode use more
257	memory.</p>	273	memory.</p>
258	</dd>
259	<dd>
260	<p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this	274	<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	275	still fares rather well. And compared to some monsters like gnome-terminal
262	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	276	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
263	43180k in daemons that stay around after exit, plus half a minute of	277	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	278	startup time, including the hundreds of warnings it spits out), it fares
265	extremely well *g*.</p>	279	extremely well *g*.</p>
266	</dd>	280	<p>
267	<p></p>	281	</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 />	282	<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	283	<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	284	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	285	of the time and effort (which is a scarce resource for me). Put even
274	shorter: It simply wouldn't exist without C++.	286	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	287	<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	288	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	289	are defined by things like X11, pseudo terminals, locale support and unix
280	domain sockets, which are all less portable than C++ itself.</p>	290	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	291	<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	292	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	293	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	294	not necessarily the case with GCC. Here is what rxvt links against on my
287	system with a minimal config:</p>	295	system with a minimal config:</p>
288	</dd>
289	<dd>
290	<pre>	296	<pre>
291	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	297	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
292	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)	298	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)
293	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)	299	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)
294	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>	300	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
295	</dd>
296	<dd>
297	<p>And here is rxvt-unicode:</p>	301	<p>And here is rxvt-unicode:</p>
298	</dd>
299	<dd>
300	<pre>	302	<pre>
301	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	303	libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
302	libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)	304	libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)
303	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)	305	libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)
304	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)	306	libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)
305	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>	307	/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),	308	<p>No large bloated libraries (of course, none were linked in statically),
309	except maybe libX11 :)</p>	309	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>	310	<p>
321	rxvt -pe tabbed</pre>	311	</p>
322	</dd>	312	<h2><a name="rendering__font___look_and_feel_issues">Rendering, Font &amp; Look and Feel Issues</a></h2>
323	<dd>
324	<pre>	313	<p>
		314	</p>
		315	<h3><a name="i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></h3>
		316	<p>First of all, transparency isn't officially supported in rxvt-unicode, so
		317	you are mostly on your own. Do not bug the author about it (but you may
		318	bug everybody else). Also, if you can't get it working consider it a rite
		319	of passage: ... and you failed.</p>
		320	<p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option
		321	descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p>
		322	<p>1. Use inheritPixmap:</p>
		323	<pre>
		324	Esetroot wallpaper.jpg
		325	urxvt -ip -tint red -sh 40</pre>
		326	<p>That works. If you think it doesn't, you lack transparency and tinting
		327	support, or you are unable to read.</p>
		328	<p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		329	to use effects other than tinting and shading: Just shade/tint/whatever
		330	your picture with gimp or any other tool:</p>
		331	<pre>
		332	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		333	urxvt -pixmap background.xpm -pe automove-background</pre>
		334	<p>That works. If you think it doesn't, you lack XPM and Perl support, or you
		335	are unable to read.</p>
		336	<p>3. Use an ARGB visual:</p>
		337	<pre>
		338	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>
		339	<p>This requires XFT support, and the support of your X-server. If that
		340	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		341	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		342	bugfixes and workarounds for Xft and Xlib to make it work, but that
		343	doesn't mean that your WM has the required kludges in place.</p>
		344	<p>4. Use xcompmgr and let it do the job:</p>
		345	<pre>
		346	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		347	-set _NET_WM_WINDOW_OPACITY 0xc0000000</pre>
		348	<p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code>
		349	by other values to change the degree of opacity. If it doesn't work and
		350	your server crashes, you got to keep the pieces.</p>
		351	<p>
		352	</p>
		353	<h3><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h3>
		354	<p>This is because there is a difference between script and language --
		355	rxvt-unicode does not know which language the text that is output is,
		356	as it only knows the unicode character codes. If rxvt-unicode first
		357	sees a japanese/chinese character, it might choose a japanese font for
		358	display. Subsequent japanese characters will use that font. Now, many
		359	chinese characters aren't represented in japanese fonts, so when the first
		360	non-japanese character comes up, rxvt-unicode will look for a chinese font
		361	-- unfortunately at this point, it will still use the japanese font for
		362	chinese characters that are also in the japanese font.</p>
		363	<p>The workaround is easy: just tag a chinese font at the end of your font
		364	list (see the previous question). The key is to view the font list as
		365	a preference list: If you expect more japanese, list a japanese font
		366	first. If you expect more chinese, put a chinese font first.</p>
		367	<p>In the future it might be possible to switch language preferences at
		368	runtime (the internal data structure has no problem with using different
		369	fonts for the same character at the same time, but no interface for this
		370	has been designed yet).</p>
		371	<p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p>
		372	<p>
		373	</p>
		374	<h3><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h3>
		375	<p>Most fonts were not designed for terminal use, which means that character
		376	size varies a lot. A font that is otherwise fine for terminal use might
		377	contain some characters that are simply too wide. Rxvt-unicode will avoid
		378	these characters. For characters that are just ``a bit'' too wide a special
		379	``careful'' rendering mode is used that redraws adjacent characters.</p>
		380	<p>All of this requires that fonts do not lie about character sizes,
		381	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		382	box, and rxvt-unicode has no way of detecting this (the correct way is to
		383	ask for the character bounding box, which unfortunately is wrong in these
		384	cases).</p>
		385	<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,
		386	or the respective font. If you encounter this problem you might try using
		387	the <code>-lsp</code> option to give the font more height. If that doesn't work, you
		388	might be forced to use a different font.</p>
		389	<p>All of this is not a problem when using X11 core fonts, as their bounding
		390	box data is correct.</p>
		391	<p>
		392	</p>
		393	<h3><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h3>
		394	<p>First of all, make sure you are running with the right terminal settings
		395	(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
		396	make sure you have specified colours for italic and bold, as otherwise
		397	rxvt-unicode might use reverse video to simulate the effect:</p>
		398	<pre>
		399	URxvt.colorBD: white
		400	URxvt.colorIT: green</pre>
		401	<p>
		402	</p>
		403	<h3><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h3>
		404	<p>For some unexplainable reason, some rare programs assume a very weird
		405	colour palette when confronted with a terminal with more than the standard
		406	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		407	these programs not to assume non-ISO colours without very good reasons.</p>
		408	<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
		409	definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
		410	fix colours but keep you from using other rxvt-unicode features.</p>
		411	<p>
		412	</p>
		413	<h3><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h3>
		414	<p>Yes, using an escape sequence. Try something like this, which has the same
		415	effect as using the <code>-fn</code> switch, and takes effect immediately:</p>
		416	<pre>
		417	printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
		418	<p>This is useful if you e.g. work primarily with japanese (and prefer a
		419	japanese font), but you have to switch to chinese temporarily, where
		420	japanese fonts would only be in your way.</p>
		421	<p>You can think of this as a kind of manual ISO-2022 switching.</p>
		422	<p>
		423	</p>
		424	<h3><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h3>
		425	<p>Many fonts have difficulties with italic characters and hinting. For
		426	example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
		427	Mono</code> completely fails in it's italic face. A workaround might be to
		428	enable freetype autohinting, i.e. like this:</p>
		429	<pre>
		430	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		431	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
		432	<p>
		433	</p>
		434	<h3><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h3>
		435	<p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		436	it is simply slow. If you still want Xft fonts you might try to disable
		437	antialiasing (by appending <code>:antialias=false</code>), which saves lots of
		438	memory and also speeds up rendering considerably.</p>
		439	<p>
		440	</p>
		441	<h3><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h3>
		442	<p>Rxvt-unicode will use whatever you specify as a font. If it needs to
		443	fall back to it's default font search list it will prefer X11 core
		444	fonts, because they are small and fast, and then use Xft fonts. It has
		445	antialiasing disabled for most of them, because the author thinks they
		446	look best that way.</p>
		447	<p>If you want antialiasing, you have to specify the fonts manually.</p>
		448	<p>
		449	</p>
		450	<h3><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h3>
		451	<p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
		452	standard foreground colour.</p>
		453	<p>For the standard background colour, blinking will actually make the
		454	text blink when compiled with <code>--enable-blinking</code>. with standard
		455	colours. Without <code>--enable-blinking</code>, the blink attribute will be
		456	ignored.</p>
		457	<p>On ANSI colours, bold/blink attributes are used to set high-intensity
		458	foreground/background colors.</p>
		459	<p>color0-7 are the low-intensity colors.</p>
		460	<p>color8-15 are the corresponding high-intensity colors.</p>
		461	<p>
		462	</p>
		463	<h3><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></h3>
		464	<p>You can change the screen colors at run-time using <em>~/.Xdefaults</em>
		465	resources (or as long-options).</p>
		466	<p>Here are values that are supposed to resemble a VGA screen,
		467	including the murky brown that passes for low-intensity yellow:</p>
		468	<pre>
		469	URxvt.color0: #000000
		470	URxvt.color1: #A80000
		471	URxvt.color2: #00A800
		472	URxvt.color3: #A8A800
		473	URxvt.color4: #0000A8
		474	URxvt.color5: #A800A8
		475	URxvt.color6: #00A8A8
		476	URxvt.color7: #A8A8A8</pre>
		477	<pre>
		478	URxvt.color8: #000054
		479	URxvt.color9: #FF0054
		480	URxvt.color10: #00FF54
		481	URxvt.color11: #FFFF54
		482	URxvt.color12: #0000FF
		483	URxvt.color13: #FF00FF
		484	URxvt.color14: #00FFFF
		485	URxvt.color15: #FFFFFF</pre>
		486	<p>And here is a more complete set of non-standard colors.</p>
		487	<pre>
		488	URxvt.cursorColor: #dc74d1
		489	URxvt.pointerColor: #dc74d1
		490	URxvt.background: #0e0e0e
		491	URxvt.foreground: #4ad5e1
		492	URxvt.color0: #000000
		493	URxvt.color8: #8b8f93
		494	URxvt.color1: #dc74d1
		495	URxvt.color9: #dc74d1
		496	URxvt.color2: #0eb8c7
		497	URxvt.color10: #0eb8c7
		498	URxvt.color3: #dfe37e
		499	URxvt.color11: #dfe37e
		500	URxvt.color5: #9e88f0
		501	URxvt.color13: #9e88f0
		502	URxvt.color6: #73f7ff
		503	URxvt.color14: #73f7ff
		504	URxvt.color7: #e1dddd
		505	URxvt.color15: #e1dddd</pre>
		506	<p>(They were described (not by me) as ``pretty girly'').</p>
		507	<p>
		508	</p>
		509	<h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3>
		510	<pre>
		511
		512	See next entry.</pre>
		513	<pre>
		514
		515	=head3 How does rxvt-unicode choose fonts?</pre>
		516	<pre>
		517
		518	Most fonts do not contain the full range of Unicode, which is
		519	fine. Chances are that the font you (or the admin/package maintainer of
		520	your system/os) have specified does not cover all the characters you want
		521	to display.</pre>
		522	<pre>
		523
		524	B&lt;rxvt-unicode&gt; makes a best-effort try at finding a replacement
		525	font. Often the result is fine, but sometimes the chosen font looks
		526	bad/ugly/wrong. Some fonts have totally strange characters that don't
		527	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		528	intelligence to detect that a specific glyph is wrong: it has to believe
		529	the font that the characters it claims to contain indeed look correct.</pre>
		530	<pre>
		531
		532	In that case, select a font of your taste and add it to the font list,
		533	e.g.:</pre>
		534	<pre>
		535
		536	urxvt -fn basefont,font2,font3...</pre>
		537	<pre>
		538
		539	When rxvt-unicode sees a character, it will first look at the base
		540	font. If the base font does not contain the character, it will go to the
		541	next font, and so on. Specifying your own fonts will also speed up this
		542	search and use less resources within rxvt-unicode and the X-server.</pre>
		543	<pre>
		544
		545	The only limitation is that none of the fonts may be larger than the base
		546	font, as the base font defines the terminal character cell size, which
		547	must be the same due to the way terminals work.</pre>
		548	<p>
		549	</p>
		550	<h2><a name="keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></h2>
		551	<p>
		552	</p>
		553	<h3><a name="the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></h3>
		554	<p>If you want to select e.g. alphanumeric words, you can use the following
		555	setting:</p>
		556	<pre>
		557	URxvt.selection.pattern-0: ([[:word:]]+)</pre>
		558	<p>If you click more than twice, the selection will be extended
		559	more and more.</p>
		560	<p>To get a selection that is very similar to the old code, try this pattern:</p>
		561	<pre>
		562	URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>
		563	<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also
		564	selects words like the old code.</p>
		565	<p>
		566	</p>
		567	<h3><a name="i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></h3>
		568	<p>You can disable the perl extension completely by setting the
		569	<strong>perl-ext-common</strong> resource to the empty string, which also keeps
		570	rxvt-unicode from initialising perl, saving memory.</p>
		571	<p>If you only want to disable specific features, you first have to
		572	identify which perl extension is responsible. For this, read the section
		573	<strong>PREPACKAGED EXTENSIONS</strong> in the <code>urxvtperl(3)</code> manpage. For
		574	example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify
		575	this <strong>perl-ext-common</strong> resource:</p>
		576	<pre>
		577	URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>
		578	<p>This will keep the default extensions, but disable the two popup
		579	extensions. Some extensions can also be configured, for example,
		580	scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any
		581	other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>
		582	<pre>
		583	URxvt.searchable-scrollback: CM-s</pre>
		584	<p>
		585	</p>
		586	<h3><a name="the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></h3>
		587	<p>See next entry.</p>
		588	<p>
		589	</p>
		590	<h3><a name="during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></h3>
		591	<p>These are caused by the <code>readline</code> perl extension. Under normal
		592	circumstances, it will move your cursor around when you click into the
		593	line that contains it. It tries hard not to do this at the wrong moment,
		594	but when running a program that doesn't parse cursor movements or in some
		595	cases during rlogin sessions, it fails to detect this properly.</p>
		596	<p>You can permamently switch this feature off by disabling the <code>readline</code>
		597	extension:</p>
		598	<pre>
325	URxvt.perl-ext-common: default,tabbed</pre>	599	URxvt.perl-ext-common: default,-readline</pre>
326	</dd>	600	<p>
327	<dd>	601	</p>
328	<p>It will also work fine with tabbing functionality of many window managers	602	<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	603	<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	604	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	605	by the wrong <code>TERM</code> setting, although the details of wether and how
332	(murxvt) terminal as an example embedding application.</p>	606	this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
333	</dd>	607	keymap. See the answer to the previous question, and please report if that
334	<p></p>	608	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 />	609	<p>
336	</dt>	610	</p>
337	<dd>	611	<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	612	<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	613	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	614	your input method. For example, if you specified <strong>OverTheSpot</strong> and
341	daemon.	615	your input method (e.g. the default input method handling Compose keys)
342	</dd>	616	does not support this (for instance because it is not visual), then
343	<p></p>	617	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 />	618	<p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than
345	</dt>	619	one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p>
346	<dd>	620	<p>
347	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	621	</p>
348	patches that considerably change the behaviour of rxvt-unicode (but	622	<h3><a name="i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></h3>
349	unfortunately this notice has been removed). Before reporting a bug to	623	<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	624	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	625	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	626	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	627	character and so on.</p>
354	Tracking System (use <code>reportbug</code> to report the bug).	628	<p>
355	</dd>	629	</p>
356	<dd>	630	<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	631	<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	632	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	633	heard that tcsh may use mouse reporting unless it otherwise specified. A
360	might encounter the same issue.</p>	634	quick check is to see if cut/paste works when the Alt or Shift keys are
361	</dd>	635	depressed.</p>
362	<p></p>	636	<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	637	</p>
364	recommendation?</a></strong><br />	638	<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>	639	<p>Assuming that the physical Backspace key corresponds to the
366	<dd>	640	BackSpace keysym (not likely for Linux ... see the following
367	You should build one binary with the default options. <em>configure</em>	641	question) there are two standard values that can be used for
368	now enables most useful options, and the trend goes to making them	642	Backspace: <code>^H</code> and <code>^?</code>.</p>
369	runtime-switchable, too, so there is usually no drawback to enbaling them,	643	<p>Historically, either value is correct, but rxvt-unicode adopts the debian
370	except higher disk and possibly memory usage. The perl interpreter should	644	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	645	choice :).</p>
372	the future) depends on it.	646	<p>Rxvt-unicode tries to inherit the current stty settings and uses the value
373	</dd>	647	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
374	<dd>	648	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	649	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	650	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	651	<p>For starting a new rxvt-unicode:</p>
378	<code>perl-ext-common</code> resource to the app-defaults file. This will keep the	652	<pre>
379	perl interpreter disabled until the user enables it.</p>	653	# use Backspace = ^H
380	</dd>	654	$ stty erase ^H
381	<dd>	655	$ urxvt</pre>
382	<p>If you can/want build more binaries, I recommend building a minimal	656	<pre>
383	one with <code>--disable-everything</code> (very useful) and a maximal one with	657	# 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	658	$ stty erase ^?
385	encodings built-in that increase download times and are rarely used).</p>	659	$ urxvt</pre>
386	</dd>	660	<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p>
387	<p></p>	661	<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 />	662	<pre>
389	</dt>	663	# use Backspace = ^H
390	<dd>	664	$ stty erase ^H
391	It should be, starting with release 7.1. You are encouraged to properly	665	$ echo -n &quot;^[[36h&quot;</pre>
392	install urxvt with privileges necessary for your OS now.	666	<pre>
393	</dd>	667	# use Backspace = ^?
394	<dd>	668	$ stty erase ^?
395	<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork	669	$ echo -n &quot;^[[36l&quot;</pre>
396	into a helper process for privileged operations (pty handling on some	670	<p>This helps satisfy some of the Backspace discrepancies that occur, but
397	systems, utmp/wtmp/lastlog handling on others) and drop privileges	671	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	672	properly reflects that.</p>
399	privileges while running (but is more relevant to urxvt, as it contains	673	<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>	674	To avoid confusion between the Backspace and Delete keys, the Delete
401	</dd>	675	key has been assigned an escape sequence to match the vt100 for Execute
402	<dd>	676	(<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	677	<p>Some other Backspace problems:</p>
404	and reduces possible bugs to initialisation code run before main(), or	678	<p>some editors use termcap/terminfo,
405	things like the dynamic loader of your system, which should result in very	679	some editors (vim I'm told) expect Backspace = ^H,
406	little risk.</p>	680	GNU Emacs (and Emacs-like editors) use ^H for help.</p>
407	</dd>	681	<p>Perhaps someday this will all be resolved in a consistent manner.</p>
408	<p></p>	682	<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 />	683	</p>
410	</dt>	684	<h3><a name="i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></h3>
411	<dd>	685	<p>There are some compile-time selections available via configure. Unless
		686	you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
		687	use the `keysym' resource to alter the keystrings associated with keysyms.</p>
		688	<p>Here's an example for a URxvt session started using <code>urxvt -name URxvt</code></p>
		689	<pre>
		690	URxvt.keysym.Home: \033[1~
		691	URxvt.keysym.End: \033[4~
		692	URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
		693	URxvt.keysym.C-slash: \033&lt;C-/&gt;
		694	URxvt.keysym.C-semicolon: \033&lt;C-;&gt;
		695	URxvt.keysym.C-grave: \033&lt;C-`&gt;
		696	URxvt.keysym.C-comma: \033&lt;C-,&gt;
		697	URxvt.keysym.C-period: \033&lt;C-.&gt;
		698	URxvt.keysym.C-0x60: \033&lt;C-`&gt;
		699	URxvt.keysym.C-Tab: \033&lt;C-Tab&gt;
		700	URxvt.keysym.C-Return: \033&lt;C-Return&gt;
		701	URxvt.keysym.S-Return: \033&lt;S-Return&gt;
		702	URxvt.keysym.S-space: \033&lt;S-Space&gt;
		703	URxvt.keysym.M-Up: \033&lt;M-Up&gt;
		704	URxvt.keysym.M-Down: \033&lt;M-Down&gt;
		705	URxvt.keysym.M-Left: \033&lt;M-Left&gt;
		706	URxvt.keysym.M-Right: \033&lt;M-Right&gt;
		707	URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
		708	URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
		709	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
		710	<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
		711	<p>
		712	</p>
		713	<h3><a name="i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></h3>
		714	<pre>
		715	KP_Insert == Insert
		716	F22 == Print
		717	F27 == Home
		718	F29 == Prior
		719	F33 == End
		720	F35 == Next</pre>
		721	<p>Rather than have rxvt-unicode try to accommodate all the various possible
		722	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		723	required for your particular machine.</p>
		724	<p>
		725	</p>
		726	<h2><a name="terminal_configuration">Terminal Configuration</a></h2>
		727	<p>
		728	</p>
		729	<h3><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h3>
		730	<p>Well, why, indeed? It does, in a way very similar to other X
		731	applications. Most importantly, this means that if you or your OS loads
		732	resources into the X display (the right way to do it), rxvt-unicode will
		733	ignore any resource files in your home directory. It will only read
		734	<em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p>
		735	<p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that
		736	resources are loaded into your X-server. In this case, you have to
		737	re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p>
		738	<p>Also consider the form resources have to use:</p>
		739	<pre>
		740	URxvt.resource: value</pre>
		741	<p>If you want to use another form (there are lots of different ways of
		742	specifying resources), make sure you understand wether and why it
		743	works. If unsure, use the form above.</p>
		744	<p>
		745	</p>
		746	<h3><a name="when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></h3>
412	The terminal description used by rxvt-unicode is not as widely available	747	<p>The terminal description used by rxvt-unicode is not as widely available
413	as that for xterm, or even rxvt (for which the same problem often arises).	748	as that for xterm, or even rxvt (for which the same problem often arises).</p>
414	</dd>
415	<dd>
416	<p>The correct solution for this problem is to install the terminfo, this can	749	<p>The correct solution for this problem is to install the terminfo, this can
417	be done like this (with ncurses' infocmp):</p>	750	be done like this (with ncurses' infocmp):</p>
418	</dd>
419	<dd>
420	<pre>	751	<pre>
421	REMOTE=remotesystem.domain	752	REMOTE=remotesystem.domain
422	infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre>	753	infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre>
423	</dd>
424	<dd>
425	<p>... or by installing rxvt-unicode normally on the remote system,</p>	754	<p>... or by installing rxvt-unicode normally on the remote system,</p>
426	</dd>
427	<dd>
428	<p>If you cannot or do not want to do this, then you can simply set	755	<p>If you cannot or do not want to do this, then you can simply set
429	<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of	756	<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of
430	problems arising, which includes wrong keymapping, less and different	757	problems arising, which includes wrong keymapping, less and different
431	colours and some refresh errors in fullscreen applications. It's a nice	758	colours and some refresh errors in fullscreen applications. It's a nice
432	quick-and-dirty workaround for rare cases, though.</p>	759	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	760	<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	761	can either recompile rxvt-unicode with the desired TERM value or use a
437	resource to set it:</p>	762	resource to set it:</p>
438	</dd>
439	<dd>
440	<pre>	763	<pre>
441	URxvt.termName: rxvt</pre>	764	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	765	<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>	766	the rxvt terminfo file with the rxvt-unicode one and use <code>TERM=rxvt</code>.</p>
446	</dd>	767	<p>
447	<p></p>	768	</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 />	769	<h3><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h3>
449	</dt>
450	<dd>
451	Most likely it's the empty definition for <code>enacs=</code>. Just replace it by	770	<p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
452	<code>enacs=\E[0@</code> and try again.	771	<code>enacs=\E[0@</code> and try again.</p>
453	</dd>	772	<p>
454	<p></p>	773	</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 />	774	<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>	775	<p>See next entry.</p>
		776	<p>
		777	</p>
457	<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />	778	<h3><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h3>
458	</dt>
459	<dd>
460	One reason you might want this is that some distributions or operating	779	<p>One reason you might want this is that some distributions or operating
461	systems still compile some programs using the long-obsoleted termcap	780	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	781	library (Fedora Core's bash is one example) and rely on a termcap entry
463	for <code>rxvt-unicode</code>.	782	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.	783	<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	784	You can also create a termcap entry by using terminfo's infocmp program
468	like this:</p>	785	like this:</p>
469	</dd>
470	<dd>
471	<pre>	786	<pre>
472	infocmp -C rxvt-unicode</pre>	787	infocmp -C rxvt-unicode</pre>
473	</dd>
474	<dd>
475	<p>Or you could use this termcap entry, generated by the command above:</p>	788	<p>Or you could use this termcap entry, generated by the command above:</p>
476	</dd>
477	<dd>
478	<pre>	789	<pre>
479	rxvt-unicode|rxvt-unicode terminal (X Window System):\	790	rxvt-unicode|rxvt-unicode terminal (X Window System):\
480	:am:bw:eo:km:mi:ms:xn:xo:\	791	:am:bw:eo:km:mi:ms:xn:xo:\
481	:co#80:it#8:li#24:lm#0:\	792	:co#80:it#8:li#24:lm#0:\
482	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	793	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
…		…
494	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\	805	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
495	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	806	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
496	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	807	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
497	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	808	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
498	:vs=\E[?25h:</pre>	809	:vs=\E[?25h:</pre>
499	</dd>	810	<p>
500	<p></p>	811	</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 />	812	<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	813	<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	814	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	815	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:	816	with most other terminals supporting colour). Either add:</p>
508	</dd>
509	<dd>
510	<pre>	817	<pre>
511	TERM rxvt-unicode</pre>	818	TERM rxvt-unicode</pre>
512	</dd>
513	<dd>
514	<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>	819	<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>
515	</dd>
516	<dd>
517	<pre>	820	<pre>
518	alias ls='ls --color=auto'</pre>	821	alias ls='ls --color=auto'</pre>
519	</dd>
520	<dd>
521	<p>to your <code>.profile</code> or <code>.bashrc</code>.</p>	822	<p>to your <code>.profile</code> or <code>.bashrc</code>.</p>
522	</dd>	823	<p>
523	<p></p>	824	</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 />	825	<h3><a name="why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></h3>
525	</dt>	826	<p>See next entry.</p>
		827	<p>
		828	</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 />	829	<h3><a name="why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></h3>
527	</dt>	830	<p>See next entry.</p>
		831	<p>
		832	</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 />	833	<h3><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h3>
529	</dt>
530	<dd>
531	Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged	834	<p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged
532	distributions (most notably Debian GNU/Linux) break rxvt-unicode	835	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	836	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	837	features. Unfortunately, some of these (most notably, again, Debian
535	GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo	838	GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo
536	file, so you will need to install it on your own (See the question <strong>When	839	file, so you will need to install it on your own (See the question <strong>When
537	I log-in to another system it tells me about missing terminfo data?</strong> on	840	I log-in to another system it tells me about missing terminfo data?</strong> on
538	how to do this).	841	how to do this).</p>
539	</dd>	842	<p>
540	<p></p>	843	</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 />	844	<h2><a name="encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></h2>
542	</dt>	845	<p>
543	<dd>	846	</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 />	847	<h3><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h3>
553	</dt>	848	<p>See next entry.</p>
		849	<p>
		850	</p>
554	<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br />	851	<h3><a name="unicode_does_not_seem_to_work">Unicode does not seem to work?</a></h3>
555	</dt>
556	<dd>
557	If you encounter strange problems like typing an accented character but	852	<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	853	getting two unrelated other characters or similar, or if program output is
559	subtly garbled, then you should check your locale settings.	854	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	855	<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	856	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	857	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>	858	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	859	<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>	860	into other problems. If nothing works you can try this in your .profile.</p>
570	</dd>
571	<dd>
572	<pre>	861	<pre>
573	printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre>	862	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	863	<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	864	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	865	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	866	it will complain loudly if it cannot set the locale). If it displays something
580	like:</p>	867	like:</p>
581	</dd>
582	<dd>
583	<pre>	868	<pre>
584	locale: Cannot set LC_CTYPE to default locale: ...</pre>	869	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>	870	<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	871	<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	872	you will need to remember a little known fact: Some programs just don't
592	support locales :(</p>	873	support locales :(</p>
593	</dd>
594	<p></p>
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>
600	Most fonts do not contain the full range of Unicode, which is
601	fine. Chances are that the font you (or the admin/package maintainer of
602	your system/os) have specified does not cover all the characters you want
603	to display.
604	</dd>
605	<dd>
606	<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement
607	font. Often the result is fine, but sometimes the chosen font looks
608	bad/ugly/wrong. Some fonts have totally strange characters that don't
609	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
610	intelligence to detect that a specific glyph is wrong: it has to believe
611	the font that the characters it claims to contain indeed look correct.</p>
612	</dd>
613	<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>
617	<dd>
618	<pre>	874	<p>
619	rxvt -fn basefont,font2,font3...</pre>	875	</p>
620	</dd>	876	<h3><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h3>
621	<dd>	877	<p>See next entry.</p>
622	<p>When rxvt-unicode sees a character, it will first look at the base	878	<p>
623	font. If the base font does not contain the character, it will go to the	879	</p>
624	next font, and so on. Specifying your own fonts will also speed up this	880	<h3><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h3>
625	search and use less resources within rxvt-unicode and the X-server.</p>	881	<p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no
626	</dd>	882	specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about
627	<dd>	883	UTF-8 or any other encodings with respect to terminal I/O.</p>
628	<p>The only limitation is that none of the fonts may be larger than the base	884	<p>The reasons is that there exists a perfectly fine mechanism for selecting
629	font, as the base font defines the terminal character cell size, which	885	the encoding, doing I/O and (most important) communicating this to all
630	must be the same due to the way terminals work.</p>	886	applications so everybody agrees on character properties such as width
631	</dd>	887	and code number. This mechanism is the <em>locale</em>. Applications not using
632	<p></p>	888	that info will have problems (for example, <code>xterm</code> gets the width of
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 />	889	characters wrong as it uses it's own, locale-independent table under all
634	</dt>
635	<dd>
636	This is because there is a difference between script and language --
637	rxvt-unicode does not know which language the text that is output is,
638	as it only knows the unicode character codes. If rxvt-unicode first
639	sees a japanese/chinese character, it might choose a japanese font for
640	display. Subsequent japanese characters will use that font. Now, many
641	chinese characters aren't represented in japanese fonts, so when the first
642	non-japanese character comes up, rxvt-unicode will look for a chinese font
643	-- unfortunately at this point, it will still use the japanese font for
644	chinese characters that are also in the japanese font.
645	</dd>
646	<dd>
647	<p>The workaround is easy: just tag a chinese font at the end of your font
648	list (see the previous question). The key is to view the font list as
649	a preference list: If you expect more japanese, list a japanese font
650	first. If you expect more chinese, put a chinese font first.</p>
651	</dd>
652	<dd>
653	<p>In the future it might be possible to switch language preferences at
654	runtime (the internal data structure has no problem with using different
655	fonts for the same character at the same time, but no interface for this
656	has been designed yet).</p>
657	</dd>
658	<dd>
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>
660	</dd>
661	<p></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 />
663	</dt>
664	<dd>
665	Most fonts were not designed for terminal use, which means that character
666	size varies a lot. A font that is otherwise fine for terminal use might
667	contain some characters that are simply too wide. Rxvt-unicode will avoid
668	these characters. For characters that are just ``a bit'' too wide a special
669	``careful'' rendering mode is used that redraws adjacent characters.
670	</dd>
671	<dd>
672	<p>All of this requires that fonts do not lie about character sizes,
673	however: Xft fonts often draw glyphs larger than their acclaimed bounding
674	box, and rxvt-unicode has no way of detecting this (the correct way is to
675	ask for the character bounding box, which unfortunately is wrong in these
676	cases).</p>	890	locales).</p>
677	</dd>	891	<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
678	<dd>	892	programs doing the same (that is, most) will automatically agree in the
679	<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,	893	interpretation of characters.</p>
680	or the respective font. If you encounter this problem you might try using	894	<p>Unfortunately, there is no system-independent way to select locales, nor
681	the <code>-lsp</code> option to give the font more height. If that doesn't work, you	895	is there a standard on how locale specifiers will look like.</p>
682	might be forced to use a different font.</p>	896	<p>On most systems, the content of the <code>LC_CTYPE</code> environment variable
683	</dd>	897	contains an arbitrary string which corresponds to an already-installed
684	<dd>	898	locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>,
685	<p>All of this is not a problem when using X11 core fonts, as their bounding	899	<code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms
686	box data is correct.</p>	900	(i.e. <code>de</code> or <code>german</code>) are also common.</p>
687	</dd>	901	<p>Rxvt-unicode ignores all other locale categories, and except for
688	<p></p>	902	the encoding, ignores country or language-specific settings,
		903	i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
		904	rxvt-unicode.</p>
		905	<p>If you want to use a specific encoding you have to make sure you start
		906	rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
		907	<p>
		908	</p>
		909	<h3><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h3>
		910	<p>Yes, using an escape sequence. Try something like this, which sets
		911	rxvt-unicode's idea of <code>LC_CTYPE</code>.</p>
		912	<pre>
		913	printf '\e]701;%s\007' ja_JP.SJIS</pre>
		914	<p>See also the previous answer.</p>
		915	<p>Sometimes this capability is rather handy when you want to work in
		916	one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
		917	(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
		918	first switches to a locale supported by xjdic and back later:</p>
		919	<pre>
		920	printf '\e]701;%s\007' ja_JP.SJIS
		921	xjdic -js
		922	printf '\e]701;%s\007' de_DE.UTF-8</pre>
		923	<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
		924	for some locales where character width differs between program- and
		925	rxvt-unicode-locales.</p>
		926	<p>
		927	</p>
		928	<h3><a name="my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></h3>
		929	<p>You can specify separate locales for the input method and the rest of the
		930	terminal, using the resource <code>imlocale</code>:</p>
		931	<pre>
		932	URxvt.imlocale: ja_JP.EUC-JP</pre>
		933	<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
		934	use your input method. Please note, however, that you will not be able to
		935	input characters outside <code>EUC-JP</code> in a normal way then, as your input
		936	method limits you.</p>
		937	<p>
		938	</p>
		939	<h3><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h3>
		940	<p>Unfortunately, this is unavoidable, as the XIM protocol is racy by
		941	design. Applications can avoid some crashes at the expense of memory
		942	leaks, and Input Methods can avoid some crashes by careful ordering at
		943	exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
		944	while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
		945	crashes cannot be completely avoided even if both sides cooperate.</p>
		946	<p>So the only workaround is not to kill your Input Method Servers.</p>
		947	<p>
		948	</p>
		949	<h2><a name="operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></h2>
		950	<p>
		951	</p>
		952	<h3><a name="i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></h3>
		953	<p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		954	patches that considerably change the behaviour of rxvt-unicode (but
		955	unfortunately this notice has been removed). Before reporting a bug to
		956	the original rxvt-unicode author please download and install the genuine
		957	version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce
		958	the problem. If you cannot, chances are that the problems are specific to
		959	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		960	Tracking System (use <code>reportbug</code> to report the bug).</p>
		961	<p>For other problems that also affect the Debian package, you can and
		962	probably should use the Debian BTS, too, because, after all, it's also a
		963	bug in the Debian version and it serves as a reminder for other users that
		964	might encounter the same issue.</p>
		965	<p>
		966	</p>
		967	<h3><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h3>
		968	<p>You should build one binary with the default options. <em>configure</em>
		969	now enables most useful options, and the trend goes to making them
		970	runtime-switchable, too, so there is usually no drawback to enbaling them,
		971	except higher disk and possibly memory usage. The perl interpreter should
		972	be enabled, as important functionality (menus, selection, likely more in
		973	the future) depends on it.</p>
		974	<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
		975	system-wide (except maybe with <code>defaults</code>). This will result in useful
		976	behaviour. If your distribution aims at low memory, add an empty
		977	<code>perl-ext-common</code> resource to the app-defaults file. This will keep the
		978	perl interpreter disabled until the user enables it.</p>
		979	<p>If you can/want build more binaries, I recommend building a minimal
		980	one with <code>--disable-everything</code> (very useful) and a maximal one with
		981	<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of
		982	encodings built-in that increase download times and are rarely used).</p>
		983	<p>
		984	</p>
		985	<h3><a name="i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></h3>
		986	<p>It should be, starting with release 7.1. You are encouraged to properly
		987	install urxvt with privileges necessary for your OS now.</p>
		988	<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork
		989	into a helper process for privileged operations (pty handling on some
		990	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		991	immediately. This is much safer than most other terminals that keep
		992	privileges while running (but is more relevant to urxvt, as it contains
		993	things as perl interpreters, which might be ``helpful'' to attackers).</p>
		994	<p>This forking is done as the very first within main(), which is very early
		995	and reduces possible bugs to initialisation code run before main(), or
		996	things like the dynamic loader of your system, which should result in very
		997	little risk.</p>
		998	<p>
		999	</p>
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 />	1000	<h3><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h3>
690	</dt>
691	<dd>
692	Seems to be a known bug, read	1001	<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	1002	<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:	1003	following ugly workaround to get non-double-wide-characters working:</p>
695	</dd>
696	<dd>
697	<pre>	1004	<pre>
698	#define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>	1005	#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>	1006	<p>
736	URxvt.colorBD: white	1007	</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 />	1008	<h3><a name="i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></h3>
755	</dt>
756	<dd>
757	Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined	1009	<p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined
758	in your compile environment, or an implementation that implements it,	1010	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	1011	wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that
760	<strong>wchar_t</strong> is represented as unicode.	1012	<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	1013	<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	1014	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>	1015	<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	1016	<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>	1017	<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	1018	<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)	1019	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	1020	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	1021	<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	1022	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	1023	simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
778	locale encoding.</p>	1024	locale encoding.</p>
779	</dd>
780	<dd>
781	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this	1025	<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
782	by carrying their own replacement functions for character set handling	1026	by carrying their own replacement functions for character set handling
783	with them, and either implementing OS-dependent hacks or doing multiple	1027	with them, and either implementing OS-dependent hacks or doing multiple
784	conversions (which is slow and unreliable in case the OS implements	1028	conversions (which is slow and unreliable in case the OS implements
785	encodings slightly different than the terminal emulator).</p>	1029	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	1030	<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	1031	system libraries once and for all, instead of forcing every app to carry
790	complete replacements for them :)</p>	1032	complete replacements for them :)</p>
791	</dd>	1033	<p>
792	<p></p>	1034	</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 />	1035	<h3><a name="i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></h3>
794	</dt>
795	<dd>
796	Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst	1036	<p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
797	problems with <code>wcwidth</code> and a compile problem.	1037	problems with <code>wcwidth</code> and a compile problem.</p>
798	</dd>	1038	<p>
799	<p></p>	1039	</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 />	1040	<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	1041	<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	1042	the X11 libraries that come with cygwin. libW11 emulation is no
805	longer supported (and makes no sense, either, as it only supported a	1043	longer supported (and makes no sense, either, as it only supported a
806	single font). I recommend starting the X-server in <code>-multiwindow</code> or	1044	single font). I recommend starting the X-server in <code>-multiwindow</code> or
807	<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the	1045	<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
808	old libW11 emulation.	1046	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	1047	<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	1048	encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
813	to 8-bit encodings.</p>	1049	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>	1050	<p>
1282	</p>	1051	</p>
1283	<hr />	1052	<hr />
1284	<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>	1053	<h1><a name="rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></h1>
1285	<p>	1054	<p>
1286	</p>	1055	</p>
1287	<hr />	1056	<hr />
1288	<h1><a name="description">DESCRIPTION</a></h1>	1057	<h1><a name="description">DESCRIPTION</a></h1>
1289	<p>The rest of this document describes various technical aspects of	1058	<p>The rest of this document describes various technical aspects of
…		…
2187	</dt>	1956	</dt>
2188	<table>	1957	<table>
2189	<tr><td>4</td><td>Shift</td></tr>	1958	<tr><td>4</td><td>Shift</td></tr>
2190	<tr><td>8</td><td>Meta</td></tr>	1959	<tr><td>8</td><td>Meta</td></tr>
2191	<tr><td>16</td><td>Control</td></tr>	1960	<tr><td>16</td><td>Control</td></tr>
2192	<tr><td>32</td><td>Double Click (Rxvt extension)</td></tr>	1961	<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>	1962	</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>	1963	<p>Row = <strong><code>&lt;y&gt; - SPACE</code> </strong>&gt;</p>
2195	</dl>	1964	</dl>
2196	<p>	1965	<p>
2197	</p>	1966	</p>
…		…
2657	<p></p>	2426	<p></p>
2658	<dt><strong><a name="item__2d_2dwith_2dxpm_2dincludes_3ddir">--with-xpm-includes=DIR</a></strong><br />	2427	<dt><strong><a name="item__2d_2dwith_2dxpm_2dincludes_3ddir">--with-xpm-includes=DIR</a></strong><br />
2659	</dt>	2428	</dt>
2660	<dd>	2429	<dd>
2661	Look for the XPM includes in DIR.	2430	Look for the XPM includes in DIR.
		2431
		2432
2662	</dd>	2433	</dd>
2663	<p></p>	2434	<p></p>
2664	<dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br />	2435	<dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br />
2665	</dt>	2436	</dt>
2666	<dd>	2437	<dd>
2667	Look for the XPM library in DIR.	2438	Look for the XPM library in DIR.
		2439
		2440
2668	</dd>	2441	</dd>
2669	<p></p>	2442	<p></p>
2670	<dt><strong><a name="item__2d_2dwith_2dxpm">--with-xpm</a></strong><br />	2443	<dt><strong><a name="item__2d_2dwith_2dxpm">--with-xpm</a></strong><br />
2671	</dt>	2444	</dt>
2672	<dd>	2445	<dd>
2673	Not needed - define via --enable-xpm-background.	2446	Not needed - define via --enable-xpm-background.
		2447
		2448
2674	</dd>	2449	</dd>
2675	<p></p></dl>	2450	<p></p></dl>
2676	<p>	2451	<p>
2677	</p>	2452	</p>
2678	<hr />	2453	<hr />
2679	<h1><a name="authors">AUTHORS</a></h1>	2454	<h1><a name="authors">AUTHORS</a></h1>
2680	<p>Marc Lehmann &lt;<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>&gt; converted this document to pod and	2455	<p>Marc Lehmann &lt;<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>&gt; converted this document to pod and
2681	reworked it from the original Rxvt documentation, which was done by Geoff	2456	reworked it from the original Rxvt documentation, which was done by Geoff
2682	Wing &lt;<a href="mailto:gcw@pobox.com">gcw@pobox.com</a>&gt;, who in turn used the XTerm documentation and other	2457	Wing &lt;<a href="mailto:gcw@pobox.com">gcw@pobox.com</a>&gt;, who in turn used the XTerm documentation and other
2683	sources.</p>	2458	sources.
		2459
		2460	</p>
2684		2461
2685	</body>	2462	</body>
2686		2463
2687	</html>	2464	</html>

Diff Legend

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