ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.98 by root, Tue Jan 31 00:56:07 2006 UTC vs.
Revision 1.162 by ayin, Sat Jan 19 15:00:49 2008 UTC

…		…
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is also available on the World Wide Web at	21	The newest version of this document is also available on the World Wide Web at
22	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod>.
23		23
		24	The main manual page for @@RXVT_NAME@@ itself is available at
		25	L<http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.1.pod>.
		26
24	=head1 FREQUENTLY ASKED QUESTIONS	27	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
25		28
26	=head2 The new selection selects pieces that are too big, how can I select
27	single words?
28		29
29	Yes. For example, if you want to select alphanumeric words, you can use	30	=head2 Meta, Features & Commandline Issues
30	the following resource:
31		31
32	URxvt.selection.pattern-0: ([[:word:]]+)	32	=head3 My question isn't answered here, can I ask a human?
33		33
34	If you click more than twice, the selection will be extended	34	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
35	more and more.	35	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		36	interested in learning about new and exciting problems (but not FAQs :).
36		37
37	To get a selection that is very similar to the old code, try this pattern:	38	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
38		39
39	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)	40	Beginning with version 7.3, there is a perl extension that implements a
		41	simple tabbed terminal. It is installed by default, so any of these should
		42	give you tabs:
40		43
41	Please also note that the I<LeftClick Shift-LeftClik> combination also	44	@@URXVT_NAME@@ -pe tabbed
42	selects words like the old code.
43		45
44	=over 4
45
46	=item I don't like the new selection/popups/hotkeys/perl, how do I
47	change/disable it?
48
49	You can disable the perl extension completely by setting the
50	B<perl-ext-common> resource to the empty string, which also keeps
51	rxvt-unicode from initialising perl, saving memory.
52
53	If you only want to disable specific features, you first have to
54	identify which perl extension is responsible. For this, read the section
55	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For
56	example, to disable the B<selection-popup> and B<option-popup>, specify
57	this B<perl-ext-common> resource:
58
59	URxvt.perl-ext-common: default,-selection-popup,-option-popup
60
61	This will keep the default extensions, but disable the two popup
62	extensions. Some extensions can also be configured, for example,
63	scrollback search mode is triggered by B<M-s>. You can move it to any
64	other combination either by setting the B<searchable-scrollback> resource:
65
66	URxvt.searchable-scrollback: CM-s
67
68	=item The cursor moves when selecting text in the current input line, how
69	do I switch this off?
70
71	=item During rlogin/ssh/telnet/etc. sessions, clicking near the cursor
72	outputs strange escape sequences, how do I fix this?
73
74	These are caused by the C<readline> perl extension. Under normal
75	circumstances, it will move your cursor around when you click into the
76	line that contains it. It tries hard not to do this at the wrong moment,
77	but when running a program that doesn't parse cursor movements or in some
78	cases during rlogin sessions, it fails to detect this properly.
79
80	You can permamently switch this feature off by disabling the C<readline>
81	extension:
82
83	URxvt.perl-ext-common: default,-readline	46	URxvt.perl-ext-common: default,tabbed
84		47
85	=item Why doesn't rxvt-unicode read my resources?	48	It will also work fine with tabbing functionality of many window managers
		49	or similar tabbing programs, and its embedding-features allow it to be
		50	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		51	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		52	(murxvt) terminal as an example embedding application.
86		53
87	Well, why, indeed? It does, in a way very similar to other X	54	=head3 How do I know which rxvt-unicode version I'm using?
88	applications. Most importantly, this means that if you or your OS loads
89	resources into the X display (the right way to do it), rxvt-unicode will
90	ignore any resource files in your home directory. It will only read
91	F<$HOME/.Xdefaults> when no resources are attached to the display.
92		55
93	If you have or use an F<$HOME/.Xresources> file, chances are that	56	The version number is displayed with the usage (-h). Also the escape
94	resources are loaded into your X-server. In this case, you have to	57	sequence C<ESC [ 8 n> sets the window title to the version number. When
95	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).	58	using the @@URXVT_NAME@@c client, the version displayed is that of the
		59	daemon.
96		60
97	Also consider the form resources have to use:	61	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
98		62
99	URxvt.resource: value	63	Rxvt-unicode tries to obey the rule of not charging you for something you
		64	don't use. One thing you should try is to configure out all settings that
		65	you don't need, for example, Xft support is a resource hog by design,
		66	when used. Compiling it out ensures that no Xft font will be loaded
		67	accidentally when rxvt-unicode tries to find a font for your characters.
100		68
101	If you want to use another form (there are lots of different ways of	69	Also, many people (me included) like large windows and even larger
102	specifying resources), make sure you understand wether and why it	70	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
103	works. If unsure, use the form above.	71	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		72	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		73	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		74	rxvt-unicode then uses 8 bytes per screen cell.
104		75
105	=item I can't get transparency working, what am I doing wrong?	76	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
106		77
107	First of all, transparency isn't officially supported in rxvt-unicode, so	78	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
108	you are mostly on your own. Do not bug the author about it (but you may	79	display, create the listening socket and then fork.
109	bug everybody else). Also, if you can't get it working consider it a rite
110	of passage: ... and you failed.
111		80
112	Here are four ways to get transparency. B<Do> read the manpage and option	81	=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c?
113	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
114		82
115	1. Use inheritPixmap:	83	If you want to start @@URXVT_NAME@@d automatically whenever you run
		84	@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
116		85
117	Esetroot wallpaper.jpg	86	#!/bin/sh
118	@@RXVT_NAME@@ -ip -tint red -sh 40	87	@@URXVT_NAME@@c "$@"
		88	if [ $? -eq 2 ]; then
		89	@@URXVT_NAME@@d -q -o -f
		90	@@URXVT_NAME@@c "$@"
		91	fi
119		92
120	That works. If you think it doesn't, you lack transparency and tinting	93	This tries to create a new terminal, and if fails with exit status 2,
121	support, or you are unable to read.	94	meaning it couldn't connect to the daemon, it will start the daemon and
		95	re-run the command. Subsequent invocations of the script will re-use the
		96	existing daemon.
122		97
123	2. Use a simple pixmap and emulate pseudo-transparency. This enables you	98	=head3 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
124	to use effects other than tinting and shading: Just shade/tint/whatever
125	your picture with gimp:
126		99
127	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	100	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
128	@@RXVT_NAME@@ -pixmap background.xpm -pe automove-background	101	so you can check and see if that is set. Note that several programs, JED,
		102	slrn, Midnight Commander automatically check this variable to decide
		103	whether or not to use color.
129		104
130	That works. If you think it doesn't, you lack XPM and Perl support, or you	105	=head3 How do I set the correct, full IP address for the DISPLAY variable?
131	are unable to read.
132		106
133	3. Use an ARGB visual:	107	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		108	insecure mode then it is possible to use the following shell script
		109	snippets to correctly set the display. If your version of rxvt-unicode
		110	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		111	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		112	regular xterm.
