ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/rxvt-unicode/doc/rxvt.7.man.in

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.54 by root, Sat Jan 28 22:16:58 2006 UTC vs.
Revision 1.62 by root, Tue Jan 31 20:50:48 2006 UTC

…		…
127	.\}	127	.\}
128	.rm #[ #] #H #V #F C	128	.rm #[ #] #H #V #F C
129	.\" ========================================================================	129	.\" ========================================================================
130	.\"	130	.\"
131	.IX Title "rxvt 7"	131	.IX Title "rxvt 7"
132	.TH rxvt 7 "2006-01-28" "7.4" "RXVT-UNICODE"	132	.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE"
133	.SH "NAME"	133	.SH "NAME"
134	RXVT REFERENCE \- FAQ, command sequences and other background information	134	RXVT REFERENCE \- FAQ, command sequences and other background information
135	.SH "SYNOPSIS"	135	.SH "SYNOPSIS"
136	.IX Header "SYNOPSIS"	136	.IX Header "SYNOPSIS"
137	.Vb 2	137	.Vb 2
…		…
151	.SH "DESCRIPTION"	151	.SH "DESCRIPTION"
152	.IX Header "DESCRIPTION"	152	.IX Header "DESCRIPTION"
153	This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting	153	This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting
154	all escape sequences, and other background information.	154	all escape sequences, and other background information.
155	.PP	155	.PP
156	The newest version of this document is	156	The newest version of this document is also available on the World Wide Web at
157	also available on the World Wide Web at
158	<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>.	157	<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>.
159	.SH "FREQUENTLY ASKED QUESTIONS"	158	.SH "FREQUENTLY ASKED QUESTIONS"
160	.IX Header "FREQUENTLY ASKED QUESTIONS"	159	.IX Header "FREQUENTLY ASKED QUESTIONS"
161	.IP "The new selection selects pieces that are too big, how can I select single words?" 4	160	.Sh "Meta, Features & Commandline Issues"
162	.IX Item "The new selection selects pieces that are too big, how can I select single words?"	161	.IX Subsection "Meta, Features & Commandline Issues"
163	Yes. For example, if you want to select alphanumeric words, you can use	162	\fIMy question isn't answered here, can I ask a human?\fR
164	the following resource:	163	.IX Subsection "My question isn't answered here, can I ask a human?"
165	.Sp	164	.PP
		165	Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR,
		166	channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be
		167	interested in learning about new and exciting problems (but not FAQs :).
		168	.PP
		169	\fIDoes it support tabs, can I have a tabbed rxvt\-unicode?\fR
		170	.IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?"
		171	.PP
		172	Beginning with version 7.3, there is a perl extension that implements a
		173	simple tabbed terminal. It is installed by default, so any of these should
		174	give you tabs:
		175	.PP
166	.Vb 1	176	.Vb 1
167	\& URxvt.selection.pattern-0: ([[:word:]]+)	177	\& @@RXVT_NAME@@ -pe tabbed
168	.Ve	178	.Ve
169	.Sp	179	.PP
170	If you click more than twice, the selection will be extended
171	more and more.
172	.Sp
173	To get a selection that is very similar to the old code, try this pattern:
174	.Sp
175	.Vb 1	180	.Vb 1
176	\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+)	181	\& URxvt.perl-ext-common: default,tabbed
177	.Ve	182	.Ve
178	.Sp	183	.PP
179	Please also note that the \fILeftClick Shift-LeftClik\fR combination also	184	It will also work fine with tabbing functionality of many window managers
180	selects words like the old code.	185	or similar tabbing programs, and its embedding-features allow it to be
181	.IP "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 4	186	embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or
182	.IX Item "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"	187	the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt
183	You can disable the perl extension completely by setting the	188	(murxvt) terminal as an example embedding application.
184	\&\fBperl-ext-common\fR resource to the empty string, which also keeps	189	.PP
185	rxvt-unicode from initialising perl, saving memory.	190	\fIHow do I know which rxvt-unicode version I'm using?\fR
186	.Sp	191	.IX Subsection "How do I know which rxvt-unicode version I'm using?"
187	If you only want to disable specific features, you first have to	192	.PP
188	identify which perl extension is responsible. For this, read the section	193	The version number is displayed with the usage (\-h). Also the escape
189	\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For	194	sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When
190	example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify	195	using the @@RXVT_NAME@@c client, the version displayed is that of the
191	this \fBperl-ext-common\fR resource:	196	daemon.
192	.Sp	197	.PP
		198	\fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR
		199	.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
		200	.PP
		201	Rxvt-unicode tries to obey the rule of not charging you for something you
		202	don't use. One thing you should try is to configure out all settings that
		203	you don't need, for example, Xft support is a resource hog by design,
		204	when used. Compiling it out ensures that no Xft font will be loaded
		205	accidentally when rxvt-unicode tries to find a font for your characters.
		206	.PP
		207	Also, many people (me included) like large windows and even larger
		208	scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
		209	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		210	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		211	use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
		212	rxvt-unicode then uses 8 bytes per screen cell.
		213	.PP
		214	\fIHow can I start @@RXVT_NAME@@d in a race-free way?\fR
		215	.IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?"
		216	.PP
		217	Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
		218	display, create the listening socket and then fork.
		219	.PP
		220	\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
		221	.IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
		222	.PP
		223	rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can
		224	check and see if that is set. Note that several programs, \s-1JED\s0, slrn,
		225	Midnight Commander automatically check this variable to decide whether or
		226	not to use color.
		227	.PP
		228	\fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR
		229	.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
		230	.PP
		231	If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
		232	insecure mode then it is possible to use the following shell script
		233	snippets to correctly set the display. If your version of rxvt-unicode
		234	wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then
		235	the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a
		236	regular xterm.
		237	.PP
		238	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		239	snippets:
		240	.PP
193	.Vb 1	241	.Vb 12
194	\& URxvt.perl-ext-common: default,-selection-popup,-option-popup	242	\& # Bourne/Korn/POSIX family of shells:
		243	\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		244	\& if [ ${TERM:-foo} = xterm ]; then
		245	\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		246	\& echo -n '^[Z'
		247	\& read term_id
		248	\& stty icanon echo
		249	\& if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		250	\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		251	\& read DISPLAY # set it in our local shell
		252	\& fi
		253	\& fi
195	.Ve	254	.Ve
196	.Sp	255	.PP
197	This will keep the default extensions, but disable the two popup	256	\fIHow do I compile the manual pages on my own?\fR
198	extensions. Some extensions can also be configured, for example,	257	.IX Subsection "How do I compile the manual pages on my own?"
199	scrollback search mode is triggered by \fBM\-s\fR. You can move it to any	258	.PP
200	other combination either by setting the \fBsearchable-scrollback\fR resource:	259	You need to have a recent version of perl installed as \fI/usr/bin/perl\fR,
201	.Sp	260	one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to
202	.Vb 1	261	the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
203	\& URxvt.searchable-scrollback: CM-s	262	.PP
204	.Ve
205	.IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4	263	\fIIsn't rxvt-unicode supposed to be small? Don't all those features bloat?\fR
206	.IX Item "Isn't rxvt supposed to be small? Don't all those features bloat?"	264	.IX Subsection "Isn't rxvt-unicode supposed to be small? Don't all those features bloat?"
		265	.PP
207	I often get asked about this, and I think, no, they didn't cause extra	266	I often get asked about this, and I think, no, they didn't cause extra
208	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see	267	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
209	that the urxvt binary is larger (due to some encoding tables always being	268	that the urxvt binary is larger (due to some encoding tables always being
210	compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even	269	compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even
211	with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many	270	with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many
212	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are	271	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
213	already in use in this mode.	272	already in use in this mode.
214	.Sp	273	.PP
215	.Vb 3	274	.Vb 3
216	\& text data bss drs rss filename	275	\& text data bss drs rss filename
217	\& 98398 1664 24 15695 1824 rxvt --disable-everything	276	\& 98398 1664 24 15695 1824 rxvt --disable-everything
218	\& 188985 9048 66616 18222 1788 urxvt --disable-everything	277	\& 188985 9048 66616 18222 1788 urxvt --disable-everything
219	.Ve	278	.Ve
220	.Sp	279	.PP
221	When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft	280	When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft
222	and full locale/XIM support which are quite bloaty inside libX11 and my	281	and full locale/XIM support which are quite bloaty inside libX11 and my
223	libc), the two diverge, but not unreasnobaly so.	282	libc), the two diverge, but not unreasnobaly so.
224	.Sp	283	.PP
225	.Vb 3	284	.Vb 3
226	\& text data bss drs rss filename	285	\& text data bss drs rss filename
227	\& 163431 2152 24 20123 2060 rxvt --enable-everything	286	\& 163431 2152 24 20123 2060 rxvt --enable-everything
228	\& 1035683 49680 66648 29096 3680 urxvt --enable-everything	287	\& 1035683 49680 66648 29096 3680 urxvt --enable-everything
229	.Ve	288	.Ve
230	.Sp	289	.PP
231	The very large size of the text section is explained by the east-asian	290	The very large size of the text section is explained by the east-asian
232	encoding tables, which, if unused, take up disk space but nothing else	291	encoding tables, which, if unused, take up disk space but nothing else
233	and can be compiled out unless you rely on X11 core fonts that use those	292	and can be compiled out unless you rely on X11 core fonts that use those
234	encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++	293	encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++
235	compiler allocates (but of course doesn't use unless you are out of	294	compiler allocates (but of course doesn't use unless you are out of
236	memory). Also, using an xft font instead of a core font immediately adds a	295	memory). Also, using an xft font instead of a core font immediately adds a
237	few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when	296	few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when
238	not used.	297	not used.
239	.Sp	298	.PP
240	Of course, due to every character using two or four bytes instead of one,	299	Of course, due to every character using two or four bytes instead of one,
241	a large scrollback buffer will ultimately make rxvt-unicode use more	300	a large scrollback buffer will ultimately make rxvt-unicode use more
242	memory.	301	memory.
243	.Sp	302	.PP
244	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this	303	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
245	still fares rather well. And compared to some monsters like gnome-terminal	304	still fares rather well. And compared to some monsters like gnome-terminal
246	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	305	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
247	43180k in daemons that stay around after exit, plus half a minute of	306	43180k in daemons that stay around after exit, plus half a minute of
248	startup time, including the hundreds of warnings it spits out), it fares	307	startup time, including the hundreds of warnings it spits out), it fares
249	extremely well *g*.	308	extremely well *g*.
		309	.PP
