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.84 by root, Mon Jan 16 15:07:27 2006 UTC vs.
Revision 1.162 by ayin, Sat Jan 19 15:00:49 2008 UTC

…		…
16	=head1 DESCRIPTION	16	=head1 DESCRIPTION
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	21	The newest version of this document is also available on the World Wide Web at
22	also available on the World Wide Web at	22	L<http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod>.
23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
24		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
25	=head1 FREQUENTLY ASKED QUESTIONS	27	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		28
27	=over 4
28		29
29	=item The new selection selects pieces that are too big, how can I select	30	=head2 Meta, Features & Commandline Issues
30	single words?
31		31
32	Yes. For example, if you want to select alphanumeric words, you can use	32	=head3 My question isn't answered here, can I ask a human?
33	the following resource:
34		33
35	URxvt.selection.pattern-0: ([[:word:]]+)	34	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		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	If you click more than twice, the selection will be extended	38	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
38	more and more.
39		39
40	To get a selection that is very similar to the old code, try this pattern:	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:
41		43
42	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)	44	@@URXVT_NAME@@ -pe tabbed
43		45
44	Please also note that the I<LeftClick Shift-LeftClik> combination also	46	URxvt.perl-ext-common: default,tabbed
45	selects words like the old code.
46		47
47	=item I don't like the new selection/popups/hotkeys/perl, how do I	48	It will also work fine with tabbing functionality of many window managers
48	change/disable it?	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.
49		53
50	You can disable the perl extension completely by setting the	54	=head3 How do I know which rxvt-unicode version I'm using?
51	B<perl-ext-common> resource to the empty string, which also keeps
52	rxvt-unicode from initialising perl, saving memory.
53		55
54	If you only want to disable specific features, you first have to	56	The version number is displayed with the usage (-h). Also the escape
55	identify which perl extension is responsible. For this, read the section	57	sequence C<ESC [ 8 n> sets the window title to the version number. When
56	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For	58	using the @@URXVT_NAME@@c client, the version displayed is that of the
57	example, to disable the B<selection-popup> and B<option-popup>, specify	59	daemon.
58	this B<perl-ext-common> resource:
59		60
60	URxvt.perl-ext-common: default,-selection-popup,-option-popup	61	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
61		62
62	This will keep the default extensions, but disable the two popup	63	Rxvt-unicode tries to obey the rule of not charging you for something you
63	extensions. Some extensions can also be configured, for example,	64	don't use. One thing you should try is to configure out all settings that
64	scrollback search mode is triggered by B<M-s>. You can move it to any	65	you don't need, for example, Xft support is a resource hog by design,
65	other combination either by setting the B<searchable-scrollback> resource:	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.
66		68
67	URxvt.searchable-scrollback: CM-s	69	Also, many people (me included) like large windows and even larger
		70	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		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.
68		75
		76	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
		77
		78	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
		79	display, create the listening socket and then fork.
		80
		81	=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c?
		82
		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:
		85
		86	#!/bin/sh
		87	@@URXVT_NAME@@c "$@"
		88	if [ $? -eq 2 ]; then
		89	@@URXVT_NAME@@d -q -o -f
		90	@@URXVT_NAME@@c "$@"
		91	fi
		92
		93	This tries to create a new terminal, and if fails with exit status 2,
		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.
		97
		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.
		99
		100	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
		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.
		104
		105	=head3 How do I set the correct, full IP address for the DISPLAY variable?
		106
		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.
		113
		114	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		115	snippets:
		116
		117	# Bourne/Korn/POSIX family of shells:
		118	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		119	if [ ${TERM:-foo} = xterm ]; then
		120	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		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
		129
		130	=head3 How do I compile the manual pages on my own?
		131
		132	You need to have a recent version of perl installed as F</usr/bin/perl>,
		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>.
		135
69	=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?
70		137
71	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
72	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
73	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
74	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
…		…
78		145
79	text data bss drs rss filename	146	text data bss drs rss filename
80	98398 1664 24 15695 1824 rxvt --disable-everything	147	98398 1664 24 15695 1824 rxvt --disable-everything
81	188985 9048 66616 18222 1788 urxvt --disable-everything	148	188985 9048 66616 18222 1788 urxvt --disable-everything
82		149
83	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
84	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
85	libc), the two diverge, but not unreasnobaly so.	152	libc), the two diverge, but not unreasonably so.
86		153
87	text data bss drs rss filename	154	text data bss drs rss filename
88	163431 2152 24 20123 2060 rxvt --enable-everything	155	163431 2152 24 20123 2060 rxvt --enable-everything
89	1035683 49680 66648 29096 3680 urxvt --enable-everything	156	1035683 49680 66648 29096 3680 urxvt --enable-everything
90		157
…		…
106	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	173	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
107	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
108	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
109	extremely well *g*.	176	extremely well *g*.
110		177
111	=item Why C++, isn't that unportable/bloated/uncool?	178	=head3 Why C++, isn't that unportable/bloated/uncool?
112		179
113	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
114	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
115	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
116	shorter: It simply wouldn't exist without C++.	183	shorter: It simply wouldn't exist without C++.
…		…
133		200
134	And here is rxvt-unicode:	201	And here is rxvt-unicode:
135		202
136	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	203	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
137	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)	204	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
138	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)	205	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
139	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)	206	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
140	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	207	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
141		208
142	No large bloated libraries (of course, none were linked in statically),	209	No large bloated libraries (of course, none were linked in statically),
143	except maybe libX11 :)	210	except maybe libX11 :)
144		211
145	=item Does it support tabs, can I have a tabbed rxvt-unicode?
146		212
147	rxvt-unicode does not directly support tabs. It will work fine with	213	=head2 Rendering, Font & Look and Feel Issues
148	tabbing functionality of many window managers or similar tabbing programs,
149	and its embedding-features allow it to be embedded into other programs,
150	as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
151	module, which features a tabbed urxvt (murxvt) terminal as an example
152	embedding application.
153		214
154	=item How do I know which rxvt-unicode version I'm using?	215	=head3 I can't get transparency working, what am I doing wrong?
155		216
156	The version number is displayed with the usage (-h). Also the escape	217	First of all, please address all transparency related issues to Sasha Vasko at
157	sequence C<ESC [ 8 n> sets the window title to the version number. When	218	sasha@aftercode.net and do not bug the author about it. Also, if you can't
158	using the @@RXVT_NAME@@c client, the version displayed is that of the	219	get it working consider it a rite of passage: ... and you failed.
159	daemon.
160		220
161	=item I am using Debian GNU/Linux and have a problem...	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!
162		223
163	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	224	1. Use transparent mode:
164	patches that considerably change the behaviour of rxvt-unicode. Before
165	reporting a bug to the original rxvt-unicode author please download and
166	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
167	and try to reproduce the problem. If you cannot, chances are that the
168	problems are specific to Debian GNU/Linux, in which case it should be
169	reported via the Debian Bug Tracking System (use C<reportbug> to report
170	the bug).
171		225
172	For other problems that also affect the Debian package, you can and	226	Esetroot wallpaper.jpg
173	probably should use the Debian BTS, too, because, after all, it's also a	227	@@URXVT_NAME@@ -tr -tint red -sh 40
174	bug in the Debian version and it serves as a reminder for other users that
175	might encounter the same issue.
176		228
177	=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?	229	That works. If you think it doesn't, you lack transparency and tinting
		230	support, or you are unable to read.
178		231
179	You should build one binary with the default options. F<configure>	232	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
180	now enables most useful options, and the trend goes to making them	233	to use effects other than tinting and shading: Just shade/tint/whatever
181	runtime-switchable, too, so there is usually no drawback to enbaling them,	234	your picture with gimp or any other tool:
182	except higher disk and possibly memory usage. The perl interpreter should
183	be enabled, as important functionality (menus, selection, likely more in
184	the future) depends on it.
185		235
186	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	236	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
187	system-wide (except maybe with C<defaults>). This will result in useful	237	@@URXVT_NAME@@ -pixmap "background.jpg;:root"
188	behaviour. If your distribution aims at low memory, add an empty
189	C<perl-ext-common> resource to the app-defaults file. This will keep the
190	perl interpreter disabled until the user enables it.
191		238
192	If you can/want build more binaries, I recommend building a minimal	239	That works. If you think it doesn't, you lack AfterImage support, or you
193	one with C<--disable-everything> (very useful) and a maximal one with	240	are unable to read.
194	C<--enable-everything> (less useful, it will be very big due to a lot of
195	encodings built-in that increase download times and are rarely used).
196		241
197	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	242	3. Use an ARGB visual:
198		243
199	Likely not. While I honestly try to make it secure, and am probably not	244	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
200	bad at it, I think it is simply unreasonable to expect all of freetype
201	+ fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be
202	secure. Also, rxvt-unicode disables some options when it detects that it
203	runs setuid or setgid, which is not nice. Besides, with the embedded perl
204	interpreter the possibility for security problems easily multiplies.
205		245
206	Elevated privileges are only required for utmp and pty operations on some	246	This requires XFT support, and the support of your X-server. If that
207	systems (for example, GNU/Linux doesn't need any extra privileges for	247	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
208	ptys, but some need it for utmp support). It is planned to mvoe this into	248	there yet, no matter what they claim. Rxvt-Unicode contains the necessary
209	a forked handler process, but this is not yet done.	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.
210		251
211	So, while setuid/setgid operation is supported and not a problem on your	252	4. Use xcompmgr and let it do the job:
212	typical single-user-no-other-logins unix desktop, always remember that
213	its an awful lot of code, most of which isn't checked for security issues
214	regularly.
215		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
		528	URxvt.perl-ext-common: default,-readline
		529
		530	=head3 My numerical keypad acts weird and generates differing output?
		531
		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.
		538
		539	=head3 My Compose (Multi_key) key is no longer working.
		540
		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.
		547
		548	In this case either do not specify a B<preeditStyle> or specify more than
		549	one pre-edit style, such as B<OverTheSpot,Root,None>.
		550
		551	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		552
		553	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		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.
		558
		559	=head3 Mouse cut/paste suddenly no longer works.
		560
		561	Make sure that mouse reporting is actually turned off since killing
		562	some editors prematurely may leave the mouse in mouse report mode. I've
		563	heard that tcsh may use mouse reporting unless it otherwise specified. A
		564	quick check is to see if cut/paste works when the Alt or Shift keys are
		565	depressed.
		566
		567	=head3 What's with the strange Backspace/Delete key behaviour?
		568
		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<^?>.
		573
		574	Historically, either value is correct, but rxvt-unicode adopts the debian
		575	policy of using C<^?> when unsure, because it's the one and only correct
		576	choice :).
		577
		578	Rxvt-unicode tries to inherit the current stty settings and uses the value
		579	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		580	started from a terminal (say, from a menu or by remote shell), then the
		581	system value of `erase', which corresponds to CERASE in <termios.h>, will
		582	be used (which may not be the same as your stty setting).
		583
		584	For starting a new rxvt-unicode:
		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
216	=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?
217		845
218	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
219	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).
220		848
221	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
222	be done like this (with ncurses' infocmp):	850	be done like this (with ncurses' infocmp and works as user and admin):
223		851
224	REMOTE=remotesystem.domain	852	REMOTE=remotesystem.domain
225	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"
226		854
227	... 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.
228		859
229	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
230	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
231	problems arising, which includes wrong keymapping, less and different	862	problems arising, which includes wrong keymapping, less and different
232	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
…		…
237	resource to set it:	868	resource to set it:
238		869
239	URxvt.termName: rxvt	870	URxvt.termName: rxvt
240		871
241	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
242	the rxvt terminfo file with the rxvt-unicode one.	873	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
243		874
244	=item C<tic> outputs some error when compiling the terminfo entry.	875	=head3 C<tic> outputs some error when compiling the terminfo entry.
245		876
246	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
247	C<enacs=\E[0@> and try again.	878	C<enacs=\E[0@> and try again.
248		879
249	=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@@.
250		881
		882	See next entry.
		883
251	=item I need a termcap file entry.	884	=head3 I need a termcap file entry.
252		885
253	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
254	systems still compile some programs using the long-obsoleted termcap	887	systems still compile some programs using the long-obsoleted termcap
255	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
256	for C<rxvt-unicode>.	889	for C<rxvt-unicode>.
257		890
258	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.
259	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
260	like this:	893	like this:
261		894
262	infocmp -C rxvt-unicode	895	infocmp -C rxvt-unicode
263		896
…		…
282	: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:\
283	: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:\
284	: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:\
285	:vs=\E[?25h:	918	:vs=\E[?25h:
286		919
287	=item Why does C<ls> no longer have coloured output?	920	=head3 Why does C<ls> no longer have coloured output?
288		921
289	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
290	decide wether a terminal has colour, but uses it's own configuration	923	decide whether a terminal has colour, but uses its own configuration
291	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
292	with most other terminals supporting colour). Either add:	925	with most other terminals supporting colour). Either add:
293		926
294	TERM rxvt-unicode	927	TERM rxvt-unicode
295		928
296	to C</etc/DIR_COLORS> or simply add:	929	to C</etc/DIR_COLORS> or simply add:
297		930
298	alias ls='ls --color=auto'	931	alias ls='ls --color=auto'
299		932
300	to your C<.profile> or C<.bashrc>.	933	to your C<.profile> or C<.bashrc>.
301		934
302	=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?
303		936
		937	See next entry.
		938
304	=item Why doesn't vim/emacs etc. make use of italic?	939	=head3 Why doesn't vim/emacs etc. make use of italic?
305		940
		941	See next entry.
		942
306	=item Why are the secondary screen-related options not working properly?	943	=head3 Why are the secondary screen-related options not working properly?
307		944
308	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
309	distributions (most notably Debian GNU/Linux) break rxvt-unicode	946	distributions (most notably Debian GNU/Linux) break rxvt-unicode
310	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
311	features. Unfortunately, some of these (most notably, again, Debian	948	features. Unfortunately, some of these (most notably, again, Debian
312	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
313	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
314	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
315	how to do this).	952	how to do this).
316		953
317	=item My numerical keypad acts weird and generates differing output?
318		954
319	Some Debian GNUL/Linux users seem to have this problem, although no	955	=head2 Encoding / Locale / Input Method Issues
320	specific details were reported so far. It is possible that this is caused
321	by the wrong C<TERM> setting, although the details of wether and how
322	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
323	keymap. See the answer to the previous question, and please report if that
324	helped.
325		956
326	=item Rxvt-unicode does not seem to understand the selected encoding?	957	=head3 Rxvt-unicode does not seem to understand the selected encoding?
327		958
		959	See next entry.
		960
328	=item Unicode does not seem to work?	961	=head3 Unicode does not seem to work?
329		962
330	If you encounter strange problems like typing an accented character but	963	If you encounter strange problems like typing an accented character but
331	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
332	subtly garbled, then you should check your locale settings.	965	subtly garbled, then you should check your locale settings.
333		966
334	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
335	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,
336	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
337	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.
338		972
339	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
340	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.
341		975
342	printf '\e]701;%s\007' "$LC_CTYPE"	976	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
343		977
344	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
345	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
346	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
347	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
…		…
353		987
354	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
355	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
356	support locales :(	990	support locales :(
357		991
358	=item Why do some characters look so much different than others?	992	=head3 How does rxvt-unicode determine the encoding to use?
359		993
360	=item How does rxvt-unicode choose fonts?	994	See next entry.
361		995
362	Most fonts do not contain the full range of Unicode, which is	996	=head3 Is there an option to switch encodings?
363	fine. Chances are that the font you (or the admin/package maintainer of
364	your system/os) have specified does not cover all the characters you want
365	to display.
366		997
367	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
368	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
369	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.
370	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
371	intelligence to detect that a specific glyph is wrong: it has to believe
372	the font that the characters it claims to contain indeed look correct.
373		1001
374	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
375	e.g.:	1003	the encoding, doing I/O and (most important) communicating this to all
376		1004	applications so everybody agrees on character properties such as width
377	@@RXVT_NAME@@ -fn basefont,font2,font3...	1005	and code number. This mechanism is the I<locale>. Applications not using
378		1006	that info will have problems (for example, C<xterm> gets the width of
379	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
380	font. If the base font does not contain the character, it will go to the
381	next font, and so on. Specifying your own fonts will also speed up this
382	search and use less resources within rxvt-unicode and the X-server.
383
384	The only limitation is that none of the fonts may be larger than the base
385	font, as the base font defines the terminal character cell size, which
386	must be the same due to the way terminals work.
387
388	=item Why do some chinese characters look so different than others?
389
390	This is because there is a difference between script and language --
391	rxvt-unicode does not know which language the text that is output is,
392	as it only knows the unicode character codes. If rxvt-unicode first
393	sees a japanese/chinese character, it might choose a japanese font for
394	display. Subsequent japanese characters will use that font. Now, many
395	chinese characters aren't represented in japanese fonts, so when the first
396	non-japanese character comes up, rxvt-unicode will look for a chinese font
397	-- unfortunately at this point, it will still use the japanese font for
398	chinese characters that are also in the japanese font.
399
400	The workaround is easy: just tag a chinese font at the end of your font
401	list (see the previous question). The key is to view the font list as
402	a preference list: If you expect more japanese, list a japanese font
403	first. If you expect more chinese, put a chinese font first.
404
405	In the future it might be possible to switch language preferences at
406	runtime (the internal data structure has no problem with using different
407	fonts for the same character at the same time, but no interface for this
408	has been designed yet).
409
410	Until then, you might get away with switching fonts at runtime (see L<Can
411	I switch the fonts at runtime?> later in this document).
412
413	=item Why does rxvt-unicode sometimes leave pixel droppings?
414
415	Most fonts were not designed for terminal use, which means that character
416	size varies a lot. A font that is otherwise fine for terminal use might
417	contain some characters that are simply too wide. Rxvt-unicode will avoid
418	these characters. For characters that are just "a bit" too wide a special
419	"careful" rendering mode is used that redraws adjacent characters.
420
421	All of this requires that fonts do not lie about character sizes,
422	however: Xft fonts often draw glyphs larger than their acclaimed bounding
423	box, and rxvt-unicode has no way of detecting this (the correct way is to
424	ask for the character bounding box, which unfortunately is wrong in these
425	cases).	1008	locales).
426		1009
427	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
428	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
429	the C<-lsp> option to give the font more height. If that doesn't work, you	1012	interpretation of characters.
430	might be forced to use a different font.
431		1013
432	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
433	box data is correct.	1015	is there a standard on how locale specifiers will look like.
434		1016
435	=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.
436		1022
437	Seems to be a known bug, read	1023	Rxvt-unicode ignores all other locale categories, and except for
438	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1024	the encoding, ignores country or language-specific settings,
439	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.
440		1027
441	#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.
442		1030
443	=item My Compose (Multi_key) key is no longer working.	1031	=head3 Can I switch locales at runtime?
444		1032
445	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
446	correctly, or you specified a B<preeditStyle> that is not supported by	1034	rxvt-unicode's idea of C<LC_CTYPE>.
447	your input method. For example, if you specified B<OverTheSpot> and
448	your input method (e.g. the default input method handling Compose keys)
449	does not support this (for instance because it is not visual), then
450	rxvt-unicode will continue without an input method.
451		1035
452	In this case either do not specify a B<preeditStyle> or specify more than	1036	printf '\33]701;%s\007' ja_JP.SJIS
453	one pre-edit style, such as B<OverTheSpot,Root,None>.
454		1037
455	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755	1038	See also the previous answer.
456		1039
457	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
458	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
459	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
460	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:
461	character and so on.
462		1044
463	=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
464		1048
465	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
466	(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
467	make sure you have specified colours for italic and bold, as otherwise	1051	rxvt-unicode-locales.
468	rxvt-unicode might use reverse video to simulate the effect:
469		1052
470	URxvt.colorBD: white	1053	=head3 I have problems getting my input method working.
471	URxvt.colorIT: green
472		1054
473	=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.
474		1056
475	For some unexplainable reason, some rare programs assume a very weird	1057	Here is a checklist:
476	colour palette when confronted with a terminal with more than the standard
477	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
478	these programs not to assume non-ISO colours without very good reasons.
479		1058
480	In the meantime, you can either edit your C<rxvt-unicode> terminfo	1059	=over 4
481	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
482	fix colours but keep you from using other rxvt-unicode features.
483		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
484	=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.
485		1164
486	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
487	in your compile environment, or an implementation that implements it,	1166	in your compile environment, or an implementation that implements it,
488	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
489	B<wchar_t> is represented as unicode.	1168	B<wchar_t> is represented as unicode.
490		1169
491	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
492	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
493	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.
494		1173
495	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
496	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>.
497		1176
…		…
511		1190
512	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
513	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
514	complete replacements for them :)	1193	complete replacements for them :)
515		1194
516	=item I use Solaris 9 and it doesn't compile/work/etc.
517
518	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
519	problems with C<wcwidth> and a compile problem.
520
521	=item How can I use rxvt-unicode under cygwin?	1195	=head3 How can I use rxvt-unicode under cygwin?
522		1196
523	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
524	the X11 libraries that come with cygwin. libW11 emulation is no	1198	the X11 libraries that come with cygwin. libW11 emulation is no
525	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
526	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
…		…
529		1203
530	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
531	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
532	to 8-bit encodings.	1206	to 8-bit encodings.
533		1207
534	=item How does rxvt-unicode determine the encoding to use?	1208	=head3 Character widths are not correct.
535		1209
536	=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.
537		1215
538	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
539	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
540	UTF-8 or any other encodings with respect to terminal I/O.
541		1218
542	The reasons is that there exists a perfectly fine mechanism for selecting	1219	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
543	the encoding, doing I/O and (most important) communicating this to all
544	applications so everybody agrees on character properties such as width
545	and code number. This mechanism is the I<locale>. Applications not using
546	that info will have problems (for example, C<xterm> gets the width of
547	characters wrong as it uses it's own, locale-independent table under all
548	locales).
549		1220
550	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
551	programs doing the same (that is, most) will automatically agree in the
552	interpretation of characters.
553
554	Unfortunately, there is no system-independent way to select locales, nor
555	is there a standard on how locale specifiers will look like.
556
557	On most systems, the content of the C<LC_CTYPE> environment variable
558	contains an arbitrary string which corresponds to an already-installed
559	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
560	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
561	(i.e. C<de> or C<german>) are also common.
562
563	Rxvt-unicode ignores all other locale categories, and except for
564	the encoding, ignores country or language-specific settings,
565	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
566	rxvt-unicode.
567
568	If you want to use a specific encoding you have to make sure you start
569	rxvt-unicode with the correct C<LC_CTYPE> category.
570
571	=item Can I switch locales at runtime?
572
573	Yes, using an escape sequence. Try something like this, which sets
574	rxvt-unicode's idea of C<LC_CTYPE>.
575
576	printf '\e]701;%s\007' ja_JP.SJIS
577
578	See also the previous answer.
579
580	Sometimes this capability is rather handy when you want to work in
581	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
582	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
583	first switches to a locale supported by xjdic and back later:
584
585	printf '\e]701;%s\007' ja_JP.SJIS
586	xjdic -js
587	printf '\e]701;%s\007' de_DE.UTF-8
588
589	You can also use xterm's C<luit> program, which usually works fine, except
590	for some locales where character width differs between program- and
591	rxvt-unicode-locales.
592
593	=item Can I switch the fonts at runtime?
594
595	Yes, using an escape sequence. Try something like this, which has the same
596	effect as using the C<-fn> switch, and takes effect immediately:
597
598	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
599
600	This is useful if you e.g. work primarily with japanese (and prefer a
601	japanese font), but you have to switch to chinese temporarily, where
602	japanese fonts would only be in your way.
603
604	You can think of this as a kind of manual ISO-2022 switching.
605
606	=item Why do italic characters look as if clipped?
607
608	Many fonts have difficulties with italic characters and hinting. For
609	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
610	Mono> completely fails in it's italic face. A workaround might be to
611	enable freetype autohinting, i.e. like this:
612
613	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
614	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
615
616	=item My input method wants <some encoding> but I want UTF-8, what can I do?
617
618	You can specify separate locales for the input method and the rest of the
619	terminal, using the resource C<imlocale>:
620
621	URxvt.imlocale: ja_JP.EUC-JP
622
623	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
624	use your input method. Please note, however, that you will not be able to
625	input characters outside C<EUC-JP> in a normal way then, as your input
626	method limits you.
627
628	=item Rxvt-unicode crashes when the X Input Method changes or exits.
629
630	Unfortunately, this is unavoidable, as the XIM protocol is racy by
631	design. Applications can avoid some crashes at the expense of memory
632	leaks, and Input Methods can avoid some crashes by careful ordering at
633	exit time. B<kinput2> (and derived input methods) generally succeeds,
634	while B<SCIM> (or similar input methods) fails. In the end, however,
635	crashes cannot be completely avoided even if both sides cooperate.
636
637	So the only workaround is not to kill your Input Method Servers.
638
639	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
640
641	Rxvt-unicode tries to obey the rule of not charging you for something you
642	don't use. One thing you should try is to configure out all settings that
643	you don't need, for example, Xft support is a resource hog by design,
644	when used. Compiling it out ensures that no Xft font will be loaded
645	accidentally when rxvt-unicode tries to find a font for your characters.
646
647	Also, many people (me included) like large windows and even larger
648	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
649	6 bytes per screen cell. For a 160x?? window this amounts to almost a
650	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
651	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
652	rxvt-unicode then uses 8 bytes per screen cell.
653
654	=item Can I speed up Xft rendering somehow?
655
656	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
657	it is simply slow. If you still want Xft fonts you might try to disable
658	antialiasing (by appending C<:antialias=false>), which saves lots of
659	memory and also speeds up rendering considerably.
660
661	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
662
663	Rxvt-unicode will use whatever you specify as a font. If it needs to
664	fall back to it's default font search list it will prefer X11 core
665	fonts, because they are small and fast, and then use Xft fonts. It has
666	antialiasing disabled for most of them, because the author thinks they
667	look best that way.
668
669	If you want antialiasing, you have to specify the fonts manually.
670
671	=item Mouse cut/paste suddenly no longer works.
672
673	Make sure that mouse reporting is actually turned off since killing
674	some editors prematurely may leave the mouse in mouse report mode. I've
675	heard that tcsh may use mouse reporting unless it otherwise specified. A
676	quick check is to see if cut/paste works when the Alt or Shift keys are
677	depressed.
678
679	=item What's with this bold/blink stuff?
680
681	If no bold colour is set via C<colorBD:>, bold will invert text using the
682	standard foreground colour.
683
684	For the standard background colour, blinking will actually make the
685	text blink when compiled with C<--enable-blinking>. with standard
686	colours. Without C<--enable-blinking>, the blink attribute will be
687	ignored.
688
689	On ANSI colours, bold/blink attributes are used to set high-intensity
690	foreground/background colors.
691
692	color0-7 are the low-intensity colors.
693
694	color8-15 are the corresponding high-intensity colors.
695
696	=item I don't like the screen colors. How do I change them?
697
698	You can change the screen colors at run-time using F<~/.Xdefaults>
699	resources (or as long-options).
700
701	Here are values that are supposed to resemble a VGA screen,
702	including the murky brown that passes for low-intensity yellow:
703
704	URxvt.color0: #000000
705	URxvt.color1: #A80000
706	URxvt.color2: #00A800
707	URxvt.color3: #A8A800
708	URxvt.color4: #0000A8
709	URxvt.color5: #A800A8
710	URxvt.color6: #00A8A8
711	URxvt.color7: #A8A8A8
712
713	URxvt.color8: #000054
714	URxvt.color9: #FF0054
715	URxvt.color10: #00FF54
716	URxvt.color11: #FFFF54
717	URxvt.color12: #0000FF
718	URxvt.color13: #FF00FF
719	URxvt.color14: #00FFFF
720	URxvt.color15: #FFFFFF
721
722	And here is a more complete set of non-standard colors described (not by
723	me) as "pretty girly".
724
725	URxvt.cursorColor: #dc74d1
726	URxvt.pointerColor: #dc74d1
727	URxvt.background: #0e0e0e
728	URxvt.foreground: #4ad5e1
729	URxvt.color0: #000000
730	URxvt.color8: #8b8f93
731	URxvt.color1: #dc74d1
732	URxvt.color9: #dc74d1
733	URxvt.color2: #0eb8c7
734	URxvt.color10: #0eb8c7
735	URxvt.color3: #dfe37e
736	URxvt.color11: #dfe37e
737	URxvt.color5: #9e88f0
738	URxvt.color13: #9e88f0
739	URxvt.color6: #73f7ff
740	URxvt.color14: #73f7ff
741	URxvt.color7: #e1dddd
742	URxvt.color15: #e1dddd
743
744	=item How can I start @@RXVT_NAME@@d in a race-free way?
745
746	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
747	display, create the listening socket and then fork.
748
749	=item What's with the strange Backspace/Delete key behaviour?
750
751	Assuming that the physical Backspace key corresponds to the
752	BackSpace keysym (not likely for Linux ... see the following
753	question) there are two standard values that can be used for
754	Backspace: C<^H> and C<^?>.
755
756	Historically, either value is correct, but rxvt-unicode adopts the debian
757	policy of using C<^?> when unsure, because it's the one only only correct
758	choice :).
759
760	Rxvt-unicode tries to inherit the current stty settings and uses the value
761	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
762	started from a terminal (say, from a menu or by remote shell), then the
763	system value of `erase', which corresponds to CERASE in <termios.h>, will
764	be used (which may not be the same as your stty setting).
765
766	For starting a new rxvt-unicode:
767
768	# use Backspace = ^H
769	$ stty erase ^H
770	$ @@RXVT_NAME@@
771
772	# use Backspace = ^?
773	$ stty erase ^?
774	$ @@RXVT_NAME@@
775
776	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
777
778	For an existing rxvt-unicode:
779
780	# use Backspace = ^H
781	$ stty erase ^H
782	$ echo -n "^[[36h"
783
784	# use Backspace = ^?
785	$ stty erase ^?
786	$ echo -n "^[[36l"
787
788	This helps satisfy some of the Backspace discrepancies that occur, but
789	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
790	properly reflects that.
791
792	The Delete key is a another casualty of the ill-defined Backspace problem.
793	To avoid confusion between the Backspace and Delete keys, the Delete
794	key has been assigned an escape sequence to match the vt100 for Execute
795	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
796
797	Some other Backspace problems:
798
799	some editors use termcap/terminfo,
800	some editors (vim I'm told) expect Backspace = ^H,
801	GNU Emacs (and Emacs-like editors) use ^H for help.
802
803	Perhaps someday this will all be resolved in a consistent manner.
804
805	=item I don't like the key-bindings. How do I change them?
806
807	There are some compile-time selections available via configure. Unless
808	you have run "configure" with the C<--disable-resources> option you can
809	use the `keysym' resource to alter the keystrings associated with keysyms.
810
811	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
812
813	URxvt.keysym.Home: \033[1~
814	URxvt.keysym.End: \033[4~
815	URxvt.keysym.C-apostrophe: \033<C-'>
816	URxvt.keysym.C-slash: \033<C-/>
817	URxvt.keysym.C-semicolon: \033<C-;>
818	URxvt.keysym.C-grave: \033<C-`>
819	URxvt.keysym.C-comma: \033<C-,>
820	URxvt.keysym.C-period: \033<C-.>
821	URxvt.keysym.C-0x60: \033<C-`>
822	URxvt.keysym.C-Tab: \033<C-Tab>
823	URxvt.keysym.C-Return: \033<C-Return>
824	URxvt.keysym.S-Return: \033<S-Return>
825	URxvt.keysym.S-space: \033<S-Space>
826	URxvt.keysym.M-Up: \033<M-Up>
827	URxvt.keysym.M-Down: \033<M-Down>
828	URxvt.keysym.M-Left: \033<M-Left>
829	URxvt.keysym.M-Right: \033<M-Right>
830	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
831	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
832	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
833
834	See some more examples in the documentation for the B<keysym> resource.
835
836	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
837	How do I make use of them? For example, the Sun Keyboard type 4
838	has the following mappings that rxvt-unicode doesn't recognize.
839
840	KP_Insert == Insert
841	F22 == Print
842	F27 == Home
843	F29 == Prior
844	F33 == End
845	F35 == Next
846
847	Rather than have rxvt-unicode try to accommodate all the various possible
848	keyboard mappings, it is better to use `xmodmap' to remap the keys as
849	required for your particular machine.
850
851	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
852	I need this to decide about setting colors etc.
853
854	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
855	check and see if that is set. Note that several programs, JED, slrn,
856	Midnight Commander automatically check this variable to decide whether or
857	not to use color.
858
859	=item How do I set the correct, full IP address for the DISPLAY variable?
860
861	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
862	insecure mode then it is possible to use the following shell script
863	snippets to correctly set the display. If your version of rxvt-unicode
864	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
865	the COLORTERM variable can be used to distinguish rxvt-unicode from a
866	regular xterm.
867
868	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
869	snippets:
870
871	# Bourne/Korn/POSIX family of shells:
872	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
873	if [ ${TERM:-foo} = xterm ]; then
874	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
875	echo -n '^[Z'
876	read term_id
877	stty icanon echo
878	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
879	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
880	read DISPLAY # set it in our local shell
881	fi
882	fi
883
884	=item How do I compile the manual pages for myself?
885
886	You need to have a recent version of perl installed as F</usr/bin/perl>,
887	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
888	the doc subdirectory and enter C<make alldoc>.
889
890	=item My question isn't answered here, can I ask a human?
891
892	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
893	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
894	interested in learning about new and exciting problems (but not FAQs :).
895
896	=back
897
898	=head1 RXVT TECHNICAL REFERENCE	1221	=head1 RXVT-UNICODE TECHNICAL REFERENCE
899
900	=head1 DESCRIPTION
901		1222
902	The rest of this document describes various technical aspects of	1223	The rest of this document describes various technical aspects of
903	B<rxvt-unicode>. First the description of supported command sequences,	1224	B<rxvt-unicode>. First the description of supported command sequences,
904	followed by menu and pixmap support and last by a description of all	1225	followed by pixmap support and last by a description of all features
905	features selectable at C<configure> time.	1226	selectable at C<configure> time.
906		1227
907	=head1 Definitions	1228	=head2 Definitions
908		1229
909	=over 4	1230	=over 4
910		1231
911	=item B<< C<c> >>	1232	=item B<< C<c> >>
912		1233
…		…
930		1251
931	A text parameter composed of printable characters.	1252	A text parameter composed of printable characters.
932		1253
933	=back	1254	=back
934		1255
935	=head1 Values	1256	=head2 Values
936		1257
937	=over 4	1258	=over 4
938		1259
939	=item B<< C<ENQ> >>	1260	=item B<< C<ENQ> >>
940		1261
…		…
983		1304
984	Space Character	1305	Space Character
985		1306
986	=back	1307	=back
987		1308
988	=head1 Escape Sequences	1309	=head2 Escape Sequences
989		1310
990	=over 4	1311	=over 4
991		1312
992	=item B<< C<ESC # 8> >>	1313	=item B<< C<ESC # 8> >>
993		1314
…		…
1091		1412
1092	=back	1413	=back
1093		1414
1094	X<CSI>	1415	X<CSI>
1095		1416
1096	=head1 CSI (Command Sequence Introducer) Sequences	1417	=head2 CSI (Command Sequence Introducer) Sequences
1097		1418
1098	=over 4	1419	=over 4
1099		1420
1100	=item B<< C<ESC [ Ps @> >>	1421	=item B<< C<ESC [ Ps @> >>
1101		1422
…		…
1371		1692
1372	=back	1693	=back
1373		1694
1374	X<PrivateModes>	1695	X<PrivateModes>
1375		1696
1376	=head1 DEC Private Modes	1697	=head2 DEC Private Modes
1377		1698
1378	=over 4	1699	=over 4
1379		1700
1380	=item B<< C<ESC [ ? Pm h> >>	1701	=item B<< C<ESC [ ? Pm h> >>
1381		1702
…		…
1397		1718
1398	Toggle DEC Private Mode Values (rxvt extension). I<where>	1719	Toggle DEC Private Mode Values (rxvt extension). I<where>
1399		1720
1400	=over 4	1721	=over 4
1401		1722
1402	=item B<< C<Ps = 1> >> (DECCKM)	1723	=item B<< C<Pm = 1> >> (DECCKM)
1403		1724
1404	=begin table	1725	=begin table
1405		1726
1406	B<< C<h> >> Application Cursor Keys	1727	B<< C<h> >> Application Cursor Keys
1407	B<< C<l> >> Normal Cursor Keys	1728	B<< C<l> >> Normal Cursor Keys
1408		1729
1409	=end table	1730	=end table
1410		1731
1411	=item B<< C<Ps = 2> >> (ANSI/VT52 mode)	1732	=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1412		1733
1413	=begin table	1734	=begin table
1414		1735
1415	B<< C<h> >> Enter VT52 mode	1736	B<< C<h> >> Enter VT52 mode
1416	B<< C<l> >> Enter VT52 mode	1737	B<< C<l> >> Enter VT52 mode
1417		1738
1418	=end table	1739	=end table
1419		1740
1420	=item B<< C<Ps = 3> >>	1741	=item B<< C<Pm = 3> >>
1421		1742
1422	=begin table	1743	=begin table
1423		1744
1424	B<< C<h> >> 132 Column Mode (DECCOLM)	1745	B<< C<h> >> 132 Column Mode (DECCOLM)
1425	B<< C<l> >> 80 Column Mode (DECCOLM)	1746	B<< C<l> >> 80 Column Mode (DECCOLM)
1426		1747
1427	=end table	1748	=end table
1428		1749
1429	=item B<< C<Ps = 4> >>	1750	=item B<< C<Pm = 4> >>
1430		1751
1431	=begin table	1752	=begin table
1432		1753
1433	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)	1754	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1434	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)	1755	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1435		1756
1436	=end table	1757	=end table
1437		1758
1438	=item B<< C<Ps = 5> >>	1759	=item B<< C<Pm = 5> >>
1439		1760
1440	=begin table	1761	=begin table
1441		1762
1442	B<< C<h> >> Reverse Video (DECSCNM)	1763	B<< C<h> >> Reverse Video (DECSCNM)
1443	B<< C<l> >> Normal Video (DECSCNM)	1764	B<< C<l> >> Normal Video (DECSCNM)
1444		1765
1445	=end table	1766	=end table
1446		1767
1447	=item B<< C<Ps = 6> >>	1768	=item B<< C<Pm = 6> >>
1448		1769
1449	=begin table	1770	=begin table
1450		1771
1451	B<< C<h> >> Origin Mode (DECOM)	1772	B<< C<h> >> Origin Mode (DECOM)
1452	B<< C<l> >> Normal Cursor Mode (DECOM)	1773	B<< C<l> >> Normal Cursor Mode (DECOM)
1453		1774
1454	=end table	1775	=end table
1455		1776
1456	=item B<< C<Ps = 7> >>	1777	=item B<< C<Pm = 7> >>
1457		1778
1458	=begin table	1779	=begin table
1459		1780
1460	B<< C<h> >> Wraparound Mode (DECAWM)	1781	B<< C<h> >> Wraparound Mode (DECAWM)
1461	B<< C<l> >> No Wraparound Mode (DECAWM)	1782	B<< C<l> >> No Wraparound Mode (DECAWM)
1462		1783
1463	=end table	1784	=end table
1464		1785
1465	=item B<< C<Ps = 8> >> I<unimplemented>	1786	=item B<< C<Pm = 8> >> I<unimplemented>
1466		1787
1467	=begin table	1788	=begin table
1468		1789
1469	B<< C<h> >> Auto-repeat Keys (DECARM)	1790	B<< C<h> >> Auto-repeat Keys (DECARM)
1470	B<< C<l> >> No Auto-repeat Keys (DECARM)	1791	B<< C<l> >> No Auto-repeat Keys (DECARM)
1471		1792
1472	=end table	1793	=end table
1473		1794
1474	=item B<< C<Ps = 9> >> X10 XTerm	1795	=item B<< C<Pm = 9> >> X10 XTerm
1475		1796
1476	=begin table	1797	=begin table
1477		1798
1478	B<< C<h> >> Send Mouse X & Y on button press.	1799	B<< C<h> >> Send Mouse X & Y on button press.
1479	B<< C<l> >> No mouse reporting.	1800	B<< C<l> >> No mouse reporting.
1480		1801
1481	=end table	1802	=end table
1482		1803
1483	=item B<< C<Ps = 25> >>	1804	=item B<< C<Pm = 25> >>
1484		1805
1485	=begin table	1806	=begin table
1486		1807
1487	B<< C<h> >> Visible cursor {cnorm/cvvis}	1808	B<< C<h> >> Visible cursor {cnorm/cvvis}
1488	B<< C<l> >> Invisible cursor {civis}	1809	B<< C<l> >> Invisible cursor {civis}
1489		1810
1490	=end table	1811	=end table
1491		1812
1492	=item B<< C<Ps = 30> >>	1813	=item B<< C<Pm = 30> >>
1493		1814
1494	=begin table	1815	=begin table
1495		1816
1496	B<< C<h> >> scrollBar visisble	1817	B<< C<h> >> scrollBar visible
1497	B<< C<l> >> scrollBar invisisble	1818	B<< C<l> >> scrollBar invisible
1498		1819
1499	=end table	1820	=end table
1500		1821
1501	=item B<< C<Ps = 35> >> (B<rxvt>)	1822	=item B<< C<Pm = 35> >> (B<rxvt>)
1502		1823
1503	=begin table	1824	=begin table
1504		1825
1505	B<< C<h> >> Allow XTerm Shift+key sequences	1826	B<< C<h> >> Allow XTerm Shift+key sequences
1506	B<< C<l> >> Disallow XTerm Shift+key sequences	1827	B<< C<l> >> Disallow XTerm Shift+key sequences
1507		1828
1508	=end table	1829	=end table
1509		1830
1510	=item B<< C<Ps = 38> >> I<unimplemented>	1831	=item B<< C<Pm = 38> >> I<unimplemented>
1511		1832
1512	Enter Tektronix Mode (DECTEK)	1833	Enter Tektronix Mode (DECTEK)
1513		1834
1514	=item B<< C<Ps = 40> >>	1835	=item B<< C<Pm = 40> >>
1515		1836
1516	=begin table	1837	=begin table
1517		1838
1518	B<< C<h> >> Allow 80/132 Mode	1839	B<< C<h> >> Allow 80/132 Mode
1519	B<< C<l> >> Disallow 80/132 Mode	1840	B<< C<l> >> Disallow 80/132 Mode
1520		1841
1521	=end table	1842	=end table
1522		1843
1523	=item B<< C<Ps = 44> >> I<unimplemented>	1844	=item B<< C<Pm = 44> >> I<unimplemented>
1524		1845
1525	=begin table	1846	=begin table
1526		1847
1527	B<< C<h> >> Turn On Margin Bell	1848	B<< C<h> >> Turn On Margin Bell
1528	B<< C<l> >> Turn Off Margin Bell	1849	B<< C<l> >> Turn Off Margin Bell
1529		1850
1530	=end table	1851	=end table
1531		1852
1532	=item B<< C<Ps = 45> >> I<unimplemented>	1853	=item B<< C<Pm = 45> >> I<unimplemented>
1533		1854
1534	=begin table	1855	=begin table
1535		1856
1536	B<< C<h> >> Reverse-wraparound Mode	1857	B<< C<h> >> Reverse-wraparound Mode
1537	B<< C<l> >> No Reverse-wraparound Mode	1858	B<< C<l> >> No Reverse-wraparound Mode
1538		1859
1539	=end table	1860	=end table
1540		1861
1541	=item B<< C<Ps = 46> >> I<unimplemented>	1862	=item B<< C<Pm = 46> >> I<unimplemented>
1542		1863
1543	=item B<< C<Ps = 47> >>	1864	=item B<< C<Pm = 47> >>
1544		1865
1545	=begin table	1866	=begin table
1546		1867
1547	B<< C<h> >> Use Alternate Screen Buffer	1868	B<< C<h> >> Use Alternate Screen Buffer
1548	B<< C<l> >> Use Normal Screen Buffer	1869	B<< C<l> >> Use Normal Screen Buffer
1549		1870
1550	=end table	1871	=end table
1551		1872
1552	X<Priv66>	1873	X<Priv66>
1553		1874
1554	=item B<< C<Ps = 66> >>	1875	=item B<< C<Pm = 66> >>
1555		1876
1556	=begin table	1877	=begin table
1557		1878
1558	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>	1879	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1559	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>	1880	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1560		1881
1561	=end table	1882	=end table
1562		1883
1563	=item B<< C<Ps = 67> >>	1884	=item B<< C<Pm = 67> >>
1564		1885
1565	=begin table	1886	=begin table
1566		1887
1567	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>	1888	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1568	B<< C<l> >> Backspace key sends B<< C<DEL> >>	1889	B<< C<l> >> Backspace key sends B<< C<DEL> >>
1569		1890
1570	=end table	1891	=end table
1571		1892
1572	=item B<< C<Ps = 1000> >> (X11 XTerm)	1893	=item B<< C<Pm = 1000> >> (X11 XTerm)
1573		1894
1574	=begin table	1895	=begin table
1575		1896
1576	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.
1577	B<< C<l> >> No mouse reporting.	1898	B<< C<l> >> No mouse reporting.
1578		1899
1579	=end table	1900	=end table
1580		1901
1581	=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented>	1902	=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1582		1903
1583	=begin table	1904	=begin table
1584		1905
1585	B<< C<h> >> Use Hilite Mouse Tracking.	1906	B<< C<h> >> Use Hilite Mouse Tracking.
1586	B<< C<l> >> No mouse reporting.	1907	B<< C<l> >> No mouse reporting.
1587		1908
1588	=end table	1909	=end table
1589		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
1590	=item B<< C<Ps = 1010> >> (B<rxvt>)	1929	=item B<< C<Pm = 1010> >> (B<rxvt>)
1591		1930
1592	=begin table	1931	=begin table
1593		1932
1594	B<< C<h> >> Don't scroll to bottom on TTY output	1933	B<< C<h> >> Don't scroll to bottom on TTY output
1595	B<< C<l> >> Scroll to bottom on TTY output	1934	B<< C<l> >> Scroll to bottom on TTY output
1596		1935
1597	=end table	1936	=end table
1598		1937
1599	=item B<< C<Ps = 1011> >> (B<rxvt>)	1938	=item B<< C<Pm = 1011> >> (B<rxvt>)
1600		1939
1601	=begin table	1940	=begin table
1602		1941
1603	B<< C<h> >> Scroll to bottom when a key is pressed	1942	B<< C<h> >> Scroll to bottom when a key is pressed
1604	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
1605		1944
1606	=end table	1945	=end table
1607		1946
1608	=item B<< C<Ps = 1021> >> (B<rxvt>)	1947	=item B<< C<Pm = 1021> >> (B<rxvt>)
1609		1948
1610	=begin table	1949	=begin table
1611		1950
1612	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>)
1613	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)
1614		1953
1615	=end table	1954	=end table
1616		1955
1617	=item B<< C<Ps = 1047> >>	1956	=item B<< C<Pm = 1047> >>
1618		1957
1619	=begin table	1958	=begin table
1620		1959
1621	B<< C<h> >> Use Alternate Screen Buffer	1960	B<< C<h> >> Use Alternate Screen Buffer
1622	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
1623		1962
1624	=end table	1963	=end table
1625		1964
1626	=item B<< C<Ps = 1048> >>	1965	=item B<< C<Pm = 1048> >>
1627		1966
1628	=begin table	1967	=begin table
1629		1968
1630	B<< C<h> >> Save cursor position	1969	B<< C<h> >> Save cursor position
1631	B<< C<l> >> Restore cursor position	1970	B<< C<l> >> Restore cursor position
1632		1971
1633	=end table	1972	=end table
1634		1973
1635	=item B<< C<Ps = 1049> >>	1974	=item B<< C<Pm = 1049> >>
1636		1975
1637	=begin table	1976	=begin table
1638		1977
1639	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
1640	B<< C<l> >> Use Normal Screen Buffer	1979	B<< C<l> >> Use Normal Screen Buffer
…		…
1645		1984
1646	=back	1985	=back
1647		1986
1648	X<XTerm>	1987	X<XTerm>
1649		1988
1650	=head1 XTerm Operating System Commands	1989	=head2 XTerm Operating System Commands
1651		1990
1652	=over 4	1991	=over 4
1653		1992
1654	=item B<< C<ESC ] Ps;Pt ST> >>	1993	=item B<< C<ESC ] Ps;Pt ST> >>
1655		1994
…		…
1662	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> >>
1663	B<< C<Ps = 1> >> Change Icon Name to B<< C<Pt> >>	2002	B<< C<Ps = 1> >> Change Icon Name to B<< C<Pt> >>
1664	B<< C<Ps = 2> >> Change Window Title to B<< C<Pt> >>	2003	B<< C<Ps = 2> >> Change Window Title to B<< C<Pt> >>
1665	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.
1666	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
1667	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> >>
1668	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> >>
1669	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> >>
1670	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> >>
1671	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> >>
1672	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]
1673	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]
1674	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	2013	B<< C<Ps = 20> >> Change background pixmap parameters (see section BACKGROUND IMAGE) (Compile AfterImage).
1675	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]
1676	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>
1677	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]
1678	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> >>
1679	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> >>
1680	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).
		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>.