134		113
135	@@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc	114	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		115	snippets:
136		116
137	This requires XFT support, and the support of your X-server. If that	117	# Bourne/Korn/POSIX family of shells:
138	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't	118	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
139	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary	119	if [ ${TERM:-foo} = xterm ]; then
140	bugfixes and workarounds for Xft and Xlib to make it work, but that	120	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
141	doesn't mean that your WM has the required kludges in place.	121	echo -n '^[Z'
		122	read term_id
		123	stty icanon echo
		124	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		125	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		126	read DISPLAY # set it in our local shell
		127	fi
		128	fi
142		129
143	4. Use xcompmgr and let it do the job:	130	=head3 How do I compile the manual pages on my own?
144		131
145	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \	132	You need to have a recent version of perl installed as F</usr/bin/perl>,
146	-set _NET_WM_WINDOW_OPACITY 0xc0000000	133	one that comes with F<pod2man>, F<pod2text> and F<pod2xhtml> (from
		134	F<Pod::Xhtml>). Then go to the doc subdirectory and enter C<make alldoc>.
147		135
148	Then click on a window you want to make transparent. Replace C<0xc0000000>
149	by other values to change the degree of opacity. If it doesn't work and
150	your server crashes, you got to keep the pieces.
151
152	=item Isn't rxvt supposed to be small? Don't all those features bloat?	136	=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
153		137
154	I often get asked about this, and I think, no, they didn't cause extra	138	I often get asked about this, and I think, no, they didn't cause extra
155	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see	139	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
156	that the urxvt binary is larger (due to some encoding tables always being	140	that the urxvt binary is larger (due to some encoding tables always being
157	compiled in), but it actually uses less memory (RSS) after startup. Even	141	compiled in), but it actually uses less memory (RSS) after startup. Even
…		…
161		145
162	text data bss drs rss filename	146	text data bss drs rss filename
163	98398 1664 24 15695 1824 rxvt --disable-everything	147	98398 1664 24 15695 1824 rxvt --disable-everything
164	188985 9048 66616 18222 1788 urxvt --disable-everything	148	188985 9048 66616 18222 1788 urxvt --disable-everything
165		149
166	When you C<--enable-everything> (which _is_ unfair, as this involves xft	150	When you C<--enable-everything> (which I<is> unfair, as this involves xft
167	and full locale/XIM support which are quite bloaty inside libX11 and my	151	and full locale/XIM support which are quite bloaty inside libX11 and my
168	libc), the two diverge, but not unreasnobaly so.	152	libc), the two diverge, but not unreasonably so.
169		153
170	text data bss drs rss filename	154	text data bss drs rss filename
171	163431 2152 24 20123 2060 rxvt --enable-everything	155	163431 2152 24 20123 2060 rxvt --enable-everything
172	1035683 49680 66648 29096 3680 urxvt --enable-everything	156	1035683 49680 66648 29096 3680 urxvt --enable-everything
173		157
…		…
189	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	173	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
190	43180k in daemons that stay around after exit, plus half a minute of	174	43180k in daemons that stay around after exit, plus half a minute of
191	startup time, including the hundreds of warnings it spits out), it fares	175	startup time, including the hundreds of warnings it spits out), it fares
192	extremely well *g*.	176	extremely well *g*.
193		177
194	=item Why C++, isn't that unportable/bloated/uncool?	178	=head3 Why C++, isn't that unportable/bloated/uncool?
195		179
196	Is this a question? :) It comes up very often. The simple answer is: I had	180	Is this a question? :) It comes up very often. The simple answer is: I had
197	to write it, and C++ allowed me to write and maintain it in a fraction	181	to write it, and C++ allowed me to write and maintain it in a fraction
198	of the time and effort (which is a scarce resource for me). Put even	182	of the time and effort (which is a scarce resource for me). Put even
199	shorter: It simply wouldn't exist without C++.	183	shorter: It simply wouldn't exist without C++.
…		…
216		200
217	And here is rxvt-unicode:	201	And here is rxvt-unicode:
218		202
219	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	203	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
220	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)	204	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
221	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)	205	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
222	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)	206	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
223	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	207	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
224		208
225	No large bloated libraries (of course, none were linked in statically),	209	No large bloated libraries (of course, none were linked in statically),
226	except maybe libX11 :)	210	except maybe libX11 :)
227		211
228	=item Does it support tabs, can I have a tabbed rxvt-unicode?
229		212
230	Beginning with version 7.3, there is a perl extension that implements a	213	=head2 Rendering, Font & Look and Feel Issues
231	simple tabbed terminal. It is installed by default, so any of these should
232	give you tabs:
233		214
234	@@RXVT_NAME@@ -pe tabbed	215	=head3 I can't get transparency working, what am I doing wrong?
235		216
		217	First of all, please address all transparency related issues to Sasha Vasko at
		218	sasha@aftercode.net and do not bug the author about it. Also, if you can't
		219	get it working consider it a rite of passage: ... and you failed.
		220
		221	Here are four ways to get transparency. B<Do> read the manpage and option
		222	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
		223
		224	1. Use transparent mode:
		225
		226	Esetroot wallpaper.jpg
		227	@@URXVT_NAME@@ -tr -tint red -sh 40
		228
		229	That works. If you think it doesn't, you lack transparency and tinting
		230	support, or you are unable to read.
		231
		232	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		233	to use effects other than tinting and shading: Just shade/tint/whatever
		234	your picture with gimp or any other tool:
		235
		236	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
		237	@@URXVT_NAME@@ -pixmap "background.jpg;:root"
		238
		239	That works. If you think it doesn't, you lack AfterImage support, or you
		240	are unable to read.
		241
		242	3. Use an ARGB visual:
		243
		244	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		245
		246	This requires XFT support, and the support of your X-server. If that
		247	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		248	there yet, no matter what they claim. Rxvt-Unicode contains the necessary
		249	bugfixes and workarounds for Xft and Xlib to make it work, but that
		250	doesn't mean that your WM has the required kludges in place.
		251
		252	4. Use xcompmgr and let it do the job:
		253
		254	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		255	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		256
		257	Then click on a window you want to make transparent. Replace C<0xc0000000>
		258	by other values to change the degree of opacity. If it doesn't work and
		259	your server crashes, you got to keep the pieces.
		260
		261	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		262
		263	Most fonts were not designed for terminal use, which means that character
		264	size varies a lot. A font that is otherwise fine for terminal use might
		265	contain some characters that are simply too wide. Rxvt-unicode will avoid
		266	these characters. For characters that are just "a bit" too wide a special
		267	"careful" rendering mode is used that redraws adjacent characters.
		268
		269	All of this requires that fonts do not lie about character sizes,
		270	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		271	box, and rxvt-unicode has no way of detecting this (the correct way is to
		272	ask for the character bounding box, which unfortunately is wrong in these
		273	cases).
		274
		275	It's not clear (to me at least), whether this is a bug in Xft, freetype,
		276	or the respective font. If you encounter this problem you might try using
		277	the C<-lsp> option to give the font more height. If that doesn't work, you
		278	might be forced to use a different font.
		279
		280	All of this is not a problem when using X11 core fonts, as their bounding
		281	box data is correct.
		282
		283	=head3 How can I keep rxvt-unicode from using reverse video so much?
		284
		285	First of all, make sure you are running with the right terminal settings
		286	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		287	make sure you have specified colours for italic and bold, as otherwise
		288	rxvt-unicode might use reverse video to simulate the effect:
		289
		290	URxvt.colorBD: white
		291	URxvt.colorIT: green
		292
		293	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		294
		295	For some unexplainable reason, some rare programs assume a very weird
		296	colour palette when confronted with a terminal with more than the standard
		297	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		298	these programs not to assume non-ISO colours without very good reasons.
		299
		300	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		301	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		302	fix colours but keep you from using other rxvt-unicode features.
		303
		304	=head3 Can I switch the fonts at runtime?
		305
		306	Yes, using an escape sequence. Try something like this, which has the same
		307	effect as using the C<-fn> switch, and takes effect immediately:
		308
		309	printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
		310
		311	This is useful if you e.g. work primarily with japanese (and prefer a
		312	japanese font), but you have to switch to chinese temporarily, where
		313	japanese fonts would only be in your way.
		314
		315	You can think of this as a kind of manual ISO-2022 switching.
		316
		317	=head3 Why do italic characters look as if clipped?
		318
		319	Many fonts have difficulties with italic characters and hinting. For
		320	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		321	Mono> completely fails in its italic face. A workaround might be to
		322	enable freetype autohinting, i.e. like this:
		323
		324	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		325	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		326
		327	=head3 Can I speed up Xft rendering somehow?
		328
		329	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		330	it is simply slow. If you still want Xft fonts you might try to disable
		331	antialiasing (by appending C<:antialias=false>), which saves lots of
		332	memory and also speeds up rendering considerably.
		333
		334	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		335
		336	Rxvt-unicode will use whatever you specify as a font. If it needs to
		337	fall back to its default font search list it will prefer X11 core
		338	fonts, because they are small and fast, and then use Xft fonts. It has
		339	antialiasing disabled for most of them, because the author thinks they
		340	look best that way.
		341
		342	If you want antialiasing, you have to specify the fonts manually.
		343
		344	=head3 What's with this bold/blink stuff?
		345
		346	If no bold colour is set via C<colorBD:>, bold will invert text using the
		347	standard foreground colour.
		348
		349	For the standard background colour, blinking will actually make
		350	the text blink when compiled with C<--enable-text-blink>. Without
		351	C<--enable-text-blink>, the blink attribute will be ignored.
		352
		353	On ANSI colours, bold/blink attributes are used to set high-intensity
		354	foreground/background colors.
		355
		356	color0-7 are the low-intensity colors.
		357
		358	color8-15 are the corresponding high-intensity colors.
		359
		360	=head3 I don't like the screen colors. How do I change them?
		361
		362	You can change the screen colors at run-time using F<~/.Xdefaults>
		363	resources (or as long-options).
		364
		365	Here are values that are supposed to resemble a VGA screen,
		366	including the murky brown that passes for low-intensity yellow:
		367
		368	URxvt.color0: #000000
		369	URxvt.color1: #A80000
		370	URxvt.color2: #00A800
		371	URxvt.color3: #A8A800
		372	URxvt.color4: #0000A8
		373	URxvt.color5: #A800A8
		374	URxvt.color6: #00A8A8
		375	URxvt.color7: #A8A8A8
		376
		377	URxvt.color8: #000054
		378	URxvt.color9: #FF0054
		379	URxvt.color10: #00FF54
		380	URxvt.color11: #FFFF54
		381	URxvt.color12: #0000FF
		382	URxvt.color13: #FF00FF
		383	URxvt.color14: #00FFFF
		384	URxvt.color15: #FFFFFF
		385
		386	And here is a more complete set of non-standard colors.
		387
		388	URxvt.cursorColor: #dc74d1
		389	URxvt.pointerColor: #dc74d1
		390	URxvt.background: #0e0e0e
		391	URxvt.foreground: #4ad5e1
		392	URxvt.color0: #000000
		393	URxvt.color8: #8b8f93
		394	URxvt.color1: #dc74d1
		395	URxvt.color9: #dc74d1
		396	URxvt.color2: #0eb8c7
		397	URxvt.color10: #0eb8c7
		398	URxvt.color3: #dfe37e
		399	URxvt.color11: #dfe37e
		400	URxvt.color5: #9e88f0
		401	URxvt.color13: #9e88f0
		402	URxvt.color6: #73f7ff
		403	URxvt.color14: #73f7ff
		404	URxvt.color7: #e1dddd
		405	URxvt.color15: #e1dddd
		406
		407	They have been described (not by me) as "pretty girly".
		408
		409	=head3 Why do some characters look so much different than others?
		410
		411	See next entry.
		412
		413	=head3 How does rxvt-unicode choose fonts?
		414
		415	Most fonts do not contain the full range of Unicode, which is
		416	fine. Chances are that the font you (or the admin/package maintainer of
		417	your system/os) have specified does not cover all the characters you want
		418	to display.
		419
		420	B<rxvt-unicode> makes a best-effort try at finding a replacement
		421	font. Often the result is fine, but sometimes the chosen font looks
		422	bad/ugly/wrong. Some fonts have totally strange characters that don't
		423	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		424	intelligence to detect that a specific glyph is wrong: it has to believe
		425	the font that the characters it claims to contain indeed look correct.
		426
		427	In that case, select a font of your taste and add it to the font list,
		428	e.g.:
		429
		430	@@URXVT_NAME@@ -fn basefont,font2,font3...
		431
		432	When rxvt-unicode sees a character, it will first look at the base
		433	font. If the base font does not contain the character, it will go to the
		434	next font, and so on. Specifying your own fonts will also speed up this
		435	search and use less resources within rxvt-unicode and the X-server.
		436
		437	The only limitation is that none of the fonts may be larger than the base
		438	font, as the base font defines the terminal character cell size, which
		439	must be the same due to the way terminals work.
		440
		441	=head3 Why do some chinese characters look so different than others?
		442
		443	This is because there is a difference between script and language --
		444	rxvt-unicode does not know which language the text that is output is,
		445	as it only knows the unicode character codes. If rxvt-unicode first
		446	sees a japanese/chinese character, it might choose a japanese font for
		447	display. Subsequent japanese characters will use that font. Now, many
		448	chinese characters aren't represented in japanese fonts, so when the first
		449	non-japanese character comes up, rxvt-unicode will look for a chinese font
		450	-- unfortunately at this point, it will still use the japanese font for
		451	chinese characters that are also in the japanese font.
		452
		453	The workaround is easy: just tag a chinese font at the end of your font
		454	list (see the previous question). The key is to view the font list as
		455	a preference list: If you expect more japanese, list a japanese font
		456	first. If you expect more chinese, put a chinese font first.
		457
		458	In the future it might be possible to switch language preferences at
		459	runtime (the internal data structure has no problem with using different
		460	fonts for the same character at the same time, but no interface for this
		461	has been designed yet).
		462
		463	Until then, you might get away with switching fonts at runtime (see L<Can
		464	I switch the fonts at runtime?> later in this document).
		465
		466	=head3 How can I make mplayer display video correctly?
		467
		468	We are working on it, in the meantime, as a workaround, use something like:
		469
		470	@@URXVT_NAME@@ -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		471
		472
		473	=head2 Keyboard, Mouse & User Interaction
		474
		475	=head3 The new selection selects pieces that are too big, how can I select single words?
		476
		477	If you want to select e.g. alphanumeric words, you can use the following
		478	setting:
		479
		480	URxvt.selection.pattern-0: ([[:word:]]+)
		481
		482	If you click more than twice, the selection will be extended
		483	more and more.
		484
		485	To get a selection that is very similar to the old code, try this pattern:
		486
		487	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		488
		489	Please also note that the I<LeftClick Shift-LeftClick> combination also
		490	selects words like the old code.
		491
		492	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		493
		494	You can disable the perl extension completely by setting the
		495	B<perl-ext-common> resource to the empty string, which also keeps
		496	rxvt-unicode from initialising perl, saving memory.
		497
		498	If you only want to disable specific features, you first have to
		499	identify which perl extension is responsible. For this, read the section
		500	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		501	example, to disable the B<selection-popup> and B<option-popup>, specify
		502	this B<perl-ext-common> resource:
		503
		504	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		505
		506	This will keep the default extensions, but disable the two popup
		507	extensions. Some extensions can also be configured, for example,
		508	scrollback search mode is triggered by B<M-s>. You can move it to any
		509	other combination either by setting the B<searchable-scrollback> resource:
		510
		511	URxvt.searchable-scrollback: CM-s
		512
		513	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		514
		515	See next entry.
		516
		517	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		518
		519	These are caused by the C<readline> perl extension. Under normal
		520	circumstances, it will move your cursor around when you click into the
		521	line that contains it. It tries hard not to do this at the wrong moment,
		522	but when running a program that doesn't parse cursor movements or in some
		523	cases during rlogin sessions, it fails to detect this properly.
		524
		525	You can permanently switch this feature off by disabling the C<readline>
		526	extension:
		527
236	URxvt.perl-ext-common: default,tabbed	528	URxvt.perl-ext-common: default,-readline
237		529
238	It will also work fine with tabbing functionality of many window managers	530	=head3 My numerical keypad acts weird and generates differing output?
239	or similar tabbing programs, and its embedding-features allow it to be
240	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
241	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
242	(murxvt) terminal as an example embedding application.
243		531
244	=item How do I know which rxvt-unicode version I'm using?	532	Some Debian GNUL/Linux users seem to have this problem, although no
		533	specific details were reported so far. It is possible that this is caused
		534	by the wrong C<TERM> setting, although the details of whether and how
		535	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		536	keymap. See the answer to the previous question, and please report if that
		537	helped.
245		538
246	The version number is displayed with the usage (-h). Also the escape	539	=head3 My Compose (Multi_key) key is no longer working.
247	sequence C<ESC [ 8 n> sets the window title to the version number. When
248	using the @@RXVT_NAME@@c client, the version displayed is that of the
249	daemon.
250		540
251	=item I am using Debian GNU/Linux and have a problem...	541	The most common causes for this are that either your locale is not set
		542	correctly, or you specified a B<preeditStyle> that is not supported by
		543	your input method. For example, if you specified B<OverTheSpot> and
		544	your input method (e.g. the default input method handling Compose keys)
		545	does not support this (for instance because it is not visual), then
		546	rxvt-unicode will continue without an input method.
252		547
253	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	548	In this case either do not specify a B<preeditStyle> or specify more than
254	patches that considerably change the behaviour of rxvt-unicode (but	549	one pre-edit style, such as B<OverTheSpot,Root,None>.
255	unfortunately this notice has been removed). Before reporting a bug to
256	the original rxvt-unicode author please download and install the genuine
257	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
258	the problem. If you cannot, chances are that the problems are specific to
259	Debian GNU/Linux, in which case it should be reported via the Debian Bug
260	Tracking System (use C<reportbug> to report the bug).
261		550
262	For other problems that also affect the Debian package, you can and	551	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
263	probably should use the Debian BTS, too, because, after all, it's also a
264	bug in the Debian version and it serves as a reminder for other users that
265	might encounter the same issue.
266		552
267	=item I am maintaining rxvt-unicode for distribution/OS XXX, any	553	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
268	recommendation?	554	international keyboards) or simply use ISO 14755 support to your
		555	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		556	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		557	character and so on.
269		558
270	You should build one binary with the default options. F<configure>	559	=head3 Mouse cut/paste suddenly no longer works.
271	now enables most useful options, and the trend goes to making them
272	runtime-switchable, too, so there is usually no drawback to enbaling them,
273	except higher disk and possibly memory usage. The perl interpreter should
274	be enabled, as important functionality (menus, selection, likely more in
275	the future) depends on it.
276		560
277	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	561	Make sure that mouse reporting is actually turned off since killing
278	system-wide (except maybe with C<defaults>). This will result in useful	562	some editors prematurely may leave the mouse in mouse report mode. I've
279	behaviour. If your distribution aims at low memory, add an empty	563	heard that tcsh may use mouse reporting unless it otherwise specified. A
280	C<perl-ext-common> resource to the app-defaults file. This will keep the	564	quick check is to see if cut/paste works when the Alt or Shift keys are
281	perl interpreter disabled until the user enables it.	565	depressed.
282		566
283	If you can/want build more binaries, I recommend building a minimal	567	=head3 What's with the strange Backspace/Delete key behaviour?
284	one with C<--disable-everything> (very useful) and a maximal one with
285	C<--enable-everything> (less useful, it will be very big due to a lot of
286	encodings built-in that increase download times and are rarely used).
287		568
288	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	569	Assuming that the physical Backspace key corresponds to the
		570	Backspace keysym (not likely for Linux ... see the following
		571	question) there are two standard values that can be used for
		572	Backspace: C<^H> and C<^?>.
