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.100 by root, Tue Jan 31 01:00:49 2006 UTC vs.
Revision 1.127 by root, Mon Apr 30 20:06:23 2007 UTC

…		…
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is also available on the World Wide Web at	21	The newest version of this document is also available on the World Wide Web at
22	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://cvs.schmorp.de/browse/rxvt-unicode/doc/rxvt.7.html>.
23		23
24	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
25		25
26	=head2 The new selection selects pieces that are too big, how can I select
27	single words?
28		26
29	If you want to select e.g. alphanumeric words, you can use the following	27	=head2 Meta, Features & Commandline Issues
30	setting:
31		28
32	URxvt.selection.pattern-0: ([[:word:]]+)	29	=head3 My question isn't answered here, can I ask a human?
33		30
34	If you click more than twice, the selection will be extended	31	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
35	more and more.	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	To get a selection that is very similar to the old code, try this pattern:	35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
38		36
39	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)	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:
40		40
41	Please also note that the I<LeftClick Shift-LeftClik> combination also	41	@@URXVT_NAME@@ -pe tabbed
42	selects words like the old code.
43		42
44	=head2 I don't like the new selection/popups/hotkeys/perl, how do I
45	change/disable it?
46
47	You can disable the perl extension completely by setting the
48	B<perl-ext-common> resource to the empty string, which also keeps
49	rxvt-unicode from initialising perl, saving memory.
50
51	If you only want to disable specific features, you first have to
52	identify which perl extension is responsible. For this, read the section
53	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For
54	example, to disable the B<selection-popup> and B<option-popup>, specify
55	this B<perl-ext-common> resource:
56
57	URxvt.perl-ext-common: default,-selection-popup,-option-popup
58
59	This will keep the default extensions, but disable the two popup
60	extensions. Some extensions can also be configured, for example,
61	scrollback search mode is triggered by B<M-s>. You can move it to any
62	other combination either by setting the B<searchable-scrollback> resource:
63
64	URxvt.searchable-scrollback: CM-s
65
66	=head3 The cursor moves when selecting text in the current input line, how
67	do I switch this off?
68
69	See next entry.
70
71	=head2 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor
72	outputs strange escape sequences, how do I fix this?
73
74	These are caused by the C<readline> perl extension. Under normal
75	circumstances, it will move your cursor around when you click into the
76	line that contains it. It tries hard not to do this at the wrong moment,
77	but when running a program that doesn't parse cursor movements or in some
78	cases during rlogin sessions, it fails to detect this properly.
79
80	You can permamently switch this feature off by disabling the C<readline>
81	extension:
82
83	URxvt.perl-ext-common: default,-readline	43	URxvt.perl-ext-common: default,tabbed
84		44
85	=head2 Why doesn't rxvt-unicode read my resources?	45	It will also work fine with tabbing functionality of many window managers
		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.
86		50
87	Well, why, indeed? It does, in a way very similar to other X	51	=head3 How do I know which rxvt-unicode version I'm using?
88	applications. Most importantly, this means that if you or your OS loads
89	resources into the X display (the right way to do it), rxvt-unicode will
90	ignore any resource files in your home directory. It will only read
91	F<$HOME/.Xdefaults> when no resources are attached to the display.
92		52
93	If you have or use an F<$HOME/.Xresources> file, chances are that	53	The version number is displayed with the usage (-h). Also the escape
94	resources are loaded into your X-server. In this case, you have to	54	sequence C<ESC [ 8 n> sets the window title to the version number. When
95	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).	55	using the @@URXVT_NAME@@c client, the version displayed is that of the
		56	daemon.
96		57
97	Also consider the form resources have to use:	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
98		59
99	URxvt.resource: value	60	Rxvt-unicode tries to obey the rule of not charging you for something you
		61	don't use. One thing you should try is to configure out all settings that
		62	you don't need, for example, Xft support is a resource hog by design,
		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.
100		65
101	If you want to use another form (there are lots of different ways of	66	Also, many people (me included) like large windows and even larger
102	specifying resources), make sure you understand wether and why it	67	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
103	works. If unsure, use the form above.	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.
104		72
105	=head2 I can't get transparency working, what am I doing wrong?	73	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
106		74
107	First of all, transparency isn't officially supported in rxvt-unicode, so	75	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
108	you are mostly on your own. Do not bug the author about it (but you may	76	display, create the listening socket and then fork.
109	bug everybody else). Also, if you can't get it working consider it a rite
110	of passage: ... and you failed.
111		77
112	Here are four ways to get transparency. B<Do> read the manpage and option	78	=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c?
113	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
114		79
115	1. Use inheritPixmap:	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:
116		82
117	Esetroot wallpaper.jpg	83	#!/bin/sh
118	@@RXVT_NAME@@ -ip -tint red -sh 40	84	@@URXVT_NAME@@c "$@"
		85	if [ $? -eq 2 ]; then
		86	@@URXVT_NAME@@d -q -o -f
		87	@@URXVT_NAME@@c "$@"
		88	fi
119		89
120	That works. If you think it doesn't, you lack transparency and tinting	90	This tries to create a new terminal, and if fails with exit status 2,
121	support, or you are unable to read.	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.
122		94
123	2. Use a simple pixmap and emulate pseudo-transparency. This enables you	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.
124	to use effects other than tinting and shading: Just shade/tint/whatever
125	your picture with gimp:
126		96
127	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	97	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
128	@@RXVT_NAME@@ -pixmap background.xpm -pe automove-background	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.
129		101
130	That works. If you think it doesn't, you lack XPM and Perl support, or you	102	=head3 How do I set the correct, full IP address for the DISPLAY variable?
131	are unable to read.
132		103
133	3. Use an ARGB visual:	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.
134		110
135	@@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc	111	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		112	snippets:
136		113
137	This requires XFT support, and the support of your X-server. If that	114	# Bourne/Korn/POSIX family of shells:
138	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't	115	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
139	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary	116	if [ ${TERM:-foo} = xterm ]; then
140	bugfixes and workarounds for Xft and Xlib to make it work, but that	117	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
141	doesn't mean that your WM has the required kludges in place.	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
142		126
143	4. Use xcompmgr and let it do the job:	127	=head3 How do I compile the manual pages on my own?
144		128
145	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \	129	You need to have a recent version of perl installed as F</usr/bin/perl>,
146	-set _NET_WM_WINDOW_OPACITY 0xc0000000	130	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		131	the doc subdirectory and enter C<make alldoc>.
147		132
148	Then click on a window you want to make transparent. Replace C<0xc0000000>
149	by other values to change the degree of opacity. If it doesn't work and
150	your server crashes, you got to keep the pieces.
151
152	=head2 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?
153		134
154	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
155	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
156	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
157	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
…		…
161		142
162	text data bss drs rss filename	143	text data bss drs rss filename
163	98398 1664 24 15695 1824 rxvt --disable-everything	144	98398 1664 24 15695 1824 rxvt --disable-everything
164	188985 9048 66616 18222 1788 urxvt --disable-everything	145	188985 9048 66616 18222 1788 urxvt --disable-everything
165		146
166	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
167	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
168	libc), the two diverge, but not unreasnobaly so.	149	libc), the two diverge, but not unreasonably so.
169		150
170	text data bss drs rss filename	151	text data bss drs rss filename
171	163431 2152 24 20123 2060 rxvt --enable-everything	152	163431 2152 24 20123 2060 rxvt --enable-everything
172	1035683 49680 66648 29096 3680 urxvt --enable-everything	153	1035683 49680 66648 29096 3680 urxvt --enable-everything
173		154
…		…
189	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
190	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
191	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
192	extremely well *g*.	173	extremely well *g*.
193		174
194	=head2 Why C++, isn't that unportable/bloated/uncool?	175	=head3 Why C++, isn't that unportable/bloated/uncool?
195		176
196	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
197	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
198	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
199	shorter: It simply wouldn't exist without C++.	180	shorter: It simply wouldn't exist without C++.
…		…
223	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
224		205
225	No large bloated libraries (of course, none were linked in statically),	206	No large bloated libraries (of course, none were linked in statically),
226	except maybe libX11 :)	207	except maybe libX11 :)
227		208
228	=head2 Does it support tabs, can I have a tabbed rxvt-unicode?
229		209
230	Beginning with version 7.3, there is a perl extension that implements a	210	=head2 Rendering, Font & Look and Feel Issues
231	simple tabbed terminal. It is installed by default, so any of these should
232	give you tabs:
233		211
234	@@RXVT_NAME@@ -pe tabbed	212	=head3 I can't get transparency working, what am I doing wrong?
235		213
		214	First of all, transparency isn't officially supported in rxvt-unicode, so
		215	you are mostly on your own. Do not bug the author about it (but you may
		216	bug everybody else). Also, if you can't get it working consider it a rite
		217	of passage: ... and you failed.
		218
		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!
		221
		222	1. Use inheritPixmap:
		223
		224	Esetroot wallpaper.jpg
		225	@@URXVT_NAME@@ -ip -tint red -sh 40
		226
		227	That works. If you think it doesn't, you lack transparency and tinting
		228	support, or you are unable to read.
		229
		230	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		231	to use effects other than tinting and shading: Just shade/tint/whatever
		232	your picture with gimp or any other tool:
		233
		234	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		235	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
		236
		237	That works. If you think it doesn't, you lack XPM and Perl support, or you
		238	are unable to read.
		239
		240	3. Use an ARGB visual:
		241
		242	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		243
		244	This requires XFT support, and the support of your X-server. If that
		245	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		246	there yet, no matter what they claim. Rxvt-Unicode contains the necessary
		247	bugfixes and workarounds for Xft and Xlib to make it work, but that
		248	doesn't mean that your WM has the required kludges in place.
		249
		250	4. Use xcompmgr and let it do the job:
		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
