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.99 by root, Tue Jan 31 00:57:35 2006 UTC vs.
Revision 1.113 by root, Thu Feb 2 18:04:45 2006 UTC

…		…
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/*checkout*/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	=head2 The cursor moves when selecting text in the current input line, how
67	do I switch this off?
68
69	=head2 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor
70	outputs strange escape sequences, how do I fix this?
71
72	These are caused by the C<readline> perl extension. Under normal
73	circumstances, it will move your cursor around when you click into the
74	line that contains it. It tries hard not to do this at the wrong moment,
75	but when running a program that doesn't parse cursor movements or in some
76	cases during rlogin sessions, it fails to detect this properly.
77
78	You can permamently switch this feature off by disabling the C<readline>
79	extension:
80
81	URxvt.perl-ext-common: default,-readline	43	URxvt.perl-ext-common: default,tabbed
82		44
83	=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.
84		50
85	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?
86	applications. Most importantly, this means that if you or your OS loads
87	resources into the X display (the right way to do it), rxvt-unicode will
88	ignore any resource files in your home directory. It will only read
89	F<$HOME/.Xdefaults> when no resources are attached to the display.
90		52
91	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
92	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
93	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.
94		57
95	Also consider the form resources have to use:	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
96		59
97	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.
98		65
99	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
100	specifying resources), make sure you understand wether and why it	67	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
101	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.
102		72
103	=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?
104		74
105	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
106	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.
107	bug everybody else). Also, if you can't get it working consider it a rite
108	of passage: ... and you failed.
109		77
110	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?
111	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
112		79
113	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:
114		82
115	Esetroot wallpaper.jpg	83	#!/bin/sh
116	@@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
117		89
118	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,
119	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.
120		94
121	2. Use a simple pixmap and emulate pseudo-transparency. This enables you	95	=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
122	to use effects other than tinting and shading: Just shade/tint/whatever
123	your picture with gimp:
124		96
125	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	97	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
126	@@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.
127		101
128	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?
129	are unable to read.
130		103
131	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.
132		110
133	@@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:
134		113
135	This requires XFT support, and the support of your X-server. If that	114	# Bourne/Korn/POSIX family of shells:
136	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
137	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary	116	if [ ${TERM:-foo} = xterm ]; then
138	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
139	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
140		126
141	4. Use xcompmgr and let it do the job:	127	=head3 How do I compile the manual pages on my own?
142		128
143	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \	129	You need to have a recent version of perl installed as F</usr/bin/perl>,
144	-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>.
145		132
146	Then click on a window you want to make transparent. Replace C<0xc0000000>
147	by other values to change the degree of opacity. If it doesn't work and
148	your server crashes, you got to keep the pieces.
149
150	=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?
151		134
152	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
153	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
154	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
155	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
…		…
159		142
160	text data bss drs rss filename	143	text data bss drs rss filename
161	98398 1664 24 15695 1824 rxvt --disable-everything	144	98398 1664 24 15695 1824 rxvt --disable-everything
162	188985 9048 66616 18222 1788 urxvt --disable-everything	145	188985 9048 66616 18222 1788 urxvt --disable-everything
163		146
164	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
165	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
166	libc), the two diverge, but not unreasnobaly so.	149	libc), the two diverge, but not unreasnobaly so.
167		150
168	text data bss drs rss filename	151	text data bss drs rss filename
169	163431 2152 24 20123 2060 rxvt --enable-everything	152	163431 2152 24 20123 2060 rxvt --enable-everything
…		…
187	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
188	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
189	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
190	extremely well *g*.	173	extremely well *g*.
191		174
192	=head2 Why C++, isn't that unportable/bloated/uncool?	175	=head3 Why C++, isn't that unportable/bloated/uncool?
193		176
194	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
195	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
196	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
197	shorter: It simply wouldn't exist without C++.	180	shorter: It simply wouldn't exist without C++.
…		…
221	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
222		205
223	No large bloated libraries (of course, none were linked in statically),	206	No large bloated libraries (of course, none were linked in statically),
224	except maybe libX11 :)	207	except maybe libX11 :)
225		208
226	=head2 Does it support tabs, can I have a tabbed rxvt-unicode?
227		209
228	Beginning with version 7.3, there is a perl extension that implements a	210	=head2 Rendering, Font & Look and Feel Issues
229	simple tabbed terminal. It is installed by default, so any of these should
230	give you tabs:
231		211
232	@@RXVT_NAME@@ -pe tabbed	212	=head3 I can't get transparency working, what am I doing wrong?
233		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 neccessary
		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), wether this is a bug in Xft, freetype,
		274	or the respective font. If you encounter this problem you might try using
		275	the C<-lsp> option to give the font more height. If that doesn't work, you
		276	might be forced to use a different font.
		277
		278	All of this is not a problem when using X11 core fonts, as their bounding
		279	box data is correct.
		280
		281	=head3 How can I keep rxvt-unicode from using reverse video so much?
		282
		283	First of all, make sure you are running with the right terminal settings
		284	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		285	make sure you have specified colours for italic and bold, as otherwise
		286	rxvt-unicode might use reverse video to simulate the effect:
		287
		288	URxvt.colorBD: white
		289	URxvt.colorIT: green
		290
		291	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		292
		293	For some unexplainable reason, some rare programs assume a very weird
		294	colour palette when confronted with a terminal with more than the standard
		295	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		296	these programs not to assume non-ISO colours without very good reasons.
		297
		298	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		299	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		300	fix colours but keep you from using other rxvt-unicode features.
		301
		302	=head3 Can I switch the fonts at runtime?
		303
		304	Yes, using an escape sequence. Try something like this, which has the same
		305	effect as using the C<-fn> switch, and takes effect immediately:
		306
		307	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		308
		309	This is useful if you e.g. work primarily with japanese (and prefer a
		310	japanese font), but you have to switch to chinese temporarily, where
		311	japanese fonts would only be in your way.
		312
		313	You can think of this as a kind of manual ISO-2022 switching.
		314
		315	=head3 Why do italic characters look as if clipped?
		316
		317	Many fonts have difficulties with italic characters and hinting. For
		318	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		319	Mono> completely fails in it's italic face. A workaround might be to
		320	enable freetype autohinting, i.e. like this:
		321
		322	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		323	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		324
		325	=head3 Can I speed up Xft rendering somehow?
		326
		327	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		328	it is simply slow. If you still want Xft fonts you might try to disable
		329	antialiasing (by appending C<:antialias=false>), which saves lots of
		330	memory and also speeds up rendering considerably.
		331
		332	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		333
		334	Rxvt-unicode will use whatever you specify as a font. If it needs to
		335	fall back to it's default font search list it will prefer X11 core
		336	fonts, because they are small and fast, and then use Xft fonts. It has
		337	antialiasing disabled for most of them, because the author thinks they
		338	look best that way.
		339
		340	If you want antialiasing, you have to specify the fonts manually.
		341
		342	=head3 What's with this bold/blink stuff?
		343
		344	If no bold colour is set via C<colorBD:>, bold will invert text using the
		345	standard foreground colour.
		346
		347	For the standard background colour, blinking will actually make the
		348	text blink when compiled with C<--enable-blinking>. with standard
		349	colours. Without C<--enable-blinking>, the blink attribute will be
		350	ignored.
		351
		352	On ANSI colours, bold/blink attributes are used to set high-intensity
		353	foreground/background colors.
		354
		355	color0-7 are the low-intensity colors.
		356
		357	color8-15 are the corresponding high-intensity colors.
		358
		359	=head3 I don't like the screen colors. How do I change them?
		360
		361	You can change the screen colors at run-time using F<~/.Xdefaults>
		362	resources (or as long-options).
		363
		364	Here are values that are supposed to resemble a VGA screen,
		365	including the murky brown that passes for low-intensity yellow:
		366
		367	URxvt.color0: #000000
		368	URxvt.color1: #A80000
		369	URxvt.color2: #00A800
		370	URxvt.color3: #A8A800
		371	URxvt.color4: #0000A8
		372	URxvt.color5: #A800A8
		373	URxvt.color6: #00A8A8
		374	URxvt.color7: #A8A8A8
		375
		376	URxvt.color8: #000054
		377	URxvt.color9: #FF0054
		378	URxvt.color10: #00FF54
		379	URxvt.color11: #FFFF54
		380	URxvt.color12: #0000FF
		381	URxvt.color13: #FF00FF
		382	URxvt.color14: #00FFFF
		383	URxvt.color15: #FFFFFF
		384
		385	And here is a more complete set of non-standard colors.
		386
		387	URxvt.cursorColor: #dc74d1
		388	URxvt.pointerColor: #dc74d1
		389	URxvt.background: #0e0e0e
		390	URxvt.foreground: #4ad5e1
		391	URxvt.color0: #000000
		392	URxvt.color8: #8b8f93
		393	URxvt.color1: #dc74d1
		394	URxvt.color9: #dc74d1
		395	URxvt.color2: #0eb8c7
		396	URxvt.color10: #0eb8c7
		397	URxvt.color3: #dfe37e
		398	URxvt.color11: #dfe37e
		399	URxvt.color5: #9e88f0
		400	URxvt.color13: #9e88f0
		401	URxvt.color6: #73f7ff
		402	URxvt.color14: #73f7ff
		403	URxvt.color7: #e1dddd
		404	URxvt.color15: #e1dddd
		405
		406	They have been described (not by me) as "pretty girly".
		407
		408	=head3 Why do some characters look so much different than others?
		409
		410	See next entry.
		411
		412	=head3 How does rxvt-unicode choose fonts?
		413
		414	Most fonts do not contain the full range of Unicode, which is
		415	fine. Chances are that the font you (or the admin/package maintainer of
		416	your system/os) have specified does not cover all the characters you want
		417	to display.
		418
		419	B<rxvt-unicode> makes a best-effort try at finding a replacement
		420	font. Often the result is fine, but sometimes the chosen font looks
		421	bad/ugly/wrong. Some fonts have totally strange characters that don't
		422	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		423	intelligence to detect that a specific glyph is wrong: it has to believe
		424	the font that the characters it claims to contain indeed look correct.
		425
		426	In that case, select a font of your taste and add it to the font list,
		427	e.g.:
		428
		429	@@URXVT_NAME@@ -fn basefont,font2,font3...
		430
		431	When rxvt-unicode sees a character, it will first look at the base
		432	font. If the base font does not contain the character, it will go to the
		433	next font, and so on. Specifying your own fonts will also speed up this
		434	search and use less resources within rxvt-unicode and the X-server.
		435
		436	The only limitation is that none of the fonts may be larger than the base
		437	font, as the base font defines the terminal character cell size, which
		438	must be the same due to the way terminals work.
		439
		440	=head3 Why do some chinese characters look so different than others?
		441
		442	This is because there is a difference between script and language --
		443	rxvt-unicode does not know which language the text that is output is,
		444	as it only knows the unicode character codes. If rxvt-unicode first
		445	sees a japanese/chinese character, it might choose a japanese font for
		446	display. Subsequent japanese characters will use that font. Now, many
		447	chinese characters aren't represented in japanese fonts, so when the first
		448	non-japanese character comes up, rxvt-unicode will look for a chinese font
		449	-- unfortunately at this point, it will still use the japanese font for
		450	chinese characters that are also in the japanese font.
		451
		452	The workaround is easy: just tag a chinese font at the end of your font
		453	list (see the previous question). The key is to view the font list as
		454	a preference list: If you expect more japanese, list a japanese font
		455	first. If you expect more chinese, put a chinese font first.
		456
		457	In the future it might be possible to switch language preferences at
		458	runtime (the internal data structure has no problem with using different
		459	fonts for the same character at the same time, but no interface for this
		460	has been designed yet).
		461
		462	Until then, you might get away with switching fonts at runtime (see L<Can
		463	I switch the fonts at runtime?> later in this document).
		464
		465	=head2 Keyboard, Mouse & User Interaction
		466
		467	=head3 The new selection selects pieces that are too big, how can I select single words?
		468
		469	If you want to select e.g. alphanumeric words, you can use the following
		470	setting:
		471
		472	URxvt.selection.pattern-0: ([[:word:]]+)
		473
		474	If you click more than twice, the selection will be extended
		475	more and more.
		476
		477	To get a selection that is very similar to the old code, try this pattern:
		478
		479	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		480
		481	Please also note that the I<LeftClick Shift-LeftClik> combination also
		482	selects words like the old code.
		483
		484	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		485
		486	You can disable the perl extension completely by setting the
		487	B<perl-ext-common> resource to the empty string, which also keeps
		488	rxvt-unicode from initialising perl, saving memory.
		489
		490	If you only want to disable specific features, you first have to
		491	identify which perl extension is responsible. For this, read the section
		492	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		493	example, to disable the B<selection-popup> and B<option-popup>, specify
		494	this B<perl-ext-common> resource:
		495
		496	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		497
		498	This will keep the default extensions, but disable the two popup
		499	extensions. Some extensions can also be configured, for example,
		500	scrollback search mode is triggered by B<M-s>. You can move it to any
		501	other combination either by setting the B<searchable-scrollback> resource:
		502
		503	URxvt.searchable-scrollback: CM-s
		504
		505	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		506
		507	See next entry.
		508
		509	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		510
		511	These are caused by the C<readline> perl extension. Under normal
		512	circumstances, it will move your cursor around when you click into the
		513	line that contains it. It tries hard not to do this at the wrong moment,
		514	but when running a program that doesn't parse cursor movements or in some
		515	cases during rlogin sessions, it fails to detect this properly.
		516
		517	You can permamently switch this feature off by disabling the C<readline>
		518	extension:
		519
