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.88 by root, Wed Jan 18 17:49:46 2006 UTC vs.
Revision 1.123 by root, Sat Dec 16 03:48:49 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/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 whether 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 unreasonably 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
89	1035683 49680 66648 29096 3680 urxvt --enable-everything	153	1035683 49680 66648 29096 3680 urxvt --enable-everything
90		154
…		…
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. 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		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 recommendation?	227	That works. If you think it doesn't, you lack transparency and tinting
		228	support, or you are unable to read.
178		229
179	You should build one binary with the default options. F<configure>	230	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	231	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,	232	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		233
186	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	234	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
187	system-wide (except maybe with C<defaults>). This will result in useful	235	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
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		236
192	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
193	one with C<--disable-everything> (very useful) and a maximal one with	238	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		239
197	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	240	3. Use an ARGB visual:
198		241
199	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
200	install urxvt with privileges necessary for your OS now.
201		243
202	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
203	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
204	systems, utmp/wtmp/lastlog handling on others) and drop privileges	246	there yet, no matter what they claim. Rxvt-Unicode contains the necessary
205	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
206	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.
207	things as perl interpreters, which might be "helpful" to attackers).
208		249
209	This forking is done as the very first within main(), which is very early	250	4. Use xcompmgr and let it do the job:
210	and reduces possible bugs to initialisation code run before main(), or
211	things like the dynamic loader of your system, which should result in very
212	little risk.
213		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), whether 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 '\33]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 its 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 its 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 permanently 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 whether 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 Can I see a typical configuration?
		664
		665	The default configuration tries to be xterm-like, which I don't like that
		666	much, but it's least surprise to regular users.
		667
		668	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		669	time into customising your terminal. To get you started, here is the
		670	author's .Xdefaults entries, with comments on what they do. It's certainly
		671	not I<typical>, but what's typical...
		672
		673	URxvt.cutchars: "()*,<>[]{}|'
		674	URxvt.print-pipe: cat >/tmp/xxx
		675
		676	These are just for testing stuff.
		677
		678	URxvt.imLocale: ja_JP.UTF-8
		679	URxvt.preeditType: OnTheSpot,None
		680
		681	This tells rxvt-unicode to use a special locale when communicating with
		682	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		683	type, which requires the C<xim-onthespot> perl extension but rewards me
		684	with correct-looking fonts.
		685
		686	URxvt.perl-lib: /root/lib/urxvt
		687	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		688	URxvt.selection.pattern-0: ( at .*? line \\d+)
		689	URxvt.selection.pattern-1: ^(/[^:]+):\
		690	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		691	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		692
		693	This is my perl configuration. The first two set the perl library
		694	directory and also tells urxvt to use a large number of extensions. I
		695	develop for myself mostly, so I actually use most of the extensions I
		696	write.
		697
		698	The selection stuff mainly makes the selection perl-error-message aware
		699	and tells it to convert perl error messages into vi-commands to load the
		700	relevant file and go tot he error line number.
		701
		702	URxvt.scrollstyle: plain
		703	URxvt.secondaryScroll: true
		704
		705	As the documentation says: plain is the preferred scrollbar for the
		706	author. The C<secondaryScroll> configures urxvt to scroll in full-screen
		707	apps, like screen, so lines scrolled out of screen end up in urxvt's
		708	scrollback buffer.
		709
		710	URxvt.background: #000000
		711	URxvt.foreground: gray90
		712	URxvt.color7: gray90
		713	URxvt.colorBD: #ffffff
		714	URxvt.cursorColor: #e0e080
		715	URxvt.throughColor: #8080f0
		716	URxvt.highlightColor: #f0f0f0
		717
		718	Some colours. Not sure which ones are being used or even non-defaults, but
		719	these are in my .Xdefaults. Most notably, they set foreground/background
		720	to light gray/black, and also make sure that the colour 7 matches the
		721	default foreground colour.
		722
		723	URxvt.underlineColor: yellow
		724
		725	Another colour, makes underline lines look different. Sometimes hurts, but
		726	is mostly a nice effect.
		727
		728	URxvt.geometry: 154x36
		729	URxvt.loginShell: false
		730	URxvt.meta: ignore
		731	URxvt.utmpInhibit: true
		732
		733	Uh, well, should be mostly self-explanatory. By specifying some defaults
		734	manually, I can quickly switch them for testing.
		735
		736	URxvt.saveLines: 8192
		737
		738	A large scrollback buffer is essential. Really.
		739
		740	URxvt.mapAlert: true
		741
		742	The only case I use it is for my IRC window, which I like to keep
		743	iconified till people msg me (which beeps).
		744
		745	URxvt.visualBell: true
		746
		747	The audible bell is often annoying, especially when in a crowd.
		748
		749	URxvt.insecure: true
		750
		751	Please don't hack my mutt! Ooops...
		752
		753	URxvt.pastableTabs: false
		754
		755	I once thought this is a great idea.
		756
		757	urxvt.font: 9x15bold,\
		758	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		759	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		760	[codeset=JISX0208]xft:Kochi Gothic, \
		761	xft:Bitstream Vera Sans Mono:autohint=true, \
		762	xft:Code2000:antialias=false
		763	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		764	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		765	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		766
		767	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		768	overwhelmed. A special note: the C<9x15bold> mentioned above is actually
		769	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		770	font (different glyphs for C<;> and many other harmless characters),
		771	while the second font is actually the C<9x15bold> from XFree4/XOrg. The
		772	bold version has less chars than the medium version, so I use it for rare
		773	characters, too. When editing sources with vim, I use italic for comments
		774	and other stuff, which looks quite good with Bitstream Vera anti-aliased.
		775
		776	Terminus is a quite bad font (many very wrong glyphs), but for most of my
		777	purposes, it works, and gives a different look, as my normal (Non-bold)
		778	font is already bold, and I want to see a difference between bold and
		779	normal fonts.
		780
		781	Please note that I used the C<urxvt> instance name and not the C<URxvt>
		782	class name. Thats because I use different configs for different purposes,
		783	for example, my IRC window is started with C<-name IRC>, and uses these
		784	defaults:
		785
		786	IRC*title: IRC
		787	IRC*geometry: 87x12+535+542
		788	IRC*saveLines: 0
		789	IRC*mapAlert: true
		790	IRC*font: suxuseuro
		791	IRC*boldFont: suxuseuro
		792	IRC*colorBD: white
		793	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		794	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		795
		796	C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font
		797	sizes. C<suxuseuro> allows me to keep an eye (and actually read)
		798	stuff while keeping a very small window. If somebody pastes something
		799	complicated (e.g. japanese), I temporarily switch to a larger font.
		800
		801	The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor
		802	C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname>
		803	file for different hosts, for example, on ym main desktop, I use:
		804
		805	URxvt.keysym.C-M-q: command:\033[3;5;5t
		806	URxvt.keysym.C-M-y: command:\033[3;5;606t
		807	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		808	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		809	URxvt.keysym.C-M-p: perl:test
		810
		811	The first for keysym definitions allow me to quickly bring some windows
		812	in the layout I like most. Ion users might start laughing but will stop
		813	immediately when I tell them that I use my own Fvwm2 module for much the
		814	same effect as Ion provides, and I only very rarely use the above key
		815	combinations :->
		816
		817	=head3 Why doesn't rxvt-unicode read my resources?
		818
		819	Well, why, indeed? It does, in a way very similar to other X
		820	applications. Most importantly, this means that if you or your OS loads
		821	resources into the X display (the right way to do it), rxvt-unicode will
		822	ignore any resource files in your home directory. It will only read
		823	F<$HOME/.Xdefaults> when no resources are attached to the display.
		824
		825	If you have or use an F<$HOME/.Xresources> file, chances are that
		826	resources are loaded into your X-server. In this case, you have to
		827	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		828
		829	Also consider the form resources have to use:
		830
		831	URxvt.resource: value
		832
		833	If you want to use another form (there are lots of different ways of
		834	specifying resources), make sure you understand whether and why it
		835	works. If unsure, use the form above.
		836
214	=item When I log-in to another system it tells me about missing terminfo data?	837	=head3 When I log-in to another system it tells me about missing terminfo data?
215		838
216	The terminal description used by rxvt-unicode is not as widely available	839	The terminal description used by rxvt-unicode is not as widely available
217	as that for xterm, or even rxvt (for which the same problem often arises).	840	as that for xterm, or even rxvt (for which the same problem often arises).
218		841
219	The correct solution for this problem is to install the terminfo, this can	842	The correct solution for this problem is to install the terminfo, this can
220	be done like this (with ncurses' infocmp):	843	be done like this (with ncurses' infocmp and works as user and admin):
221		844
222	REMOTE=remotesystem.domain	845	REMOTE=remotesystem.domain
223	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	846	infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
224		847
225	... or by installing rxvt-unicode normally on the remote system,	848	... or by installing rxvt-unicode normally on the remote system,
		849
		850	One some systems you might need to set C<$TERMINFO> to the full path of
		851	F<$HOME/.terminfo> for this to work.
226		852
227	If you cannot or do not want to do this, then you can simply set	853	If you cannot or do not want to do this, then you can simply set
228	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of	854	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
229	problems arising, which includes wrong keymapping, less and different	855	problems arising, which includes wrong keymapping, less and different
230	colours and some refresh errors in fullscreen applications. It's a nice	856	colours and some refresh errors in fullscreen applications. It's a nice
…		…
235	resource to set it:	861	resource to set it:
236		862
237	URxvt.termName: rxvt	863	URxvt.termName: rxvt
238		864
239	If you don't plan to use B<rxvt> (quite common...) you could also replace	865	If you don't plan to use B<rxvt> (quite common...) you could also replace
240	the rxvt terminfo file with the rxvt-unicode one.	866	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
241		867
242	=item C<tic> outputs some error when compiling the terminfo entry.	868	=head3 C<tic> outputs some error when compiling the terminfo entry.
243		869
244	Most likely it's the empty definition for C<enacs=>. Just replace it by	870	Most likely it's the empty definition for C<enacs=>. Just replace it by
245	C<enacs=\E[0@> and try again.	871	C<enacs=\E[0@> and try again.
246		872
247	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	873	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
248		874
		875	See next entry.
		876
249	=item I need a termcap file entry.	877	=head3 I need a termcap file entry.
250		878
251	One reason you might want this is that some distributions or operating	879	One reason you might want this is that some distributions or operating
252	systems still compile some programs using the long-obsoleted termcap	880	systems still compile some programs using the long-obsoleted termcap
253	library (Fedora Core's bash is one example) and rely on a termcap entry	881	library (Fedora Core's bash is one example) and rely on a termcap entry
254	for C<rxvt-unicode>.	882	for C<rxvt-unicode>.
255		883
256	You could use rxvt's termcap entry with resonable results in many cases.	884	You could use rxvt's termcap entry with reasonable results in many cases.
257	You can also create a termcap entry by using terminfo's infocmp program	885	You can also create a termcap entry by using terminfo's infocmp program
258	like this:	886	like this:
259		887
260	infocmp -C rxvt-unicode	888	infocmp -C rxvt-unicode
261		889
…		…
280	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	908	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
281	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	909	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
282	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	910	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
283	:vs=\E[?25h:	911	:vs=\E[?25h:
284		912
285	=item Why does C<ls> no longer have coloured output?	913	=head3 Why does C<ls> no longer have coloured output?
286		914
287	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	915	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
288	decide wether a terminal has colour, but uses it's own configuration	916	decide whether a terminal has colour, but uses its own configuration
289	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	917	file. Needless to say, C<rxvt-unicode> is not in its default file (among
290	with most other terminals supporting colour). Either add:	918	with most other terminals supporting colour). Either add:
291		919
292	TERM rxvt-unicode	920	TERM rxvt-unicode
293		921
294	to C</etc/DIR_COLORS> or simply add:	922	to C</etc/DIR_COLORS> or simply add:
295		923
296	alias ls='ls --color=auto'	924	alias ls='ls --color=auto'
297		925
298	to your C<.profile> or C<.bashrc>.	926	to your C<.profile> or C<.bashrc>.
299		927
300	=item Why doesn't vim/emacs etc. use the 88 colour mode?	928	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
301		929
		930	See next entry.
		931
302	=item Why doesn't vim/emacs etc. make use of italic?	932	=head3 Why doesn't vim/emacs etc. make use of italic?
303		933
		934	See next entry.
		935
304	=item Why are the secondary screen-related options not working properly?	936	=head3 Why are the secondary screen-related options not working properly?
305		937
306	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	938	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
307	distributions (most notably Debian GNU/Linux) break rxvt-unicode	939	distributions (most notably Debian GNU/Linux) break rxvt-unicode
308	by setting C<TERM> to C<rxvt>, which doesn't have these extra	940	by setting C<TERM> to C<rxvt>, which doesn't have these extra
309	features. Unfortunately, some of these (most notably, again, Debian	941	features. Unfortunately, some of these (most notably, again, Debian
310	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	942	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
311	file, so you will need to install it on your own (See the question B<When	943	file, so you will need to install it on your own (See the question B<When
312	I log-in to another system it tells me about missing terminfo data?> on	944	I log-in to another system it tells me about missing terminfo data?> on
313	how to do this).	945	how to do this).
314		946
315	=item My numerical keypad acts weird and generates differing output?
316		947
317	Some Debian GNUL/Linux users seem to have this problem, although no	948	=head2 Encoding / Locale / Input Method Issues
318	specific details were reported so far. It is possible that this is caused
319	by the wrong C<TERM> setting, although the details of wether and how
320	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
321	keymap. See the answer to the previous question, and please report if that
322	helped.
323		949
324	=item Rxvt-unicode does not seem to understand the selected encoding?	950	=head3 Rxvt-unicode does not seem to understand the selected encoding?
325		951
		952	See next entry.
		953
326	=item Unicode does not seem to work?	954	=head3 Unicode does not seem to work?
327		955
328	If you encounter strange problems like typing an accented character but	956	If you encounter strange problems like typing an accented character but
329	getting two unrelated other characters or similar, or if program output is	957	getting two unrelated other characters or similar, or if program output is
330	subtly garbled, then you should check your locale settings.	958	subtly garbled, then you should check your locale settings.
331		959
…		…
335	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.	963	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
336		964
337	The best thing is to fix your startup environment, as you will likely run	965	The best thing is to fix your startup environment, as you will likely run
338	into other problems. If nothing works you can try this in your .profile.	966	into other problems. If nothing works you can try this in your .profile.
339		967
340	printf '\e]701;%s\007' "$LC_CTYPE"	968	printf '\33]701;%s\007' "$LC_CTYPE"
341		969
342	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	970	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
343	supported on your systems. Some systems have a C<locale> command which	971	supported on your systems. Some systems have a C<locale> command which
344	displays this (also, C<perl -e0> can be used to check locale settings, as	972	displays this (also, C<perl -e0> can be used to check locale settings, as
345	it will complain loudly if it cannot set the locale). If it displays something	973	it will complain loudly if it cannot set the locale). If it displays something
…		…
351		979
352	If nothing works and you are sure that everything is set correctly then	980	If nothing works and you are sure that everything is set correctly then
353	you will need to remember a little known fact: Some programs just don't	981	you will need to remember a little known fact: Some programs just don't
354	support locales :(	982	support locales :(
355		983
356	=item Why do some characters look so much different than others?	984	=head3 How does rxvt-unicode determine the encoding to use?
357		985
358	=item How does rxvt-unicode choose fonts?	986	See next entry.
359		987
360	Most fonts do not contain the full range of Unicode, which is	988	=head3 Is there an option to switch encodings?
361	fine. Chances are that the font you (or the admin/package maintainer of
362	your system/os) have specified does not cover all the characters you want
363	to display.
364		989
365	B<rxvt-unicode> makes a best-effort try at finding a replacement	990	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
366	font. Often the result is fine, but sometimes the chosen font looks	991	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
367	bad/ugly/wrong. Some fonts have totally strange characters that don't	992	UTF-8 or any other encodings with respect to terminal I/O.
368	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
369	intelligence to detect that a specific glyph is wrong: it has to believe
370	the font that the characters it claims to contain indeed look correct.
371		993
372	In that case, select a font of your taste and add it to the font list,	994	The reasons is that there exists a perfectly fine mechanism for selecting
373	e.g.:	995	the encoding, doing I/O and (most important) communicating this to all
374		996	applications so everybody agrees on character properties such as width
375	@@RXVT_NAME@@ -fn basefont,font2,font3...	997	and code number. This mechanism is the I<locale>. Applications not using
376		998	that info will have problems (for example, C<xterm> gets the width of
377	When rxvt-unicode sees a character, it will first look at the base	999	characters wrong as it uses its own, locale-independent table under all
378	font. If the base font does not contain the character, it will go to the
379	next font, and so on. Specifying your own fonts will also speed up this
380	search and use less resources within rxvt-unicode and the X-server.
381
382	The only limitation is that none of the fonts may be larger than the base
383	font, as the base font defines the terminal character cell size, which
384	must be the same due to the way terminals work.
385
386	=item Why do some chinese characters look so different than others?
387
388	This is because there is a difference between script and language --
389	rxvt-unicode does not know which language the text that is output is,
390	as it only knows the unicode character codes. If rxvt-unicode first
391	sees a japanese/chinese character, it might choose a japanese font for
392	display. Subsequent japanese characters will use that font. Now, many
393	chinese characters aren't represented in japanese fonts, so when the first
394	non-japanese character comes up, rxvt-unicode will look for a chinese font
395	-- unfortunately at this point, it will still use the japanese font for
396	chinese characters that are also in the japanese font.
397
398	The workaround is easy: just tag a chinese font at the end of your font
399	list (see the previous question). The key is to view the font list as
400	a preference list: If you expect more japanese, list a japanese font
401	first. If you expect more chinese, put a chinese font first.
402
403	In the future it might be possible to switch language preferences at
404	runtime (the internal data structure has no problem with using different
405	fonts for the same character at the same time, but no interface for this
406	has been designed yet).
407
408	Until then, you might get away with switching fonts at runtime (see L<Can
409	I switch the fonts at runtime?> later in this document).
410
411	=item Why does rxvt-unicode sometimes leave pixel droppings?
412
413	Most fonts were not designed for terminal use, which means that character
414	size varies a lot. A font that is otherwise fine for terminal use might
415	contain some characters that are simply too wide. Rxvt-unicode will avoid
416	these characters. For characters that are just "a bit" too wide a special
417	"careful" rendering mode is used that redraws adjacent characters.
418
419	All of this requires that fonts do not lie about character sizes,
420	however: Xft fonts often draw glyphs larger than their acclaimed bounding
421	box, and rxvt-unicode has no way of detecting this (the correct way is to
422	ask for the character bounding box, which unfortunately is wrong in these
423	cases).	1000	locales).
424		1001
425	It's not clear (to me at least), wether this is a bug in Xft, freetype,	1002	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
426	or the respective font. If you encounter this problem you might try using	1003	programs doing the same (that is, most) will automatically agree in the
427	the C<-lsp> option to give the font more height. If that doesn't work, you	1004	interpretation of characters.
428	might be forced to use a different font.
429		1005
430	All of this is not a problem when using X11 core fonts, as their bounding	1006	Unfortunately, there is no system-independent way to select locales, nor
431	box data is correct.	1007	is there a standard on how locale specifiers will look like.
432		1008
		1009	On most systems, the content of the C<LC_CTYPE> environment variable
		1010	contains an arbitrary string which corresponds to an already-installed
		1011	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1012	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1013	(i.e. C<de> or C<german>) are also common.
		1014
		1015	Rxvt-unicode ignores all other locale categories, and except for
		1016	the encoding, ignores country or language-specific settings,
		1017	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		1018	rxvt-unicode.
		1019
		1020	If you want to use a specific encoding you have to make sure you start
		1021	rxvt-unicode with the correct C<LC_CTYPE> category.
		1022
		1023	=head3 Can I switch locales at runtime?
		1024
		1025	Yes, using an escape sequence. Try something like this, which sets
		1026	rxvt-unicode's idea of C<LC_CTYPE>.
		1027
		1028	printf '\33]701;%s\007' ja_JP.SJIS
		1029
		1030	See also the previous answer.
		1031
		1032	Sometimes this capability is rather handy when you want to work in
		1033	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		1034	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		1035	first switches to a locale supported by xjdic and back later:
		1036
		1037	printf '\33]701;%s\007' ja_JP.SJIS
		1038	xjdic -js
		1039	printf '\33]701;%s\007' de_DE.UTF-8
		1040
		1041	You can also use xterm's C<luit> program, which usually works fine, except
		1042	for some locales where character width differs between program- and
		1043	rxvt-unicode-locales.
		1044
		1045	=head3 I have problems getting my input method working.
		1046
		1047	Try a search engine, as this is slightly different for every input method server.
		1048
		1049	Here is a checklist:
		1050
		1051	=over 4
		1052
		1053	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		1054
		1055	Try C<locale -a> or check the documentation for your OS.
		1056
		1057	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		1058
		1059	For example, B<kinput2> does not support UTF-8 locales, you should use
		1060	C<ja_JP.EUC-JP> or equivalent.
		1061
		1062	=item - Make sure your XIM server is actually running.
		1063
		1064	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		1065
		1066	When you want to use e.g. B<kinput2>, it must be set to
		1067	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
		1068	method servers are running with this command:
		1069
		1070	xprop -root XIM_SERVERS
		1071
		1072	=item
		1073
		1074	=back
		1075
		1076	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		1077
		1078	You can specify separate locales for the input method and the rest of the
		1079	terminal, using the resource C<imlocale>:
		1080
		1081	URxvt.imlocale: ja_JP.EUC-JP
		1082
		1083	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1084	use your input method. Please note, however, that, depending on your Xlib
		1085	version, you may not be able to input characters outside C<EUC-JP> in a
		1086	normal way then, as your input method limits you.
		1087
		1088	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		1089
		1090	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1091	design. Applications can avoid some crashes at the expense of memory
		1092	leaks, and Input Methods can avoid some crashes by careful ordering at
		1093	exit time. B<kinput2> (and derived input methods) generally succeeds,
		1094	while B<SCIM> (or similar input methods) fails. In the end, however,
		1095	crashes cannot be completely avoided even if both sides cooperate.
		1096
		1097	So the only workaround is not to kill your Input Method Servers.
		1098
		1099
		1100	=head2 Operating Systems / Package Maintaining
		1101
		1102	=head3 I am using Debian GNU/Linux and have a problem...
		1103
		1104	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1105	patches that considerably change the behaviour of rxvt-unicode (but
		1106	unfortunately this notice has been removed). Before reporting a bug to
		1107	the original rxvt-unicode author please download and install the genuine
		1108	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1109	the problem. If you cannot, chances are that the problems are specific to
		1110	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1111	Tracking System (use C<reportbug> to report the bug).
		1112
		1113	For other problems that also affect the Debian package, you can and
		1114	probably should use the Debian BTS, too, because, after all, it's also a
		1115	bug in the Debian version and it serves as a reminder for other users that
		1116	might encounter the same issue.
		1117
		1118	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1119
		1120	You should build one binary with the default options. F<configure>
		1121	now enables most useful options, and the trend goes to making them
		1122	runtime-switchable, too, so there is usually no drawback to enabling them,
		1123	except higher disk and possibly memory usage. The perl interpreter should
		1124	be enabled, as important functionality (menus, selection, likely more in
		1125	the future) depends on it.
		1126
		1127	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		1128	system-wide (except maybe with C<defaults>). This will result in useful
		1129	behaviour. If your distribution aims at low memory, add an empty
		1130	C<perl-ext-common> resource to the app-defaults file. This will keep the
		1131	perl interpreter disabled until the user enables it.
		1132
		1133	If you can/want build more binaries, I recommend building a minimal
		1134	one with C<--disable-everything> (very useful) and a maximal one with
		1135	C<--enable-everything> (less useful, it will be very big due to a lot of
		1136	encodings built-in that increase download times and are rarely used).
		1137
		1138	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1139
		1140	It should be, starting with release 7.1. You are encouraged to properly
		1141	install urxvt with privileges necessary for your OS now.
		1142
		1143	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1144	into a helper process for privileged operations (pty handling on some
		1145	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1146	immediately. This is much safer than most other terminals that keep
		1147	privileges while running (but is more relevant to urxvt, as it contains
		1148	things as perl interpreters, which might be "helpful" to attackers).
		1149
		1150	This forking is done as the very first within main(), which is very early
		1151	and reduces possible bugs to initialisation code run before main(), or
		1152	things like the dynamic loader of your system, which should result in very
		1153	little risk.
		1154
433	=item On Solaris 9, many line-drawing characters are too wide.	1155	=head3 On Solaris 9, many line-drawing characters are too wide.
434		1156
435	Seems to be a known bug, read	1157	Seems to be a known bug, read
436	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1158	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
437	following ugly workaround to get non-double-wide-characters working:	1159	following ugly workaround to get non-double-wide-characters working:
438		1160
439	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1161	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
440		1162
441	=item My Compose (Multi_key) key is no longer working.
442
443	The most common causes for this are that either your locale is not set
444	correctly, or you specified a B<preeditStyle> that is not supported by
445	your input method. For example, if you specified B<OverTheSpot> and
446	your input method (e.g. the default input method handling Compose keys)
447	does not support this (for instance because it is not visual), then
448	rxvt-unicode will continue without an input method.
449
450	In this case either do not specify a B<preeditStyle> or specify more than
451	one pre-edit style, such as B<OverTheSpot,Root,None>.
452
453	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
454
455	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
456	international keyboards) or simply use ISO 14755 support to your
457	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
458	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
459	character and so on.
460
461	=item How can I keep rxvt-unicode from using reverse video so much?
462
463	First of all, make sure you are running with the right terminal settings
464	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
465	make sure you have specified colours for italic and bold, as otherwise
466	rxvt-unicode might use reverse video to simulate the effect:
467
468	URxvt.colorBD: white
469	URxvt.colorIT: green
470
471	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
472
473	For some unexplainable reason, some rare programs assume a very weird
474	colour palette when confronted with a terminal with more than the standard
475	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
476	these programs not to assume non-ISO colours without very good reasons.
477
478	In the meantime, you can either edit your C<rxvt-unicode> terminfo
479	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
480	fix colours but keep you from using other rxvt-unicode features.
481
482	=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.
483		1164
484	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
485	in your compile environment, or an implementation that implements it,	1166	in your compile environment, or an implementation that implements it,
486	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
487	B<wchar_t> is represented as unicode.	1168	B<wchar_t> is represented as unicode.
488		1169
489	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
490	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
491	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.
492		1173
493	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
494	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>.
495		1176
…		…
509		1190
510	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
511	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
512	complete replacements for them :)	1193	complete replacements for them :)
513		1194
514	=item I use Solaris 9 and it doesn't compile/work/etc.	1195	=head3 I use Solaris 9 and it doesn't compile/work/etc.
515		1196
516	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1197	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
517	problems with C<wcwidth> and a compile problem.	1198	problems with C<wcwidth> and a compile problem.
518		1199
519	=item How can I use rxvt-unicode under cygwin?	1200	=head3 How can I use rxvt-unicode under cygwin?
520		1201
521	rxvt-unicode should compile and run out of the box on cygwin, using	1202	rxvt-unicode should compile and run out of the box on cygwin, using
522	the X11 libraries that come with cygwin. libW11 emulation is no	1203	the X11 libraries that come with cygwin. libW11 emulation is no
523	longer supported (and makes no sense, either, as it only supported a	1204	longer supported (and makes no sense, either, as it only supported a
524	single font). I recommend starting the X-server in C<-multiwindow> or	1205	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
527		1208
528	At the time of this writing, cygwin didn't seem to support any multi-byte	1209	At the time of this writing, cygwin didn't seem to support any multi-byte
529	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1210	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
530	to 8-bit encodings.	1211	to 8-bit encodings.
531		1212
532	=item How does rxvt-unicode determine the encoding to use?
533
534	=item Is there an option to switch encodings?
535
536	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
537	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
538	UTF-8 or any other encodings with respect to terminal I/O.
539
540	The reasons is that there exists a perfectly fine mechanism for selecting
541	the encoding, doing I/O and (most important) communicating this to all
542	applications so everybody agrees on character properties such as width
543	and code number. This mechanism is the I<locale>. Applications not using
544	that info will have problems (for example, C<xterm> gets the width of
545	characters wrong as it uses it's own, locale-independent table under all
546	locales).
547
548	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
549	programs doing the same (that is, most) will automatically agree in the
550	interpretation of characters.
551
552	Unfortunately, there is no system-independent way to select locales, nor
553	is there a standard on how locale specifiers will look like.
554
555	On most systems, the content of the C<LC_CTYPE> environment variable
556	contains an arbitrary string which corresponds to an already-installed
557	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
558	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
559	(i.e. C<de> or C<german>) are also common.
560
561	Rxvt-unicode ignores all other locale categories, and except for
562	the encoding, ignores country or language-specific settings,
563	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
564	rxvt-unicode.
565
566	If you want to use a specific encoding you have to make sure you start
567	rxvt-unicode with the correct C<LC_CTYPE> category.
568
569	=item Can I switch locales at runtime?
570
571	Yes, using an escape sequence. Try something like this, which sets
572	rxvt-unicode's idea of C<LC_CTYPE>.
573
574	printf '\e]701;%s\007' ja_JP.SJIS
575
576	See also the previous answer.
577
578	Sometimes this capability is rather handy when you want to work in
579	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
580	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
581	first switches to a locale supported by xjdic and back later:
582
583	printf '\e]701;%s\007' ja_JP.SJIS
584	xjdic -js
585	printf '\e]701;%s\007' de_DE.UTF-8
586
587	You can also use xterm's C<luit> program, which usually works fine, except
588	for some locales where character width differs between program- and
589	rxvt-unicode-locales.
590
591	=item Can I switch the fonts at runtime?
592
593	Yes, using an escape sequence. Try something like this, which has the same
594	effect as using the C<-fn> switch, and takes effect immediately:
595
596	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
597
598	This is useful if you e.g. work primarily with japanese (and prefer a
599	japanese font), but you have to switch to chinese temporarily, where
600	japanese fonts would only be in your way.
601
602	You can think of this as a kind of manual ISO-2022 switching.
603
604	=item Why do italic characters look as if clipped?
605
606	Many fonts have difficulties with italic characters and hinting. For
607	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
608	Mono> completely fails in it's italic face. A workaround might be to
609	enable freetype autohinting, i.e. like this:
610
611	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
612	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
613
614	=item My input method wants <some encoding> but I want UTF-8, what can I do?
615
616	You can specify separate locales for the input method and the rest of the
617	terminal, using the resource C<imlocale>:
618
619	URxvt.imlocale: ja_JP.EUC-JP
620
621	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
622	use your input method. Please note, however, that you will not be able to
623	input characters outside C<EUC-JP> in a normal way then, as your input
624	method limits you.
625
626	=item Rxvt-unicode crashes when the X Input Method changes or exits.
627
628	Unfortunately, this is unavoidable, as the XIM protocol is racy by
629	design. Applications can avoid some crashes at the expense of memory
630	leaks, and Input Methods can avoid some crashes by careful ordering at
631	exit time. B<kinput2> (and derived input methods) generally succeeds,
632	while B<SCIM> (or similar input methods) fails. In the end, however,
633	crashes cannot be completely avoided even if both sides cooperate.
634
635	So the only workaround is not to kill your Input Method Servers.
636
637	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
638
639	Rxvt-unicode tries to obey the rule of not charging you for something you
640	don't use. One thing you should try is to configure out all settings that
641	you don't need, for example, Xft support is a resource hog by design,
642	when used. Compiling it out ensures that no Xft font will be loaded
643	accidentally when rxvt-unicode tries to find a font for your characters.
644
645	Also, many people (me included) like large windows and even larger
646	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
647	6 bytes per screen cell. For a 160x?? window this amounts to almost a
648	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
649	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
650	rxvt-unicode then uses 8 bytes per screen cell.
651
652	=item Can I speed up Xft rendering somehow?
653
654	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
655	it is simply slow. If you still want Xft fonts you might try to disable
656	antialiasing (by appending C<:antialias=false>), which saves lots of
657	memory and also speeds up rendering considerably.
658
659	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
660
661	Rxvt-unicode will use whatever you specify as a font. If it needs to
662	fall back to it's default font search list it will prefer X11 core
663	fonts, because they are small and fast, and then use Xft fonts. It has
664	antialiasing disabled for most of them, because the author thinks they
665	look best that way.
666
667	If you want antialiasing, you have to specify the fonts manually.
668
669	=item Mouse cut/paste suddenly no longer works.
670
671	Make sure that mouse reporting is actually turned off since killing
672	some editors prematurely may leave the mouse in mouse report mode. I've
673	heard that tcsh may use mouse reporting unless it otherwise specified. A
674	quick check is to see if cut/paste works when the Alt or Shift keys are
675	depressed.
676
677	=item What's with this bold/blink stuff?
678
679	If no bold colour is set via C<colorBD:>, bold will invert text using the
680	standard foreground colour.
681
682	For the standard background colour, blinking will actually make the
683	text blink when compiled with C<--enable-blinking>. with standard
684	colours. Without C<--enable-blinking>, the blink attribute will be
685	ignored.
686
687	On ANSI colours, bold/blink attributes are used to set high-intensity
688	foreground/background colors.
689
690	color0-7 are the low-intensity colors.
691
692	color8-15 are the corresponding high-intensity colors.
693
694	=item I don't like the screen colors. How do I change them?
695
696	You can change the screen colors at run-time using F<~/.Xdefaults>
697	resources (or as long-options).
698
699	Here are values that are supposed to resemble a VGA screen,
700	including the murky brown that passes for low-intensity yellow:
701
702	URxvt.color0: #000000
703	URxvt.color1: #A80000
704	URxvt.color2: #00A800
705	URxvt.color3: #A8A800
706	URxvt.color4: #0000A8
707	URxvt.color5: #A800A8
708	URxvt.color6: #00A8A8
709	URxvt.color7: #A8A8A8
710
711	URxvt.color8: #000054
712	URxvt.color9: #FF0054
713	URxvt.color10: #00FF54
714	URxvt.color11: #FFFF54
715	URxvt.color12: #0000FF
716	URxvt.color13: #FF00FF
717	URxvt.color14: #00FFFF
718	URxvt.color15: #FFFFFF
719
720	And here is a more complete set of non-standard colors described (not by
721	me) as "pretty girly".
722
723	URxvt.cursorColor: #dc74d1
724	URxvt.pointerColor: #dc74d1
725	URxvt.background: #0e0e0e
726	URxvt.foreground: #4ad5e1
727	URxvt.color0: #000000
728	URxvt.color8: #8b8f93
729	URxvt.color1: #dc74d1
730	URxvt.color9: #dc74d1
731	URxvt.color2: #0eb8c7
732	URxvt.color10: #0eb8c7
733	URxvt.color3: #dfe37e
734	URxvt.color11: #dfe37e
735	URxvt.color5: #9e88f0
736	URxvt.color13: #9e88f0
737	URxvt.color6: #73f7ff
738	URxvt.color14: #73f7ff
739	URxvt.color7: #e1dddd
740	URxvt.color15: #e1dddd
741
742	=item How can I start @@RXVT_NAME@@d in a race-free way?
743
744	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
745	display, create the listening socket and then fork.
746
747	=item What's with the strange Backspace/Delete key behaviour?
748
749	Assuming that the physical Backspace key corresponds to the
750	BackSpace keysym (not likely for Linux ... see the following
751	question) there are two standard values that can be used for
752	Backspace: C<^H> and C<^?>.
753
754	Historically, either value is correct, but rxvt-unicode adopts the debian
755	policy of using C<^?> when unsure, because it's the one only only correct
756	choice :).
757
758	Rxvt-unicode tries to inherit the current stty settings and uses the value
759	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
760	started from a terminal (say, from a menu or by remote shell), then the
761	system value of `erase', which corresponds to CERASE in <termios.h>, will
762	be used (which may not be the same as your stty setting).
763
764	For starting a new rxvt-unicode:
765
766	# use Backspace = ^H
767	$ stty erase ^H
768	$ @@RXVT_NAME@@
769
770	# use Backspace = ^?
771	$ stty erase ^?
772	$ @@RXVT_NAME@@
773
774	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
775
776	For an existing rxvt-unicode:
777
778	# use Backspace = ^H
779	$ stty erase ^H
780	$ echo -n "^[[36h"
781
782	# use Backspace = ^?
783	$ stty erase ^?
784	$ echo -n "^[[36l"
785
786	This helps satisfy some of the Backspace discrepancies that occur, but
787	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
788	properly reflects that.
789
790	The Delete key is a another casualty of the ill-defined Backspace problem.
791	To avoid confusion between the Backspace and Delete keys, the Delete
792	key has been assigned an escape sequence to match the vt100 for Execute
793	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
794
795	Some other Backspace problems:
796
797	some editors use termcap/terminfo,
798	some editors (vim I'm told) expect Backspace = ^H,
799	GNU Emacs (and Emacs-like editors) use ^H for help.
800
801	Perhaps someday this will all be resolved in a consistent manner.
802
803	=item I don't like the key-bindings. How do I change them?
804
805	There are some compile-time selections available via configure. Unless
806	you have run "configure" with the C<--disable-resources> option you can
807	use the `keysym' resource to alter the keystrings associated with keysyms.
808
809	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
810
811	URxvt.keysym.Home: \033[1~
812	URxvt.keysym.End: \033[4~
813	URxvt.keysym.C-apostrophe: \033<C-'>
814	URxvt.keysym.C-slash: \033<C-/>
815	URxvt.keysym.C-semicolon: \033<C-;>
816	URxvt.keysym.C-grave: \033<C-`>
817	URxvt.keysym.C-comma: \033<C-,>
818	URxvt.keysym.C-period: \033<C-.>
819	URxvt.keysym.C-0x60: \033<C-`>
820	URxvt.keysym.C-Tab: \033<C-Tab>
821	URxvt.keysym.C-Return: \033<C-Return>
822	URxvt.keysym.S-Return: \033<S-Return>
823	URxvt.keysym.S-space: \033<S-Space>
824	URxvt.keysym.M-Up: \033<M-Up>
825	URxvt.keysym.M-Down: \033<M-Down>
826	URxvt.keysym.M-Left: \033<M-Left>
827	URxvt.keysym.M-Right: \033<M-Right>
828	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
829	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
830	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
831
832	See some more examples in the documentation for the B<keysym> resource.
833
834	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
835	How do I make use of them? For example, the Sun Keyboard type 4
836	has the following mappings that rxvt-unicode doesn't recognize.
837
838	KP_Insert == Insert
839	F22 == Print
840	F27 == Home
841	F29 == Prior
842	F33 == End
843	F35 == Next
844
845	Rather than have rxvt-unicode try to accommodate all the various possible
846	keyboard mappings, it is better to use `xmodmap' to remap the keys as
847	required for your particular machine.
848
849	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
850	I need this to decide about setting colors etc.
851
852	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
853	check and see if that is set. Note that several programs, JED, slrn,
854	Midnight Commander automatically check this variable to decide whether or
855	not to use color.
856
857	=item How do I set the correct, full IP address for the DISPLAY variable?
858
859	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
860	insecure mode then it is possible to use the following shell script
861	snippets to correctly set the display. If your version of rxvt-unicode
862	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
863	the COLORTERM variable can be used to distinguish rxvt-unicode from a
864	regular xterm.
865
866	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
867	snippets:
868
869	# Bourne/Korn/POSIX family of shells:
870	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
871	if [ ${TERM:-foo} = xterm ]; then
872	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
873	echo -n '^[Z'
874	read term_id
875	stty icanon echo
876	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
877	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
878	read DISPLAY # set it in our local shell
879	fi
880	fi
881
882	=item How do I compile the manual pages for myself?
883
884	You need to have a recent version of perl installed as F</usr/bin/perl>,
885	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
886	the doc subdirectory and enter C<make alldoc>.
887
888	=item My question isn't answered here, can I ask a human?
889
890	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
891	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
892	interested in learning about new and exciting problems (but not FAQs :).
893
894	=back
895
896	=head1 RXVT TECHNICAL REFERENCE	1213	=head1 RXVT-UNICODE TECHNICAL REFERENCE
897
898	=head1 DESCRIPTION
899		1214
900	The rest of this document describes various technical aspects of	1215	The rest of this document describes various technical aspects of
901	B<rxvt-unicode>. First the description of supported command sequences,	1216	B<rxvt-unicode>. First the description of supported command sequences,
902	followed by pixmap support and last by a description of all features	1217	followed by pixmap support and last by a description of all features
903	selectable at C<configure> time.	1218	selectable at C<configure> time.
904		1219
905	=head1 Definitions	1220	=head2 Definitions
906		1221
907	=over 4	1222	=over 4
908		1223
909	=item B<< C<c> >>	1224	=item B<< C<c> >>
910		1225
…		…
928		1243
929	A text parameter composed of printable characters.	1244	A text parameter composed of printable characters.
930		1245
931	=back	1246	=back
932		1247
933	=head1 Values	1248	=head2 Values
934		1249
935	=over 4	1250	=over 4
936		1251
937	=item B<< C<ENQ> >>	1252	=item B<< C<ENQ> >>
938		1253
…		…
981		1296
982	Space Character	1297	Space Character
983		1298
984	=back	1299	=back
985		1300
986	=head1 Escape Sequences	1301	=head2 Escape Sequences
987		1302
988	=over 4	1303	=over 4
989		1304
990	=item B<< C<ESC # 8> >>	1305	=item B<< C<ESC # 8> >>
991		1306
…		…
1089		1404
1090	=back	1405	=back
1091		1406
1092	X<CSI>	1407	X<CSI>
1093		1408
1094	=head1 CSI (Command Sequence Introducer) Sequences	1409	=head2 CSI (Command Sequence Introducer) Sequences
1095		1410
1096	=over 4	1411	=over 4
1097		1412
1098	=item B<< C<ESC [ Ps @> >>	1413	=item B<< C<ESC [ Ps @> >>
1099		1414
…		…
1369		1684
1370	=back	1685	=back
1371		1686
1372	X<PrivateModes>	1687	X<PrivateModes>
1373		1688
1374	=head1 DEC Private Modes	1689	=head2 DEC Private Modes
1375		1690
1376	=over 4	1691	=over 4
1377		1692
1378	=item B<< C<ESC [ ? Pm h> >>	1693	=item B<< C<ESC [ ? Pm h> >>
1379		1694
…		…
1395		1710
1396	Toggle DEC Private Mode Values (rxvt extension). I<where>	1711	Toggle DEC Private Mode Values (rxvt extension). I<where>
1397		1712
1398	=over 4	1713	=over 4
1399		1714
1400	=item B<< C<Ps = 1> >> (DECCKM)	1715	=item B<< C<Pm = 1> >> (DECCKM)
1401		1716
1402	=begin table	1717	=begin table
1403		1718
1404	B<< C<h> >> Application Cursor Keys	1719	B<< C<h> >> Application Cursor Keys
1405	B<< C<l> >> Normal Cursor Keys	1720	B<< C<l> >> Normal Cursor Keys
1406		1721
1407	=end table	1722	=end table
1408		1723
1409	=item B<< C<Ps = 2> >> (ANSI/VT52 mode)	1724	=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1410		1725
1411	=begin table	1726	=begin table
1412		1727
1413	B<< C<h> >> Enter VT52 mode	1728	B<< C<h> >> Enter VT52 mode
1414	B<< C<l> >> Enter VT52 mode	1729	B<< C<l> >> Enter VT52 mode
1415		1730
1416	=end table	1731	=end table
1417		1732
1418	=item B<< C<Ps = 3> >>	1733	=item B<< C<Pm = 3> >>
1419		1734
1420	=begin table	1735	=begin table
1421		1736
1422	B<< C<h> >> 132 Column Mode (DECCOLM)	1737	B<< C<h> >> 132 Column Mode (DECCOLM)
1423	B<< C<l> >> 80 Column Mode (DECCOLM)	1738	B<< C<l> >> 80 Column Mode (DECCOLM)
1424		1739
1425	=end table	1740	=end table
1426		1741
1427	=item B<< C<Ps = 4> >>	1742	=item B<< C<Pm = 4> >>
1428		1743
1429	=begin table	1744	=begin table
1430		1745
1431	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)	1746	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1432	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)	1747	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1433		1748
1434	=end table	1749	=end table
1435		1750
1436	=item B<< C<Ps = 5> >>	1751	=item B<< C<Pm = 5> >>
1437		1752
1438	=begin table	1753	=begin table
1439		1754
1440	B<< C<h> >> Reverse Video (DECSCNM)	1755	B<< C<h> >> Reverse Video (DECSCNM)
1441	B<< C<l> >> Normal Video (DECSCNM)	1756	B<< C<l> >> Normal Video (DECSCNM)
1442		1757
1443	=end table	1758	=end table
1444		1759
1445	=item B<< C<Ps = 6> >>	1760	=item B<< C<Pm = 6> >>
1446		1761
1447	=begin table	1762	=begin table
1448		1763
1449	B<< C<h> >> Origin Mode (DECOM)	1764	B<< C<h> >> Origin Mode (DECOM)
1450	B<< C<l> >> Normal Cursor Mode (DECOM)	1765	B<< C<l> >> Normal Cursor Mode (DECOM)
1451		1766
1452	=end table	1767	=end table
1453		1768
1454	=item B<< C<Ps = 7> >>	1769	=item B<< C<Pm = 7> >>
1455		1770
1456	=begin table	1771	=begin table
1457		1772
1458	B<< C<h> >> Wraparound Mode (DECAWM)	1773	B<< C<h> >> Wraparound Mode (DECAWM)
1459	B<< C<l> >> No Wraparound Mode (DECAWM)	1774	B<< C<l> >> No Wraparound Mode (DECAWM)
1460		1775
1461	=end table	1776	=end table
1462		1777
1463	=item B<< C<Ps = 8> >> I<unimplemented>	1778	=item B<< C<Pm = 8> >> I<unimplemented>
1464		1779
1465	=begin table	1780	=begin table
1466		1781
1467	B<< C<h> >> Auto-repeat Keys (DECARM)	1782	B<< C<h> >> Auto-repeat Keys (DECARM)
1468	B<< C<l> >> No Auto-repeat Keys (DECARM)	1783	B<< C<l> >> No Auto-repeat Keys (DECARM)
1469		1784
1470	=end table	1785	=end table
1471		1786
1472	=item B<< C<Ps = 9> >> X10 XTerm	1787	=item B<< C<Pm = 9> >> X10 XTerm
1473		1788
1474	=begin table	1789	=begin table
1475		1790
1476	B<< C<h> >> Send Mouse X & Y on button press.	1791	B<< C<h> >> Send Mouse X & Y on button press.
1477	B<< C<l> >> No mouse reporting.	1792	B<< C<l> >> No mouse reporting.
1478		1793
1479	=end table	1794	=end table
1480		1795
1481	=item B<< C<Ps = 25> >>	1796	=item B<< C<Pm = 25> >>
1482		1797
1483	=begin table	1798	=begin table
1484		1799
1485	B<< C<h> >> Visible cursor {cnorm/cvvis}	1800	B<< C<h> >> Visible cursor {cnorm/cvvis}
1486	B<< C<l> >> Invisible cursor {civis}	1801	B<< C<l> >> Invisible cursor {civis}
1487		1802
1488	=end table	1803	=end table
1489		1804
1490	=item B<< C<Ps = 30> >>	1805	=item B<< C<Pm = 30> >>
1491		1806
1492	=begin table	1807	=begin table
1493		1808
1494	B<< C<h> >> scrollBar visisble	1809	B<< C<h> >> scrollBar visisble
1495	B<< C<l> >> scrollBar invisisble	1810	B<< C<l> >> scrollBar invisisble
1496		1811
1497	=end table	1812	=end table
1498		1813
1499	=item B<< C<Ps = 35> >> (B<rxvt>)	1814	=item B<< C<Pm = 35> >> (B<rxvt>)
1500		1815
1501	=begin table	1816	=begin table
1502		1817
1503	B<< C<h> >> Allow XTerm Shift+key sequences	1818	B<< C<h> >> Allow XTerm Shift+key sequences
1504	B<< C<l> >> Disallow XTerm Shift+key sequences	1819	B<< C<l> >> Disallow XTerm Shift+key sequences
1505		1820
1506	=end table	1821	=end table
1507		1822
1508	=item B<< C<Ps = 38> >> I<unimplemented>	1823	=item B<< C<Pm = 38> >> I<unimplemented>
1509		1824
1510	Enter Tektronix Mode (DECTEK)	1825	Enter Tektronix Mode (DECTEK)
1511		1826
1512	=item B<< C<Ps = 40> >>	1827	=item B<< C<Pm = 40> >>
1513		1828
1514	=begin table	1829	=begin table
1515		1830
1516	B<< C<h> >> Allow 80/132 Mode	1831	B<< C<h> >> Allow 80/132 Mode
1517	B<< C<l> >> Disallow 80/132 Mode	1832	B<< C<l> >> Disallow 80/132 Mode
1518		1833
1519	=end table	1834	=end table
1520		1835
1521	=item B<< C<Ps = 44> >> I<unimplemented>	1836	=item B<< C<Pm = 44> >> I<unimplemented>
1522		1837
1523	=begin table	1838	=begin table
1524		1839
1525	B<< C<h> >> Turn On Margin Bell	1840	B<< C<h> >> Turn On Margin Bell
1526	B<< C<l> >> Turn Off Margin Bell	1841	B<< C<l> >> Turn Off Margin Bell
1527		1842
1528	=end table	1843	=end table
1529		1844
1530	=item B<< C<Ps = 45> >> I<unimplemented>	1845	=item B<< C<Pm = 45> >> I<unimplemented>
1531		1846
1532	=begin table	1847	=begin table
1533		1848
1534	B<< C<h> >> Reverse-wraparound Mode	1849	B<< C<h> >> Reverse-wraparound Mode
1535	B<< C<l> >> No Reverse-wraparound Mode	1850	B<< C<l> >> No Reverse-wraparound Mode
1536		1851
1537	=end table	1852	=end table
1538		1853
1539	=item B<< C<Ps = 46> >> I<unimplemented>	1854	=item B<< C<Pm = 46> >> I<unimplemented>
1540		1855
1541	=item B<< C<Ps = 47> >>	1856	=item B<< C<Pm = 47> >>
1542		1857
1543	=begin table	1858	=begin table
1544		1859
1545	B<< C<h> >> Use Alternate Screen Buffer	1860	B<< C<h> >> Use Alternate Screen Buffer
1546	B<< C<l> >> Use Normal Screen Buffer	1861	B<< C<l> >> Use Normal Screen Buffer
1547		1862
1548	=end table	1863	=end table
1549		1864
1550	X<Priv66>	1865	X<Priv66>
1551		1866
1552	=item B<< C<Ps = 66> >>	1867	=item B<< C<Pm = 66> >>
1553		1868
1554	=begin table	1869	=begin table
1555		1870
1556	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>	1871	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1557	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>	1872	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1558		1873
1559	=end table	1874	=end table
1560		1875
1561	=item B<< C<Ps = 67> >>	1876	=item B<< C<Pm = 67> >>
1562		1877
1563	=begin table	1878	=begin table
1564		1879
1565	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>	1880	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1566	B<< C<l> >> Backspace key sends B<< C<DEL> >>	1881	B<< C<l> >> Backspace key sends B<< C<DEL> >>
1567		1882
1568	=end table	1883	=end table
1569		1884
1570	=item B<< C<Ps = 1000> >> (X11 XTerm)	1885	=item B<< C<Pm = 1000> >> (X11 XTerm)
1571		1886
1572	=begin table	1887	=begin table
1573		1888
1574	B<< C<h> >> Send Mouse X & Y on button press and release.	1889	B<< C<h> >> Send Mouse X & Y on button press and release.
1575	B<< C<l> >> No mouse reporting.	1890	B<< C<l> >> No mouse reporting.
1576		1891
1577	=end table	1892	=end table
1578		1893
1579	=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented>	1894	=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1580		1895
1581	=begin table	1896	=begin table
1582		1897
1583	B<< C<h> >> Use Hilite Mouse Tracking.	1898	B<< C<h> >> Use Hilite Mouse Tracking.
1584	B<< C<l> >> No mouse reporting.	1899	B<< C<l> >> No mouse reporting.
1585		1900
1586	=end table	1901	=end table
1587		1902
1588	=item B<< C<Ps = 1010> >> (B<rxvt>)	1903	=item B<< C<Pm = 1010> >> (B<rxvt>)
1589		1904
1590	=begin table	1905	=begin table
1591		1906
1592	B<< C<h> >> Don't scroll to bottom on TTY output	1907	B<< C<h> >> Don't scroll to bottom on TTY output
1593	B<< C<l> >> Scroll to bottom on TTY output	1908	B<< C<l> >> Scroll to bottom on TTY output
1594		1909
1595	=end table	1910	=end table
1596		1911
1597	=item B<< C<Ps = 1011> >> (B<rxvt>)	1912	=item B<< C<Pm = 1011> >> (B<rxvt>)
1598		1913
1599	=begin table	1914	=begin table
1600		1915
1601	B<< C<h> >> Scroll to bottom when a key is pressed	1916	B<< C<h> >> Scroll to bottom when a key is pressed
1602	B<< C<l> >> Don't scroll to bottom when a key is pressed	1917	B<< C<l> >> Don't scroll to bottom when a key is pressed
1603		1918
1604	=end table	1919	=end table
1605		1920
1606	=item B<< C<Ps = 1021> >> (B<rxvt>)	1921	=item B<< C<Pm = 1021> >> (B<rxvt>)
1607		1922
1608	=begin table	1923	=begin table
1609		1924
1610	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)	1925	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
1611	B<< C<l> >> Font styles have no effect on intensity (Compile styles)	1926	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1612		1927
1613	=end table	1928	=end table
1614		1929
1615	=item B<< C<Ps = 1047> >>	1930	=item B<< C<Pm = 1047> >>
1616		1931
1617	=begin table	1932	=begin table
1618		1933
1619	B<< C<h> >> Use Alternate Screen Buffer	1934	B<< C<h> >> Use Alternate Screen Buffer
1620	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it	1935	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1621		1936
1622	=end table	1937	=end table
1623		1938
1624	=item B<< C<Ps = 1048> >>	1939	=item B<< C<Pm = 1048> >>
1625		1940
1626	=begin table	1941	=begin table
1627		1942
1628	B<< C<h> >> Save cursor position	1943	B<< C<h> >> Save cursor position
1629	B<< C<l> >> Restore cursor position	1944	B<< C<l> >> Restore cursor position
1630		1945
1631	=end table	1946	=end table
1632		1947
1633	=item B<< C<Ps = 1049> >>	1948	=item B<< C<Pm = 1049> >>
1634		1949
1635	=begin table	1950	=begin table
1636		1951
1637	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it	1952	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1638	B<< C<l> >> Use Normal Screen Buffer	1953	B<< C<l> >> Use Normal Screen Buffer
…		…
1643		1958
1644	=back	1959	=back
1645		1960
1646	X<XTerm>	1961	X<XTerm>
1647		1962
1648	=head1 XTerm Operating System Commands	1963	=head2 XTerm Operating System Commands
1649		1964
1650	=over 4	1965	=over 4
1651		1966
1652	=item B<< C<ESC ] Ps;Pt ST> >>	1967	=item B<< C<ESC ] Ps;Pt ST> >>
1653		1968
…		…
1674	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1989	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1675	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	1990	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1676	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> >>	1991	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> >>
1677	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1992	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1678	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).	1993	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).
		1994	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>.
1679	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1995	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1680	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	1996	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1681	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>	1997	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
1682	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>	1998	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1683	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1999	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
…		…
1690		2006
1691	=end table	2007	=end table
1692		2008
1693	=back	2009	=back
1694		2010
1695	X<XPM>
1696
1697	=head1 XPM	2011	=head1 XPM
1698		2012
1699	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	2013	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1700	of B<< C<Pt> >> can be the name of the background pixmap followed by a	2014	of B<< C<Pt> >> can be the name of the background pixmap followed by a
1701	sequence of scaling/positioning commands separated by semi-colons. The	2015	sequence of scaling/positioning commands separated by semi-colons. The
…		…
1798	=begin table	2112	=begin table
1799		2113
1800	4 Shift	2114	4 Shift
1801	8 Meta	2115	8 Meta
1802	16 Control	2116	16 Control
1803	32 Double Click I<(Rxvt extension)>	2117	32 Double Click I<(rxvt extension)>
1804		2118
1805	=end table	2119	=end table
1806		2120
1807	Col = B<< C<< <x> - SPACE >> >>	2121	Col = B<< C<< <x> - SPACE >> >>
1808		2122
…		…
1946	alternative input methods (e.g. kinput2) and will also correctly	2260	alternative input methods (e.g. kinput2) and will also correctly
1947	set up the input for people using dead keys or compose keys.	2261	set up the input for people using dead keys or compose keys.
1948		2262
1949	=item --enable-unicode3 (default: off)	2263	=item --enable-unicode3 (default: off)
1950		2264
		2265	Recommended to stay off unless you really need non-BMP characters.
		2266
1951	Enable direct support for displaying unicode codepoints above	2267	Enable direct support for displaying unicode codepoints above
1952	65535 (the basic multilingual page). This increases storage	2268	65535 (the basic multilingual page). This increases storage
1953	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2269	requirements per character from 2 to 4 bytes. X11 fonts do not yet
1954	support these extra characters, but Xft does.	2270	support these extra characters, but Xft does.
1955		2271
…		…
1965	composite characters. This is required for proper viewing of text	2281	composite characters. This is required for proper viewing of text
1966	where accents are encoded as seperate unicode characters. This is	2282	where accents are encoded as seperate unicode characters. This is
1967	done by using precomposited characters when available or creating	2283	done by using precomposited characters when available or creating
1968	new pseudo-characters when no precomposed form exists.	2284	new pseudo-characters when no precomposed form exists.
1969		2285
1970	Without --enable-unicode3, the number of additional precomposed characters	2286	Without --enable-unicode3, the number of additional precomposed
1971	is rather limited (2048, if this is full, rxvt-unicode will use the	2287	characters is somewhat limited (the 6400 private use characters will be
1972	private use area, extending the number of combinations to 8448). With
1973	--enable-unicode3, no practical limit exists.	2288	(ab-)used). With --enable-unicode3, no practical limit exists.
1974		2289
1975	This option will also enable storage (but not display) of characters	2290	This option will also enable storage (but not display) of characters
1976	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2291	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1977		2292
1978	The combining table also contains entries for arabic presentation forms,	2293	The combining table also contains entries for arabic presentation forms,
1979	but these are not currently used. Bug me if you want these to be used (and	2294	but these are not currently used. Bug me if you want these to be used (and
1980	tell me how these are to be used...).	2295	tell me how these are to be used...).
1981		2296
1982	=item --enable-fallback(=CLASS) (default: Rxvt)	2297	=item --enable-fallback(=CLASS) (default: Rxvt)
1983		2298
1984	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.	2299	When reading resource settings, also read settings for class CLASS. To
		2300	disable resource fallback use --disable-fallback.
1985		2301
1986	=item --with-res-name=NAME (default: urxvt)	2302	=item --with-res-name=NAME (default: urxvt)
1987		2303
1988	Use the given name as default application name when	2304	Use the given name as default application name when
1989	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2305	reading resources. Specify --with-res-name=rxvt to replace rxvt.
…		…
2079		2395
2080	MWM-hints	2396	MWM-hints
2081	EWMH-hints (pid, utf8 names) and protocols (ping)	2397	EWMH-hints (pid, utf8 names) and protocols (ping)
2082	seperate underline colour (-underlineColor)	2398	seperate underline colour (-underlineColor)
2083	settable border widths and borderless switch (-w, -b, -bl)	2399	settable border widths and borderless switch (-w, -b, -bl)
		2400	visual depth selection (-depth)
2084	settable extra linespacing /-lsp)	2401	settable extra linespacing /-lsp)
2085	iso-14755-2 and -3, and visual feedback	2402	iso-14755-2 and -3, and visual feedback
2086	backindex and forwardindex escape sequence
2087	window op and some xterm/OSC escape sequences
2088	tripleclickwords (-tcw)	2403	tripleclickwords (-tcw)
2089	settable insecure mode (-insecure)	2404	settable insecure mode (-insecure)
2090	keysym remapping support	2405	keysym remapping support
2091	cursor blinking and underline cursor (-cb, -uc)	2406	cursor blinking and underline cursor (-cb, -uc)
2092	XEmbed support (-embed)	2407	XEmbed support (-embed)
2093	user-pty (-pty-fd)	2408	user-pty (-pty-fd)
2094	hold on exit (-hold)	2409	hold on exit (-hold)
2095	skip builtin block graphics (-sbg)	2410	skip builtin block graphics (-sbg)
		2411	separate highlightcolor support (-hc)
		2412
		2413	It also enables some non-essential features otherwise disabled, such as:
		2414
		2415	some round-trip time optimisations
		2416	nearest color allocation on pseudocolor screens
		2417	UTF8_STRING supporr for selection
2096	sgr modes 90..97 and 100..107	2418	sgr modes 90..97 and 100..107
		2419	backindex and forwardindex escape sequences
		2420	view change/zero scorllback esacpe sequences
		2421	locale switching escape sequence
		2422	window op and some xterm/OSC escape sequences
		2423	rectangular selections
		2424	trailing space removal for selections
		2425	verbose X error handling
2097		2426
2098	=item --enable-iso14755 (default: on)	2427	=item --enable-iso14755 (default: on)
2099		2428
2100	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2429	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2101	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2430	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2122	Remove support for mouse selection style like that of xterm.	2451	Remove support for mouse selection style like that of xterm.
2123		2452
2124	=item --enable-dmalloc (default: off)	2453	=item --enable-dmalloc (default: off)
2125		2454
2126	Use Gray Watson's malloc - which is good for debugging See	2455	Use Gray Watson's malloc - which is good for debugging See
2127	http://www.letters.com/dmalloc/ for details If you use either this or the	2456	L<http://www.letters.com/dmalloc/> for details If you use either this or the
2128	next option, you may need to edit src/Makefile after compiling to point	2457	next option, you may need to edit src/Makefile after compiling to point
2129	DINCLUDE and DLIB to the right places.	2458	DINCLUDE and DLIB to the right places.
2130		2459
2131	You can only use either this option and the following (should	2460	You can only use either this option and the following (should
2132	you use either) .	2461	you use either) .
…		…
2144		2473
2145	=item --enable-pointer-blank (default: on)	2474	=item --enable-pointer-blank (default: on)
2146		2475
2147	Add support to have the pointer disappear when typing or inactive.	2476	Add support to have the pointer disappear when typing or inactive.
2148		2477
2149	=item --enable-perl (default: off)	2478	=item --enable-perl (default: on)
2150		2479
2151	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>	2480	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2152	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files	2481	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
2153	in F<src/perl-ext/> for the extensions that are installed by default. The	2482	in F<src/perl-ext/> for the extensions that are installed by default. The
2154	perl interpreter that is used can be specified via the C<PERL> environment	2483	perl interpreter that is used can be specified via the C<PERL> environment

Diff Legend

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