236	URxvt.perl-ext-common: default,tabbed	520	URxvt.perl-ext-common: default,-readline
237		521
238	It will also work fine with tabbing functionality of many window managers	522	=head3 My numerical keypad acts weird and generates differing output?
239	or similar tabbing programs, and its embedding-features allow it to be
240	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
241	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
242	(murxvt) terminal as an example embedding application.
243		523
244	=head2 How do I know which rxvt-unicode version I'm using?	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.
245		530
246	The version number is displayed with the usage (-h). Also the escape	531	=head3 My Compose (Multi_key) key is no longer working.
247	sequence C<ESC [ 8 n> sets the window title to the version number. When
248	using the @@RXVT_NAME@@c client, the version displayed is that of the
249	daemon.
250		532
251	=head2 I am using Debian GNU/Linux and have a problem...	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.
252		539
253	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	540	In this case either do not specify a B<preeditStyle> or specify more than
254	patches that considerably change the behaviour of rxvt-unicode (but	541	one pre-edit style, such as B<OverTheSpot,Root,None>.
255	unfortunately this notice has been removed). Before reporting a bug to
256	the original rxvt-unicode author please download and install the genuine
257	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
258	the problem. If you cannot, chances are that the problems are specific to
259	Debian GNU/Linux, in which case it should be reported via the Debian Bug
260	Tracking System (use C<reportbug> to report the bug).
261		542
262	For other problems that also affect the Debian package, you can and	543	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
263	probably should use the Debian BTS, too, because, after all, it's also a
264	bug in the Debian version and it serves as a reminder for other users that
265	might encounter the same issue.
266		544
267	=head2 I am maintaining rxvt-unicode for distribution/OS XXX, any	545	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
268	recommendation?	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.
269		550
270	You should build one binary with the default options. F<configure>	551	=head3 Mouse cut/paste suddenly no longer works.
271	now enables most useful options, and the trend goes to making them
272	runtime-switchable, too, so there is usually no drawback to enbaling them,
273	except higher disk and possibly memory usage. The perl interpreter should
274	be enabled, as important functionality (menus, selection, likely more in
275	the future) depends on it.
276		552
277	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	553	Make sure that mouse reporting is actually turned off since killing
278	system-wide (except maybe with C<defaults>). This will result in useful	554	some editors prematurely may leave the mouse in mouse report mode. I've
279	behaviour. If your distribution aims at low memory, add an empty	555	heard that tcsh may use mouse reporting unless it otherwise specified. A
280	C<perl-ext-common> resource to the app-defaults file. This will keep the	556	quick check is to see if cut/paste works when the Alt or Shift keys are
281	perl interpreter disabled until the user enables it.	557	depressed.
282		558
283	If you can/want build more binaries, I recommend building a minimal	559	=head3 What's with the strange Backspace/Delete key behaviour?
284	one with C<--disable-everything> (very useful) and a maximal one with
285	C<--enable-everything> (less useful, it will be very big due to a lot of
286	encodings built-in that increase download times and are rarely used).
287		560
288	=head2 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	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<^?>.
289		565
290	It should be, starting with release 7.1. You are encouraged to properly	566	Historically, either value is correct, but rxvt-unicode adopts the debian
291	install urxvt with privileges necessary for your OS now.	567	policy of using C<^?> when unsure, because it's the one and only correct
		568	choice :).