250	.IP "Why \*(C+, isn't that unportable/bloated/uncool?" 4	310	\fIWhy \*(C+, isn't that unportable/bloated/uncool?\fR
251	.IX Item "Why , isn't that unportable/bloated/uncool?"	311	.IX Subsection "Why , isn't that unportable/bloated/uncool?"
		312	.PP
252	Is this a question? :) It comes up very often. The simple answer is: I had	313	Is this a question? :) It comes up very often. The simple answer is: I had
253	to write it, and \*(C+ allowed me to write and maintain it in a fraction	314	to write it, and \*(C+ allowed me to write and maintain it in a fraction
254	of the time and effort (which is a scarce resource for me). Put even	315	of the time and effort (which is a scarce resource for me). Put even
255	shorter: It simply wouldn't exist without \*(C+.	316	shorter: It simply wouldn't exist without \*(C+.
256	.Sp	317	.PP
257	My personal stance on this is that \*(C+ is less portable than C, but in	318	My personal stance on this is that \*(C+ is less portable than C, but in
258	the case of rxvt-unicode this hardly matters, as its portability limits	319	the case of rxvt-unicode this hardly matters, as its portability limits
259	are defined by things like X11, pseudo terminals, locale support and unix	320	are defined by things like X11, pseudo terminals, locale support and unix
260	domain sockets, which are all less portable than \*(C+ itself.	321	domain sockets, which are all less portable than \*(C+ itself.
261	.Sp	322	.PP
262	Regarding the bloat, see the above question: It's easy to write programs	323	Regarding the bloat, see the above question: It's easy to write programs
263	in C that use gobs of memory, an certainly possible to write programs in	324	in C that use gobs of memory, an certainly possible to write programs in
264	\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is	325	\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is
265	not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my	326	not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my
266	system with a minimal config:	327	system with a minimal config:
267	.Sp	328	.PP
268	.Vb 4	329	.Vb 4
269	\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	330	\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
270	\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)	331	\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
271	\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)	332	\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
272	\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	333	\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
273	.Ve	334	.Ve
274	.Sp	335	.PP
275	And here is rxvt\-unicode:	336	And here is rxvt\-unicode:
276	.Sp	337	.PP
277	.Vb 5	338	.Vb 5
278	\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	339	\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
279	\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)	340	\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
280	\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)	341	\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
281	\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)	342	\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
282	\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	343	\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
283	.Ve	344	.Ve
284	.Sp	345	.PP
285	No large bloated libraries (of course, none were linked in statically),	346	No large bloated libraries (of course, none were linked in statically),
286	except maybe libX11 :)	347	except maybe libX11 :)
287	.IP "Does it support tabs, can I have a tabbed rxvt\-unicode?" 4	348	.Sh "Rendering, Font & Look and Feel Issues"
288	.IX Item "Does it support tabs, can I have a tabbed rxvt-unicode?"	349	.IX Subsection "Rendering, Font & Look and Feel Issues"
289	Beginning with version 7.3, there is a perl extension that implements a	350	\fII can't get transparency working, what am I doing wrong?\fR
290	simple tabbed terminal. It is installed by default, so any of these should	351	.IX Subsection "I can't get transparency working, what am I doing wrong?"
291	give you tabs:	352	.PP
292	.Sp	353	First of all, transparency isn't officially supported in rxvt\-unicode, so
		354	you are mostly on your own. Do not bug the author about it (but you may
		355	bug everybody else). Also, if you can't get it working consider it a rite
		356	of passage: ... and you failed.
		357	.PP
		358	Here are four ways to get transparency. \fBDo\fR read the manpage and option
		359	descriptions for the programs mentioned and rxvt\-unicode. Really, do it!
		360	.PP
		361	1. Use inheritPixmap:
		362	.PP
		363	.Vb 2
		364	\& Esetroot wallpaper.jpg
		365	\& @@RXVT_NAME@@ -ip -tint red -sh 40
		366	.Ve
		367	.PP
		368	That works. If you think it doesn't, you lack transparency and tinting
		369	support, or you are unable to read.
		370	.PP
		371	2. Use a simple pixmap and emulate pseudo\-transparency. This enables you
		372	to use effects other than tinting and shading: Just shade/tint/whatever
		373	your picture with gimp or any other tool:
		374	.PP
		375	.Vb 2
		376	\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		377	\& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background
		378	.Ve
		379	.PP
		380	That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you
		381	are unable to read.
		382	.PP
		383	3. Use an \s-1ARGB\s0 visual:
		384	.PP