289		573
290	It should be, starting with release 7.1. You are encouraged to properly	574	Historically, either value is correct, but rxvt-unicode adopts the debian
291	install urxvt with privileges necessary for your OS now.	575	policy of using C<^?> when unsure, because it's the one and only correct
		576	choice :).
292		577
293	When rxvt-unicode detects that it runs setuid or setgid, it will fork	578	Rxvt-unicode tries to inherit the current stty settings and uses the value
294	into a helper process for privileged operations (pty handling on some	579	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
295	systems, utmp/wtmp/lastlog handling on others) and drop privileges	580	started from a terminal (say, from a menu or by remote shell), then the
296	immediately. This is much safer than most other terminals that keep	581	system value of `erase', which corresponds to CERASE in <termios.h>, will
297	privileges while running (but is more relevant to urxvt, as it contains	582	be used (which may not be the same as your stty setting).
298	things as perl interpreters, which might be "helpful" to attackers).
299		583
300	This forking is done as the very first within main(), which is very early	584	For starting a new rxvt-unicode:
301	and reduces possible bugs to initialisation code run before main(), or
302	things like the dynamic loader of your system, which should result in very
303	little risk.
304		585
		586	# use Backspace = ^H
		587	$ stty erase ^H
		588	$ @@URXVT_NAME@@
		589
		590	# use Backspace = ^?
		591	$ stty erase ^?
		592	$ @@URXVT_NAME@@
		593
		594	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		595
		596	For an existing rxvt-unicode:
		597
		598	# use Backspace = ^H
		599	$ stty erase ^H
		600	$ echo -n "^[[36h"
		601
		602	# use Backspace = ^?
		603	$ stty erase ^?
		604	$ echo -n "^[[36l"
		605
		606	This helps satisfy some of the Backspace discrepancies that occur, but
		607	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		608	properly reflects that.
		609
		610	The Delete key is a another casualty of the ill-defined Backspace problem.
		611	To avoid confusion between the Backspace and Delete keys, the Delete
		612	key has been assigned an escape sequence to match the vt100 for Execute
		613	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		614
		615	Some other Backspace problems:
		616
		617	some editors use termcap/terminfo,
		618	some editors (vim I'm told) expect Backspace = ^H,
		619	GNU Emacs (and Emacs-like editors) use ^H for help.
		620
		621	Perhaps someday this will all be resolved in a consistent manner.
		622
		623	=head3 I don't like the key-bindings. How do I change them?
		624
		625	There are some compile-time selections available via configure. Unless
		626	you have run "configure" with the C<--disable-resources> option you can
		627	use the `keysym' resource to alter the keystrings associated with keysyms.
		628
		629	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		630
		631	URxvt.keysym.Home: \033[1~
		632	URxvt.keysym.End: \033[4~
		633	URxvt.keysym.C-apostrophe: \033<C-'>
		634	URxvt.keysym.C-slash: \033<C-/>
		635	URxvt.keysym.C-semicolon: \033<C-;>
		636	URxvt.keysym.C-grave: \033<C-`>
		637	URxvt.keysym.C-comma: \033<C-,>
		638	URxvt.keysym.C-period: \033<C-.>
		639	URxvt.keysym.C-0x60: \033<C-`>
		640	URxvt.keysym.C-Tab: \033<C-Tab>
		641	URxvt.keysym.C-Return: \033<C-Return>
		642	URxvt.keysym.S-Return: \033<S-Return>
		643	URxvt.keysym.S-space: \033<S-Space>
		644	URxvt.keysym.M-Up: \033<M-Up>
		645	URxvt.keysym.M-Down: \033<M-Down>
		646	URxvt.keysym.M-Left: \033<M-Left>
		647	URxvt.keysym.M-Right: \033<M-Right>
		648	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		649	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		650	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		651
		652	See some more examples in the documentation for the B<keysym> resource.
		653
		654	=head3 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
		655
		656	KP_Insert == Insert
		657	F22 == Print
		658	F27 == Home
		659	F29 == Prior
		660	F33 == End
		661	F35 == Next
		662
		663	Rather than have rxvt-unicode try to accommodate all the various possible
		664	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		665	required for your particular machine.
		666
		667
		668	=head2 Terminal Configuration
		669
		670	=head3 Can I see a typical configuration?
		671
		672	The default configuration tries to be xterm-like, which I don't like that
		673	much, but it's least surprise to regular users.
		674
		675	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		676	time into customising your terminal. To get you started, here is the
		677	author's .Xdefaults entries, with comments on what they do. It's certainly
		678	not I<typical>, but what's typical...
		679
		680	URxvt.cutchars: "()*,<>[]{}|'
		681	URxvt.print-pipe: cat >/tmp/xxx
		682
		683	These are just for testing stuff.
		684
		685	URxvt.imLocale: ja_JP.UTF-8
		686	URxvt.preeditType: OnTheSpot,None
		687
		688	This tells rxvt-unicode to use a special locale when communicating with
		689	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		690	type, which requires the C<xim-onthespot> perl extension but rewards me
		691	with correct-looking fonts.
		692
		693	URxvt.perl-lib: /root/lib/urxvt
		694	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		695	URxvt.selection.pattern-0: ( at .*? line \\d+)
		696	URxvt.selection.pattern-1: ^(/[^:]+):\
		697	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		698	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		699
		700	This is my perl configuration. The first two set the perl library
		701	directory and also tells urxvt to use a large number of extensions. I
		702	develop for myself mostly, so I actually use most of the extensions I
		703	write.
		704
		705	The selection stuff mainly makes the selection perl-error-message aware
		706	and tells it to convert perl error messages into vi-commands to load the
		707	relevant file and go tot he error line number.
		708
		709	URxvt.scrollstyle: plain
		710	URxvt.secondaryScroll: true
		711
		712	As the documentation says: plain is the preferred scrollbar for the
		713	author. The C<secondaryScroll> configures urxvt to scroll in full-screen
		714	apps, like screen, so lines scrolled out of screen end up in urxvt's
		715	scrollback buffer.
		716
		717	URxvt.background: #000000
		718	URxvt.foreground: gray90
		719	URxvt.color7: gray90
		720	URxvt.colorBD: #ffffff
		721	URxvt.cursorColor: #e0e080
		722	URxvt.throughColor: #8080f0
		723	URxvt.highlightColor: #f0f0f0
		724
		725	Some colours. Not sure which ones are being used or even non-defaults, but
		726	these are in my .Xdefaults. Most notably, they set foreground/background
		727	to light gray/black, and also make sure that the colour 7 matches the
		728	default foreground colour.
		729
		730	URxvt.underlineColor: yellow
		731
		732	Another colour, makes underline lines look different. Sometimes hurts, but
		733	is mostly a nice effect.
		734
		735	URxvt.geometry: 154x36
		736	URxvt.loginShell: false
		737	URxvt.meta: ignore
		738	URxvt.utmpInhibit: true
		739
		740	Uh, well, should be mostly self-explanatory. By specifying some defaults
		741	manually, I can quickly switch them for testing.
		742
		743	URxvt.saveLines: 8192
		744
		745	A large scrollback buffer is essential. Really.
		746
		747	URxvt.mapAlert: true
		748
		749	The only case I use it is for my IRC window, which I like to keep
		750	iconified till people msg me (which beeps).
		751
		752	URxvt.visualBell: true
		753
		754	The audible bell is often annoying, especially when in a crowd.
		755
		756	URxvt.insecure: true
		757
		758	Please don't hack my mutt! Ooops...
		759
		760	URxvt.pastableTabs: false
		761
		762	I once thought this is a great idea.
		763
		764	urxvt.font: 9x15bold,\
		765	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		766	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		767	[codeset=JISX0208]xft:Kochi Gothic, \
		768	xft:Bitstream Vera Sans Mono:autohint=true, \
		769	xft:Code2000:antialias=false
		770	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		771	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		772	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		773
		774	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		775	overwhelmed. A special note: the C<9x15bold> mentioned above is actually
		776	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		777	font (different glyphs for C<;> and many other harmless characters),
		778	while the second font is actually the C<9x15bold> from XFree4/XOrg. The
		779	bold version has less chars than the medium version, so I use it for rare
		780	characters, too. When editing sources with vim, I use italic for comments
		781	and other stuff, which looks quite good with Bitstream Vera anti-aliased.
		782
		783	Terminus is a quite bad font (many very wrong glyphs), but for most of my
		784	purposes, it works, and gives a different look, as my normal (Non-bold)
		785	font is already bold, and I want to see a difference between bold and
		786	normal fonts.
		787
		788	Please note that I used the C<urxvt> instance name and not the C<URxvt>
		789	class name. Thats because I use different configs for different purposes,
		790	for example, my IRC window is started with C<-name IRC>, and uses these
		791	defaults:
		792
		793	IRC*title: IRC
		794	IRC*geometry: 87x12+535+542
		795	IRC*saveLines: 0
		796	IRC*mapAlert: true
		797	IRC*font: suxuseuro
		798	IRC*boldFont: suxuseuro
		799	IRC*colorBD: white
		800	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		801	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		802
		803	C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font
		804	sizes. C<suxuseuro> allows me to keep an eye (and actually read)
		805	stuff while keeping a very small window. If somebody pastes something
		806	complicated (e.g. japanese), I temporarily switch to a larger font.
		807
		808	The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor
		809	C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname>
		810	file for different hosts, for example, on ym main desktop, I use:
		811
		812	URxvt.keysym.C-M-q: command:\033[3;5;5t
		813	URxvt.keysym.C-M-y: command:\033[3;5;606t
		814	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		815	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		816	URxvt.keysym.C-M-p: perl:test
		817
		818	The first for keysym definitions allow me to quickly bring some windows
		819	in the layout I like most. Ion users might start laughing but will stop
		820	immediately when I tell them that I use my own Fvwm2 module for much the
		821	same effect as Ion provides, and I only very rarely use the above key
		822	combinations :->
		823
		824	=head3 Why doesn't rxvt-unicode read my resources?
		825
		826	Well, why, indeed? It does, in a way very similar to other X
		827	applications. Most importantly, this means that if you or your OS loads
		828	resources into the X display (the right way to do it), rxvt-unicode will
		829	ignore any resource files in your home directory. It will only read
		830	F<$HOME/.Xdefaults> when no resources are attached to the display.
		831
		832	If you have or use an F<$HOME/.Xresources> file, chances are that
		833	resources are loaded into your X-server. In this case, you have to
		834	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		835
		836	Also consider the form resources have to use:
		837
		838	URxvt.resource: value
		839
		840	If you want to use another form (there are lots of different ways of
		841	specifying resources), make sure you understand whether and why it
		842	works. If unsure, use the form above.
		843
305	=item When I log-in to another system it tells me about missing terminfo data?	844	=head3 When I log-in to another system it tells me about missing terminfo data?
306		845
307	The terminal description used by rxvt-unicode is not as widely available	846	The terminal description used by rxvt-unicode is not as widely available
308	as that for xterm, or even rxvt (for which the same problem often arises).	847	as that for xterm, or even rxvt (for which the same problem often arises).
309		848
310	The correct solution for this problem is to install the terminfo, this can	849	The correct solution for this problem is to install the terminfo, this can
311	be done like this (with ncurses' infocmp):	850	be done like this (with ncurses' infocmp and works as user and admin):
312		851
313	REMOTE=remotesystem.domain	852	REMOTE=remotesystem.domain
314	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	853	infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
315		854
316	... or by installing rxvt-unicode normally on the remote system,	855	... or by installing rxvt-unicode normally on the remote system,
		856
		857	One some systems you might need to set C<$TERMINFO> to the full path of
		858	F<$HOME/.terminfo> for this to work.
317		859
318	If you cannot or do not want to do this, then you can simply set	860	If you cannot or do not want to do this, then you can simply set
319	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of	861	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
320	problems arising, which includes wrong keymapping, less and different	862	problems arising, which includes wrong keymapping, less and different
321	colours and some refresh errors in fullscreen applications. It's a nice	863	colours and some refresh errors in fullscreen applications. It's a nice
…		…
326	resource to set it:	868	resource to set it:
327		869
328	URxvt.termName: rxvt	870	URxvt.termName: rxvt
329		871
330	If you don't plan to use B<rxvt> (quite common...) you could also replace	872	If you don't plan to use B<rxvt> (quite common...) you could also replace
331	the rxvt terminfo file with the rxvt-unicode one.	873	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
332		874
333	=item C<tic> outputs some error when compiling the terminfo entry.	875	=head3 C<tic> outputs some error when compiling the terminfo entry.
334		876
335	Most likely it's the empty definition for C<enacs=>. Just replace it by	877	Most likely it's the empty definition for C<enacs=>. Just replace it by
336	C<enacs=\E[0@> and try again.	878	C<enacs=\E[0@> and try again.
337		879
338	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	880	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
339		881
		882	See next entry.
		883
340	=item I need a termcap file entry.	884	=head3 I need a termcap file entry.
341		885
342	One reason you might want this is that some distributions or operating	886	One reason you might want this is that some distributions or operating
343	systems still compile some programs using the long-obsoleted termcap	887	systems still compile some programs using the long-obsoleted termcap
344	library (Fedora Core's bash is one example) and rely on a termcap entry	888	library (Fedora Core's bash is one example) and rely on a termcap entry
345	for C<rxvt-unicode>.	889	for C<rxvt-unicode>.
346		890
347	You could use rxvt's termcap entry with resonable results in many cases.	891	You could use rxvt's termcap entry with reasonable results in many cases.
348	You can also create a termcap entry by using terminfo's infocmp program	892	You can also create a termcap entry by using terminfo's infocmp program
349	like this:	893	like this:
350		894
351	infocmp -C rxvt-unicode	895	infocmp -C rxvt-unicode
352		896
…		…
371	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	915	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
372	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	916	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
373	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	917	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
374	:vs=\E[?25h:	918	:vs=\E[?25h:
375		919
376	=item Why does C<ls> no longer have coloured output?	920	=head3 Why does C<ls> no longer have coloured output?
377		921
378	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	922	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
379	decide wether a terminal has colour, but uses it's own configuration	923	decide whether a terminal has colour, but uses its own configuration
380	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	924	file. Needless to say, C<rxvt-unicode> is not in its default file (among
381	with most other terminals supporting colour). Either add:	925	with most other terminals supporting colour). Either add:
382		926
383	TERM rxvt-unicode	927	TERM rxvt-unicode
384		928
385	to C</etc/DIR_COLORS> or simply add:	929	to C</etc/DIR_COLORS> or simply add:
386		930
387	alias ls='ls --color=auto'	931	alias ls='ls --color=auto'
388		932
389	to your C<.profile> or C<.bashrc>.	933	to your C<.profile> or C<.bashrc>.
390		934
391	=item Why doesn't vim/emacs etc. use the 88 colour mode?	935	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
392		936
		937	See next entry.
		938
393	=item Why doesn't vim/emacs etc. make use of italic?	939	=head3 Why doesn't vim/emacs etc. make use of italic?
394		940
		941	See next entry.
		942
395	=item Why are the secondary screen-related options not working properly?	943	=head3 Why are the secondary screen-related options not working properly?
396		944
397	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	945	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
398	distributions (most notably Debian GNU/Linux) break rxvt-unicode	946	distributions (most notably Debian GNU/Linux) break rxvt-unicode
399	by setting C<TERM> to C<rxvt>, which doesn't have these extra	947	by setting C<TERM> to C<rxvt>, which doesn't have these extra
400	features. Unfortunately, some of these (most notably, again, Debian	948	features. Unfortunately, some of these (most notably, again, Debian
401	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	949	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
402	file, so you will need to install it on your own (See the question B<When	950	file, so you will need to install it on your own (See the question B<When
403	I log-in to another system it tells me about missing terminfo data?> on	951	I log-in to another system it tells me about missing terminfo data?> on
404	how to do this).	952	how to do this).
405		953
406	=item My numerical keypad acts weird and generates differing output?
407		954
408	Some Debian GNUL/Linux users seem to have this problem, although no	955	=head2 Encoding / Locale / Input Method Issues
409	specific details were reported so far. It is possible that this is caused
410	by the wrong C<TERM> setting, although the details of wether and how
411	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
412	keymap. See the answer to the previous question, and please report if that
413	helped.
414		956
415	=item Rxvt-unicode does not seem to understand the selected encoding?	957	=head3 Rxvt-unicode does not seem to understand the selected encoding?
416		958
		959	See next entry.
		960
417	=item Unicode does not seem to work?	961	=head3 Unicode does not seem to work?
418		962
419	If you encounter strange problems like typing an accented character but	963	If you encounter strange problems like typing an accented character but
420	getting two unrelated other characters or similar, or if program output is	964	getting two unrelated other characters or similar, or if program output is
421	subtly garbled, then you should check your locale settings.	965	subtly garbled, then you should check your locale settings.
422		966
423	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	967	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
424	programs. Often rxvt-unicode is started in the C<C> locale, while the	968	programs running in it. Often rxvt-unicode is started in the C<C> locale,
425	login script running within the rxvt-unicode window changes the locale to	969	while the login script running within the rxvt-unicode window changes the
426	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.	970	locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is
		971	not going to work, and is the most common cause for problems.
427		972
428	The best thing is to fix your startup environment, as you will likely run	973	The best thing is to fix your startup environment, as you will likely run
429	into other problems. If nothing works you can try this in your .profile.	974	into other problems. If nothing works you can try this in your .profile.
430		975
431	printf '\e]701;%s\007' "$LC_CTYPE"	976	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
432		977
433	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	978	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
434	supported on your systems. Some systems have a C<locale> command which	979	supported on your systems. Some systems have a C<locale> command which
435	displays this (also, C<perl -e0> can be used to check locale settings, as	980	displays this (also, C<perl -e0> can be used to check locale settings, as
436	it will complain loudly if it cannot set the locale). If it displays something	981	it will complain loudly if it cannot set the locale). If it displays something
…		…
442		987
443	If nothing works and you are sure that everything is set correctly then	988	If nothing works and you are sure that everything is set correctly then
444	you will need to remember a little known fact: Some programs just don't	989	you will need to remember a little known fact: Some programs just don't
445	support locales :(	990	support locales :(
446		991
447	=item Why do some characters look so much different than others?	992	=head3 How does rxvt-unicode determine the encoding to use?
448		993
449	=item How does rxvt-unicode choose fonts?	994	See next entry.
450		995
451	Most fonts do not contain the full range of Unicode, which is	996	=head3 Is there an option to switch encodings?
452	fine. Chances are that the font you (or the admin/package maintainer of
453	your system/os) have specified does not cover all the characters you want
454	to display.
455		997
456	B<rxvt-unicode> makes a best-effort try at finding a replacement	998	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
457	font. Often the result is fine, but sometimes the chosen font looks	999	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
458	bad/ugly/wrong. Some fonts have totally strange characters that don't	1000	UTF-8 or any other encodings with respect to terminal I/O.
459	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
460	intelligence to detect that a specific glyph is wrong: it has to believe
461	the font that the characters it claims to contain indeed look correct.
462		1001
463	In that case, select a font of your taste and add it to the font list,	1002	The reasons is that there exists a perfectly fine mechanism for selecting
464	e.g.:	1003	the encoding, doing I/O and (most important) communicating this to all
465		1004	applications so everybody agrees on character properties such as width
466	@@RXVT_NAME@@ -fn basefont,font2,font3...	1005	and code number. This mechanism is the I<locale>. Applications not using
467		1006	that info will have problems (for example, C<xterm> gets the width of
468	When rxvt-unicode sees a character, it will first look at the base	1007	characters wrong as it uses its own, locale-independent table under all
469	font. If the base font does not contain the character, it will go to the
470	next font, and so on. Specifying your own fonts will also speed up this
471	search and use less resources within rxvt-unicode and the X-server.
472
473	The only limitation is that none of the fonts may be larger than the base
474	font, as the base font defines the terminal character cell size, which
475	must be the same due to the way terminals work.
476
477	=item Why do some chinese characters look so different than others?
478
479	This is because there is a difference between script and language --
480	rxvt-unicode does not know which language the text that is output is,
481	as it only knows the unicode character codes. If rxvt-unicode first
482	sees a japanese/chinese character, it might choose a japanese font for
483	display. Subsequent japanese characters will use that font. Now, many
484	chinese characters aren't represented in japanese fonts, so when the first
485	non-japanese character comes up, rxvt-unicode will look for a chinese font
486	-- unfortunately at this point, it will still use the japanese font for
487	chinese characters that are also in the japanese font.
488
489	The workaround is easy: just tag a chinese font at the end of your font
490	list (see the previous question). The key is to view the font list as
491	a preference list: If you expect more japanese, list a japanese font
492	first. If you expect more chinese, put a chinese font first.
493
494	In the future it might be possible to switch language preferences at
495	runtime (the internal data structure has no problem with using different
496	fonts for the same character at the same time, but no interface for this
497	has been designed yet).
498
499	Until then, you might get away with switching fonts at runtime (see L<Can
500	I switch the fonts at runtime?> later in this document).
501
502	=item Why does rxvt-unicode sometimes leave pixel droppings?
503
504	Most fonts were not designed for terminal use, which means that character
505	size varies a lot. A font that is otherwise fine for terminal use might
506	contain some characters that are simply too wide. Rxvt-unicode will avoid
507	these characters. For characters that are just "a bit" too wide a special
508	"careful" rendering mode is used that redraws adjacent characters.
509
510	All of this requires that fonts do not lie about character sizes,
511	however: Xft fonts often draw glyphs larger than their acclaimed bounding
512	box, and rxvt-unicode has no way of detecting this (the correct way is to
513	ask for the character bounding box, which unfortunately is wrong in these
514	cases).	1008	locales).
515		1009
516	It's not clear (to me at least), wether this is a bug in Xft, freetype,	1010	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
517	or the respective font. If you encounter this problem you might try using	1011	programs doing the same (that is, most) will automatically agree in the
518	the C<-lsp> option to give the font more height. If that doesn't work, you	1012	interpretation of characters.
519	might be forced to use a different font.
520		1013
521	All of this is not a problem when using X11 core fonts, as their bounding	1014	Unfortunately, there is no system-independent way to select locales, nor
522	box data is correct.	1015	is there a standard on how locale specifiers will look like.
523		1016
524	=item On Solaris 9, many line-drawing characters are too wide.	1017	On most systems, the content of the C<LC_CTYPE> environment variable
		1018	contains an arbitrary string which corresponds to an already-installed
		1019	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1020	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1021	(i.e. C<de> or C<german>) are also common.
525		1022
526	Seems to be a known bug, read	1023	Rxvt-unicode ignores all other locale categories, and except for
527	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1024	the encoding, ignores country or language-specific settings,
528	following ugly workaround to get non-double-wide-characters working:	1025	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		1026	rxvt-unicode.
529		1027
530	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1028	If you want to use a specific encoding you have to make sure you start
		1029	rxvt-unicode with the correct C<LC_CTYPE> category.
531		1030
532	=item My Compose (Multi_key) key is no longer working.	1031	=head3 Can I switch locales at runtime?
533		1032
534	The most common causes for this are that either your locale is not set	1033	Yes, using an escape sequence. Try something like this, which sets
535	correctly, or you specified a B<preeditStyle> that is not supported by	1034	rxvt-unicode's idea of C<LC_CTYPE>.
536	your input method. For example, if you specified B<OverTheSpot> and
537	your input method (e.g. the default input method handling Compose keys)
538	does not support this (for instance because it is not visual), then
539	rxvt-unicode will continue without an input method.
540		1035
541	In this case either do not specify a B<preeditStyle> or specify more than	1036	printf '\33]701;%s\007' ja_JP.SJIS
542	one pre-edit style, such as B<OverTheSpot,Root,None>.
543		1037
544	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755	1038	See also the previous answer.
545		1039
546	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on	1040	Sometimes this capability is rather handy when you want to work in
547	international keyboards) or simply use ISO 14755 support to your	1041	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
548	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other	1042	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
549	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape	1043	first switches to a locale supported by xjdic and back later:
550	character and so on.
551		1044
552	=item How can I keep rxvt-unicode from using reverse video so much?	1045	printf '\33]701;%s\007' ja_JP.SJIS
		1046	xjdic -js
		1047	printf '\33]701;%s\007' de_DE.UTF-8
553		1048
554	First of all, make sure you are running with the right terminal settings	1049	You can also use xterm's C<luit> program, which usually works fine, except
555	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then	1050	for some locales where character width differs between program- and
556	make sure you have specified colours for italic and bold, as otherwise	1051	rxvt-unicode-locales.
557	rxvt-unicode might use reverse video to simulate the effect:
558		1052
559	URxvt.colorBD: white	1053	=head3 I have problems getting my input method working.
560	URxvt.colorIT: green
561		1054
562	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?	1055	Try a search engine, as this is slightly different for every input method server.
563		1056
564	For some unexplainable reason, some rare programs assume a very weird	1057	Here is a checklist:
565	colour palette when confronted with a terminal with more than the standard
566	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
567	these programs not to assume non-ISO colours without very good reasons.
568		1058
569	In the meantime, you can either edit your C<rxvt-unicode> terminfo	1059	=over 4
570	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
571	fix colours but keep you from using other rxvt-unicode features.
572		1060
		1061	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		1062
		1063	Try C<locale -a> or check the documentation for your OS.
		1064
		1065	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		1066
		1067	For example, B<kinput2> does not support UTF-8 locales, you should use
		1068	C<ja_JP.EUC-JP> or equivalent.
		1069
		1070	=item - Make sure your XIM server is actually running.
		1071
		1072	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		1073
		1074	When you want to use e.g. B<kinput2>, it must be set to
		1075	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
		1076	method servers are running with this command:
		1077
		1078	xprop -root XIM_SERVERS
		1079
		1080	=item
		1081
		1082	=back
		1083
		1084	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		1085
		1086	You can specify separate locales for the input method and the rest of the
		1087	terminal, using the resource C<imlocale>:
		1088
		1089	URxvt.imlocale: ja_JP.EUC-JP
		1090
		1091	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1092	use your input method. Please note, however, that, depending on your Xlib
		1093	version, you may not be able to input characters outside C<EUC-JP> in a
		1094	normal way then, as your input method limits you.
		1095
		1096	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		1097
		1098	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1099	design. Applications can avoid some crashes at the expense of memory
		1100	leaks, and Input Methods can avoid some crashes by careful ordering at
		1101	exit time. B<kinput2> (and derived input methods) generally succeeds,
		1102	while B<SCIM> (or similar input methods) fails. In the end, however,
		1103	crashes cannot be completely avoided even if both sides cooperate.
		1104
		1105	So the only workaround is not to kill your Input Method Servers.
		1106
		1107
		1108	=head2 Operating Systems / Package Maintaining
		1109
		1110	=head3 I am using Debian GNU/Linux and have a problem...
		1111
		1112	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1113	patches that considerably change the behaviour of rxvt-unicode (but
		1114	unfortunately this notice has been removed). Before reporting a bug to
		1115	the original rxvt-unicode author please download and install the genuine
		1116	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1117	the problem. If you cannot, chances are that the problems are specific to
		1118	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1119	Tracking System (use C<reportbug> to report the bug).
		1120
		1121	For other problems that also affect the Debian package, you can and
		1122	probably should use the Debian BTS, too, because, after all, it's also a
		1123	bug in the Debian version and it serves as a reminder for other users that
		1124	might encounter the same issue.
		1125
		1126	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1127
		1128	You should build one binary with the default options. F<configure>
		1129	now enables most useful options, and the trend goes to making them
		1130	runtime-switchable, too, so there is usually no drawback to enabling them,
		1131	except higher disk and possibly memory usage. The perl interpreter should
		1132	be enabled, as important functionality (menus, selection, likely more in
		1133	the future) depends on it.
		1134
		1135	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		1136	system-wide (except maybe with C<defaults>). This will result in useful
		1137	behaviour. If your distribution aims at low memory, add an empty
		1138	C<perl-ext-common> resource to the app-defaults file. This will keep the
		1139	perl interpreter disabled until the user enables it.
		1140
		1141	If you can/want build more binaries, I recommend building a minimal
		1142	one with C<--disable-everything> (very useful) and a maximal one with
		1143	C<--enable-everything> (less useful, it will be very big due to a lot of
		1144	encodings built-in that increase download times and are rarely used).
		1145
		1146	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1147
		1148	It should be, starting with release 7.1. You are encouraged to properly
		1149	install urxvt with privileges necessary for your OS now.
		1150
		1151	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1152	into a helper process for privileged operations (pty handling on some
		1153	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1154	immediately. This is much safer than most other terminals that keep
		1155	privileges while running (but is more relevant to urxvt, as it contains
		1156	things as perl interpreters, which might be "helpful" to attackers).
		1157
		1158	This forking is done as the very first within main(), which is very early
		1159	and reduces possible bugs to initialisation code run before main(), or
		1160	things like the dynamic loader of your system, which should result in very
		1161	little risk.
		1162
573	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	1163	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
574		1164
575	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1165	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
576	in your compile environment, or an implementation that implements it,	1166	in your compile environment, or an implementation that implements it,
577	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1167	whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
578	B<wchar_t> is represented as unicode.	1168	B<wchar_t> is represented as unicode.
579		1169
580	As you might have guessed, FreeBSD does neither define this symobl nor	1170	As you might have guessed, FreeBSD does neither define this symbol nor
581	does it support it. Instead, it uses it's own internal representation of	1171	does it support it. Instead, it uses its own internal representation of
582	B<wchar_t>. This is, of course, completely fine with respect to standards.	1172	B<wchar_t>. This is, of course, completely fine with respect to standards.
583		1173
584	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and	1174	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
585	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.	1175	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
586		1176
…		…
600		1190
601	The rxvt-unicode author insists that the right way to fix this is in the	1191	The rxvt-unicode author insists that the right way to fix this is in the
602	system libraries once and for all, instead of forcing every app to carry	1192	system libraries once and for all, instead of forcing every app to carry
603	complete replacements for them :)	1193	complete replacements for them :)
604		1194
605	=item I use Solaris 9 and it doesn't compile/work/etc.
606
607	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
608	problems with C<wcwidth> and a compile problem.
609
610	=item How can I use rxvt-unicode under cygwin?	1195	=head3 How can I use rxvt-unicode under cygwin?
611		1196
612	rxvt-unicode should compile and run out of the box on cygwin, using	1197	rxvt-unicode should compile and run out of the box on cygwin, using
613	the X11 libraries that come with cygwin. libW11 emulation is no	1198	the X11 libraries that come with cygwin. libW11 emulation is no
614	longer supported (and makes no sense, either, as it only supported a	1199	longer supported (and makes no sense, either, as it only supported a
615	single font). I recommend starting the X-server in C<-multiwindow> or	1200	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
618		1203
619	At the time of this writing, cygwin didn't seem to support any multi-byte	1204	At the time of this writing, cygwin didn't seem to support any multi-byte
620	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1205	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
621	to 8-bit encodings.	1206	to 8-bit encodings.
622		1207
623	=item How does rxvt-unicode determine the encoding to use?	1208	=head3 Character widths are not correct.
624		1209
625	=item Is there an option to switch encodings?	1210	urxvt uses the system wcwidth function to know the information about
		1211	the width of characters, so on systems with incorrect locale data you
		1212	will likely get bad results. Two notorious examples are Solaris 9,
		1213	where single-width characters like U+2514 are reported as double-width,
		1214	and Darwin 8, where combining chars are reported having width 1.
626		1215
627	Unlike some other terminals, rxvt-unicode has no encoding switch, and no	1216	The solution is to upgrade your system or switch to a better one. A
628	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about	1217	possibly working workaround is to use a wcwidth implementation like
629	UTF-8 or any other encodings with respect to terminal I/O.
630		1218
631	The reasons is that there exists a perfectly fine mechanism for selecting	1219	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
632	the encoding, doing I/O and (most important) communicating this to all
633	applications so everybody agrees on character properties such as width
634	and code number. This mechanism is the I<locale>. Applications not using
635	that info will have problems (for example, C<xterm> gets the width of
636	characters wrong as it uses it's own, locale-independent table under all
637	locales).
638		1220
639	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
640	programs doing the same (that is, most) will automatically agree in the
641	interpretation of characters.
642
643	Unfortunately, there is no system-independent way to select locales, nor
644	is there a standard on how locale specifiers will look like.
645
646	On most systems, the content of the C<LC_CTYPE> environment variable
647	contains an arbitrary string which corresponds to an already-installed
648	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
649	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
650	(i.e. C<de> or C<german>) are also common.
651
652	Rxvt-unicode ignores all other locale categories, and except for
653	the encoding, ignores country or language-specific settings,
654	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
655	rxvt-unicode.
656
657	If you want to use a specific encoding you have to make sure you start
658	rxvt-unicode with the correct C<LC_CTYPE> category.
659
660	=item Can I switch locales at runtime?
661
662	Yes, using an escape sequence. Try something like this, which sets
663	rxvt-unicode's idea of C<LC_CTYPE>.
664
665	printf '\e]701;%s\007' ja_JP.SJIS
666
667	See also the previous answer.
668
669	Sometimes this capability is rather handy when you want to work in
670	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
671	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
672	first switches to a locale supported by xjdic and back later:
673
674	printf '\e]701;%s\007' ja_JP.SJIS
675	xjdic -js
676	printf '\e]701;%s\007' de_DE.UTF-8
677
678	You can also use xterm's C<luit> program, which usually works fine, except
679	for some locales where character width differs between program- and
680	rxvt-unicode-locales.
681
682	=item Can I switch the fonts at runtime?
683
684	Yes, using an escape sequence. Try something like this, which has the same
685	effect as using the C<-fn> switch, and takes effect immediately:
686
687	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
688
689	This is useful if you e.g. work primarily with japanese (and prefer a
690	japanese font), but you have to switch to chinese temporarily, where
691	japanese fonts would only be in your way.
692
693	You can think of this as a kind of manual ISO-2022 switching.
694
695	=item Why do italic characters look as if clipped?
696
697	Many fonts have difficulties with italic characters and hinting. For
698	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
699	Mono> completely fails in it's italic face. A workaround might be to
700	enable freetype autohinting, i.e. like this:
701
702	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
703	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
704
705	=item My input method wants <some encoding> but I want UTF-8, what can I do?
706
707	You can specify separate locales for the input method and the rest of the
708	terminal, using the resource C<imlocale>:
709
710	URxvt.imlocale: ja_JP.EUC-JP
711
712	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
713	use your input method. Please note, however, that you will not be able to
714	input characters outside C<EUC-JP> in a normal way then, as your input
715	method limits you.
716
717	=item Rxvt-unicode crashes when the X Input Method changes or exits.
718
719	Unfortunately, this is unavoidable, as the XIM protocol is racy by
720	design. Applications can avoid some crashes at the expense of memory
721	leaks, and Input Methods can avoid some crashes by careful ordering at
722	exit time. B<kinput2> (and derived input methods) generally succeeds,
723	while B<SCIM> (or similar input methods) fails. In the end, however,
724	crashes cannot be completely avoided even if both sides cooperate.
725
726	So the only workaround is not to kill your Input Method Servers.
727
728	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
729
730	Rxvt-unicode tries to obey the rule of not charging you for something you
731	don't use. One thing you should try is to configure out all settings that
732	you don't need, for example, Xft support is a resource hog by design,
733	when used. Compiling it out ensures that no Xft font will be loaded
734	accidentally when rxvt-unicode tries to find a font for your characters.
735
736	Also, many people (me included) like large windows and even larger
737	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
738	6 bytes per screen cell. For a 160x?? window this amounts to almost a
739	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
740	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
741	rxvt-unicode then uses 8 bytes per screen cell.
742
743	=item Can I speed up Xft rendering somehow?
744
745	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
746	it is simply slow. If you still want Xft fonts you might try to disable
747	antialiasing (by appending C<:antialias=false>), which saves lots of
748	memory and also speeds up rendering considerably.
749
750	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
751
752	Rxvt-unicode will use whatever you specify as a font. If it needs to
753	fall back to it's default font search list it will prefer X11 core
754	fonts, because they are small and fast, and then use Xft fonts. It has
755	antialiasing disabled for most of them, because the author thinks they
756	look best that way.
757
758	If you want antialiasing, you have to specify the fonts manually.
759
760	=item Mouse cut/paste suddenly no longer works.
761
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
768	=item What's with this bold/blink stuff?
769
770	If no bold colour is set via C<colorBD:>, bold will invert text using the
771	standard foreground colour.
772
773	For the standard background colour, blinking will actually make the
774	text blink when compiled with C<--enable-blinking>. with standard
775	colours. Without C<--enable-blinking>, the blink attribute will be
776	ignored.
777
778	On ANSI colours, bold/blink attributes are used to set high-intensity
779	foreground/background colors.
780
781	color0-7 are the low-intensity colors.
782
783	color8-15 are the corresponding high-intensity colors.
784
785	=item I don't like the screen colors. How do I change them?
786
787	You can change the screen colors at run-time using F<~/.Xdefaults>
788	resources (or as long-options).
789
790	Here are values that are supposed to resemble a VGA screen,
791	including the murky brown that passes for low-intensity yellow:
792
793	URxvt.color0: #000000
794	URxvt.color1: #A80000
795	URxvt.color2: #00A800
796	URxvt.color3: #A8A800
797	URxvt.color4: #0000A8
798	URxvt.color5: #A800A8
799	URxvt.color6: #00A8A8
800	URxvt.color7: #A8A8A8
801
802	URxvt.color8: #000054
803	URxvt.color9: #FF0054
804	URxvt.color10: #00FF54
805	URxvt.color11: #FFFF54
806	URxvt.color12: #0000FF
807	URxvt.color13: #FF00FF
808	URxvt.color14: #00FFFF
809	URxvt.color15: #FFFFFF
810
811	And here is a more complete set of non-standard colors described (not by
812	me) as "pretty girly".
813
814	URxvt.cursorColor: #dc74d1
815	URxvt.pointerColor: #dc74d1
816	URxvt.background: #0e0e0e
817	URxvt.foreground: #4ad5e1
818	URxvt.color0: #000000
819	URxvt.color8: #8b8f93
820	URxvt.color1: #dc74d1
821	URxvt.color9: #dc74d1
822	URxvt.color2: #0eb8c7
823	URxvt.color10: #0eb8c7
824	URxvt.color3: #dfe37e
825	URxvt.color11: #dfe37e
826	URxvt.color5: #9e88f0
827	URxvt.color13: #9e88f0
828	URxvt.color6: #73f7ff
829	URxvt.color14: #73f7ff
830	URxvt.color7: #e1dddd
831	URxvt.color15: #e1dddd
832
833	=item How can I start @@RXVT_NAME@@d in a race-free way?
834
835	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
836	display, create the listening socket and then fork.
837
838	=item What's with the strange Backspace/Delete key behaviour?
839
840	Assuming that the physical Backspace key corresponds to the
841	BackSpace keysym (not likely for Linux ... see the following
842	question) there are two standard values that can be used for
843	Backspace: C<^H> and C<^?>.
844
845	Historically, either value is correct, but rxvt-unicode adopts the debian
846	policy of using C<^?> when unsure, because it's the one only only correct
847	choice :).
848
849	Rxvt-unicode tries to inherit the current stty settings and uses the value
850	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
851	started from a terminal (say, from a menu or by remote shell), then the
852	system value of `erase', which corresponds to CERASE in <termios.h>, will
853	be used (which may not be the same as your stty setting).
854
855	For starting a new rxvt-unicode:
856
857	# use Backspace = ^H
858	$ stty erase ^H
859	$ @@RXVT_NAME@@
860
861	# use Backspace = ^?
862	$ stty erase ^?
863	$ @@RXVT_NAME@@
864
865	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
866
867	For an existing rxvt-unicode:
868
869	# use Backspace = ^H
870	$ stty erase ^H
871	$ echo -n "^[[36h"
872
873	# use Backspace = ^?
874	$ stty erase ^?
875	$ echo -n "^[[36l"
876
877	This helps satisfy some of the Backspace discrepancies that occur, but
878	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
879	properly reflects that.
880
881	The Delete key is a another casualty of the ill-defined Backspace problem.
882	To avoid confusion between the Backspace and Delete keys, the Delete
883	key has been assigned an escape sequence to match the vt100 for Execute
884	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
885
886	Some other Backspace problems:
887
888	some editors use termcap/terminfo,
889	some editors (vim I'm told) expect Backspace = ^H,
890	GNU Emacs (and Emacs-like editors) use ^H for help.
891
892	Perhaps someday this will all be resolved in a consistent manner.
893
894	=item I don't like the key-bindings. How do I change them?
895
896	There are some compile-time selections available via configure. Unless
897	you have run "configure" with the C<--disable-resources> option you can
898	use the `keysym' resource to alter the keystrings associated with keysyms.
899
900	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
901
902	URxvt.keysym.Home: \033[1~
903	URxvt.keysym.End: \033[4~
904	URxvt.keysym.C-apostrophe: \033<C-'>
905	URxvt.keysym.C-slash: \033<C-/>
906	URxvt.keysym.C-semicolon: \033<C-;>
907	URxvt.keysym.C-grave: \033<C-`>
908	URxvt.keysym.C-comma: \033<C-,>
909	URxvt.keysym.C-period: \033<C-.>
910	URxvt.keysym.C-0x60: \033<C-`>
911	URxvt.keysym.C-Tab: \033<C-Tab>
912	URxvt.keysym.C-Return: \033<C-Return>
913	URxvt.keysym.S-Return: \033<S-Return>
914	URxvt.keysym.S-space: \033<S-Space>
915	URxvt.keysym.M-Up: \033<M-Up>
916	URxvt.keysym.M-Down: \033<M-Down>
917	URxvt.keysym.M-Left: \033<M-Left>
918	URxvt.keysym.M-Right: \033<M-Right>
919	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
920	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
921	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
922
923	See some more examples in the documentation for the B<keysym> resource.
924
925	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
926	How do I make use of them? For example, the Sun Keyboard type 4
927	has the following mappings that rxvt-unicode doesn't recognize.
928
929	KP_Insert == Insert
930	F22 == Print
931	F27 == Home
932	F29 == Prior
933	F33 == End
934	F35 == Next
935
936	Rather than have rxvt-unicode try to accommodate all the various possible
937	keyboard mappings, it is better to use `xmodmap' to remap the keys as
938	required for your particular machine.
939
940	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
941	I need this to decide about setting colors etc.
942
943	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
944	check and see if that is set. Note that several programs, JED, slrn,
945	Midnight Commander automatically check this variable to decide whether or
946	not to use color.
947
948	=item How do I set the correct, full IP address for the DISPLAY variable?
949
950	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
951	insecure mode then it is possible to use the following shell script
952	snippets to correctly set the display. If your version of rxvt-unicode
953	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
954	the COLORTERM variable can be used to distinguish rxvt-unicode from a
955	regular xterm.
956
957	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
958	snippets:
959
960	# Bourne/Korn/POSIX family of shells:
961	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
962	if [ ${TERM:-foo} = xterm ]; then
963	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
964	echo -n '^[Z'
965	read term_id
966	stty icanon echo
967	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
968	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
969	read DISPLAY # set it in our local shell
970	fi
971	fi
972
973	=item How do I compile the manual pages for myself?
974
975	You need to have a recent version of perl installed as F</usr/bin/perl>,
976	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
977	the doc subdirectory and enter C<make alldoc>.
978
979	=item My question isn't answered here, can I ask a human?
980
981	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
982	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
983	interested in learning about new and exciting problems (but not FAQs :).
984
985	=back
986
987	=head1 RXVT TECHNICAL REFERENCE	1221	=head1 RXVT-UNICODE TECHNICAL REFERENCE
988
989	=head1 DESCRIPTION
990		1222
991	The rest of this document describes various technical aspects of	1223	The rest of this document describes various technical aspects of
992	B<rxvt-unicode>. First the description of supported command sequences,	1224	B<rxvt-unicode>. First the description of supported command sequences,
993	followed by pixmap support and last by a description of all features	1225	followed by pixmap support and last by a description of all features
994	selectable at C<configure> time.	1226	selectable at C<configure> time.
995		1227
996	=head1 Definitions	1228	=head2 Definitions
997		1229
998	=over 4	1230	=over 4
999		1231
1000	=item B<< C<c> >>	1232	=item B<< C<c> >>
1001		1233
…		…
1019		1251
1020	A text parameter composed of printable characters.	1252	A text parameter composed of printable characters.
1021		1253
1022	=back	1254	=back
1023		1255
1024	=head1 Values	1256	=head2 Values
1025		1257
1026	=over 4	1258	=over 4
1027		1259
1028	=item B<< C<ENQ> >>	1260	=item B<< C<ENQ> >>
1029		1261
…		…
1072		1304
1073	Space Character	1305	Space Character
1074		1306
1075	=back	1307	=back
1076		1308
1077	=head1 Escape Sequences	1309	=head2 Escape Sequences
1078		1310
1079	=over 4	1311	=over 4
1080		1312
1081	=item B<< C<ESC # 8> >>	1313	=item B<< C<ESC # 8> >>
1082		1314
…		…
1180		1412
1181	=back	1413	=back
1182		1414
1183	X<CSI>	1415	X<CSI>
1184		1416
1185	=head1 CSI (Command Sequence Introducer) Sequences	1417	=head2 CSI (Command Sequence Introducer) Sequences
1186		1418
1187	=over 4	1419	=over 4
1188		1420
1189	=item B<< C<ESC [ Ps @> >>	1421	=item B<< C<ESC [ Ps @> >>
1190		1422
…		…
1460		1692
1461	=back	1693	=back
1462		1694
1463	X<PrivateModes>	1695	X<PrivateModes>
1464		1696
1465	=head1 DEC Private Modes	1697	=head2 DEC Private Modes
1466		1698
1467	=over 4	1699	=over 4
1468		1700
1469	=item B<< C<ESC [ ? Pm h> >>	1701	=item B<< C<ESC [ ? Pm h> >>
1470		1702
…		…
1486		1718
1487	Toggle DEC Private Mode Values (rxvt extension). I<where>	1719	Toggle DEC Private Mode Values (rxvt extension). I<where>
1488		1720
1489	=over 4	1721	=over 4
1490		1722
1491	=item B<< C<Ps = 1> >> (DECCKM)	1723	=item B<< C<Pm = 1> >> (DECCKM)
1492		1724
1493	=begin table	1725	=begin table
1494		1726
1495	B<< C<h> >> Application Cursor Keys	1727	B<< C<h> >> Application Cursor Keys
1496	B<< C<l> >> Normal Cursor Keys	1728	B<< C<l> >> Normal Cursor Keys
1497		1729
1498	=end table	1730	=end table
1499		1731
1500	=item B<< C<Ps = 2> >> (ANSI/VT52 mode)	1732	=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1501		1733
1502	=begin table	1734	=begin table
1503		1735
1504	B<< C<h> >> Enter VT52 mode	1736	B<< C<h> >> Enter VT52 mode
1505	B<< C<l> >> Enter VT52 mode	1737	B<< C<l> >> Enter VT52 mode
1506		1738
1507	=end table	1739	=end table
1508		1740
1509	=item B<< C<Ps = 3> >>	1741	=item B<< C<Pm = 3> >>
1510		1742
1511	=begin table	1743	=begin table
1512		1744
1513	B<< C<h> >> 132 Column Mode (DECCOLM)	1745	B<< C<h> >> 132 Column Mode (DECCOLM)
1514	B<< C<l> >> 80 Column Mode (DECCOLM)	1746	B<< C<l> >> 80 Column Mode (DECCOLM)
1515		1747
1516	=end table	1748	=end table
1517		1749
1518	=item B<< C<Ps = 4> >>	1750	=item B<< C<Pm = 4> >>
1519		1751
1520	=begin table	1752	=begin table
1521		1753
1522	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)	1754	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1523	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)	1755	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1524		1756
1525	=end table	1757	=end table
1526		1758
1527	=item B<< C<Ps = 5> >>	1759	=item B<< C<Pm = 5> >>
1528		1760
1529	=begin table	1761	=begin table
1530		1762
1531	B<< C<h> >> Reverse Video (DECSCNM)	1763	B<< C<h> >> Reverse Video (DECSCNM)
1532	B<< C<l> >> Normal Video (DECSCNM)	1764	B<< C<l> >> Normal Video (DECSCNM)
1533		1765
1534	=end table	1766	=end table
1535		1767
1536	=item B<< C<Ps = 6> >>	1768	=item B<< C<Pm = 6> >>
1537		1769
1538	=begin table	1770	=begin table
1539		1771
1540	B<< C<h> >> Origin Mode (DECOM)	1772	B<< C<h> >> Origin Mode (DECOM)
1541	B<< C<l> >> Normal Cursor Mode (DECOM)	1773	B<< C<l> >> Normal Cursor Mode (DECOM)
1542		1774
1543	=end table	1775	=end table
1544		1776
1545	=item B<< C<Ps = 7> >>	1777	=item B<< C<Pm = 7> >>
1546		1778
1547	=begin table	1779	=begin table
1548		1780
1549	B<< C<h> >> Wraparound Mode (DECAWM)	1781	B<< C<h> >> Wraparound Mode (DECAWM)
1550	B<< C<l> >> No Wraparound Mode (DECAWM)	1782	B<< C<l> >> No Wraparound Mode (DECAWM)
1551		1783
1552	=end table	1784	=end table
1553		1785
1554	=item B<< C<Ps = 8> >> I<unimplemented>	1786	=item B<< C<Pm = 8> >> I<unimplemented>
1555		1787
1556	=begin table	1788	=begin table
1557		1789
1558	B<< C<h> >> Auto-repeat Keys (DECARM)	1790	B<< C<h> >> Auto-repeat Keys (DECARM)
1559	B<< C<l> >> No Auto-repeat Keys (DECARM)	1791	B<< C<l> >> No Auto-repeat Keys (DECARM)
1560		1792
1561	=end table	1793	=end table
1562		1794
1563	=item B<< C<Ps = 9> >> X10 XTerm	1795	=item B<< C<Pm = 9> >> X10 XTerm
1564		1796
1565	=begin table	1797	=begin table
1566		1798
1567	B<< C<h> >> Send Mouse X & Y on button press.	1799	B<< C<h> >> Send Mouse X & Y on button press.
1568	B<< C<l> >> No mouse reporting.	1800	B<< C<l> >> No mouse reporting.
1569		1801
1570	=end table	1802	=end table
1571		1803
1572	=item B<< C<Ps = 25> >>	1804	=item B<< C<Pm = 25> >>
1573		1805
1574	=begin table	1806	=begin table
1575		1807
1576	B<< C<h> >> Visible cursor {cnorm/cvvis}	1808	B<< C<h> >> Visible cursor {cnorm/cvvis}
1577	B<< C<l> >> Invisible cursor {civis}	1809	B<< C<l> >> Invisible cursor {civis}
1578		1810
1579	=end table	1811	=end table
1580		1812
1581	=item B<< C<Ps = 30> >>	1813	=item B<< C<Pm = 30> >>
1582		1814
1583	=begin table	1815	=begin table
1584		1816
1585	B<< C<h> >> scrollBar visisble	1817	B<< C<h> >> scrollBar visible
1586	B<< C<l> >> scrollBar invisisble	1818	B<< C<l> >> scrollBar invisible
1587		1819
1588	=end table	1820	=end table
1589		1821
1590	=item B<< C<Ps = 35> >> (B<rxvt>)	1822	=item B<< C<Pm = 35> >> (B<rxvt>)
1591		1823
1592	=begin table	1824	=begin table
1593		1825
1594	B<< C<h> >> Allow XTerm Shift+key sequences	1826	B<< C<h> >> Allow XTerm Shift+key sequences
1595	B<< C<l> >> Disallow XTerm Shift+key sequences	1827	B<< C<l> >> Disallow XTerm Shift+key sequences
1596		1828
1597	=end table	1829	=end table
1598		1830
1599	=item B<< C<Ps = 38> >> I<unimplemented>	1831	=item B<< C<Pm = 38> >> I<unimplemented>
1600		1832
1601	Enter Tektronix Mode (DECTEK)	1833	Enter Tektronix Mode (DECTEK)
1602		1834
1603	=item B<< C<Ps = 40> >>	1835	=item B<< C<Pm = 40> >>
1604		1836
1605	=begin table	1837	=begin table
1606		1838
1607	B<< C<h> >> Allow 80/132 Mode	1839	B<< C<h> >> Allow 80/132 Mode
1608	B<< C<l> >> Disallow 80/132 Mode	1840	B<< C<l> >> Disallow 80/132 Mode
1609		1841
1610	=end table	1842	=end table
1611		1843
1612	=item B<< C<Ps = 44> >> I<unimplemented>	1844	=item B<< C<Pm = 44> >> I<unimplemented>
1613		1845
1614	=begin table	1846	=begin table
1615		1847
1616	B<< C<h> >> Turn On Margin Bell	1848	B<< C<h> >> Turn On Margin Bell
1617	B<< C<l> >> Turn Off Margin Bell	1849	B<< C<l> >> Turn Off Margin Bell
1618		1850
1619	=end table	1851	=end table
1620		1852
1621	=item B<< C<Ps = 45> >> I<unimplemented>	1853	=item B<< C<Pm = 45> >> I<unimplemented>
1622		1854
1623	=begin table	1855	=begin table
1624		1856
1625	B<< C<h> >> Reverse-wraparound Mode	1857	B<< C<h> >> Reverse-wraparound Mode
1626	B<< C<l> >> No Reverse-wraparound Mode	1858	B<< C<l> >> No Reverse-wraparound Mode
1627		1859
1628	=end table	1860	=end table
1629		1861
1630	=item B<< C<Ps = 46> >> I<unimplemented>	1862	=item B<< C<Pm = 46> >> I<unimplemented>
1631		1863
1632	=item B<< C<Ps = 47> >>	1864	=item B<< C<Pm = 47> >>
1633		1865
1634	=begin table	1866	=begin table
1635		1867
1636	B<< C<h> >> Use Alternate Screen Buffer	1868	B<< C<h> >> Use Alternate Screen Buffer
1637	B<< C<l> >> Use Normal Screen Buffer	1869	B<< C<l> >> Use Normal Screen Buffer
1638		1870
1639	=end table	1871	=end table
1640		1872
1641	X<Priv66>	1873	X<Priv66>
1642		1874
1643	=item B<< C<Ps = 66> >>	1875	=item B<< C<Pm = 66> >>
1644		1876
1645	=begin table	1877	=begin table
1646		1878
1647	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>	1879	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1648	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>	1880	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1649		1881
1650	=end table	1882	=end table
1651		1883
1652	=item B<< C<Ps = 67> >>	1884	=item B<< C<Pm = 67> >>
1653		1885
1654	=begin table	1886	=begin table
1655		1887
1656	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>	1888	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1657	B<< C<l> >> Backspace key sends B<< C<DEL> >>	1889	B<< C<l> >> Backspace key sends B<< C<DEL> >>
1658		1890
1659	=end table	1891	=end table
1660		1892
1661	=item B<< C<Ps = 1000> >> (X11 XTerm)	1893	=item B<< C<Pm = 1000> >> (X11 XTerm)
1662		1894
1663	=begin table	1895	=begin table
1664		1896
1665	B<< C<h> >> Send Mouse X & Y on button press and release.	1897	B<< C<h> >> Send Mouse X & Y on button press and release.
1666	B<< C<l> >> No mouse reporting.	1898	B<< C<l> >> No mouse reporting.
1667		1899
1668	=end table	1900	=end table
1669		1901
1670	=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented>	1902	=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1671		1903
1672	=begin table	1904	=begin table
1673		1905
1674	B<< C<h> >> Use Hilite Mouse Tracking.	1906	B<< C<h> >> Use Hilite Mouse Tracking.
1675	B<< C<l> >> No mouse reporting.	1907	B<< C<l> >> No mouse reporting.
1676		1908
1677	=end table	1909	=end table
1678		1910
		1911	=item B<< C<Pm = 1002> >> (X11 XTerm)
		1912
		1913	=begin table
		1914
		1915	B<< C<h> >> Send Mouse X & Y on button press and release, and motion with a button pressed.
		1916	B<< C<l> >> No mouse reporting.
		1917
		1918	=end table
		1919
		1920	=item B<< C<Pm = 1003> >> (X11 XTerm)
		1921
		1922	=begin table
		1923
		1924	B<< C<h> >> Send Mouse X & Y on button press and release, and motion.
		1925	B<< C<l> >> No mouse reporting.
		1926
		1927	=end table
		1928
1679	=item B<< C<Ps = 1010> >> (B<rxvt>)	1929	=item B<< C<Pm = 1010> >> (B<rxvt>)
1680		1930
1681	=begin table	1931	=begin table
1682		1932
1683	B<< C<h> >> Don't scroll to bottom on TTY output	1933	B<< C<h> >> Don't scroll to bottom on TTY output
1684	B<< C<l> >> Scroll to bottom on TTY output	1934	B<< C<l> >> Scroll to bottom on TTY output
1685		1935
1686	=end table	1936	=end table
1687		1937
1688	=item B<< C<Ps = 1011> >> (B<rxvt>)	1938	=item B<< C<Pm = 1011> >> (B<rxvt>)
1689		1939
1690	=begin table	1940	=begin table
1691		1941
1692	B<< C<h> >> Scroll to bottom when a key is pressed	1942	B<< C<h> >> Scroll to bottom when a key is pressed
1693	B<< C<l> >> Don't scroll to bottom when a key is pressed	1943	B<< C<l> >> Don't scroll to bottom when a key is pressed
1694		1944
1695	=end table	1945	=end table
1696		1946
1697	=item B<< C<Ps = 1021> >> (B<rxvt>)	1947	=item B<< C<Pm = 1021> >> (B<rxvt>)
1698		1948
1699	=begin table	1949	=begin table
1700		1950
1701	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)	1951	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
1702	B<< C<l> >> Font styles have no effect on intensity (Compile styles)	1952	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1703		1953
1704	=end table	1954	=end table
1705		1955
1706	=item B<< C<Ps = 1047> >>	1956	=item B<< C<Pm = 1047> >>
1707		1957
1708	=begin table	1958	=begin table
1709		1959
1710	B<< C<h> >> Use Alternate Screen Buffer	1960	B<< C<h> >> Use Alternate Screen Buffer
1711	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it	1961	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1712		1962
1713	=end table	1963	=end table
1714		1964
1715	=item B<< C<Ps = 1048> >>	1965	=item B<< C<Pm = 1048> >>
1716		1966
1717	=begin table	1967	=begin table
1718		1968
1719	B<< C<h> >> Save cursor position	1969	B<< C<h> >> Save cursor position
1720	B<< C<l> >> Restore cursor position	1970	B<< C<l> >> Restore cursor position
1721		1971
1722	=end table	1972	=end table
1723		1973
1724	=item B<< C<Ps = 1049> >>	1974	=item B<< C<Pm = 1049> >>
1725		1975
1726	=begin table	1976	=begin table
1727		1977
1728	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it	1978	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1729	B<< C<l> >> Use Normal Screen Buffer	1979	B<< C<l> >> Use Normal Screen Buffer
…		…
1734		1984
1735	=back	1985	=back
1736		1986
1737	X<XTerm>	1987	X<XTerm>
1738		1988
1739	=head1 XTerm Operating System Commands	1989	=head2 XTerm Operating System Commands
1740		1990
1741	=over 4	1991	=over 4
1742		1992
1743	=item B<< C<ESC ] Ps;Pt ST> >>	1993	=item B<< C<ESC ] Ps;Pt ST> >>
1744		1994
…		…
1751	B<< C<Ps = 0> >> Change Icon Name and Window Title to B<< C<Pt> >>	2001	B<< C<Ps = 0> >> Change Icon Name and Window Title to B<< C<Pt> >>
1752	B<< C<Ps = 1> >> Change Icon Name to B<< C<Pt> >>	2002	B<< C<Ps = 1> >> Change Icon Name to B<< C<Pt> >>
1753	B<< C<Ps = 2> >> Change Window Title to B<< C<Pt> >>	2003	B<< C<Ps = 2> >> Change Window Title to B<< C<Pt> >>
1754	B<< C<Ps = 3> >> If B<< C<Pt> >> starts with a B<< C<?> >>, query the (STRING) property of the window and return it. If B<< C<Pt> >> contains a B<< C<=> >>, set the named property to the given value, else delete the specified property.	2004	B<< C<Ps = 3> >> If B<< C<Pt> >> starts with a B<< C<?> >>, query the (STRING) property of the window and return it. If B<< C<Pt> >> contains a B<< C<=> >>, set the named property to the given value, else delete the specified property.
1755	B<< C<Ps = 4> >> B<< C<Pt> >> is a semi-colon separated sequence of one or more semi-colon separated B<number>/B<name> pairs, where B<number> is an index to a colour and B<name> is the name of a colour. Each pair causes the B<number>ed colour to be changed to B<name>. Numbers 0-7 corresponds to low-intensity (normal) colours and 8-15 corresponds to high-intensity colours. 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white	2005	B<< C<Ps = 4> >> B<< C<Pt> >> is a semi-colon separated sequence of one or more semi-colon separated B<number>/B<name> pairs, where B<number> is an index to a colour and B<name> is the name of a colour. Each pair causes the B<number>ed colour to be changed to B<name>. Numbers 0-7 corresponds to low-intensity (normal) colours and 8-15 corresponds to high-intensity colours. 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white
1756	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	2006	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >>
1757	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	2007	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >>
1758	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	2008	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1759	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	2009	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1760	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	2010	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1761	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]	2011	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1762	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]	2012	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1763	B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM).	2013	B<< C<Ps = 20> >> Change background pixmap parameters (see section BACKGROUND IMAGE) (Compile AfterImage).
1764	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.	2014	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. [deprecated, use 10]
1765	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	2015	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1766	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	2016	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>. [deprecated, use 11]
1767	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>	2017	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>
1768	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	2018	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1769	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).	2019	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).
1770	B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>.	2020	B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>.
1771	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	2021	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
…		…
1782		2032
1783	=end table	2033	=end table
1784		2034
1785	=back	2035	=back
1786		2036
1787	X<XPM>	2037	=head1 BACKGROUND IMAGE
1788		2038
1789	=head1 XPM
1790
1791	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	2039	For the BACKGROUND IMAGE XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> the value
1792	of B<< C<Pt> >> can be the name of the background pixmap followed by a	2040	of B<< C<Pt> >> can be the name of the background image file followed by a
1793	sequence of scaling/positioning commands separated by semi-colons. The	2041	sequence of scaling/positioning commands separated by semi-colons. The
1794	scaling/positioning commands are as follows:	2042	scaling/positioning commands are as follows:
1795		2043
1796	=over 4	2044	=over 4
1797		2045
…		…
1835		2083
1836	For example:	2084	For example:
1837		2085
1838	=over 4	2086	=over 4
1839		2087
1840	=item B<\E]20;funky\a>	2088	=item B<\E]20;funky.jpg\a>
1841		2089
1842	load B<funky.xpm> as a tiled image	2090	load B<funky.jpg> as a tiled image
1843		2091
1844	=item B<\E]20;mona;100\a>	2092	=item B<\E]20;mona.jpg;100\a>
1845		2093
1846	load B<mona.xpm> with a scaling of 100%	2094	load B<mona.jpg> with a scaling of 100%
1847		2095
1848	=item B<\E]20;;200;?\a>	2096	=item B<\E]20;;200;?\a>
1849		2097
1850	rescale the current pixmap to 200% and display the image geometry in	2098	rescale the current pixmap to 200% and display the image geometry in
1851	the title	2099	the title
…		…
1890	=begin table	2138	=begin table
1891		2139
1892	4 Shift	2140	4 Shift
1893	8 Meta	2141	8 Meta
1894	16 Control	2142	16 Control
1895	32 Double Click I<(Rxvt extension)>	2143	32 Double Click I<(rxvt extension)>
1896		2144
1897	=end table	2145	=end table
1898		2146
1899	Col = B<< C<< <x> - SPACE >> >>	2147	Col = B<< C<< <x> - SPACE >> >>
1900		2148
…		…
1978		2226
1979	=head1 CONFIGURE OPTIONS	2227	=head1 CONFIGURE OPTIONS
1980		2228
1981	General hint: if you get compile errors, then likely your configuration	2229	General hint: if you get compile errors, then likely your configuration
1982	hasn't been tested well. Either try with C<--enable-everything> or use	2230	hasn't been tested well. Either try with C<--enable-everything> or use
1983	the F<./reconf> script as a base for experiments. F<./reconf> is used by	2231	the default configuration (i.e. no C<--enable-xxx> or C<--disable-xxx>
1984	myself, so it should generally be a working config. Of course, you should	2232	switches). Of course, you should always report when a combination doesn't
1985	always report when a combination doesn't work, so it can be fixed. Marc	2233	work, so it can be fixed. Marc Lehmann <rxvt@schmorp.de>.
1986	Lehmann <rxvt@schmorp.de>.
1987		2234
1988	All	2235	All
1989		2236
1990	=over 4	2237	=over 4
1991		2238
…		…
2023		2270
2024	=begin table	2271	=begin table
2025		2272
2026	all all available codeset groups	2273	all all available codeset groups
2027	zh common chinese encodings	2274	zh common chinese encodings
2028	zh_ext rarely used but very big chinese encodigs	2275	zh_ext rarely used but very big chinese encodings
2029	jp common japanese encodings	2276	jp common japanese encodings
2030	jp_ext rarely used but big japanese encodings	2277	jp_ext rarely used but big japanese encodings
2031	kr korean encodings	2278	kr korean encodings
2032		2279
2033	=end table	2280	=end table
…		…
2047	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2294	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2048	support these extra characters, but Xft does.	2295	support these extra characters, but Xft does.
2049		2296
2050	Please note that rxvt-unicode can store unicode code points >65535	2297	Please note that rxvt-unicode can store unicode code points >65535
2051	even without this flag, but the number of such characters is	2298	even without this flag, but the number of such characters is
2052	limited to a view thousand (shared with combining characters,	2299	limited to a few thousand (shared with combining characters,
2053	see next switch), and right now rxvt-unicode cannot display them	2300	see next switch), and right now rxvt-unicode cannot display them
2054	(input/output and cut&paste still work, though).	2301	(input/output and cut&paste still work, though).
2055		2302
2056	=item --enable-combining (default: on)	2303	=item --enable-combining (default: on)
2057		2304
…		…
2080	=item --with-res-name=NAME (default: urxvt)	2327	=item --with-res-name=NAME (default: urxvt)
2081		2328
2082	Use the given name as default application name when	2329	Use the given name as default application name when
2083	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2330	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2084		2331
2085	=item --with-res-class=CLASS /default: URxvt)	2332	=item --with-res-class=CLASS (default: URxvt)
2086		2333
2087	Use the given class as default application class	2334	Use the given class as default application class
2088	when reading resources. Specify --with-res-class=Rxvt to replace	2335	when reading resources. Specify --with-res-class=Rxvt to replace
2089	rxvt.	2336	rxvt.
2090		2337
…		…
2103		2350
2104	Write user and tty to lastlog file (used by programs like	2351	Write user and tty to lastlog file (used by programs like
2105	F<lastlogin>) at start of rxvt execution. This option requires	2352	F<lastlogin>) at start of rxvt execution. This option requires
2106	--enable-utmp to also be specified.	2353	--enable-utmp to also be specified.
2107		2354
2108	=item --enable-xpm-background (default: on)	2355	=item --enable-afterimage (default: on)
2109		2356
2110	Add support for XPM background pixmaps.	2357	Add support for libAfterImage to be used for transparency and background
		2358	images. It adds support for many file formats including JPG, PNG,
		2359	SVG, TIFF, GIF, XPM, BMP, ICO, XCF, TGA and AfterStep image XML
		2360	(L<http://www.afterstep.org/visualdoc.php?show=asimagexml>).
		2361
		2362	This option also adds such eye candy as blending an image over the root
		2363	background, as well as dynamic scaling and bluring of background images.
		2364
		2365	Note that with this option enabled, @@RXVT_NAME@@'s memory footprint might
		2366	increase by a few megabytes even if no extra features are used (mostly due
		2367	to third-party libraries used by libAI). Memory footprint may somewhat be
		2368	lowered if libAfterImage is configured without support for SVG.
2111		2369
2112	=item --enable-transparency (default: on)	2370	=item --enable-transparency (default: on)
2113		2371
2114	Add support for inheriting parent backgrounds thus giving a fake	2372	Add support for backgrounds, creating illusion of transparency in the term.
2115	transparency to the term.
2116		2373
2117	=item --enable-fading (default: on)	2374	=item --enable-fading (default: on)
2118		2375
2119	Add support for fading the text when focus is lost (requires C<--enable-transparency>).	2376	Add support for fading the text when focus is lost.
2120
2121	=item --enable-tinting (default: on)
2122
2123	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2124		2377
2125	=item --enable-rxvt-scroll (default: on)	2378	=item --enable-rxvt-scroll (default: on)
2126		2379
2127	Add support for the original rxvt scrollbar.	2380	Add support for the original rxvt scrollbar.
2128		2381
…		…
2138		2391
2139	Add support for a very unobtrusive, plain-looking scrollbar that	2392	Add support for a very unobtrusive, plain-looking scrollbar that
2140	is the favourite of the rxvt-unicode author, having used it for	2393	is the favourite of the rxvt-unicode author, having used it for
2141	many years.	2394	many years.
2142		2395
2143	=item --enable-ttygid (default: off)
2144
2145	Change tty device setting to group "tty" - only use this if
2146	your system uses this type of security.
2147
2148	=item --disable-backspace-key	2396	=item --disable-backspace-key
2149		2397
2150	Removes any handling of the backspace key by us - let the X server do it.	2398	Removes any handling of the backspace key by us - let the X server do it.
2151		2399
2152	=item --disable-delete-key	2400	=item --disable-delete-key
…		…
2171	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2419	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2172	in combination with other switches) is:	2420	in combination with other switches) is:
2173		2421
2174	MWM-hints	2422	MWM-hints
2175	EWMH-hints (pid, utf8 names) and protocols (ping)	2423	EWMH-hints (pid, utf8 names) and protocols (ping)
		2424	urgency hint
2176	seperate underline colour (-underlineColor)	2425	seperate underline colour (-underlineColor)
2177	settable border widths and borderless switch (-w, -b, -bl)	2426	settable border widths and borderless switch (-w, -b, -bl)
2178	visual depth selection (-depth)	2427	visual depth selection (-depth)
2179	settable extra linespacing /-lsp)	2428	settable extra linespacing /-lsp)
2180	iso-14755-2 and -3, and visual feedback	2429	iso-14755 5.1 (basic) support
2181	tripleclickwords (-tcw)	2430	tripleclickwords (-tcw)
2182	settable insecure mode (-insecure)	2431	settable insecure mode (-insecure)
2183	keysym remapping support	2432	keysym remapping support
2184	cursor blinking and underline cursor (-cb, -uc)	2433	cursor blinking and underline cursor (-cb, -uc)
2185	XEmbed support (-embed)	2434	XEmbed support (-embed)
2186	user-pty (-pty-fd)	2435	user-pty (-pty-fd)
2187	hold on exit (-hold)	2436	hold on exit (-hold)
		2437	compile in built-in block graphics
2188	skip builtin block graphics (-sbg)	2438	skip builtin block graphics (-sbg)
		2439	separate highlightcolor support (-hc)
2189		2440
2190	It also enabled some non-essential features otherwise disabled, such as:	2441	It also enables some non-essential features otherwise disabled, such as:
2191		2442
2192	some round-trip time optimisations	2443	some round-trip time optimisations
2193	nearest color allocation on pseudocolor screens	2444	nearest color allocation on pseudocolor screens
2194	UTF8_STRING supporr for selection	2445	UTF8_STRING support for selection
2195	sgr modes 90..97 and 100..107	2446	sgr modes 90..97 and 100..107
2196	backindex and forwardindex escape sequences	2447	backindex and forwardindex escape sequences
2197	view change/zero scorllback esacpe sequences	2448	view change/zero scrollback escape sequences
2198	locale switching escape sequence	2449	locale switching escape sequence
2199	window op and some xterm/OSC escape sequences	2450	window op and some xterm/OSC escape sequences
2200	rectangular selections	2451	rectangular selections
2201	trailing space removal for selections	2452	trailing space removal for selections
2202	verbose X error handling	2453	verbose X error handling
…		…
2211	=item --enable-keepscrolling (default: on)	2462	=item --enable-keepscrolling (default: on)
2212		2463
2213	Add support for continual scrolling of the display when you hold	2464	Add support for continual scrolling of the display when you hold
2214	the mouse button down on a scrollbar arrow.	2465	the mouse button down on a scrollbar arrow.
2215		2466
		2467	=item --enable-selectionscrolling (default: on)
		2468
		2469	Add support for scrolling when the selection moves to the top or
		2470	bottom of the screen.
		2471
2216	=item --enable-mousewheel (default: on)	2472	=item --enable-mousewheel (default: on)
2217		2473
2218	Add support for scrolling via mouse wheel or buttons 4 & 5.	2474	Add support for scrolling via mouse wheel or buttons 4 & 5.
2219		2475
2220	=item --enable-slipwheeling (default: on)	2476	=item --enable-slipwheeling (default: on)
2221		2477
2222	Add support for continual scrolling (using the mouse wheel as an	2478	Add support for continual scrolling (using the mouse wheel as an
2223	accelerator) while the control key is held down. This option	2479	accelerator) while the control key is held down. This option
2224	requires --enable-mousewheel to also be specified.	2480	requires --enable-mousewheel to also be specified.
2225		2481
2226	=item --disable-new-selection
2227
2228	Remove support for mouse selection style like that of xterm.
2229
2230	=item --enable-dmalloc (default: off)
2231
2232	Use Gray Watson's malloc - which is good for debugging See
2233	http://www.letters.com/dmalloc/ for details If you use either this or the
2234	next option, you may need to edit src/Makefile after compiling to point
2235	DINCLUDE and DLIB to the right places.
2236
2237	You can only use either this option and the following (should
2238	you use either) .
2239
2240	=item --enable-dlmalloc (default: off)
2241
2242	Use Doug Lea's malloc - which is good for a production version
2243	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2244
2245	=item --enable-smart-resize (default: on)	2482	=item --enable-smart-resize (default: off)
2246		2483
2247	Add smart growth/shrink behaviour when changing font size via hot	2484	Add smart growth/shrink behaviour when resizing.
2248	keys. This should keep the window corner which is closest to a corner of	2485	This should keep the window corner which is closest to a corner of
2249	the screen in a fixed position.	2486	the screen in a fixed position.
2250		2487
		2488	=item --enable-text-blink (default: on)
		2489
		2490	Add support for blinking text.
		2491
2251	=item --enable-pointer-blank (default: on)	2492	=item --enable-pointer-blank (default: on)
2252		2493
2253	Add support to have the pointer disappear when typing or inactive.	2494	Add support to have the pointer disappear when typing or inactive.
2254		2495
2255	=item --enable-perl (default: on)	2496	=item --enable-perl (default: on)
2256		2497
2257	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>	2498	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2258	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files	2499	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the
2259	in F<src/perl-ext/> for the extensions that are installed by default. The	2500	files in F<src/perl-ext/> for the extensions that are installed by
2260	perl interpreter that is used can be specified via the C<PERL> environment	2501	default. The perl interpreter that is used can be specified via the
2261	variable when running configure.	2502	C<PERL> environment variable when running configure. Even when compiled
		2503	in, perl will I<not> be initialised when all extensions have been disabled
		2504	C<-pe "" --perl-ext-common "">, so it should be safe to enable from a
		2505	resource standpoint.
		2506
		2507	=item --with-afterimage-config=DIR
		2508
		2509	Look for the libAfterImage config script in DIR.
2262		2510
2263	=item --with-name=NAME (default: urxvt)	2511	=item --with-name=NAME (default: urxvt)
2264		2512
2265	Set the basename for the installed binaries, resulting	2513	Set the basename for the installed binaries, resulting
2266	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2514	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
…		…
2276	PATH.	2524	PATH.
2277		2525
2278	=item --with-x	2526	=item --with-x
2279		2527
2280	Use the X Window System (pretty much default, eh?).	2528	Use the X Window System (pretty much default, eh?).
2281
2282	=item --with-xpm-includes=DIR
2283
2284	Look for the XPM includes in DIR.
2285
2286	=item --with-xpm-library=DIR
2287
2288	Look for the XPM library in DIR.
2289
2290	=item --with-xpm
2291
2292	Not needed - define via --enable-xpm-background.
2293		2529
2294	=back	2530	=back
2295		2531
2296	=head1 AUTHORS	2532	=head1 AUTHORS
2297		2533

Diff Legend

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