292		569
293	When rxvt-unicode detects that it runs setuid or setgid, it will fork	570	Rxvt-unicode tries to inherit the current stty settings and uses the value
294	into a helper process for privileged operations (pty handling on some	571	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
295	systems, utmp/wtmp/lastlog handling on others) and drop privileges	572	started from a terminal (say, from a menu or by remote shell), then the
296	immediately. This is much safer than most other terminals that keep	573	system value of `erase', which corresponds to CERASE in <termios.h>, will
297	privileges while running (but is more relevant to urxvt, as it contains	574	be used (which may not be the same as your stty setting).
298	things as perl interpreters, which might be "helpful" to attackers).
299		575
300	This forking is done as the very first within main(), which is very early	576	For starting a new rxvt-unicode:
301	and reduces possible bugs to initialisation code run before main(), or
302	things like the dynamic loader of your system, which should result in very
303	little risk.
304		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
305	=head2 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?
306		838
307	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
308	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).
309		841
310	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
311	be done like this (with ncurses' infocmp):	843	be done like this (with ncurses' infocmp and works as user and admin):
312		844
313	REMOTE=remotesystem.domain	845	REMOTE=remotesystem.domain
314	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"
315		847
316	... 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.
317		852
318	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
319	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
320	problems arising, which includes wrong keymapping, less and different	855	problems arising, which includes wrong keymapping, less and different
321	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
…		…
326	resource to set it:	861	resource to set it:
327		862
328	URxvt.termName: rxvt	863	URxvt.termName: rxvt
329		864
330	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
331	the rxvt terminfo file with the rxvt-unicode one.	866	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
332		867
333	=head2 C<tic> outputs some error when compiling the terminfo entry.	868	=head3 C<tic> outputs some error when compiling the terminfo entry.
334		869
335	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
336	C<enacs=\E[0@> and try again.	871	C<enacs=\E[0@> and try again.
337		872
338	=head2 C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	873	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
339		874
340	See next entry.	875	See next entry.
341		876
342	=head2 I need a termcap file entry.	877	=head3 I need a termcap file entry.
343		878
344	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
345	systems still compile some programs using the long-obsoleted termcap	880	systems still compile some programs using the long-obsoleted termcap
346	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
347	for C<rxvt-unicode>.	882	for C<rxvt-unicode>.
348		883
349	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.
350	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
351	like this:	886	like this:
352		887
353	infocmp -C rxvt-unicode	888	infocmp -C rxvt-unicode
354		889
…		…
373	: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:\
374	: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:\
375	: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:\
376	:vs=\E[?25h:	911	:vs=\E[?25h:
377		912
378	=head2 Why does C<ls> no longer have coloured output?	913	=head3 Why does C<ls> no longer have coloured output?
379		914
380	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
381	decide wether a terminal has colour, but uses it's own configuration	916	decide whether a terminal has colour, but uses its own configuration
382	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
383	with most other terminals supporting colour). Either add:	918	with most other terminals supporting colour). Either add:
384		919
385	TERM rxvt-unicode	920	TERM rxvt-unicode
386		921
387	to C</etc/DIR_COLORS> or simply add:	922	to C</etc/DIR_COLORS> or simply add:
388		923
389	alias ls='ls --color=auto'	924	alias ls='ls --color=auto'
390		925
391	to your C<.profile> or C<.bashrc>.	926	to your C<.profile> or C<.bashrc>.
392		927
393	=head2 Why doesn't vim/emacs etc. use the 88 colour mode?	928	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
394		929
395	See next entry.	930	See next entry.
396		931
397	=head2 Why doesn't vim/emacs etc. make use of italic?	932	=head3 Why doesn't vim/emacs etc. make use of italic?
398		933
399	See next entry.	934	See next entry.
400		935
401	=head2 Why are the secondary screen-related options not working properly?	936	=head3 Why are the secondary screen-related options not working properly?
402		937
403	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
404	distributions (most notably Debian GNU/Linux) break rxvt-unicode	939	distributions (most notably Debian GNU/Linux) break rxvt-unicode
405	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
406	features. Unfortunately, some of these (most notably, again, Debian	941	features. Unfortunately, some of these (most notably, again, Debian
407	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
408	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
409	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
410	how to do this).	945	how to do this).
411		946
412	=head2 My numerical keypad acts weird and generates differing output?
413		947
414	Some Debian GNUL/Linux users seem to have this problem, although no	948	=head2 Encoding / Locale / Input Method Issues
415	specific details were reported so far. It is possible that this is caused
416	by the wrong C<TERM> setting, although the details of wether and how
417	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
418	keymap. See the answer to the previous question, and please report if that
419	helped.
420		949
421	=head2 Rxvt-unicode does not seem to understand the selected encoding?	950	=head3 Rxvt-unicode does not seem to understand the selected encoding?
422		951
423	See next entry.	952	See next entry.
424		953
425	=head2 Unicode does not seem to work?	954	=head3 Unicode does not seem to work?
426		955
427	If you encounter strange problems like typing an accented character but	956	If you encounter strange problems like typing an accented character but
428	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
429	subtly garbled, then you should check your locale settings.	958	subtly garbled, then you should check your locale settings.
430		959
431	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	960	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
432	programs. Often rxvt-unicode is started in the C<C> locale, while the	961	programs running in it. Often rxvt-unicode is started in the C<C> locale,
433	login script running within the rxvt-unicode window changes the locale to	962	while the login script running within the rxvt-unicode window changes the
434	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.	963	locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is
		964	not going to work, and is the most common cause for problems.
435		965
436	The best thing is to fix your startup environment, as you will likely run	966	The best thing is to fix your startup environment, as you will likely run
437	into other problems. If nothing works you can try this in your .profile.	967	into other problems. If nothing works you can try this in your .profile.
438		968
439	printf '\e]701;%s\007' "$LC_CTYPE"	969	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
440		970
441	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	971	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
442	supported on your systems. Some systems have a C<locale> command which	972	supported on your systems. Some systems have a C<locale> command which
443	displays this (also, C<perl -e0> can be used to check locale settings, as	973	displays this (also, C<perl -e0> can be used to check locale settings, as
444	it will complain loudly if it cannot set the locale). If it displays something	974	it will complain loudly if it cannot set the locale). If it displays something
…		…
450		980
451	If nothing works and you are sure that everything is set correctly then	981	If nothing works and you are sure that everything is set correctly then
452	you will need to remember a little known fact: Some programs just don't	982	you will need to remember a little known fact: Some programs just don't
453	support locales :(	983	support locales :(
454		984
455	=head2 Why do some characters look so much different than others?	985	=head3 How does rxvt-unicode determine the encoding to use?
456		986
457	See next entry.	987	See next entry.
458		988
459	=head2 How does rxvt-unicode choose fonts?	989	=head3 Is there an option to switch encodings?
460		990
461	Most fonts do not contain the full range of Unicode, which is	991	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
462	fine. Chances are that the font you (or the admin/package maintainer of	992	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
463	your system/os) have specified does not cover all the characters you want	993	UTF-8 or any other encodings with respect to terminal I/O.
464	to display.
465		994
466	B<rxvt-unicode> makes a best-effort try at finding a replacement	995	The reasons is that there exists a perfectly fine mechanism for selecting
467	font. Often the result is fine, but sometimes the chosen font looks	996	the encoding, doing I/O and (most important) communicating this to all
468	bad/ugly/wrong. Some fonts have totally strange characters that don't	997	applications so everybody agrees on character properties such as width
469	resemble the correct glyph at all, and rxvt-unicode lacks the artificial	998	and code number. This mechanism is the I<locale>. Applications not using
470	intelligence to detect that a specific glyph is wrong: it has to believe	999	that info will have problems (for example, C<xterm> gets the width of
471	the font that the characters it claims to contain indeed look correct.	1000	characters wrong as it uses its own, locale-independent table under all
472
473	In that case, select a font of your taste and add it to the font list,
474	e.g.:
475
476	@@RXVT_NAME@@ -fn basefont,font2,font3...
477
478	When rxvt-unicode sees a character, it will first look at the base
479	font. If the base font does not contain the character, it will go to the
480	next font, and so on. Specifying your own fonts will also speed up this
481	search and use less resources within rxvt-unicode and the X-server.
482
483	The only limitation is that none of the fonts may be larger than the base
484	font, as the base font defines the terminal character cell size, which
485	must be the same due to the way terminals work.
486
487	=head2 Why do some chinese characters look so different than others?
488
489	This is because there is a difference between script and language --
490	rxvt-unicode does not know which language the text that is output is,
491	as it only knows the unicode character codes. If rxvt-unicode first
492	sees a japanese/chinese character, it might choose a japanese font for
493	display. Subsequent japanese characters will use that font. Now, many
494	chinese characters aren't represented in japanese fonts, so when the first
495	non-japanese character comes up, rxvt-unicode will look for a chinese font
496	-- unfortunately at this point, it will still use the japanese font for
497	chinese characters that are also in the japanese font.
498
499	The workaround is easy: just tag a chinese font at the end of your font
500	list (see the previous question). The key is to view the font list as
501	a preference list: If you expect more japanese, list a japanese font
502	first. If you expect more chinese, put a chinese font first.
503
504	In the future it might be possible to switch language preferences at
505	runtime (the internal data structure has no problem with using different
506	fonts for the same character at the same time, but no interface for this
507	has been designed yet).
508
509	Until then, you might get away with switching fonts at runtime (see L<Can
510	I switch the fonts at runtime?> later in this document).
511
512	=head2 Why does rxvt-unicode sometimes leave pixel droppings?
513
514	Most fonts were not designed for terminal use, which means that character
515	size varies a lot. A font that is otherwise fine for terminal use might
516	contain some characters that are simply too wide. Rxvt-unicode will avoid
517	these characters. For characters that are just "a bit" too wide a special
518	"careful" rendering mode is used that redraws adjacent characters.
519
520	All of this requires that fonts do not lie about character sizes,
521	however: Xft fonts often draw glyphs larger than their acclaimed bounding
522	box, and rxvt-unicode has no way of detecting this (the correct way is to
523	ask for the character bounding box, which unfortunately is wrong in these
524	cases).	1001	locales).
525		1002
526	It's not clear (to me at least), wether this is a bug in Xft, freetype,	1003	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
527	or the respective font. If you encounter this problem you might try using	1004	programs doing the same (that is, most) will automatically agree in the
528	the C<-lsp> option to give the font more height. If that doesn't work, you	1005	interpretation of characters.
529	might be forced to use a different font.
530		1006
531	All of this is not a problem when using X11 core fonts, as their bounding	1007	Unfortunately, there is no system-independent way to select locales, nor
532	box data is correct.	1008	is there a standard on how locale specifiers will look like.
533		1009
		1010	On most systems, the content of the C<LC_CTYPE> environment variable
		1011	contains an arbitrary string which corresponds to an already-installed
		1012	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1013	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1014	(i.e. C<de> or C<german>) are also common.
		1015
		1016	Rxvt-unicode ignores all other locale categories, and except for
		1017	the encoding, ignores country or language-specific settings,
		1018	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		1019	rxvt-unicode.
		1020
		1021	If you want to use a specific encoding you have to make sure you start
		1022	rxvt-unicode with the correct C<LC_CTYPE> category.
		1023
		1024	=head3 Can I switch locales at runtime?
		1025
		1026	Yes, using an escape sequence. Try something like this, which sets
		1027	rxvt-unicode's idea of C<LC_CTYPE>.
		1028
		1029	printf '\33]701;%s\007' ja_JP.SJIS
		1030
		1031	See also the previous answer.
		1032
		1033	Sometimes this capability is rather handy when you want to work in
		1034	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		1035	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		1036	first switches to a locale supported by xjdic and back later:
		1037
		1038	printf '\33]701;%s\007' ja_JP.SJIS
		1039	xjdic -js
		1040	printf '\33]701;%s\007' de_DE.UTF-8
		1041
		1042	You can also use xterm's C<luit> program, which usually works fine, except
		1043	for some locales where character width differs between program- and
		1044	rxvt-unicode-locales.
		1045
		1046	=head3 I have problems getting my input method working.
		1047
		1048	Try a search engine, as this is slightly different for every input method server.
		1049
		1050	Here is a checklist:
		1051
		1052	=over 4
		1053
		1054	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		1055
		1056	Try C<locale -a> or check the documentation for your OS.
		1057
		1058	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		1059
		1060	For example, B<kinput2> does not support UTF-8 locales, you should use
		1061	C<ja_JP.EUC-JP> or equivalent.
		1062
		1063	=item - Make sure your XIM server is actually running.
		1064
		1065	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		1066
		1067	When you want to use e.g. B<kinput2>, it must be set to
		1068	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
		1069	method servers are running with this command:
		1070
		1071	xprop -root XIM_SERVERS
		1072
		1073	=item
		1074
		1075	=back
		1076
		1077	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		1078
		1079	You can specify separate locales for the input method and the rest of the
		1080	terminal, using the resource C<imlocale>:
		1081
		1082	URxvt.imlocale: ja_JP.EUC-JP
		1083
		1084	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1085	use your input method. Please note, however, that, depending on your Xlib
		1086	version, you may not be able to input characters outside C<EUC-JP> in a
		1087	normal way then, as your input method limits you.
		1088
		1089	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		1090
		1091	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1092	design. Applications can avoid some crashes at the expense of memory
		1093	leaks, and Input Methods can avoid some crashes by careful ordering at
		1094	exit time. B<kinput2> (and derived input methods) generally succeeds,
		1095	while B<SCIM> (or similar input methods) fails. In the end, however,
		1096	crashes cannot be completely avoided even if both sides cooperate.
		1097
		1098	So the only workaround is not to kill your Input Method Servers.
		1099
		1100
		1101	=head2 Operating Systems / Package Maintaining
		1102
		1103	=head3 I am using Debian GNU/Linux and have a problem...
		1104
		1105	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1106	patches that considerably change the behaviour of rxvt-unicode (but
		1107	unfortunately this notice has been removed). Before reporting a bug to
		1108	the original rxvt-unicode author please download and install the genuine
		1109	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1110	the problem. If you cannot, chances are that the problems are specific to
		1111	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1112	Tracking System (use C<reportbug> to report the bug).
		1113
		1114	For other problems that also affect the Debian package, you can and
		1115	probably should use the Debian BTS, too, because, after all, it's also a
		1116	bug in the Debian version and it serves as a reminder for other users that
		1117	might encounter the same issue.
		1118
		1119	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1120
		1121	You should build one binary with the default options. F<configure>
		1122	now enables most useful options, and the trend goes to making them
		1123	runtime-switchable, too, so there is usually no drawback to enabling them,
		1124	except higher disk and possibly memory usage. The perl interpreter should
		1125	be enabled, as important functionality (menus, selection, likely more in
		1126	the future) depends on it.
		1127
		1128	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		1129	system-wide (except maybe with C<defaults>). This will result in useful
		1130	behaviour. If your distribution aims at low memory, add an empty
		1131	C<perl-ext-common> resource to the app-defaults file. This will keep the
		1132	perl interpreter disabled until the user enables it.
		1133
		1134	If you can/want build more binaries, I recommend building a minimal
		1135	one with C<--disable-everything> (very useful) and a maximal one with
		1136	C<--enable-everything> (less useful, it will be very big due to a lot of
		1137	encodings built-in that increase download times and are rarely used).
		1138
		1139	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1140
		1141	It should be, starting with release 7.1. You are encouraged to properly
		1142	install urxvt with privileges necessary for your OS now.
		1143
		1144	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1145	into a helper process for privileged operations (pty handling on some
		1146	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1147	immediately. This is much safer than most other terminals that keep
		1148	privileges while running (but is more relevant to urxvt, as it contains
		1149	things as perl interpreters, which might be "helpful" to attackers).
		1150
		1151	This forking is done as the very first within main(), which is very early
		1152	and reduces possible bugs to initialisation code run before main(), or
		1153	things like the dynamic loader of your system, which should result in very
		1154	little risk.
		1155
534	=head2 On Solaris 9, many line-drawing characters are too wide.	1156	=head3 On Solaris 9, many line-drawing characters are too wide.
535		1157
536	Seems to be a known bug, read	1158	Seems to be a known bug, read
537	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1159	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
538	following ugly workaround to get non-double-wide-characters working:	1160	following ugly workaround to get non-double-wide-characters working:
539		1161
540	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1162	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
541		1163
542	=head2 My Compose (Multi_key) key is no longer working.
543
544	The most common causes for this are that either your locale is not set
545	correctly, or you specified a B<preeditStyle> that is not supported by
546	your input method. For example, if you specified B<OverTheSpot> and
547	your input method (e.g. the default input method handling Compose keys)
548	does not support this (for instance because it is not visual), then
549	rxvt-unicode will continue without an input method.
550
551	In this case either do not specify a B<preeditStyle> or specify more than
552	one pre-edit style, such as B<OverTheSpot,Root,None>.
553
554	=head2 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
555
556	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
557	international keyboards) or simply use ISO 14755 support to your
558	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
559	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
560	character and so on.
561
562	=head2 How can I keep rxvt-unicode from using reverse video so much?
563
564	First of all, make sure you are running with the right terminal settings
565	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
566	make sure you have specified colours for italic and bold, as otherwise
567	rxvt-unicode might use reverse video to simulate the effect:
568
569	URxvt.colorBD: white
570	URxvt.colorIT: green
571
572	=head2 Some programs assume totally weird colours (red instead of blue), how can I fix that?
573
574	For some unexplainable reason, some rare programs assume a very weird
575	colour palette when confronted with a terminal with more than the standard
576	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
577	these programs not to assume non-ISO colours without very good reasons.
578
579	In the meantime, you can either edit your C<rxvt-unicode> terminfo
580	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
581	fix colours but keep you from using other rxvt-unicode features.
582
583	=head2 I am on FreeBSD and rxvt-unicode does not seem to work at all.	1164	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
584		1165
585	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1166	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
586	in your compile environment, or an implementation that implements it,	1167	in your compile environment, or an implementation that implements it,
587	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1168	whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
588	B<wchar_t> is represented as unicode.	1169	B<wchar_t> is represented as unicode.
589		1170
590	As you might have guessed, FreeBSD does neither define this symobl nor	1171	As you might have guessed, FreeBSD does neither define this symbol nor
591	does it support it. Instead, it uses it's own internal representation of	1172	does it support it. Instead, it uses its own internal representation of
592	B<wchar_t>. This is, of course, completely fine with respect to standards.	1173	B<wchar_t>. This is, of course, completely fine with respect to standards.
593		1174
594	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and	1175	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
595	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.	1176	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
596		1177
…		…
610		1191
611	The rxvt-unicode author insists that the right way to fix this is in the	1192	The rxvt-unicode author insists that the right way to fix this is in the
612	system libraries once and for all, instead of forcing every app to carry	1193	system libraries once and for all, instead of forcing every app to carry
613	complete replacements for them :)	1194	complete replacements for them :)
614		1195
615	=head2 I use Solaris 9 and it doesn't compile/work/etc.	1196	=head3 I use Solaris 9 and it doesn't compile/work/etc.
616		1197
617	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1198	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
618	problems with C<wcwidth> and a compile problem.	1199	problems with C<wcwidth> and a compile problem.
619		1200
620	=head2 How can I use rxvt-unicode under cygwin?	1201	=head3 How can I use rxvt-unicode under cygwin?
621		1202
622	rxvt-unicode should compile and run out of the box on cygwin, using	1203	rxvt-unicode should compile and run out of the box on cygwin, using
623	the X11 libraries that come with cygwin. libW11 emulation is no	1204	the X11 libraries that come with cygwin. libW11 emulation is no
624	longer supported (and makes no sense, either, as it only supported a	1205	longer supported (and makes no sense, either, as it only supported a
625	single font). I recommend starting the X-server in C<-multiwindow> or	1206	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
628		1209
629	At the time of this writing, cygwin didn't seem to support any multi-byte	1210	At the time of this writing, cygwin didn't seem to support any multi-byte
630	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1211	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
631	to 8-bit encodings.	1212	to 8-bit encodings.
632		1213
633	=head2 How does rxvt-unicode determine the encoding to use?
634
635	See next entry.
636
637	=head2 Is there an option to switch encodings?
638
639	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
640	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
641	UTF-8 or any other encodings with respect to terminal I/O.
642
643	The reasons is that there exists a perfectly fine mechanism for selecting
644	the encoding, doing I/O and (most important) communicating this to all
645	applications so everybody agrees on character properties such as width
646	and code number. This mechanism is the I<locale>. Applications not using
647	that info will have problems (for example, C<xterm> gets the width of
648	characters wrong as it uses it's own, locale-independent table under all
649	locales).
650
651	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
652	programs doing the same (that is, most) will automatically agree in the
653	interpretation of characters.
654
655	Unfortunately, there is no system-independent way to select locales, nor
656	is there a standard on how locale specifiers will look like.
657
658	On most systems, the content of the C<LC_CTYPE> environment variable
659	contains an arbitrary string which corresponds to an already-installed
660	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
661	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
662	(i.e. C<de> or C<german>) are also common.
663
664	Rxvt-unicode ignores all other locale categories, and except for
665	the encoding, ignores country or language-specific settings,
666	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
667	rxvt-unicode.
668
669	If you want to use a specific encoding you have to make sure you start
670	rxvt-unicode with the correct C<LC_CTYPE> category.
671
672	=head2 Can I switch locales at runtime?
673
674	Yes, using an escape sequence. Try something like this, which sets
675	rxvt-unicode's idea of C<LC_CTYPE>.
676
677	printf '\e]701;%s\007' ja_JP.SJIS
678
679	See also the previous answer.
680
681	Sometimes this capability is rather handy when you want to work in
682	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
683	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
684	first switches to a locale supported by xjdic and back later:
685
686	printf '\e]701;%s\007' ja_JP.SJIS
687	xjdic -js
688	printf '\e]701;%s\007' de_DE.UTF-8
689
690	You can also use xterm's C<luit> program, which usually works fine, except
691	for some locales where character width differs between program- and
692	rxvt-unicode-locales.
693
694	=head2 Can I switch the fonts at runtime?
695
696	Yes, using an escape sequence. Try something like this, which has the same
697	effect as using the C<-fn> switch, and takes effect immediately:
698
699	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
700
701	This is useful if you e.g. work primarily with japanese (and prefer a
702	japanese font), but you have to switch to chinese temporarily, where
703	japanese fonts would only be in your way.
704
705	You can think of this as a kind of manual ISO-2022 switching.
706
707	=head2 Why do italic characters look as if clipped?
708
709	Many fonts have difficulties with italic characters and hinting. For
710	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
711	Mono> completely fails in it's italic face. A workaround might be to
712	enable freetype autohinting, i.e. like this:
713
714	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
715	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
716
717	=head2 My input method wants <some encoding> but I want UTF-8, what can I do?
718
719	You can specify separate locales for the input method and the rest of the
720	terminal, using the resource C<imlocale>:
721
722	URxvt.imlocale: ja_JP.EUC-JP
723
724	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
725	use your input method. Please note, however, that you will not be able to
726	input characters outside C<EUC-JP> in a normal way then, as your input
727	method limits you.
728
729	=head2 Rxvt-unicode crashes when the X Input Method changes or exits.
730
731	Unfortunately, this is unavoidable, as the XIM protocol is racy by
732	design. Applications can avoid some crashes at the expense of memory
733	leaks, and Input Methods can avoid some crashes by careful ordering at
734	exit time. B<kinput2> (and derived input methods) generally succeeds,
735	while B<SCIM> (or similar input methods) fails. In the end, however,
736	crashes cannot be completely avoided even if both sides cooperate.
737
738	So the only workaround is not to kill your Input Method Servers.
739
740	=head2 Rxvt-unicode uses gobs of memory, how can I reduce that?
741
742	Rxvt-unicode tries to obey the rule of not charging you for something you
743	don't use. One thing you should try is to configure out all settings that
744	you don't need, for example, Xft support is a resource hog by design,
745	when used. Compiling it out ensures that no Xft font will be loaded
746	accidentally when rxvt-unicode tries to find a font for your characters.
747
748	Also, many people (me included) like large windows and even larger
749	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
750	6 bytes per screen cell. For a 160x?? window this amounts to almost a
751	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
752	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
753	rxvt-unicode then uses 8 bytes per screen cell.
754
755	=head2 Can I speed up Xft rendering somehow?
756
757	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
758	it is simply slow. If you still want Xft fonts you might try to disable
759	antialiasing (by appending C<:antialias=false>), which saves lots of
760	memory and also speeds up rendering considerably.
761
762	=head2 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
763
764	Rxvt-unicode will use whatever you specify as a font. If it needs to
765	fall back to it's default font search list it will prefer X11 core
766	fonts, because they are small and fast, and then use Xft fonts. It has
767	antialiasing disabled for most of them, because the author thinks they
768	look best that way.
769
770	If you want antialiasing, you have to specify the fonts manually.
771
772	=head2 Mouse cut/paste suddenly no longer works.
773
774	Make sure that mouse reporting is actually turned off since killing
775	some editors prematurely may leave the mouse in mouse report mode. I've
776	heard that tcsh may use mouse reporting unless it otherwise specified. A
777	quick check is to see if cut/paste works when the Alt or Shift keys are
778	depressed.
779
780	=head2 What's with this bold/blink stuff?
781
782	If no bold colour is set via C<colorBD:>, bold will invert text using the
783	standard foreground colour.
784
785	For the standard background colour, blinking will actually make the
786	text blink when compiled with C<--enable-blinking>. with standard
787	colours. Without C<--enable-blinking>, the blink attribute will be
788	ignored.
789
790	On ANSI colours, bold/blink attributes are used to set high-intensity
791	foreground/background colors.
792
793	color0-7 are the low-intensity colors.
794
795	color8-15 are the corresponding high-intensity colors.
796
797	=head2 I don't like the screen colors. How do I change them?
798
799	You can change the screen colors at run-time using F<~/.Xdefaults>
800	resources (or as long-options).
801
802	Here are values that are supposed to resemble a VGA screen,
803	including the murky brown that passes for low-intensity yellow:
804
805	URxvt.color0: #000000
806	URxvt.color1: #A80000
807	URxvt.color2: #00A800
808	URxvt.color3: #A8A800
809	URxvt.color4: #0000A8
810	URxvt.color5: #A800A8
811	URxvt.color6: #00A8A8
812	URxvt.color7: #A8A8A8
813
814	URxvt.color8: #000054
815	URxvt.color9: #FF0054
816	URxvt.color10: #00FF54
817	URxvt.color11: #FFFF54
818	URxvt.color12: #0000FF
819	URxvt.color13: #FF00FF
820	URxvt.color14: #00FFFF
821	URxvt.color15: #FFFFFF
822
823	And here is a more complete set of non-standard colors described (not by
824	me) as "pretty girly".
825
826	URxvt.cursorColor: #dc74d1
827	URxvt.pointerColor: #dc74d1
828	URxvt.background: #0e0e0e
829	URxvt.foreground: #4ad5e1
830	URxvt.color0: #000000
831	URxvt.color8: #8b8f93
832	URxvt.color1: #dc74d1
833	URxvt.color9: #dc74d1
834	URxvt.color2: #0eb8c7
835	URxvt.color10: #0eb8c7
836	URxvt.color3: #dfe37e
837	URxvt.color11: #dfe37e
838	URxvt.color5: #9e88f0
839	URxvt.color13: #9e88f0
840	URxvt.color6: #73f7ff
841	URxvt.color14: #73f7ff
842	URxvt.color7: #e1dddd
843	URxvt.color15: #e1dddd
844
845	=head2 How can I start @@RXVT_NAME@@d in a race-free way?
846
847	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
848	display, create the listening socket and then fork.
849
850	=head2 What's with the strange Backspace/Delete key behaviour?
851
852	Assuming that the physical Backspace key corresponds to the
853	BackSpace keysym (not likely for Linux ... see the following
854	question) there are two standard values that can be used for
855	Backspace: C<^H> and C<^?>.
856
857	Historically, either value is correct, but rxvt-unicode adopts the debian
858	policy of using C<^?> when unsure, because it's the one only only correct
859	choice :).
860
861	Rxvt-unicode tries to inherit the current stty settings and uses the value
862	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
863	started from a terminal (say, from a menu or by remote shell), then the
864	system value of `erase', which corresponds to CERASE in <termios.h>, will
865	be used (which may not be the same as your stty setting).
866
867	For starting a new rxvt-unicode:
868
869	# use Backspace = ^H
870	$ stty erase ^H
871	$ @@RXVT_NAME@@
872
873	# use Backspace = ^?
874	$ stty erase ^?
875	$ @@RXVT_NAME@@
876
877	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
878
879	For an existing rxvt-unicode:
880
881	# use Backspace = ^H
882	$ stty erase ^H
883	$ echo -n "^[[36h"
884
885	# use Backspace = ^?
886	$ stty erase ^?
887	$ echo -n "^[[36l"
888
889	This helps satisfy some of the Backspace discrepancies that occur, but
890	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
891	properly reflects that.
892
893	The Delete key is a another casualty of the ill-defined Backspace problem.
894	To avoid confusion between the Backspace and Delete keys, the Delete
895	key has been assigned an escape sequence to match the vt100 for Execute
896	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
897
898	Some other Backspace problems:
899
900	some editors use termcap/terminfo,
901	some editors (vim I'm told) expect Backspace = ^H,
902	GNU Emacs (and Emacs-like editors) use ^H for help.
903
904	Perhaps someday this will all be resolved in a consistent manner.
905
906	=head2 I don't like the key-bindings. How do I change them?
907
908	There are some compile-time selections available via configure. Unless
909	you have run "configure" with the C<--disable-resources> option you can
910	use the `keysym' resource to alter the keystrings associated with keysyms.
911
912	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
913
914	URxvt.keysym.Home: \033[1~
915	URxvt.keysym.End: \033[4~
916	URxvt.keysym.C-apostrophe: \033<C-'>
917	URxvt.keysym.C-slash: \033<C-/>
918	URxvt.keysym.C-semicolon: \033<C-;>
919	URxvt.keysym.C-grave: \033<C-`>
920	URxvt.keysym.C-comma: \033<C-,>
921	URxvt.keysym.C-period: \033<C-.>
922	URxvt.keysym.C-0x60: \033<C-`>
923	URxvt.keysym.C-Tab: \033<C-Tab>
924	URxvt.keysym.C-Return: \033<C-Return>
925	URxvt.keysym.S-Return: \033<S-Return>
926	URxvt.keysym.S-space: \033<S-Space>
927	URxvt.keysym.M-Up: \033<M-Up>
928	URxvt.keysym.M-Down: \033<M-Down>
929	URxvt.keysym.M-Left: \033<M-Left>
930	URxvt.keysym.M-Right: \033<M-Right>
931	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
932	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
933	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
934
935	See some more examples in the documentation for the B<keysym> resource.
936
937	=head2 I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
938	How do I make use of them? For example, the Sun Keyboard type 4
939	has the following mappings that rxvt-unicode doesn't recognize.
940
941	KP_Insert == Insert
942	F22 == Print
943	F27 == Home
944	F29 == Prior
945	F33 == End
946	F35 == Next
947
948	Rather than have rxvt-unicode try to accommodate all the various possible
949	keyboard mappings, it is better to use `xmodmap' to remap the keys as
950	required for your particular machine.
951
952	=head2 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
953	I need this to decide about setting colors etc.
954
955	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
956	check and see if that is set. Note that several programs, JED, slrn,
957	Midnight Commander automatically check this variable to decide whether or
958	not to use color.
959
960	=head2 How do I set the correct, full IP address for the DISPLAY variable?
961
962	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
963	insecure mode then it is possible to use the following shell script
964	snippets to correctly set the display. If your version of rxvt-unicode
965	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
966	the COLORTERM variable can be used to distinguish rxvt-unicode from a
967	regular xterm.
968
969	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
970	snippets:
971
972	# Bourne/Korn/POSIX family of shells:
973	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
974	if [ ${TERM:-foo} = xterm ]; then
975	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
976	echo -n '^[Z'
977	read term_id
978	stty icanon echo
979	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
980	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
981	read DISPLAY # set it in our local shell
982	fi
983	fi
984
985	=head2 How do I compile the manual pages for myself?
986
987	You need to have a recent version of perl installed as F</usr/bin/perl>,
988	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
989	the doc subdirectory and enter C<make alldoc>.
990
991	=head2 My question isn't answered here, can I ask a human?
992
993	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
994	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
995	interested in learning about new and exciting problems (but not FAQs :).
996
997	=head1 RXVT TECHNICAL REFERENCE	1214	=head1 RXVT-UNICODE TECHNICAL REFERENCE
998
999	=head1 DESCRIPTION
1000		1215
1001	The rest of this document describes various technical aspects of	1216	The rest of this document describes various technical aspects of
1002	B<rxvt-unicode>. First the description of supported command sequences,	1217	B<rxvt-unicode>. First the description of supported command sequences,
1003	followed by pixmap support and last by a description of all features	1218	followed by pixmap support and last by a description of all features
1004	selectable at C<configure> time.	1219	selectable at C<configure> time.
1005		1220
1006	=head1 Definitions	1221	=head2 Definitions
1007		1222
1008	=over 4	1223	=over 4
1009		1224
1010	=item B<< C<c> >>	1225	=item B<< C<c> >>
1011		1226
…		…
1029		1244
1030	A text parameter composed of printable characters.	1245	A text parameter composed of printable characters.
1031		1246
1032	=back	1247	=back
1033		1248
1034	=head1 Values	1249	=head2 Values
1035		1250
1036	=over 4	1251	=over 4
1037		1252
1038	=item B<< C<ENQ> >>	1253	=item B<< C<ENQ> >>
1039		1254
…		…
1082		1297
1083	Space Character	1298	Space Character
1084		1299
1085	=back	1300	=back
1086		1301
1087	=head1 Escape Sequences	1302	=head2 Escape Sequences
1088		1303
1089	=over 4	1304	=over 4
1090		1305
1091	=item B<< C<ESC # 8> >>	1306	=item B<< C<ESC # 8> >>
1092		1307
…		…
1190		1405
1191	=back	1406	=back
1192		1407
1193	X<CSI>	1408	X<CSI>
1194		1409
1195	=head1 CSI (Command Sequence Introducer) Sequences	1410	=head2 CSI (Command Sequence Introducer) Sequences
1196		1411
1197	=over 4	1412	=over 4
1198		1413
1199	=item B<< C<ESC [ Ps @> >>	1414	=item B<< C<ESC [ Ps @> >>
1200		1415
…		…
1470		1685
1471	=back	1686	=back
1472		1687
1473	X<PrivateModes>	1688	X<PrivateModes>
1474		1689
1475	=head1 DEC Private Modes	1690	=head2 DEC Private Modes
1476		1691
1477	=over 4	1692	=over 4
1478		1693
1479	=item B<< C<ESC [ ? Pm h> >>	1694	=item B<< C<ESC [ ? Pm h> >>
1480		1695
…		…
1496		1711
1497	Toggle DEC Private Mode Values (rxvt extension). I<where>	1712	Toggle DEC Private Mode Values (rxvt extension). I<where>
1498		1713
1499	=over 4	1714	=over 4
1500		1715
1501	=item B<< C<Ps = 1> >> (DECCKM)	1716	=item B<< C<Pm = 1> >> (DECCKM)
1502		1717
1503	=begin table	1718	=begin table
1504		1719
1505	B<< C<h> >> Application Cursor Keys	1720	B<< C<h> >> Application Cursor Keys
1506	B<< C<l> >> Normal Cursor Keys	1721	B<< C<l> >> Normal Cursor Keys
1507		1722
1508	=end table	1723	=end table
1509		1724
1510	=item B<< C<Ps = 2> >> (ANSI/VT52 mode)	1725	=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1511		1726
1512	=begin table	1727	=begin table
1513		1728
1514	B<< C<h> >> Enter VT52 mode	1729	B<< C<h> >> Enter VT52 mode
1515	B<< C<l> >> Enter VT52 mode	1730	B<< C<l> >> Enter VT52 mode
1516		1731
1517	=end table	1732	=end table
1518		1733
1519	=item B<< C<Ps = 3> >>	1734	=item B<< C<Pm = 3> >>
1520		1735
1521	=begin table	1736	=begin table
1522		1737
1523	B<< C<h> >> 132 Column Mode (DECCOLM)	1738	B<< C<h> >> 132 Column Mode (DECCOLM)
1524	B<< C<l> >> 80 Column Mode (DECCOLM)	1739	B<< C<l> >> 80 Column Mode (DECCOLM)
1525		1740
1526	=end table	1741	=end table
1527		1742
1528	=item B<< C<Ps = 4> >>	1743	=item B<< C<Pm = 4> >>
1529		1744
1530	=begin table	1745	=begin table
1531		1746
1532	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)	1747	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1533	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)	1748	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1534		1749
1535	=end table	1750	=end table
1536		1751
1537	=item B<< C<Ps = 5> >>	1752	=item B<< C<Pm = 5> >>
1538		1753
1539	=begin table	1754	=begin table
1540		1755
1541	B<< C<h> >> Reverse Video (DECSCNM)	1756	B<< C<h> >> Reverse Video (DECSCNM)
1542	B<< C<l> >> Normal Video (DECSCNM)	1757	B<< C<l> >> Normal Video (DECSCNM)
1543		1758
1544	=end table	1759	=end table
1545		1760
1546	=item B<< C<Ps = 6> >>	1761	=item B<< C<Pm = 6> >>
1547		1762
1548	=begin table	1763	=begin table
1549		1764
1550	B<< C<h> >> Origin Mode (DECOM)	1765	B<< C<h> >> Origin Mode (DECOM)
1551	B<< C<l> >> Normal Cursor Mode (DECOM)	1766	B<< C<l> >> Normal Cursor Mode (DECOM)
1552		1767
1553	=end table	1768	=end table
1554		1769
1555	=item B<< C<Ps = 7> >>	1770	=item B<< C<Pm = 7> >>
1556		1771
1557	=begin table	1772	=begin table
1558		1773
1559	B<< C<h> >> Wraparound Mode (DECAWM)	1774	B<< C<h> >> Wraparound Mode (DECAWM)
1560	B<< C<l> >> No Wraparound Mode (DECAWM)	1775	B<< C<l> >> No Wraparound Mode (DECAWM)
1561		1776
1562	=end table	1777	=end table
1563		1778
1564	=item B<< C<Ps = 8> >> I<unimplemented>	1779	=item B<< C<Pm = 8> >> I<unimplemented>
1565		1780
1566	=begin table	1781	=begin table
1567		1782
1568	B<< C<h> >> Auto-repeat Keys (DECARM)	1783	B<< C<h> >> Auto-repeat Keys (DECARM)
1569	B<< C<l> >> No Auto-repeat Keys (DECARM)	1784	B<< C<l> >> No Auto-repeat Keys (DECARM)
1570		1785
1571	=end table	1786	=end table
1572		1787
1573	=item B<< C<Ps = 9> >> X10 XTerm	1788	=item B<< C<Pm = 9> >> X10 XTerm
1574		1789
1575	=begin table	1790	=begin table
1576		1791
1577	B<< C<h> >> Send Mouse X & Y on button press.	1792	B<< C<h> >> Send Mouse X & Y on button press.
1578	B<< C<l> >> No mouse reporting.	1793	B<< C<l> >> No mouse reporting.
1579		1794
1580	=end table	1795	=end table
1581		1796
1582	=item B<< C<Ps = 25> >>	1797	=item B<< C<Pm = 25> >>
1583		1798
1584	=begin table	1799	=begin table
1585		1800
1586	B<< C<h> >> Visible cursor {cnorm/cvvis}	1801	B<< C<h> >> Visible cursor {cnorm/cvvis}
1587	B<< C<l> >> Invisible cursor {civis}	1802	B<< C<l> >> Invisible cursor {civis}
1588		1803
1589	=end table	1804	=end table
1590		1805
1591	=item B<< C<Ps = 30> >>	1806	=item B<< C<Pm = 30> >>
1592		1807
1593	=begin table	1808	=begin table
1594		1809
1595	B<< C<h> >> scrollBar visisble	1810	B<< C<h> >> scrollBar visisble
1596	B<< C<l> >> scrollBar invisisble	1811	B<< C<l> >> scrollBar invisisble
1597		1812
1598	=end table	1813	=end table
1599		1814
1600	=item B<< C<Ps = 35> >> (B<rxvt>)	1815	=item B<< C<Pm = 35> >> (B<rxvt>)
1601		1816
1602	=begin table	1817	=begin table
1603		1818
1604	B<< C<h> >> Allow XTerm Shift+key sequences	1819	B<< C<h> >> Allow XTerm Shift+key sequences
1605	B<< C<l> >> Disallow XTerm Shift+key sequences	1820	B<< C<l> >> Disallow XTerm Shift+key sequences
1606		1821
1607	=end table	1822	=end table
1608		1823
1609	=item B<< C<Ps = 38> >> I<unimplemented>	1824	=item B<< C<Pm = 38> >> I<unimplemented>
1610		1825
1611	Enter Tektronix Mode (DECTEK)	1826	Enter Tektronix Mode (DECTEK)
1612		1827
1613	=item B<< C<Ps = 40> >>	1828	=item B<< C<Pm = 40> >>
1614		1829
1615	=begin table	1830	=begin table
1616		1831
1617	B<< C<h> >> Allow 80/132 Mode	1832	B<< C<h> >> Allow 80/132 Mode
1618	B<< C<l> >> Disallow 80/132 Mode	1833	B<< C<l> >> Disallow 80/132 Mode
1619		1834
1620	=end table	1835	=end table
1621		1836
1622	=item B<< C<Ps = 44> >> I<unimplemented>	1837	=item B<< C<Pm = 44> >> I<unimplemented>
1623		1838
1624	=begin table	1839	=begin table
1625		1840
1626	B<< C<h> >> Turn On Margin Bell	1841	B<< C<h> >> Turn On Margin Bell
1627	B<< C<l> >> Turn Off Margin Bell	1842	B<< C<l> >> Turn Off Margin Bell
1628		1843
1629	=end table	1844	=end table
1630		1845
1631	=item B<< C<Ps = 45> >> I<unimplemented>	1846	=item B<< C<Pm = 45> >> I<unimplemented>
1632		1847
1633	=begin table	1848	=begin table
1634		1849
1635	B<< C<h> >> Reverse-wraparound Mode	1850	B<< C<h> >> Reverse-wraparound Mode
1636	B<< C<l> >> No Reverse-wraparound Mode	1851	B<< C<l> >> No Reverse-wraparound Mode
1637		1852
1638	=end table	1853	=end table
1639		1854
1640	=item B<< C<Ps = 46> >> I<unimplemented>	1855	=item B<< C<Pm = 46> >> I<unimplemented>
1641		1856
1642	=item B<< C<Ps = 47> >>	1857	=item B<< C<Pm = 47> >>
1643		1858
1644	=begin table	1859	=begin table
1645		1860
1646	B<< C<h> >> Use Alternate Screen Buffer	1861	B<< C<h> >> Use Alternate Screen Buffer
1647	B<< C<l> >> Use Normal Screen Buffer	1862	B<< C<l> >> Use Normal Screen Buffer
1648		1863
1649	=end table	1864	=end table
1650		1865
1651	X<Priv66>	1866	X<Priv66>
1652		1867
1653	=item B<< C<Ps = 66> >>	1868	=item B<< C<Pm = 66> >>
1654		1869
1655	=begin table	1870	=begin table
1656		1871
1657	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>	1872	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1658	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>	1873	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1659		1874
1660	=end table	1875	=end table
1661		1876
1662	=item B<< C<Ps = 67> >>	1877	=item B<< C<Pm = 67> >>
1663		1878
1664	=begin table	1879	=begin table
1665		1880
1666	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>	1881	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1667	B<< C<l> >> Backspace key sends B<< C<DEL> >>	1882	B<< C<l> >> Backspace key sends B<< C<DEL> >>
1668		1883
1669	=end table	1884	=end table
1670		1885
1671	=item B<< C<Ps = 1000> >> (X11 XTerm)	1886	=item B<< C<Pm = 1000> >> (X11 XTerm)
1672		1887
1673	=begin table	1888	=begin table
1674		1889
1675	B<< C<h> >> Send Mouse X & Y on button press and release.	1890	B<< C<h> >> Send Mouse X & Y on button press and release.
1676	B<< C<l> >> No mouse reporting.	1891	B<< C<l> >> No mouse reporting.
1677		1892
1678	=end table	1893	=end table
1679		1894
1680	=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented>	1895	=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1681		1896
1682	=begin table	1897	=begin table
1683		1898
1684	B<< C<h> >> Use Hilite Mouse Tracking.	1899	B<< C<h> >> Use Hilite Mouse Tracking.
1685	B<< C<l> >> No mouse reporting.	1900	B<< C<l> >> No mouse reporting.
1686		1901
1687	=end table	1902	=end table
1688		1903
1689	=item B<< C<Ps = 1010> >> (B<rxvt>)	1904	=item B<< C<Pm = 1010> >> (B<rxvt>)
1690		1905
1691	=begin table	1906	=begin table
1692		1907
1693	B<< C<h> >> Don't scroll to bottom on TTY output	1908	B<< C<h> >> Don't scroll to bottom on TTY output
1694	B<< C<l> >> Scroll to bottom on TTY output	1909	B<< C<l> >> Scroll to bottom on TTY output
1695		1910
1696	=end table	1911	=end table
1697		1912
1698	=item B<< C<Ps = 1011> >> (B<rxvt>)	1913	=item B<< C<Pm = 1011> >> (B<rxvt>)
1699		1914
1700	=begin table	1915	=begin table
1701		1916
1702	B<< C<h> >> Scroll to bottom when a key is pressed	1917	B<< C<h> >> Scroll to bottom when a key is pressed
1703	B<< C<l> >> Don't scroll to bottom when a key is pressed	1918	B<< C<l> >> Don't scroll to bottom when a key is pressed
1704		1919
1705	=end table	1920	=end table
1706		1921
1707	=item B<< C<Ps = 1021> >> (B<rxvt>)	1922	=item B<< C<Pm = 1021> >> (B<rxvt>)
1708		1923
1709	=begin table	1924	=begin table
1710		1925
1711	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)	1926	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
1712	B<< C<l> >> Font styles have no effect on intensity (Compile styles)	1927	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1713		1928
1714	=end table	1929	=end table
1715		1930
1716	=item B<< C<Ps = 1047> >>	1931	=item B<< C<Pm = 1047> >>
1717		1932
1718	=begin table	1933	=begin table
1719		1934
1720	B<< C<h> >> Use Alternate Screen Buffer	1935	B<< C<h> >> Use Alternate Screen Buffer
1721	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it	1936	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1722		1937
1723	=end table	1938	=end table
1724		1939
1725	=item B<< C<Ps = 1048> >>	1940	=item B<< C<Pm = 1048> >>
1726		1941
1727	=begin table	1942	=begin table
1728		1943
1729	B<< C<h> >> Save cursor position	1944	B<< C<h> >> Save cursor position
1730	B<< C<l> >> Restore cursor position	1945	B<< C<l> >> Restore cursor position
1731		1946
1732	=end table	1947	=end table
1733		1948
1734	=item B<< C<Ps = 1049> >>	1949	=item B<< C<Pm = 1049> >>
1735		1950
1736	=begin table	1951	=begin table
1737		1952
1738	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it	1953	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1739	B<< C<l> >> Use Normal Screen Buffer	1954	B<< C<l> >> Use Normal Screen Buffer
…		…
1744		1959
1745	=back	1960	=back
1746		1961
1747	X<XTerm>	1962	X<XTerm>
1748		1963
1749	=head1 XTerm Operating System Commands	1964	=head2 XTerm Operating System Commands
1750		1965
1751	=over 4	1966	=over 4
1752		1967
1753	=item B<< C<ESC ] Ps;Pt ST> >>	1968	=item B<< C<ESC ] Ps;Pt ST> >>
1754		1969
…		…
1792		2007
1793	=end table	2008	=end table
1794		2009
1795	=back	2010	=back
1796		2011
1797	X<XPM>
1798
1799	=head1 XPM	2012	=head1 XPM
1800		2013
1801	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	2014	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1802	of B<< C<Pt> >> can be the name of the background pixmap followed by a	2015	of B<< C<Pt> >> can be the name of the background pixmap followed by a
1803	sequence of scaling/positioning commands separated by semi-colons. The	2016	sequence of scaling/positioning commands separated by semi-colons. The
…		…
1900	=begin table	2113	=begin table
1901		2114
1902	4 Shift	2115	4 Shift
1903	8 Meta	2116	8 Meta
1904	16 Control	2117	16 Control
1905	32 Double Click I<(Rxvt extension)>	2118	32 Double Click I<(rxvt extension)>
1906		2119
1907	=end table	2120	=end table
1908		2121
1909	Col = B<< C<< <x> - SPACE >> >>	2122	Col = B<< C<< <x> - SPACE >> >>
1910		2123
…		…
1988		2201
1989	=head1 CONFIGURE OPTIONS	2202	=head1 CONFIGURE OPTIONS
1990		2203
1991	General hint: if you get compile errors, then likely your configuration	2204	General hint: if you get compile errors, then likely your configuration
1992	hasn't been tested well. Either try with C<--enable-everything> or use	2205	hasn't been tested well. Either try with C<--enable-everything> or use
1993	the F<./reconf> script as a base for experiments. F<./reconf> is used by	2206	the default configuration (i.e. C<--enable-xxx> or C<--disable-xxx>). Of
1994	myself, so it should generally be a working config. Of course, you should	2207	course, you should always report when a combination doesn't work, so it
1995	always report when a combination doesn't work, so it can be fixed. Marc	2208	can be fixed. Marc Lehmann <rxvt@schmorp.de>.
1996	Lehmann <rxvt@schmorp.de>.
1997		2209
1998	All	2210	All
1999		2211
2000	=over 4	2212	=over 4
2001		2213
…		…
2033		2245
2034	=begin table	2246	=begin table
2035		2247
2036	all all available codeset groups	2248	all all available codeset groups
2037	zh common chinese encodings	2249	zh common chinese encodings
2038	zh_ext rarely used but very big chinese encodigs	2250	zh_ext rarely used but very big chinese encodings
2039	jp common japanese encodings	2251	jp common japanese encodings
2040	jp_ext rarely used but big japanese encodings	2252	jp_ext rarely used but big japanese encodings
2041	kr korean encodings	2253	kr korean encodings
2042		2254
2043	=end table	2255	=end table
…		…
2194	cursor blinking and underline cursor (-cb, -uc)	2406	cursor blinking and underline cursor (-cb, -uc)
2195	XEmbed support (-embed)	2407	XEmbed support (-embed)
2196	user-pty (-pty-fd)	2408	user-pty (-pty-fd)
2197	hold on exit (-hold)	2409	hold on exit (-hold)
2198	skip builtin block graphics (-sbg)	2410	skip builtin block graphics (-sbg)
		2411	separate highlightcolor support (-hc)
