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

Diff Legend

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