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.89 by root, Wed Jan 18 21:00:39 2006 UTC vs.
Revision 1.111 by root, Thu Feb 2 00:31:47 2006 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
23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
24		23
25	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		25
27	=over 4
28		26
29	=item The new selection selects pieces that are too big, how can I select	27	=head2 Meta, Features & Commandline Issues
30	single words?
31		28
32	Yes. For example, if you want to select alphanumeric words, you can use	29	=head3 My question isn't answered here, can I ask a human?
33	the following resource:
34		30
35	URxvt.selection.pattern-0: ([[:word:]]+)	31	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		32	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		33	interested in learning about new and exciting problems (but not FAQs :).
36		34
37	If you click more than twice, the selection will be extended	35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
38	more and more.
39		36
40	To get a selection that is very similar to the old code, try this pattern:	37	Beginning with version 7.3, there is a perl extension that implements a
		38	simple tabbed terminal. It is installed by default, so any of these should
		39	give you tabs:
41		40
42	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)	41	@@URXVT_NAME@@ -pe tabbed
43		42
44	Please also note that the I<LeftClick Shift-LeftClik> combination also	43	URxvt.perl-ext-common: default,tabbed
45	selects words like the old code.
46		44
47	=item I don't like the new selection/popups/hotkeys/perl, how do I	45	It will also work fine with tabbing functionality of many window managers
48	change/disable it?	46	or similar tabbing programs, and its embedding-features allow it to be
		47	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		48	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		49	(murxvt) terminal as an example embedding application.
49		50
50	You can disable the perl extension completely by setting the	51	=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		52
54	If you only want to disable specific features, you first have to	53	The version number is displayed with the usage (-h). Also the escape
55	identify which perl extension is responsible. For this, read the section	54	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	55	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	56	daemon.
58	this B<perl-ext-common> resource:
59		57
60	URxvt.perl-ext-common: default,-selection-popup,-option-popup	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
61		59
62	This will keep the default extensions, but disable the two popup	60	Rxvt-unicode tries to obey the rule of not charging you for something you
63	extensions. Some extensions can also be configured, for example,	61	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	62	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:	63	when used. Compiling it out ensures that no Xft font will be loaded
		64	accidentally when rxvt-unicode tries to find a font for your characters.
66		65
67	URxvt.searchable-scrollback: CM-s	66	Also, many people (me included) like large windows and even larger
		67	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		68	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		69	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		70	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		71	rxvt-unicode then uses 8 bytes per screen cell.
68		72
		73	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
		74
		75	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
		76	display, create the listening socket and then fork.
		77
		78	=head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?
		79
		80	If you want to start @@URXVT_NAME@@d automatically whenever you run
		81	@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
		82
		83	#!/bin/sh
		84	@@URXVT_NAME@@c "$@"
		85	if [ $? -eq 2 ]; then
		86	@@URXVT_NAME@@d -q -o -f
		87	@@URXVT_NAME@@c "$@"
		88	fi
		89
		90	This tries to create a new terminal, and if fails with exit status 2,
		91	meaning it couldn't connect to the daemon, it will start the daemon and
		92	re-run the command. Subsequent invocations of the script will re-use the
		93	existing daemon.
		94
		95	=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
		96
		97	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
		98	so you can check and see if that is set. Note that several programs, JED,
		99	slrn, Midnight Commander automatically check this variable to decide
		100	whether or not to use color.
		101
		102	=head3 How do I set the correct, full IP address for the DISPLAY variable?
		103
		104	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		105	insecure mode then it is possible to use the following shell script
		106	snippets to correctly set the display. If your version of rxvt-unicode
		107	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		108	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		109	regular xterm.
		110
		111	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		112	snippets:
		113
		114	# Bourne/Korn/POSIX family of shells:
		115	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		116	if [ ${TERM:-foo} = xterm ]; then
		117	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		118	echo -n '^[Z'
		119	read term_id
		120	stty icanon echo
		121	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		122	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		123	read DISPLAY # set it in our local shell
		124	fi
		125	fi
		126
		127	=head3 How do I compile the manual pages on my own?
		128
		129	You need to have a recent version of perl installed as F</usr/bin/perl>,
		130	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		131	the doc subdirectory and enter C<make alldoc>.
		132
