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.155 by ayin, Sun Dec 9 12:15:39 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	=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 whether 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<pod2xhtml> (from
		131	F<Pod::Xhtml>). Then go to 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 unreasonably 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
170	1035683 49680 66648 29096 3680 urxvt --enable-everything	153	1035683 49680 66648 29096 3680 urxvt --enable-everything
171		154
…		…
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++.
…		…
214		197
215	And here is rxvt-unicode:	198	And here is rxvt-unicode:
216		199
217	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	200	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
218	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)	201	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
219	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)	202	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
220	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)	203	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
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, please address all transparency related issues to Sasha Vasko at
		215	sasha@aftercode.net and do not bug the author about it. Also, if you can't
		216	get it working consider it a rite of passage: ... and you failed.
		217
		218	Here are four ways to get transparency. B<Do> read the manpage and option
		219	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
		220
		221	1. Use transparent mode:
		222
		223	Esetroot wallpaper.jpg
		224	@@URXVT_NAME@@ -tr -tint red -sh 40
		225
		226	That works. If you think it doesn't, you lack transparency and tinting
		227	support, or you are unable to read.
		228
		229	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		230	to use effects other than tinting and shading: Just shade/tint/whatever
		231	your picture with gimp or any other tool:
		232
		233	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
		234	@@URXVT_NAME@@ -pixmap "background.jpg;:root"
		235
		236	That works. If you think it doesn't, you lack AfterImage support, or you
		237	are unable to read.
		238
		239	3. Use an ARGB visual:
		240
		241	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		242
		243	This requires XFT support, and the support of your X-server. If that
		244	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		245	there yet, no matter what they claim. Rxvt-Unicode contains the necessary
		246	bugfixes and workarounds for Xft and Xlib to make it work, but that
		247	doesn't mean that your WM has the required kludges in place.
		248
		249	4. Use xcompmgr and let it do the job:
		250
		251	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		252	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		253
		254	Then click on a window you want to make transparent. Replace C<0xc0000000>
		255	by other values to change the degree of opacity. If it doesn't work and
		256	your server crashes, you got to keep the pieces.
		257
		258	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		259
		260	Most fonts were not designed for terminal use, which means that character
		261	size varies a lot. A font that is otherwise fine for terminal use might
		262	contain some characters that are simply too wide. Rxvt-unicode will avoid
		263	these characters. For characters that are just "a bit" too wide a special
		264	"careful" rendering mode is used that redraws adjacent characters.
		265
		266	All of this requires that fonts do not lie about character sizes,
		267	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		268	box, and rxvt-unicode has no way of detecting this (the correct way is to
		269	ask for the character bounding box, which unfortunately is wrong in these
		270	cases).
		271
		272	It's not clear (to me at least), whether this is a bug in Xft, freetype,
		273	or the respective font. If you encounter this problem you might try using
		274	the C<-lsp> option to give the font more height. If that doesn't work, you
		275	might be forced to use a different font.
		276
		277	All of this is not a problem when using X11 core fonts, as their bounding
		278	box data is correct.
		279
		280	=head3 How can I keep rxvt-unicode from using reverse video so much?
		281
		282	First of all, make sure you are running with the right terminal settings
		283	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		284	make sure you have specified colours for italic and bold, as otherwise
		285	rxvt-unicode might use reverse video to simulate the effect:
		286
		287	URxvt.colorBD: white
		288	URxvt.colorIT: green
		289
		290	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		291
		292	For some unexplainable reason, some rare programs assume a very weird
		293	colour palette when confronted with a terminal with more than the standard
		294	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		295	these programs not to assume non-ISO colours without very good reasons.
		296
		297	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		298	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		299	fix colours but keep you from using other rxvt-unicode features.
		300
		301	=head3 Can I switch the fonts at runtime?
		302
		303	Yes, using an escape sequence. Try something like this, which has the same
		304	effect as using the C<-fn> switch, and takes effect immediately:
		305
		306	printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
		307
		308	This is useful if you e.g. work primarily with japanese (and prefer a
		309	japanese font), but you have to switch to chinese temporarily, where
		310	japanese fonts would only be in your way.
		311
		312	You can think of this as a kind of manual ISO-2022 switching.
		313
		314	=head3 Why do italic characters look as if clipped?
		315
		316	Many fonts have difficulties with italic characters and hinting. For
		317	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		318	Mono> completely fails in its italic face. A workaround might be to
		319	enable freetype autohinting, i.e. like this:
		320
		321	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		322	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		323
		324	=head3 Can I speed up Xft rendering somehow?
		325
		326	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		327	it is simply slow. If you still want Xft fonts you might try to disable
		328	antialiasing (by appending C<:antialias=false>), which saves lots of
		329	memory and also speeds up rendering considerably.
		330
		331	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		332
		333	Rxvt-unicode will use whatever you specify as a font. If it needs to
		334	fall back to its default font search list it will prefer X11 core
		335	fonts, because they are small and fast, and then use Xft fonts. It has
		336	antialiasing disabled for most of them, because the author thinks they
		337	look best that way.
		338
		339	If you want antialiasing, you have to specify the fonts manually.
		340
		341	=head3 What's with this bold/blink stuff?
		342
		343	If no bold colour is set via C<colorBD:>, bold will invert text using the
		344	standard foreground colour.
		345
		346	For the standard background colour, blinking will actually make
		347	the text blink when compiled with C<--enable-text-blink>. Without
		348	C<--enable-text-blink>, the blink attribute will be ignored.
		349
		350	On ANSI colours, bold/blink attributes are used to set high-intensity
		351	foreground/background colors.
		352
		353	color0-7 are the low-intensity colors.
		354
		355	color8-15 are the corresponding high-intensity colors.
		356
		357	=head3 I don't like the screen colors. How do I change them?
		358
		359	You can change the screen colors at run-time using F<~/.Xdefaults>
		360	resources (or as long-options).
		361
		362	Here are values that are supposed to resemble a VGA screen,
		363	including the murky brown that passes for low-intensity yellow:
		364
		365	URxvt.color0: #000000
		366	URxvt.color1: #A80000
		367	URxvt.color2: #00A800
		368	URxvt.color3: #A8A800
		369	URxvt.color4: #0000A8
		370	URxvt.color5: #A800A8
		371	URxvt.color6: #00A8A8
		372	URxvt.color7: #A8A8A8
		373
		374	URxvt.color8: #000054
		375	URxvt.color9: #FF0054
		376	URxvt.color10: #00FF54
		377	URxvt.color11: #FFFF54
		378	URxvt.color12: #0000FF
		379	URxvt.color13: #FF00FF
		380	URxvt.color14: #00FFFF
		381	URxvt.color15: #FFFFFF
		382
		383	And here is a more complete set of non-standard colors.
		384
		385	URxvt.cursorColor: #dc74d1
		386	URxvt.pointerColor: #dc74d1
		387	URxvt.background: #0e0e0e
		388	URxvt.foreground: #4ad5e1
		389	URxvt.color0: #000000
		390	URxvt.color8: #8b8f93
		391	URxvt.color1: #dc74d1
		392	URxvt.color9: #dc74d1
		393	URxvt.color2: #0eb8c7
		394	URxvt.color10: #0eb8c7
		395	URxvt.color3: #dfe37e
		396	URxvt.color11: #dfe37e
		397	URxvt.color5: #9e88f0
		398	URxvt.color13: #9e88f0
		399	URxvt.color6: #73f7ff
		400	URxvt.color14: #73f7ff
		401	URxvt.color7: #e1dddd
		402	URxvt.color15: #e1dddd
		403
		404	They have been described (not by me) as "pretty girly".
		405
		406	=head3 Why do some characters look so much different than others?
		407
		408	See next entry.
		409
		410	=head3 How does rxvt-unicode choose fonts?
		411
		412	Most fonts do not contain the full range of Unicode, which is
		413	fine. Chances are that the font you (or the admin/package maintainer of
		414	your system/os) have specified does not cover all the characters you want
		415	to display.
		416
		417	B<rxvt-unicode> makes a best-effort try at finding a replacement
		418	font. Often the result is fine, but sometimes the chosen font looks
		419	bad/ugly/wrong. Some fonts have totally strange characters that don't
		420	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		421	intelligence to detect that a specific glyph is wrong: it has to believe
		422	the font that the characters it claims to contain indeed look correct.
		423
		424	In that case, select a font of your taste and add it to the font list,
		425	e.g.:
		426
		427	@@URXVT_NAME@@ -fn basefont,font2,font3...
		428
		429	When rxvt-unicode sees a character, it will first look at the base
		430	font. If the base font does not contain the character, it will go to the
		431	next font, and so on. Specifying your own fonts will also speed up this
		432	search and use less resources within rxvt-unicode and the X-server.
		433
		434	The only limitation is that none of the fonts may be larger than the base
		435	font, as the base font defines the terminal character cell size, which
		436	must be the same due to the way terminals work.
		437
		438	=head3 Why do some chinese characters look so different than others?
		439
		440	This is because there is a difference between script and language --
		441	rxvt-unicode does not know which language the text that is output is,
		442	as it only knows the unicode character codes. If rxvt-unicode first
		443	sees a japanese/chinese character, it might choose a japanese font for
		444	display. Subsequent japanese characters will use that font. Now, many
		445	chinese characters aren't represented in japanese fonts, so when the first
		446	non-japanese character comes up, rxvt-unicode will look for a chinese font
		447	-- unfortunately at this point, it will still use the japanese font for
		448	chinese characters that are also in the japanese font.
		449
		450	The workaround is easy: just tag a chinese font at the end of your font
		451	list (see the previous question). The key is to view the font list as
		452	a preference list: If you expect more japanese, list a japanese font
		453	first. If you expect more chinese, put a chinese font first.
		454
		455	In the future it might be possible to switch language preferences at
		456	runtime (the internal data structure has no problem with using different
		457	fonts for the same character at the same time, but no interface for this
		458	has been designed yet).
		459
		460	Until then, you might get away with switching fonts at runtime (see L<Can
		461	I switch the fonts at runtime?> later in this document).
		462
		463	=head3 How can I make mplayer display video correctly?
		464
		465	We are working on it, in the meantime, as a workaround, use something like:
		466
		467	@@URXVT_NAME@@ -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		468
		469
		470	=head2 Keyboard, Mouse & User Interaction
		471
		472	=head3 The new selection selects pieces that are too big, how can I select single words?
		473
		474	If you want to select e.g. alphanumeric words, you can use the following
		475	setting:
		476
		477	URxvt.selection.pattern-0: ([[:word:]]+)
		478
		479	If you click more than twice, the selection will be extended
		480	more and more.
		481
		482	To get a selection that is very similar to the old code, try this pattern:
		483
		484	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		485
		486	Please also note that the I<LeftClick Shift-LeftClik> combination also
		487	selects words like the old code.
		488
		489	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		490
		491	You can disable the perl extension completely by setting the
		492	B<perl-ext-common> resource to the empty string, which also keeps
		493	rxvt-unicode from initialising perl, saving memory.
		494
		495	If you only want to disable specific features, you first have to
		496	identify which perl extension is responsible. For this, read the section
		497	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		498	example, to disable the B<selection-popup> and B<option-popup>, specify
		499	this B<perl-ext-common> resource:
		500
		501	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		502
		503	This will keep the default extensions, but disable the two popup
		504	extensions. Some extensions can also be configured, for example,
		505	scrollback search mode is triggered by B<M-s>. You can move it to any
		506	other combination either by setting the B<searchable-scrollback> resource:
		507
		508	URxvt.searchable-scrollback: CM-s
		509
		510	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		511
		512	See next entry.
		513
		514	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		515
		516	These are caused by the C<readline> perl extension. Under normal
		517	circumstances, it will move your cursor around when you click into the
		518	line that contains it. It tries hard not to do this at the wrong moment,
		519	but when running a program that doesn't parse cursor movements or in some
		520	cases during rlogin sessions, it fails to detect this properly.
		521
		522	You can permanently switch this feature off by disabling the C<readline>
		523	extension:
		524