234	URxvt.perl-ext-common: default,tabbed	520	URxvt.perl-ext-common: default,-readline
235		521
236	It will also work fine with tabbing functionality of many window managers	522	=head3 My numerical keypad acts weird and generates differing output?
237	or similar tabbing programs, and its embedding-features allow it to be
238	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
239	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
240	(murxvt) terminal as an example embedding application.
241		523
242	=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 wether and how
		527	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		528	keymap. See the answer to the previous question, and please report if that
		529	helped.
243		530
244	The version number is displayed with the usage (-h). Also the escape	531	=head3 My Compose (Multi_key) key is no longer working.
245	sequence C<ESC [ 8 n> sets the window title to the version number. When
246	using the @@RXVT_NAME@@c client, the version displayed is that of the
247	daemon.
248		532
249	=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.
250		539
251	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
252	patches that considerably change the behaviour of rxvt-unicode (but	541	one pre-edit style, such as B<OverTheSpot,Root,None>.
253	unfortunately this notice has been removed). Before reporting a bug to
254	the original rxvt-unicode author please download and install the genuine
255	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
256	the problem. If you cannot, chances are that the problems are specific to
257	Debian GNU/Linux, in which case it should be reported via the Debian Bug
258	Tracking System (use C<reportbug> to report the bug).
259		542
260	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
261	probably should use the Debian BTS, too, because, after all, it's also a
262	bug in the Debian version and it serves as a reminder for other users that
263	might encounter the same issue.
264		544
265	=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
266	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.
267		550
268	You should build one binary with the default options. F<configure>	551	=head3 Mouse cut/paste suddenly no longer works.
269	now enables most useful options, and the trend goes to making them
270	runtime-switchable, too, so there is usually no drawback to enbaling them,
271	except higher disk and possibly memory usage. The perl interpreter should
272	be enabled, as important functionality (menus, selection, likely more in
273	the future) depends on it.
274		552
275	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
276	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
277	behaviour. If your distribution aims at low memory, add an empty	555	heard that tcsh may use mouse reporting unless it otherwise specified. A
278	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
279	perl interpreter disabled until the user enables it.	557	depressed.
280		558
281	If you can/want build more binaries, I recommend building a minimal	559	=head3 What's with the strange Backspace/Delete key behaviour?
282	one with C<--disable-everything> (very useful) and a maximal one with
283	C<--enable-everything> (less useful, it will be very big due to a lot of
284	encodings built-in that increase download times and are rarely used).
285		560
286	=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<^?>.
287		565
288	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
289	install urxvt with privileges necessary for your OS now.	567	policy of using C<^?> when unsure, because it's the one only only correct
		568	choice :).