2199		2412
2200	It also enabled some non-essential features otherwise disabled, such as:	2413	It also enables some non-essential features otherwise disabled, such as:
2201		2414
2202	some round-trip time optimisations	2415	some round-trip time optimisations
2203	nearest color allocation on pseudocolor screens	2416	nearest color allocation on pseudocolor screens
2204	UTF8_STRING supporr for selection	2417	UTF8_STRING support for selection
2205	sgr modes 90..97 and 100..107	2418	sgr modes 90..97 and 100..107
2206	backindex and forwardindex escape sequences	2419	backindex and forwardindex escape sequences
2207	view change/zero scorllback esacpe sequences	2420	view change/zero scrollback escape sequences
2208	locale switching escape sequence	2421	locale switching escape sequence
2209	window op and some xterm/OSC escape sequences	2422	window op and some xterm/OSC escape sequences
2210	rectangular selections	2423	rectangular selections
2211	trailing space removal for selections	2424	trailing space removal for selections
2212	verbose X error handling	2425	verbose X error handling
…		…
2238	Remove support for mouse selection style like that of xterm.	2451	Remove support for mouse selection style like that of xterm.
2239		2452
2240	=item --enable-dmalloc (default: off)	2453	=item --enable-dmalloc (default: off)
2241		2454
2242	Use Gray Watson's malloc - which is good for debugging See	2455	Use Gray Watson's malloc - which is good for debugging See
2243	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
2244	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
2245	DINCLUDE and DLIB to the right places.	2458	DINCLUDE and DLIB to the right places.
2246		2459
2247	You can only use either this option and the following (should	2460	You can only use either this option and the following (should
2248	you use either) .	2461	you use either) .

Diff Legend

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