293	.Vb 1	385	.Vb 1
294	\& @@RXVT_NAME@@ -pe tabbed	386	\& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
295	.Ve	387	.Ve
296	.Sp	388	.PP
		389	This requires \s-1XFT\s0 support, and the support of your X\-server. If that
		390	doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
		391	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		392	bugfixes and workarounds for Xft and Xlib to make it work, but that
		393	doesn't mean that your \s-1WM\s0 has the required kludges in place.
		394	.PP
		395	4. Use xcompmgr and let it do the job:
		396	.PP
		397	.Vb 2
		398	\& xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e
		399	\& -set _NET_WM_WINDOW_OPACITY 0xc0000000
		400	.Ve
		401	.PP
		402	Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
		403	by other values to change the degree of opacity. If it doesn't work and
		404	your server crashes, you got to keep the pieces.
		405	.PP
		406	\fIWhy do some chinese characters look so different than others?\fR
		407	.IX Subsection "Why do some chinese characters look so different than others?"
		408	.PP
		409	This is because there is a difference between script and language \*(--
		410	rxvt-unicode does not know which language the text that is output is,
		411	as it only knows the unicode character codes. If rxvt-unicode first
		412	sees a japanese/chinese character, it might choose a japanese font for
		413	display. Subsequent japanese characters will use that font. Now, many
		414	chinese characters aren't represented in japanese fonts, so when the first
		415	non-japanese character comes up, rxvt-unicode will look for a chinese font
		416	\&\*(-- unfortunately at this point, it will still use the japanese font for
		417	chinese characters that are also in the japanese font.
		418	.PP
		419	The workaround is easy: just tag a chinese font at the end of your font
		420	list (see the previous question). The key is to view the font list as
		421	a preference list: If you expect more japanese, list a japanese font
		422	first. If you expect more chinese, put a chinese font first.
		423	.PP
		424	In the future it might be possible to switch language preferences at
		425	runtime (the internal data structure has no problem with using different
		426	fonts for the same character at the same time, but no interface for this
		427	has been designed yet).
		428	.PP
		429	Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
		430	.PP
		431	\fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR
		432	.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
		433	.PP
		434	Most fonts were not designed for terminal use, which means that character
		435	size varies a lot. A font that is otherwise fine for terminal use might
		436	contain some characters that are simply too wide. Rxvt-unicode will avoid
		437	these characters. For characters that are just \*(L"a bit\*(R" too wide a special
		438	\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
		439	.PP
		440	All of this requires that fonts do not lie about character sizes,
		441	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		442	box, and rxvt-unicode has no way of detecting this (the correct way is to
		443	ask for the character bounding box, which unfortunately is wrong in these
		444	cases).
		445	.PP
		446	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		447	or the respective font. If you encounter this problem you might try using
		448	the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
		449	might be forced to use a different font.
		450	.PP
		451	All of this is not a problem when using X11 core fonts, as their bounding
		452	box data is correct.
		453	.PP
		454	\fIHow can I keep rxvt-unicode from using reverse video so much?\fR
		455	.IX Subsection "How can I keep rxvt-unicode from using reverse video so much?"
		456	.PP
		457	First of all, make sure you are running with the right terminal settings
		458	(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
		459	make sure you have specified colours for italic and bold, as otherwise
		460	rxvt-unicode might use reverse video to simulate the effect:
		461	.PP
		462	.Vb 2
		463	\& URxvt.colorBD: white
		464	\& URxvt.colorIT: green
		465	.Ve
		466	.PP
		467	\fISome programs assume totally weird colours (red instead of blue), how can I fix that?\fR
		468	.IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
		469	.PP
		470	For some unexplainable reason, some rare programs assume a very weird
		471	colour palette when confronted with a terminal with more than the standard
		472	8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
		473	these programs not to assume non-ISO colours without very good reasons.
		474	.PP
		475	In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
		476	definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
		477	fix colours but keep you from using other rxvt-unicode features.
		478	.PP
		479	\fICan I switch the fonts at runtime?\fR
		480	.IX Subsection "Can I switch the fonts at runtime?"
		481	.PP
		482	Yes, using an escape sequence. Try something like this, which has the same
		483	effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
		484	.PP
297	.Vb 1	485	.Vb 1
		486	\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
		487	.Ve
		488	.PP
		489	This is useful if you e.g. work primarily with japanese (and prefer a
		490	japanese font), but you have to switch to chinese temporarily, where
		491	japanese fonts would only be in your way.
		492	.PP
		493	You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
		494	.PP
		495	\fIWhy do italic characters look as if clipped?\fR
		496	.IX Subsection "Why do italic characters look as if clipped?"
		497	.PP
		498	Many fonts have difficulties with italic characters and hinting. For
		499	example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
		500	Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
		501	enable freetype autohinting, i.e. like this:
		502	.PP
		503	.Vb 2
		504	\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		505	\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		506	.Ve
		507	.PP
		508	\fICan I speed up Xft rendering somehow?\fR
		509	.IX Subsection "Can I speed up Xft rendering somehow?"
		510	.PP
		511	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		512	it is simply slow. If you still want Xft fonts you might try to disable
		513	antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
		514	memory and also speeds up rendering considerably.
		515	.PP
		516	\fIRxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?\fR
		517	.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
		518	.PP
		519	Rxvt-unicode will use whatever you specify as a font. If it needs to
		520	fall back to it's default font search list it will prefer X11 core
		521	fonts, because they are small and fast, and then use Xft fonts. It has
		522	antialiasing disabled for most of them, because the author thinks they
		523	look best that way.
		524	.PP
		525	If you want antialiasing, you have to specify the fonts manually.
		526	.PP
		527	\fIWhat's with this bold/blink stuff?\fR
		528	.IX Subsection "What's with this bold/blink stuff?"
		529	.PP
		530	If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
		531	standard foreground colour.
		532	.PP
		533	For the standard background colour, blinking will actually make the
		534	text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
		535	colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
		536	ignored.
		537	.PP
		538	On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
		539	foreground/background colors.
		540	.PP
		541	color0\-7 are the low-intensity colors.
		542	.PP
		543	color8\-15 are the corresponding high-intensity colors.
		544	.PP
		545	\fII don't like the screen colors. How do I change them?\fR
		546	.IX Subsection "I don't like the screen colors. How do I change them?"
		547	.PP
		548	You can change the screen colors at run-time using \fI~/.Xdefaults\fR
		549	resources (or as long\-options).
		550	.PP
		551	Here are values that are supposed to resemble a \s-1VGA\s0 screen,
		552	including the murky brown that passes for low-intensity yellow:
		553	.PP
		554	.Vb 8
		555	\& URxvt.color0: #000000
		556	\& URxvt.color1: #A80000
		557	\& URxvt.color2: #00A800
		558	\& URxvt.color3: #A8A800
		559	\& URxvt.color4: #0000A8
		560	\& URxvt.color5: #A800A8
		561	\& URxvt.color6: #00A8A8
		562	\& URxvt.color7: #A8A8A8
		563	.Ve
		564	.PP
		565	.Vb 8
		566	\& URxvt.color8: #000054
		567	\& URxvt.color9: #FF0054
		568	\& URxvt.color10: #00FF54
		569	\& URxvt.color11: #FFFF54
		570	\& URxvt.color12: #0000FF
		571	\& URxvt.color13: #FF00FF
		572	\& URxvt.color14: #00FFFF
		573	\& URxvt.color15: #FFFFFF
		574	.Ve
		575	.PP
		576	And here is a more complete set of non-standard colors described (not by
		577	me) as \*(L"pretty girly\*(R".
		578	.PP
		579	.Vb 18
		580	\& URxvt.cursorColor: #dc74d1
		581	\& URxvt.pointerColor: #dc74d1
		582	\& URxvt.background: #0e0e0e
		583	\& URxvt.foreground: #4ad5e1
		584	\& URxvt.color0: #000000
		585	\& URxvt.color8: #8b8f93
		586	\& URxvt.color1: #dc74d1
		587	\& URxvt.color9: #dc74d1
		588	\& URxvt.color2: #0eb8c7
		589	\& URxvt.color10: #0eb8c7
		590	\& URxvt.color3: #dfe37e
		591	\& URxvt.color11: #dfe37e
		592	\& URxvt.color5: #9e88f0
		593	\& URxvt.color13: #9e88f0
		594	\& URxvt.color6: #73f7ff
		595	\& URxvt.color14: #73f7ff
		596	\& URxvt.color7: #e1dddd
		597	\& URxvt.color15: #e1dddd
		598	.Ve
		599	.PP
		600	\fIWhy do some characters look so much different than others?\fR
		601	.IX Subsection "Why do some characters look so much different than others?"
		602	.PP
		603	See next entry.
		604	.PP
		605	\fIHow does rxvt-unicode choose fonts?\fR
		606	.IX Subsection "How does rxvt-unicode choose fonts?"
		607	.PP
		608	Most fonts do not contain the full range of Unicode, which is
		609	fine. Chances are that the font you (or the admin/package maintainer of
		610	your system/os) have specified does not cover all the characters you want
		611	to display.
		612	.PP
		613	\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement
		614	font. Often the result is fine, but sometimes the chosen font looks
		615	bad/ugly/wrong. Some fonts have totally strange characters that don't
		616	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		617	intelligence to detect that a specific glyph is wrong: it has to believe
		618	the font that the characters it claims to contain indeed look correct.
		619	.PP
		620	In that case, select a font of your taste and add it to the font list,
		621	e.g.:
		622	.PP
		623	.Vb 1
		624	\& @@RXVT_NAME@@ -fn basefont,font2,font3...
		625	.Ve
		626	.PP
		627	When rxvt-unicode sees a character, it will first look at the base
		628	font. If the base font does not contain the character, it will go to the
		629	next font, and so on. Specifying your own fonts will also speed up this
		630	search and use less resources within rxvt-unicode and the X\-server.
		631	.PP
		632	The only limitation is that none of the fonts may be larger than the base
		633	font, as the base font defines the terminal character cell size, which
		634	must be the same due to the way terminals work.
		635	.Sh "Keyboard, Mouse & User Interaction"
		636	.IX Subsection "Keyboard, Mouse & User Interaction"
		637	\fIThe new selection selects pieces that are too big, how can I select single words?\fR
		638	.IX Subsection "The new selection selects pieces that are too big, how can I select single words?"
		639	.PP
		640	If you want to select e.g. alphanumeric words, you can use the following
		641	setting:
		642	.PP
		643	.Vb 1
		644	\& URxvt.selection.pattern-0: ([[:word:]]+)
		645	.Ve
		646	.PP
		647	If you click more than twice, the selection will be extended
		648	more and more.
		649	.PP
		650	To get a selection that is very similar to the old code, try this pattern:
		651	.PP
		652	.Vb 1
		653	\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+)
		654	.Ve
		655	.PP
		656	Please also note that the \fILeftClick Shift-LeftClik\fR combination also
		657	selects words like the old code.
		658	.PP
		659	\fII don't like the new selection/popups/hotkeys/perl, how do I change/disable it?\fR
		660	.IX Subsection "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"
		661	.PP
		662	You can disable the perl extension completely by setting the
		663	\&\fBperl-ext-common\fR resource to the empty string, which also keeps
		664	rxvt-unicode from initialising perl, saving memory.
		665	.PP
		666	If you only want to disable specific features, you first have to
		667	identify which perl extension is responsible. For this, read the section
		668	\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For
		669	example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify
		670	this \fBperl-ext-common\fR resource:
		671	.PP
		672	.Vb 1
		673	\& URxvt.perl-ext-common: default,-selection-popup,-option-popup
		674	.Ve
		675	.PP
		676	This will keep the default extensions, but disable the two popup
		677	extensions. Some extensions can also be configured, for example,
		678	scrollback search mode is triggered by \fBM\-s\fR. You can move it to any
		679	other combination either by setting the \fBsearchable-scrollback\fR resource:
		680	.PP
		681	.Vb 1
		682	\& URxvt.searchable-scrollback: CM-s
		683	.Ve
		684	.PP
		685	\fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR
		686	.IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?"
		687	.PP
		688	See next entry.
		689	.PP
		690	\fIDuring rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?\fR
		691	.IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
		692	.PP
		693	These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal
		694	circumstances, it will move your cursor around when you click into the
		695	line that contains it. It tries hard not to do this at the wrong moment,
		696	but when running a program that doesn't parse cursor movements or in some
		697	cases during rlogin sessions, it fails to detect this properly.
		698	.PP
		699	You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
		700	extension:
		701	.PP
		702	.Vb 1
298	\& URxvt.perl-ext-common: default,tabbed	703	\& URxvt.perl-ext-common: default,-readline
299	.Ve	704	.Ve
300	.Sp	705	.PP
301	It will also work fine with tabbing functionality of many window managers	706	\fIMy numerical keypad acts weird and generates differing output?\fR
302	or similar tabbing programs, and its embedding-features allow it to be	707	.IX Subsection "My numerical keypad acts weird and generates differing output?"
303	embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or	708	.PP
304	the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt	709	Some Debian GNUL/Linux users seem to have this problem, although no
305	(murxvt) terminal as an example embedding application.	710	specific details were reported so far. It is possible that this is caused
306	.IP "How do I know which rxvt-unicode version I'm using?" 4	711	by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
307	.IX Item "How do I know which rxvt-unicode version I'm using?"	712	this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
308	The version number is displayed with the usage (\-h). Also the escape	713	keymap. See the answer to the previous question, and please report if that
309	sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When	714	helped.
310	using the @@RXVT_NAME@@c client, the version displayed is that of the	715	.PP
311	daemon.	716	\fIMy Compose (Multi_key) key is no longer working.\fR
312	.IP "I am using Debian GNU/Linux and have a problem..." 4	717	.IX Subsection "My Compose (Multi_key) key is no longer working."
313	.IX Item "I am using Debian GNU/Linux and have a problem..."	718	.PP
314	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	719	The most common causes for this are that either your locale is not set
315	patches that considerably change the behaviour of rxvt-unicode (but	720	correctly, or you specified a \fBpreeditStyle\fR that is not supported by
316	unfortunately this notice has been removed). Before reporting a bug to	721	your input method. For example, if you specified \fBOverTheSpot\fR and
317	the original rxvt-unicode author please download and install the genuine	722	your input method (e.g. the default input method handling Compose keys)
318	version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce	723	does not support this (for instance because it is not visual), then
319	the problem. If you cannot, chances are that the problems are specific to	724	rxvt-unicode will continue without an input method.
320	Debian GNU/Linux, in which case it should be reported via the Debian Bug	725	.PP
321	Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).	726	In this case either do not specify a \fBpreeditStyle\fR or specify more than
322	.Sp	727	one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
323	For other problems that also affect the Debian package, you can and	728	.PP
324	probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a	729	\fII cannot type \f(CI\*(C`Ctrl\-Shift\-2\*(C'\fI to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755\fR
325	bug in the Debian version and it serves as a reminder for other users that	730	.IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
326	might encounter the same issue.	731	.PP
327	.IP "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" 4	732	Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
328	.IX Item "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"	733	international keyboards) or simply use \s-1ISO\s0 14755 support to your
329	You should build one binary with the default options. \fIconfigure\fR	734	advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
330	now enables most useful options, and the trend goes to making them	735	codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
331	runtime\-switchable, too, so there is usually no drawback to enbaling them,	736	character and so on.
332	except higher disk and possibly memory usage. The perl interpreter should	737	.PP
333	be enabled, as important functionality (menus, selection, likely more in	738	\fIMouse cut/paste suddenly no longer works.\fR
334	the future) depends on it.	739	.IX Subsection "Mouse cut/paste suddenly no longer works."
335	.Sp	740	.PP
336	You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources	741	Make sure that mouse reporting is actually turned off since killing
337	system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful	742	some editors prematurely may leave the mouse in mouse report mode. I've
338	behaviour. If your distribution aims at low memory, add an empty	743	heard that tcsh may use mouse reporting unless it otherwise specified. A
339	\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the	744	quick check is to see if cut/paste works when the Alt or Shift keys are
340	perl interpreter disabled until the user enables it.	745	depressed.
341	.Sp	746	.PP
342	If you can/want build more binaries, I recommend building a minimal	747	\fIWhat's with the strange Backspace/Delete key behaviour?\fR
343	one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with	748	.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
344	\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of	749	.PP
345	encodings built-in that increase download times and are rarely used).	750	Assuming that the physical Backspace key corresponds to the
346	.IP "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" 4	751	BackSpace keysym (not likely for Linux ... see the following
347	.IX Item "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?"	752	question) there are two standard values that can be used for
348	It should be, starting with release 7.1. You are encouraged to properly	753	Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
349	install urxvt with privileges necessary for your \s-1OS\s0 now.	754	.PP
350	.Sp	755	Historically, either value is correct, but rxvt-unicode adopts the debian
351	When rxvt-unicode detects that it runs setuid or setgid, it will fork	756	policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
352	into a helper process for privileged operations (pty handling on some	757	choice :).
353	systems, utmp/wtmp/lastlog handling on others) and drop privileges	758	.PP
354	immediately. This is much safer than most other terminals that keep	759	Rxvt-unicode tries to inherit the current stty settings and uses the value
355	privileges while running (but is more relevant to urxvt, as it contains	760	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
356	things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).	761	started from a terminal (say, from a menu or by remote shell), then the
357	.Sp	762	system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
358	This forking is done as the very first within \fImain()\fR, which is very early	763	be used (which may not be the same as your stty setting).
359	and reduces possible bugs to initialisation code run before \fImain()\fR, or	764	.PP
360	things like the dynamic loader of your system, which should result in very	765	For starting a new rxvt\-unicode:
361	little risk.	766	.PP
		767	.Vb 3
		768	\& # use Backspace = ^H
		769	\& $ stty erase ^H
		770	\& $ @@RXVT_NAME@@
		771	.Ve
		772	.PP
		773	.Vb 3
		774	\& # use Backspace = ^?
		775	\& $ stty erase ^?
		776	\& $ @@RXVT_NAME@@
		777	.Ve
		778	.PP
		779	Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
		780	.PP
		781	For an existing rxvt\-unicode:
		782	.PP
		783	.Vb 3
		784	\& # use Backspace = ^H
		785	\& $ stty erase ^H
		786	\& $ echo -n "^[[36h"
		787	.Ve
		788	.PP
		789	.Vb 3
		790	\& # use Backspace = ^?
		791	\& $ stty erase ^?
		792	\& $ echo -n "^[[36l"
		793	.Ve
		794	.PP
		795	This helps satisfy some of the Backspace discrepancies that occur, but
		796	if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
		797	properly reflects that.
		798	.PP
		799	The Delete key is a another casualty of the ill-defined Backspace problem.
		800	To avoid confusion between the Backspace and Delete keys, the Delete
		801	key has been assigned an escape sequence to match the vt100 for Execute
		802	(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
		803	.PP
		804	Some other Backspace problems:
		805	.PP
		806	some editors use termcap/terminfo,
		807	some editors (vim I'm told) expect Backspace = ^H,
		808	\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
		809	.PP
		810	Perhaps someday this will all be resolved in a consistent manner.
		811	.PP
		812	\fII don't like the key\-bindings. How do I change them?\fR
		813	.IX Subsection "I don't like the key-bindings. How do I change them?"
		814	.PP
		815	There are some compile-time selections available via configure. Unless
		816	you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
		817	use the `keysym' resource to alter the keystrings associated with keysyms.
		818	.PP
		819	Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR
		820	.PP
		821	.Vb 20
		822	\& URxvt.keysym.Home: \e033[1~
		823	\& URxvt.keysym.End: \e033[4~
		824	\& URxvt.keysym.C-apostrophe: \e033<C-'>
		825	\& URxvt.keysym.C-slash: \e033<C-/>
		826	\& URxvt.keysym.C-semicolon: \e033<C-;>
		827	\& URxvt.keysym.C-grave: \e033<C-`>
		828	\& URxvt.keysym.C-comma: \e033<C-,>
		829	\& URxvt.keysym.C-period: \e033<C-.>
		830	\& URxvt.keysym.C-0x60: \e033<C-`>
		831	\& URxvt.keysym.C-Tab: \e033<C-Tab>
		832	\& URxvt.keysym.C-Return: \e033<C-Return>
		833	\& URxvt.keysym.S-Return: \e033<S-Return>
		834	\& URxvt.keysym.S-space: \e033<S-Space>
		835	\& URxvt.keysym.M-Up: \e033<M-Up>
		836	\& URxvt.keysym.M-Down: \e033<M-Down>
		837	\& URxvt.keysym.M-Left: \e033<M-Left>
		838	\& URxvt.keysym.M-Right: \e033<M-Right>
		839	\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 >
		840	\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
		841	\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
		842	.Ve
		843	.PP
		844	See some more examples in the documentation for the \fBkeysym\fR resource.
		845	.PP
		846	\fII'm using keyboard model \s-1XXX\s0 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\fR
		847	.IX Subsection "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"
		848	.PP
		849	.Vb 6
		850	\& KP_Insert == Insert
		851	\& F22 == Print
		852	\& F27 == Home
		853	\& F29 == Prior
		854	\& F33 == End
		855	\& F35 == Next
		856	.Ve
		857	.PP
		858	Rather than have rxvt-unicode try to accommodate all the various possible
		859	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		860	required for your particular machine.
		861	.Sh "Terminal Configuration"
		862	.IX Subsection "Terminal Configuration"
		863	\fIWhy doesn't rxvt-unicode read my resources?\fR
		864	.IX Subsection "Why doesn't rxvt-unicode read my resources?"
		865	.PP
		866	Well, why, indeed? It does, in a way very similar to other X
		867	applications. Most importantly, this means that if you or your \s-1OS\s0 loads
		868	resources into the X display (the right way to do it), rxvt-unicode will
		869	ignore any resource files in your home directory. It will only read
		870	\&\fI$HOME/.Xdefaults\fR when no resources are attached to the display.
		871	.PP
		872	If you have or use an \fI$HOME/.Xresources\fR file, chances are that
		873	resources are loaded into your X\-server. In this case, you have to
		874	re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR).
		875	.PP
		876	Also consider the form resources have to use:
		877	.PP
		878	.Vb 1
		879	\& URxvt.resource: value
		880	.Ve
		881	.PP
		882	If you want to use another form (there are lots of different ways of
		883	specifying resources), make sure you understand wether and why it
		884	works. If unsure, use the form above.
		885	.PP
362	.IP "When I log-in to another system it tells me about missing terminfo data?" 4	886	\fIWhen I log-in to another system it tells me about missing terminfo data?\fR
363	.IX Item "When I log-in to another system it tells me about missing terminfo data?"	887	.IX Subsection "When I log-in to another system it tells me about missing terminfo data?"
		888	.PP
364	The terminal description used by rxvt-unicode is not as widely available	889	The terminal description used by rxvt-unicode is not as widely available
365	as that for xterm, or even rxvt (for which the same problem often arises).	890	as that for xterm, or even rxvt (for which the same problem often arises).
366	.Sp	891	.PP
367	The correct solution for this problem is to install the terminfo, this can	892	The correct solution for this problem is to install the terminfo, this can
368	be done like this (with ncurses' infocmp):	893	be done like this (with ncurses' infocmp):
369	.Sp	894	.PP
370	.Vb 2	895	.Vb 2
371	\& REMOTE=remotesystem.domain	896	\& REMOTE=remotesystem.domain
372	\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	897	\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
373	.Ve	898	.Ve
374	.Sp	899	.PP
375	\&... or by installing rxvt-unicode normally on the remote system,	900	\&... or by installing rxvt-unicode normally on the remote system,
376	.Sp	901	.PP
377	If you cannot or do not want to do this, then you can simply set	902	If you cannot or do not want to do this, then you can simply set
378	\&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of	903	\&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of
379	problems arising, which includes wrong keymapping, less and different	904	problems arising, which includes wrong keymapping, less and different
380	colours and some refresh errors in fullscreen applications. It's a nice	905	colours and some refresh errors in fullscreen applications. It's a nice
381	quick-and-dirty workaround for rare cases, though.	906	quick-and-dirty workaround for rare cases, though.
382	.Sp	907	.PP
383	If you always want to do this (and are fine with the consequences) you	908	If you always want to do this (and are fine with the consequences) you
384	can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a	909	can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a
385	resource to set it:	910	resource to set it:
386	.Sp	911	.PP
387	.Vb 1	912	.Vb 1
388	\& URxvt.termName: rxvt	913	\& URxvt.termName: rxvt
389	.Ve	914	.Ve
390	.Sp	915	.PP
391	If you don't plan to use \fBrxvt\fR (quite common...) you could also replace	916	If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
392	the rxvt terminfo file with the rxvt-unicode one.	917	the rxvt terminfo file with the rxvt-unicode one.
393	.ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4	918	.PP
394	.el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4	919	\fI\f(CI\*(C`tic\*(C'\fI outputs some error when compiling the terminfo entry.\fR
395	.IX Item "tic outputs some error when compiling the terminfo entry."	920	.IX Subsection "tic outputs some error when compiling the terminfo entry."
		921	.PP
396	Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by	922	Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
397	\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.	923	\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
398	.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4	924	.PP
399	.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4	925	\fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@RXVT_NAME@@.\fR
400	.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@."	926	.IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@."
401	.PD 0	927	.PP
		928	See next entry.
		929	.PP
402	.IP "I need a termcap file entry." 4	930	\fII need a termcap file entry.\fR
403	.IX Item "I need a termcap file entry."	931	.IX Subsection "I need a termcap file entry."
404	.PD	932	.PP
405	One reason you might want this is that some distributions or operating	933	One reason you might want this is that some distributions or operating
406	systems still compile some programs using the long-obsoleted termcap	934	systems still compile some programs using the long-obsoleted termcap
407	library (Fedora Core's bash is one example) and rely on a termcap entry	935	library (Fedora Core's bash is one example) and rely on a termcap entry
408	for \f(CW\*(C`rxvt\-unicode\*(C'\fR.	936	for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
409	.Sp	937	.PP
410	You could use rxvt's termcap entry with resonable results in many cases.	938	You could use rxvt's termcap entry with resonable results in many cases.
411	You can also create a termcap entry by using terminfo's infocmp program	939	You can also create a termcap entry by using terminfo's infocmp program
412	like this:	940	like this:
413	.Sp	941	.PP
414	.Vb 1	942	.Vb 1
415	\& infocmp -C rxvt-unicode	943	\& infocmp -C rxvt-unicode
416	.Ve	944	.Ve
417	.Sp	945	.PP
418	Or you could use this termcap entry, generated by the command above:	946	Or you could use this termcap entry, generated by the command above:
419	.Sp	947	.PP
420	.Vb 20	948	.Vb 20
421	\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e	949	\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e
422	\& :am:bw:eo:km:mi:ms:xn:xo:\e	950	\& :am:bw:eo:km:mi:ms:xn:xo:\e
423	\& :co#80:it#8:li#24:lm#0:\e	951	\& :co#80:it#8:li#24:lm#0:\e
424	\& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e	952	\& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e
…		…
437	\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e	965	\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e
438	\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e	966	\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e
439	\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e	967	\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e
440	\& :vs=\eE[?25h:	968	\& :vs=\eE[?25h:
441	.Ve	969	.Ve
442	.ie n .IP "Why does ""ls"" no longer have coloured output?" 4	970	.PP
443	.el .IP "Why does \f(CWls\fR no longer have coloured output?" 4	971	\fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR
444	.IX Item "Why does ls no longer have coloured output?"	972	.IX Subsection "Why does ls no longer have coloured output?"
		973	.PP
445	The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to	974	The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
446	decide wether a terminal has colour, but uses it's own configuration	975	decide wether a terminal has colour, but uses it's own configuration
447	file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among	976	file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among
448	with most other terminals supporting colour). Either add:	977	with most other terminals supporting colour). Either add:
449	.Sp	978	.PP
450	.Vb 1	979	.Vb 1
451	\& TERM rxvt-unicode	980	\& TERM rxvt-unicode
452	.Ve	981	.Ve
453	.Sp	982	.PP
454	to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:	983	to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
455	.Sp	984	.PP
456	.Vb 1	985	.Vb 1
457	\& alias ls='ls --color=auto'	986	\& alias ls='ls --color=auto'
458	.Ve	987	.Ve
459	.Sp	988	.PP
460	to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.	989	to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
		990	.PP
461	.IP "Why doesn't vim/emacs etc. use the 88 colour mode?" 4	991	\fIWhy doesn't vim/emacs etc. use the 88 colour mode?\fR
462	.IX Item "Why doesn't vim/emacs etc. use the 88 colour mode?"	992	.IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?"
463	.PD 0	993	.PP
		994	See next entry.
		995	.PP
464	.IP "Why doesn't vim/emacs etc. make use of italic?" 4	996	\fIWhy doesn't vim/emacs etc. make use of italic?\fR
465	.IX Item "Why doesn't vim/emacs etc. make use of italic?"	997	.IX Subsection "Why doesn't vim/emacs etc. make use of italic?"
		998	.PP
		999	See next entry.
		1000	.PP
466	.IP "Why are the secondary screen-related options not working properly?" 4	1001	\fIWhy are the secondary screen-related options not working properly?\fR
467	.IX Item "Why are the secondary screen-related options not working properly?"	1002	.IX Subsection "Why are the secondary screen-related options not working properly?"
468	.PD	1003	.PP
469	Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged	1004	Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged
470	distributions (most notably Debian GNU/Linux) break rxvt-unicode	1005	distributions (most notably Debian GNU/Linux) break rxvt-unicode
471	by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra	1006	by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra
472	features. Unfortunately, some of these (most notably, again, Debian	1007	features. Unfortunately, some of these (most notably, again, Debian
473	GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo	1008	GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
474	file, so you will need to install it on your own (See the question \fBWhen	1009	file, so you will need to install it on your own (See the question \fBWhen
475	I log-in to another system it tells me about missing terminfo data?\fR on	1010	I log-in to another system it tells me about missing terminfo data?\fR on
476	how to do this).	1011	how to do this).
477	.IP "My numerical keypad acts weird and generates differing output?" 4	1012	.Sh "Encoding / Locale / Input Method Issues"
478	.IX Item "My numerical keypad acts weird and generates differing output?"	1013	.IX Subsection "Encoding / Locale / Input Method Issues"
479	Some Debian GNUL/Linux users seem to have this problem, although no
480	specific details were reported so far. It is possible that this is caused
481	by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
482	this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
483	keymap. See the answer to the previous question, and please report if that
484	helped.
485	.IP "Rxvt-unicode does not seem to understand the selected encoding?" 4	1014	\fIRxvt-unicode does not seem to understand the selected encoding?\fR
486	.IX Item "Rxvt-unicode does not seem to understand the selected encoding?"	1015	.IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?"
487	.PD 0	1016	.PP
		1017	See next entry.
		1018	.PP
488	.IP "Unicode does not seem to work?" 4	1019	\fIUnicode does not seem to work?\fR
489	.IX Item "Unicode does not seem to work?"	1020	.IX Subsection "Unicode does not seem to work?"
490	.PD	1021	.PP
491	If you encounter strange problems like typing an accented character but	1022	If you encounter strange problems like typing an accented character but
492	getting two unrelated other characters or similar, or if program output is	1023	getting two unrelated other characters or similar, or if program output is
493	subtly garbled, then you should check your locale settings.	1024	subtly garbled, then you should check your locale settings.
494	.Sp	1025	.PP
495	Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the	1026	Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the
496	programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the	1027	programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the
497	login script running within the rxvt-unicode window changes the locale to	1028	login script running within the rxvt-unicode window changes the locale to
498	something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work.	1029	something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work.
499	.Sp	1030	.PP
500	The best thing is to fix your startup environment, as you will likely run	1031	The best thing is to fix your startup environment, as you will likely run
501	into other problems. If nothing works you can try this in your .profile.	1032	into other problems. If nothing works you can try this in your .profile.
502	.Sp	1033	.PP
503	.Vb 1	1034	.Vb 1
504	\& printf '\ee]701;%s\e007' "$LC_CTYPE"	1035	\& printf '\ee]701;%s\e007' "$LC_CTYPE"
505	.Ve	1036	.Ve
506	.Sp	1037	.PP
507	If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not	1038	If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not
508	supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which	1039	supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which
509	displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as	1040	displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as
510	it will complain loudly if it cannot set the locale). If it displays something	1041	it will complain loudly if it cannot set the locale). If it displays something
511	like:	1042	like:
512	.Sp	1043	.PP
513	.Vb 1	1044	.Vb 1
514	\& locale: Cannot set LC_CTYPE to default locale: ...	1045	\& locale: Cannot set LC_CTYPE to default locale: ...
515	.Ve	1046	.Ve
516	.Sp	1047	.PP
517	Then the locale you specified is not supported on your system.	1048	Then the locale you specified is not supported on your system.
518	.Sp	1049	.PP
519	If nothing works and you are sure that everything is set correctly then	1050	If nothing works and you are sure that everything is set correctly then
520	you will need to remember a little known fact: Some programs just don't	1051	you will need to remember a little known fact: Some programs just don't
521	support locales :(	1052	support locales :(
522	.IP "Why do some characters look so much different than others?" 4	1053	.PP
523	.IX Item "Why do some characters look so much different than others?"	1054	\fIHow does rxvt-unicode determine the encoding to use?\fR
524	.PD 0	1055	.IX Subsection "How does rxvt-unicode determine the encoding to use?"
525	.IP "How does rxvt-unicode choose fonts?" 4	1056	.PP
526	.IX Item "How does rxvt-unicode choose fonts?"	1057	See next entry.
527	.PD	1058	.PP
528	Most fonts do not contain the full range of Unicode, which is	1059	\fIIs there an option to switch encodings?\fR
529	fine. Chances are that the font you (or the admin/package maintainer of	1060	.IX Subsection "Is there an option to switch encodings?"
530	your system/os) have specified does not cover all the characters you want	1061	.PP
531	to display.	1062	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
532	.Sp	1063	specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
533	\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement	1064	\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
534	font. Often the result is fine, but sometimes the chosen font looks	1065	.PP
535	bad/ugly/wrong. Some fonts have totally strange characters that don't	1066	The reasons is that there exists a perfectly fine mechanism for selecting
536	resemble the correct glyph at all, and rxvt-unicode lacks the artificial	1067	the encoding, doing I/O and (most important) communicating this to all
537	intelligence to detect that a specific glyph is wrong: it has to believe	1068	applications so everybody agrees on character properties such as width
538	the font that the characters it claims to contain indeed look correct.	1069	and code number. This mechanism is the \fIlocale\fR. Applications not using
539	.Sp	1070	that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
540	In that case, select a font of your taste and add it to the font list,	1071	characters wrong as it uses it's own, locale-independent table under all
541	e.g.:	1072	locales).
542	.Sp	1073	.PP
		1074	Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
		1075	programs doing the same (that is, most) will automatically agree in the
		1076	interpretation of characters.
		1077	.PP
		1078	Unfortunately, there is no system-independent way to select locales, nor
		1079	is there a standard on how locale specifiers will look like.
		1080	.PP
		1081	On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
		1082	contains an arbitrary string which corresponds to an already-installed
		1083	locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
		1084	\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
		1085	(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
		1086	.PP
		1087	Rxvt-unicode ignores all other locale categories, and except for
		1088	the encoding, ignores country or language-specific settings,
		1089	i.e. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR and \f(CW\*(C`ja_JP.UTF\-8\*(C'\fR are the normally same to
		1090	rxvt\-unicode.
		1091	.PP
		1092	If you want to use a specific encoding you have to make sure you start
		1093	rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
		1094	.PP
		1095	\fICan I switch locales at runtime?\fR
		1096	.IX Subsection "Can I switch locales at runtime?"
		1097	.PP
		1098	Yes, using an escape sequence. Try something like this, which sets
		1099	rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
		1100	.PP
543	.Vb 1	1101	.Vb 1
544	\& @@RXVT_NAME@@ -fn basefont,font2,font3...	1102	\& printf '\ee]701;%s\e007' ja_JP.SJIS
545	.Ve	1103	.Ve
546	.Sp	1104	.PP
547	When rxvt-unicode sees a character, it will first look at the base	1105	See also the previous answer.
548	font. If the base font does not contain the character, it will go to the	1106	.PP
549	next font, and so on. Specifying your own fonts will also speed up this	1107	Sometimes this capability is rather handy when you want to work in
550	search and use less resources within rxvt-unicode and the X\-server.	1108	one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
551	.Sp	1109	(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
552	The only limitation is that none of the fonts may be larger than the base	1110	first switches to a locale supported by xjdic and back later:
553	font, as the base font defines the terminal character cell size, which	1111	.PP
554	must be the same due to the way terminals work.	1112	.Vb 3
555	.IP "Why do some chinese characters look so different than others?" 4	1113	\& printf '\ee]701;%s\e007' ja_JP.SJIS
556	.IX Item "Why do some chinese characters look so different than others?"	1114	\& xjdic -js
557	This is because there is a difference between script and language \*(--	1115	\& printf '\ee]701;%s\e007' de_DE.UTF-8
558	rxvt-unicode does not know which language the text that is output is,	1116	.Ve
559	as it only knows the unicode character codes. If rxvt-unicode first	1117	.PP
560	sees a japanese/chinese character, it might choose a japanese font for	1118	You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
561	display. Subsequent japanese characters will use that font. Now, many	1119	for some locales where character width differs between program\- and
562	chinese characters aren't represented in japanese fonts, so when the first	1120	rxvt\-unicode\-locales.
563	non-japanese character comes up, rxvt-unicode will look for a chinese font	1121	.PP
564	\&\*(-- unfortunately at this point, it will still use the japanese font for	1122	\fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR
565	chinese characters that are also in the japanese font.	1123	.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
566	.Sp	1124	.PP
567	The workaround is easy: just tag a chinese font at the end of your font	1125	You can specify separate locales for the input method and the rest of the
568	list (see the previous question). The key is to view the font list as	1126	terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
569	a preference list: If you expect more japanese, list a japanese font	1127	.PP
570	first. If you expect more chinese, put a chinese font first.	1128	.Vb 1
571	.Sp	1129	\& URxvt.imlocale: ja_JP.EUC-JP
572	In the future it might be possible to switch language preferences at	1130	.Ve
573	runtime (the internal data structure has no problem with using different	1131	.PP
574	fonts for the same character at the same time, but no interface for this	1132	Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
575	has been designed yet).	1133	use your input method. Please note, however, that you will not be able to
576	.Sp	1134	input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
577	Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).	1135	method limits you.
578	.IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4	1136	.PP
579	.IX Item "Why does rxvt-unicode sometimes leave pixel droppings?"	1137	\fIRxvt-unicode crashes when the X Input Method changes or exits.\fR
580	Most fonts were not designed for terminal use, which means that character	1138	.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
581	size varies a lot. A font that is otherwise fine for terminal use might	1139	.PP
582	contain some characters that are simply too wide. Rxvt-unicode will avoid	1140	Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
583	these characters. For characters that are just \*(L"a bit\*(R" too wide a special	1141	design. Applications can avoid some crashes at the expense of memory
584	\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.	1142	leaks, and Input Methods can avoid some crashes by careful ordering at
585	.Sp	1143	exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
586	All of this requires that fonts do not lie about character sizes,	1144	while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however,
587	however: Xft fonts often draw glyphs larger than their acclaimed bounding	1145	crashes cannot be completely avoided even if both sides cooperate.
588	box, and rxvt-unicode has no way of detecting this (the correct way is to	1146	.PP
589	ask for the character bounding box, which unfortunately is wrong in these	1147	So the only workaround is not to kill your Input Method Servers.
590	cases).	1148	.Sh "Operating Systems / Package Maintaining"
591	.Sp	1149	.IX Subsection "Operating Systems / Package Maintaining"
592	It's not clear (to me at least), wether this is a bug in Xft, freetype,	1150	\fII am using Debian GNU/Linux and have a problem...\fR
593	or the respective font. If you encounter this problem you might try using	1151	.IX Subsection "I am using Debian GNU/Linux and have a problem..."
594	the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you	1152	.PP
595	might be forced to use a different font.	1153	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
596	.Sp	1154	patches that considerably change the behaviour of rxvt-unicode (but
597	All of this is not a problem when using X11 core fonts, as their bounding	1155	unfortunately this notice has been removed). Before reporting a bug to
598	box data is correct.	1156	the original rxvt-unicode author please download and install the genuine
		1157	version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce
		1158	the problem. If you cannot, chances are that the problems are specific to
		1159	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1160	Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
		1161	.PP
		1162	For other problems that also affect the Debian package, you can and
		1163	probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a
		1164	bug in the Debian version and it serves as a reminder for other users that
		1165	might encounter the same issue.
		1166	.PP
		1167	\fII am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?\fR
		1168	.IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"
		1169	.PP
		1170	You should build one binary with the default options. \fIconfigure\fR
		1171	now enables most useful options, and the trend goes to making them
		1172	runtime\-switchable, too, so there is usually no drawback to enbaling them,
		1173	except higher disk and possibly memory usage. The perl interpreter should
		1174	be enabled, as important functionality (menus, selection, likely more in
		1175	the future) depends on it.
		1176	.PP
		1177	You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources
		1178	system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful
		1179	behaviour. If your distribution aims at low memory, add an empty
		1180	\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the
		1181	perl interpreter disabled until the user enables it.
		1182	.PP
		1183	If you can/want build more binaries, I recommend building a minimal
		1184	one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with
		1185	\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of
		1186	encodings built-in that increase download times and are rarely used).
		1187	.PP
		1188	\fII need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?\fR
		1189	.IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?"
		1190	.PP
		1191	It should be, starting with release 7.1. You are encouraged to properly
		1192	install urxvt with privileges necessary for your \s-1OS\s0 now.
		1193	.PP
		1194	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1195	into a helper process for privileged operations (pty handling on some
		1196	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1197	immediately. This is much safer than most other terminals that keep
		1198	privileges while running (but is more relevant to urxvt, as it contains
		1199	things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).
		1200	.PP
		1201	This forking is done as the very first within \fImain()\fR, which is very early
		1202	and reduces possible bugs to initialisation code run before \fImain()\fR, or
		1203	things like the dynamic loader of your system, which should result in very
		1204	little risk.
		1205	.PP
599	.IP "On Solaris 9, many line-drawing characters are too wide." 4	1206	\fIOn Solaris 9, many line-drawing characters are too wide.\fR
600	.IX Item "On Solaris 9, many line-drawing characters are too wide."	1207	.IX Subsection "On Solaris 9, many line-drawing characters are too wide."
		1208	.PP
601	Seems to be a known bug, read	1209	Seems to be a known bug, read
602	<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1210	<http://nixdoc.net/files/forum/about34198.html>. Some people use the
603	following ugly workaround to get non-double-wide-characters working:	1211	following ugly workaround to get non-double-wide-characters working:
604	.Sp	1212	.PP
605	.Vb 1	1213	.Vb 1
606	\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1214	\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
607	.Ve	1215	.Ve
608	.IP "My Compose (Multi_key) key is no longer working." 4	1216	.PP
609	.IX Item "My Compose (Multi_key) key is no longer working."
610	The most common causes for this are that either your locale is not set
611	correctly, or you specified a \fBpreeditStyle\fR that is not supported by
612	your input method. For example, if you specified \fBOverTheSpot\fR and
613	your input method (e.g. the default input method handling Compose keys)
614	does not support this (for instance because it is not visual), then
615	rxvt-unicode will continue without an input method.
616	.Sp
617	In this case either do not specify a \fBpreeditStyle\fR or specify more than
618	one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
619	.ie n .IP "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4
620	.el .IP "I cannot type \f(CWCtrl\-Shift\-2\fR to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4
621	.IX Item "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
622	Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
623	international keyboards) or simply use \s-1ISO\s0 14755 support to your
624	advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
625	codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
626	character and so on.
627	.IP "How can I keep rxvt-unicode from using reverse video so much?" 4
628	.IX Item "How can I keep rxvt-unicode from using reverse video so much?"
629	First of all, make sure you are running with the right terminal settings
630	(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
631	make sure you have specified colours for italic and bold, as otherwise
632	rxvt-unicode might use reverse video to simulate the effect:
633	.Sp
634	.Vb 2
635	\& URxvt.colorBD: white
636	\& URxvt.colorIT: green
637	.Ve
638	.IP "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 4
639	.IX Item "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
640	For some unexplainable reason, some rare programs assume a very weird
641	colour palette when confronted with a terminal with more than the standard
642	8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
643	these programs not to assume non-ISO colours without very good reasons.
644	.Sp
645	In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
646	definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
647	fix colours but keep you from using other rxvt-unicode features.
648	.IP "I am on FreeBSD and rxvt-unicode does not seem to work at all." 4	1217	\fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR
649	.IX Item "I am on FreeBSD and rxvt-unicode does not seem to work at all."	1218	.IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all."
		1219	.PP
650	Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined	1220	Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
651	in your compile environment, or an implementation that implements it,	1221	in your compile environment, or an implementation that implements it,
652	wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that	1222	wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
653	\&\fBwchar_t\fR is represented as unicode.	1223	\&\fBwchar_t\fR is represented as unicode.
654	.Sp	1224	.PP
655	As you might have guessed, FreeBSD does neither define this symobl nor	1225	As you might have guessed, FreeBSD does neither define this symobl nor
656	does it support it. Instead, it uses it's own internal representation of	1226	does it support it. Instead, it uses it's own internal representation of
657	\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.	1227	\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
658	.Sp	1228	.PP
659	However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and	1229	However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and
660	\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.	1230	\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.
661	.Sp	1231	.PP
662	\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language	1232	\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language
663	apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized)	1233	apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized)
664	representation of \fBwchar_t\fR makes it impossible to convert between	1234	representation of \fBwchar_t\fR makes it impossible to convert between
665	\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding	1235	\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding
666	without implementing OS-specific-wrappers for each and every locale. There	1236	without implementing OS-specific-wrappers for each and every locale. There
667	simply are no APIs to convert \fBwchar_t\fR into anything except the current	1237	simply are no APIs to convert \fBwchar_t\fR into anything except the current
668	locale encoding.	1238	locale encoding.
669	.Sp	1239	.PP
670	Some applications (such as the formidable \fBmlterm\fR) work around this	1240	Some applications (such as the formidable \fBmlterm\fR) work around this
671	by carrying their own replacement functions for character set handling	1241	by carrying their own replacement functions for character set handling
672	with them, and either implementing OS-dependent hacks or doing multiple	1242	with them, and either implementing OS-dependent hacks or doing multiple
673	conversions (which is slow and unreliable in case the \s-1OS\s0 implements	1243	conversions (which is slow and unreliable in case the \s-1OS\s0 implements
674	encodings slightly different than the terminal emulator).	1244	encodings slightly different than the terminal emulator).
675	.Sp	1245	.PP
676	The rxvt-unicode author insists that the right way to fix this is in the	1246	The rxvt-unicode author insists that the right way to fix this is in the
677	system libraries once and for all, instead of forcing every app to carry	1247	system libraries once and for all, instead of forcing every app to carry
678	complete replacements for them :)	1248	complete replacements for them :)
		1249	.PP
679	.IP "I use Solaris 9 and it doesn't compile/work/etc." 4	1250	\fII use Solaris 9 and it doesn't compile/work/etc.\fR
680	.IX Item "I use Solaris 9 and it doesn't compile/work/etc."	1251	.IX Subsection "I use Solaris 9 and it doesn't compile/work/etc."
		1252	.PP
681	Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst	1253	Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
682	problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.	1254	problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
		1255	.PP
683	.IP "How can I use rxvt-unicode under cygwin?" 4	1256	\fIHow can I use rxvt-unicode under cygwin?\fR
684	.IX Item "How can I use rxvt-unicode under cygwin?"	1257	.IX Subsection "How can I use rxvt-unicode under cygwin?"
		1258	.PP
685	rxvt-unicode should compile and run out of the box on cygwin, using	1259	rxvt-unicode should compile and run out of the box on cygwin, using
686	the X11 libraries that come with cygwin. libW11 emulation is no	1260	the X11 libraries that come with cygwin. libW11 emulation is no
687	longer supported (and makes no sense, either, as it only supported a	1261	longer supported (and makes no sense, either, as it only supported a
688	single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or	1262	single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
689	\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the	1263	\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
690	old libW11 emulation.	1264	old libW11 emulation.
691	.Sp	1265	.PP
692	At the time of this writing, cygwin didn't seem to support any multi-byte	1266	At the time of this writing, cygwin didn't seem to support any multi-byte
693	encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited	1267	encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
694	to 8\-bit encodings.	1268	to 8\-bit encodings.
695	.IP "How does rxvt-unicode determine the encoding to use?" 4
696	.IX Item "How does rxvt-unicode determine the encoding to use?"
697	.PD 0
698	.IP "Is there an option to switch encodings?" 4
699	.IX Item "Is there an option to switch encodings?"
700	.PD
701	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
702	specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
703	\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
704	.Sp
705	The reasons is that there exists a perfectly fine mechanism for selecting
706	the encoding, doing I/O and (most important) communicating this to all
707	applications so everybody agrees on character properties such as width
708	and code number. This mechanism is the \fIlocale\fR. Applications not using
709	that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
710	characters wrong as it uses it's own, locale-independent table under all
711	locales).
712	.Sp
713	Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
714	programs doing the same (that is, most) will automatically agree in the
715	interpretation of characters.
716	.Sp
717	Unfortunately, there is no system-independent way to select locales, nor
718	is there a standard on how locale specifiers will look like.
719	.Sp
720	On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
721	contains an arbitrary string which corresponds to an already-installed
722	locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
723	\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
724	(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
725	.Sp
726	Rxvt-unicode ignores all other locale categories, and except for
727	the encoding, ignores country or language-specific settings,
728	i.e. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR and \f(CW\*(C`ja_JP.UTF\-8\*(C'\fR are the normally same to
729	rxvt\-unicode.
730	.Sp
731	If you want to use a specific encoding you have to make sure you start
732	rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
733	.IP "Can I switch locales at runtime?" 4
734	.IX Item "Can I switch locales at runtime?"
735	Yes, using an escape sequence. Try something like this, which sets
736	rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
737	.Sp
738	.Vb 1
739	\& printf '\ee]701;%s\e007' ja_JP.SJIS
740	.Ve
741	.Sp
742	See also the previous answer.
743	.Sp
744	Sometimes this capability is rather handy when you want to work in
745	one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
746	(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
747	first switches to a locale supported by xjdic and back later:
748	.Sp
749	.Vb 3
750	\& printf '\ee]701;%s\e007' ja_JP.SJIS
751	\& xjdic -js
752	\& printf '\ee]701;%s\e007' de_DE.UTF-8
753	.Ve
754	.Sp
755	You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
756	for some locales where character width differs between program\- and
757	rxvt\-unicode\-locales.
758	.IP "Can I switch the fonts at runtime?" 4
759	.IX Item "Can I switch the fonts at runtime?"
760	Yes, using an escape sequence. Try something like this, which has the same
761	effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
762	.Sp
763	.Vb 1
764	\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
765	.Ve
766	.Sp
767	This is useful if you e.g. work primarily with japanese (and prefer a
768	japanese font), but you have to switch to chinese temporarily, where
769	japanese fonts would only be in your way.
770	.Sp
771	You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
772	.IP "Why do italic characters look as if clipped?" 4
773	.IX Item "Why do italic characters look as if clipped?"
774	Many fonts have difficulties with italic characters and hinting. For
775	example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
776	Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
777	enable freetype autohinting, i.e. like this:
778	.Sp
779	.Vb 2
780	\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
781	\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
782	.Ve
783	.IP "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" 4
784	.IX Item "My input method wants <some encoding> but I want UTF-8, what can I do?"
785	You can specify separate locales for the input method and the rest of the
786	terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
787	.Sp
788	.Vb 1
789	\& URxvt.imlocale: ja_JP.EUC-JP
790	.Ve
791	.Sp
792	Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
793	use your input method. Please note, however, that you will not be able to
794	input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
795	method limits you.
796	.IP "Rxvt-unicode crashes when the X Input Method changes or exits." 4
797	.IX Item "Rxvt-unicode crashes when the X Input Method changes or exits."
798	Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
799	design. Applications can avoid some crashes at the expense of memory
800	leaks, and Input Methods can avoid some crashes by careful ordering at
801	exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
802	while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however,
803	crashes cannot be completely avoided even if both sides cooperate.
804	.Sp
805	So the only workaround is not to kill your Input Method Servers.
806	.IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4
807	.IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?"
808	Rxvt-unicode tries to obey the rule of not charging you for something you
809	don't use. One thing you should try is to configure out all settings that
810	you don't need, for example, Xft support is a resource hog by design,
811	when used. Compiling it out ensures that no Xft font will be loaded
812	accidentally when rxvt-unicode tries to find a font for your characters.
813	.Sp
814	Also, many people (me included) like large windows and even larger
815	scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
816	6 bytes per screen cell. For a 160x?? window this amounts to almost a
817	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
818	use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
819	rxvt-unicode then uses 8 bytes per screen cell.
820	.IP "Can I speed up Xft rendering somehow?" 4
821	.IX Item "Can I speed up Xft rendering somehow?"
822	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
823	it is simply slow. If you still want Xft fonts you might try to disable
824	antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
825	memory and also speeds up rendering considerably.
826	.IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4
827	.IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
828	Rxvt-unicode will use whatever you specify as a font. If it needs to
829	fall back to it's default font search list it will prefer X11 core
830	fonts, because they are small and fast, and then use Xft fonts. It has
831	antialiasing disabled for most of them, because the author thinks they
832	look best that way.
833	.Sp
834	If you want antialiasing, you have to specify the fonts manually.
835	.IP "Mouse cut/paste suddenly no longer works." 4
836	.IX Item "Mouse cut/paste suddenly no longer works."
837	Make sure that mouse reporting is actually turned off since killing
838	some editors prematurely may leave the mouse in mouse report mode. I've
839	heard that tcsh may use mouse reporting unless it otherwise specified. A
840	quick check is to see if cut/paste works when the Alt or Shift keys are
841	depressed.
842	.IP "What's with this bold/blink stuff?" 4
843	.IX Item "What's with this bold/blink stuff?"
844	If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
845	standard foreground colour.
846	.Sp
847	For the standard background colour, blinking will actually make the
848	text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
849	colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
850	ignored.
851	.Sp
852	On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
853	foreground/background colors.
854	.Sp
855	color0\-7 are the low-intensity colors.
856	.Sp
857	color8\-15 are the corresponding high-intensity colors.
858	.IP "I don't like the screen colors. How do I change them?" 4
859	.IX Item "I don't like the screen colors. How do I change them?"
860	You can change the screen colors at run-time using \fI~/.Xdefaults\fR
861	resources (or as long\-options).
862	.Sp
863	Here are values that are supposed to resemble a \s-1VGA\s0 screen,
864	including the murky brown that passes for low-intensity yellow:
865	.Sp
866	.Vb 8
867	\& URxvt.color0: #000000
868	\& URxvt.color1: #A80000
869	\& URxvt.color2: #00A800
870	\& URxvt.color3: #A8A800
871	\& URxvt.color4: #0000A8
872	\& URxvt.color5: #A800A8
873	\& URxvt.color6: #00A8A8
874	\& URxvt.color7: #A8A8A8
875	.Ve
876	.Sp
877	.Vb 8
878	\& URxvt.color8: #000054
879	\& URxvt.color9: #FF0054
880	\& URxvt.color10: #00FF54
881	\& URxvt.color11: #FFFF54
882	\& URxvt.color12: #0000FF
883	\& URxvt.color13: #FF00FF
884	\& URxvt.color14: #00FFFF
885	\& URxvt.color15: #FFFFFF
886	.Ve
887	.Sp
888	And here is a more complete set of non-standard colors described (not by
889	me) as \*(L"pretty girly\*(R".
890	.Sp
891	.Vb 18
892	\& URxvt.cursorColor: #dc74d1
893	\& URxvt.pointerColor: #dc74d1
894	\& URxvt.background: #0e0e0e
895	\& URxvt.foreground: #4ad5e1
896	\& URxvt.color0: #000000
897	\& URxvt.color8: #8b8f93
898	\& URxvt.color1: #dc74d1
899	\& URxvt.color9: #dc74d1
900	\& URxvt.color2: #0eb8c7
901	\& URxvt.color10: #0eb8c7
902	\& URxvt.color3: #dfe37e
903	\& URxvt.color11: #dfe37e
904	\& URxvt.color5: #9e88f0
905	\& URxvt.color13: #9e88f0
906	\& URxvt.color6: #73f7ff
907	\& URxvt.color14: #73f7ff
908	\& URxvt.color7: #e1dddd
909	\& URxvt.color15: #e1dddd
910	.Ve
911	.IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4
912	.IX Item "How can I start @@RXVT_NAME@@d in a race-free way?"
913	Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
914	display, create the listening socket and then fork.
915	.IP "What's with the strange Backspace/Delete key behaviour?" 4
916	.IX Item "What's with the strange Backspace/Delete key behaviour?"
917	Assuming that the physical Backspace key corresponds to the
918	BackSpace keysym (not likely for Linux ... see the following
919	question) there are two standard values that can be used for
920	Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
921	.Sp
922	Historically, either value is correct, but rxvt-unicode adopts the debian
923	policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
924	choice :).
925	.Sp
926	Rxvt-unicode tries to inherit the current stty settings and uses the value
927	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
928	started from a terminal (say, from a menu or by remote shell), then the
929	system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
930	be used (which may not be the same as your stty setting).
931	.Sp
932	For starting a new rxvt\-unicode:
933	.Sp
934	.Vb 3
935	\& # use Backspace = ^H
936	\& $ stty erase ^H
937	\& $ @@RXVT_NAME@@
938	.Ve
939	.Sp
940	.Vb 3
941	\& # use Backspace = ^?
942	\& $ stty erase ^?
943	\& $ @@RXVT_NAME@@
944	.Ve
945	.Sp
946	Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
947	.Sp
948	For an existing rxvt\-unicode:
949	.Sp
950	.Vb 3
951	\& # use Backspace = ^H
952	\& $ stty erase ^H
953	\& $ echo -n "^[[36h"
954	.Ve
955	.Sp
956	.Vb 3
957	\& # use Backspace = ^?
958	\& $ stty erase ^?
959	\& $ echo -n "^[[36l"
960	.Ve
961	.Sp
962	This helps satisfy some of the Backspace discrepancies that occur, but
963	if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
964	properly reflects that.
965	.Sp
966	The Delete key is a another casualty of the ill-defined Backspace problem.
967	To avoid confusion between the Backspace and Delete keys, the Delete
968	key has been assigned an escape sequence to match the vt100 for Execute
969	(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
970	.Sp
971	Some other Backspace problems:
972	.Sp
973	some editors use termcap/terminfo,
974	some editors (vim I'm told) expect Backspace = ^H,
975	\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
976	.Sp
977	Perhaps someday this will all be resolved in a consistent manner.
978	.IP "I don't like the key\-bindings. How do I change them?" 4
979	.IX Item "I don't like the key-bindings. How do I change them?"
980	There are some compile-time selections available via configure. Unless
981	you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
982	use the `keysym' resource to alter the keystrings associated with keysyms.
983	.Sp
984	Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR
985	.Sp
986	.Vb 20
987	\& URxvt.keysym.Home: \e033[1~
988	\& URxvt.keysym.End: \e033[4~
989	\& URxvt.keysym.C-apostrophe: \e033<C-'>
990	\& URxvt.keysym.C-slash: \e033<C-/>
991	\& URxvt.keysym.C-semicolon: \e033<C-;>
992	\& URxvt.keysym.C-grave: \e033<C-`>
993	\& URxvt.keysym.C-comma: \e033<C-,>
994	\& URxvt.keysym.C-period: \e033<C-.>
995	\& URxvt.keysym.C-0x60: \e033<C-`>
996	\& URxvt.keysym.C-Tab: \e033<C-Tab>
997	\& URxvt.keysym.C-Return: \e033<C-Return>
998	\& URxvt.keysym.S-Return: \e033<S-Return>
999	\& URxvt.keysym.S-space: \e033<S-Space>
1000	\& URxvt.keysym.M-Up: \e033<M-Up>
1001	\& URxvt.keysym.M-Down: \e033<M-Down>
1002	\& URxvt.keysym.M-Left: \e033<M-Left>
1003	\& URxvt.keysym.M-Right: \e033<M-Right>
1004	\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 >
1005	\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
1006	\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
1007	.Ve
1008	.Sp
1009	See some more examples in the documentation for the \fBkeysym\fR resource.
1010	.IP "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." 4
1011	.IX Item "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 mappings that rxvt-unicode doesn't recognize."
1012	.Vb 6
1013	\& KP_Insert == Insert
1014	\& F22 == Print
1015	\& F27 == Home
1016	\& F29 == Prior
1017	\& F33 == End
1018	\& F35 == Next
1019	.Ve
1020	.Sp
1021	Rather than have rxvt-unicode try to accommodate all the various possible
1022	keyboard mappings, it is better to use `xmodmap' to remap the keys as
1023	required for your particular machine.
1024	.IP "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." 4
1025	.IX Item "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
1026	rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can
1027	check and see if that is set. Note that several programs, \s-1JED\s0, slrn,
1028	Midnight Commander automatically check this variable to decide whether or
1029	not to use color.
1030	.IP "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" 4
1031	.IX Item "How do I set the correct, full IP address for the DISPLAY variable?"
1032	If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
1033	insecure mode then it is possible to use the following shell script
1034	snippets to correctly set the display. If your version of rxvt-unicode
1035	wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then
1036	the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a
1037	regular xterm.
1038	.Sp
1039	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
1040	snippets:
1041	.Sp
1042	.Vb 12
1043	\& # Bourne/Korn/POSIX family of shells:
1044	\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
1045	\& if [ ${TERM:-foo} = xterm ]; then
1046	\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
1047	\& echo -n '^[Z'
1048	\& read term_id
1049	\& stty icanon echo
1050	\& if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
1051	\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
1052	\& read DISPLAY # set it in our local shell
1053	\& fi
1054	\& fi
1055	.Ve
1056	.IP "How do I compile the manual pages for myself?" 4
1057	.IX Item "How do I compile the manual pages for myself?"
1058	You need to have a recent version of perl installed as \fI/usr/bin/perl\fR,
1059	one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to
1060	the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
1061	.IP "My question isn't answered here, can I ask a human?" 4
1062	.IX Item "My question isn't answered here, can I ask a human?"
1063	Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR,
1064	channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be
1065	interested in learning about new and exciting problems (but not FAQs :).
1066	.SH "RXVT TECHNICAL REFERENCE"	1269	.SH "RXVT TECHNICAL REFERENCE"
1067	.IX Header "RXVT TECHNICAL REFERENCE"	1270	.IX Header "RXVT TECHNICAL REFERENCE"
1068	.SH "DESCRIPTION"	1271	.SH "DESCRIPTION"
1069	.IX Header "DESCRIPTION"	1272	.IX Header "DESCRIPTION"
1070	The rest of this document describes various technical aspects of	1273	The rest of this document describes various technical aspects of
…		…
2165	disable this.	2368	disable this.
2166	.Sp	2369	.Sp
2167	A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly	2370	A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly
2168	in combination with other switches) is:	2371	in combination with other switches) is:
2169	.Sp	2372	.Sp
2170	.Vb 18	2373	.Vb 15
2171	\& MWM-hints	2374	\& MWM-hints
2172	\& EWMH-hints (pid, utf8 names) and protocols (ping)	2375	\& EWMH-hints (pid, utf8 names) and protocols (ping)
2173	\& seperate underline colour (-underlineColor)	2376	\& seperate underline colour (-underlineColor)
2174	\& settable border widths and borderless switch (-w, -b, -bl)	2377	\& settable border widths and borderless switch (-w, -b, -bl)
2175	\& visual selection (-depth)	2378	\& visual depth selection (-depth)
2176	\& settable extra linespacing /-lsp)	2379	\& settable extra linespacing /-lsp)
2177	\& iso-14755-2 and -3, and visual feedback	2380	\& iso-14755-2 and -3, and visual feedback
2178	\& backindex and forwardindex escape sequence
2179	\& window op and some xterm/OSC escape sequences
2180	\& tripleclickwords (-tcw)	2381	\& tripleclickwords (-tcw)
2181	\& settable insecure mode (-insecure)	2382	\& settable insecure mode (-insecure)
2182	\& keysym remapping support	2383	\& keysym remapping support
2183	\& cursor blinking and underline cursor (-cb, -uc)	2384	\& cursor blinking and underline cursor (-cb, -uc)
2184	\& XEmbed support (-embed)	2385	\& XEmbed support (-embed)
2185	\& user-pty (-pty-fd)	2386	\& user-pty (-pty-fd)
2186	\& hold on exit (-hold)	2387	\& hold on exit (-hold)
2187	\& skip builtin block graphics (-sbg)	2388	\& skip builtin block graphics (-sbg)
		2389	.Ve
		2390	.Sp
		2391	It also enabled some non-essential features otherwise disabled, such as:
		2392	.Sp
		2393	.Vb 11
		2394	\& some round-trip time optimisations
		2395	\& nearest color allocation on pseudocolor screens
		2396	\& UTF8_STRING supporr for selection
2188	\& sgr modes 90..97 and 100..107	2397	\& sgr modes 90..97 and 100..107
		2398	\& backindex and forwardindex escape sequences
		2399	\& view change/zero scorllback esacpe sequences
		2400	\& locale switching escape sequence
		2401	\& window op and some xterm/OSC escape sequences
		2402	\& rectangular selections
		2403	\& trailing space removal for selections
		2404	\& verbose X error handling
2189	.Ve	2405	.Ve
2190	.IP "\-\-enable\-iso14755 (default: on)" 4	2406	.IP "\-\-enable\-iso14755 (default: on)" 4
2191	.IX Item "--enable-iso14755 (default: on)"	2407	.IX Item "--enable-iso14755 (default: on)"
2192	Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or	2408	Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or
2193	\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by	2409	\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by

Diff Legend

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