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.69 by root, Wed Jan 4 00:10:29 2006 UTC vs.
Revision 1.162 by ayin, Sat Jan 19 15:00:49 2008 UTC

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

Diff Legend

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