1681	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> >>
1682	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	2022	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1683	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>	2023	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
1684	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>	2024	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1685	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	2025	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
…		…
1692		2032
1693	=end table	2033	=end table
1694		2034
1695	=back	2035	=back
1696		2036
1697	X<XPM>	2037	=head1 BACKGROUND IMAGE
1698		2038
1699	=head1 XPM
1700
1701	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
1702	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
1703	sequence of scaling/positioning commands separated by semi-colons. The	2041	sequence of scaling/positioning commands separated by semi-colons. The
1704	scaling/positioning commands are as follows:	2042	scaling/positioning commands are as follows:
1705		2043
1706	=over 4	2044	=over 4
1707		2045
…		…
1745		2083
1746	For example:	2084	For example:
1747		2085
1748	=over 4	2086	=over 4
1749		2087
1750	=item B<\E]20;funky\a>	2088	=item B<\E]20;funky.jpg\a>
1751		2089
1752	load B<funky.xpm> as a tiled image	2090	load B<funky.jpg> as a tiled image
1753		2091
1754	=item B<\E]20;mona;100\a>	2092	=item B<\E]20;mona.jpg;100\a>
1755		2093
1756	load B<mona.xpm> with a scaling of 100%	2094	load B<mona.jpg> with a scaling of 100%
1757		2095
1758	=item B<\E]20;;200;?\a>	2096	=item B<\E]20;;200;?\a>
1759		2097
1760	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
1761	the title	2099	the title
…		…
1800	=begin table	2138	=begin table
1801		2139
1802	4 Shift	2140	4 Shift
1803	8 Meta	2141	8 Meta
1804	16 Control	2142	16 Control
1805	32 Double Click I<(Rxvt extension)>	2143	32 Double Click I<(rxvt extension)>
1806		2144
1807	=end table	2145	=end table
1808		2146
1809	Col = B<< C<< <x> - SPACE >> >>	2147	Col = B<< C<< <x> - SPACE >> >>
1810		2148
…		…
1888		2226
1889	=head1 CONFIGURE OPTIONS	2227	=head1 CONFIGURE OPTIONS
1890		2228
1891	General hint: if you get compile errors, then likely your configuration	2229	General hint: if you get compile errors, then likely your configuration
1892	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
1893	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>
1894	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
1895	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>.
1896	Lehmann <rxvt@schmorp.de>.
1897		2234
1898	All	2235	All
1899		2236
1900	=over 4	2237	=over 4
1901		2238
…		…
1933		2270
1934	=begin table	2271	=begin table
1935		2272
1936	all all available codeset groups	2273	all all available codeset groups
1937	zh common chinese encodings	2274	zh common chinese encodings
1938	zh_ext rarely used but very big chinese encodigs	2275	zh_ext rarely used but very big chinese encodings
1939	jp common japanese encodings	2276	jp common japanese encodings
1940	jp_ext rarely used but big japanese encodings	2277	jp_ext rarely used but big japanese encodings
1941	kr korean encodings	2278	kr korean encodings
1942		2279
1943	=end table	2280	=end table
…		…
1947	Add support for XIM (X Input Method) protocol. This allows using	2284	Add support for XIM (X Input Method) protocol. This allows using
1948	alternative input methods (e.g. kinput2) and will also correctly	2285	alternative input methods (e.g. kinput2) and will also correctly
1949	set up the input for people using dead keys or compose keys.	2286	set up the input for people using dead keys or compose keys.
1950		2287
1951	=item --enable-unicode3 (default: off)	2288	=item --enable-unicode3 (default: off)
		2289
		2290	Recommended to stay off unless you really need non-BMP characters.
