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

Diff Legend

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