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

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

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.47 by root, Mon Feb 14 10:48:44 2005 UTC vs. Revision 1.164 by ayin, Sun Jan 20 14:12:39 2008 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.47 by root, Mon Feb 14 10:48:44 2005 UTC vs.
Revision 1.164 by ayin, Sun Jan 20 14:12:39 2008 UTC