1952		2291
1953	Enable direct support for displaying unicode codepoints above	2292	Enable direct support for displaying unicode codepoints above
1954	65535 (the basic multilingual page). This increases storage	2293	65535 (the basic multilingual page). This increases storage
1955	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
1956	support these extra characters, but Xft does.	2295	support these extra characters, but Xft does.
1957		2296
1958	Please note that rxvt-unicode can store unicode code points >65535	2297	Please note that rxvt-unicode can store unicode code points >65535
1959	even without this flag, but the number of such characters is	2298	even without this flag, but the number of such characters is
1960	limited to a view thousand (shared with combining characters,	2299	limited to a few thousand (shared with combining characters,
1961	see next switch), and right now rxvt-unicode cannot display them	2300	see next switch), and right now rxvt-unicode cannot display them
1962	(input/output and cut&paste still work, though).	2301	(input/output and cut&paste still work, though).
1963		2302
1964	=item --enable-combining (default: on)	2303	=item --enable-combining (default: on)
1965		2304
…		…
1967	composite characters. This is required for proper viewing of text	2306	composite characters. This is required for proper viewing of text
1968	where accents are encoded as seperate unicode characters. This is	2307	where accents are encoded as seperate unicode characters. This is
1969	done by using precomposited characters when available or creating	2308	done by using precomposited characters when available or creating
1970	new pseudo-characters when no precomposed form exists.	2309	new pseudo-characters when no precomposed form exists.
1971		2310
1972	Without --enable-unicode3, the number of additional precomposed characters	2311	Without --enable-unicode3, the number of additional precomposed
1973	is rather limited (2048, if this is full, rxvt-unicode will use the	2312	characters is somewhat limited (the 6400 private use characters will be
1974	private use area, extending the number of combinations to 8448). With
1975	--enable-unicode3, no practical limit exists.	2313	(ab-)used). With --enable-unicode3, no practical limit exists.
1976		2314
1977	This option will also enable storage (but not display) of characters	2315	This option will also enable storage (but not display) of characters
1978	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2316	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1979		2317
1980	The combining table also contains entries for arabic presentation forms,	2318	The combining table also contains entries for arabic presentation forms,
1981	but these are not currently used. Bug me if you want these to be used (and	2319	but these are not currently used. Bug me if you want these to be used (and
1982	tell me how these are to be used...).	2320	tell me how these are to be used...).
1983		2321
1984	=item --enable-fallback(=CLASS) (default: Rxvt)	2322	=item --enable-fallback(=CLASS) (default: Rxvt)
1985		2323
1986	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.	2324	When reading resource settings, also read settings for class CLASS. To
		2325	disable resource fallback use --disable-fallback.