234	URxvt.perl-ext-common: default,tabbed	525	URxvt.perl-ext-common: default,-readline
235		526
236	It will also work fine with tabbing functionality of many window managers	527	=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		528
242	=head2 How do I know which rxvt-unicode version I'm using?	529	Some Debian GNUL/Linux users seem to have this problem, although no
		530	specific details were reported so far. It is possible that this is caused
		531	by the wrong C<TERM> setting, although the details of whether and how
		532	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		533	keymap. See the answer to the previous question, and please report if that
		534	helped.
243		535
244	The version number is displayed with the usage (-h). Also the escape	536	=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		537
249	=head2 I am using Debian GNU/Linux and have a problem...	538	The most common causes for this are that either your locale is not set
		539	correctly, or you specified a B<preeditStyle> that is not supported by
		540	your input method. For example, if you specified B<OverTheSpot> and
		541	your input method (e.g. the default input method handling Compose keys)
		542	does not support this (for instance because it is not visual), then
		543	rxvt-unicode will continue without an input method.
250		544
251	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	545	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	546	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		547
260	For other problems that also affect the Debian package, you can and	548	=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		549
265	=head2 I am maintaining rxvt-unicode for distribution/OS XXX, any	550	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
266	recommendation?	551	international keyboards) or simply use ISO 14755 support to your
		552	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		553	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		554	character and so on.
267		555
268	You should build one binary with the default options. F<configure>	556	=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		557
275	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	558	Make sure that mouse reporting is actually turned off since killing
276	system-wide (except maybe with C<defaults>). This will result in useful	559	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	560	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	561	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.	562	depressed.
280		563
281	If you can/want build more binaries, I recommend building a minimal	564	=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		565
286	=head2 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	566	Assuming that the physical Backspace key corresponds to the
		567	Backspace keysym (not likely for Linux ... see the following
		568	question) there are two standard values that can be used for
		569	Backspace: C<^H> and C<^?>.
287		570
288	It should be, starting with release 7.1. You are encouraged to properly	571	Historically, either value is correct, but rxvt-unicode adopts the debian
289	install urxvt with privileges necessary for your OS now.	572	policy of using C<^?> when unsure, because it's the one and only correct
		573	choice :).
