[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.56 by root, Wed Jul 13 01:01:41 2005 UTC vs.
Revision 1.195 by sf-exg, Fri Sep 3 09:57:30 2010 UTC

…		…
16	=head1 DESCRIPTION	16	=head1 DESCRIPTION
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is	21	The newest version of this document is also available on the World Wide Web at
22	also available on the World Wide Web at	22	L<http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod>.
23	L<http://cvs.schmorp.de/browse/checkout/rxvt-unicode/doc/rxvt.7.html>.
24		23
		24	The main manual page for @@RXVT_NAME@@ itself is available at
		25	L<http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.1.pod>.
		26
25	=head1 FREQUENTLY ASKED QUESTIONS	27	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		28
27	=over 4
28		29
		30	=head2 Meta, Features & Commandline Issues
		31
		32	=head3 My question isn't answered here, can I ask a human?
		33
		34	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		35	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		36	interested in learning about new and exciting problems (but not FAQs :).
		37
		38	=head3 I use Gentoo, and I have a problem...
		39
		40	There are three big problems with Gentoo Linux: first of all, most if not
		41	all Gentoo systems are completely broken (missing or mismatched header
		42	files, broken compiler etc. are just the tip of the iceberg); secondly,
		43	the Gentoo maintainer thinks it is a good idea to add broken patches to
		44	the code; and lastly, it should be called Gentoo GNU/Linux.
		45
		46	For these reasons, it is impossible to support rxvt-unicode on
		47	Gentoo. Problems appearing on Gentoo systems will usually simply be
		48	ignored unless they can be reproduced on non-Gentoo systems.
		49
		50	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
		51
		52	Beginning with version 7.3, there is a perl extension that implements a
		53	simple tabbed terminal. It is installed by default, so any of these should
		54	give you tabs:
		55
		56	@@URXVT_NAME@@ -pe tabbed
		57
		58	URxvt.perl-ext-common: default,tabbed
		59
		60	It will also work fine with tabbing functionality of many window managers
		61	or similar tabbing programs, and its embedding-features allow it to be
		62	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		63	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		64	(murxvt) terminal as an example embedding application.
		65
29	=item How do I know which rxvt-unicode version I'm using?	66	=head3 How do I know which rxvt-unicode version I'm using?
30		67
31	The version number is displayed with the usage (-h). Also the escape	68	The version number is displayed with the usage (-h). Also the escape
32	sequence C<ESC [ 8 n> sets the window title to the version number.	69	sequence C<ESC [ 8 n> sets the window title to the version number. When
		70	using the @@URXVT_NAME@@c client, the version displayed is that of the
		71	daemon.
33		72
34	=item I am using Debian GNU/Linux and have a problem...
35
36	The Debian GNU/Linux package of rxvt-unicode contains large patches that
37	considerably change the behaviour of rxvt-unicode. Before reporting a
38	bug to the original rxvt-unicode author please download and install the
39	genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to
40	reproduce the problem. If you cannot, chances are that the problems are
41	specific to Debian GNU/Linux, in which case it should be reported via the
42	Debian Bug Tracking System (use C<reportbug> to report the bug).
43
44	For other problems that also affect the Debian package, you can and
45	probably should use the Debian BTS, too, because, after all, it's also a
46	bug in the Debian version and it serves as a reminder for other users that
47	might encounter the same issue.
48
49	=item When I log-in to another system it tells me about missing terminfo data?
50
51	The terminal description used by rxvt-unicode is not as widely available
52	as that for xterm, or even rxvt (for which the same problem often arises).
53
54	The correct solution for this problem is to install the terminfo, this can
55	be done like this (with ncurses' infocmp):
56
57	REMOTE=remotesystem.domain
58	infocmp rxvt-unicode \| ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
59
60	... or by installing rxvt-unicode normally on the remote system,
61
62	If you cannot or do not want to do this, then you can simply set
63	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
64	problems arising, which includes wrong keymapping, less and different
65	colours and some refresh errors in fullscreen applications. It's a nice
66	quick-and-dirty workaround for rare cases, though.
67
68	If you always want to do this (and are fine with the consequences) you
69	can either recompile rxvt-unicode with the desired TERM value or use a
70	resource to set it:
71
72	URxvt.termName: rxvt
73
74	If you don't plan to use B<rxvt> (quite common...) you could also replace
75	the rxvt terminfo file with the rxvt-unicode one.
76
77	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
78
79	=item I need a termcap file entry.
80
81	One reason you might want this is that some distributions or operating
82	systems still compile some programs using the long-obsoleted termcap
83	library (Fedora Core's bash is one example) and rely on a termcap entry
84	for C<rxvt-unicode>.
85
86	You could use rxvt's termcap entry with resonable results in many cases.
87	You can also create a termcap entry by using terminfo's infocmp program
88	like this:
89
90	infocmp -C rxvt-unicode
91
92	Or you could use this termcap entry, generated by the command above:
93
94	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
95	:am:bw:eo:km:mi:ms:xn:xo:\
96	:co#80:it#8:li#24:lm#0:\
97	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
98	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
99	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
100	:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
101	:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
102	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
103	:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
104	:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
105	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
106	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
107	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
108	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
109	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
110	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
111	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
112	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
113	:vs=\E[?25h:
114
115	=item Why does C<ls> no longer have coloured output?
116
117	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
118	decide wether a terminal has colour, but uses it's own configuration
119	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
120	with most other terminals supporting colour). Either add:
121
122	TERM rxvt-unicode
123
124	to C</etc/DIR_COLORS> or simply add:
125
126	alias ls='ls --color=auto'
127
128	to your C<.profile> or C<.bashrc>.
129
130	=item Why doesn't vim/emacs etc. use the 88 colour mode?
131
132	=item Why doesn't vim/emacs etc. make use of italic?
133
134	=item Why are the secondary screen-related options not working properly?
135
136	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
137	distributions (most notably Debian GNU/Linux) break rxvt-unicode
138	by setting C<TERM> to C<rxvt>, which doesn't have these extra
139	features. Unfortunately, some of these (most notably, again, Debian
140	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
141	file, so you will need to install it on your own (See the question B<When
142	I log-in to another system it tells me about missing terminfo data?> on
143	how to do this).
144
145	=item My numerical keypad acts weird and generates differing output?
146
147	Some Debian GNUL/Linux users seem to have this problem, although no
148	specific details were reported so far. It is possible that this is caused
149	by the wrong C<TERM> setting, although the details of wether and how
150	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
151	keymap. See the answer to the previous question, and please report if that
152	helped.
153
154	=item Rxvt-unicode does not seem to understand the selected encoding?
155
156	=item Unicode does not seem to work?
157
158	If you encounter strange problems like typing an accented character but
159	getting two unrelated other characters or similar, or if program output is
160	subtly garbled, then you should check your locale settings.
161
162	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
163	programs. Often rxvt-unicode is started in the C<C> locale, while the
164	login script running within the rxvt-unicode window changes the locale to
165	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
166
167	The best thing is to fix your startup environment, as you will likely run
168	into other problems. If nothing works you can try this in your .profile.
169
170	printf '\e]701;%s\007' "$LC_CTYPE"
171
172	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
173	supported on your systems. Some systems have a C<locale> command which
174	displays this (also, C<perl -e0> can be used to check locale settings, as
175	it will complain loudly if it cannot set the locale). If it displays something
176	like:
177
178	locale: Cannot set LC_CTYPE to default locale: ...
179
180	Then the locale you specified is not supported on your system.
181
182	If nothing works and you are sure that everything is set correctly then
183	you will need to remember a little known fact: Some programs just don't
184	support locales :(
185
186	=item Why do some characters look so much different than others?
187
188	=item How does rxvt-unicode choose fonts?
189
190	Most fonts do not contain the full range of Unicode, which is
191	fine. Chances are that the font you (or the admin/package maintainer of
192	your system/os) have specified does not cover all the characters you want
193	to display.
194
195	B<rxvt-unicode> makes a best-effort try at finding a replacement
196	font. Often the result is fine, but sometimes the chosen font looks
197	bad/ugly/wrong. Some fonts have totally strange characters that don't
198	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
199	intelligence to detect that a specific glyph is wrong: it has to believe
200	the font that the characters it claims to contain indeed look correct.
201
202	In that case, select a font of your taste and add it to the font list,
203	e.g.:
204
205	@@RXVT_NAME@@ -fn basefont,font2,font3...
206
207	When rxvt-unicode sees a character, it will first look at the base
208	font. If the base font does not contain the character, it will go to the
209	next font, and so on. Specifying your own fonts will also speed up this
210	search and use less resources within rxvt-unicode and the X-server.
211
212	The only limitation is that none of the fonts may be larger than the base
213	font, as the base font defines the terminal character cell size, which
214	must be the same due to the way terminals work.
215
216	=item Why do some chinese characters look so different than others?
217
218	This is because there is a difference between script and language --
219	rxvt-unicode does not know which language the text that is output is,
220	as it only knows the unicode character codes. If rxvt-unicode first
221	sees a japanese/chinese character, it might choose a japanese font for
222	display. Subsequent japanese characters will use that font. Now, many
223	chinese characters aren't represented in japanese fonts, so when the first
224	non-japanese character comes up, rxvt-unicode will look for a chinese font
225	-- unfortunately at this point, it will still use the japanese font for
226	chinese characters that are also in the japanese font.
227
228	The workaround is easy: just tag a chinese font at the end of your font
229	list (see the previous question). The key is to view the font list as
230	a preference list: If you expect more japanese, list a japanese font
231	first. If you expect more chinese, put a chinese font first.
232
233	In the future it might be possible to switch language preferences at
234	runtime (the internal data structure has no problem with using different
235	fonts for the same character at the same time, but no interface for this
236	has been designed yet).
237
238	Until then, you might get away with switching fonts at runtime (see L<Can
239	I switch the fonts at runtime?> later in this document).
240
241	=item Why does rxvt-unicode sometimes leave pixel droppings?
242
243	Most fonts were not designed for terminal use, which means that character
244	size varies a lot. A font that is otherwise fine for terminal use might
245	contain some characters that are simply too wide. Rxvt-unicode will avoid
246	these characters. For characters that are just "a bit" too wide a special
247	"careful" rendering mode is used that redraws adjacent characters.
248
249	All of this requires that fonts do not lie about character sizes,
250	however: Xft fonts often draw glyphs larger than their acclaimed bounding
251	box, and rxvt-unicode has no way of detecting this (the correct way is to
252	ask for the character bounding box, which unfortunately is wrong in these
253	cases).
254
255	It's not clear (to me at least), wether this is a bug in Xft, freetype,
256	or the respective font. If you encounter this problem you might try using
257	the C<-lsp> option to give the font more height. If that doesn't work, you
258	might be forced to use a different font.
259
260	All of this is not a problem when using X11 core fonts, as their bounding
261	box data is correct.
262
263	=item On Solaris 9, many line-drawing characters are too wide.
264
265	Seems to be a known bug, read
266	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
267	following ugly workaround to get non-double-wide-characters working:
268
269	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
270
271	=item My Compose (Multi_key) key is no longer working.
272
273	The most common causes for this are that either your locale is not set
274	correctly, or you specified a B<preeditStyle> that is not supported by
275	your input method. For example, if you specified B<OverTheSpot> and
276	your input method (e.g. the default input method handling Compose keys)
277	does not support this (for instance because it is not visual), then
278	rxvt-unicode will continue without an input method.
279
280	In this case either do not specify a B<preeditStyle> or specify more than
281	one pre-edit style, such as B<OverTheSpot,Root,None>.
282
283	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
284
285	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
286	international keyboards) or simply use ISO 14755 support to your
287	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
288	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
289	character and so on.
290
291	=item How can I keep rxvt-unicode from using reverse video so much?
292
293	First of all, make sure you are running with the right terminal settings
294	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
295	make sure you have specified colours for italic and bold, as otherwise
296	rxvt-unicode might use reverse video to simulate the effect:
297
298	URxvt.colorBD: white
299	URxvt.colorIT: green
300
301	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
302
303	For some unexplainable reason, some rare programs assume a very weird
304	colour palette when confronted with a terminal with more than the standard
305	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
306	these programs not to assume non-ISO colours without very good reasons.
307
308	In the meantime, you can either edit your C<rxvt-unicode> terminfo
309	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
310	fix colours but keep you from using other rxvt-unicode features.
311
312	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
313
314	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
315	in your compile environment, or an implementation that implements it,
316	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
317	B<wchar_t> is represented as unicode.
318
319	As you might have guessed, FreeBSD does neither define this symobl nor
320	does it support it. Instead, it uses it's own internal representation of
321	B<wchar_t>. This is, of course, completely fine with respect to standards.
322
323	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
324	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
325
326	C<__STDC_ISO_10646__> is the only sane way to support multi-language
327	apps in an OS, as using a locale-dependent (and non-standardized)
328	representation of B<wchar_t> makes it impossible to convert between
329	B<wchar_t> (as used by X11 and your applications) and any other encoding
330	without implementing OS-specific-wrappers for each and every locale. There
331	simply are no APIs to convert B<wchar_t> into anything except the current
332	locale encoding.
333
334	Some applications (such as the formidable B<mlterm>) work around this
335	by carrying their own replacement functions for character set handling
336	with them, and either implementing OS-dependent hacks or doing multiple
337	conversions (which is slow and unreliable in case the OS implements
338	encodings slightly different than the terminal emulator).
339
340	The rxvt-unicode author insists that the right way to fix this is in the
341	system libraries once and for all, instead of forcing every app to carry
342	complete replacements for them :)
343
344	=item I use Solaris 9 and it doesn't compile/work/etc.
345
346	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
347	problems with C<wcwidth> and a compile problem.
348
349	=item How can I use rxvt-unicode under cygwin?
350
351	rxvt-unicode should compile and run out of the box on cygwin, using
352	the X11 libraries that come with cygwin. libW11 emulation is no
353	longer supported (and makes no sense, either, as it only supported a
354	single font). I recommend starting the X-server in C<-multiwindow> or
355	C<-rootless> mode instead, which will result in similar look&feel as the
356	old libW11 emulation.
357
358	At the time of this writing, cygwin didn't seem to support any multi-byte
359	encodings, so you are likely limited to 8-bit encodings.
360
361	=item How does rxvt-unicode determine the encoding to use?
362
363	=item Is there an option to switch encodings?
364
365	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
366	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
367	UTF-8 or any other encodings with respect to terminal I/O.
368
369	The reasons is that there exists a perfectly fine mechanism for selecting
370	the encoding, doing I/O and (most important) communicating this to all
371	applications so everybody agrees on character properties such as width
372	and code number. This mechanism is the I<locale>. Applications not using
373	that info will have problems (for example, C<xterm> gets the width of
374	characters wrong as it uses it's own, locale-independent table under all
375	locales).
376
377	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
378	programs doing the same (that is, most) will automatically agree in the
379	interpretation of characters.
380
381	Unfortunately, there is no system-independent way to select locales, nor
382	is there a standard on how locale specifiers will look like.
383
384	On most systems, the content of the C<LC_CTYPE> environment variable
385	contains an arbitrary string which corresponds to an already-installed
386	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
387	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
388	(i.e. C<de> or C<german>) are also common.
389
390	Rxvt-unicode ignores all other locale categories, and except for
391	the encoding, ignores country or language-specific settings,
392	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
393	rxvt-unicode.
394
395	If you want to use a specific encoding you have to make sure you start
396	rxvt-unicode with the correct C<LC_CTYPE> category.
397
398	=item Can I switch locales at runtime?
399
400	Yes, using an escape sequence. Try something like this, which sets
401	rxvt-unicode's idea of C<LC_CTYPE>.
402
403	printf '\e]701;%s\007' ja_JP.SJIS
404
405	See also the previous answer.
406
407	Sometimes this capability is rather handy when you want to work in
408	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
409	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
410	first switches to a locale supported by xjdic and back later:
411
412	printf '\e]701;%s\007' ja_JP.SJIS
413	xjdic -js
414	printf '\e]701;%s\007' de_DE.UTF-8
415
416	You can also use xterm's C<luit> program, which usually works fine, except
417	for some locales where character width differs between program- and
418	rxvt-unicode-locales.
419
420	=item Can I switch the fonts at runtime?
421
422	Yes, using an escape sequence. Try something like this, which has the same
423	effect as using the C<-fn> switch, and takes effect immediately:
424
425	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
426
427	This is useful if you e.g. work primarily with japanese (and prefer a
428	japanese font), but you have to switch to chinese temporarily, where
429	japanese fonts would only be in your way.
430
431	You can think of this as a kind of manual ISO-2022 switching.
432
433	=item Why do italic characters look as if clipped?
434
435	Many fonts have difficulties with italic characters and hinting. For
436	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
437	Mono> completely fails in it's italic face. A workaround might be to
438	enable freetype autohinting, i.e. like this:
439
440	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
441	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
442
443	=item My input method wants <some encoding> but I want UTF-8, what can I do?
444
445	You can specify separate locales for the input method and the rest of the
446	terminal, using the resource C<imlocale>:
447
448	URxvt*imlocale: ja_JP.EUC-JP
449
450	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
451	use your input method. Please note, however, that you will not be able to
452	input characters outside C<EUC-JP> in a normal way then, as your input
453	method limits you.
454
455	=item Rxvt-unicode crashes when the X Input Method changes or exits.
456
457	Unfortunately, this is unavoidable, as the XIM protocol is racy by
458	design. Applications can avoid some crashes at the expense of memory
459	leaks, and Input Methods can avoid some crashes by careful ordering at
460	exit time. B<kinput2> (and derived input methods) generally succeeds,
461	while B<SCIM> (or similar input methods) fails. In the end, however,
462	crashes cannot be completely avoided even if both sides cooperate.
463
464	So the only workaround is not to kill your Input Method Servers.
465
466	=item Rxvt-unicode uses gobs of memory, how can I reduce that?	73	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
467		74
468	Rxvt-unicode tries to obey the rule of not charging you for something you	75	Rxvt-unicode tries to obey the rule of not charging you for something you
469	don't use. One thing you should try is to configure out all settings that	76	don't use. One thing you should try is to configure out all settings that
470	you don't need, for example, Xft support is a resource hog by design,	77	you don't need, for example, Xft support is a resource hog by design,
471	when used. Compiling it out ensures that no Xft font will be loaded	78	when used. Compiling it out ensures that no Xft font will be loaded
…		…
476	6 bytes per screen cell. For a 160x?? window this amounts to almost a	83	6 bytes per screen cell. For a 160x?? window this amounts to almost a
477	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)	84	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
478	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as	85	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
479	rxvt-unicode then uses 8 bytes per screen cell.	86	rxvt-unicode then uses 8 bytes per screen cell.
480		87
		88	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
		89
		90	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
		91	display, create the listening socket and then fork.
		92
		93	=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c?
		94
		95	If you want to start @@URXVT_NAME@@d automatically whenever you run
		96	@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
		97
		98	#!/bin/sh
		99	@@URXVT_NAME@@c "$@"
		100	if [ $? -eq 2 ]; then
		101	@@URXVT_NAME@@d -q -o -f
		102	@@URXVT_NAME@@c "$@"
		103	fi
		104
		105	This tries to create a new terminal, and if fails with exit status 2,
		106	meaning it couldn't connect to the daemon, it will start the daemon and
		107	re-run the command. Subsequent invocations of the script will re-use the
		108	existing daemon.
		109
		110	=head3 How do I distinguish whether I'm running rxvt-unicode or a regular
		111	xterm? I need this to decide about setting colours etc.
		112
		113	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
		114	so you can check and see if that is set. Note that several programs, JED,
		115	slrn, Midnight Commander automatically check this variable to decide
		116	whether or not to use colour.
		117
		118	=head3 How do I set the correct, full IP address for the DISPLAY variable?
		119
		120	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		121	insecure mode then it is possible to use the following shell script
		122	snippets to correctly set the display. If your version of rxvt-unicode
		123	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		124	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		125	regular xterm.
		126
		127	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		128	snippets:
		129
		130	# Bourne/Korn/POSIX family of shells:
		131	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		132	if [ ${TERM:-foo} = xterm ]; then
		133	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		134	echo -n '^[Z'
		135	read term_id
		136	stty icanon echo
		137	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		138	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		139	read DISPLAY # set it in our local shell
		140	fi
		141	fi
		142
		143	=head3 How do I compile the manual pages on my own?
		144
		145	You need to have a recent version of perl installed as F</usr/bin/perl>,
		146	one that comes with F<pod2man>, F<pod2text> and F<pod2xhtml> (from
		147	F<Pod::Xhtml>). Then go to the doc subdirectory and enter C<make alldoc>.
		148
		149	=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
		150
		151	I often get asked about this, and I think, no, they didn't cause extra
		152	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
		153	that the urxvt binary is larger (due to some encoding tables always being
		154	compiled in), but it actually uses less memory (RSS) after startup. Even
		155	with C<--disable-everything>, this comparison is a bit unfair, as many
		156	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		157	already in use in this mode.
		158
		159	text data bss drs rss filename
		160	98398 1664 24 15695 1824 rxvt --disable-everything
		161	188985 9048 66616 18222 1788 urxvt --disable-everything
		162
		163	When you C<--enable-everything> (which I<is> unfair, as this involves xft
		164	and full locale/XIM support which are quite bloaty inside libX11 and my
		165	libc), the two diverge, but not unreasonably so.
		166
		167	text data bss drs rss filename
		168	163431 2152 24 20123 2060 rxvt --enable-everything
		169	1035683 49680 66648 29096 3680 urxvt --enable-everything
		170
		171	The very large size of the text section is explained by the east-asian
		172	encoding tables, which, if unused, take up disk space but nothing else
		173	and can be compiled out unless you rely on X11 core fonts that use those
		174	encodings. The BSS size comes from the 64k emergency buffer that my c++
		175	compiler allocates (but of course doesn't use unless you are out of
		176	memory). Also, using an xft font instead of a core font immediately adds a
		177	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
		178	not used.
		179
		180	Of course, due to every character using two or four bytes instead of one,
		181	a large scrollback buffer will ultimately make rxvt-unicode use more
		182	memory.
		183
		184	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
		185	still fares rather well. And compared to some monsters like gnome-terminal
		186	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
		187	43180k in daemons that stay around after exit, plus half a minute of
		188	startup time, including the hundreds of warnings it spits out), it fares
		189	extremely well g.
		190
		191	=head3 Why C++, isn't that unportable/bloated/uncool?
		192
		193	Is this a question? :) It comes up very often. The simple answer is: I had
		194	to write it, and C++ allowed me to write and maintain it in a fraction
		195	of the time and effort (which is a scarce resource for me). Put even
		196	shorter: It simply wouldn't exist without C++.
		197
		198	My personal stance on this is that C++ is less portable than C, but in
		199	the case of rxvt-unicode this hardly matters, as its portability limits
		200	are defined by things like X11, pseudo terminals, locale support and unix
		201	domain sockets, which are all less portable than C++ itself.
		202
		203	Regarding the bloat, see the above question: It's easy to write programs
		204	in C that use gobs of memory, an certainly possible to write programs in
		205	C++ that don't. C++ also often comes with large libraries, but this is
		206	not necessarily the case with GCC. Here is what rxvt links against on my
		207	system with a minimal config:
		208
		209	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		210	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
		211	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
		212	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		213
		214	And here is rxvt-unicode:
		215
		216	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		217	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		218	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
		219	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
		220	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		221
		222	No large bloated libraries (of course, none were linked in statically),
		223	except maybe libX11 :)
		224
		225
		226	=head2 Rendering, Font & Look and Feel Issues
		227
		228	=head3 I can't get transparency working, what am I doing wrong?
		229
		230	First of all, please address all transparency related issues to Sasha Vasko at
		231	sasha@aftercode.net and do not bug the author about it. Also, if you can't
		232	get it working consider it a rite of passage: ... and you failed.
		233
		234	Here are four ways to get transparency. B<Do> read the manpage and option
		235	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
		236
		237	1. Use transparent mode:
		238
		239	Esetroot wallpaper.jpg
		240	@@URXVT_NAME@@ -tr -tint red -sh 40
		241
		242	That works. If you think it doesn't, you lack transparency and tinting
		243	support, or you are unable to read.
		244
		245	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		246	to use effects other than tinting and shading: Just shade/tint/whatever
		247	your picture with gimp or any other tool:
		248
		249	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
		250	@@URXVT_NAME@@ -pixmap "background.jpg;:root"
		251
		252	That works. If you think it doesn't, you lack AfterImage support, or you
		253	are unable to read.
		254
		255	3. Use an ARGB visual:
		256
		257	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		258
		259	This requires XFT support, and the support of your X-server. If that
		260	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		261	there yet, no matter what they claim. Rxvt-Unicode contains the necessary
		262	bugfixes and workarounds for Xft and Xlib to make it work, but that
		263	doesn't mean that your WM has the required kludges in place.
		264
		265	4. Use xcompmgr and let it do the job:
		266
		267	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		268	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		269
		270	Then click on a window you want to make transparent. Replace C<0xc0000000>
		271	by other values to change the degree of opacity. If it doesn't work and
		272	your server crashes, you got to keep the pieces.
		273
		274	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		275
		276	Most fonts were not designed for terminal use, which means that character
		277	size varies a lot. A font that is otherwise fine for terminal use might
		278	contain some characters that are simply too wide. Rxvt-unicode will avoid
		279	these characters. For characters that are just "a bit" too wide a special
		280	"careful" rendering mode is used that redraws adjacent characters.
		281
		282	All of this requires that fonts do not lie about character sizes,
		283	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		284	box, and rxvt-unicode has no way of detecting this (the correct way is to
		285	ask for the character bounding box, which unfortunately is wrong in these
		286	cases).
		287
		288	It's not clear (to me at least), whether this is a bug in Xft, freetype,
		289	or the respective font. If you encounter this problem you might try using
		290	the C<-lsp> option to give the font more height. If that doesn't work, you
		291	might be forced to use a different font.
		292
		293	All of this is not a problem when using X11 core fonts, as their bounding
		294	box data is correct.
		295
		296	=head3 How can I keep rxvt-unicode from using reverse video so much?
		297
		298	First of all, make sure you are running with the right terminal settings
		299	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		300	make sure you have specified colours for italic and bold, as otherwise
		301	rxvt-unicode might use reverse video to simulate the effect:
		302
		303	URxvt.colorBD: white
		304	URxvt.colorIT: green
		305
		306	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		307
		308	For some unexplainable reason, some rare programs assume a very weird
		309	colour palette when confronted with a terminal with more than the standard
		310	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		311	these programs not to assume non-ISO colours without very good reasons.
		312
		313	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		314	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		315	fix colours but keep you from using other rxvt-unicode features.
		316
		317	=head3 Can I switch the fonts at runtime?
		318
		319	Yes, using an escape sequence. Try something like this, which has the same
		320	effect as using the C<-fn> switch, and takes effect immediately:
		321
		322	printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
		323
		324	This is useful if you e.g. work primarily with japanese (and prefer a
		325	japanese font), but you have to switch to chinese temporarily, where
		326	japanese fonts would only be in your way.
		327
		328	You can think of this as a kind of manual ISO-2022 switching.
		329
		330	=head3 Why do italic characters look as if clipped?
		331
		332	Many fonts have difficulties with italic characters and hinting. For
		333	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		334	Mono> completely fails in its italic face. A workaround might be to
		335	enable freetype autohinting, i.e. like this:
		336
		337	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		338	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		339
481	=item Can I speed up Xft rendering somehow?	340	=head3 Can I speed up Xft rendering somehow?
482		341
483	Yes, the most obvious way to speed it up is to avoid Xft entirely, as	342	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
484	it is simply slow. If you still want Xft fonts you might try to disable	343	it is simply slow. If you still want Xft fonts you might try to disable
485	antialiasing (by appending C<:antialiasing=false>), which saves lots of	344	antialiasing (by appending C<:antialias=false>), which saves lots of
486	memory and also speeds up rendering considerably.	345	memory and also speeds up rendering considerably.
487		346
488	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	347	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
489		348
490	Rxvt-unicode will use whatever you specify as a font. If it needs to	349	Rxvt-unicode will use whatever you specify as a font. If it needs to
491	fall back to it's default font search list it will prefer X11 core	350	fall back to its default font search list it will prefer X11 core
492	fonts, because they are small and fast, and then use Xft fonts. It has	351	fonts, because they are small and fast, and then use Xft fonts. It has
493	antialiasing disabled for most of them, because the author thinks they	352	antialiasing disabled for most of them, because the author thinks they
494	look best that way.	353	look best that way.
495		354
496	If you want antialiasing, you have to specify the fonts manually.	355	If you want antialiasing, you have to specify the fonts manually.
497		356
498	=item Mouse cut/paste suddenly no longer works.
499
500	Make sure that mouse reporting is actually turned off since killing
501	some editors prematurely may leave the mouse in mouse report mode. I've
502	heard that tcsh may use mouse reporting unless it otherwise specified. A
503	quick check is to see if cut/paste works when the Alt or Shift keys are
504	depressed. See @@RXVT_NAME@@(7)
505
506	=item What's with this bold/blink stuff?	357	=head3 What's with this bold/blink stuff?
507		358
508	If no bold colour is set via C<colorBD:>, bold will invert text using the	359	If no bold colour is set via C<colorBD:>, bold will invert text using the
509	standard foreground colour.	360	standard foreground colour.
510		361
511	For the standard background colour, blinking will actually make the	362	For the standard background colour, blinking will actually make
512	text blink when compiled with C<--enable-blinking>. with standard	363	the text blink when compiled with C<--enable-text-blink>. Without
513	colours. Without C<--enable-blinking>, the blink attribute will be	364	C<--enable-text-blink>, the blink attribute will be ignored.
514	ignored.
515		365
516	On ANSI colours, bold/blink attributes are used to set high-intensity	366	On ANSI colours, bold/blink attributes are used to set high-intensity
517	foreground/background colors.	367	foreground/background colours.
518		368
519	color0-7 are the low-intensity colors.	369	color0-7 are the low-intensity colours.
520		370
521	color8-15 are the corresponding high-intensity colors.	371	color8-15 are the corresponding high-intensity colours.
522		372
523	=item I don't like the screen colors. How do I change them?	373	=head3 I don't like the screen colours. How do I change them?
524		374
525	You can change the screen colors at run-time using F<~/.Xdefaults>	375	You can change the screen colours at run-time using F<~/.Xdefaults>
526	resources (or as long-options).	376	resources (or as long-options).
527		377
528	Here are values that are supposed to resemble a VGA screen,	378	Here are values that are supposed to resemble a VGA screen,
529	including the murky brown that passes for low-intensity yellow:	379	including the murky brown that passes for low-intensity yellow:
530		380
…		…
544	URxvt.color12: #0000FF	394	URxvt.color12: #0000FF
545	URxvt.color13: #FF00FF	395	URxvt.color13: #FF00FF
546	URxvt.color14: #00FFFF	396	URxvt.color14: #00FFFF
547	URxvt.color15: #FFFFFF	397	URxvt.color15: #FFFFFF
548		398
549	And here is a more complete set of non-standard colors described (not by	399	And here is a more complete set of non-standard colours.
550	me) as "pretty girly".
551		400
552	URxvt.cursorColor: #dc74d1	401	URxvt.cursorColor: #dc74d1
553	URxvt.pointerColor: #dc74d1	402	URxvt.pointerColor: #dc74d1
554	URxvt.background: #0e0e0e	403	URxvt.background: #0e0e0e
555	URxvt.foreground: #4ad5e1	404	URxvt.foreground: #4ad5e1
…		…
566	URxvt.color6: #73f7ff	415	URxvt.color6: #73f7ff
567	URxvt.color14: #73f7ff	416	URxvt.color14: #73f7ff
568	URxvt.color7: #e1dddd	417	URxvt.color7: #e1dddd
569	URxvt.color15: #e1dddd	418	URxvt.color15: #e1dddd
570		419
571	=item How can I start @@RXVT_NAME@@d in a race-free way?	420	They have been described (not by me) as "pretty girly".
572		421
573	Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a	422	=head3 Why do some characters look so much different than others?
574	server that answers @@RXVT_NAME@@c's requests, so it doesn't background
575	itself.
576		423
577	To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the	424	See next entry.
578	following method to wait for the startup message before continuing:
579		425
580	{ @@RXVT_NAME@@d & } \| read	426	=head3 How does rxvt-unicode choose fonts?
581		427
		428	Most fonts do not contain the full range of Unicode, which is
		429	fine. Chances are that the font you (or the admin/package maintainer of
		430	your system/os) have specified does not cover all the characters you want
		431	to display.
		432
		433	B<rxvt-unicode> makes a best-effort try at finding a replacement
		434	font. Often the result is fine, but sometimes the chosen font looks
		435	bad/ugly/wrong. Some fonts have totally strange characters that don't
		436	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		437	intelligence to detect that a specific glyph is wrong: it has to believe
		438	the font that the characters it claims to contain indeed look correct.
		439
		440	In that case, select a font of your taste and add it to the font list,
		441	e.g.:
		442
		443	@@URXVT_NAME@@ -fn basefont,font2,font3...
		444
		445	When rxvt-unicode sees a character, it will first look at the base
		446	font. If the base font does not contain the character, it will go to the
		447	next font, and so on. Specifying your own fonts will also speed up this
		448	search and use less resources within rxvt-unicode and the X-server.
		449
		450	The only limitation is that none of the fonts may be larger than the base
		451	font, as the base font defines the terminal character cell size, which
		452	must be the same due to the way terminals work.
		453
		454	=head3 Why do some chinese characters look so different than others?
		455
		456	This is because there is a difference between script and language --
		457	rxvt-unicode does not know which language the text that is output is,
		458	as it only knows the unicode character codes. If rxvt-unicode first
		459	sees a japanese/chinese character, it might choose a japanese font for
		460	display. Subsequent japanese characters will use that font. Now, many
		461	chinese characters aren't represented in japanese fonts, so when the first
		462	non-japanese character comes up, rxvt-unicode will look for a chinese font
		463	-- unfortunately at this point, it will still use the japanese font for
		464	chinese characters that are also in the japanese font.
		465
		466	The workaround is easy: just tag a chinese font at the end of your font
		467	list (see the previous question). The key is to view the font list as
		468	a preference list: If you expect more japanese, list a japanese font
		469	first. If you expect more chinese, put a chinese font first.
		470
		471	In the future it might be possible to switch language preferences at
		472	runtime (the internal data structure has no problem with using different
		473	fonts for the same character at the same time, but no interface for this
		474	has been designed yet).
		475
		476	Until then, you might get away with switching fonts at runtime (see L<Can
		477	I switch the fonts at runtime?> later in this document).
		478
		479	=head3 How can I make mplayer display video correctly?
		480
		481	We are working on it, in the meantime, as a workaround, use something like:
		482
		483	@@URXVT_NAME@@ -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		484
		485
		486	=head2 Keyboard, Mouse & User Interaction
		487
		488	=head3 The new selection selects pieces that are too big, how can I select single words?
		489
		490	If you want to select e.g. alphanumeric words, you can use the following
		491	setting:
		492
		493	URxvt.selection.pattern-0: ([[:word:]]+)
		494
		495	If you click more than twice, the selection will be extended
		496	more and more.
		497
		498	To get a selection that is very similar to the old code, try this pattern:
		499
		500	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{\|})]+)
		501
		502	Please also note that the I<LeftClick Shift-LeftClick> combination also
		503	selects words like the old code.
		504
		505	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		506
		507	You can disable the perl extension completely by setting the
		508	B<perl-ext-common> resource to the empty string, which also keeps
		509	rxvt-unicode from initialising perl, saving memory.
		510
		511	If you only want to disable specific features, you first have to
		512	identify which perl extension is responsible. For this, read the section
		513	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		514	example, to disable the B<selection-popup> and B<option-popup>, specify
		515	this B<perl-ext-common> resource:
		516
		517	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		518
		519	This will keep the default extensions, but disable the two popup
		520	extensions. Some extensions can also be configured, for example,
		521	scrollback search mode is triggered by B<M-s>. You can move it to any
		522	other combination either by setting the B<searchable-scrollback> resource:
		523
		524	URxvt.searchable-scrollback: CM-s
		525
		526	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		527
		528	See next entry.
		529
		530	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		531
		532	These are caused by the C<readline> perl extension. Under normal
		533	circumstances, it will move your cursor around when you click into the
		534	line that contains it. It tries hard not to do this at the wrong moment,
		535	but when running a program that doesn't parse cursor movements or in some
		536	cases during rlogin sessions, it fails to detect this properly.
		537
		538	You can permanently switch this feature off by disabling the C<readline>
		539	extension:
		540
		541	URxvt.perl-ext-common: default,-readline
		542
		543	=head3 My numerical keypad acts weird and generates differing output?
		544
		545	Some Debian GNUL/Linux users seem to have this problem, although no
		546	specific details were reported so far. It is possible that this is caused
		547	by the wrong C<TERM> setting, although the details of whether and how
		548	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		549	keymap. See the answer to the previous question, and please report if that
		550	helped.
		551
		552	=head3 My Compose (Multi_key) key is no longer working.
		553
		554	The most common causes for this are that either your locale is not set
		555	correctly, or you specified a B<preeditStyle> that is not supported by
		556	your input method. For example, if you specified B<OverTheSpot> and
		557	your input method (e.g. the default input method handling Compose keys)
		558	does not support this (for instance because it is not visual), then
		559	rxvt-unicode will continue without an input method.
		560
		561	In this case either do not specify a B<preeditStyle> or specify more than
		562	one pre-edit style, such as B<OverTheSpot,Root,None>.
		563
		564	If it still doesn't work, then maybe your input method doesn't support
		565	compose sequences - to fall back to the built-in one, make sure you don't
		566	specify an input method via C<-im> or C<XMODIFIERS>.
		567
		568	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		569
		570	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		571	international keyboards) or simply use ISO 14755 support to your
		572	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		573	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		574	character and so on.
		575
		576	=head3 Mouse cut/paste suddenly no longer works.
		577
		578	Make sure that mouse reporting is actually turned off since killing
		579	some editors prematurely may leave the mouse in mouse report mode. I've
		580	heard that tcsh may use mouse reporting unless it otherwise specified. A
		581	quick check is to see if cut/paste works when the Alt or Shift keys are
		582	depressed.
		583