1987		2326
1988	=item --with-res-name=NAME (default: urxvt)	2327	=item --with-res-name=NAME (default: urxvt)
1989		2328
1990	Use the given name as default application name when	2329	Use the given name as default application name when
1991	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2330	reading resources. Specify --with-res-name=rxvt to replace rxvt.
1992		2331
1993	=item --with-res-class=CLASS /default: URxvt)	2332	=item --with-res-class=CLASS (default: URxvt)
1994		2333
1995	Use the given class as default application class	2334	Use the given class as default application class
1996	when reading resources. Specify --with-res-class=Rxvt to replace	2335	when reading resources. Specify --with-res-class=Rxvt to replace
1997	rxvt.	2336	rxvt.
1998		2337
…		…
2011		2350
2012	Write user and tty to lastlog file (used by programs like	2351	Write user and tty to lastlog file (used by programs like
2013	F<lastlogin>) at start of rxvt execution. This option requires	2352	F<lastlogin>) at start of rxvt execution. This option requires
2014	--enable-utmp to also be specified.	2353	--enable-utmp to also be specified.
2015		2354
2016	=item --enable-xpm-background (default: on)	2355	=item --enable-afterimage (default: on)
2017		2356
2018	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.
2019		2369
2020	=item --enable-transparency (default: on)	2370	=item --enable-transparency (default: on)
2021		2371
2022	Add support for inheriting parent backgrounds thus giving a fake	2372	Add support for backgrounds, creating illusion of transparency in the term.
2023	transparency to the term.
2024		2373
2025	=item --enable-fading (default: on)	2374	=item --enable-fading (default: on)
2026		2375
2027	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.
2028
2029	=item --enable-tinting (default: on)
2030
2031	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2032		2377
2033	=item --enable-rxvt-scroll (default: on)	2378	=item --enable-rxvt-scroll (default: on)
2034		2379
2035	Add support for the original rxvt scrollbar.	2380	Add support for the original rxvt scrollbar.
2036		2381
…		…
2046		2391
2047	Add support for a very unobtrusive, plain-looking scrollbar that	2392	Add support for a very unobtrusive, plain-looking scrollbar that
2048	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
2049	many years.	2394	many years.
2050		2395
2051	=item --enable-half-shadow (default: off)
2052
2053	Make shadows on the scrollbar only half the normal width & height.
2054	only applicable to rxvt scrollbars.
2055
2056	=item --enable-ttygid (default: off)
2057
2058	Change tty device setting to group "tty" - only use this if
2059	your system uses this type of security.
2060
2061	=item --disable-backspace-key	2396	=item --disable-backspace-key
2062		2397
2063	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.
2064		2399
2065	=item --disable-delete-key	2400	=item --disable-delete-key
…		…
2084	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
2085	in combination with other switches) is:	2420	in combination with other switches) is:
2086		2421
2087	MWM-hints	2422	MWM-hints
2088	EWMH-hints (pid, utf8 names) and protocols (ping)	2423	EWMH-hints (pid, utf8 names) and protocols (ping)
		2424	urgency hint
