ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/rxvt-unicode/doc/rxvt.7.pod

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

Diff Legend

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