290		574
291	When rxvt-unicode detects that it runs setuid or setgid, it will fork	575	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	576	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
293	systems, utmp/wtmp/lastlog handling on others) and drop privileges	577	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	578	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	579	be used (which may not be the same as your stty setting).
296	things as perl interpreters, which might be "helpful" to attackers).
297		580
298	This forking is done as the very first within main(), which is very early	581	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		582
		583	# use Backspace = ^H
		584	$ stty erase ^H
		585	$ @@URXVT_NAME@@
		586
		587	# use Backspace = ^?
		588	$ stty erase ^?
		589	$ @@URXVT_NAME@@
		590
		591	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		592
		593	For an existing rxvt-unicode:
		594
		595	# use Backspace = ^H
		596	$ stty erase ^H
		597	$ echo -n "^[[36h"
		598
		599	# use Backspace = ^?
		600	$ stty erase ^?
		601	$ echo -n "^[[36l"
		602
		603	This helps satisfy some of the Backspace discrepancies that occur, but
		604	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		605	properly reflects that.
		606
		607	The Delete key is a another casualty of the ill-defined Backspace problem.
		608	To avoid confusion between the Backspace and Delete keys, the Delete
		609	key has been assigned an escape sequence to match the vt100 for Execute
		610	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		611
		612	Some other Backspace problems:
		613
		614	some editors use termcap/terminfo,
		615	some editors (vim I'm told) expect Backspace = ^H,
		616	GNU Emacs (and Emacs-like editors) use ^H for help.
		617
		618	Perhaps someday this will all be resolved in a consistent manner.
		619
		620	=head3 I don't like the key-bindings. How do I change them?
		621
		622	There are some compile-time selections available via configure. Unless
		623	you have run "configure" with the C<--disable-resources> option you can
		624	use the `keysym' resource to alter the keystrings associated with keysyms.
		625
		626	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		627
		628	URxvt.keysym.Home: \033[1~
		629	URxvt.keysym.End: \033[4~
		630	URxvt.keysym.C-apostrophe: \033<C-'>
		631	URxvt.keysym.C-slash: \033<C-/>
		632	URxvt.keysym.C-semicolon: \033<C-;>
		633	URxvt.keysym.C-grave: \033<C-`>
		634	URxvt.keysym.C-comma: \033<C-,>
		635	URxvt.keysym.C-period: \033<C-.>
		636	URxvt.keysym.C-0x60: \033<C-`>
		637	URxvt.keysym.C-Tab: \033<C-Tab>
		638	URxvt.keysym.C-Return: \033<C-Return>
		639	URxvt.keysym.S-Return: \033<S-Return>
		640	URxvt.keysym.S-space: \033<S-Space>
		641	URxvt.keysym.M-Up: \033<M-Up>
		642	URxvt.keysym.M-Down: \033<M-Down>
		643	URxvt.keysym.M-Left: \033<M-Left>
		644	URxvt.keysym.M-Right: \033<M-Right>
		645	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		646	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		647	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		648
		649	See some more examples in the documentation for the B<keysym> resource.
		650
		651	=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
		652
		653	KP_Insert == Insert
		654	F22 == Print
		655	F27 == Home
		656	F29 == Prior
		657	F33 == End
		658	F35 == Next
		659
		660	Rather than have rxvt-unicode try to accommodate all the various possible
		661	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		662	required for your particular machine.
		663
		664
		665	=head2 Terminal Configuration
		666
		667	=head3 Can I see a typical configuration?
		668
		669	The default configuration tries to be xterm-like, which I don't like that
		670	much, but it's least surprise to regular users.
		671
		672	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		673	time into customising your terminal. To get you started, here is the
		674	author's .Xdefaults entries, with comments on what they do. It's certainly
		675	not I<typical>, but what's typical...
		676
		677	URxvt.cutchars: "()*,<>[]{}|'
		678	URxvt.print-pipe: cat >/tmp/xxx
		679
		680	These are just for testing stuff.
		681
		682	URxvt.imLocale: ja_JP.UTF-8
		683	URxvt.preeditType: OnTheSpot,None
		684
		685	This tells rxvt-unicode to use a special locale when communicating with
		686	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		687	type, which requires the C<xim-onthespot> perl extension but rewards me
		688	with correct-looking fonts.
		689
		690	URxvt.perl-lib: /root/lib/urxvt
		691	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		692	URxvt.selection.pattern-0: ( at .*? line \\d+)
		693	URxvt.selection.pattern-1: ^(/[^:]+):\
		694	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		695	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		696
		697	This is my perl configuration. The first two set the perl library
		698	directory and also tells urxvt to use a large number of extensions. I
		699	develop for myself mostly, so I actually use most of the extensions I
		700	write.
		701
		702	The selection stuff mainly makes the selection perl-error-message aware
		703	and tells it to convert perl error messages into vi-commands to load the
		704	relevant file and go tot he error line number.
		705
		706	URxvt.scrollstyle: plain
		707	URxvt.secondaryScroll: true
		708
		709	As the documentation says: plain is the preferred scrollbar for the
		710	author. The C<secondaryScroll> configures urxvt to scroll in full-screen
		711	apps, like screen, so lines scrolled out of screen end up in urxvt's
		712	scrollback buffer.
		713
		714	URxvt.background: #000000
		715	URxvt.foreground: gray90
		716	URxvt.color7: gray90
		717	URxvt.colorBD: #ffffff
		718	URxvt.cursorColor: #e0e080
		719	URxvt.throughColor: #8080f0
		720	URxvt.highlightColor: #f0f0f0
		721
		722	Some colours. Not sure which ones are being used or even non-defaults, but
		723	these are in my .Xdefaults. Most notably, they set foreground/background
		724	to light gray/black, and also make sure that the colour 7 matches the
		725	default foreground colour.
		726
		727	URxvt.underlineColor: yellow
		728
		729	Another colour, makes underline lines look different. Sometimes hurts, but
		730	is mostly a nice effect.
		731
		732	URxvt.geometry: 154x36
		733	URxvt.loginShell: false
		734	URxvt.meta: ignore
		735	URxvt.utmpInhibit: true
		736
		737	Uh, well, should be mostly self-explanatory. By specifying some defaults
		738	manually, I can quickly switch them for testing.
		739
		740	URxvt.saveLines: 8192
		741
		742	A large scrollback buffer is essential. Really.
		743
		744	URxvt.mapAlert: true
		745
		746	The only case I use it is for my IRC window, which I like to keep
		747	iconified till people msg me (which beeps).
		748
		749	URxvt.visualBell: true
		750
		751	The audible bell is often annoying, especially when in a crowd.
		752
		753	URxvt.insecure: true
		754
		755	Please don't hack my mutt! Ooops...
		756
		757	URxvt.pastableTabs: false
		758
		759	I once thought this is a great idea.
		760
		761	urxvt.font: 9x15bold,\
		762	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		763	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		764	[codeset=JISX0208]xft:Kochi Gothic, \
		765	xft:Bitstream Vera Sans Mono:autohint=true, \
		766	xft:Code2000:antialias=false
		767	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		768	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		769	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		770
		771	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		772	overwhelmed. A special note: the C<9x15bold> mentioned above is actually
		773	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		774	font (different glyphs for C<;> and many other harmless characters),
		775	while the second font is actually the C<9x15bold> from XFree4/XOrg. The
		776	bold version has less chars than the medium version, so I use it for rare
		777	characters, too. When editing sources with vim, I use italic for comments
		778	and other stuff, which looks quite good with Bitstream Vera anti-aliased.
		779
		780	Terminus is a quite bad font (many very wrong glyphs), but for most of my
		781	purposes, it works, and gives a different look, as my normal (Non-bold)
		782	font is already bold, and I want to see a difference between bold and
		783	normal fonts.
		784
		785	Please note that I used the C<urxvt> instance name and not the C<URxvt>
		786	class name. Thats because I use different configs for different purposes,
		787	for example, my IRC window is started with C<-name IRC>, and uses these
		788	defaults:
		789
		790	IRC*title: IRC
		791	IRC*geometry: 87x12+535+542
		792	IRC*saveLines: 0
		793	IRC*mapAlert: true
		794	IRC*font: suxuseuro
		795	IRC*boldFont: suxuseuro
		796	IRC*colorBD: white
		797	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		798	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		799
		800	C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font
		801	sizes. C<suxuseuro> allows me to keep an eye (and actually read)
		802	stuff while keeping a very small window. If somebody pastes something
		803	complicated (e.g. japanese), I temporarily switch to a larger font.
		804
		805	The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor
		806	C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname>
		807	file for different hosts, for example, on ym main desktop, I use:
		808
		809	URxvt.keysym.C-M-q: command:\033[3;5;5t
		810	URxvt.keysym.C-M-y: command:\033[3;5;606t
		811	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		812	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		813	URxvt.keysym.C-M-p: perl:test
		814
		815	The first for keysym definitions allow me to quickly bring some windows
		816	in the layout I like most. Ion users might start laughing but will stop
		817	immediately when I tell them that I use my own Fvwm2 module for much the
		818	same effect as Ion provides, and I only very rarely use the above key
		819	combinations :->
		820
		821	=head3 Why doesn't rxvt-unicode read my resources?
		822
		823	Well, why, indeed? It does, in a way very similar to other X
		824	applications. Most importantly, this means that if you or your OS loads
		825	resources into the X display (the right way to do it), rxvt-unicode will
		826	ignore any resource files in your home directory. It will only read
		827	F<$HOME/.Xdefaults> when no resources are attached to the display.
		828
		829	If you have or use an F<$HOME/.Xresources> file, chances are that
		830	resources are loaded into your X-server. In this case, you have to
		831	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		832
		833	Also consider the form resources have to use:
		834
		835	URxvt.resource: value
		836
		837	If you want to use another form (there are lots of different ways of
		838	specifying resources), make sure you understand whether and why it
		839	works. If unsure, use the form above.
		840
303	=head2 When I log-in to another system it tells me about missing terminfo data?	841	=head3 When I log-in to another system it tells me about missing terminfo data?
304		842
305	The terminal description used by rxvt-unicode is not as widely available	843	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).	844	as that for xterm, or even rxvt (for which the same problem often arises).
307		845
308	The correct solution for this problem is to install the terminfo, this can	846	The correct solution for this problem is to install the terminfo, this can
309	be done like this (with ncurses' infocmp):	847	be done like this (with ncurses' infocmp and works as user and admin):
310		848
311	REMOTE=remotesystem.domain	849	REMOTE=remotesystem.domain
312	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	850	infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
313		851
314	... or by installing rxvt-unicode normally on the remote system,	852	... or by installing rxvt-unicode normally on the remote system,
		853
		854	One some systems you might need to set C<$TERMINFO> to the full path of
		855	F<$HOME/.terminfo> for this to work.
315		856
316	If you cannot or do not want to do this, then you can simply set	857	If you cannot or do not want to do this, then you can simply set
317	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of	858	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
318	problems arising, which includes wrong keymapping, less and different	859	problems arising, which includes wrong keymapping, less and different
319	colours and some refresh errors in fullscreen applications. It's a nice	860	colours and some refresh errors in fullscreen applications. It's a nice
…		…
324	resource to set it:	865	resource to set it:
325		866
326	URxvt.termName: rxvt	867	URxvt.termName: rxvt
327		868
328	If you don't plan to use B<rxvt> (quite common...) you could also replace	869	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.	870	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
330		871
331	=head2 C<tic> outputs some error when compiling the terminfo entry.	872	=head3 C<tic> outputs some error when compiling the terminfo entry.
332		873
333	Most likely it's the empty definition for C<enacs=>. Just replace it by	874	Most likely it's the empty definition for C<enacs=>. Just replace it by
334	C<enacs=\E[0@> and try again.	875	C<enacs=\E[0@> and try again.
335		876
336	=head2 C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	877	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
337		878
		879	See next entry.
		880
338	=head2 I need a termcap file entry.	881	=head3 I need a termcap file entry.
339		882
340	One reason you might want this is that some distributions or operating	883	One reason you might want this is that some distributions or operating
341	systems still compile some programs using the long-obsoleted termcap	884	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	885	library (Fedora Core's bash is one example) and rely on a termcap entry
343	for C<rxvt-unicode>.	886	for C<rxvt-unicode>.
344		887
345	You could use rxvt's termcap entry with resonable results in many cases.	888	You could use rxvt's termcap entry with reasonable results in many cases.
346	You can also create a termcap entry by using terminfo's infocmp program	889	You can also create a termcap entry by using terminfo's infocmp program
347	like this:	890	like this:
348		891
349	infocmp -C rxvt-unicode	892	infocmp -C rxvt-unicode
350		893
…		…
369	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	912	: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:\	913	: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:\	914	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
372	:vs=\E[?25h:	915	:vs=\E[?25h:
373		916
374	=head2 Why does C<ls> no longer have coloured output?	917	=head3 Why does C<ls> no longer have coloured output?
375		918
376	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	919	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	920	decide whether a terminal has colour, but uses its own configuration
378	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	921	file. Needless to say, C<rxvt-unicode> is not in its default file (among
379	with most other terminals supporting colour). Either add:	922	with most other terminals supporting colour). Either add:
380		923
381	TERM rxvt-unicode	924	TERM rxvt-unicode
382		925
383	to C</etc/DIR_COLORS> or simply add:	926	to C</etc/DIR_COLORS> or simply add:
384		927
385	alias ls='ls --color=auto'	928	alias ls='ls --color=auto'
386		929
387	to your C<.profile> or C<.bashrc>.	930	to your C<.profile> or C<.bashrc>.
388		931
389	=head2 Why doesn't vim/emacs etc. use the 88 colour mode?	932	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
390		933
		934	See next entry.
		935
391	=head2 Why doesn't vim/emacs etc. make use of italic?	936	=head3 Why doesn't vim/emacs etc. make use of italic?
392		937
		938	See next entry.
		939
393	=head2 Why are the secondary screen-related options not working properly?	940	=head3 Why are the secondary screen-related options not working properly?
394		941
395	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	942	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
396	distributions (most notably Debian GNU/Linux) break rxvt-unicode	943	distributions (most notably Debian GNU/Linux) break rxvt-unicode
397	by setting C<TERM> to C<rxvt>, which doesn't have these extra	944	by setting C<TERM> to C<rxvt>, which doesn't have these extra
398	features. Unfortunately, some of these (most notably, again, Debian	945	features. Unfortunately, some of these (most notably, again, Debian
399	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	946	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	947	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	948	I log-in to another system it tells me about missing terminfo data?> on
402	how to do this).	949	how to do this).
403		950
404	=head2 My numerical keypad acts weird and generates differing output?
405		951
406	Some Debian GNUL/Linux users seem to have this problem, although no	952	=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		953
413	=head2 Rxvt-unicode does not seem to understand the selected encoding?	954	=head3 Rxvt-unicode does not seem to understand the selected encoding?
414		955
		956	See next entry.
		957
415	=head2 Unicode does not seem to work?	958	=head3 Unicode does not seem to work?
416		959
417	If you encounter strange problems like typing an accented character but	960	If you encounter strange problems like typing an accented character but
418	getting two unrelated other characters or similar, or if program output is	961	getting two unrelated other characters or similar, or if program output is
419	subtly garbled, then you should check your locale settings.	962	subtly garbled, then you should check your locale settings.
420		963
421	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	964	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
422	programs. Often rxvt-unicode is started in the C<C> locale, while the	965	programs running in it. Often rxvt-unicode is started in the C<C> locale,
423	login script running within the rxvt-unicode window changes the locale to	966	while the login script running within the rxvt-unicode window changes the
424	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.	967	locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is
		968	not going to work, and is the most common cause for problems.
425		969
426	The best thing is to fix your startup environment, as you will likely run	970	The best thing is to fix your startup environment, as you will likely run
427	into other problems. If nothing works you can try this in your .profile.	971	into other problems. If nothing works you can try this in your .profile.
428		972
429	printf '\e]701;%s\007' "$LC_CTYPE"	973	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
430		974
431	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	975	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
432	supported on your systems. Some systems have a C<locale> command which	976	supported on your systems. Some systems have a C<locale> command which
433	displays this (also, C<perl -e0> can be used to check locale settings, as	977	displays this (also, C<perl -e0> can be used to check locale settings, as
434	it will complain loudly if it cannot set the locale). If it displays something	978	it will complain loudly if it cannot set the locale). If it displays something
…		…
440		984
441	If nothing works and you are sure that everything is set correctly then	985	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	986	you will need to remember a little known fact: Some programs just don't
443	support locales :(	987	support locales :(
444		988
445	=head2 Why do some characters look so much different than others?	989	=head3 How does rxvt-unicode determine the encoding to use?
446		990
447	=head2 How does rxvt-unicode choose fonts?	991	See next entry.
448		992
449	Most fonts do not contain the full range of Unicode, which is	993	=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		994
454	B<rxvt-unicode> makes a best-effort try at finding a replacement	995	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	996	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	997	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		998
461	In that case, select a font of your taste and add it to the font list,	999	The reasons is that there exists a perfectly fine mechanism for selecting
462	e.g.:	1000	the encoding, doing I/O and (most important) communicating this to all
463		1001	applications so everybody agrees on character properties such as width
464	@@RXVT_NAME@@ -fn basefont,font2,font3...	1002	and code number. This mechanism is the I<locale>. Applications not using
465		1003	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	1004	characters wrong as it uses its 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).	1005	locales).
513		1006
514	It's not clear (to me at least), wether this is a bug in Xft, freetype,	1007	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	1008	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	1009	interpretation of characters.
517	might be forced to use a different font.
518		1010
519	All of this is not a problem when using X11 core fonts, as their bounding	1011	Unfortunately, there is no system-independent way to select locales, nor
520	box data is correct.	1012	is there a standard on how locale specifiers will look like.
521		1013
522	=head2 On Solaris 9, many line-drawing characters are too wide.	1014	On most systems, the content of the C<LC_CTYPE> environment variable
		1015	contains an arbitrary string which corresponds to an already-installed
		1016	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1017	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1018	(i.e. C<de> or C<german>) are also common.
523		1019
524	Seems to be a known bug, read	1020	Rxvt-unicode ignores all other locale categories, and except for
525	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1021	the encoding, ignores country or language-specific settings,
526	following ugly workaround to get non-double-wide-characters working:	1022	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		1023	rxvt-unicode.
527		1024
528	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1025	If you want to use a specific encoding you have to make sure you start
		1026	rxvt-unicode with the correct C<LC_CTYPE> category.
529		1027
530	=head2 My Compose (Multi_key) key is no longer working.	1028	=head3 Can I switch locales at runtime?
531		1029
532	The most common causes for this are that either your locale is not set	1030	Yes, using an escape sequence. Try something like this, which sets
533	correctly, or you specified a B<preeditStyle> that is not supported by	1031	rxvt-unicode's idea of C<LC_CTYPE>.
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		1032
539	In this case either do not specify a B<preeditStyle> or specify more than	1033	printf '\33]701;%s\007' ja_JP.SJIS
540	one pre-edit style, such as B<OverTheSpot,Root,None>.
541		1034
542	=head2 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755	1035	See also the previous answer.
543		1036
544	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on	1037	Sometimes this capability is rather handy when you want to work in
545	international keyboards) or simply use ISO 14755 support to your	1038	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
546	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other	1039	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
547	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape	1040	first switches to a locale supported by xjdic and back later:
548	character and so on.
549		1041
550	=head2 How can I keep rxvt-unicode from using reverse video so much?	1042	printf '\33]701;%s\007' ja_JP.SJIS
		1043	xjdic -js
		1044	printf '\33]701;%s\007' de_DE.UTF-8
551		1045
552	First of all, make sure you are running with the right terminal settings	1046	You can also use xterm's C<luit> program, which usually works fine, except
553	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then	1047	for some locales where character width differs between program- and
554	make sure you have specified colours for italic and bold, as otherwise	1048	rxvt-unicode-locales.
555	rxvt-unicode might use reverse video to simulate the effect:
556		1049
557	URxvt.colorBD: white	1050	=head3 I have problems getting my input method working.
558	URxvt.colorIT: green
559		1051
560	=head2 Some programs assume totally weird colours (red instead of blue), how can I fix that?	1052	Try a search engine, as this is slightly different for every input method server.
561		1053
562	For some unexplainable reason, some rare programs assume a very weird	1054	Here is a checklist:
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		1055
567	In the meantime, you can either edit your C<rxvt-unicode> terminfo	1056	=over 4
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		1057
		1058	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		1059
		1060	Try C<locale -a> or check the documentation for your OS.
		1061
		1062	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		1063
		1064	For example, B<kinput2> does not support UTF-8 locales, you should use
		1065	C<ja_JP.EUC-JP> or equivalent.
		1066
		1067	=item - Make sure your XIM server is actually running.
		1068
		1069	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		1070
		1071	When you want to use e.g. B<kinput2>, it must be set to
		1072	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
		1073	method servers are running with this command:
		1074
		1075	xprop -root XIM_SERVERS
		1076
		1077	=item
		1078
		1079	=back
		1080
		1081	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		1082
		1083	You can specify separate locales for the input method and the rest of the
		1084	terminal, using the resource C<imlocale>:
		1085
		1086	URxvt.imlocale: ja_JP.EUC-JP
		1087
		1088	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1089	use your input method. Please note, however, that, depending on your Xlib
		1090	version, you may not be able to input characters outside C<EUC-JP> in a
		1091	normal way then, as your input method limits you.
		1092
		1093	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		1094
		1095	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1096	design. Applications can avoid some crashes at the expense of memory
		1097	leaks, and Input Methods can avoid some crashes by careful ordering at
		1098	exit time. B<kinput2> (and derived input methods) generally succeeds,
		1099	while B<SCIM> (or similar input methods) fails. In the end, however,
		1100	crashes cannot be completely avoided even if both sides cooperate.
		1101
		1102	So the only workaround is not to kill your Input Method Servers.
		1103
		1104
		1105	=head2 Operating Systems / Package Maintaining
		1106
		1107	=head3 I am using Debian GNU/Linux and have a problem...
		1108
		1109	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1110	patches that considerably change the behaviour of rxvt-unicode (but
		1111	unfortunately this notice has been removed). Before reporting a bug to
		1112	the original rxvt-unicode author please download and install the genuine
		1113	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1114	the problem. If you cannot, chances are that the problems are specific to
		1115	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1116	Tracking System (use C<reportbug> to report the bug).
		1117
		1118	For other problems that also affect the Debian package, you can and
		1119	probably should use the Debian BTS, too, because, after all, it's also a
		1120	bug in the Debian version and it serves as a reminder for other users that
		1121	might encounter the same issue.
		1122
		1123	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1124
		1125	You should build one binary with the default options. F<configure>
		1126	now enables most useful options, and the trend goes to making them
		1127	runtime-switchable, too, so there is usually no drawback to enabling them,
		1128	except higher disk and possibly memory usage. The perl interpreter should
		1129	be enabled, as important functionality (menus, selection, likely more in
		1130	the future) depends on it.
		1131
		1132	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		1133	system-wide (except maybe with C<defaults>). This will result in useful
		1134	behaviour. If your distribution aims at low memory, add an empty
		1135	C<perl-ext-common> resource to the app-defaults file. This will keep the
		1136	perl interpreter disabled until the user enables it.
		1137
		1138	If you can/want build more binaries, I recommend building a minimal
		1139	one with C<--disable-everything> (very useful) and a maximal one with
		1140	C<--enable-everything> (less useful, it will be very big due to a lot of
		1141	encodings built-in that increase download times and are rarely used).
		1142
		1143	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1144
		1145	It should be, starting with release 7.1. You are encouraged to properly
		1146	install urxvt with privileges necessary for your OS now.
		1147
		1148	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1149	into a helper process for privileged operations (pty handling on some
		1150	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1151	immediately. This is much safer than most other terminals that keep
		1152	privileges while running (but is more relevant to urxvt, as it contains
		1153	things as perl interpreters, which might be "helpful" to attackers).
		1154
		1155	This forking is done as the very first within main(), which is very early
		1156	and reduces possible bugs to initialisation code run before main(), or
		1157	things like the dynamic loader of your system, which should result in very
		1158	little risk.
		1159
571	=head2 I am on FreeBSD and rxvt-unicode does not seem to work at all.	1160	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
572		1161
573	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1162	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
574	in your compile environment, or an implementation that implements it,	1163	in your compile environment, or an implementation that implements it,
575	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1164	whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
576	B<wchar_t> is represented as unicode.	1165	B<wchar_t> is represented as unicode.
577		1166
578	As you might have guessed, FreeBSD does neither define this symobl nor	1167	As you might have guessed, FreeBSD does neither define this symbol nor
579	does it support it. Instead, it uses it's own internal representation of	1168	does it support it. Instead, it uses its own internal representation of
580	B<wchar_t>. This is, of course, completely fine with respect to standards.	1169	B<wchar_t>. This is, of course, completely fine with respect to standards.
581		1170
582	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and	1171	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
583	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.	1172	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
584		1173
…		…
598		1187
599	The rxvt-unicode author insists that the right way to fix this is in the	1188	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	1189	system libraries once and for all, instead of forcing every app to carry
601	complete replacements for them :)	1190	complete replacements for them :)
602		1191
603	=head2 I use Solaris 9 and it doesn't compile/work/etc.
604
605	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
606	problems with C<wcwidth> and a compile problem.
607
608	=head2 How can I use rxvt-unicode under cygwin?	1192	=head3 How can I use rxvt-unicode under cygwin?
609		1193
610	rxvt-unicode should compile and run out of the box on cygwin, using	1194	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	1195	the X11 libraries that come with cygwin. libW11 emulation is no
612	longer supported (and makes no sense, either, as it only supported a	1196	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	1197	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
616		1200
617	At the time of this writing, cygwin didn't seem to support any multi-byte	1201	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	1202	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
619	to 8-bit encodings.	1203	to 8-bit encodings.
620		1204
621	=head2 How does rxvt-unicode determine the encoding to use?	1205	=head3 Character widths are not correct.
622		1206
623	=head2 Is there an option to switch encodings?	1207	urxvt uses the system wcwidth function to know the information about
		1208	the width of characters, so on systems with incorrect locale data you
		1209	will likely get bad results. Two notorious examples are Solaris 9,
		1210	where single-width characters like U+2514 are reported as double-width,
		1211	and Darwin 8, where combining chars are reported having width 1.
624		1212
625	Unlike some other terminals, rxvt-unicode has no encoding switch, and no	1213	The solution is to upgrade your system or switch to a better one. A
626	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about	1214	possibly working workaround is to use a wcwidth implementation like
627	UTF-8 or any other encodings with respect to terminal I/O.
628		1215
629	The reasons is that there exists a perfectly fine mechanism for selecting	1216	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
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		1217
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	1218	=head1 RXVT-UNICODE TECHNICAL REFERENCE
984
985	=head1 DESCRIPTION
986		1219
987	The rest of this document describes various technical aspects of	1220	The rest of this document describes various technical aspects of
988	B<rxvt-unicode>. First the description of supported command sequences,	1221	B<rxvt-unicode>. First the description of supported command sequences,
989	followed by pixmap support and last by a description of all features	1222	followed by pixmap support and last by a description of all features
990	selectable at C<configure> time.	1223	selectable at C<configure> time.
991		1224
992	=head1 Definitions	1225	=head2 Definitions
993		1226
994	=over 4	1227	=over 4
995		1228
996	=item B<< C<c> >>	1229	=item B<< C<c> >>
997		1230
…		…
1015		1248
1016	A text parameter composed of printable characters.	1249	A text parameter composed of printable characters.
1017		1250
1018	=back	1251	=back
1019		1252
1020	=head1 Values	1253	=head2 Values
1021		1254
1022	=over 4	1255	=over 4
1023		1256
1024	=item B<< C<ENQ> >>	1257	=item B<< C<ENQ> >>
1025		1258
…		…
1068		1301
1069	Space Character	1302	Space Character
1070		1303
1071	=back	1304	=back
1072		1305
1073	=head1 Escape Sequences	1306	=head2 Escape Sequences
1074		1307
1075	=over 4	1308	=over 4
1076		1309
1077	=item B<< C<ESC # 8> >>	1310	=item B<< C<ESC # 8> >>
1078		1311
…		…
1176		1409
1177	=back	1410	=back
1178		1411
1179	X<CSI>	1412	X<CSI>
1180		1413
1181	=head1 CSI (Command Sequence Introducer) Sequences	1414	=head2 CSI (Command Sequence Introducer) Sequences
1182		1415
1183	=over 4	1416	=over 4
1184		1417
1185	=item B<< C<ESC [ Ps @> >>	1418	=item B<< C<ESC [ Ps @> >>
1186		1419
…		…
1456		1689
1457	=back	1690	=back
1458		1691
1459	X<PrivateModes>	1692	X<PrivateModes>
1460		1693
1461	=head1 DEC Private Modes	1694	=head2 DEC Private Modes
1462		1695
1463	=over 4	1696	=over 4
1464		1697
1465	=item B<< C<ESC [ ? Pm h> >>	1698	=item B<< C<ESC [ ? Pm h> >>
1466		1699
…		…
1482		1715
1483	Toggle DEC Private Mode Values (rxvt extension). I<where>	1716	Toggle DEC Private Mode Values (rxvt extension). I<where>
1484		1717
1485	=over 4	1718	=over 4
1486		1719
1487	=item B<< C<Ps = 1> >> (DECCKM)	1720	=item B<< C<Pm = 1> >> (DECCKM)
1488		1721
1489	=begin table	1722	=begin table
1490		1723
1491	B<< C<h> >> Application Cursor Keys	1724	B<< C<h> >> Application Cursor Keys
1492	B<< C<l> >> Normal Cursor Keys	1725	B<< C<l> >> Normal Cursor Keys
1493		1726
1494	=end table	1727	=end table
1495		1728
1496	=item B<< C<Ps = 2> >> (ANSI/VT52 mode)	1729	=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1497		1730
1498	=begin table	1731	=begin table
1499		1732
1500	B<< C<h> >> Enter VT52 mode	1733	B<< C<h> >> Enter VT52 mode
1501	B<< C<l> >> Enter VT52 mode	1734	B<< C<l> >> Enter VT52 mode
1502		1735
1503	=end table	1736	=end table
1504		1737
1505	=item B<< C<Ps = 3> >>	1738	=item B<< C<Pm = 3> >>
1506		1739
1507	=begin table	1740	=begin table
1508		1741
1509	B<< C<h> >> 132 Column Mode (DECCOLM)	1742	B<< C<h> >> 132 Column Mode (DECCOLM)
1510	B<< C<l> >> 80 Column Mode (DECCOLM)	1743	B<< C<l> >> 80 Column Mode (DECCOLM)
1511		1744
1512	=end table	1745	=end table
1513		1746
1514	=item B<< C<Ps = 4> >>	1747	=item B<< C<Pm = 4> >>
1515		1748
1516	=begin table	1749	=begin table
1517		1750
1518	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)	1751	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1519	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)	1752	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1520		1753
1521	=end table	1754	=end table
1522		1755
1523	=item B<< C<Ps = 5> >>	1756	=item B<< C<Pm = 5> >>
1524		1757
1525	=begin table	1758	=begin table
1526		1759
1527	B<< C<h> >> Reverse Video (DECSCNM)	1760	B<< C<h> >> Reverse Video (DECSCNM)
1528	B<< C<l> >> Normal Video (DECSCNM)	1761	B<< C<l> >> Normal Video (DECSCNM)
1529		1762
1530	=end table	1763	=end table
1531		1764
1532	=item B<< C<Ps = 6> >>	1765	=item B<< C<Pm = 6> >>
1533		1766
1534	=begin table	1767	=begin table
1535		1768
1536	B<< C<h> >> Origin Mode (DECOM)	1769	B<< C<h> >> Origin Mode (DECOM)
1537	B<< C<l> >> Normal Cursor Mode (DECOM)	1770	B<< C<l> >> Normal Cursor Mode (DECOM)
1538		1771
1539	=end table	1772	=end table
1540		1773
1541	=item B<< C<Ps = 7> >>	1774	=item B<< C<Pm = 7> >>
1542		1775
1543	=begin table	1776	=begin table
1544		1777
1545	B<< C<h> >> Wraparound Mode (DECAWM)	1778	B<< C<h> >> Wraparound Mode (DECAWM)
1546	B<< C<l> >> No Wraparound Mode (DECAWM)	1779	B<< C<l> >> No Wraparound Mode (DECAWM)
1547		1780
1548	=end table	1781	=end table
1549		1782
1550	=item B<< C<Ps = 8> >> I<unimplemented>	1783	=item B<< C<Pm = 8> >> I<unimplemented>
1551		1784
1552	=begin table	1785	=begin table
1553		1786
1554	B<< C<h> >> Auto-repeat Keys (DECARM)	1787	B<< C<h> >> Auto-repeat Keys (DECARM)
1555	B<< C<l> >> No Auto-repeat Keys (DECARM)	1788	B<< C<l> >> No Auto-repeat Keys (DECARM)
1556		1789
1557	=end table	1790	=end table
1558		1791
1559	=item B<< C<Ps = 9> >> X10 XTerm	1792	=item B<< C<Pm = 9> >> X10 XTerm
1560		1793
1561	=begin table	1794	=begin table
1562		1795
1563	B<< C<h> >> Send Mouse X & Y on button press.	1796	B<< C<h> >> Send Mouse X & Y on button press.
1564	B<< C<l> >> No mouse reporting.	1797	B<< C<l> >> No mouse reporting.
1565		1798
1566	=end table	1799	=end table
1567		1800
1568	=item B<< C<Ps = 25> >>	1801	=item B<< C<Pm = 25> >>
1569		1802
1570	=begin table	1803	=begin table
1571		1804
1572	B<< C<h> >> Visible cursor {cnorm/cvvis}	1805	B<< C<h> >> Visible cursor {cnorm/cvvis}
1573	B<< C<l> >> Invisible cursor {civis}	1806	B<< C<l> >> Invisible cursor {civis}
1574		1807
1575	=end table	1808	=end table
1576		1809
1577	=item B<< C<Ps = 30> >>	1810	=item B<< C<Pm = 30> >>
1578		1811
1579	=begin table	1812	=begin table
1580		1813
1581	B<< C<h> >> scrollBar visisble	1814	B<< C<h> >> scrollBar visisble
1582	B<< C<l> >> scrollBar invisisble	1815	B<< C<l> >> scrollBar invisisble
1583		1816
1584	=end table	1817	=end table
1585		1818
1586	=item B<< C<Ps = 35> >> (B<rxvt>)	1819	=item B<< C<Pm = 35> >> (B<rxvt>)
1587		1820
1588	=begin table	1821	=begin table
1589		1822
1590	B<< C<h> >> Allow XTerm Shift+key sequences	1823	B<< C<h> >> Allow XTerm Shift+key sequences
1591	B<< C<l> >> Disallow XTerm Shift+key sequences	1824	B<< C<l> >> Disallow XTerm Shift+key sequences
1592		1825
1593	=end table	1826	=end table
1594		1827
1595	=item B<< C<Ps = 38> >> I<unimplemented>	1828	=item B<< C<Pm = 38> >> I<unimplemented>
1596		1829
1597	Enter Tektronix Mode (DECTEK)	1830	Enter Tektronix Mode (DECTEK)
1598		1831
1599	=item B<< C<Ps = 40> >>	1832	=item B<< C<Pm = 40> >>
1600		1833
1601	=begin table	1834	=begin table
1602		1835
1603	B<< C<h> >> Allow 80/132 Mode	1836	B<< C<h> >> Allow 80/132 Mode
1604	B<< C<l> >> Disallow 80/132 Mode	1837	B<< C<l> >> Disallow 80/132 Mode
1605		1838
1606	=end table	1839	=end table
1607		1840
1608	=item B<< C<Ps = 44> >> I<unimplemented>	1841	=item B<< C<Pm = 44> >> I<unimplemented>
1609		1842
1610	=begin table	1843	=begin table
1611		1844
1612	B<< C<h> >> Turn On Margin Bell	1845	B<< C<h> >> Turn On Margin Bell
1613	B<< C<l> >> Turn Off Margin Bell	1846	B<< C<l> >> Turn Off Margin Bell
1614		1847
1615	=end table	1848	=end table
1616		1849
1617	=item B<< C<Ps = 45> >> I<unimplemented>	1850	=item B<< C<Pm = 45> >> I<unimplemented>
1618		1851
1619	=begin table	1852	=begin table
1620		1853
1621	B<< C<h> >> Reverse-wraparound Mode	1854	B<< C<h> >> Reverse-wraparound Mode
1622	B<< C<l> >> No Reverse-wraparound Mode	1855	B<< C<l> >> No Reverse-wraparound Mode
1623		1856
1624	=end table	1857	=end table
1625		1858
1626	=item B<< C<Ps = 46> >> I<unimplemented>	1859	=item B<< C<Pm = 46> >> I<unimplemented>
1627		1860
1628	=item B<< C<Ps = 47> >>	1861	=item B<< C<Pm = 47> >>
1629		1862
1630	=begin table	1863	=begin table
1631		1864
1632	B<< C<h> >> Use Alternate Screen Buffer	1865	B<< C<h> >> Use Alternate Screen Buffer
1633	B<< C<l> >> Use Normal Screen Buffer	1866	B<< C<l> >> Use Normal Screen Buffer
1634		1867
1635	=end table	1868	=end table
1636		1869
1637	X<Priv66>	1870	X<Priv66>
1638		1871
1639	=item B<< C<Ps = 66> >>	1872	=item B<< C<Pm = 66> >>
1640		1873
1641	=begin table	1874	=begin table
1642		1875
1643	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>	1876	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1644	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>	1877	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1645		1878
1646	=end table	1879	=end table
1647		1880
1648	=item B<< C<Ps = 67> >>	1881	=item B<< C<Pm = 67> >>
1649		1882
1650	=begin table	1883	=begin table
1651		1884
1652	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>	1885	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1653	B<< C<l> >> Backspace key sends B<< C<DEL> >>	1886	B<< C<l> >> Backspace key sends B<< C<DEL> >>
1654		1887
1655	=end table	1888	=end table
1656		1889
1657	=item B<< C<Ps = 1000> >> (X11 XTerm)	1890	=item B<< C<Pm = 1000> >> (X11 XTerm)
1658		1891
1659	=begin table	1892	=begin table
1660		1893
1661	B<< C<h> >> Send Mouse X & Y on button press and release.	1894	B<< C<h> >> Send Mouse X & Y on button press and release.
1662	B<< C<l> >> No mouse reporting.	1895	B<< C<l> >> No mouse reporting.
1663		1896
1664	=end table	1897	=end table
1665		1898
1666	=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented>	1899	=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1667		1900
1668	=begin table	1901	=begin table
1669		1902
1670	B<< C<h> >> Use Hilite Mouse Tracking.	1903	B<< C<h> >> Use Hilite Mouse Tracking.
1671	B<< C<l> >> No mouse reporting.	1904	B<< C<l> >> No mouse reporting.
1672		1905
1673	=end table	1906	=end table
1674		1907
		1908	=item B<< C<Pm = 1002> >> (X11 XTerm)
		1909
		1910	=begin table
		1911
		1912	B<< C<h> >> Send Mouse X & Y on button press and release, and motion with a button pressed.
		1913	B<< C<l> >> No mouse reporting.
		1914
		1915	=end table
		1916
		1917	=item B<< C<Pm = 1003> >> (X11 XTerm)
		1918
		1919	=begin table
		1920
		1921	B<< C<h> >> Send Mouse X & Y on button press and release, and motion.
		1922	B<< C<l> >> No mouse reporting.
		1923
		1924	=end table
		1925
1675	=item B<< C<Ps = 1010> >> (B<rxvt>)	1926	=item B<< C<Pm = 1010> >> (B<rxvt>)
1676		1927
1677	=begin table	1928	=begin table
1678		1929
1679	B<< C<h> >> Don't scroll to bottom on TTY output	1930	B<< C<h> >> Don't scroll to bottom on TTY output
1680	B<< C<l> >> Scroll to bottom on TTY output	1931	B<< C<l> >> Scroll to bottom on TTY output
1681		1932
1682	=end table	1933	=end table
1683		1934
1684	=item B<< C<Ps = 1011> >> (B<rxvt>)	1935	=item B<< C<Pm = 1011> >> (B<rxvt>)
1685		1936
1686	=begin table	1937	=begin table
1687		1938
1688	B<< C<h> >> Scroll to bottom when a key is pressed	1939	B<< C<h> >> Scroll to bottom when a key is pressed
1689	B<< C<l> >> Don't scroll to bottom when a key is pressed	1940	B<< C<l> >> Don't scroll to bottom when a key is pressed
1690		1941
1691	=end table	1942	=end table
1692		1943
1693	=item B<< C<Ps = 1021> >> (B<rxvt>)	1944	=item B<< C<Pm = 1021> >> (B<rxvt>)
1694		1945
1695	=begin table	1946	=begin table
1696		1947
1697	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)	1948	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
1698	B<< C<l> >> Font styles have no effect on intensity (Compile styles)	1949	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1699		1950
1700	=end table	1951	=end table
1701		1952
1702	=item B<< C<Ps = 1047> >>	1953	=item B<< C<Pm = 1047> >>
1703		1954
1704	=begin table	1955	=begin table
1705		1956
1706	B<< C<h> >> Use Alternate Screen Buffer	1957	B<< C<h> >> Use Alternate Screen Buffer
1707	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it	1958	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1708		1959
1709	=end table	1960	=end table
1710		1961
1711	=item B<< C<Ps = 1048> >>	1962	=item B<< C<Pm = 1048> >>
1712		1963
1713	=begin table	1964	=begin table
1714		1965
1715	B<< C<h> >> Save cursor position	1966	B<< C<h> >> Save cursor position
1716	B<< C<l> >> Restore cursor position	1967	B<< C<l> >> Restore cursor position
1717		1968
1718	=end table	1969	=end table
1719		1970
1720	=item B<< C<Ps = 1049> >>	1971	=item B<< C<Pm = 1049> >>
1721		1972
1722	=begin table	1973	=begin table
1723		1974
1724	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it	1975	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1725	B<< C<l> >> Use Normal Screen Buffer	1976	B<< C<l> >> Use Normal Screen Buffer
…		…
1730		1981
1731	=back	1982	=back
1732		1983
1733	X<XTerm>	1984	X<XTerm>
1734		1985
1735	=head1 XTerm Operating System Commands	1986	=head2 XTerm Operating System Commands
1736		1987
1737	=over 4	1988	=over 4
1738		1989
1739	=item B<< C<ESC ] Ps;Pt ST> >>	1990	=item B<< C<ESC ] Ps;Pt ST> >>
1740		1991
…		…
1754	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	2005	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1755	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	2006	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1756	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	2007	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1757	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]	2008	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1758	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]	2009	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1759	B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM).	2010	B<< C<Ps = 20> >> Change background pixmap parameters (see section BACKGROUND IMAGE) (Compile AfterImage).
1760	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.	2011	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1761	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	2012	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1762	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	2013	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1763	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>	2014	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>
1764	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	2015	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
…		…
1778		2029
1779	=end table	2030	=end table
1780		2031
1781	=back	2032	=back
1782		2033
1783	X<XPM>	2034	=head1 BACKGROUND IMAGE
1784		2035
1785	=head1 XPM
1786
1787	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	2036	For the BACGROUND IMAGE 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	2037	of B<< C<Pt> >> can be the name of the background image file followed by a
1789	sequence of scaling/positioning commands separated by semi-colons. The	2038	sequence of scaling/positioning commands separated by semi-colons. The
1790	scaling/positioning commands are as follows:	2039	scaling/positioning commands are as follows:
1791		2040
1792	=over 4	2041	=over 4
1793		2042
…		…
1831		2080
1832	For example:	2081	For example:
1833		2082
1834	=over 4	2083	=over 4
1835		2084
1836	=item B<\E]20;funky\a>	2085	=item B<\E]20;funky.jpg\a>
1837		2086
1838	load B<funky.xpm> as a tiled image	2087	load B<funky.jpg> as a tiled image
1839		2088
1840	=item B<\E]20;mona;100\a>	2089	=item B<\E]20;mona.jpg;100\a>
1841		2090
1842	load B<mona.xpm> with a scaling of 100%	2091	load B<mona.jpg> with a scaling of 100%
1843		2092
1844	=item B<\E]20;;200;?\a>	2093	=item B<\E]20;;200;?\a>
1845		2094
1846	rescale the current pixmap to 200% and display the image geometry in	2095	rescale the current pixmap to 200% and display the image geometry in
1847	the title	2096	the title
…		…
1886	=begin table	2135	=begin table
1887		2136
1888	4 Shift	2137	4 Shift
1889	8 Meta	2138	8 Meta
1890	16 Control	2139	16 Control
1891	32 Double Click I<(Rxvt extension)>	2140	32 Double Click I<(rxvt extension)>
1892		2141
1893	=end table	2142	=end table
1894		2143
1895	Col = B<< C<< <x> - SPACE >> >>	2144	Col = B<< C<< <x> - SPACE >> >>
1896		2145
…		…
1974		2223
1975	=head1 CONFIGURE OPTIONS	2224	=head1 CONFIGURE OPTIONS
1976		2225
1977	General hint: if you get compile errors, then likely your configuration	2226	General hint: if you get compile errors, then likely your configuration
1978	hasn't been tested well. Either try with C<--enable-everything> or use	2227	hasn't been tested well. Either try with C<--enable-everything> or use
1979	the F<./reconf> script as a base for experiments. F<./reconf> is used by	2228	the default configuration (i.e. no C<--enable-xxx> or C<--disable-xxx>
1980	myself, so it should generally be a working config. Of course, you should	2229	switches). Of course, you should always report when a combination doesn't
1981	always report when a combination doesn't work, so it can be fixed. Marc	2230	work, so it can be fixed. Marc Lehmann <rxvt@schmorp.de>.
1982	Lehmann <rxvt@schmorp.de>.
1983		2231
1984	All	2232	All
1985		2233
1986	=over 4	2234	=over 4
1987		2235
…		…
2019		2267
2020	=begin table	2268	=begin table
2021		2269
2022	all all available codeset groups	2270	all all available codeset groups
2023	zh common chinese encodings	2271	zh common chinese encodings
2024	zh_ext rarely used but very big chinese encodigs	2272	zh_ext rarely used but very big chinese encodings
2025	jp common japanese encodings	2273	jp common japanese encodings
2026	jp_ext rarely used but big japanese encodings	2274	jp_ext rarely used but big japanese encodings
2027	kr korean encodings	2275	kr korean encodings
2028		2276
2029	=end table	2277	=end table
…		…
2043	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2291	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2044	support these extra characters, but Xft does.	2292	support these extra characters, but Xft does.
2045		2293
2046	Please note that rxvt-unicode can store unicode code points >65535	2294	Please note that rxvt-unicode can store unicode code points >65535
2047	even without this flag, but the number of such characters is	2295	even without this flag, but the number of such characters is
2048	limited to a view thousand (shared with combining characters,	2296	limited to a few thousand (shared with combining characters,
2049	see next switch), and right now rxvt-unicode cannot display them	2297	see next switch), and right now rxvt-unicode cannot display them
2050	(input/output and cut&paste still work, though).	2298	(input/output and cut&paste still work, though).
2051		2299
2052	=item --enable-combining (default: on)	2300	=item --enable-combining (default: on)
2053		2301
…		…
2076	=item --with-res-name=NAME (default: urxvt)	2324	=item --with-res-name=NAME (default: urxvt)
2077		2325
2078	Use the given name as default application name when	2326	Use the given name as default application name when
2079	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2327	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2080		2328
2081	=item --with-res-class=CLASS /default: URxvt)	2329	=item --with-res-class=CLASS (default: URxvt)
2082		2330
2083	Use the given class as default application class	2331	Use the given class as default application class
2084	when reading resources. Specify --with-res-class=Rxvt to replace	2332	when reading resources. Specify --with-res-class=Rxvt to replace
2085	rxvt.	2333	rxvt.
2086		2334
…		…
2099		2347
2100	Write user and tty to lastlog file (used by programs like	2348	Write user and tty to lastlog file (used by programs like
2101	F<lastlogin>) at start of rxvt execution. This option requires	2349	F<lastlogin>) at start of rxvt execution. This option requires
2102	--enable-utmp to also be specified.	2350	--enable-utmp to also be specified.
2103		2351
2104	=item --enable-xpm-background (default: on)	2352	=item --enable-afterimage (default: on)
2105		2353
2106	Add support for XPM background pixmaps.	2354	Add support for libAfterImage to be used for transparency and background
		2355	images. It adds support for many file formats including JPG, PNG,
		2356	SVG, TIFF, GIF, XPM, BMP, ICO, XCF, TGA and AfterStep image XML
		2357	(L<http://www.afterstep.org/visualdoc.php?show=asimagexml>).
		2358
		2359	This option also adds such eye candy as blending an image over the root
		2360	background, as well as dynamic scaling and bluring of background images.
		2361
		2362	Note that with this option enabled, @@RXVT_NAME@@'s memory footprint might
		2363	increase by a few megabytes even if no extra features are used (mostly due
		2364	to third-party libraries used by libAI). Memory footprint may somewhat be
		2365	lowered if libAfterImage is configured without support for SVG.
2107		2366
2108	=item --enable-transparency (default: on)	2367	=item --enable-transparency (default: on)
2109		2368
2110	Add support for inheriting parent backgrounds thus giving a fake	2369	Add support for backgrounds, creating illusion of transparency in the term.
2111	transparency to the term.
2112		2370
2113	=item --enable-fading (default: on)	2371	=item --enable-fading (default: on)
2114		2372
2115	Add support for fading the text when focus is lost (requires C<--enable-transparency>).	2373	Add support for fading the text when focus is lost.
2116
2117	=item --enable-tinting (default: on)
2118
2119	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2120		2374
2121	=item --enable-rxvt-scroll (default: on)	2375	=item --enable-rxvt-scroll (default: on)
2122		2376
2123	Add support for the original rxvt scrollbar.	2377	Add support for the original rxvt scrollbar.
2124		2378
…		…
2167	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2421	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2168	in combination with other switches) is:	2422	in combination with other switches) is:
2169		2423
2170	MWM-hints	2424	MWM-hints
2171	EWMH-hints (pid, utf8 names) and protocols (ping)	2425	EWMH-hints (pid, utf8 names) and protocols (ping)
		2426	urgency hint
2172	seperate underline colour (-underlineColor)	2427	seperate underline colour (-underlineColor)
2173	settable border widths and borderless switch (-w, -b, -bl)	2428	settable border widths and borderless switch (-w, -b, -bl)
2174	visual depth selection (-depth)	2429	visual depth selection (-depth)
2175	settable extra linespacing /-lsp)	2430	settable extra linespacing /-lsp)
2176	iso-14755-2 and -3, and visual feedback	2431	iso-14755 5.1 (basic) support
2177	tripleclickwords (-tcw)	2432	tripleclickwords (-tcw)
2178	settable insecure mode (-insecure)	2433	settable insecure mode (-insecure)
2179	keysym remapping support	2434	keysym remapping support
2180	cursor blinking and underline cursor (-cb, -uc)	2435	cursor blinking and underline cursor (-cb, -uc)
2181	XEmbed support (-embed)	2436	XEmbed support (-embed)
2182	user-pty (-pty-fd)	2437	user-pty (-pty-fd)
2183	hold on exit (-hold)	2438	hold on exit (-hold)
		2439	compile in built-in block graphics
2184	skip builtin block graphics (-sbg)	2440	skip builtin block graphics (-sbg)
		2441	separate highlightcolor support (-hc)
2185		2442
2186	It also enabled some non-essential features otherwise disabled, such as:	2443	It also enables some non-essential features otherwise disabled, such as:
2187		2444
2188	some round-trip time optimisations	2445	some round-trip time optimisations
2189	nearest color allocation on pseudocolor screens	2446	nearest color allocation on pseudocolor screens
2190	UTF8_STRING supporr for selection	2447	UTF8_STRING support for selection
2191	sgr modes 90..97 and 100..107	2448	sgr modes 90..97 and 100..107
2192	backindex and forwardindex escape sequences	2449	backindex and forwardindex escape sequences
2193	view change/zero scorllback esacpe sequences	2450	view change/zero scrollback escape sequences
2194	locale switching escape sequence	2451	locale switching escape sequence
2195	window op and some xterm/OSC escape sequences	2452	window op and some xterm/OSC escape sequences
2196	rectangular selections	2453	rectangular selections
2197	trailing space removal for selections	2454	trailing space removal for selections
2198	verbose X error handling	2455	verbose X error handling
…		…
2207	=item --enable-keepscrolling (default: on)	2464	=item --enable-keepscrolling (default: on)
2208		2465
2209	Add support for continual scrolling of the display when you hold	2466	Add support for continual scrolling of the display when you hold
2210	the mouse button down on a scrollbar arrow.	2467	the mouse button down on a scrollbar arrow.
2211		2468
		2469	=item --enable-selectionscrolling (default: on)
		2470
		2471	Add support for scrolling when the selection moves to the top or
		2472	bottom of the screen.
		2473
2212	=item --enable-mousewheel (default: on)	2474	=item --enable-mousewheel (default: on)
2213		2475
2214	Add support for scrolling via mouse wheel or buttons 4 & 5.	2476	Add support for scrolling via mouse wheel or buttons 4 & 5.
2215		2477
2216	=item --enable-slipwheeling (default: on)	2478	=item --enable-slipwheeling (default: on)
2217		2479
2218	Add support for continual scrolling (using the mouse wheel as an	2480	Add support for continual scrolling (using the mouse wheel as an
2219	accelerator) while the control key is held down. This option	2481	accelerator) while the control key is held down. This option
2220	requires --enable-mousewheel to also be specified.	2482	requires --enable-mousewheel to also be specified.
2221		2483
2222	=item --disable-new-selection
2223
2224	Remove support for mouse selection style like that of xterm.
2225
2226	=item --enable-dmalloc (default: off)
2227
2228	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
2230	next option, you may need to edit src/Makefile after compiling to point
2231	DINCLUDE and DLIB to the right places.
2232
2233	You can only use either this option and the following (should
2234	you use either) .
2235
2236	=item --enable-dlmalloc (default: off)
2237
2238	Use Doug Lea's malloc - which is good for a production version
2239	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2240
2241	=item --enable-smart-resize (default: on)	2484	=item --enable-smart-resize (default: off)
2242		2485
2243	Add smart growth/shrink behaviour when changing font size via hot	2486	Add smart growth/shrink behaviour when resizing.
2244	keys. This should keep the window corner which is closest to a corner of	2487	This should keep the window corner which is closest to a corner of
2245	the screen in a fixed position.	2488	the screen in a fixed position.
2246		2489
2247	=item --enable-pointer-blank (default: on)	2490	=item --enable-pointer-blank (default: on)
2248		2491
2249	Add support to have the pointer disappear when typing or inactive.	2492	Add support to have the pointer disappear when typing or inactive.
2250		2493
2251	=item --enable-perl (default: on)	2494	=item --enable-perl (default: on)
2252		2495
2253	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>	2496	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2254	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files	2497	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the
2255	in F<src/perl-ext/> for the extensions that are installed by default. The	2498	files in F<src/perl-ext/> for the extensions that are installed by
2256	perl interpreter that is used can be specified via the C<PERL> environment	2499	default. The perl interpreter that is used can be specified via the
2257	variable when running configure.	2500	C<PERL> environment variable when running configure. Even when compiled
		2501	in, perl will I<not> be initialised when all extensions have been disabled
		2502	C<-pe "" --perl-ext-common "">, so it should be safe to enable from a
		2503	resource standpoint.
		2504
		2505	=item --with-afterimage-config=DIR
		2506
		2507	Look for the libAfterImage config script in DIR.
2258		2508
2259	=item --with-name=NAME (default: urxvt)	2509	=item --with-name=NAME (default: urxvt)
2260		2510
2261	Set the basename for the installed binaries, resulting	2511	Set the basename for the installed binaries, resulting
2262	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2512	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
…		…
2272	PATH.	2522	PATH.
2273		2523
2274	=item --with-x	2524	=item --with-x
2275		2525
2276	Use the X Window System (pretty much default, eh?).	2526	Use the X Window System (pretty much default, eh?).
2277
2278	=item --with-xpm-includes=DIR
2279
2280	Look for the XPM includes in DIR.
2281
2282	=item --with-xpm-library=DIR
2283
2284	Look for the XPM library in DIR.
2285
2286	=item --with-xpm
2287
2288	Not needed - define via --enable-xpm-background.
2289		2527
2290	=back	2528	=back
2291		2529
2292	=head1 AUTHORS	2530	=head1 AUTHORS
2293		2531

Diff Legend

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