2089	seperate underline colour (-underlineColor)	2425	seperate underline colour (-underlineColor)
2090	settable border widths and borderless switch (-w, -b, -bl)	2426	settable border widths and borderless switch (-w, -b, -bl)
		2427	visual depth selection (-depth)
2091	settable extra linespacing /-lsp)	2428	settable extra linespacing /-lsp)
2092	iso-14755-2 and -3, and visual feedback	2429	iso-14755 5.1 (basic) support
2093	backindex and forwardindex escape sequence
2094	window op and some xterm/OSC escape sequences
2095	tripleclickwords (-tcw)	2430	tripleclickwords (-tcw)
2096	settable insecure mode (-insecure)	2431	settable insecure mode (-insecure)
2097	keysym remapping support	2432	keysym remapping support
2098	cursor blinking and underline cursor (-cb, -uc)	2433	cursor blinking and underline cursor (-cb, -uc)
2099	XEmbed support (-embed)	2434	XEmbed support (-embed)
2100	user-pty (-pty-fd)	2435	user-pty (-pty-fd)
2101	hold on exit (-hold)	2436	hold on exit (-hold)
		2437	compile in built-in block graphics
2102	skip builtin block graphics (-sbg)	2438	skip builtin block graphics (-sbg)
		2439	separate highlightcolor support (-hc)
		2440
		2441	It also enables some non-essential features otherwise disabled, such as:
		2442
		2443	some round-trip time optimisations
		2444	nearest color allocation on pseudocolor screens
		2445	UTF8_STRING support for selection