69	=item Isn't rxvt supposed to be small? Don't all those features bloat?	133	=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
70		134
71	I often get asked about this, and I think, no, they didn't cause extra	135	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	136	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	137	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	138	compiled in), but it actually uses less memory (RSS) after startup. Even
…		…
78		142
79	text data bss drs rss filename	143	text data bss drs rss filename
80	98398 1664 24 15695 1824 rxvt --disable-everything	144	98398 1664 24 15695 1824 rxvt --disable-everything
81	188985 9048 66616 18222 1788 urxvt --disable-everything	145	188985 9048 66616 18222 1788 urxvt --disable-everything
82		146
83	When you C<--enable-everything> (which _is_ unfair, as this involves xft	147	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	148	and full locale/XIM support which are quite bloaty inside libX11 and my
85	libc), the two diverge, but not unreasnobaly so.	149	libc), the two diverge, but not unreasnobaly so.
86		150
87	text data bss drs rss filename	151	text data bss drs rss filename
88	163431 2152 24 20123 2060 rxvt --enable-everything	152	163431 2152 24 20123 2060 rxvt --enable-everything
…		…
106	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
107	43180k in daemons that stay around after exit, plus half a minute of	171	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	172	startup time, including the hundreds of warnings it spits out), it fares
109	extremely well *g*.	173	extremely well *g*.
110		174
111	=item Why C++, isn't that unportable/bloated/uncool?	175	=head3 Why C++, isn't that unportable/bloated/uncool?
112		176
113	Is this a question? :) It comes up very often. The simple answer is: I had	177	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	178	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	179	of the time and effort (which is a scarce resource for me). Put even
116	shorter: It simply wouldn't exist without C++.	180	shorter: It simply wouldn't exist without C++.
…		…
140	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
141		205
142	No large bloated libraries (of course, none were linked in statically),	206	No large bloated libraries (of course, none were linked in statically),
143	except maybe libX11 :)	207	except maybe libX11 :)
144		208
145	=item Does it support tabs, can I have a tabbed rxvt-unicode?
146		209
147	rxvt-unicode does not directly support tabs. It will work fine with	210	=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		211
154	=item How do I know which rxvt-unicode version I'm using?	212	=head3 I can't get transparency working, what am I doing wrong?
155		213
156	The version number is displayed with the usage (-h). Also the escape	214	First of all, transparency isn't officially supported in rxvt-unicode, so
157	sequence C<ESC [ 8 n> sets the window title to the version number. When	215	you are mostly on your own. Do not bug the author about it (but you may
158	using the @@RXVT_NAME@@c client, the version displayed is that of the	216	bug everybody else). Also, if you can't get it working consider it a rite
159	daemon.	217	of passage: ... and you failed.
160		218
161	=item I am using Debian GNU/Linux and have a problem...	219	Here are four ways to get transparency. B<Do> read the manpage and option
		220	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
162		221
163	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	222	1. Use inheritPixmap:
164	patches that considerably change the behaviour of rxvt-unicode (but
165	unfortunately this notice has been removed). Before reporting a bug to
166	the original rxvt-unicode author please download and install the genuine
167	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
168	the problem. If you cannot, chances are that the problems are specific to
169	Debian GNU/Linux, in which case it should be reported via the Debian Bug
170	Tracking System (use C<reportbug> to report the bug).
171		223
172	For other problems that also affect the Debian package, you can and	224	Esetroot wallpaper.jpg
173	probably should use the Debian BTS, too, because, after all, it's also a	225	@@URXVT_NAME@@ -ip -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		226
177	=item I am maintaining rxvt-unicode for distribution/OS XXX, any	227	That works. If you think it doesn't, you lack transparency and tinting
178	recommendation?	228	support, or you are unable to read.
179		229
180	You should build one binary with the default options. F<configure>	230	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
181	now enables most useful options, and the trend goes to making them	231	to use effects other than tinting and shading: Just shade/tint/whatever
182	runtime-switchable, too, so there is usually no drawback to enbaling them,	232	your picture with gimp or any other tool:
183	except higher disk and possibly memory usage. The perl interpreter should
184	be enabled, as important functionality (menus, selection, likely more in
185	the future) depends on it.
186		233
187	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	234	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
188	system-wide (except maybe with C<defaults>). This will result in useful	235	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
189	behaviour. If your distribution aims at low memory, add an empty
190	C<perl-ext-common> resource to the app-defaults file. This will keep the
191	perl interpreter disabled until the user enables it.
192		236
193	If you can/want build more binaries, I recommend building a minimal	237	That works. If you think it doesn't, you lack XPM and Perl support, or you
194	one with C<--disable-everything> (very useful) and a maximal one with	238	are unable to read.
195	C<--enable-everything> (less useful, it will be very big due to a lot of
196	encodings built-in that increase download times and are rarely used).
197		239
198	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	240	3. Use an ARGB visual:
199		241
200	It should be, starting with release 7.1. You are encouraged to properly	242	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
201	install urxvt with privileges necessary for your OS now.
202		243
203	When rxvt-unicode detects that it runs setuid or setgid, it will fork	244	This requires XFT support, and the support of your X-server. If that
204	into a helper process for privileged operations (pty handling on some	245	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
205	systems, utmp/wtmp/lastlog handling on others) and drop privileges	246	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
206	immediately. This is much safer than most other terminals that keep	247	bugfixes and workarounds for Xft and Xlib to make it work, but that
207	privileges while running (but is more relevant to urxvt, as it contains	248	doesn't mean that your WM has the required kludges in place.
208	things as perl interpreters, which might be "helpful" to attackers).
209		249
210	This forking is done as the very first within main(), which is very early	250	4. Use xcompmgr and let it do the job:
211	and reduces possible bugs to initialisation code run before main(), or
212	things like the dynamic loader of your system, which should result in very
213	little risk.
214		251
		252	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		253	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		254
		255	Then click on a window you want to make transparent. Replace C<0xc0000000>
		256	by other values to change the degree of opacity. If it doesn't work and
		257	your server crashes, you got to keep the pieces.
		258
		259	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		260
		261	Most fonts were not designed for terminal use, which means that character
		262	size varies a lot. A font that is otherwise fine for terminal use might
		263	contain some characters that are simply too wide. Rxvt-unicode will avoid
		264	these characters. For characters that are just "a bit" too wide a special
		265	"careful" rendering mode is used that redraws adjacent characters.
		266
		267	All of this requires that fonts do not lie about character sizes,
		268	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		269	box, and rxvt-unicode has no way of detecting this (the correct way is to
		270	ask for the character bounding box, which unfortunately is wrong in these
		271	cases).
		272
		273	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		274	or the respective font. If you encounter this problem you might try using
		275	the C<-lsp> option to give the font more height. If that doesn't work, you
		276	might be forced to use a different font.
		277
		278	All of this is not a problem when using X11 core fonts, as their bounding
		279	box data is correct.
		280
		281	=head3 How can I keep rxvt-unicode from using reverse video so much?
		282
		283	First of all, make sure you are running with the right terminal settings
		284	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		285	make sure you have specified colours for italic and bold, as otherwise
		286	rxvt-unicode might use reverse video to simulate the effect:
		287
		288	URxvt.colorBD: white
		289	URxvt.colorIT: green
		290
		291	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		292
		293	For some unexplainable reason, some rare programs assume a very weird
		294	colour palette when confronted with a terminal with more than the standard
		295	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		296	these programs not to assume non-ISO colours without very good reasons.
		297
		298	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		299	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		300	fix colours but keep you from using other rxvt-unicode features.
		301
		302	=head3 Can I switch the fonts at runtime?
		303
		304	Yes, using an escape sequence. Try something like this, which has the same
		305	effect as using the C<-fn> switch, and takes effect immediately:
		306
		307	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		308
		309	This is useful if you e.g. work primarily with japanese (and prefer a
		310	japanese font), but you have to switch to chinese temporarily, where
		311	japanese fonts would only be in your way.
		312
		313	You can think of this as a kind of manual ISO-2022 switching.
		314
		315	=head3 Why do italic characters look as if clipped?
		316
		317	Many fonts have difficulties with italic characters and hinting. For
		318	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		319	Mono> completely fails in it's italic face. A workaround might be to
		320	enable freetype autohinting, i.e. like this:
		321
		322	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		323	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		324
		325	=head3 Can I speed up Xft rendering somehow?
		326
		327	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		328	it is simply slow. If you still want Xft fonts you might try to disable
		329	antialiasing (by appending C<:antialias=false>), which saves lots of
		330	memory and also speeds up rendering considerably.
		331
		332	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		333
		334	Rxvt-unicode will use whatever you specify as a font. If it needs to
		335	fall back to it's default font search list it will prefer X11 core
		336	fonts, because they are small and fast, and then use Xft fonts. It has
		337	antialiasing disabled for most of them, because the author thinks they
		338	look best that way.
		339
		340	If you want antialiasing, you have to specify the fonts manually.
		341
		342	=head3 What's with this bold/blink stuff?
		343
		344	If no bold colour is set via C<colorBD:>, bold will invert text using the
		345	standard foreground colour.
		346
		347	For the standard background colour, blinking will actually make the
		348	text blink when compiled with C<--enable-blinking>. with standard
		349	colours. Without C<--enable-blinking>, the blink attribute will be
		350	ignored.
		351
		352	On ANSI colours, bold/blink attributes are used to set high-intensity
		353	foreground/background colors.
		354
		355	color0-7 are the low-intensity colors.
		356
		357	color8-15 are the corresponding high-intensity colors.
		358
		359	=head3 I don't like the screen colors. How do I change them?
		360
		361	You can change the screen colors at run-time using F<~/.Xdefaults>
		362	resources (or as long-options).
		363
		364	Here are values that are supposed to resemble a VGA screen,
		365	including the murky brown that passes for low-intensity yellow:
		366
		367	URxvt.color0: #000000
		368	URxvt.color1: #A80000
		369	URxvt.color2: #00A800
		370	URxvt.color3: #A8A800
		371	URxvt.color4: #0000A8
		372	URxvt.color5: #A800A8
		373	URxvt.color6: #00A8A8
		374	URxvt.color7: #A8A8A8
		375
		376	URxvt.color8: #000054
		377	URxvt.color9: #FF0054
		378	URxvt.color10: #00FF54
		379	URxvt.color11: #FFFF54
		380	URxvt.color12: #0000FF
		381	URxvt.color13: #FF00FF
		382	URxvt.color14: #00FFFF
		383	URxvt.color15: #FFFFFF
		384
		385	And here is a more complete set of non-standard colors.
		386
		387	URxvt.cursorColor: #dc74d1
		388	URxvt.pointerColor: #dc74d1
		389	URxvt.background: #0e0e0e
		390	URxvt.foreground: #4ad5e1
		391	URxvt.color0: #000000
		392	URxvt.color8: #8b8f93
		393	URxvt.color1: #dc74d1
		394	URxvt.color9: #dc74d1
		395	URxvt.color2: #0eb8c7
		396	URxvt.color10: #0eb8c7
		397	URxvt.color3: #dfe37e
		398	URxvt.color11: #dfe37e
		399	URxvt.color5: #9e88f0
		400	URxvt.color13: #9e88f0
		401	URxvt.color6: #73f7ff
		402	URxvt.color14: #73f7ff
		403	URxvt.color7: #e1dddd
		404	URxvt.color15: #e1dddd
		405
		406	They have been described (not by me) as "pretty girly".
		407
		408	=head3 Why do some characters look so much different than others?
		409
		410	See next entry.
		411
		412	=head3 How does rxvt-unicode choose fonts?
		413
		414	Most fonts do not contain the full range of Unicode, which is
		415	fine. Chances are that the font you (or the admin/package maintainer of
		416	your system/os) have specified does not cover all the characters you want
		417	to display.
		418
		419	B<rxvt-unicode> makes a best-effort try at finding a replacement
		420	font. Often the result is fine, but sometimes the chosen font looks
		421	bad/ugly/wrong. Some fonts have totally strange characters that don't
		422	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		423	intelligence to detect that a specific glyph is wrong: it has to believe
		424	the font that the characters it claims to contain indeed look correct.
		425
		426	In that case, select a font of your taste and add it to the font list,
		427	e.g.:
		428
		429	@@URXVT_NAME@@ -fn basefont,font2,font3...
		430
		431	When rxvt-unicode sees a character, it will first look at the base
		432	font. If the base font does not contain the character, it will go to the
		433	next font, and so on. Specifying your own fonts will also speed up this
		434	search and use less resources within rxvt-unicode and the X-server.
		435
		436	The only limitation is that none of the fonts may be larger than the base
		437	font, as the base font defines the terminal character cell size, which
		438	must be the same due to the way terminals work.
		439
		440	=head3 Why do some chinese characters look so different than others?
		441
		442	This is because there is a difference between script and language --
		443	rxvt-unicode does not know which language the text that is output is,
		444	as it only knows the unicode character codes. If rxvt-unicode first
		445	sees a japanese/chinese character, it might choose a japanese font for
		446	display. Subsequent japanese characters will use that font. Now, many
		447	chinese characters aren't represented in japanese fonts, so when the first
		448	non-japanese character comes up, rxvt-unicode will look for a chinese font
		449	-- unfortunately at this point, it will still use the japanese font for
		450	chinese characters that are also in the japanese font.
		451
		452	The workaround is easy: just tag a chinese font at the end of your font
		453	list (see the previous question). The key is to view the font list as
		454	a preference list: If you expect more japanese, list a japanese font
		455	first. If you expect more chinese, put a chinese font first.
		456
		457	In the future it might be possible to switch language preferences at
		458	runtime (the internal data structure has no problem with using different
		459	fonts for the same character at the same time, but no interface for this
		460	has been designed yet).
		461
		462	Until then, you might get away with switching fonts at runtime (see L<Can
		463	I switch the fonts at runtime?> later in this document).
		464
		465	=head2 Keyboard, Mouse & User Interaction
		466
		467	=head3 The new selection selects pieces that are too big, how can I select single words?
		468
		469	If you want to select e.g. alphanumeric words, you can use the following
		470	setting:
		471
		472	URxvt.selection.pattern-0: ([[:word:]]+)
		473
		474	If you click more than twice, the selection will be extended
		475	more and more.
		476
		477	To get a selection that is very similar to the old code, try this pattern:
		478
		479	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		480
		481	Please also note that the I<LeftClick Shift-LeftClik> combination also
		482	selects words like the old code.
		483
		484	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		485
		486	You can disable the perl extension completely by setting the
		487	B<perl-ext-common> resource to the empty string, which also keeps
		488	rxvt-unicode from initialising perl, saving memory.
		489
		490	If you only want to disable specific features, you first have to
		491	identify which perl extension is responsible. For this, read the section
		492	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		493	example, to disable the B<selection-popup> and B<option-popup>, specify
		494	this B<perl-ext-common> resource:
		495
		496	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		497
		498	This will keep the default extensions, but disable the two popup
		499	extensions. Some extensions can also be configured, for example,
		500	scrollback search mode is triggered by B<M-s>. You can move it to any
		501	other combination either by setting the B<searchable-scrollback> resource:
		502
		503	URxvt.searchable-scrollback: CM-s
		504
		505	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		506
		507	See next entry.
		508
		509	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		510
		511	These are caused by the C<readline> perl extension. Under normal
		512	circumstances, it will move your cursor around when you click into the
		513	line that contains it. It tries hard not to do this at the wrong moment,
		514	but when running a program that doesn't parse cursor movements or in some
		515	cases during rlogin sessions, it fails to detect this properly.
		516
		517	You can permamently switch this feature off by disabling the C<readline>
		518	extension:
		519
		520	URxvt.perl-ext-common: default,-readline
		521
		522	=head3 My numerical keypad acts weird and generates differing output?
		523
		524	Some Debian GNUL/Linux users seem to have this problem, although no
		525	specific details were reported so far. It is possible that this is caused
		526	by the wrong C<TERM> setting, although the details of wether and how
		527	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		528	keymap. See the answer to the previous question, and please report if that
		529	helped.
		530
		531	=head3 My Compose (Multi_key) key is no longer working.
		532
		533	The most common causes for this are that either your locale is not set
		534	correctly, or you specified a B<preeditStyle> that is not supported by
		535	your input method. For example, if you specified B<OverTheSpot> and
		536	your input method (e.g. the default input method handling Compose keys)
		537	does not support this (for instance because it is not visual), then
		538	rxvt-unicode will continue without an input method.
		539
		540	In this case either do not specify a B<preeditStyle> or specify more than
		541	one pre-edit style, such as B<OverTheSpot,Root,None>.
		542
		543	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		544
		545	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		546	international keyboards) or simply use ISO 14755 support to your
		547	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		548	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		549	character and so on.
		550
		551	=head3 Mouse cut/paste suddenly no longer works.
		552
		553	Make sure that mouse reporting is actually turned off since killing
		554	some editors prematurely may leave the mouse in mouse report mode. I've
		555	heard that tcsh may use mouse reporting unless it otherwise specified. A
		556	quick check is to see if cut/paste works when the Alt or Shift keys are
		557	depressed.
		558
		559	=head3 What's with the strange Backspace/Delete key behaviour?
		560
		561	Assuming that the physical Backspace key corresponds to the
		562	BackSpace keysym (not likely for Linux ... see the following
		563	question) there are two standard values that can be used for
		564	Backspace: C<^H> and C<^?>.
		565
		566	Historically, either value is correct, but rxvt-unicode adopts the debian
		567	policy of using C<^?> when unsure, because it's the one only only correct
		568	choice :).
		569
		570	Rxvt-unicode tries to inherit the current stty settings and uses the value
		571	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		572	started from a terminal (say, from a menu or by remote shell), then the
		573	system value of `erase', which corresponds to CERASE in <termios.h>, will
		574	be used (which may not be the same as your stty setting).
		575
		576	For starting a new rxvt-unicode:
		577
		578	# use Backspace = ^H
		579	$ stty erase ^H
		580	$ @@URXVT_NAME@@
		581
		582	# use Backspace = ^?
		583	$ stty erase ^?
		584	$ @@URXVT_NAME@@
		585
		586	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		587
		588	For an existing rxvt-unicode:
		589
		590	# use Backspace = ^H
		591	$ stty erase ^H
		592	$ echo -n "^[[36h"
		593
		594	# use Backspace = ^?
		595	$ stty erase ^?
		596	$ echo -n "^[[36l"
		597
		598	This helps satisfy some of the Backspace discrepancies that occur, but
		599	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		600	properly reflects that.
		601
		602	The Delete key is a another casualty of the ill-defined Backspace problem.
		603	To avoid confusion between the Backspace and Delete keys, the Delete
		604	key has been assigned an escape sequence to match the vt100 for Execute
		605	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		606
		607	Some other Backspace problems:
		608
		609	some editors use termcap/terminfo,
		610	some editors (vim I'm told) expect Backspace = ^H,
		611	GNU Emacs (and Emacs-like editors) use ^H for help.
		612
		613	Perhaps someday this will all be resolved in a consistent manner.
		614
		615	=head3 I don't like the key-bindings. How do I change them?
		616
		617	There are some compile-time selections available via configure. Unless
		618	you have run "configure" with the C<--disable-resources> option you can
		619	use the `keysym' resource to alter the keystrings associated with keysyms.
		620
		621	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		622
		623	URxvt.keysym.Home: \033[1~
		624	URxvt.keysym.End: \033[4~
		625	URxvt.keysym.C-apostrophe: \033<C-'>
		626	URxvt.keysym.C-slash: \033<C-/>
		627	URxvt.keysym.C-semicolon: \033<C-;>
		628	URxvt.keysym.C-grave: \033<C-`>
		629	URxvt.keysym.C-comma: \033<C-,>
		630	URxvt.keysym.C-period: \033<C-.>
		631	URxvt.keysym.C-0x60: \033<C-`>
		632	URxvt.keysym.C-Tab: \033<C-Tab>
		633	URxvt.keysym.C-Return: \033<C-Return>
		634	URxvt.keysym.S-Return: \033<S-Return>
		635	URxvt.keysym.S-space: \033<S-Space>
		636	URxvt.keysym.M-Up: \033<M-Up>
		637	URxvt.keysym.M-Down: \033<M-Down>
		638	URxvt.keysym.M-Left: \033<M-Left>
		639	URxvt.keysym.M-Right: \033<M-Right>
		640	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		641	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		642	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		643
		644	See some more examples in the documentation for the B<keysym> resource.
		645
		646	=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
		647
		648	KP_Insert == Insert
		649	F22 == Print
		650	F27 == Home
		651	F29 == Prior
		652	F33 == End
		653	F35 == Next
		654
		655	Rather than have rxvt-unicode try to accommodate all the various possible
		656	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		657	required for your particular machine.
		658
		659
		660
		661	=head2 Terminal Configuration
		662
		663	=head3 Why doesn't rxvt-unicode read my resources?
		664
		665	Well, why, indeed? It does, in a way very similar to other X
		666	applications. Most importantly, this means that if you or your OS loads
		667	resources into the X display (the right way to do it), rxvt-unicode will
		668	ignore any resource files in your home directory. It will only read
		669	F<$HOME/.Xdefaults> when no resources are attached to the display.
		670
		671	If you have or use an F<$HOME/.Xresources> file, chances are that
		672	resources are loaded into your X-server. In this case, you have to
		673	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		674
		675	Also consider the form resources have to use:
		676
		677	URxvt.resource: value
		678
		679	If you want to use another form (there are lots of different ways of
		680	specifying resources), make sure you understand wether and why it
		681	works. If unsure, use the form above.
		682
215	=item When I log-in to another system it tells me about missing terminfo data?	683	=head3 When I log-in to another system it tells me about missing terminfo data?
216		684
217	The terminal description used by rxvt-unicode is not as widely available	685	The terminal description used by rxvt-unicode is not as widely available
218	as that for xterm, or even rxvt (for which the same problem often arises).	686	as that for xterm, or even rxvt (for which the same problem often arises).
219		687
220	The correct solution for this problem is to install the terminfo, this can	688	The correct solution for this problem is to install the terminfo, this can
…		…
236	resource to set it:	704	resource to set it:
237		705
238	URxvt.termName: rxvt	706	URxvt.termName: rxvt
239		707
240	If you don't plan to use B<rxvt> (quite common...) you could also replace	708	If you don't plan to use B<rxvt> (quite common...) you could also replace
241	the rxvt terminfo file with the rxvt-unicode one.	709	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
242		710
243	=item C<tic> outputs some error when compiling the terminfo entry.	711	=head3 C<tic> outputs some error when compiling the terminfo entry.
244		712
245	Most likely it's the empty definition for C<enacs=>. Just replace it by	713	Most likely it's the empty definition for C<enacs=>. Just replace it by
246	C<enacs=\E[0@> and try again.	714	C<enacs=\E[0@> and try again.
247		715
248	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	716	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
249		717
		718	See next entry.
		719
250	=item I need a termcap file entry.	720	=head3 I need a termcap file entry.
251		721
252	One reason you might want this is that some distributions or operating	722	One reason you might want this is that some distributions or operating
253	systems still compile some programs using the long-obsoleted termcap	723	systems still compile some programs using the long-obsoleted termcap
254	library (Fedora Core's bash is one example) and rely on a termcap entry	724	library (Fedora Core's bash is one example) and rely on a termcap entry
255	for C<rxvt-unicode>.	725	for C<rxvt-unicode>.
…		…
281	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	751	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
282	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	752	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
283	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	753	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
284	:vs=\E[?25h:	754	:vs=\E[?25h:
285		755
286	=item Why does C<ls> no longer have coloured output?	756	=head3 Why does C<ls> no longer have coloured output?
287		757
288	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	758	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
289	decide wether a terminal has colour, but uses it's own configuration	759	decide wether a terminal has colour, but uses it's own configuration
290	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	760	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
291	with most other terminals supporting colour). Either add:	761	with most other terminals supporting colour). Either add:
…		…
296		766
297	alias ls='ls --color=auto'	767	alias ls='ls --color=auto'
298		768
299	to your C<.profile> or C<.bashrc>.	769	to your C<.profile> or C<.bashrc>.
300		770
301	=item Why doesn't vim/emacs etc. use the 88 colour mode?	771	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
302		772
		773	See next entry.
		774
303	=item Why doesn't vim/emacs etc. make use of italic?	775	=head3 Why doesn't vim/emacs etc. make use of italic?
304		776
		777	See next entry.
		778
305	=item Why are the secondary screen-related options not working properly?	779	=head3 Why are the secondary screen-related options not working properly?
306		780
307	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	781	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
308	distributions (most notably Debian GNU/Linux) break rxvt-unicode	782	distributions (most notably Debian GNU/Linux) break rxvt-unicode
309	by setting C<TERM> to C<rxvt>, which doesn't have these extra	783	by setting C<TERM> to C<rxvt>, which doesn't have these extra
310	features. Unfortunately, some of these (most notably, again, Debian	784	features. Unfortunately, some of these (most notably, again, Debian
311	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	785	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
312	file, so you will need to install it on your own (See the question B<When	786	file, so you will need to install it on your own (See the question B<When
313	I log-in to another system it tells me about missing terminfo data?> on	787	I log-in to another system it tells me about missing terminfo data?> on
314	how to do this).	788	how to do this).
315		789
316	=item My numerical keypad acts weird and generates differing output?
317		790
318	Some Debian GNUL/Linux users seem to have this problem, although no	791	=head2 Encoding / Locale / Input Method Issues
319	specific details were reported so far. It is possible that this is caused
320	by the wrong C<TERM> setting, although the details of wether and how
321	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
322	keymap. See the answer to the previous question, and please report if that
323	helped.
324		792
325	=item Rxvt-unicode does not seem to understand the selected encoding?	793	=head3 Rxvt-unicode does not seem to understand the selected encoding?
326		794
		795	See next entry.
		796
327	=item Unicode does not seem to work?	797	=head3 Unicode does not seem to work?
328		798
329	If you encounter strange problems like typing an accented character but	799	If you encounter strange problems like typing an accented character but
330	getting two unrelated other characters or similar, or if program output is	800	getting two unrelated other characters or similar, or if program output is
331	subtly garbled, then you should check your locale settings.	801	subtly garbled, then you should check your locale settings.
332		802
…		…
352		822
353	If nothing works and you are sure that everything is set correctly then	823	If nothing works and you are sure that everything is set correctly then
354	you will need to remember a little known fact: Some programs just don't	824	you will need to remember a little known fact: Some programs just don't
355	support locales :(	825	support locales :(
356		826
357	=item Why do some characters look so much different than others?	827	=head3 How does rxvt-unicode determine the encoding to use?
358		828
359	=item How does rxvt-unicode choose fonts?	829	See next entry.
360		830
361	Most fonts do not contain the full range of Unicode, which is	831	=head3 Is there an option to switch encodings?
362	fine. Chances are that the font you (or the admin/package maintainer of
363	your system/os) have specified does not cover all the characters you want
364	to display.
365		832
366	B<rxvt-unicode> makes a best-effort try at finding a replacement	833	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
367	font. Often the result is fine, but sometimes the chosen font looks	834	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
368	bad/ugly/wrong. Some fonts have totally strange characters that don't	835	UTF-8 or any other encodings with respect to terminal I/O.
369	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
370	intelligence to detect that a specific glyph is wrong: it has to believe
371	the font that the characters it claims to contain indeed look correct.
372		836
373	In that case, select a font of your taste and add it to the font list,	837	The reasons is that there exists a perfectly fine mechanism for selecting
374	e.g.:	838	the encoding, doing I/O and (most important) communicating this to all
375		839	applications so everybody agrees on character properties such as width
376	@@RXVT_NAME@@ -fn basefont,font2,font3...	840	and code number. This mechanism is the I<locale>. Applications not using
377		841	that info will have problems (for example, C<xterm> gets the width of
378	When rxvt-unicode sees a character, it will first look at the base	842	characters wrong as it uses it's own, locale-independent table under all
379	font. If the base font does not contain the character, it will go to the
380	next font, and so on. Specifying your own fonts will also speed up this
381	search and use less resources within rxvt-unicode and the X-server.
382
383	The only limitation is that none of the fonts may be larger than the base
384	font, as the base font defines the terminal character cell size, which
385	must be the same due to the way terminals work.
386
387	=item Why do some chinese characters look so different than others?
388
389	This is because there is a difference between script and language --
390	rxvt-unicode does not know which language the text that is output is,
391	as it only knows the unicode character codes. If rxvt-unicode first
392	sees a japanese/chinese character, it might choose a japanese font for
393	display. Subsequent japanese characters will use that font. Now, many
394	chinese characters aren't represented in japanese fonts, so when the first
395	non-japanese character comes up, rxvt-unicode will look for a chinese font
396	-- unfortunately at this point, it will still use the japanese font for
397	chinese characters that are also in the japanese font.
398
399	The workaround is easy: just tag a chinese font at the end of your font
400	list (see the previous question). The key is to view the font list as
401	a preference list: If you expect more japanese, list a japanese font
402	first. If you expect more chinese, put a chinese font first.
403
404	In the future it might be possible to switch language preferences at
405	runtime (the internal data structure has no problem with using different
406	fonts for the same character at the same time, but no interface for this
407	has been designed yet).
408
409	Until then, you might get away with switching fonts at runtime (see L<Can
410	I switch the fonts at runtime?> later in this document).
411
412	=item Why does rxvt-unicode sometimes leave pixel droppings?
413
414	Most fonts were not designed for terminal use, which means that character
415	size varies a lot. A font that is otherwise fine for terminal use might
416	contain some characters that are simply too wide. Rxvt-unicode will avoid
417	these characters. For characters that are just "a bit" too wide a special
418	"careful" rendering mode is used that redraws adjacent characters.
419
420	All of this requires that fonts do not lie about character sizes,
421	however: Xft fonts often draw glyphs larger than their acclaimed bounding
422	box, and rxvt-unicode has no way of detecting this (the correct way is to
423	ask for the character bounding box, which unfortunately is wrong in these
424	cases).	843	locales).
425		844
426	It's not clear (to me at least), wether this is a bug in Xft, freetype,	845	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
427	or the respective font. If you encounter this problem you might try using	846	programs doing the same (that is, most) will automatically agree in the
428	the C<-lsp> option to give the font more height. If that doesn't work, you	847	interpretation of characters.
429	might be forced to use a different font.
430		848
431	All of this is not a problem when using X11 core fonts, as their bounding	849	Unfortunately, there is no system-independent way to select locales, nor
432	box data is correct.	850	is there a standard on how locale specifiers will look like.
433		851
		852	On most systems, the content of the C<LC_CTYPE> environment variable
		853	contains an arbitrary string which corresponds to an already-installed
		854	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		855	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		856	(i.e. C<de> or C<german>) are also common.
		857
		858	Rxvt-unicode ignores all other locale categories, and except for
		859	the encoding, ignores country or language-specific settings,
		860	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		861	rxvt-unicode.
		862
		863	If you want to use a specific encoding you have to make sure you start
		864	rxvt-unicode with the correct C<LC_CTYPE> category.
		865
		866	=head3 Can I switch locales at runtime?
		867
		868	Yes, using an escape sequence. Try something like this, which sets
		869	rxvt-unicode's idea of C<LC_CTYPE>.
		870
		871	printf '\e]701;%s\007' ja_JP.SJIS
		872
		873	See also the previous answer.
		874
		875	Sometimes this capability is rather handy when you want to work in
		876	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		877	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		878	first switches to a locale supported by xjdic and back later:
		879
		880	printf '\e]701;%s\007' ja_JP.SJIS
		881	xjdic -js
		882	printf '\e]701;%s\007' de_DE.UTF-8
		883
		884	You can also use xterm's C<luit> program, which usually works fine, except
		885	for some locales where character width differs between program- and
		886	rxvt-unicode-locales.
		887
		888	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		889
		890	You can specify separate locales for the input method and the rest of the
		891	terminal, using the resource C<imlocale>:
		892
		893	URxvt.imlocale: ja_JP.EUC-JP
		894
		895	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		896	use your input method. Please note, however, that you will not be able to
		897	input characters outside C<EUC-JP> in a normal way then, as your input
		898	method limits you.
		899
		900	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		901
		902	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		903	design. Applications can avoid some crashes at the expense of memory
		904	leaks, and Input Methods can avoid some crashes by careful ordering at
		905	exit time. B<kinput2> (and derived input methods) generally succeeds,
		906	while B<SCIM> (or similar input methods) fails. In the end, however,
		907	crashes cannot be completely avoided even if both sides cooperate.
		908
		909	So the only workaround is not to kill your Input Method Servers.
		910
		911
		912	=head2 Operating Systems / Package Maintaining
		913
		914	=head3 I am using Debian GNU/Linux and have a problem...
		915
		916	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		917	patches that considerably change the behaviour of rxvt-unicode (but
		918	unfortunately this notice has been removed). Before reporting a bug to
		919	the original rxvt-unicode author please download and install the genuine
		920	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		921	the problem. If you cannot, chances are that the problems are specific to
		922	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		923	Tracking System (use C<reportbug> to report the bug).
		924
		925	For other problems that also affect the Debian package, you can and
		926	probably should use the Debian BTS, too, because, after all, it's also a
		927	bug in the Debian version and it serves as a reminder for other users that
		928	might encounter the same issue.
		929
		930	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		931
		932	You should build one binary with the default options. F<configure>
		933	now enables most useful options, and the trend goes to making them
		934	runtime-switchable, too, so there is usually no drawback to enbaling them,
		935	except higher disk and possibly memory usage. The perl interpreter should
		936	be enabled, as important functionality (menus, selection, likely more in
		937	the future) depends on it.
		938
		939	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		940	system-wide (except maybe with C<defaults>). This will result in useful
		941	behaviour. If your distribution aims at low memory, add an empty
		942	C<perl-ext-common> resource to the app-defaults file. This will keep the
		943	perl interpreter disabled until the user enables it.
		944
		945	If you can/want build more binaries, I recommend building a minimal
		946	one with C<--disable-everything> (very useful) and a maximal one with
		947	C<--enable-everything> (less useful, it will be very big due to a lot of
		948	encodings built-in that increase download times and are rarely used).
		949
		950	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		951
		952	It should be, starting with release 7.1. You are encouraged to properly
		953	install urxvt with privileges necessary for your OS now.
		954
		955	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		956	into a helper process for privileged operations (pty handling on some
		957	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		958	immediately. This is much safer than most other terminals that keep
		959	privileges while running (but is more relevant to urxvt, as it contains
		960	things as perl interpreters, which might be "helpful" to attackers).
		961
		962	This forking is done as the very first within main(), which is very early
		963	and reduces possible bugs to initialisation code run before main(), or
		964	things like the dynamic loader of your system, which should result in very
		965	little risk.
		966
434	=item On Solaris 9, many line-drawing characters are too wide.	967	=head3 On Solaris 9, many line-drawing characters are too wide.
435		968
436	Seems to be a known bug, read	969	Seems to be a known bug, read
437	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	970	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
438	following ugly workaround to get non-double-wide-characters working:	971	following ugly workaround to get non-double-wide-characters working:
439		972
440	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	973	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
441		974
442	=item My Compose (Multi_key) key is no longer working.
443
444	The most common causes for this are that either your locale is not set
445	correctly, or you specified a B<preeditStyle> that is not supported by
446	your input method. For example, if you specified B<OverTheSpot> and
447	your input method (e.g. the default input method handling Compose keys)
448	does not support this (for instance because it is not visual), then
449	rxvt-unicode will continue without an input method.
450
451	In this case either do not specify a B<preeditStyle> or specify more than
452	one pre-edit style, such as B<OverTheSpot,Root,None>.
453
454	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
455
456	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
457	international keyboards) or simply use ISO 14755 support to your
458	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
459	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
460	character and so on.
461
462	=item How can I keep rxvt-unicode from using reverse video so much?
463
464	First of all, make sure you are running with the right terminal settings
465	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
466	make sure you have specified colours for italic and bold, as otherwise
467	rxvt-unicode might use reverse video to simulate the effect:
468
469	URxvt.colorBD: white
470	URxvt.colorIT: green
471
472	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
473
474	For some unexplainable reason, some rare programs assume a very weird
475	colour palette when confronted with a terminal with more than the standard
476	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
477	these programs not to assume non-ISO colours without very good reasons.
478
479	In the meantime, you can either edit your C<rxvt-unicode> terminfo
480	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
481	fix colours but keep you from using other rxvt-unicode features.
482
483	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	975	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
484		976
485	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	977	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
486	in your compile environment, or an implementation that implements it,	978	in your compile environment, or an implementation that implements it,
487	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	979	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
488	B<wchar_t> is represented as unicode.	980	B<wchar_t> is represented as unicode.
…		…
510		1002
511	The rxvt-unicode author insists that the right way to fix this is in the	1003	The rxvt-unicode author insists that the right way to fix this is in the
512	system libraries once and for all, instead of forcing every app to carry	1004	system libraries once and for all, instead of forcing every app to carry
513	complete replacements for them :)	1005	complete replacements for them :)
514		1006
515	=item I use Solaris 9 and it doesn't compile/work/etc.	1007	=head3 I use Solaris 9 and it doesn't compile/work/etc.
516		1008
517	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1009	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
518	problems with C<wcwidth> and a compile problem.	1010	problems with C<wcwidth> and a compile problem.
519		1011
520	=item How can I use rxvt-unicode under cygwin?	1012	=head3 How can I use rxvt-unicode under cygwin?
521		1013
522	rxvt-unicode should compile and run out of the box on cygwin, using	1014	rxvt-unicode should compile and run out of the box on cygwin, using
523	the X11 libraries that come with cygwin. libW11 emulation is no	1015	the X11 libraries that come with cygwin. libW11 emulation is no
524	longer supported (and makes no sense, either, as it only supported a	1016	longer supported (and makes no sense, either, as it only supported a
525	single font). I recommend starting the X-server in C<-multiwindow> or	1017	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
528		1020
529	At the time of this writing, cygwin didn't seem to support any multi-byte	1021	At the time of this writing, cygwin didn't seem to support any multi-byte
530	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1022	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
531	to 8-bit encodings.	1023	to 8-bit encodings.
532		1024
533	=item How does rxvt-unicode determine the encoding to use?
534
535	=item Is there an option to switch encodings?
536
537	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
538	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
539	UTF-8 or any other encodings with respect to terminal I/O.
540
541	The reasons is that there exists a perfectly fine mechanism for selecting
542	the encoding, doing I/O and (most important) communicating this to all
543	applications so everybody agrees on character properties such as width
544	and code number. This mechanism is the I<locale>. Applications not using
545	that info will have problems (for example, C<xterm> gets the width of
546	characters wrong as it uses it's own, locale-independent table under all
547	locales).
548
549	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
550	programs doing the same (that is, most) will automatically agree in the
551	interpretation of characters.
552
553	Unfortunately, there is no system-independent way to select locales, nor
554	is there a standard on how locale specifiers will look like.
555
556	On most systems, the content of the C<LC_CTYPE> environment variable
557	contains an arbitrary string which corresponds to an already-installed
558	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
559	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
560	(i.e. C<de> or C<german>) are also common.
561
562	Rxvt-unicode ignores all other locale categories, and except for
563	the encoding, ignores country or language-specific settings,
564	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
565	rxvt-unicode.
566
567	If you want to use a specific encoding you have to make sure you start
568	rxvt-unicode with the correct C<LC_CTYPE> category.
569
570	=item Can I switch locales at runtime?
571
572	Yes, using an escape sequence. Try something like this, which sets
573	rxvt-unicode's idea of C<LC_CTYPE>.
574
575	printf '\e]701;%s\007' ja_JP.SJIS
576
577	See also the previous answer.
578
579	Sometimes this capability is rather handy when you want to work in
580	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
581	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
582	first switches to a locale supported by xjdic and back later:
583
584	printf '\e]701;%s\007' ja_JP.SJIS
585	xjdic -js
586	printf '\e]701;%s\007' de_DE.UTF-8
587
588	You can also use xterm's C<luit> program, which usually works fine, except
589	for some locales where character width differs between program- and
590	rxvt-unicode-locales.
591
592	=item Can I switch the fonts at runtime?
593
594	Yes, using an escape sequence. Try something like this, which has the same
595	effect as using the C<-fn> switch, and takes effect immediately:
596
597	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
598
599	This is useful if you e.g. work primarily with japanese (and prefer a
600	japanese font), but you have to switch to chinese temporarily, where
601	japanese fonts would only be in your way.
602
603	You can think of this as a kind of manual ISO-2022 switching.
604
605	=item Why do italic characters look as if clipped?
606
607	Many fonts have difficulties with italic characters and hinting. For
608	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
609	Mono> completely fails in it's italic face. A workaround might be to
610	enable freetype autohinting, i.e. like this:
611
612	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
613	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
614
615	=item My input method wants <some encoding> but I want UTF-8, what can I do?
616
617	You can specify separate locales for the input method and the rest of the
618	terminal, using the resource C<imlocale>:
619
620	URxvt.imlocale: ja_JP.EUC-JP
621
622	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
623	use your input method. Please note, however, that you will not be able to
624	input characters outside C<EUC-JP> in a normal way then, as your input
625	method limits you.
626
627	=item Rxvt-unicode crashes when the X Input Method changes or exits.
628
629	Unfortunately, this is unavoidable, as the XIM protocol is racy by
630	design. Applications can avoid some crashes at the expense of memory
631	leaks, and Input Methods can avoid some crashes by careful ordering at
632	exit time. B<kinput2> (and derived input methods) generally succeeds,
633	while B<SCIM> (or similar input methods) fails. In the end, however,
634	crashes cannot be completely avoided even if both sides cooperate.
635
636	So the only workaround is not to kill your Input Method Servers.
637
638	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
639
640	Rxvt-unicode tries to obey the rule of not charging you for something you
641	don't use. One thing you should try is to configure out all settings that
642	you don't need, for example, Xft support is a resource hog by design,
643	when used. Compiling it out ensures that no Xft font will be loaded
644	accidentally when rxvt-unicode tries to find a font for your characters.
645
646	Also, many people (me included) like large windows and even larger
647	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
648	6 bytes per screen cell. For a 160x?? window this amounts to almost a
649	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
650	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
651	rxvt-unicode then uses 8 bytes per screen cell.
652
653	=item Can I speed up Xft rendering somehow?
654
655	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
656	it is simply slow. If you still want Xft fonts you might try to disable
657	antialiasing (by appending C<:antialias=false>), which saves lots of
658	memory and also speeds up rendering considerably.
659
660	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
661
662	Rxvt-unicode will use whatever you specify as a font. If it needs to
663	fall back to it's default font search list it will prefer X11 core
664	fonts, because they are small and fast, and then use Xft fonts. It has
665	antialiasing disabled for most of them, because the author thinks they
666	look best that way.
667
668	If you want antialiasing, you have to specify the fonts manually.
669
670	=item Mouse cut/paste suddenly no longer works.
671
672	Make sure that mouse reporting is actually turned off since killing
673	some editors prematurely may leave the mouse in mouse report mode. I've
674	heard that tcsh may use mouse reporting unless it otherwise specified. A
675	quick check is to see if cut/paste works when the Alt or Shift keys are
676	depressed.
677
678	=item What's with this bold/blink stuff?
679
680	If no bold colour is set via C<colorBD:>, bold will invert text using the
681	standard foreground colour.
682
683	For the standard background colour, blinking will actually make the
684	text blink when compiled with C<--enable-blinking>. with standard
685	colours. Without C<--enable-blinking>, the blink attribute will be
686	ignored.
687
688	On ANSI colours, bold/blink attributes are used to set high-intensity
689	foreground/background colors.
690
691	color0-7 are the low-intensity colors.
692
693	color8-15 are the corresponding high-intensity colors.
694
695	=item I don't like the screen colors. How do I change them?
696
697	You can change the screen colors at run-time using F<~/.Xdefaults>
698	resources (or as long-options).
699
700	Here are values that are supposed to resemble a VGA screen,
701	including the murky brown that passes for low-intensity yellow:
702
703	URxvt.color0: #000000
704	URxvt.color1: #A80000
705	URxvt.color2: #00A800
706	URxvt.color3: #A8A800
707	URxvt.color4: #0000A8
708	URxvt.color5: #A800A8
709	URxvt.color6: #00A8A8
710	URxvt.color7: #A8A8A8
711
712	URxvt.color8: #000054
713	URxvt.color9: #FF0054
714	URxvt.color10: #00FF54
715	URxvt.color11: #FFFF54
716	URxvt.color12: #0000FF
717	URxvt.color13: #FF00FF
718	URxvt.color14: #00FFFF
719	URxvt.color15: #FFFFFF
720
721	And here is a more complete set of non-standard colors described (not by
722	me) as "pretty girly".
723
724	URxvt.cursorColor: #dc74d1
725	URxvt.pointerColor: #dc74d1
726	URxvt.background: #0e0e0e
727	URxvt.foreground: #4ad5e1
728	URxvt.color0: #000000
729	URxvt.color8: #8b8f93
730	URxvt.color1: #dc74d1
731	URxvt.color9: #dc74d1
732	URxvt.color2: #0eb8c7
733	URxvt.color10: #0eb8c7
734	URxvt.color3: #dfe37e
735	URxvt.color11: #dfe37e
736	URxvt.color5: #9e88f0
737	URxvt.color13: #9e88f0
738	URxvt.color6: #73f7ff
739	URxvt.color14: #73f7ff
740	URxvt.color7: #e1dddd
741	URxvt.color15: #e1dddd
742
743	=item How can I start @@RXVT_NAME@@d in a race-free way?
744
745	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
746	display, create the listening socket and then fork.
747
748	=item What's with the strange Backspace/Delete key behaviour?
749
750	Assuming that the physical Backspace key corresponds to the
751	BackSpace keysym (not likely for Linux ... see the following
752	question) there are two standard values that can be used for
753	Backspace: C<^H> and C<^?>.
754
755	Historically, either value is correct, but rxvt-unicode adopts the debian
756	policy of using C<^?> when unsure, because it's the one only only correct
757	choice :).
758
759	Rxvt-unicode tries to inherit the current stty settings and uses the value
760	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
761	started from a terminal (say, from a menu or by remote shell), then the
762	system value of `erase', which corresponds to CERASE in <termios.h>, will
763	be used (which may not be the same as your stty setting).
764
765	For starting a new rxvt-unicode:
766
767	# use Backspace = ^H
768	$ stty erase ^H
769	$ @@RXVT_NAME@@
770
771	# use Backspace = ^?
772	$ stty erase ^?
773	$ @@RXVT_NAME@@
774
775	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
776
777	For an existing rxvt-unicode:
778
779	# use Backspace = ^H
780	$ stty erase ^H
781	$ echo -n "^[[36h"
782
783	# use Backspace = ^?
784	$ stty erase ^?
785	$ echo -n "^[[36l"
786
787	This helps satisfy some of the Backspace discrepancies that occur, but
788	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
789	properly reflects that.
790
791	The Delete key is a another casualty of the ill-defined Backspace problem.
792	To avoid confusion between the Backspace and Delete keys, the Delete
793	key has been assigned an escape sequence to match the vt100 for Execute
794	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
795
796	Some other Backspace problems:
797
798	some editors use termcap/terminfo,
799	some editors (vim I'm told) expect Backspace = ^H,
800	GNU Emacs (and Emacs-like editors) use ^H for help.
801
802	Perhaps someday this will all be resolved in a consistent manner.
803
804	=item I don't like the key-bindings. How do I change them?
805
806	There are some compile-time selections available via configure. Unless
807	you have run "configure" with the C<--disable-resources> option you can
808	use the `keysym' resource to alter the keystrings associated with keysyms.
809
810	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
811
812	URxvt.keysym.Home: \033[1~
813	URxvt.keysym.End: \033[4~
814	URxvt.keysym.C-apostrophe: \033<C-'>
815	URxvt.keysym.C-slash: \033<C-/>
816	URxvt.keysym.C-semicolon: \033<C-;>
817	URxvt.keysym.C-grave: \033<C-`>
818	URxvt.keysym.C-comma: \033<C-,>
819	URxvt.keysym.C-period: \033<C-.>
820	URxvt.keysym.C-0x60: \033<C-`>
821	URxvt.keysym.C-Tab: \033<C-Tab>
822	URxvt.keysym.C-Return: \033<C-Return>
823	URxvt.keysym.S-Return: \033<S-Return>
824	URxvt.keysym.S-space: \033<S-Space>
825	URxvt.keysym.M-Up: \033<M-Up>
826	URxvt.keysym.M-Down: \033<M-Down>
827	URxvt.keysym.M-Left: \033<M-Left>
828	URxvt.keysym.M-Right: \033<M-Right>
829	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
830	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
831	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
832
833	See some more examples in the documentation for the B<keysym> resource.
834
835	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
836	How do I make use of them? For example, the Sun Keyboard type 4
837	has the following mappings that rxvt-unicode doesn't recognize.
838
839	KP_Insert == Insert
840	F22 == Print
841	F27 == Home
842	F29 == Prior
843	F33 == End
844	F35 == Next
845
846	Rather than have rxvt-unicode try to accommodate all the various possible
847	keyboard mappings, it is better to use `xmodmap' to remap the keys as
848	required for your particular machine.
849
850	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
851	I need this to decide about setting colors etc.
852
853	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
854	check and see if that is set. Note that several programs, JED, slrn,
855	Midnight Commander automatically check this variable to decide whether or
856	not to use color.
857
858	=item How do I set the correct, full IP address for the DISPLAY variable?
859
860	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
861	insecure mode then it is possible to use the following shell script
862	snippets to correctly set the display. If your version of rxvt-unicode
863	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
864	the COLORTERM variable can be used to distinguish rxvt-unicode from a
865	regular xterm.
866
867	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
868	snippets:
869
870	# Bourne/Korn/POSIX family of shells:
871	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
872	if [ ${TERM:-foo} = xterm ]; then
873	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
874	echo -n '^[Z'
875	read term_id
876	stty icanon echo
877	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
878	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
879	read DISPLAY # set it in our local shell
880	fi
881	fi
882
883	=item How do I compile the manual pages for myself?
884
885	You need to have a recent version of perl installed as F</usr/bin/perl>,
886	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
887	the doc subdirectory and enter C<make alldoc>.
888
889	=item My question isn't answered here, can I ask a human?
890
891	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
892	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
893	interested in learning about new and exciting problems (but not FAQs :).
894
895	=back
896
897	=head1 RXVT TECHNICAL REFERENCE	1025	=head1 RXVT-UNICODE TECHNICAL REFERENCE
898
899	=head1 DESCRIPTION
900		1026
901	The rest of this document describes various technical aspects of	1027	The rest of this document describes various technical aspects of
902	B<rxvt-unicode>. First the description of supported command sequences,	1028	B<rxvt-unicode>. First the description of supported command sequences,
903	followed by pixmap support and last by a description of all features	1029	followed by pixmap support and last by a description of all features
904	selectable at C<configure> time.	1030	selectable at C<configure> time.
905		1031
906	=head1 Definitions	1032	=head2 Definitions
907		1033
908	=over 4	1034	=over 4
909		1035
910	=item B<< C<c> >>	1036	=item B<< C<c> >>
911		1037
…		…
929		1055
930	A text parameter composed of printable characters.	1056	A text parameter composed of printable characters.
931		1057
932	=back	1058	=back
933		1059
934	=head1 Values	1060	=head2 Values
935		1061
936	=over 4	1062	=over 4
937		1063
938	=item B<< C<ENQ> >>	1064	=item B<< C<ENQ> >>
939		1065
…		…
982		1108
983	Space Character	1109	Space Character
984		1110
985	=back	1111	=back
986		1112
987	=head1 Escape Sequences	1113	=head2 Escape Sequences
988		1114
989	=over 4	1115	=over 4
990		1116
991	=item B<< C<ESC # 8> >>	1117	=item B<< C<ESC # 8> >>
992		1118
…		…
1090		1216
1091	=back	1217	=back
1092		1218
1093	X<CSI>	1219	X<CSI>
1094		1220
1095	=head1 CSI (Command Sequence Introducer) Sequences	1221	=head2 CSI (Command Sequence Introducer) Sequences
1096		1222
1097	=over 4	1223	=over 4
1098		1224
1099	=item B<< C<ESC [ Ps @> >>	1225	=item B<< C<ESC [ Ps @> >>
1100		1226
…		…
1370		1496
1371	=back	1497	=back
1372		1498
1373	X<PrivateModes>	1499	X<PrivateModes>
1374		1500
1375	=head1 DEC Private Modes	1501	=head2 DEC Private Modes
1376		1502
1377	=over 4	1503	=over 4
1378		1504
1379	=item B<< C<ESC [ ? Pm h> >>	1505	=item B<< C<ESC [ ? Pm h> >>
1380		1506
…		…
1644		1770
1645	=back	1771	=back
1646		1772
1647	X<XTerm>	1773	X<XTerm>
1648		1774
1649	=head1 XTerm Operating System Commands	1775	=head2 XTerm Operating System Commands
1650		1776
1651	=over 4	1777	=over 4
1652		1778
1653	=item B<< C<ESC ] Ps;Pt ST> >>	1779	=item B<< C<ESC ] Ps;Pt ST> >>
1654		1780
…		…
1675	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1801	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1676	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	1802	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1677	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> >>	1803	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> >>
1678	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1804	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1679	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).	1805	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).
		1806	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>.
1680	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1807	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1681	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	1808	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1682	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>	1809	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
1683	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>	1810	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1684	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1811	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
…		…
1691		1818
1692	=end table	1819	=end table
1693		1820
1694	=back	1821	=back
1695		1822
1696	X<XPM>
1697
1698	=head1 XPM	1823	=head1 XPM
1699		1824
1700	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1825	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1701	of B<< C<Pt> >> can be the name of the background pixmap followed by a	1826	of B<< C<Pt> >> can be the name of the background pixmap followed by a
1702	sequence of scaling/positioning commands separated by semi-colons. The	1827	sequence of scaling/positioning commands separated by semi-colons. The
…		…
1799	=begin table	1924	=begin table
1800		1925
1801	4 Shift	1926	4 Shift
1802	8 Meta	1927	8 Meta
1803	16 Control	1928	16 Control
1804	32 Double Click I<(Rxvt extension)>	1929	32 Double Click I<(rxvt extension)>
1805		1930
1806	=end table	1931	=end table
1807		1932
1808	Col = B<< C<< <x> - SPACE >> >>	1933	Col = B<< C<< <x> - SPACE >> >>
1809		1934
…		…
1947	alternative input methods (e.g. kinput2) and will also correctly	2072	alternative input methods (e.g. kinput2) and will also correctly
1948	set up the input for people using dead keys or compose keys.	2073	set up the input for people using dead keys or compose keys.
1949		2074
1950	=item --enable-unicode3 (default: off)	2075	=item --enable-unicode3 (default: off)
1951		2076
		2077	Recommended to stay off unless you really need non-BMP characters.
		2078
1952	Enable direct support for displaying unicode codepoints above	2079	Enable direct support for displaying unicode codepoints above
1953	65535 (the basic multilingual page). This increases storage	2080	65535 (the basic multilingual page). This increases storage
1954	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2081	requirements per character from 2 to 4 bytes. X11 fonts do not yet
1955	support these extra characters, but Xft does.	2082	support these extra characters, but Xft does.
1956		2083
…		…
1966	composite characters. This is required for proper viewing of text	2093	composite characters. This is required for proper viewing of text
1967	where accents are encoded as seperate unicode characters. This is	2094	where accents are encoded as seperate unicode characters. This is
1968	done by using precomposited characters when available or creating	2095	done by using precomposited characters when available or creating
1969	new pseudo-characters when no precomposed form exists.	2096	new pseudo-characters when no precomposed form exists.
1970		2097
1971	Without --enable-unicode3, the number of additional precomposed characters	2098	Without --enable-unicode3, the number of additional precomposed
1972	is rather limited (2048, if this is full, rxvt-unicode will use the	2099	characters is somewhat limited (the 6400 private use characters will be
1973	private use area, extending the number of combinations to 8448). With
1974	--enable-unicode3, no practical limit exists.	2100	(ab-)used). With --enable-unicode3, no practical limit exists.
1975		2101
1976	This option will also enable storage (but not display) of characters	2102	This option will also enable storage (but not display) of characters
1977	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2103	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1978		2104
1979	The combining table also contains entries for arabic presentation forms,	2105	The combining table also contains entries for arabic presentation forms,
1980	but these are not currently used. Bug me if you want these to be used (and	2106	but these are not currently used. Bug me if you want these to be used (and
1981	tell me how these are to be used...).	2107	tell me how these are to be used...).
1982		2108
1983	=item --enable-fallback(=CLASS) (default: Rxvt)	2109	=item --enable-fallback(=CLASS) (default: Rxvt)
1984		2110
1985	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.	2111	When reading resource settings, also read settings for class CLASS. To
		2112	disable resource fallback use --disable-fallback.
1986		2113
1987	=item --with-res-name=NAME (default: urxvt)	2114	=item --with-res-name=NAME (default: urxvt)
1988		2115
1989	Use the given name as default application name when	2116	Use the given name as default application name when
1990	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2117	reading resources. Specify --with-res-name=rxvt to replace rxvt.
…		…
2080		2207
2081	MWM-hints	2208	MWM-hints
2082	EWMH-hints (pid, utf8 names) and protocols (ping)	2209	EWMH-hints (pid, utf8 names) and protocols (ping)
2083	seperate underline colour (-underlineColor)	2210	seperate underline colour (-underlineColor)
2084	settable border widths and borderless switch (-w, -b, -bl)	2211	settable border widths and borderless switch (-w, -b, -bl)
		2212	visual depth selection (-depth)
2085	settable extra linespacing /-lsp)	2213	settable extra linespacing /-lsp)
2086	iso-14755-2 and -3, and visual feedback	2214	iso-14755-2 and -3, and visual feedback
2087	backindex and forwardindex escape sequence
2088	window op and some xterm/OSC escape sequences
2089	tripleclickwords (-tcw)	2215	tripleclickwords (-tcw)
2090	settable insecure mode (-insecure)	2216	settable insecure mode (-insecure)
2091	keysym remapping support	2217	keysym remapping support
2092	cursor blinking and underline cursor (-cb, -uc)	2218	cursor blinking and underline cursor (-cb, -uc)
2093	XEmbed support (-embed)	2219	XEmbed support (-embed)
2094	user-pty (-pty-fd)	2220	user-pty (-pty-fd)
2095	hold on exit (-hold)	2221	hold on exit (-hold)
2096	skip builtin block graphics (-sbg)	2222	skip builtin block graphics (-sbg)
		2223
		2224	It also enabled some non-essential features otherwise disabled, such as:
		2225
		2226	some round-trip time optimisations
		2227	nearest color allocation on pseudocolor screens
		2228	UTF8_STRING supporr for selection
2097	sgr modes 90..97 and 100..107	2229	sgr modes 90..97 and 100..107
		2230	backindex and forwardindex escape sequences
		2231	view change/zero scorllback esacpe sequences
		2232	locale switching escape sequence
		2233	window op and some xterm/OSC escape sequences
		2234	rectangular selections
		2235	trailing space removal for selections
		2236	verbose X error handling
2098		2237
2099	=item --enable-iso14755 (default: on)	2238	=item --enable-iso14755 (default: on)
2100		2239
2101	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2240	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2102	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2241	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2145		2284
2146	=item --enable-pointer-blank (default: on)	2285	=item --enable-pointer-blank (default: on)
2147		2286
2148	Add support to have the pointer disappear when typing or inactive.	2287	Add support to have the pointer disappear when typing or inactive.
2149		2288
2150	=item --enable-perl (default: off)	2289	=item --enable-perl (default: on)
2151		2290
2152	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>	2291	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2153	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files	2292	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
2154	in F<src/perl-ext/> for the extensions that are installed by default. The	2293	in F<src/perl-ext/> for the extensions that are installed by default. The
2155	perl interpreter that is used can be specified via the C<PERL> environment	2294	perl interpreter that is used can be specified via the C<PERL> environment

Diff Legend

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