582	=item What's with the strange Backspace/Delete key behaviour?	584	=head3 What's with the strange Backspace/Delete key behaviour?
583		585
584	Assuming that the physical Backspace key corresponds to the	586	Assuming that the physical Backspace key corresponds to the
585	BackSpace keysym (not likely for Linux ... see the following	587	Backspace keysym (not likely for Linux ... see the following
586	question) there are two standard values that can be used for	588	question) there are two standard values that can be used for
587	Backspace: C<^H> and C<^?>.	589	Backspace: C<^H> and C<^?>.
588		590
589	Historically, either value is correct, but rxvt-unicode adopts the debian	591	Historically, either value is correct, but rxvt-unicode adopts the debian
590	policy of using C<^?> when unsure, because it's the one only only correct	592	policy of using C<^?> when unsure, because it's the one and only correct
591	choice :).	593	choice :).
592		594
593	Rxvt-unicode tries to inherit the current stty settings and uses the value	595	It is possible to toggle between C<^H> and C<^?> with the DECBKM
594	of `erase' to guess the value for backspace. If rxvt-unicode wasn't	596	private mode:
595	started from a terminal (say, from a menu or by remote shell), then the
596	system value of `erase', which corresponds to CERASE in <termios.h>, will
597	be used (which may not be the same as your stty setting).
598
599	For starting a new rxvt-unicode:
600		597
601	# use Backspace = ^H	598	# use Backspace = ^H
602	$ stty erase ^H	599	$ stty erase ^H
603	$ @@RXVT_NAME@@	600	$ echo -n "^[[?67h"
604		601
605	# use Backspace = ^?	602	# use Backspace = ^?
606	$ stty erase ^?	603	$ stty erase ^?
607	$ @@RXVT_NAME@@
608
609	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
610
611	For an existing rxvt-unicode:
612
613	# use Backspace = ^H
614	$ stty erase ^H
615	$ echo -n "^[[36h"
616
617	# use Backspace = ^?
618	$ stty erase ^?
619	$ echo -n "^[[36l"	604	$ echo -n "^[[?67l"
620		605
621	This helps satisfy some of the Backspace discrepancies that occur, but	606	This helps satisfy some of the Backspace discrepancies that occur, but
622	if you use Backspace = C<^H>, make sure that the termcap/terminfo value	607	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
623	properly reflects that.	608	properly reflects that.
624		609
…		…
633	some editors (vim I'm told) expect Backspace = ^H,	618	some editors (vim I'm told) expect Backspace = ^H,
634	GNU Emacs (and Emacs-like editors) use ^H for help.	619	GNU Emacs (and Emacs-like editors) use ^H for help.
635		620
636	Perhaps someday this will all be resolved in a consistent manner.	621	Perhaps someday this will all be resolved in a consistent manner.
637		622
638	=item I don't like the key-bindings. How do I change them?	623	=head3 I don't like the key-bindings. How do I change them?
639		624
640	There are some compile-time selections available via configure. Unless	625	There are some compile-time selections available via configure. Unless
641	you have run "configure" with the C<--disable-resources> option you can	626	you have run "configure" with the C<--disable-resources> option you can
642	use the `keysym' resource to alter the keystrings associated with keysyms.	627	use the `keysym' resource to alter the keystrings associated with keysyms.
643		628
644	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>	629	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
645		630
646	URxvt.keysym.Home: \033[1~	631	URxvt.keysym.Home: \033[1~
647	URxvt.keysym.End: \033[4~	632	URxvt.keysym.End: \033[4~
648	URxvt.keysym.C-apostrophe: \033<C-'>	633	URxvt.keysym.C-apostrophe: \033<C-'>
649	URxvt.keysym.C-slash: \033<C-/>	634	URxvt.keysym.C-slash: \033<C-/>
…		…
664	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >	649	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
665	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007	650	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
666		651
667	See some more examples in the documentation for the B<keysym> resource.	652	See some more examples in the documentation for the B<keysym> resource.
668		653
669	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.	654	=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
670	How do I make use of them? For example, the Sun Keyboard type 4
671	has the following mappings that rxvt-unicode doesn't recognize.
672		655
673	KP_Insert == Insert	656	KP_Insert == Insert
674	F22 == Print	657	F22 == Print
675	F27 == Home	658	F27 == Home
676	F29 == Prior	659	F29 == Prior
…		…
679		662
680	Rather than have rxvt-unicode try to accommodate all the various possible	663	Rather than have rxvt-unicode try to accommodate all the various possible
681	keyboard mappings, it is better to use `xmodmap' to remap the keys as	664	keyboard mappings, it is better to use `xmodmap' to remap the keys as
682	required for your particular machine.	665	required for your particular machine.
683		666
684	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
685	I need this to decide about setting colors etc.
686		667
687	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can	668	=head2 Terminal Configuration
688	check and see if that is set. Note that several programs, JED, slrn,
689	Midnight Commander automatically check this variable to decide whether or
690	not to use color.
691		669
692	=item How do I set the correct, full IP address for the DISPLAY variable?	670	=head3 Can I see a typical configuration?
693		671
694	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled	672	The default configuration tries to be xterm-like, which I don't like that
695	insecure mode then it is possible to use the following shell script	673	much, but it's least surprise to regular users.
696	snippets to correctly set the display. If your version of rxvt-unicode
697	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
698	the COLORTERM variable can be used to distinguish rxvt-unicode from a
699	regular xterm.
700		674
701	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script	675	As a rxvt or rxvt-unicode user, you are practically supposed to invest
702	snippets:	676	time into customising your terminal. To get you started, here is the
		677	author's .Xdefaults entries, with comments on what they do. It's certainly
		678	not I<typical>, but what's typical...
703		679
704	# Bourne/Korn/POSIX family of shells:	680	URxvt.cutchars: "()*,<>[]{}\|'
705	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know	681	URxvt.print-pipe: cat >/tmp/xxx
706	if [ ${TERM:-foo} = xterm ]; then
707	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
708	echo -n '^[Z'
709	read term_id
710	stty icanon echo
711	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
712	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
713	read DISPLAY # set it in our local shell
714	fi
715	fi
716		682
717	=item How do I compile the manual pages for myself?	683	These are just for testing stuff.
718		684
719	You need to have a recent version of perl installed as F</usr/bin/perl>,	685	URxvt.imLocale: ja_JP.UTF-8
720	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to	686	URxvt.preeditType: OnTheSpot,None
721	the doc subdirectory and enter C<make alldoc>.
722		687
723	=item My question isn't answered here, can I ask a human?	688	This tells rxvt-unicode to use a special locale when communicating with
		689	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		690	type, which requires the C<xim-onthespot> perl extension but rewards me
		691	with correct-looking fonts.
724		692
725	Before sending me mail, you could go to IRC: C<irc.freenode.net>,	693	URxvt.perl-lib: /root/lib/urxvt
726	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be	694	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
727	interested in learning about new and exciting problems (but not FAQs :).	695	URxvt.selection.pattern-0: ( at .*? line \\d+)
		696	URxvt.selection.pattern-1: ^(/[^:]+):\
		697	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		698	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		699
		700	This is my perl configuration. The first two set the perl library
		701	directory and also tells urxvt to use a large number of extensions. I
		702	develop for myself mostly, so I actually use most of the extensions I
		703	write.
		704
		705	The selection stuff mainly makes the selection perl-error-message aware
		706	and tells it to convert perl error messages into vi-commands to load the
		707	relevant file and go to the error line number.
		708
		709	URxvt.scrollstyle: plain
		710	URxvt.secondaryScroll: true
		711
		712	As the documentation says: plain is the preferred scrollbar for the
		713	author. The C<secondaryScroll> configures urxvt to scroll in full-screen
		714	apps, like screen, so lines scrolled out of screen end up in urxvt's
		715	scrollback buffer.
		716
		717	URxvt.background: #000000
		718	URxvt.foreground: gray90
		719	URxvt.color7: gray90
		720	URxvt.colorBD: #ffffff
		721	URxvt.cursorColor: #e0e080
		722	URxvt.throughColor: #8080f0
		723	URxvt.highlightColor: #f0f0f0
		724
		725	Some colours. Not sure which ones are being used or even non-defaults, but
		726	these are in my .Xdefaults. Most notably, they set foreground/background
		727	to light gray/black, and also make sure that the colour 7 matches the
		728	default foreground colour.
		729
		730	URxvt.underlineColor: yellow
		731
		732	Another colour, makes underline lines look different. Sometimes hurts, but
		733	is mostly a nice effect.
		734
		735	URxvt.geometry: 154x36
		736	URxvt.loginShell: false
		737	URxvt.meta: ignore
		738	URxvt.utmpInhibit: true
		739
		740	Uh, well, should be mostly self-explanatory. By specifying some defaults
		741	manually, I can quickly switch them for testing.
		742
		743	URxvt.saveLines: 8192
		744
		745	A large scrollback buffer is essential. Really.
		746
		747	URxvt.mapAlert: true
		748
		749	The only case I use it is for my IRC window, which I like to keep
		750	iconified till people msg me (which beeps).
		751
		752	URxvt.visualBell: true
		753
		754	The audible bell is often annoying, especially when in a crowd.
		755
		756	URxvt.insecure: true
		757
		758	Please don't hack my mutt! Ooops...
		759
		760	URxvt.pastableTabs: false
		761
		762	I once thought this is a great idea.
		763
		764	urxvt.font: 9x15bold,\
		765	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		766	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		767	[codeset=JISX0208]xft:Kochi Gothic, \
		768	xft:Bitstream Vera Sans Mono:autohint=true, \
		769	xft:Code2000:antialias=false
		770	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		771	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		772	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		773
		774	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		775	overwhelmed. A special note: the C<9x15bold> mentioned above is actually
		776	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		777	font (different glyphs for C<;> and many other harmless characters),
		778	while the second font is actually the C<9x15bold> from XFree4/XOrg. The
		779	bold version has less chars than the medium version, so I use it for rare
		780	characters, too. When editing sources with vim, I use italic for comments
		781	and other stuff, which looks quite good with Bitstream Vera anti-aliased.
		782
		783	Terminus is a quite bad font (many very wrong glyphs), but for most of my
		784	purposes, it works, and gives a different look, as my normal (Non-bold)
		785	font is already bold, and I want to see a difference between bold and
		786	normal fonts.
		787
		788	Please note that I used the C<urxvt> instance name and not the C<URxvt>
		789	class name. That is because I use different configs for different purposes,
		790	for example, my IRC window is started with C<-name IRC>, and uses these
		791	defaults:
		792
		793	IRC*title: IRC
		794	IRC*geometry: 87x12+535+542
		795	IRC*saveLines: 0
		796	IRC*mapAlert: true
		797	IRC*font: suxuseuro
		798	IRC*boldFont: suxuseuro
		799	IRC*colorBD: white
		800	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		801	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		802
		803	C<Alt-Ctrl-1> and C<Alt-Ctrl-2> switch between two different font
		804	sizes. C<suxuseuro> allows me to keep an eye (and actually read)
		805	stuff while keeping a very small window. If somebody pastes something
		806	complicated (e.g. japanese), I temporarily switch to a larger font.
		807
		808	The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor
		809	C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname>
		810	file for different hosts, for example, on my main desktop, I use:
		811
		812	URxvt.keysym.C-M-q: command:\033[3;5;5t
		813	URxvt.keysym.C-M-y: command:\033[3;5;606t
		814	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		815	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		816	URxvt.keysym.C-M-p: perl:test
		817
		818	The first for keysym definitions allow me to quickly bring some windows
		819	in the layout I like most. Ion users might start laughing but will stop
		820	immediately when I tell them that I use my own Fvwm2 module for much the
		821	same effect as Ion provides, and I only very rarely use the above key
		822	combinations :->
		823
		824	=head3 Why doesn't rxvt-unicode read my resources?
		825
		826	Well, why, indeed? It does, in a way very similar to other X
		827	applications. Most importantly, this means that if you or your OS loads
		828	resources into the X display (the right way to do it), rxvt-unicode will
		829	ignore any resource files in your home directory. It will only read
		830	F<$HOME/.Xdefaults> when no resources are attached to the display.
		831
		832	If you have or use an F<$HOME/.Xresources> file, chances are that
		833	resources are loaded into your X-server. In this case, you have to
		834	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		835
		836	Also consider the form resources have to use:
		837
		838	URxvt.resource: value
		839
		840	If you want to use another form (there are lots of different ways of
		841	specifying resources), make sure you understand whether and why it
		842	works. If unsure, use the form above.
		843
		844	=head3 When I log-in to another system it tells me about missing terminfo data?
		845
		846	The terminal description used by rxvt-unicode is not as widely available
		847	as that for xterm, or even rxvt (for which the same problem often arises).
		848
		849	The correct solution for this problem is to install the terminfo, this can
		850	be done by simply installing rxvt-unicode on the remote system as well
		851	(in case you have a nice package manager ready), or you can install the
		852	terminfo database manually like this (with ncurses infocmp. works as
		853	user and root):
		854
		855	REMOTE=remotesystem.domain
		856	infocmp rxvt-unicode \| ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
		857
		858	One some systems you might need to set C<$TERMINFO> to the full path of
		859	F<$HOME/.terminfo> for this to work.
		860
		861	If you cannot or do not want to do this, then you can simply set
		862	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
		863	problems arising, which includes wrong keymapping, less and different
		864	colours and some refresh errors in fullscreen applications. It's a nice
		865	quick-and-dirty workaround for rare cases, though.
		866
		867	If you always want to do this (and are fine with the consequences) you
		868	can either recompile rxvt-unicode with the desired TERM value or use a
		869	resource to set it:
		870
		871	URxvt.termName: rxvt
		872
		873	If you don't plan to use B<rxvt> (quite common...) you could also replace
		874	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
		875
		876	=head3 nano fails with "Error opening terminal: rxvt-unicode"
		877
		878	This exceptionally confusing and useless error message is printed by nano
		879	when it can't find the terminfo database. Nothing is wrong with your
		880	terminal, read the previous answer for a solution.
		881
		882	=head3 C<tic> outputs some error when compiling the terminfo entry.
		883
		884	Most likely it's the empty definition for C<enacs=>. Just replace it by
		885	C<enacs=\E[0@> and try again.
		886
		887	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
		888
		889	See next entry.
		890
		891	=head3 I need a termcap file entry.
		892
		893	One reason you might want this is that some distributions or operating
		894	systems still compile some programs using the long-obsoleted termcap
		895	library (Fedora Core's bash is one example) and rely on a termcap entry
		896	for C<rxvt-unicode>.
		897
		898	You could use rxvt's termcap entry with reasonable results in many cases.
		899	You can also create a termcap entry by using terminfo's infocmp program
		900	like this:
		901
		902	infocmp -C rxvt-unicode
		903
		904	Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap,
		905	generated by the command above.
		906
		907	=head3 Why does C<ls> no longer have coloured output?
		908
		909	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
		910	decide whether a terminal has colour, but uses its own configuration
		911	file. Needless to say, C<rxvt-unicode> is not in its default file (among
		912	with most other terminals supporting colour). Either add:
		913
		914	TERM rxvt-unicode
		915
		916	to C</etc/DIR_COLORS> or simply add:
		917
		918	alias ls='ls --color=auto'
		919
		920	to your C<.profile> or C<.bashrc>.
		921
		922	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
		923
		924	See next entry.
		925
		926	=head3 Why doesn't vim/emacs etc. make use of italic?
		927
		928	See next entry.
		929
		930	=head3 Why are the secondary screen-related options not working properly?
		931
		932	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
		933	distributions (most notably Debian GNU/Linux) break rxvt-unicode
		934	by setting C<TERM> to C<rxvt>, which doesn't have these extra
		935	features. Unfortunately, some of these (most notably, again, Debian
		936	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
		937	file, so you will need to install it on your own (See the question B<When
		938	I log-in to another system it tells me about missing terminfo data?> on
		939	how to do this).
		940
		941
		942	=head2 Encoding / Locale / Input Method Issues
		943
		944	=head3 Rxvt-unicode does not seem to understand the selected encoding?
		945
		946	See next entry.
		947
		948	=head3 Unicode does not seem to work?
		949
		950	If you encounter strange problems like typing an accented character but
		951	getting two unrelated other characters or similar, or if program output is
		952	subtly garbled, then you should check your locale settings.
		953
		954	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
		955	programs running in it. Often rxvt-unicode is started in the C<C> locale,
		956	while the login script running within the rxvt-unicode window changes the
		957	locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is
		958	not going to work, and is the most common cause for problems.
		959
		960	The best thing is to fix your startup environment, as you will likely run
		961	into other problems. If nothing works you can try this in your .profile.
		962
		963	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
		964
		965	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
		966	supported on your systems. Some systems have a C<locale> command which
		967	displays this (also, C<perl -e0> can be used to check locale settings, as
		968	it will complain loudly if it cannot set the locale). If it displays something
		969	like:
		970
		971	locale: Cannot set LC_CTYPE to default locale: ...
		972
		973	Then the locale you specified is not supported on your system.
		974
		975	If nothing works and you are sure that everything is set correctly then
		976	you will need to remember a little known fact: Some programs just don't
		977	support locales :(
		978
		979	=head3 How does rxvt-unicode determine the encoding to use?
		980
		981	See next entry.
		982
		983	=head3 Is there an option to switch encodings?
		984
		985	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		986	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
		987	UTF-8 or any other encodings with respect to terminal I/O.
		988
		989	The reasons is that there exists a perfectly fine mechanism for selecting
		990	the encoding, doing I/O and (most important) communicating this to all
		991	applications so everybody agrees on character properties such as width
		992	and code number. This mechanism is the I<locale>. Applications not using
		993	that info will have problems (for example, C<xterm> gets the width of
		994	characters wrong as it uses its own, locale-independent table under all
		995	locales).
		996
		997	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
		998	programs doing the same (that is, most) will automatically agree in the
		999	interpretation of characters.
		1000
		1001	Unfortunately, there is no system-independent way to select locales, nor
		1002	is there a standard on how locale specifiers will look like.
		1003
		1004	On most systems, the content of the C<LC_CTYPE> environment variable
		1005	contains an arbitrary string which corresponds to an already-installed
		1006	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1007	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1008	(i.e. C<de> or C<german>) are also common.
		1009
		1010	Rxvt-unicode ignores all other locale categories, and except for
		1011	the encoding, ignores country or language-specific settings,
		1012	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		1013	rxvt-unicode.
		1014
		1015	If you want to use a specific encoding you have to make sure you start
		1016	rxvt-unicode with the correct C<LC_CTYPE> category.
		1017
		1018	=head3 Can I switch locales at runtime?
		1019
		1020	Yes, using an escape sequence. Try something like this, which sets
		1021	rxvt-unicode's idea of C<LC_CTYPE>.
		1022
		1023	printf '\33]701;%s\007' ja_JP.SJIS
		1024
		1025	See also the previous answer.
		1026
		1027	Sometimes this capability is rather handy when you want to work in
		1028	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		1029	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		1030	first switches to a locale supported by xjdic and back later:
		1031
		1032	printf '\33]701;%s\007' ja_JP.SJIS
		1033	xjdic -js
		1034	printf '\33]701;%s\007' de_DE.UTF-8
		1035
		1036	You can also use xterm's C<luit> program, which usually works fine, except
		1037	for some locales where character width differs between program- and
		1038	rxvt-unicode-locales.
		1039
		1040	=head3 I have problems getting my input method working.
		1041
		1042	Try a search engine, as this is slightly different for every input method server.
		1043
		1044	Here is a checklist:
		1045
		1046	=over 4
		1047
		1048	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		1049
		1050	Try C<locale -a> or check the documentation for your OS.
		1051
		1052	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		1053
		1054	For example, B<kinput2> does not support UTF-8 locales, you should use
		1055	C<ja_JP.EUC-JP> or equivalent.
		1056
		1057	=item - Make sure your XIM server is actually running.
		1058
		1059	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		1060
		1061	When you want to use e.g. B<kinput2>, it must be set to
		1062	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
		1063	method servers are running with this command:
		1064
		1065	xprop -root XIM_SERVERS
		1066
		1067	=item
728		1068
729	=back	1069	=back
730		1070
		1071	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		1072
		1073	You can specify separate locales for the input method and the rest of the
		1074	terminal, using the resource C<imlocale>:
		1075
		1076	URxvt.imlocale: ja_JP.EUC-JP
		1077
		1078	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1079	use your input method. Please note, however, that, depending on your Xlib
		1080	version, you may not be able to input characters outside C<EUC-JP> in a
		1081	normal way then, as your input method limits you.
		1082
		1083	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		1084
		1085	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1086	design. Applications can avoid some crashes at the expense of memory
		1087	leaks, and Input Methods can avoid some crashes by careful ordering at
		1088	exit time. B<kinput2> (and derived input methods) generally succeeds,
		1089	while B<SCIM> (or similar input methods) fails. In the end, however,
		1090	crashes cannot be completely avoided even if both sides cooperate.
		1091
		1092	So the only workaround is not to kill your Input Method Servers.
		1093
		1094
		1095	=head2 Operating Systems / Package Maintaining
		1096
		1097	=head3 I am using Debian GNU/Linux and have a problem...
		1098
		1099	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1100	patches that considerably change the behaviour of rxvt-unicode (but
		1101	unfortunately this notice has been removed). Before reporting a bug to
		1102	the original rxvt-unicode author please download and install the genuine
		1103	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1104	the problem. If you cannot, chances are that the problems are specific to
		1105	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1106	Tracking System (use C<reportbug> to report the bug).
		1107
		1108	For other problems that also affect the Debian package, you can and
		1109	probably should use the Debian BTS, too, because, after all, it's also a
		1110	bug in the Debian version and it serves as a reminder for other users that
		1111	might encounter the same issue.
		1112
		1113	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1114
		1115	You should build one binary with the default options. F<configure>
		1116	now enables most useful options, and the trend goes to making them
		1117	runtime-switchable, too, so there is usually no drawback to enabling them,
		1118	except higher disk and possibly memory usage. The perl interpreter should
		1119	be enabled, as important functionality (menus, selection, likely more in
		1120	the future) depends on it.
		1121
		1122	You should not overwrite the C<perl-ext-common> and C<perl-ext> resources
		1123	system-wide (except maybe with C<defaults>). This will result in useful
		1124	behaviour. If your distribution aims at low memory, add an empty
		1125	C<perl-ext-common> resource to the app-defaults file. This will keep the
		1126	perl interpreter disabled until the user enables it.
		1127
		1128	If you can/want build more binaries, I recommend building a minimal
		1129	one with C<--disable-everything> (very useful) and a maximal one with
		1130	C<--enable-everything> (less useful, it will be very big due to a lot of
		1131	encodings built-in that increase download times and are rarely used).
		1132
		1133	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1134
		1135	It should be, starting with release 7.1. You are encouraged to properly
		1136	install urxvt with privileges necessary for your OS now.
		1137
		1138	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1139	into a helper process for privileged operations (pty handling on some
		1140	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1141	immediately. This is much safer than most other terminals that keep
		1142	privileges while running (but is more relevant to urxvt, as it contains
		1143	things as perl interpreters, which might be "helpful" to attackers).
		1144
		1145	This forking is done as the very first within main(), which is very early
		1146	and reduces possible bugs to initialisation code run before main(), or
		1147	things like the dynamic loader of your system, which should result in very
		1148	little risk.
		1149
		1150	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
		1151
		1152	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
		1153	in your compile environment, or an implementation that implements it,
		1154	whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
		1155	B<wchar_t> is represented as unicode.
		1156
		1157	As you might have guessed, FreeBSD does neither define this symbol nor
		1158	does it support it. Instead, it uses its own internal representation of
		1159	B<wchar_t>. This is, of course, completely fine with respect to standards.
		1160
		1161	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
		1162	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>).
		1163
		1164	C<__STDC_ISO_10646__> is the only sane way to support multi-language
		1165	apps in an OS, as using a locale-dependent (and non-standardized)
		1166	representation of B<wchar_t> makes it impossible to convert between
		1167	B<wchar_t> (as used by X11 and your applications) and any other encoding
		1168	without implementing OS-specific-wrappers for each and every locale. There
		1169	simply are no APIs to convert B<wchar_t> into anything except the current
		1170	locale encoding.
		1171
		1172	Some applications (such as the formidable B<mlterm>) work around this
		1173	by carrying their own replacement functions for character set handling
		1174	with them, and either implementing OS-dependent hacks or doing multiple
		1175	conversions (which is slow and unreliable in case the OS implements
		1176	encodings slightly different than the terminal emulator).
		1177
		1178	The rxvt-unicode author insists that the right way to fix this is in the
		1179	system libraries once and for all, instead of forcing every app to carry
		1180	complete replacements for them :)
		1181
		1182	=head3 How can I use rxvt-unicode under cygwin?
		1183
		1184	rxvt-unicode should compile and run out of the box on cygwin, using
		1185	the X11 libraries that come with cygwin. libW11 emulation is no
		1186	longer supported (and makes no sense, either, as it only supported a
		1187	single font). I recommend starting the X-server in C<-multiwindow> or
		1188	C<-rootless> mode instead, which will result in similar look&feel as the
		1189	old libW11 emulation.
		1190
		1191	At the time of this writing, cygwin didn't seem to support any multi-byte
		1192	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		1193	to 8-bit encodings.
		1194
		1195	=head3 Character widths are not correct.
		1196
		1197	urxvt uses the system wcwidth function to know the information about
		1198	the width of characters, so on systems with incorrect locale data you
		1199	will likely get bad results. Two notorious examples are Solaris 9,
		1200	where single-width characters like U+2514 are reported as double-width,
		1201	and Darwin 8, where combining chars are reported having width 1.
		1202
		1203	The solution is to upgrade your system or switch to a better one. A
		1204	possibly working workaround is to use a wcwidth implementation like
		1205
		1206	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
		1207
731	=head1 RXVT TECHNICAL REFERENCE	1208	=head1 RXVT-UNICODE TECHNICAL REFERENCE
732
733	=head1 DESCRIPTION
734		1209
735	The rest of this document describes various technical aspects of	1210	The rest of this document describes various technical aspects of
736	B<rxvt-unicode>. First the description of supported command sequences,	1211	B<rxvt-unicode>. First the description of supported command sequences,
737	followed by menu and pixmap support and last by a description of all	1212	followed by pixmap support and last by a description of all features
738	features selectable at C<configure> time.	1213	selectable at C<configure> time.
739		1214
740	=head1 Definitions	1215	=head2 Definitions
741		1216
742	=over 4	1217	=over 4
743		1218
744	=item B<< C<c> >>	1219	=item B<< C<c> >>
745		1220
…		…
763		1238
764	A text parameter composed of printable characters.	1239	A text parameter composed of printable characters.
765		1240
766	=back	1241	=back
767		1242
768	=head1 Values	1243	=head2 Values
769		1244
770	=over 4	1245	=over 4
771		1246
772	=item B<< C<ENQ> >>	1247	=item B<< C<ENQ> >>
773		1248
…		…
816		1291
817	Space Character	1292	Space Character
818		1293
819	=back	1294	=back
820		1295
821	=head1 Escape Sequences	1296	=head2 Escape Sequences
822		1297
823	=over 4	1298	=over 4
824		1299
825	=item B<< C<ESC # 8> >>	1300	=item B<< C<ESC # 8> >>
826		1301
…		…
836		1311
837	=item B<< C<ESC => >>	1312	=item B<< C<ESC => >>
838		1313
839	Application Keypad (SMKX). See also next sequence.	1314	Application Keypad (SMKX). See also next sequence.
840		1315
841	=item B<<< C<< ESC >> >>>	1316	=item B<<< C<< ESC > >> >>>
842		1317
843	Normal Keypad (RMKX)	1318	Normal Keypad (RMKX)
844		1319
845	B<Note:> If the numeric keypad is activated, eg, B<Num_Lock> has been	1320	B<Note:> If the numeric keypad is activated, eg, B<Num_Lock> has been
846	pressed, numbers or control functions are generated by the numeric keypad	1321	pressed, numbers or control functions are generated by the numeric keypad
…		…
924		1399
925	=back	1400	=back
926		1401
927	X<CSI>	1402	X<CSI>
928		1403
929	=head1 CSI (Command Sequence Introducer) Sequences	1404	=head2 CSI (Command Sequence Introducer) Sequences
930		1405
931	=over 4	1406	=over 4
932		1407
933	=item B<< C<ESC [ Ps @> >>	1408	=item B<< C<ESC [ Ps @> >>
934		1409
…		…
989	=begin table	1464	=begin table
990		1465
991	B<< C<Ps = 0> >> Clear to Right (default)	1466	B<< C<Ps = 0> >> Clear to Right (default)
992	B<< C<Ps = 1> >> Clear to Left	1467	B<< C<Ps = 1> >> Clear to Left
993	B<< C<Ps = 2> >> Clear All	1468	B<< C<Ps = 2> >> Clear All
		1469	B<< C<Ps = 3> >> Like Ps = 0, but is ignored when wrapped
		1470	(@@RXVT_NAME@@ extension)
994		1471
995	=end table	1472	=end table
996		1473
997	=item B<< C<ESC [ Ps L> >>	1474	=item B<< C<ESC [ Ps L> >>
998		1475
…		…
1130	B<< C<Ps = 32 / 42> >> fg/bg Green	1607	B<< C<Ps = 32 / 42> >> fg/bg Green
1131	B<< C<Ps = 33 / 43> >> fg/bg Yellow	1608	B<< C<Ps = 33 / 43> >> fg/bg Yellow
1132	B<< C<Ps = 34 / 44> >> fg/bg Blue	1609	B<< C<Ps = 34 / 44> >> fg/bg Blue
1133	B<< C<Ps = 35 / 45> >> fg/bg Magenta	1610	B<< C<Ps = 35 / 45> >> fg/bg Magenta
1134	B<< C<Ps = 36 / 46> >> fg/bg Cyan	1611	B<< C<Ps = 36 / 46> >> fg/bg Cyan
1135	B<< C<Ps = 38;5 / 48;5> >> set fg/bg to color #m (ISO 8613-6)	1612	B<< C<Ps = 38;5 / 48;5> >> set fg/bg to colour #m (ISO 8613-6)
1136	B<< C<Ps = 37 / 47> >> fg/bg White	1613	B<< C<Ps = 37 / 47> >> fg/bg White
1137	B<< C<Ps = 39 / 49> >> fg/bg Default	1614	B<< C<Ps = 39 / 49> >> fg/bg Default
1138	B<< C<Ps = 90 / 100> >> fg/bg Bright Black	1615	B<< C<Ps = 90 / 100> >> fg/bg Bright Black
1139	B<< C<Ps = 91 / 101> >> fg/bg Bright Red	1616	B<< C<Ps = 91 / 101> >> fg/bg Bright Red
1140	B<< C<Ps = 92 / 102> >> fg/bg Bright Green	1617	B<< C<Ps = 92 / 102> >> fg/bg Bright Green
…		…
1204		1681
1205	=back	1682	=back
1206		1683
1207	X<PrivateModes>	1684	X<PrivateModes>
1208		1685
1209	=head1 DEC Private Modes	1686	=head2 DEC Private Modes
1210		1687
1211	=over 4	1688	=over 4
1212		1689
1213	=item B<< C<ESC [ ? Pm h> >>	1690	=item B<< C<ESC [ ? Pm h> >>
1214		1691
…		…
1230		1707
1231	Toggle DEC Private Mode Values (rxvt extension). I<where>	1708	Toggle DEC Private Mode Values (rxvt extension). I<where>
1232		1709
1233	=over 4	1710	=over 4
1234		1711
1235	=item B<< C<Ps = 1> >> (DECCKM)	1712	=item B<< C<Pm = 1> >> (DECCKM)
1236		1713
1237	=begin table	1714	=begin table
1238		1715
1239	B<< C<h> >> Application Cursor Keys	1716	B<< C<h> >> Application Cursor Keys
1240	B<< C<l> >> Normal Cursor Keys	1717	B<< C<l> >> Normal Cursor Keys
1241		1718
1242	=end table	1719	=end table
1243		1720
1244	=item B<< C<Ps = 2> >> (ANSI/VT52 mode)	1721	=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1245		1722
1246	=begin table	1723	=begin table
1247		1724
1248	B<< C<h> >> Enter VT52 mode	1725	B<< C<h> >> Enter VT52 mode
1249	B<< C<l> >> Enter VT52 mode	1726	B<< C<l> >> Enter VT52 mode
1250		1727
1251	=end table	1728	=end table
1252		1729
1253	=item B<< C<Ps = 3> >>	1730	=item B<< C<Pm = 3> >>
1254		1731
1255	=begin table	1732	=begin table
1256		1733
1257	B<< C<h> >> 132 Column Mode (DECCOLM)	1734	B<< C<h> >> 132 Column Mode (DECCOLM)
1258	B<< C<l> >> 80 Column Mode (DECCOLM)	1735	B<< C<l> >> 80 Column Mode (DECCOLM)
1259		1736
1260	=end table	1737	=end table
1261		1738
1262	=item B<< C<Ps = 4> >>	1739	=item B<< C<Pm = 4> >>
1263		1740
1264	=begin table	1741	=begin table
1265		1742
1266	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)	1743	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1267	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)	1744	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1268		1745
1269	=end table	1746	=end table
1270		1747
1271	=item B<< C<Ps = 5> >>	1748	=item B<< C<Pm = 5> >>
1272		1749
1273	=begin table	1750	=begin table
1274		1751
1275	B<< C<h> >> Reverse Video (DECSCNM)	1752	B<< C<h> >> Reverse Video (DECSCNM)
1276	B<< C<l> >> Normal Video (DECSCNM)	1753	B<< C<l> >> Normal Video (DECSCNM)
1277		1754
1278	=end table	1755	=end table
1279		1756
1280	=item B<< C<Ps = 6> >>	1757	=item B<< C<Pm = 6> >>
1281		1758
1282	=begin table	1759	=begin table
1283		1760
1284	B<< C<h> >> Origin Mode (DECOM)	1761	B<< C<h> >> Origin Mode (DECOM)
1285	B<< C<l> >> Normal Cursor Mode (DECOM)	1762	B<< C<l> >> Normal Cursor Mode (DECOM)
1286		1763
1287	=end table	1764	=end table
1288		1765
1289	=item B<< C<Ps = 7> >>	1766	=item B<< C<Pm = 7> >>
1290		1767
1291	=begin table	1768	=begin table
1292		1769
1293	B<< C<h> >> Wraparound Mode (DECAWM)	1770	B<< C<h> >> Wraparound Mode (DECAWM)
1294	B<< C<l> >> No Wraparound Mode (DECAWM)	1771	B<< C<l> >> No Wraparound Mode (DECAWM)
1295		1772
1296	=end table	1773	=end table
1297		1774
1298	=item B<< C<Ps = 8> >> I<unimplemented>	1775	=item B<< C<Pm = 8> >> I<unimplemented>
1299		1776
1300	=begin table	1777	=begin table
1301		1778
1302	B<< C<h> >> Auto-repeat Keys (DECARM)	1779	B<< C<h> >> Auto-repeat Keys (DECARM)
1303	B<< C<l> >> No Auto-repeat Keys (DECARM)	1780	B<< C<l> >> No Auto-repeat Keys (DECARM)
1304		1781
1305	=end table	1782	=end table
1306		1783
1307	=item B<< C<Ps = 9> >> X10 XTerm	1784	=item B<< C<Pm = 9> >> X10 XTerm
1308		1785
1309	=begin table	1786	=begin table
1310		1787
1311	B<< C<h> >> Send Mouse X & Y on button press.	1788	B<< C<h> >> Send Mouse X & Y on button press.
1312	B<< C<l> >> No mouse reporting.	1789	B<< C<l> >> No mouse reporting.
1313		1790
1314	=end table	1791	=end table
1315		1792
1316	=item B<< C<Ps = 10> >> (B<rxvt>)
1317
1318	=begin table
1319
1320	B<< C<h> >> menuBar visible
1321	B<< C<l> >> menuBar invisible
1322
1323	=end table
1324
1325	=item B<< C<Ps = 25> >>	1793	=item B<< C<Pm = 25> >>
1326		1794
1327	=begin table	1795	=begin table
1328		1796
1329	B<< C<h> >> Visible cursor {cnorm/cvvis}	1797	B<< C<h> >> Visible cursor {cnorm/cvvis}
1330	B<< C<l> >> Invisible cursor {civis}	1798	B<< C<l> >> Invisible cursor {civis}
1331		1799
1332	=end table	1800	=end table
1333		1801
1334	=item B<< C<Ps = 30> >>	1802	=item B<< C<Pm = 30> >>
1335		1803
1336	=begin table	1804	=begin table
1337		1805
1338	B<< C<h> >> scrollBar visisble	1806	B<< C<h> >> scrollBar visible
1339	B<< C<l> >> scrollBar invisisble	1807	B<< C<l> >> scrollBar invisible
1340		1808
1341	=end table	1809	=end table
1342		1810
1343	=item B<< C<Ps = 35> >> (B<rxvt>)	1811	=item B<< C<Pm = 35> >> (B<rxvt>)
1344		1812
1345	=begin table	1813	=begin table
1346		1814
1347	B<< C<h> >> Allow XTerm Shift+key sequences	1815	B<< C<h> >> Allow XTerm Shift+key sequences
1348	B<< C<l> >> Disallow XTerm Shift+key sequences	1816	B<< C<l> >> Disallow XTerm Shift+key sequences
1349		1817
1350	=end table	1818	=end table
1351		1819
1352	=item B<< C<Ps = 38> >> I<unimplemented>	1820	=item B<< C<Pm = 38> >> I<unimplemented>
1353		1821
1354	Enter Tektronix Mode (DECTEK)	1822	Enter Tektronix Mode (DECTEK)
1355		1823
1356	=item B<< C<Ps = 40> >>	1824	=item B<< C<Pm = 40> >>
1357		1825
1358	=begin table	1826	=begin table
1359		1827
1360	B<< C<h> >> Allow 80/132 Mode	1828	B<< C<h> >> Allow 80/132 Mode
1361	B<< C<l> >> Disallow 80/132 Mode	1829	B<< C<l> >> Disallow 80/132 Mode
1362		1830
1363	=end table	1831	=end table
1364		1832
1365	=item B<< C<Ps = 44> >> I<unimplemented>	1833	=item B<< C<Pm = 44> >> I<unimplemented>
1366		1834
1367	=begin table	1835	=begin table
1368		1836
1369	B<< C<h> >> Turn On Margin Bell	1837	B<< C<h> >> Turn On Margin Bell
1370	B<< C<l> >> Turn Off Margin Bell	1838	B<< C<l> >> Turn Off Margin Bell
1371		1839
1372	=end table	1840	=end table
1373		1841
1374	=item B<< C<Ps = 45> >> I<unimplemented>	1842	=item B<< C<Pm = 45> >> I<unimplemented>
1375		1843
1376	=begin table	1844	=begin table
1377		1845
1378	B<< C<h> >> Reverse-wraparound Mode	1846	B<< C<h> >> Reverse-wraparound Mode
1379	B<< C<l> >> No Reverse-wraparound Mode	1847	B<< C<l> >> No Reverse-wraparound Mode
1380		1848
1381	=end table	1849	=end table
1382		1850
1383	=item B<< C<Ps = 46> >> I<unimplemented>	1851	=item B<< C<Pm = 46> >> I<unimplemented>
1384		1852
1385	=item B<< C<Ps = 47> >>	1853	=item B<< C<Pm = 47> >>
1386		1854
1387	=begin table	1855	=begin table
1388		1856
1389	B<< C<h> >> Use Alternate Screen Buffer	1857	B<< C<h> >> Use Alternate Screen Buffer
1390	B<< C<l> >> Use Normal Screen Buffer	1858	B<< C<l> >> Use Normal Screen Buffer
1391		1859
1392	=end table	1860	=end table
1393		1861
1394	X<Priv66>	1862	X<Priv66>
1395		1863
1396	=item B<< C<Ps = 66> >>	1864	=item B<< C<Pm = 66> >>
1397		1865
1398	=begin table	1866	=begin table
1399		1867
1400	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>	1868	B<< C<h> >> Application Keypad (DECKPAM/DECPAM) == C<ESC =>
1401	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>	1869	B<< C<l> >> Normal Keypad (DECKPNM/DECPNM) == C<< ESC > >>
1402		1870
1403	=end table	1871	=end table
1404		1872
1405	=item B<< C<Ps = 67> >>	1873	=item B<< C<Pm = 67> >>
1406		1874
1407	=begin table	1875	=begin table
1408		1876
1409	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>	1877	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1410	B<< C<l> >> Backspace key sends B<< C<DEL> >>	1878	B<< C<l> >> Backspace key sends B<< C<DEL> >>
1411		1879
1412	=end table	1880	=end table
1413		1881
1414	=item B<< C<Ps = 1000> >> (X11 XTerm)	1882	=item B<< C<Pm = 1000> >> (X11 XTerm)
1415		1883
1416	=begin table	1884	=begin table
1417		1885
1418	B<< C<h> >> Send Mouse X & Y on button press and release.	1886	B<< C<h> >> Send Mouse X & Y on button press and release.
1419	B<< C<l> >> No mouse reporting.	1887	B<< C<l> >> No mouse reporting.
1420		1888
1421	=end table	1889	=end table
1422		1890
1423	=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented>	1891	=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1424		1892
1425	=begin table	1893	=begin table
1426		1894
1427	B<< C<h> >> Use Hilite Mouse Tracking.	1895	B<< C<h> >> Use Hilite Mouse Tracking.
1428	B<< C<l> >> No mouse reporting.	1896	B<< C<l> >> No mouse reporting.
1429		1897
1430	=end table	1898	=end table
1431		1899
		1900	=item B<< C<Pm = 1002> >> (X11 XTerm)
		1901
		1902	=begin table
		1903
		1904	B<< C<h> >> Send Mouse X & Y on button press and release, and motion with a button pressed.
		1905	B<< C<l> >> No mouse reporting.
		1906
		1907	=end table
		1908
		1909	=item B<< C<Pm = 1003> >> (X11 XTerm)
		1910
		1911	=begin table
		1912
		1913	B<< C<h> >> Send Mouse X & Y on button press and release, and motion.
		1914	B<< C<l> >> No mouse reporting.
		1915
		1916	=end table
		1917
1432	=item B<< C<Ps = 1010> >> (B<rxvt>)	1918	=item B<< C<Pm = 1010> >> (B<rxvt>)
1433		1919
1434	=begin table	1920	=begin table
1435		1921
1436	B<< C<h> >> Don't scroll to bottom on TTY output	1922	B<< C<h> >> Don't scroll to bottom on TTY output
1437	B<< C<l> >> Scroll to bottom on TTY output	1923	B<< C<l> >> Scroll to bottom on TTY output
1438		1924
1439	=end table	1925	=end table
1440		1926
1441	=item B<< C<Ps = 1011> >> (B<rxvt>)	1927	=item B<< C<Pm = 1011> >> (B<rxvt>)
1442		1928
1443	=begin table	1929	=begin table
1444		1930
1445	B<< C<h> >> Scroll to bottom when a key is pressed	1931	B<< C<h> >> Scroll to bottom when a key is pressed
1446	B<< C<l> >> Don't scroll to bottom when a key is pressed	1932	B<< C<l> >> Don't scroll to bottom when a key is pressed
1447		1933
1448	=end table	1934	=end table
1449		1935
		1936	=item B<< C<Pm = 1021> >> (B<rxvt>)
		1937
		1938	=begin table
		1939
		1940	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
		1941	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
		1942
		1943	=end table
		1944
1450	=item B<< C<Ps = 1047> >>	1945	=item B<< C<Pm = 1047> >>
1451		1946
1452	=begin table	1947	=begin table
1453		1948
1454	B<< C<h> >> Use Alternate Screen Buffer	1949	B<< C<h> >> Use Alternate Screen Buffer
1455	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it	1950	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1456		1951
1457	=end table	1952	=end table
1458		1953
1459	=item B<< C<Ps = 1048> >>	1954	=item B<< C<Pm = 1048> >>
1460		1955
1461	=begin table	1956	=begin table
1462		1957
1463	B<< C<h> >> Save cursor position	1958	B<< C<h> >> Save cursor position
1464	B<< C<l> >> Restore cursor position	1959	B<< C<l> >> Restore cursor position
1465		1960
1466	=end table	1961	=end table
1467		1962
1468	=item B<< C<Ps = 1049> >>	1963	=item B<< C<Pm = 1049> >>
1469		1964
1470	=begin table	1965	=begin table
1471		1966
1472	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it	1967	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1473	B<< C<l> >> Use Normal Screen Buffer	1968	B<< C<l> >> Use Normal Screen Buffer
1474		1969
1475	=end table	1970	=end table
1476		1971
		1972	=item B<< C<Pm = 2004> >>
		1973
		1974	=begin table
		1975
		1976	B<< C<h> >> Enable bracketed paste mode - prepend / append to the pasted text the control sequences C<ESC [ 200 ~> / C<ESC [ 201 ~>
		1977	B<< C<l> >> Disable bracketed paste mode
		1978
		1979	=end table
		1980
1477	=back	1981	=back
1478		1982
1479	=back	1983	=back
1480		1984
1481	X<XTerm>	1985	X<XTerm>
1482		1986
1483	=head1 XTerm Operating System Commands	1987	=head2 XTerm Operating System Commands
1484		1988
1485	=over 4	1989	=over 4
1486		1990
1487	=item B<< C<ESC ] Ps;Pt ST> >>	1991	=item B<< C<ESC ] Ps;Pt ST> >>
1488		1992
…		…
1495	B<< C<Ps = 0> >> Change Icon Name and Window Title to B<< C<Pt> >>	1999	B<< C<Ps = 0> >> Change Icon Name and Window Title to B<< C<Pt> >>
1496	B<< C<Ps = 1> >> Change Icon Name to B<< C<Pt> >>	2000	B<< C<Ps = 1> >> Change Icon Name to B<< C<Pt> >>
1497	B<< C<Ps = 2> >> Change Window Title to B<< C<Pt> >>	2001	B<< C<Ps = 2> >> Change Window Title to B<< C<Pt> >>
1498	B<< C<Ps = 3> >> If B<< C<Pt> >> starts with a B<< C<?> >>, query the (STRING) property of the window and return it. If B<< C<Pt> >> contains a B<< C<=> >>, set the named property to the given value, else delete the specified property.	2002	B<< C<Ps = 3> >> If B<< C<Pt> >> starts with a B<< C<?> >>, query the (STRING) property of the window and return it. If B<< C<Pt> >> contains a B<< C<=> >>, set the named property to the given value, else delete the specified property.
1499	B<< C<Ps = 4> >> B<< C<Pt> >> is a semi-colon separated sequence of one or more semi-colon separated B<number>/B<name> pairs, where B<number> is an index to a colour and B<name> is the name of a colour. Each pair causes the B<number>ed colour to be changed to B<name>. Numbers 0-7 corresponds to low-intensity (normal) colours and 8-15 corresponds to high-intensity colours. 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white	2003	B<< C<Ps = 4> >> B<< C<Pt> >> is a semi-colon separated sequence of one or more semi-colon separated B<number>/B<name> pairs, where B<number> is an index to a colour and B<name> is the name of a colour. Each pair causes the B<number>ed colour to be changed to B<name>. Numbers 0-7 corresponds to low-intensity (normal) colours and 8-15 corresponds to high-intensity colours. 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white
1500	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	2004	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >>
1501	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	2005	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >>
1502	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	2006	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1503	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	2007	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1504	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	2008	B<< C<Ps = 17> >> Change background colour of highlight characters to B<< C<Pt> >>
1505	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	2009	B<< C<Ps = 19> >> Change foreground colour of highlight characters to B<< C<Pt> >>
1506	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	2010	B<< C<Ps = 20> >> Change background pixmap parameters (see section BACKGROUND IMAGE) (Compile AfterImage).
1507	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
1508	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> >>. [deprecated, use 10]
1509	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>
1510	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> >>. [deprecated, use 11]
1511	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> >>
1512	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> >> [disabled]
1513	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).	2016	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).
1514	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).	2017	B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>.
1515	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	2018	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1516	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	2019	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
		2020	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		2021	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
		2022	B<< C<Ps = 708> >> Change colour of the border to B<< C<Pt> >>
1517	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	2023	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1518	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	2024	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1519	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	2025	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1520	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	2026	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1521	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).	2027	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1522	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).	2028	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		2029	B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1523		2030
1524	=end table	2031	=end table
1525		2032
1526	=back	2033	=back
1527		2034
1528	X<menuBar>	2035	=head1 BACKGROUND IMAGE
1529		2036
1530	=head1 menuBar
1531
1532	B<< The exact syntax used is I<almost> solidified. >>
1533	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1534	menuBar.
1535
1536	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1537	omitted: use B<./> to specify a menu relative to the current menu.
1538
1539	=head2 Overview of menuBar operation
1540
1541	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1542	of C<Pt> can be used for a variety of tasks:
1543
1544	At the top level is the current menuBar which is a member of a circular
1545	linked-list of other such menuBars.
1546
1547	The menuBar acts as a parent for the various drop-down menus, which in
1548	turn, may have labels, separator lines, menuItems and subMenus.
1549
1550	The menuItems are the useful bits: you can use them to mimic keyboard
1551	input or even to send text or escape sequences back to rxvt.
1552
1553	The menuBar syntax is intended to provide a simple yet robust method of
1554	constructing and manipulating menus and navigating through the
1555	menuBars.
1556
1557	The first step is to use the tag B<< [menu:I<name>] >> which creates
1558	the menuBar called I<name> and allows access. You may now or menus,
1559	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1560	menuBar access as B<readonly> to prevent accidental corruption of the
1561	menus. To re-access the current menuBar for alterations, use the tag
1562	B<[menu]>, make the alterations and then use B<[done]>
1563
1564	X<menuBarCommands>
1565
1566	=head2 Commands
1567
1568	=over 4
1569
1570	=item B<< [menu:+I<name>] >>
1571
1572	access the named menuBar for creation or alteration. If a new menuBar
1573	is created, it is called I<name> (max of 15 chars) and the current
1574	menuBar is pushed onto the stack
1575
1576	=item B<[menu]>
1577
1578	access the current menuBar for alteration
1579
1580	=item B<< [title:+I<string>] >>
1581
1582	set the current menuBar's title to I<string>, which may contain the
1583	following format specifiers:
1584
1585	B<%n> rxvt name (as per the B<-name> command-line option)
1586	B<%v> rxvt version
1587	B<%%> literal B<%> character
1588
1589	=item B<[done]>
1590
1591	set menuBar access as B<readonly>.
1592	End-of-file tag for B<< [read:+I<file>] >> operations.
1593
1594	=item B<< [read:+I<file>] >>
1595
1596	read menu commands directly from I<file> (extension ".menu" will be
1597	appended if required.) Start reading at a line with B<[menu]> or B<<
1598	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1599
1600	Blank and comment lines (starting with B<#>) are ignored. Actually,
1601	since any invalid menu commands are also ignored, almost anything could
1602	be construed as a comment line, but this may be tightened up in the
1603	future ... so don't count on it!.
1604
1605	=item B<< [read:+I<file>;+I<name>] >>
1606
1607	The same as B<< [read:+I<file>] >>, but start reading at a line with
1608	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1609	B<[done]> is encountered.
1610
1611	=item B<[dump]>
1612
1613	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1614	later rereading.
1615
1616	=item B<[rm:name]>
1617
1618	remove the named menuBar
1619
1620	=item B<[rm] [rm:]>
1621
1622	remove the current menuBar
1623
1624	=item B<[rm] [rm:]>
1625
1626	remove all menuBars
1627
1628	=item B<[swap]>
1629
1630	swap the top two menuBars
1631
1632	=item B<[prev]>
1633
1634	access the previous menuBar
1635
1636	=item B<[next]>
1637
1638	access the next menuBar
1639
1640	=item B<[show]>
1641
1642	Enable display of the menuBar
1643
1644	=item B<[hide]>
1645
1646	Disable display of the menuBar
1647
1648	=item B<< [pixmap:+I<name>] >>
1649
1650	=item B<< [pixmap:+I<name>;I<scaling>] >>
1651
1652	(set the background pixmap globally
1653
1654	B<< A Future implementation I<may> make this local to the menubar >>)
1655
1656	=item B<< [:+I<command>:] >>
1657
1658	ignore the menu readonly status and issue a I<command> to or a menu or
1659	menuitem or change the ; a useful shortcut for setting the quick arrows
1660	from a menuBar.
1661
1662	=back
1663
1664	X<menuBarAdd>
1665
1666	=head2 Adding and accessing menus
1667
1668	The following commands may also be B<+> prefixed.
1669
1670	=over 4
1671
1672	=item B</+>
1673
1674	access menuBar top level
1675
1676	=item B<./+>
1677
1678	access current menu level
1679
1680	=item B<../+>
1681
1682	access parent menu (1 level up)
1683
1684	=item B<../../>
1685
1686	access parent menu (multiple levels up)
1687
1688	=item B<< I</path/>menu >>
1689
1690	add/access menu
1691
1692	=item B<< I</path/>menu/* >>
1693
1694	add/access menu and clear it if it exists
1695
1696	=item B<< I</path/>{-} >>
1697
1698	add separator
1699
1700	=item B<< I</path/>{item} >>
1701
1702	add B<item> as a label
1703
1704	=item B<< I</path/>{item} action >>
1705
1706	add/alter I<menuitem> with an associated I<action>
1707
1708	=item B<< I</path/>{item}{right-text} >>
1709
1710	add/alter I<menuitem> with B<right-text> as the right-justified text
1711	and as the associated I<action>
1712
1713	=item B<< I</path/>{item}{rtext} action >>
1714
1715	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1716	the right-justified text.
1717
1718	=back
1719
1720	=over 4
1721
1722	=item Special characters in I<action> must be backslash-escaped:
1723
1724	B<\a \b \E \e \n \r \t \octal>
1725
1726	=item or in control-character notation:
1727
1728	B<^@, ^A .. ^Z .. ^_, ^?>
1729
1730	=back
1731
1732	To send a string starting with a B<NUL> (B<^@>) character to the
1733	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1734	the first of which will be stripped off and the balance directed to the
1735	program. Otherwise if I<action> begins with B<NUL> followed by
1736	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1737	balance is sent back to rxvt.
1738
1739	As a convenience for the many Emacs-type editors, I<action> may start
1740	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1741	appended if missed from B<M-x> commands.
1742
1743	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1744	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1745
1746	=over 4
1747
1748	=item For example,
1749
1750	B<M-xapropos> is equivalent to B<\Exapropos\r>
1751
1752	=item and
1753
1754	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1755
1756	=back
1757
1758	The option B<< {I<right-rtext>} >> will be right-justified. In the
1759	absence of a specified action, this text will be used as the I<action>
1760	as well.
1761
1762	=over 4
1763
1764	=item For example,
1765
1766	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1767
1768	=back
1769
1770	The left label I<is> necessary, since it's used for matching, but
1771	implicitly hiding the left label (by using same name for both left and
1772	right labels), or explicitly hiding the left label (by preceeding it
1773	with a dot), makes it possible to have right-justified text only.
1774
1775	=over 4
1776
1777	=item For example,
1778
1779	B</File/{Open}{Open} Open-File-Action>
1780
1781	=item or hiding it
1782
1783	B</File/{.anylabel}{Open} Open-File-Action>
1784
1785	=back
1786
1787	X<menuBarRemove>
1788
1789	=head2 Removing menus
1790
1791	=over 4
1792
1793	=item B<< -/*+ >>
1794
1795	remove all menus from the menuBar, the same as B<[clear]>
1796
1797	=item B<< -+I</path>menu+ >>
1798
1799	remove menu
1800
1801	=item B<< -+I</path>{item}+ >>
1802
1803	remove item
1804
1805	=item B<< -+I</path>{-} >>
1806
1807	remove separator)
1808
1809	=item B<-/path/menu/*>
1810
1811	remove all items, separators and submenus from menu
1812
1813	=back
1814
1815	X<menuBarArrows>
1816
1817	=head2 Quick Arrows
1818
1819	The menus also provide a hook for I<quick arrows> to provide easier
1820	user access. If nothing has been explicitly set, the default is to
1821	emulate the curror keys. The syntax permits each arrow to be altered
1822	individually or all four at once without re-entering their common
1823	beginning/end text. For example, to explicitly associate cursor actions
1824	with the arrows, any of the following forms could be used:
1825
1826	=over 4
1827
1828	=item B<< <r>+I<Right> >>
1829
1830	=item B<< <l>+I<Left> >>
1831
1832	=item B<< <u>+I<Up> >>
1833
1834	=item B<< <d>+I<Down> >>
1835
1836	Define actions for the respective arrow buttons
1837
1838	=item B<< <b>+I<Begin> >>
1839
1840	=item B<< <e>+I<End> >>
1841
1842	Define common beginning/end parts for I<quick arrows> which used in
1843	conjunction with the above <r> <l> <u> <d> constructs
1844
1845	=back
1846
1847	=over 4
1848
1849	=item For example, define arrows individually,
1850
1851	<u>\E[A
1852
1853	<d>\E[B
1854
1855	<r>\E[C
1856
1857	<l>\E[D
1858
1859	=item or all at once
1860
1861	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
1862
1863	=item or more compactly (factoring out common parts)
1864
1865	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
1866
1867	=back
1868
1869	X<menuBarSummary>
1870
1871	=head2 Command Summary
1872
1873	A short summary of the most I<common> commands:
1874
1875	=over 4
1876
1877	=item [menu:name]
1878
1879	use an existing named menuBar or start a new one
1880
1881	=item [menu]
1882
1883	use the current menuBar
1884
1885	=item [title:string]
1886
1887	set menuBar title
1888
1889	=item [done]
1890
1891	set menu access to readonly and, if reading from a file, signal EOF
1892
1893	=item [done:name]
1894
1895	if reading from a file using [read:file;name] signal EOF
1896
1897	=item [rm:name]
1898
1899	remove named menuBar(s)
1900
1901	=item [rm] [rm:]
1902
1903	remove current menuBar
1904
1905	=item [rm] [rm:]
1906
1907	remove all menuBar(s)
1908
1909	=item [swap]
1910
1911	swap top two menuBars
1912
1913	=item [prev]
1914
1915	access the previous menuBar
1916
1917	=item [next]
1918
1919	access the next menuBar
1920
1921	=item [show]
1922
1923	map menuBar
1924
1925	=item [hide]
1926
1927	unmap menuBar
1928
1929	=item [pixmap;file]
1930
1931	=item [pixmap;file;scaling]
1932
1933	set a background pixmap
1934
1935	=item [read:file]
1936
1937	=item [read:file;name]
1938
1939	read in a menu from a file
1940
1941	=item [dump]
1942
1943	dump out all menuBars to /tmp/rxvt-PID
1944
1945	=item /
1946
1947	access menuBar top level
1948
1949	=item ./
1950
1951	=item ../
1952
1953	=item ../../
1954
1955	access current or parent menu level
1956
1957	=item /path/menu
1958
1959	add/access menu
1960
1961	=item /path/{-}
1962
1963	add separator
1964
1965	=item /path/{item}{rtext} action
1966
1967	add/alter menu item
1968
1969	=item -/*
1970
1971	remove all menus from the menuBar
1972
1973	=item -/path/menu
1974
1975	remove menu items, separators and submenus from menu
1976
1977	=item -/path/menu
1978
1979	remove menu
1980
1981	=item -/path/{item}
1982
1983	remove item
1984
1985	=item -/path/{-}
1986
1987	remove separator
1988
1989	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
1990
1991	menu quick arrows
1992
1993	=back
1994	X<XPM>
1995
1996	=head1 XPM
1997
1998	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	2037	For the BACKGROUND IMAGE XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> the value
1999	of B<< C<Pt> >> can be the name of the background pixmap followed by a	2038	of B<< C<Pt> >> can be the name of the background image file followed by a
2000	sequence of scaling/positioning commands separated by semi-colons. The	2039	sequence of scaling/positioning commands separated by semi-colons. The
2001	scaling/positioning commands are as follows:	2040	scaling/positioning commands are as follows:
2002		2041
2003	=over 4	2042	=over 4
2004		2043
…		…
2042		2081
2043	For example:	2082	For example:
2044		2083
2045	=over 4	2084	=over 4
2046		2085
2047	=item B<\E]20;funky\a>	2086	=item B<\E]20;funky.jpg\a>
2048		2087
2049	load B<funky.xpm> as a tiled image	2088	load B<funky.jpg> as a tiled image
2050		2089
2051	=item B<\E]20;mona;100\a>	2090	=item B<\E]20;mona.jpg;100\a>
2052		2091
2053	load B<mona.xpm> with a scaling of 100%	2092	load B<mona.jpg> with a scaling of 100%
2054		2093
2055	=item B<\E]20;;200;?\a>	2094	=item B<\E]20;;200;?\a>
2056		2095
2057	rescale the current pixmap to 200% and display the image geometry in	2096	rescale the current pixmap to 200% and display the image geometry in
2058	the title	2097	the title
2059		2098
2060	=back	2099	=back
		2100
2061	X<Mouse>	2101	X<Mouse>
2062		2102
2063	=head1 Mouse Reporting	2103	=head1 Mouse Reporting
2064		2104
2065	=over 4	2105	=over 4
…		…
2097	=begin table	2137	=begin table
2098		2138
2099	4 Shift	2139	4 Shift
2100	8 Meta	2140	8 Meta
2101	16 Control	2141	16 Control
2102	32 Double Click I<(Rxvt extension)>	2142	32 Double Click I<(rxvt extension)>
2103		2143
2104	=end table	2144	=end table
2105		2145
2106	Col = B<< C<< <x> - SPACE >> >>	2146	Col = B<< C<< <x> - SPACE >> >>
2107		2147
2108	Row = B<< C<< <y> - SPACE >> >>	2148	Row = B<< C<< <y> - SPACE >> >>
2109		2149
2110	=back	2150	=back
		2151
		2152	=head1 Key Codes
		2153
2111	X<KeyCodes>	2154	X<KeyCodes>
2112
2113	=head1 Key Codes
2114		2155
2115	Note: B<Shift> + B<F1>-B<F10> generates B<F11>-B<F20>	2156	Note: B<Shift> + B<F1>-B<F10> generates B<F11>-B<F20>
2116		2157
2117	For the keypad, use B<Shift> to temporarily override Application-Keypad	2158	For the keypad, use B<Shift> to temporarily override Application-Keypad
2118	setting use B<Num_Lock> to toggle Application-Keypad setting if	2159	setting use B<Num_Lock> to toggle Application-Keypad setting if
2119	B<Num_Lock> is off, toggle Application-Keypad setting. Also note that	2160	B<Num_Lock> is off, toggle Application-Keypad setting. Also note that
2120	values of B<Home>, B<End>, B<Delete> may have been compiled differently on	2161	values of B<BackSpace>, B<Delete> may have been compiled differently on
2121	your system.	2162	your system.
2122		2163
2123	=begin table	2164	=begin table
2124		2165
2125	B<Normal> B<Shift> B<Control> B<Ctrl+Shift>	2166	B<Normal> B<Shift> B<Control> B<Ctrl+Shift>
…		…
2184	=end table	2225	=end table
2185		2226
2186	=head1 CONFIGURE OPTIONS	2227	=head1 CONFIGURE OPTIONS
2187		2228
2188	General hint: if you get compile errors, then likely your configuration	2229	General hint: if you get compile errors, then likely your configuration
2189	hasn't been tested well. Either try with --enable-everything or use the	2230	hasn't been tested well. Either try with C<--enable-everything> or use
2190	./reconf script as a base for experiments. ./reconf is used by myself,	2231	the default configuration (i.e. no C<--enable-xxx> or C<--disable-xxx>
2191	so it should generally be a working config. Of course, you should always	2232	switches). Of course, you should always report when a combination doesn't
2192	report when a combination doesn't work, so it can be fixed. Marc Lehmann	2233	work, so it can be fixed. Marc Lehmann <rxvt@schmorp.de>.
2193	<rxvt@schmorp.de>.	2234
		2235	All
2194		2236
2195	=over 4	2237	=over 4
2196		2238
2197	=item --enable-everything	2239	=item --enable-everything
2198		2240
2199	Add support for all non-multichoice options listed in "./configure	2241	Add (or remove) support for all non-multichoice options listed
2200	--help". Note that unlike other enable options this is order dependant.	2242	in C<./configure --help>, except for C<--enable-assert> and
		2243	C<--enable-256-color>.
		2244
2201	You can specify this and then disable options which this enables by	2245	You can specify this and then disable options you do not like by
2202	I<following> this with the appropriate commands.	2246	I<following> this with the appropriate C<--disable-...> arguments,
		2247	or you can start with a minimal configuration by specifying
		2248	C<--disable-everything> and than adding just the C<--enable-...> arguments
		2249	you want.
2203		2250
2204	=item --enable-xft	2251	=item --enable-xft (default: enabled)
2205		2252
2206	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2253	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2207	slower and require lots of memory, but as long as you don't use them, you	2254	slower and require lots of memory, but as long as you don't use them, you
2208	don't pay for them.	2255	don't pay for them.
2209		2256
2210	=item --enable-font-styles	2257	=item --enable-font-styles (default: on)
2211		2258
2212	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2259	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2213	styles. The fonts can be set manually or automatically.	2260	styles. The fonts can be set manually or automatically.
2214		2261
2215	=item --with-codesets=NAME,...	2262	=item --with-codesets=NAME,... (default: all)
2216		2263
2217	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>	2264	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2218	are always compiled in, which includes most 8-bit character sets). These	2265	are always compiled in, which includes most 8-bit character sets). These
2219	codeset tables are used for driving X11 core fonts, they are not required	2266	codeset tables are used for driving X11 core fonts, they are not required
2220	for Xft fonts, although having them compiled in lets rxvt-unicode choose	2267	for Xft fonts, although having them compiled in lets rxvt-unicode choose
…		…
2224		2271
2225	=begin table	2272	=begin table
2226		2273
2227	all all available codeset groups	2274	all all available codeset groups
2228	zh common chinese encodings	2275	zh common chinese encodings
2229	zh_ext rarely used but very big chinese encodigs	2276	zh_ext rarely used but very big chinese encodings
2230	jp common japanese encodings	2277	jp common japanese encodings
2231	jp_ext rarely used but big japanese encodings	2278	jp_ext rarely used but big japanese encodings
2232	kr korean encodings	2279	kr korean encodings
2233		2280
2234	=end table	2281	=end table
2235		2282
2236	=item --enable-xim	2283	=item --enable-xim (default: on)
2237		2284
2238	Add support for XIM (X Input Method) protocol. This allows using	2285	Add support for XIM (X Input Method) protocol. This allows using
2239	alternative input methods (e.g. kinput2) and will also correctly	2286	alternative input methods (e.g. kinput2) and will also correctly
2240	set up the input for people using dead keys or compose keys.	2287	set up the input for people using dead keys or compose keys.
2241		2288
2242	=item --enable-unicode3	2289	=item --enable-unicode3 (default: off)
		2290
		2291	Recommended to stay off unless you really need non-BMP characters.
2243		2292
2244	Enable direct support for displaying unicode codepoints above	2293	Enable direct support for displaying unicode codepoints above
2245	65535 (the basic multilingual page). This increases storage	2294	65535 (the basic multilingual page). This increases storage
2246	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2295	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2247	support these extra characters, but Xft does.	2296	support these extra characters, but Xft does.
2248		2297
2249	Please note that rxvt-unicode can store unicode code points >65535	2298	Please note that rxvt-unicode can store unicode code points >65535
2250	even without this flag, but the number of such characters is	2299	even without this flag, but the number of such characters is
2251	limited to a view thousand (shared with combining characters,	2300	limited to a few thousand (shared with combining characters,
2252	see next switch), and right now rxvt-unicode cannot display them	2301	see next switch), and right now rxvt-unicode cannot display them
2253	(input/output and cut&paste still work, though).	2302	(input/output and cut&paste still work, though).
2254		2303
2255	=item --enable-combining	2304	=item --enable-combining (default: on)
2256		2305
2257	Enable automatic composition of combining characters into	2306	Enable automatic composition of combining characters into
2258	composite characters. This is required for proper viewing of text	2307	composite characters. This is required for proper viewing of text
2259	where accents are encoded as seperate unicode characters. This is	2308	where accents are encoded as separate unicode characters. This is
2260	done by using precomposited characters when available or creating	2309	done by using precomposited characters when available or creating
2261	new pseudo-characters when no precomposed form exists.	2310	new pseudo-characters when no precomposed form exists.
2262		2311
2263	Without --enable-unicode3, the number of additional precomposed characters	2312	Without --enable-unicode3, the number of additional precomposed
2264	is rather limited (2048, if this is full, rxvt-unicode will use the	2313	characters is somewhat limited (the 6400 private use characters will be
2265	private use area, extending the number of combinations to 8448). With
2266	--enable-unicode3, no practical limit exists.	2314	(ab-)used). With --enable-unicode3, no practical limit exists.
2267		2315
2268	This option will also enable storage (but not display) of characters	2316	This option will also enable storage (but not display) of characters
2269	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2317	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2270		2318
2271	The combining table also contains entries for arabic presentation forms,	2319	The combining table also contains entries for arabic presentation forms,
2272	but these are not currently used. Bug me if you want these to be used (and	2320	but these are not currently used. Bug me if you want these to be used (and
2273	tell me how these are to be used...).	2321	tell me how these are to be used...).
2274		2322
2275	=item --enable-fallback(=CLASS)	2323	=item --enable-fallback(=CLASS) (default: Rxvt)
2276		2324
2277	When reading resource settings, also read settings for class CLASS	2325	When reading resource settings, also read settings for class CLASS. To
2278	(default: Rxvt). To disable resource fallback use --disable-fallback.	2326	disable resource fallback use --disable-fallback.
2279		2327
2280	=item --with-res-name=NAME	2328	=item --with-res-name=NAME (default: urxvt)
2281		2329
2282	Use the given name (default: urxvt) as default application name when	2330	Use the given name as default application name when
2283	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2331	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2284		2332
2285	=item --with-res-class=CLASS	2333	=item --with-res-class=CLASS (default: URxvt)
2286		2334
2287	Use the given class (default: URxvt) as default application class	2335	Use the given class as default application class
2288	when reading resources. Specify --with-res-class=Rxvt to replace	2336	when reading resources. Specify --with-res-class=Rxvt to replace
2289	rxvt.	2337	rxvt.
2290		2338
2291	=item --enable-utmp	2339	=item --enable-utmp (default: on)
2292		2340
2293	Write user and tty to utmp file (used by programs like F<w>) at	2341	Write user and tty to utmp file (used by programs like F<w>) at
2294	start of rxvt execution and delete information when rxvt exits.	2342	start of rxvt execution and delete information when rxvt exits.
2295		2343
2296	=item --enable-wtmp	2344	=item --enable-wtmp (default: on)
2297		2345
2298	Write user and tty to wtmp file (used by programs like F<last>) at	2346	Write user and tty to wtmp file (used by programs like F<last>) at
2299	start of rxvt execution and write logout when rxvt exits. This	2347	start of rxvt execution and write logout when rxvt exits. This
2300	option requires --enable-utmp to also be specified.	2348	option requires --enable-utmp to also be specified.
2301		2349
2302	=item --enable-lastlog	2350	=item --enable-lastlog (default: on)
2303		2351
2304	Write user and tty to lastlog file (used by programs like	2352	Write user and tty to lastlog file (used by programs like
2305	F<lastlogin>) at start of rxvt execution. This option requires	2353	F<lastlogin>) at start of rxvt execution. This option requires
2306	--enable-utmp to also be specified.	2354	--enable-utmp to also be specified.
2307		2355
2308	=item --enable-xpm-background	2356	=item --enable-afterimage (default: on)
2309		2357
2310	Add support for XPM background pixmaps.	2358	Add support for libAfterImage to be used for background
		2359	images. It adds support for many file formats including JPG, PNG,
		2360	SVG, TIFF, GIF, XPM, BMP, ICO, XCF, TGA and AfterStep image XML
		2361	(L<http://www.afterstep.org/visualdoc.php?show=asimagexml>).
2311		2362
		2363	This option also adds the possibility, when transparency is enabled,
		2364	of blending an image over the root background and blurring the root
		2365	background.
		2366
		2367	Note that with this option enabled, @@RXVT_NAME@@'s memory footprint might
		2368	increase by a few megabytes even if no extra features are used (mostly due
		2369	to third-party libraries used by libAI). Memory footprint may somewhat be
		2370	lowered if libAfterImage is configured without support for SVG.
		2371
2312	=item --enable-transparency	2372	=item --enable-transparency (default: on)
2313		2373
2314	Add support for inheriting parent backgrounds thus giving a fake	2374	Add support for backgrounds, creating illusion of transparency in the term.
2315	transparency to the term.
2316		2375
2317	=item --enable-fading	2376	=item --enable-fading (default: on)
2318		2377
2319	Add support for fading the text when focus is lost.	2378	Add support for fading the text when focus is lost.
2320		2379
2321	=item --enable-tinting
2322
2323	Add support for tinting of transparent backgrounds.
2324
2325	=item --enable-menubar
2326
2327	Add support for our menu bar system (this interacts badly with
2328	dynamic locale switching currently).
2329
2330	=item --enable-rxvt-scroll	2380	=item --enable-rxvt-scroll (default: on)
2331		2381
2332	Add support for the original rxvt scrollbar.	2382	Add support for the original rxvt scrollbar.
2333		2383
2334	=item --enable-next-scroll	2384	=item --enable-next-scroll (default: on)
2335		2385
2336	Add support for a NeXT-like scrollbar.	2386	Add support for a NeXT-like scrollbar.
2337		2387
2338	=item --enable-xterm-scroll	2388	=item --enable-xterm-scroll (default: on)
2339		2389
2340	Add support for an Xterm-like scrollbar.	2390	Add support for an Xterm-like scrollbar.
2341		2391
2342	=item --enable-plain-scroll
2343
2344	Add support for a very unobtrusive, plain-looking scrollbar that
2345	is the favourite of the rxvt-unicode author, having used it for
2346	many years.
2347
2348	=item --enable-half-shadow
2349
2350	Make shadows on the scrollbar only half the normal width & height.
2351	only applicable to rxvt scrollbars.
2352
2353	=item --enable-ttygid
2354
2355	Change tty device setting to group "tty" - only use this if
2356	your system uses this type of security.
2357
2358	=item --disable-backspace-key	2392	=item --disable-backspace-key
2359		2393
2360	Disable any handling of the backspace key by us - let the X server	2394	Removes any handling of the backspace key by us - let the X server do it.
		2395
		2396	=item --disable-delete-key
		2397
		2398	Removes any handling of the delete key by us - let the X server
2361	do it.	2399	do it.
2362		2400
2363	=item --disable-delete-key
2364
2365	Disable any handling of the delete key by us - let the X server
2366	do it.
2367
2368	=item --disable-resources	2401	=item --disable-resources
2369		2402
2370	Remove all resources checking.	2403	Removes any support for resource checking.
2371
2372	=item --enable-xgetdefault
2373
2374	Make resources checking via XGetDefault() instead of our small
2375	version which only checks ~/.Xdefaults, or if that doesn't exist then
2376	~/.Xresources.
2377
2378	Please note that nowadays, things like XIM will automatically pull in and
2379	use the full X resource manager, so the overhead of using it might be very
2380	small, if nonexistant.
2381
2382	=item --enable-strings
2383
2384	Add support for our possibly faster memset() function and other
2385	various routines, overriding your system's versions which may
2386	have been hand-crafted in assembly or may require extra libraries
2387	to link in. (this breaks ANSI-C rules and has problems on many
2388	GNU/Linux systems).
2389		2404
2390	=item --disable-swapscreen	2405	=item --disable-swapscreen
2391		2406
2392	Remove support for swap screen.	2407	Remove support for secondary/swap screen.
2393		2408
2394	=item --enable-frills	2409	=item --enable-frills (default: on)
2395		2410
2396	Add support for many small features that are not essential but nice to	2411	Add support for many small features that are not essential but nice to
2397	have. Normally you want this, but for very small binaries you may want to	2412	have. Normally you want this, but for very small binaries you may want to
2398	disable this.	2413	disable this.
2399		2414
2400	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2415	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2401	in combination with other switches) is:	2416	in combination with other switches) is:
2402		2417
2403	MWM-hints	2418	MWM-hints
2404	EWMH-hints (pid, utf8 names) and protocols (ping)	2419	EWMH-hints (pid, utf8 names) and protocols (ping)
2405	seperate underline colour	2420	urgency hint
		2421	separate underline colour (-underlineColor)
2406	settable border widths and borderless switch	2422	settable border widths and borderless switch (-w, -b, -bl)
		2423	visual depth selection (-depth)
2407	settable extra linespacing	2424	settable extra linespacing (-lsp)
2408	iso-14755-2 and -3, and visual feedback	2425	iso-14755 5.1 (basic) support
		2426	tripleclickwords (-tcw)
		2427	settable insecure mode (-insecure)
		2428	keysym remapping support
		2429	cursor blinking and underline cursor (-bc, -uc)
		2430	XEmbed support (-embed)
		2431	user-pty (-pty-fd)
		2432	hold on exit (-hold)
		2433	compile in built-in block graphics
		2434	skip builtin block graphics (-sbg)
		2435	separate highlight colour (-highlightColor, -highlightTextColor)
		2436
		2437	It also enables some non-essential features otherwise disabled, such as:
		2438
		2439	some round-trip time optimisations
		2440	nearest colour allocation on pseudocolor screens
		2441	UTF8_STRING support for selection
		2442	sgr modes 90..97 and 100..107
2409	backindex and forwardindex escape sequence	2443	backindex and forwardindex escape sequences
		2444	view change/zero scrollback escape sequences
		2445	locale switching escape sequence
2410	window op and some xterm/OSC escape sequences	2446	window op and some xterm/OSC escape sequences
2411	tripleclickwords	2447	rectangular selections
2412	settable insecure mode	2448	trailing space removal for selections
2413	keysym remapping support	2449	verbose X error handling
2414	cursor blinking and underline cursor
2415	-embed and -pty-fd options
2416		2450
2417	=item --enable-iso14755	2451	=item --enable-iso14755 (default: on)
2418		2452
2419	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2453	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1)).
2420	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2454	Basic support (section 5.1) is enabled by C<--enable-frills>, while
2421	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with	2455	support for 5.2, 5.3 and 5.4 is enabled with this switch.
2422	this switch.
2423		2456
2424	=item --enable-keepscrolling	2457	=item --enable-keepscrolling (default: on)
2425		2458
2426	Add support for continual scrolling of the display when you hold	2459	Add support for continual scrolling of the display when you hold
2427	the mouse button down on a scrollbar arrow.	2460	the mouse button down on a scrollbar arrow.
2428		2461
		2462	=item --enable-selectionscrolling (default: on)
		2463
		2464	Add support for scrolling when the selection moves to the top or
		2465	bottom of the screen.
		2466
2429	=item --enable-mousewheel	2467	=item --enable-mousewheel (default: on)
2430		2468
2431	Add support for scrolling via mouse wheel or buttons 4 & 5.	2469	Add support for scrolling via mouse wheel or buttons 4 & 5.
2432		2470
2433	=item --enable-slipwheeling	2471	=item --enable-slipwheeling (default: on)
2434		2472
2435	Add support for continual scrolling (using the mouse wheel as an	2473	Add support for continual scrolling (using the mouse wheel as an
2436	accelerator) while the control key is held down. This option	2474	accelerator) while the control key is held down. This option
2437	requires --enable-mousewheel to also be specified.	2475	requires --enable-mousewheel to also be specified.
2438		2476
2439	=item --disable-new-selection
2440
2441	Remove support for mouse selection style like that of xterm.
2442
2443	=item --enable-dmalloc
2444
2445	Use Gray Watson's malloc - which is good for debugging See
2446	http://www.letters.com/dmalloc/ for details If you use either this or the
2447	next option, you may need to edit src/Makefile after compiling to point
2448	DINCLUDE and DLIB to the right places.
2449
2450	You can only use either this option and the following (should
2451	you use either) .
2452
2453	=item --enable-dlmalloc
2454
2455	Use Doug Lea's malloc - which is good for a production version
2456	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2457
2458	=item --enable-smart-resize	2477	=item --enable-smart-resize (default: off)
2459		2478
2460	Add smart growth/shrink behaviour when changing font size via from hot	2479	Add smart growth/shrink behaviour when resizing.
2461	keys. This should keep in a fixed position the rxvt corner which is	2480	This should keep the window corner which is closest to a corner of
2462	closest to a corner of the screen.	2481	the screen in a fixed position.
2463		2482
		2483	=item --enable-text-blink (default: on)
		2484
		2485	Add support for blinking text.
		2486
2464	=item --enable-pointer-blank	2487	=item --enable-pointer-blank (default: on)
2465		2488
2466	Add support to have the pointer disappear when typing or inactive.	2489	Add support to have the pointer disappear when typing or inactive.
2467		2490
2468	=item --with-name=NAME	2491	=item --enable-perl (default: on)
2469		2492
		2493	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
		2494	manpage for more info on this feature, or the files in F<src/perl/>
		2495	for the extensions that are installed by default.
		2496	The perl interpreter that is used can be specified via the C<PERL>
		2497	environment variable when running configure. Even when compiled in,
		2498	perl will I<not> be initialised when all extensions have been disabled
		2499	C<-pe "" --perl-ext-common "">, so it should be safe to enable from a
		2500	resource standpoint.
		2501
		2502	=item --enable-assert (default: off)
		2503
		2504	Enables the assertions in the code, normally disabled. This switch is only
		2505	useful when developing rxvt-unicode.
		2506
		2507	=item --enable-256-color (default: off)
		2508
		2509	Force use of so-called 256 colour mode, to work around buggy applications
		2510	that do not support termcap/terminfo, or simply improve support for
		2511	applications hardcoding the xterm 256 colour table.
		2512
		2513	This switch breaks termcap/terminfo compatibility to C<TERM=rxvt-unicode>,
		2514	and consequently sets C<TERM> to C<rxvt-unicode-256color> by default
		2515	(F<doc/etc/> contains termcap/terminfo definitions for both).
		2516
		2517	It also results in higher memory usage and can slow down @@RXVT_NAME@@
		2518	dramatically when more than six fonts are in use by a terminal instance.
		2519
		2520	=item --with-afterimage-config=DIR
		2521
		2522	Look for the libAfterImage config script in DIR.
		2523
		2524	=item --with-name=NAME (default: urxvt)
		2525
2470	Set the basename for the installed binaries (default: C<urxvt>, resulting	2526	Set the basename for the installed binaries, resulting
2471	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2527	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
2472	C<rxvt>.	2528	C<rxvt>.
2473		2529
2474	=item --with-term=NAME	2530	=item --with-term=NAME (default: rxvt-unicode)
2475		2531
2476	Change the environmental variable for the terminal to NAME (default	2532	Change the environmental variable for the terminal to NAME.
2477	C<rxvt-unicode>)
2478		2533
2479	=item --with-terminfo=PATH	2534	=item --with-terminfo=PATH
2480		2535
2481	Change the environmental variable for the path to the terminfo tree to	2536	Change the environmental variable for the path to the terminfo tree to
2482	PATH.	2537	PATH.
2483		2538
2484	=item --with-x	2539	=item --with-x
2485		2540
2486	Use the X Window System (pretty much default, eh?).	2541	Use the X Window System (pretty much default, eh?).
2487
2488	=item --with-xpm-includes=DIR
2489
2490	Look for the XPM includes in DIR.
2491
2492	=item --with-xpm-library=DIR
2493
2494	Look for the XPM library in DIR.
2495
2496	=item --with-xpm
2497
2498	Not needed - define via --enable-xpm-background.
2499		2542
2500	=back	2543	=back
2501		2544
2502	=head1 AUTHORS	2545	=head1 AUTHORS
2503		2546

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.56 by root, Wed Jul 13 01:01:41 2005 UTC vs. Revision 1.195 by sf-exg, Fri Sep 3 09:57:30 2010 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.56 by root, Wed Jul 13 01:01:41 2005 UTC vs.
Revision 1.195 by sf-exg, Fri Sep 3 09:57:30 2010 UTC