290		569
291	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
292	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
293	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
294	immediately. This is much safer than most other terminals that keep	573	system value of `erase', which corresponds to CERASE in <termios.h>, will
295	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).
296	things as perl interpreters, which might be "helpful" to attackers).
297		575
298	This forking is done as the very first within main(), which is very early	576	For starting a new rxvt-unicode:
299	and reduces possible bugs to initialisation code run before main(), or
300	things like the dynamic loader of your system, which should result in very
301	little risk.
302		577
		578	# use Backspace = ^H
		579	$ stty erase ^H
		580	$ @@URXVT_NAME@@
		581
		582	# use Backspace = ^?
		583	$ stty erase ^?
		584	$ @@URXVT_NAME@@
		585
		586	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		587
		588	For an existing rxvt-unicode:
		589
		590	# use Backspace = ^H
		591	$ stty erase ^H
		592	$ echo -n "^[[36h"
		593
		594	# use Backspace = ^?
		595	$ stty erase ^?
		596	$ echo -n "^[[36l"
		597
		598	This helps satisfy some of the Backspace discrepancies that occur, but
		599	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		600	properly reflects that.
		601
		602	The Delete key is a another casualty of the ill-defined Backspace problem.
		603	To avoid confusion between the Backspace and Delete keys, the Delete
		604	key has been assigned an escape sequence to match the vt100 for Execute
		605	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		606
		607	Some other Backspace problems:
		608
		609	some editors use termcap/terminfo,
		610	some editors (vim I'm told) expect Backspace = ^H,
		611	GNU Emacs (and Emacs-like editors) use ^H for help.
		612
		613	Perhaps someday this will all be resolved in a consistent manner.
		614
		615	=head3 I don't like the key-bindings. How do I change them?
		616
		617	There are some compile-time selections available via configure. Unless
		618	you have run "configure" with the C<--disable-resources> option you can
		619	use the `keysym' resource to alter the keystrings associated with keysyms.
		620
		621	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		622
		623	URxvt.keysym.Home: \033[1~
		624	URxvt.keysym.End: \033[4~
		625	URxvt.keysym.C-apostrophe: \033<C-'>
		626	URxvt.keysym.C-slash: \033<C-/>
		627	URxvt.keysym.C-semicolon: \033<C-;>
		628	URxvt.keysym.C-grave: \033<C-`>
		629	URxvt.keysym.C-comma: \033<C-,>
		630	URxvt.keysym.C-period: \033<C-.>
		631	URxvt.keysym.C-0x60: \033<C-`>
		632	URxvt.keysym.C-Tab: \033<C-Tab>
		633	URxvt.keysym.C-Return: \033<C-Return>
		634	URxvt.keysym.S-Return: \033<S-Return>
		635	URxvt.keysym.S-space: \033<S-Space>
		636	URxvt.keysym.M-Up: \033<M-Up>
		637	URxvt.keysym.M-Down: \033<M-Down>
		638	URxvt.keysym.M-Left: \033<M-Left>
		639	URxvt.keysym.M-Right: \033<M-Right>
		640	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		641	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		642	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		643
		644	See some more examples in the documentation for the B<keysym> resource.
		645
		646	=head3 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map
		647
		648	KP_Insert == Insert
		649	F22 == Print
		650	F27 == Home
		651	F29 == Prior
		652	F33 == End
		653	F35 == Next
		654
		655	Rather than have rxvt-unicode try to accommodate all the various possible
		656	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		657	required for your particular machine.
		658
		659
		660
		661	=head2 Terminal Configuration
		662
		663	=head3 Why doesn't rxvt-unicode read my resources?
		664
		665	Well, why, indeed? It does, in a way very similar to other X
		666	applications. Most importantly, this means that if you or your OS loads
		667	resources into the X display (the right way to do it), rxvt-unicode will
		668	ignore any resource files in your home directory. It will only read
		669	F<$HOME/.Xdefaults> when no resources are attached to the display.
		670
		671	If you have or use an F<$HOME/.Xresources> file, chances are that
		672	resources are loaded into your X-server. In this case, you have to
		673	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		674
		675	Also consider the form resources have to use:
		676
		677	URxvt.resource: value
		678
		679	If you want to use another form (there are lots of different ways of
		680	specifying resources), make sure you understand wether and why it
		681	works. If unsure, use the form above.
		682
303	=head2 When I log-in to another system it tells me about missing terminfo data?	683	=head3 When I log-in to another system it tells me about missing terminfo data?
304		684
305	The terminal description used by rxvt-unicode is not as widely available	685	The terminal description used by rxvt-unicode is not as widely available
306	as that for xterm, or even rxvt (for which the same problem often arises).	686	as that for xterm, or even rxvt (for which the same problem often arises).
307		687
308	The correct solution for this problem is to install the terminfo, this can	688	The correct solution for this problem is to install the terminfo, this can
…		…
324	resource to set it:	704	resource to set it:
325		705
326	URxvt.termName: rxvt	706	URxvt.termName: rxvt
327		707
328	If you don't plan to use B<rxvt> (quite common...) you could also replace	708	If you don't plan to use B<rxvt> (quite common...) you could also replace
329	the rxvt terminfo file with the rxvt-unicode one.	709	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
330		710
331	=head2 C<tic> outputs some error when compiling the terminfo entry.	711	=head3 C<tic> outputs some error when compiling the terminfo entry.
332		712
333	Most likely it's the empty definition for C<enacs=>. Just replace it by	713	Most likely it's the empty definition for C<enacs=>. Just replace it by
334	C<enacs=\E[0@> and try again.	714	C<enacs=\E[0@> and try again.
335		715
336	=head2 C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	716	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
337		717
		718	See next entry.
		719
338	=head2 I need a termcap file entry.	720	=head3 I need a termcap file entry.
339		721
340	One reason you might want this is that some distributions or operating	722	One reason you might want this is that some distributions or operating
341	systems still compile some programs using the long-obsoleted termcap	723	systems still compile some programs using the long-obsoleted termcap
342	library (Fedora Core's bash is one example) and rely on a termcap entry	724	library (Fedora Core's bash is one example) and rely on a termcap entry
343	for C<rxvt-unicode>.	725	for C<rxvt-unicode>.
…		…
369	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	751	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
370	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	752	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
371	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	753	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
372	:vs=\E[?25h:	754	:vs=\E[?25h:
373		755
374	=head2 Why does C<ls> no longer have coloured output?	756	=head3 Why does C<ls> no longer have coloured output?
375		757
376	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	758	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
377	decide wether a terminal has colour, but uses it's own configuration	759	decide wether a terminal has colour, but uses it's own configuration
378	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	760	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
379	with most other terminals supporting colour). Either add:	761	with most other terminals supporting colour). Either add:
…		…
384		766
385	alias ls='ls --color=auto'	767	alias ls='ls --color=auto'
386		768
387	to your C<.profile> or C<.bashrc>.	769	to your C<.profile> or C<.bashrc>.
388		770
389	=head2 Why doesn't vim/emacs etc. use the 88 colour mode?	771	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
390		772
		773	See next entry.
		774
391	=head2 Why doesn't vim/emacs etc. make use of italic?	775	=head3 Why doesn't vim/emacs etc. make use of italic?
392		776
		777	See next entry.
		778
393	=head2 Why are the secondary screen-related options not working properly?	779	=head3 Why are the secondary screen-related options not working properly?
394		780
395	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	781	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
396	distributions (most notably Debian GNU/Linux) break rxvt-unicode	782	distributions (most notably Debian GNU/Linux) break rxvt-unicode
397	by setting C<TERM> to C<rxvt>, which doesn't have these extra	783	by setting C<TERM> to C<rxvt>, which doesn't have these extra
398	features. Unfortunately, some of these (most notably, again, Debian	784	features. Unfortunately, some of these (most notably, again, Debian
399	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	785	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
400	file, so you will need to install it on your own (See the question B<When	786	file, so you will need to install it on your own (See the question B<When
401	I log-in to another system it tells me about missing terminfo data?> on	787	I log-in to another system it tells me about missing terminfo data?> on
402	how to do this).	788	how to do this).
403		789
404	=head2 My numerical keypad acts weird and generates differing output?
405		790
406	Some Debian GNUL/Linux users seem to have this problem, although no	791	=head2 Encoding / Locale / Input Method Issues
407	specific details were reported so far. It is possible that this is caused
408	by the wrong C<TERM> setting, although the details of wether and how
409	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
410	keymap. See the answer to the previous question, and please report if that
411	helped.
412		792
413	=head2 Rxvt-unicode does not seem to understand the selected encoding?	793	=head3 Rxvt-unicode does not seem to understand the selected encoding?
414		794
		795	See next entry.
		796
415	=head2 Unicode does not seem to work?	797	=head3 Unicode does not seem to work?
416		798
417	If you encounter strange problems like typing an accented character but	799	If you encounter strange problems like typing an accented character but
418	getting two unrelated other characters or similar, or if program output is	800	getting two unrelated other characters or similar, or if program output is
419	subtly garbled, then you should check your locale settings.	801	subtly garbled, then you should check your locale settings.
420		802
…		…
440		822
441	If nothing works and you are sure that everything is set correctly then	823	If nothing works and you are sure that everything is set correctly then
442	you will need to remember a little known fact: Some programs just don't	824	you will need to remember a little known fact: Some programs just don't
443	support locales :(	825	support locales :(
444		826
445	=head2 Why do some characters look so much different than others?	827	=head3 How does rxvt-unicode determine the encoding to use?
446		828
447	=head2 How does rxvt-unicode choose fonts?	829	See next entry.
448		830
449	Most fonts do not contain the full range of Unicode, which is	831	=head3 Is there an option to switch encodings?
450	fine. Chances are that the font you (or the admin/package maintainer of
451	your system/os) have specified does not cover all the characters you want
452	to display.
453		832
454	B<rxvt-unicode> makes a best-effort try at finding a replacement	833	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
455	font. Often the result is fine, but sometimes the chosen font looks	834	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
456	bad/ugly/wrong. Some fonts have totally strange characters that don't	835	UTF-8 or any other encodings with respect to terminal I/O.
457	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
458	intelligence to detect that a specific glyph is wrong: it has to believe
459	the font that the characters it claims to contain indeed look correct.
460		836
461	In that case, select a font of your taste and add it to the font list,	837	The reasons is that there exists a perfectly fine mechanism for selecting
462	e.g.:	838	the encoding, doing I/O and (most important) communicating this to all
463		839	applications so everybody agrees on character properties such as width
464	@@RXVT_NAME@@ -fn basefont,font2,font3...	840	and code number. This mechanism is the I<locale>. Applications not using
465		841	that info will have problems (for example, C<xterm> gets the width of
466	When rxvt-unicode sees a character, it will first look at the base	842	characters wrong as it uses it's own, locale-independent table under all
467	font. If the base font does not contain the character, it will go to the
468	next font, and so on. Specifying your own fonts will also speed up this
469	search and use less resources within rxvt-unicode and the X-server.
470
471	The only limitation is that none of the fonts may be larger than the base
472	font, as the base font defines the terminal character cell size, which
473	must be the same due to the way terminals work.
474
475	=head2 Why do some chinese characters look so different than others?
476
477	This is because there is a difference between script and language --
478	rxvt-unicode does not know which language the text that is output is,
479	as it only knows the unicode character codes. If rxvt-unicode first
480	sees a japanese/chinese character, it might choose a japanese font for
481	display. Subsequent japanese characters will use that font. Now, many
482	chinese characters aren't represented in japanese fonts, so when the first
483	non-japanese character comes up, rxvt-unicode will look for a chinese font
484	-- unfortunately at this point, it will still use the japanese font for
485	chinese characters that are also in the japanese font.
486
487	The workaround is easy: just tag a chinese font at the end of your font
488	list (see the previous question). The key is to view the font list as
489	a preference list: If you expect more japanese, list a japanese font
490	first. If you expect more chinese, put a chinese font first.
491
492	In the future it might be possible to switch language preferences at
493	runtime (the internal data structure has no problem with using different
494	fonts for the same character at the same time, but no interface for this
495	has been designed yet).
496
497	Until then, you might get away with switching fonts at runtime (see L<Can
498	I switch the fonts at runtime?> later in this document).
499
500	=head2 Why does rxvt-unicode sometimes leave pixel droppings?
501
502	Most fonts were not designed for terminal use, which means that character
503	size varies a lot. A font that is otherwise fine for terminal use might
504	contain some characters that are simply too wide. Rxvt-unicode will avoid
505	these characters. For characters that are just "a bit" too wide a special
506	"careful" rendering mode is used that redraws adjacent characters.
507
508	All of this requires that fonts do not lie about character sizes,
509	however: Xft fonts often draw glyphs larger than their acclaimed bounding
510	box, and rxvt-unicode has no way of detecting this (the correct way is to
511	ask for the character bounding box, which unfortunately is wrong in these
512	cases).	843	locales).
513		844
514	It's not clear (to me at least), wether this is a bug in Xft, freetype,	845	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
515	or the respective font. If you encounter this problem you might try using	846	programs doing the same (that is, most) will automatically agree in the
516	the C<-lsp> option to give the font more height. If that doesn't work, you	847	interpretation of characters.
517	might be forced to use a different font.
518		848
519	All of this is not a problem when using X11 core fonts, as their bounding	849	Unfortunately, there is no system-independent way to select locales, nor
520	box data is correct.	850	is there a standard on how locale specifiers will look like.
521		851
		852	On most systems, the content of the C<LC_CTYPE> environment variable
		853	contains an arbitrary string which corresponds to an already-installed
		854	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		855	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		856	(i.e. C<de> or C<german>) are also common.
		857
		858	Rxvt-unicode ignores all other locale categories, and except for
		859	the encoding, ignores country or language-specific settings,
		860	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		861	rxvt-unicode.
		862
		863	If you want to use a specific encoding you have to make sure you start
		864	rxvt-unicode with the correct C<LC_CTYPE> category.
		865
		866	=head3 Can I switch locales at runtime?
		867
		868	Yes, using an escape sequence. Try something like this, which sets
		869	rxvt-unicode's idea of C<LC_CTYPE>.
		870
		871	printf '\e]701;%s\007' ja_JP.SJIS
		872
		873	See also the previous answer.
		874
		875	Sometimes this capability is rather handy when you want to work in
		876	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		877	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		878	first switches to a locale supported by xjdic and back later:
		879
		880	printf '\e]701;%s\007' ja_JP.SJIS
		881	xjdic -js
		882	printf '\e]701;%s\007' de_DE.UTF-8
		883
		884	You can also use xterm's C<luit> program, which usually works fine, except
		885	for some locales where character width differs between program- and
		886	rxvt-unicode-locales.
		887
		888	=head3 I have problems getting my input method working.
		889
		890	Try a search engine, as this is slightly different for every input method server.
		891
		892	Here is a checklist:
		893
		894	=over 4
		895
		896	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		897
		898	Try C<locale -a> or check the documentation for your OS.
		899
		900	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		901
		902	For example, B<kinput2> does not support UTF-8 locales, you should use
		903	C<ja_JP.EUC-JP> or equivalent.
		904
		905	=item - Make sure your XIM server is actually running.
		906
		907	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		908
		909	When you want to use e.g. B<kinput2>, it must be set to
		910	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input
		911	method servers are running with this command:
		912
		913	xprop -root XIM_SERVERS
		914
		915	=item
		916
		917	=back
		918
		919	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		920
		921	You can specify separate locales for the input method and the rest of the
		922	terminal, using the resource C<imlocale>:
		923
		924	URxvt.imlocale: ja_JP.EUC-JP
		925
		926	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		927	use your input method. Please note, however, that, depending on your Xlib
		928	version, you may not be able to input characters outside C<EUC-JP> in a
		929	normal way then, as your input method limits you.
		930
		931	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		932
		933	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		934	design. Applications can avoid some crashes at the expense of memory
		935	leaks, and Input Methods can avoid some crashes by careful ordering at
		936	exit time. B<kinput2> (and derived input methods) generally succeeds,
		937	while B<SCIM> (or similar input methods) fails. In the end, however,
		938	crashes cannot be completely avoided even if both sides cooperate.
		939
		940	So the only workaround is not to kill your Input Method Servers.
		941
		942
		943	=head2 Operating Systems / Package Maintaining
		944
		945	=head3 I am using Debian GNU/Linux and have a problem...
		946
		947	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		948	patches that considerably change the behaviour of rxvt-unicode (but
		949	unfortunately this notice has been removed). Before reporting a bug to
		950	the original rxvt-unicode author please download and install the genuine
		951	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		952	the problem. If you cannot, chances are that the problems are specific to
		953	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		954	Tracking System (use C<reportbug> to report the bug).
		955
		956	For other problems that also affect the Debian package, you can and
		957	probably should use the Debian BTS, too, because, after all, it's also a
		958	bug in the Debian version and it serves as a reminder for other users that
		959	might encounter the same issue.
		960
		961	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		962
		963	You should build one binary with the default options. F<configure>
		964	now enables most useful options, and the trend goes to making them
		965	runtime-switchable, too, so there is usually no drawback to enbaling them,
		966	except higher disk and possibly memory usage. The perl interpreter should
		967	be enabled, as important functionality (menus, selection, likely more in
		968	the future) depends on it.
		969
		970	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		971	system-wide (except maybe with C<defaults>). This will result in useful
		972	behaviour. If your distribution aims at low memory, add an empty
		973	C<perl-ext-common> resource to the app-defaults file. This will keep the
		974	perl interpreter disabled until the user enables it.
		975
		976	If you can/want build more binaries, I recommend building a minimal
		977	one with C<--disable-everything> (very useful) and a maximal one with
		978	C<--enable-everything> (less useful, it will be very big due to a lot of
		979	encodings built-in that increase download times and are rarely used).
		980
		981	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		982
		983	It should be, starting with release 7.1. You are encouraged to properly
		984	install urxvt with privileges necessary for your OS now.
		985
		986	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		987	into a helper process for privileged operations (pty handling on some
		988	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		989	immediately. This is much safer than most other terminals that keep
		990	privileges while running (but is more relevant to urxvt, as it contains
		991	things as perl interpreters, which might be "helpful" to attackers).
		992
		993	This forking is done as the very first within main(), which is very early
		994	and reduces possible bugs to initialisation code run before main(), or
		995	things like the dynamic loader of your system, which should result in very
		996	little risk.
		997
522	=head2 On Solaris 9, many line-drawing characters are too wide.	998	=head3 On Solaris 9, many line-drawing characters are too wide.
523		999
524	Seems to be a known bug, read	1000	Seems to be a known bug, read
525	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1001	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
526	following ugly workaround to get non-double-wide-characters working:	1002	following ugly workaround to get non-double-wide-characters working:
527		1003
528	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1004	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
529		1005
530	=head2 My Compose (Multi_key) key is no longer working.
531
532	The most common causes for this are that either your locale is not set
533	correctly, or you specified a B<preeditStyle> that is not supported by
534	your input method. For example, if you specified B<OverTheSpot> and
535	your input method (e.g. the default input method handling Compose keys)
536	does not support this (for instance because it is not visual), then
537	rxvt-unicode will continue without an input method.
538
539	In this case either do not specify a B<preeditStyle> or specify more than
540	one pre-edit style, such as B<OverTheSpot,Root,None>.
541
542	=head2 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
543
544	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
545	international keyboards) or simply use ISO 14755 support to your
546	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
547	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
548	character and so on.
549
550	=head2 How can I keep rxvt-unicode from using reverse video so much?
551
552	First of all, make sure you are running with the right terminal settings
553	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
554	make sure you have specified colours for italic and bold, as otherwise
555	rxvt-unicode might use reverse video to simulate the effect:
556
557	URxvt.colorBD: white
558	URxvt.colorIT: green
559
560	=head2 Some programs assume totally weird colours (red instead of blue), how can I fix that?
561
562	For some unexplainable reason, some rare programs assume a very weird
563	colour palette when confronted with a terminal with more than the standard
564	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
565	these programs not to assume non-ISO colours without very good reasons.
566
567	In the meantime, you can either edit your C<rxvt-unicode> terminfo
568	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
569	fix colours but keep you from using other rxvt-unicode features.
570
571	=head2 I am on FreeBSD and rxvt-unicode does not seem to work at all.	1006	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
572		1007
573	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1008	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
574	in your compile environment, or an implementation that implements it,	1009	in your compile environment, or an implementation that implements it,
575	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1010	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
576	B<wchar_t> is represented as unicode.	1011	B<wchar_t> is represented as unicode.
…		…
598		1033
599	The rxvt-unicode author insists that the right way to fix this is in the	1034	The rxvt-unicode author insists that the right way to fix this is in the
600	system libraries once and for all, instead of forcing every app to carry	1035	system libraries once and for all, instead of forcing every app to carry
601	complete replacements for them :)	1036	complete replacements for them :)
602		1037
603	=head2 I use Solaris 9 and it doesn't compile/work/etc.	1038	=head3 I use Solaris 9 and it doesn't compile/work/etc.
604		1039
605	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1040	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
606	problems with C<wcwidth> and a compile problem.	1041	problems with C<wcwidth> and a compile problem.
607		1042
608	=head2 How can I use rxvt-unicode under cygwin?	1043	=head3 How can I use rxvt-unicode under cygwin?
609		1044
610	rxvt-unicode should compile and run out of the box on cygwin, using	1045	rxvt-unicode should compile and run out of the box on cygwin, using
611	the X11 libraries that come with cygwin. libW11 emulation is no	1046	the X11 libraries that come with cygwin. libW11 emulation is no
612	longer supported (and makes no sense, either, as it only supported a	1047	longer supported (and makes no sense, either, as it only supported a
613	single font). I recommend starting the X-server in C<-multiwindow> or	1048	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
616		1051
617	At the time of this writing, cygwin didn't seem to support any multi-byte	1052	At the time of this writing, cygwin didn't seem to support any multi-byte
618	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1053	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
619	to 8-bit encodings.	1054	to 8-bit encodings.
620		1055
621	=head2 How does rxvt-unicode determine the encoding to use?
622
623	=head2 Is there an option to switch encodings?
624
625	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
626	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
627	UTF-8 or any other encodings with respect to terminal I/O.
628
629	The reasons is that there exists a perfectly fine mechanism for selecting
630	the encoding, doing I/O and (most important) communicating this to all
631	applications so everybody agrees on character properties such as width
632	and code number. This mechanism is the I<locale>. Applications not using
633	that info will have problems (for example, C<xterm> gets the width of
634	characters wrong as it uses it's own, locale-independent table under all
635	locales).
636
637	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
638	programs doing the same (that is, most) will automatically agree in the
639	interpretation of characters.
640
641	Unfortunately, there is no system-independent way to select locales, nor
642	is there a standard on how locale specifiers will look like.
643
644	On most systems, the content of the C<LC_CTYPE> environment variable
645	contains an arbitrary string which corresponds to an already-installed
646	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
647	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
648	(i.e. C<de> or C<german>) are also common.
649
650	Rxvt-unicode ignores all other locale categories, and except for
651	the encoding, ignores country or language-specific settings,
652	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
653	rxvt-unicode.
654
655	If you want to use a specific encoding you have to make sure you start
656	rxvt-unicode with the correct C<LC_CTYPE> category.
657
658	=head2 Can I switch locales at runtime?
659
660	Yes, using an escape sequence. Try something like this, which sets
661	rxvt-unicode's idea of C<LC_CTYPE>.
662
663	printf '\e]701;%s\007' ja_JP.SJIS
664
665	See also the previous answer.
666
667	Sometimes this capability is rather handy when you want to work in
668	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
669	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
670	first switches to a locale supported by xjdic and back later:
671
672	printf '\e]701;%s\007' ja_JP.SJIS
673	xjdic -js
674	printf '\e]701;%s\007' de_DE.UTF-8
675
676	You can also use xterm's C<luit> program, which usually works fine, except
677	for some locales where character width differs between program- and
678	rxvt-unicode-locales.
679
680	=head2 Can I switch the fonts at runtime?
681
682	Yes, using an escape sequence. Try something like this, which has the same
683	effect as using the C<-fn> switch, and takes effect immediately:
684
685	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
686
687	This is useful if you e.g. work primarily with japanese (and prefer a
688	japanese font), but you have to switch to chinese temporarily, where
689	japanese fonts would only be in your way.
690
691	You can think of this as a kind of manual ISO-2022 switching.
692
693	=head2 Why do italic characters look as if clipped?
694
695	Many fonts have difficulties with italic characters and hinting. For
696	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
697	Mono> completely fails in it's italic face. A workaround might be to
698	enable freetype autohinting, i.e. like this:
699
700	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
701	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
702
703	=head2 My input method wants <some encoding> but I want UTF-8, what can I do?
704
705	You can specify separate locales for the input method and the rest of the
706	terminal, using the resource C<imlocale>:
707
708	URxvt.imlocale: ja_JP.EUC-JP
709
710	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
711	use your input method. Please note, however, that you will not be able to
712	input characters outside C<EUC-JP> in a normal way then, as your input
713	method limits you.
714
715	=head2 Rxvt-unicode crashes when the X Input Method changes or exits.
716
717	Unfortunately, this is unavoidable, as the XIM protocol is racy by
718	design. Applications can avoid some crashes at the expense of memory
719	leaks, and Input Methods can avoid some crashes by careful ordering at
720	exit time. B<kinput2> (and derived input methods) generally succeeds,
721	while B<SCIM> (or similar input methods) fails. In the end, however,
722	crashes cannot be completely avoided even if both sides cooperate.
723
724	So the only workaround is not to kill your Input Method Servers.
725
726	=head2 Rxvt-unicode uses gobs of memory, how can I reduce that?
727
728	Rxvt-unicode tries to obey the rule of not charging you for something you
729	don't use. One thing you should try is to configure out all settings that
730	you don't need, for example, Xft support is a resource hog by design,
731	when used. Compiling it out ensures that no Xft font will be loaded
732	accidentally when rxvt-unicode tries to find a font for your characters.
733
734	Also, many people (me included) like large windows and even larger
735	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
736	6 bytes per screen cell. For a 160x?? window this amounts to almost a
737	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
738	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
739	rxvt-unicode then uses 8 bytes per screen cell.
740
741	=head2 Can I speed up Xft rendering somehow?
742
743	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
744	it is simply slow. If you still want Xft fonts you might try to disable
745	antialiasing (by appending C<:antialias=false>), which saves lots of
746	memory and also speeds up rendering considerably.
747
748	=head2 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
749
750	Rxvt-unicode will use whatever you specify as a font. If it needs to
751	fall back to it's default font search list it will prefer X11 core
752	fonts, because they are small and fast, and then use Xft fonts. It has
753	antialiasing disabled for most of them, because the author thinks they
754	look best that way.
755
756	If you want antialiasing, you have to specify the fonts manually.
757
758	=head2 Mouse cut/paste suddenly no longer works.
759
760	Make sure that mouse reporting is actually turned off since killing
761	some editors prematurely may leave the mouse in mouse report mode. I've
762	heard that tcsh may use mouse reporting unless it otherwise specified. A
763	quick check is to see if cut/paste works when the Alt or Shift keys are
764	depressed.
765
766	=head2 What's with this bold/blink stuff?
767
768	If no bold colour is set via C<colorBD:>, bold will invert text using the
769	standard foreground colour.
770
771	For the standard background colour, blinking will actually make the
772	text blink when compiled with C<--enable-blinking>. with standard
773	colours. Without C<--enable-blinking>, the blink attribute will be
774	ignored.
775
776	On ANSI colours, bold/blink attributes are used to set high-intensity
777	foreground/background colors.
778
779	color0-7 are the low-intensity colors.
780
781	color8-15 are the corresponding high-intensity colors.
782
783	=head2 I don't like the screen colors. How do I change them?
784
785	You can change the screen colors at run-time using F<~/.Xdefaults>
786	resources (or as long-options).
787
788	Here are values that are supposed to resemble a VGA screen,
789	including the murky brown that passes for low-intensity yellow:
790
791	URxvt.color0: #000000
792	URxvt.color1: #A80000
793	URxvt.color2: #00A800
794	URxvt.color3: #A8A800
795	URxvt.color4: #0000A8
796	URxvt.color5: #A800A8
797	URxvt.color6: #00A8A8
798	URxvt.color7: #A8A8A8
799
800	URxvt.color8: #000054
801	URxvt.color9: #FF0054
802	URxvt.color10: #00FF54
803	URxvt.color11: #FFFF54
804	URxvt.color12: #0000FF
805	URxvt.color13: #FF00FF
806	URxvt.color14: #00FFFF
807	URxvt.color15: #FFFFFF
808
809	And here is a more complete set of non-standard colors described (not by
810	me) as "pretty girly".
811
812	URxvt.cursorColor: #dc74d1
813	URxvt.pointerColor: #dc74d1
814	URxvt.background: #0e0e0e
815	URxvt.foreground: #4ad5e1
816	URxvt.color0: #000000
817	URxvt.color8: #8b8f93
818	URxvt.color1: #dc74d1
819	URxvt.color9: #dc74d1
820	URxvt.color2: #0eb8c7
821	URxvt.color10: #0eb8c7
822	URxvt.color3: #dfe37e
823	URxvt.color11: #dfe37e
824	URxvt.color5: #9e88f0
825	URxvt.color13: #9e88f0
826	URxvt.color6: #73f7ff
827	URxvt.color14: #73f7ff
828	URxvt.color7: #e1dddd
829	URxvt.color15: #e1dddd
830
831	=head2 How can I start @@RXVT_NAME@@d in a race-free way?
832
833	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
834	display, create the listening socket and then fork.
835
836	=head2 What's with the strange Backspace/Delete key behaviour?
837
838	Assuming that the physical Backspace key corresponds to the
839	BackSpace keysym (not likely for Linux ... see the following
840	question) there are two standard values that can be used for
841	Backspace: C<^H> and C<^?>.
842
843	Historically, either value is correct, but rxvt-unicode adopts the debian
844	policy of using C<^?> when unsure, because it's the one only only correct
845	choice :).
846
847	Rxvt-unicode tries to inherit the current stty settings and uses the value
848	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
849	started from a terminal (say, from a menu or by remote shell), then the
850	system value of `erase', which corresponds to CERASE in <termios.h>, will
851	be used (which may not be the same as your stty setting).
852
853	For starting a new rxvt-unicode:
854
855	# use Backspace = ^H
856	$ stty erase ^H
857	$ @@RXVT_NAME@@
858
859	# use Backspace = ^?
860	$ stty erase ^?
861	$ @@RXVT_NAME@@
862
863	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
864
865	For an existing rxvt-unicode:
866
867	# use Backspace = ^H
868	$ stty erase ^H
869	$ echo -n "^[[36h"
870
871	# use Backspace = ^?
872	$ stty erase ^?
873	$ echo -n "^[[36l"
874
875	This helps satisfy some of the Backspace discrepancies that occur, but
876	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
877	properly reflects that.
878
879	The Delete key is a another casualty of the ill-defined Backspace problem.
880	To avoid confusion between the Backspace and Delete keys, the Delete
881	key has been assigned an escape sequence to match the vt100 for Execute
882	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
883
884	Some other Backspace problems:
885
886	some editors use termcap/terminfo,
887	some editors (vim I'm told) expect Backspace = ^H,
888	GNU Emacs (and Emacs-like editors) use ^H for help.
889
890	Perhaps someday this will all be resolved in a consistent manner.
891
892	=head2 I don't like the key-bindings. How do I change them?
893
894	There are some compile-time selections available via configure. Unless
895	you have run "configure" with the C<--disable-resources> option you can
896	use the `keysym' resource to alter the keystrings associated with keysyms.
897
898	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
899
900	URxvt.keysym.Home: \033[1~
901	URxvt.keysym.End: \033[4~
902	URxvt.keysym.C-apostrophe: \033<C-'>
903	URxvt.keysym.C-slash: \033<C-/>
904	URxvt.keysym.C-semicolon: \033<C-;>
905	URxvt.keysym.C-grave: \033<C-`>
906	URxvt.keysym.C-comma: \033<C-,>
907	URxvt.keysym.C-period: \033<C-.>
908	URxvt.keysym.C-0x60: \033<C-`>
909	URxvt.keysym.C-Tab: \033<C-Tab>
910	URxvt.keysym.C-Return: \033<C-Return>
911	URxvt.keysym.S-Return: \033<S-Return>
912	URxvt.keysym.S-space: \033<S-Space>
913	URxvt.keysym.M-Up: \033<M-Up>
914	URxvt.keysym.M-Down: \033<M-Down>
915	URxvt.keysym.M-Left: \033<M-Left>
916	URxvt.keysym.M-Right: \033<M-Right>
917	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
918	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
919	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
920
921	See some more examples in the documentation for the B<keysym> resource.
922
923	=head2 I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
924	How do I make use of them? For example, the Sun Keyboard type 4
925	has the following mappings that rxvt-unicode doesn't recognize.
926
927	KP_Insert == Insert
928	F22 == Print
929	F27 == Home
930	F29 == Prior
931	F33 == End
932	F35 == Next
933
934	Rather than have rxvt-unicode try to accommodate all the various possible
935	keyboard mappings, it is better to use `xmodmap' to remap the keys as
936	required for your particular machine.
937
938	=head2 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
939	I need this to decide about setting colors etc.
940
941	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
942	check and see if that is set. Note that several programs, JED, slrn,
943	Midnight Commander automatically check this variable to decide whether or
944	not to use color.
945
946	=head2 How do I set the correct, full IP address for the DISPLAY variable?
947
948	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
949	insecure mode then it is possible to use the following shell script
950	snippets to correctly set the display. If your version of rxvt-unicode
951	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
952	the COLORTERM variable can be used to distinguish rxvt-unicode from a
953	regular xterm.
954
955	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
956	snippets:
957
958	# Bourne/Korn/POSIX family of shells:
959	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
960	if [ ${TERM:-foo} = xterm ]; then
961	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
962	echo -n '^[Z'
963	read term_id
964	stty icanon echo
965	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
966	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
967	read DISPLAY # set it in our local shell
968	fi
969	fi
970
971	=head2 How do I compile the manual pages for myself?
972
973	You need to have a recent version of perl installed as F</usr/bin/perl>,
974	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
975	the doc subdirectory and enter C<make alldoc>.
976
977	=head2 My question isn't answered here, can I ask a human?
978
979	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
980	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
981	interested in learning about new and exciting problems (but not FAQs :).
982
983	=head1 RXVT TECHNICAL REFERENCE	1056	=head1 RXVT-UNICODE TECHNICAL REFERENCE
984
985	=head1 DESCRIPTION
986		1057
987	The rest of this document describes various technical aspects of	1058	The rest of this document describes various technical aspects of
988	B<rxvt-unicode>. First the description of supported command sequences,	1059	B<rxvt-unicode>. First the description of supported command sequences,
989	followed by pixmap support and last by a description of all features	1060	followed by pixmap support and last by a description of all features
990	selectable at C<configure> time.	1061	selectable at C<configure> time.
991		1062
992	=head1 Definitions	1063	=head2 Definitions
993		1064
994	=over 4	1065	=over 4
995		1066
996	=item B<< C<c> >>	1067	=item B<< C<c> >>
997		1068
…		…
1015		1086
1016	A text parameter composed of printable characters.	1087	A text parameter composed of printable characters.
1017		1088
1018	=back	1089	=back
1019		1090
1020	=head1 Values	1091	=head2 Values
1021		1092
1022	=over 4	1093	=over 4
1023		1094
1024	=item B<< C<ENQ> >>	1095	=item B<< C<ENQ> >>
1025		1096
…		…
1068		1139
1069	Space Character	1140	Space Character
1070		1141
1071	=back	1142	=back
1072		1143
1073	=head1 Escape Sequences	1144	=head2 Escape Sequences
1074		1145
1075	=over 4	1146	=over 4
1076		1147
1077	=item B<< C<ESC # 8> >>	1148	=item B<< C<ESC # 8> >>
1078		1149
…		…
1176		1247
1177	=back	1248	=back
1178		1249
1179	X<CSI>	1250	X<CSI>
1180		1251
1181	=head1 CSI (Command Sequence Introducer) Sequences	1252	=head2 CSI (Command Sequence Introducer) Sequences
1182		1253
1183	=over 4	1254	=over 4
1184		1255
1185	=item B<< C<ESC [ Ps @> >>	1256	=item B<< C<ESC [ Ps @> >>
1186		1257
…		…
1456		1527
1457	=back	1528	=back
1458		1529
1459	X<PrivateModes>	1530	X<PrivateModes>
1460		1531
1461	=head1 DEC Private Modes	1532	=head2 DEC Private Modes
1462		1533
1463	=over 4	1534	=over 4
1464		1535
1465	=item B<< C<ESC [ ? Pm h> >>	1536	=item B<< C<ESC [ ? Pm h> >>
1466		1537
…		…
1730		1801
1731	=back	1802	=back
1732		1803
1733	X<XTerm>	1804	X<XTerm>
1734		1805
1735	=head1 XTerm Operating System Commands	1806	=head2 XTerm Operating System Commands
1736		1807
1737	=over 4	1808	=over 4
1738		1809
1739	=item B<< C<ESC ] Ps;Pt ST> >>	1810	=item B<< C<ESC ] Ps;Pt ST> >>
1740		1811
…		…
1778		1849
1779	=end table	1850	=end table
1780		1851
1781	=back	1852	=back
1782		1853
1783	X<XPM>
1784
1785	=head1 XPM	1854	=head1 XPM
1786		1855
1787	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1856	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1788	of B<< C<Pt> >> can be the name of the background pixmap followed by a	1857	of B<< C<Pt> >> can be the name of the background pixmap followed by a
1789	sequence of scaling/positioning commands separated by semi-colons. The	1858	sequence of scaling/positioning commands separated by semi-colons. The
…		…
1886	=begin table	1955	=begin table
1887		1956
1888	4 Shift	1957	4 Shift
1889	8 Meta	1958	8 Meta
1890	16 Control	1959	16 Control
1891	32 Double Click I<(Rxvt extension)>	1960	32 Double Click I<(rxvt extension)>
1892		1961
1893	=end table	1962	=end table
1894		1963
1895	Col = B<< C<< <x> - SPACE >> >>	1964	Col = B<< C<< <x> - SPACE >> >>
1896		1965
…		…
2224	Remove support for mouse selection style like that of xterm.	2293	Remove support for mouse selection style like that of xterm.
2225		2294
2226	=item --enable-dmalloc (default: off)	2295	=item --enable-dmalloc (default: off)
2227		2296
2228	Use Gray Watson's malloc - which is good for debugging See	2297	Use Gray Watson's malloc - which is good for debugging See
2229	http://www.letters.com/dmalloc/ for details If you use either this or the	2298	L<http://www.letters.com/dmalloc/> for details If you use either this or the
2230	next option, you may need to edit src/Makefile after compiling to point	2299	next option, you may need to edit src/Makefile after compiling to point
2231	DINCLUDE and DLIB to the right places.	2300	DINCLUDE and DLIB to the right places.
2232		2301
2233	You can only use either this option and the following (should	2302	You can only use either this option and the following (should
2234	you use either) .	2303	you use either) .

Diff Legend

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