2103	sgr modes 90..97 and 100..107	2446	sgr modes 90..97 and 100..107
		2447	backindex and forwardindex escape sequences
		2448	view change/zero scrollback escape sequences
		2449	locale switching escape sequence
		2450	window op and some xterm/OSC escape sequences
		2451	rectangular selections
		2452	trailing space removal for selections
		2453	verbose X error handling
2104		2454
2105	=item --enable-iso14755 (default: on)	2455	=item --enable-iso14755 (default: on)
2106		2456
2107	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2457	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2108	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2458	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2112	=item --enable-keepscrolling (default: on)	2462	=item --enable-keepscrolling (default: on)
2113		2463
2114	Add support for continual scrolling of the display when you hold	2464	Add support for continual scrolling of the display when you hold
2115	the mouse button down on a scrollbar arrow.	2465	the mouse button down on a scrollbar arrow.
2116		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
2117	=item --enable-mousewheel (default: on)	2472	=item --enable-mousewheel (default: on)
2118		2473
2119	Add support for scrolling via mouse wheel or buttons 4 & 5.	2474	Add support for scrolling via mouse wheel or buttons 4 & 5.
2120		2475
2121	=item --enable-slipwheeling (default: on)	2476	=item --enable-slipwheeling (default: on)
2122		2477
2123	Add support for continual scrolling (using the mouse wheel as an	2478	Add support for continual scrolling (using the mouse wheel as an
2124	accelerator) while the control key is held down. This option	2479	accelerator) while the control key is held down. This option
2125	requires --enable-mousewheel to also be specified.	2480	requires --enable-mousewheel to also be specified.
2126		2481
2127	=item --disable-new-selection
2128
2129	Remove support for mouse selection style like that of xterm.
2130
2131	=item --enable-dmalloc (default: off)
2132
2133	Use Gray Watson's malloc - which is good for debugging See
2134	http://www.letters.com/dmalloc/ for details If you use either this or the
2135	next option, you may need to edit src/Makefile after compiling to point
2136	DINCLUDE and DLIB to the right places.
2137
2138	You can only use either this option and the following (should
2139	you use either) .
2140
2141	=item --enable-dlmalloc (default: off)
2142
2143	Use Doug Lea's malloc - which is good for a production version
2144	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2145
2146	=item --enable-smart-resize (default: on)	2482	=item --enable-smart-resize (default: off)
2147		2483
2148	Add smart growth/shrink behaviour when changing font size via hot	2484	Add smart growth/shrink behaviour when resizing.
2149	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
2150	the screen in a fixed position.	2486	the screen in a fixed position.
2151		2487
		2488	=item --enable-text-blink (default: on)
		2489
		2490	Add support for blinking text.
		2491
2152	=item --enable-pointer-blank (default: on)	2492	=item --enable-pointer-blank (default: on)
2153		2493
2154	Add support to have the pointer disappear when typing or inactive.	2494	Add support to have the pointer disappear when typing or inactive.
2155		2495
2156	=item --enable-perl (default: off)	2496	=item --enable-perl (default: on)
2157		2497
2158	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)>
2159	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
2160	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
2161	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
2162	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.
2163		2510
2164	=item --with-name=NAME (default: urxvt)	2511	=item --with-name=NAME (default: urxvt)
2165		2512
2166	Set the basename for the installed binaries, resulting	2513	Set the basename for the installed binaries, resulting
2167	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
…		…
2177	PATH.	2524	PATH.
2178		2525
2179	=item --with-x	2526	=item --with-x
2180		2527
2181	Use the X Window System (pretty much default, eh?).	2528	Use the X Window System (pretty much default, eh?).
2182
2183	=item --with-xpm-includes=DIR
2184
2185	Look for the XPM includes in DIR.
2186
2187	=item --with-xpm-library=DIR
2188
2189	Look for the XPM library in DIR.
2190
2191	=item --with-xpm
2192
2193	Not needed - define via --enable-xpm-background.
2194		2529
2195	=back	2530	=back
2196		2531
2197	=head1 AUTHORS	2532	=head1 AUTHORS
2198		2533

Diff Legend

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