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.74 by root, Mon Jan 9 07:24:43 2006 UTC vs.
Revision 1.113 by root, Thu Feb 2 18:04:45 2006 UTC

…		…
16	=head1 DESCRIPTION	16	=head1 DESCRIPTION
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is	21	The newest version of this document is also available on the World Wide Web at
22	also available on the World Wide Web at
23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
24		23
25	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		25
27	=over 4
28		26
		27	=head2 Meta, Features & Commandline Issues
		28
		29	=head3 My question isn't answered here, can I ask a human?
		30
		31	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		32	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		33	interested in learning about new and exciting problems (but not FAQs :).
		34
		35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
		36
		37	Beginning with version 7.3, there is a perl extension that implements a
		38	simple tabbed terminal. It is installed by default, so any of these should
		39	give you tabs:
		40
		41	@@URXVT_NAME@@ -pe tabbed
		42
		43	URxvt.perl-ext-common: default,tabbed
		44
		45	It will also work fine with tabbing functionality of many window managers
		46	or similar tabbing programs, and its embedding-features allow it to be
		47	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		48	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		49	(murxvt) terminal as an example embedding application.
		50
		51	=head3 How do I know which rxvt-unicode version I'm using?
		52
		53	The version number is displayed with the usage (-h). Also the escape
		54	sequence C<ESC [ 8 n> sets the window title to the version number. When
		55	using the @@URXVT_NAME@@c client, the version displayed is that of the
		56	daemon.
		57
		58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
		59
		60	Rxvt-unicode tries to obey the rule of not charging you for something you
		61	don't use. One thing you should try is to configure out all settings that
		62	you don't need, for example, Xft support is a resource hog by design,
		63	when used. Compiling it out ensures that no Xft font will be loaded
		64	accidentally when rxvt-unicode tries to find a font for your characters.
		65
		66	Also, many people (me included) like large windows and even larger
		67	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		68	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		69	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		70	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		71	rxvt-unicode then uses 8 bytes per screen cell.
		72
		73	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
		74
		75	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
		76	display, create the listening socket and then fork.
		77
		78	=head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?
		79
		80	If you want to start @@URXVT_NAME@@d automatically whenever you run
		81	@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
		82
		83	#!/bin/sh
		84	@@URXVT_NAME@@c "$@"
		85	if [ $? -eq 2 ]; then
		86	@@URXVT_NAME@@d -q -o -f
		87	@@URXVT_NAME@@c "$@"
		88	fi
		89
		90	This tries to create a new terminal, and if fails with exit status 2,
		91	meaning it couldn't connect to the daemon, it will start the daemon and
		92	re-run the command. Subsequent invocations of the script will re-use the
		93	existing daemon.
		94
		95	=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
		96
		97	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
		98	so you can check and see if that is set. Note that several programs, JED,
		99	slrn, Midnight Commander automatically check this variable to decide
		100	whether or not to use color.
		101
		102	=head3 How do I set the correct, full IP address for the DISPLAY variable?
		103
		104	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		105	insecure mode then it is possible to use the following shell script
		106	snippets to correctly set the display. If your version of rxvt-unicode
		107	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		108	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		109	regular xterm.
		110
		111	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		112	snippets:
		113
		114	# Bourne/Korn/POSIX family of shells:
		115	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		116	if [ ${TERM:-foo} = xterm ]; then
		117	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		118	echo -n '^[Z'
		119	read term_id
		120	stty icanon echo
		121	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		122	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		123	read DISPLAY # set it in our local shell
		124	fi
		125	fi
		126
		127	=head3 How do I compile the manual pages on my own?
		128
		129	You need to have a recent version of perl installed as F</usr/bin/perl>,
		130	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		131	the doc subdirectory and enter C<make alldoc>.
		132
29	=item Isn't rxvt supposed to be small? Don't all those features bloat?	133	=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
30		134
31	I often get asked about this, and I think, no, they didn't cause extra	135	I often get asked about this, and I think, no, they didn't cause extra
32	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see	136	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
33	that the urxvt binary is larger (due to some encoding tables always being	137	that the urxvt binary is larger (due to some encoding tables always being
34	compiled in), but it actually uses less memory (RSS) after startup. Even	138	compiled in), but it actually uses less memory (RSS) after startup. Even
…		…
38		142
39	text data bss drs rss filename	143	text data bss drs rss filename
40	98398 1664 24 15695 1824 rxvt --disable-everything	144	98398 1664 24 15695 1824 rxvt --disable-everything
41	188985 9048 66616 18222 1788 urxvt --disable-everything	145	188985 9048 66616 18222 1788 urxvt --disable-everything
42		146
43	When you C<--enable-everything> (which _is_ unfair, as this involves xft	147	When you C<--enable-everything> (which I<is> unfair, as this involves xft
44	and full locale/XIM support which are quite bloaty inside libX11 and my	148	and full locale/XIM support which are quite bloaty inside libX11 and my
45	libc), the two diverge, but not unreasnobaly so.	149	libc), the two diverge, but not unreasnobaly so.
46		150
47	text data bss drs rss filename	151	text data bss drs rss filename
48	163431 2152 24 20123 2060 rxvt --enable-everything	152	163431 2152 24 20123 2060 rxvt --enable-everything
…		…
66	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
67	43180k in daemons that stay around after exit, plus half a minute of	171	43180k in daemons that stay around after exit, plus half a minute of
68	startup time, including the hundreds of warnings it spits out), it fares	172	startup time, including the hundreds of warnings it spits out), it fares
69	extremely well *g*.	173	extremely well *g*.
70		174
71	=item Why C++, isn't that unportable/bloated/uncool?	175	=head3 Why C++, isn't that unportable/bloated/uncool?
72		176
73	Is this a question? :) It comes up very often. The simple answer is: I had	177	Is this a question? :) It comes up very often. The simple answer is: I had
74	to write it, and C++ allowed me to write and maintain it in a fraction	178	to write it, and C++ allowed me to write and maintain it in a fraction
75	of the time and effort (which is a scarce resource for me). Put even	179	of the time and effort (which is a scarce resource for me). Put even
76	shorter: It simply wouldn't exist without C++.	180	shorter: It simply wouldn't exist without C++.
…		…
100	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
101		205
102	No large bloated libraries (of course, none were linked in statically),	206	No large bloated libraries (of course, none were linked in statically),
103	except maybe libX11 :)	207	except maybe libX11 :)
104		208
105	=item Does it support tabs, can I have a tabbed rxvt-unicode?
106		209
107	rxvt-unicode does not directly support tabs. It will work fine with	210	=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		211
114	=item How do I know which rxvt-unicode version I'm using?	212	=head3 I can't get transparency working, what am I doing wrong?
115		213
116	The version number is displayed with the usage (-h). Also the escape	214	First of all, transparency isn't officially supported in rxvt-unicode, so
117	sequence C<ESC [ 8 n> sets the window title to the version number. When	215	you are mostly on your own. Do not bug the author about it (but you may
118	using the @@RXVT_NAME@@c client, the version displayed is that of the	216	bug everybody else). Also, if you can't get it working consider it a rite
119	daemon.	217	of passage: ... and you failed.
120		218
121	=item I am using Debian GNU/Linux and have a problem...	219	Here are four ways to get transparency. B<Do> read the manpage and option
		220	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
122		221
123	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	222	1. Use inheritPixmap:
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		223
132	For other problems that also affect the Debian package, you can and	224	Esetroot wallpaper.jpg
133	probably should use the Debian BTS, too, because, after all, it's also a	225	@@URXVT_NAME@@ -ip -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		226
137	=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?	227	That works. If you think it doesn't, you lack transparency and tinting
		228	support, or you are unable to read.
138		229
139	You should build one binary with the default options. F<configure>	230	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
140	now enables most useful options, and the trend goes to making them	231	to use effects other than tinting and shading: Just shade/tint/whatever
141	runtime-switchable, too, so there is usually no drawback to enbaling them,	232	your picture with gimp or any other tool:
142	except higher disk and possibly memory usage. The perl interpreter should
143	be enabled, as important functionality (menus, selection, likely more in
144	the future) depends on it.
145		233
146	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	234	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
147	system-wide (except maybe with C<defaults>). This will result in useful	235	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
148	behaviour. If your distribution aims at low memory, add an empty
149	C<perl-ext-common> resource to the app-defaults file. This will keep the
150	perl interpreter disabled until the user enables it.
151		236
152	If you can/want build more binaries, I recommend building a minimal	237	That works. If you think it doesn't, you lack XPM and Perl support, or you
153	one with C<--disable-everything> (very useful) and a maximal one with	238	are unable to read.
154	C<--enable-everything> (less useful, it will be very big due to a lot of
155	encodings built-in that increase download times and are rarely used).
156		239
157	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	240	3. Use an ARGB visual:
158		241
159	Likely not. While I honestly try to make it secure, and am probably	242	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
160	not bad at it, I think it is simply unreasonable to expect all of
161	freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to all be
162	secure. Also, rxvt-unicode disables some options when it detects that it
163	runs setuid or setgid, which is not nice.
164		243
165	Elevated privileges are only required for utmp and pty operations on some	244	This requires XFT support, and the support of your X-server. If that
166	systems (for example, GNU/Linux doesn't need any extra privileges for	245	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
167	ptys, but some need it for utmp support). If rxvt-unicode doesn't support	246	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
168	the library/setuid helper that your OS needs I'll be happy to assist you	247	bugfixes and workarounds for Xft and Xlib to make it work, but that
169	in implementing support for it.	248	doesn't mean that your WM has the required kludges in place.
170		249
171	So, while setuid/setgid operation is supported and not a problem on your	250	4. Use xcompmgr and let it do the job:
172	typical single-user-no-other-logins unix desktop, always remember that
173	its an awful lot of code, most of which isn't checked for security issues
174	regularly.
175		251
		252	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		253	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		254
		255	Then click on a window you want to make transparent. Replace C<0xc0000000>
		256	by other values to change the degree of opacity. If it doesn't work and
		257	your server crashes, you got to keep the pieces.
		258
		259	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		260
		261	Most fonts were not designed for terminal use, which means that character
		262	size varies a lot. A font that is otherwise fine for terminal use might
		263	contain some characters that are simply too wide. Rxvt-unicode will avoid
		264	these characters. For characters that are just "a bit" too wide a special
		265	"careful" rendering mode is used that redraws adjacent characters.
		266
		267	All of this requires that fonts do not lie about character sizes,
		268	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		269	box, and rxvt-unicode has no way of detecting this (the correct way is to
		270	ask for the character bounding box, which unfortunately is wrong in these
		271	cases).
		272
		273	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		274	or the respective font. If you encounter this problem you might try using
		275	the C<-lsp> option to give the font more height. If that doesn't work, you
		276	might be forced to use a different font.
		277
		278	All of this is not a problem when using X11 core fonts, as their bounding
		279	box data is correct.
		280
		281	=head3 How can I keep rxvt-unicode from using reverse video so much?
		282
		283	First of all, make sure you are running with the right terminal settings
		284	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		285	make sure you have specified colours for italic and bold, as otherwise
		286	rxvt-unicode might use reverse video to simulate the effect:
		287
		288	URxvt.colorBD: white
		289	URxvt.colorIT: green
		290
		291	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		292
		293	For some unexplainable reason, some rare programs assume a very weird
		294	colour palette when confronted with a terminal with more than the standard
		295	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		296	these programs not to assume non-ISO colours without very good reasons.
		297
		298	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		299	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		300	fix colours but keep you from using other rxvt-unicode features.
		301
		302	=head3 Can I switch the fonts at runtime?
		303
		304	Yes, using an escape sequence. Try something like this, which has the same
		305	effect as using the C<-fn> switch, and takes effect immediately:
		306
		307	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		308
		309	This is useful if you e.g. work primarily with japanese (and prefer a
		310	japanese font), but you have to switch to chinese temporarily, where
		311	japanese fonts would only be in your way.
		312
		313	You can think of this as a kind of manual ISO-2022 switching.
		314
		315	=head3 Why do italic characters look as if clipped?
		316
		317	Many fonts have difficulties with italic characters and hinting. For
		318	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		319	Mono> completely fails in it's italic face. A workaround might be to
		320	enable freetype autohinting, i.e. like this:
		321
		322	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		323	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		324
		325	=head3 Can I speed up Xft rendering somehow?
		326
		327	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		328	it is simply slow. If you still want Xft fonts you might try to disable
		329	antialiasing (by appending C<:antialias=false>), which saves lots of
		330	memory and also speeds up rendering considerably.
		331
		332	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		333
		334	Rxvt-unicode will use whatever you specify as a font. If it needs to
		335	fall back to it's default font search list it will prefer X11 core
		336	fonts, because they are small and fast, and then use Xft fonts. It has
		337	antialiasing disabled for most of them, because the author thinks they
		338	look best that way.
		339
		340	If you want antialiasing, you have to specify the fonts manually.
		341
		342	=head3 What's with this bold/blink stuff?
		343
		344	If no bold colour is set via C<colorBD:>, bold will invert text using the
		345	standard foreground colour.
		346
		347	For the standard background colour, blinking will actually make the
		348	text blink when compiled with C<--enable-blinking>. with standard
		349	colours. Without C<--enable-blinking>, the blink attribute will be
		350	ignored.
		351
		352	On ANSI colours, bold/blink attributes are used to set high-intensity
		353	foreground/background colors.
		354
		355	color0-7 are the low-intensity colors.
		356
		357	color8-15 are the corresponding high-intensity colors.
		358
		359	=head3 I don't like the screen colors. How do I change them?
		360
		361	You can change the screen colors at run-time using F<~/.Xdefaults>
		362	resources (or as long-options).
		363
		364	Here are values that are supposed to resemble a VGA screen,
		365	including the murky brown that passes for low-intensity yellow:
		366
		367	URxvt.color0: #000000
		368	URxvt.color1: #A80000
		369	URxvt.color2: #00A800
		370	URxvt.color3: #A8A800
		371	URxvt.color4: #0000A8
		372	URxvt.color5: #A800A8
		373	URxvt.color6: #00A8A8
		374	URxvt.color7: #A8A8A8
		375
		376	URxvt.color8: #000054
		377	URxvt.color9: #FF0054
		378	URxvt.color10: #00FF54
		379	URxvt.color11: #FFFF54
		380	URxvt.color12: #0000FF
		381	URxvt.color13: #FF00FF
		382	URxvt.color14: #00FFFF
		383	URxvt.color15: #FFFFFF
		384
		385	And here is a more complete set of non-standard colors.
		386
		387	URxvt.cursorColor: #dc74d1
		388	URxvt.pointerColor: #dc74d1
		389	URxvt.background: #0e0e0e
		390	URxvt.foreground: #4ad5e1
		391	URxvt.color0: #000000
		392	URxvt.color8: #8b8f93
		393	URxvt.color1: #dc74d1
		394	URxvt.color9: #dc74d1
		395	URxvt.color2: #0eb8c7
		396	URxvt.color10: #0eb8c7
		397	URxvt.color3: #dfe37e
		398	URxvt.color11: #dfe37e
		399	URxvt.color5: #9e88f0
		400	URxvt.color13: #9e88f0
		401	URxvt.color6: #73f7ff
		402	URxvt.color14: #73f7ff
		403	URxvt.color7: #e1dddd
		404	URxvt.color15: #e1dddd
		405
		406	They have been described (not by me) as "pretty girly".
		407
		408	=head3 Why do some characters look so much different than others?
		409
		410	See next entry.
		411
		412	=head3 How does rxvt-unicode choose fonts?
		413
		414	Most fonts do not contain the full range of Unicode, which is
		415	fine. Chances are that the font you (or the admin/package maintainer of
		416	your system/os) have specified does not cover all the characters you want
		417	to display.
		418
		419	B<rxvt-unicode> makes a best-effort try at finding a replacement
		420	font. Often the result is fine, but sometimes the chosen font looks
		421	bad/ugly/wrong. Some fonts have totally strange characters that don't
		422	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		423	intelligence to detect that a specific glyph is wrong: it has to believe
		424	the font that the characters it claims to contain indeed look correct.
		425
		426	In that case, select a font of your taste and add it to the font list,
		427	e.g.:
		428
		429	@@URXVT_NAME@@ -fn basefont,font2,font3...
		430
		431	When rxvt-unicode sees a character, it will first look at the base
		432	font. If the base font does not contain the character, it will go to the
		433	next font, and so on. Specifying your own fonts will also speed up this
		434	search and use less resources within rxvt-unicode and the X-server.
		435
		436	The only limitation is that none of the fonts may be larger than the base
		437	font, as the base font defines the terminal character cell size, which
		438	must be the same due to the way terminals work.
		439
		440	=head3 Why do some chinese characters look so different than others?
		441
		442	This is because there is a difference between script and language --
		443	rxvt-unicode does not know which language the text that is output is,
		444	as it only knows the unicode character codes. If rxvt-unicode first
		445	sees a japanese/chinese character, it might choose a japanese font for
		446	display. Subsequent japanese characters will use that font. Now, many
		447	chinese characters aren't represented in japanese fonts, so when the first
		448	non-japanese character comes up, rxvt-unicode will look for a chinese font
		449	-- unfortunately at this point, it will still use the japanese font for
		450	chinese characters that are also in the japanese font.
		451
		452	The workaround is easy: just tag a chinese font at the end of your font
		453	list (see the previous question). The key is to view the font list as
		454	a preference list: If you expect more japanese, list a japanese font
		455	first. If you expect more chinese, put a chinese font first.
		456
		457	In the future it might be possible to switch language preferences at
		458	runtime (the internal data structure has no problem with using different
		459	fonts for the same character at the same time, but no interface for this
		460	has been designed yet).
		461
		462	Until then, you might get away with switching fonts at runtime (see L<Can
		463	I switch the fonts at runtime?> later in this document).
		464
		465	=head2 Keyboard, Mouse & User Interaction
		466
		467	=head3 The new selection selects pieces that are too big, how can I select single words?
		468
		469	If you want to select e.g. alphanumeric words, you can use the following
		470	setting:
		471
		472	URxvt.selection.pattern-0: ([[:word:]]+)
		473
		474	If you click more than twice, the selection will be extended
		475	more and more.
		476
		477	To get a selection that is very similar to the old code, try this pattern:
		478
		479	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		480
		481	Please also note that the I<LeftClick Shift-LeftClik> combination also
		482	selects words like the old code.
		483
		484	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		485
		486	You can disable the perl extension completely by setting the
		487	B<perl-ext-common> resource to the empty string, which also keeps
		488	rxvt-unicode from initialising perl, saving memory.
		489
		490	If you only want to disable specific features, you first have to
		491	identify which perl extension is responsible. For this, read the section
		492	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		493	example, to disable the B<selection-popup> and B<option-popup>, specify
		494	this B<perl-ext-common> resource:
		495
		496	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		497
		498	This will keep the default extensions, but disable the two popup
		499	extensions. Some extensions can also be configured, for example,
		500	scrollback search mode is triggered by B<M-s>. You can move it to any
		501	other combination either by setting the B<searchable-scrollback> resource:
		502
		503	URxvt.searchable-scrollback: CM-s
		504
		505	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		506
		507	See next entry.
		508
		509	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		510
		511	These are caused by the C<readline> perl extension. Under normal
		512	circumstances, it will move your cursor around when you click into the
		513	line that contains it. It tries hard not to do this at the wrong moment,
		514	but when running a program that doesn't parse cursor movements or in some
		515	cases during rlogin sessions, it fails to detect this properly.
		516
		517	You can permamently switch this feature off by disabling the C<readline>
		518	extension:
		519
		520	URxvt.perl-ext-common: default,-readline
		521
		522	=head3 My numerical keypad acts weird and generates differing output?
		523
		524	Some Debian GNUL/Linux users seem to have this problem, although no
		525	specific details were reported so far. It is possible that this is caused
		526	by the wrong C<TERM> setting, although the details of wether and how
		527	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		528	keymap. See the answer to the previous question, and please report if that
		529	helped.
		530
		531	=head3 My Compose (Multi_key) key is no longer working.
		532
		533	The most common causes for this are that either your locale is not set
		534	correctly, or you specified a B<preeditStyle> that is not supported by
		535	your input method. For example, if you specified B<OverTheSpot> and
		536	your input method (e.g. the default input method handling Compose keys)
		537	does not support this (for instance because it is not visual), then
		538	rxvt-unicode will continue without an input method.
		539
		540	In this case either do not specify a B<preeditStyle> or specify more than
		541	one pre-edit style, such as B<OverTheSpot,Root,None>.
		542
		543	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		544
		545	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		546	international keyboards) or simply use ISO 14755 support to your
		547	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		548	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		549	character and so on.
		550
		551	=head3 Mouse cut/paste suddenly no longer works.
		552
		553	Make sure that mouse reporting is actually turned off since killing
		554	some editors prematurely may leave the mouse in mouse report mode. I've
		555	heard that tcsh may use mouse reporting unless it otherwise specified. A
		556	quick check is to see if cut/paste works when the Alt or Shift keys are
		557	depressed.
		558
		559	=head3 What's with the strange Backspace/Delete key behaviour?
		560
		561	Assuming that the physical Backspace key corresponds to the
		562	BackSpace keysym (not likely for Linux ... see the following
		563	question) there are two standard values that can be used for
		564	Backspace: C<^H> and C<^?>.
		565
		566	Historically, either value is correct, but rxvt-unicode adopts the debian
		567	policy of using C<^?> when unsure, because it's the one only only correct
		568	choice :).
		569
		570	Rxvt-unicode tries to inherit the current stty settings and uses the value
		571	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		572	started from a terminal (say, from a menu or by remote shell), then the
		573	system value of `erase', which corresponds to CERASE in <termios.h>, will
		574	be used (which may not be the same as your stty setting).
		575
		576	For starting a new rxvt-unicode:
		577
		578	# use Backspace = ^H
		579	$ stty erase ^H
		580	$ @@URXVT_NAME@@
		581
		582	# use Backspace = ^?
		583	$ stty erase ^?
		584	$ @@URXVT_NAME@@
		585
		586	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		587
		588	For an existing rxvt-unicode:
		589
		590	# use Backspace = ^H
		591	$ stty erase ^H
		592	$ echo -n "^[[36h"
		593
		594	# use Backspace = ^?
		595	$ stty erase ^?
		596	$ echo -n "^[[36l"
		597
		598	This helps satisfy some of the Backspace discrepancies that occur, but
		599	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		600	properly reflects that.
		601
		602	The Delete key is a another casualty of the ill-defined Backspace problem.
		603	To avoid confusion between the Backspace and Delete keys, the Delete
		604	key has been assigned an escape sequence to match the vt100 for Execute
		605	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		606
		607	Some other Backspace problems:
		608
		609	some editors use termcap/terminfo,
		610	some editors (vim I'm told) expect Backspace = ^H,
		611	GNU Emacs (and Emacs-like editors) use ^H for help.
		612
		613	Perhaps someday this will all be resolved in a consistent manner.
		614
		615	=head3 I don't like the key-bindings. How do I change them?
		616
		617	There are some compile-time selections available via configure. Unless
		618	you have run "configure" with the C<--disable-resources> option you can
		619	use the `keysym' resource to alter the keystrings associated with keysyms.
		620
		621	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		622
		623	URxvt.keysym.Home: \033[1~
		624	URxvt.keysym.End: \033[4~
		625	URxvt.keysym.C-apostrophe: \033<C-'>
		626	URxvt.keysym.C-slash: \033<C-/>
		627	URxvt.keysym.C-semicolon: \033<C-;>
		628	URxvt.keysym.C-grave: \033<C-`>
		629	URxvt.keysym.C-comma: \033<C-,>
		630	URxvt.keysym.C-period: \033<C-.>
		631	URxvt.keysym.C-0x60: \033<C-`>
		632	URxvt.keysym.C-Tab: \033<C-Tab>
		633	URxvt.keysym.C-Return: \033<C-Return>
		634	URxvt.keysym.S-Return: \033<S-Return>
		635	URxvt.keysym.S-space: \033<S-Space>
		636	URxvt.keysym.M-Up: \033<M-Up>
		637	URxvt.keysym.M-Down: \033<M-Down>
		638	URxvt.keysym.M-Left: \033<M-Left>
		639	URxvt.keysym.M-Right: \033<M-Right>
		640	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		641	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		642	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		643
		644	See some more examples in the documentation for the B<keysym> resource.
		645
		646	=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
		647
		648	KP_Insert == Insert
		649	F22 == Print
		650	F27 == Home
		651	F29 == Prior
		652	F33 == End
		653	F35 == Next
		654
		655	Rather than have rxvt-unicode try to accommodate all the various possible
		656	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		657	required for your particular machine.
		658
		659
		660
		661	=head2 Terminal Configuration
		662
		663	=head3 Why doesn't rxvt-unicode read my resources?
		664
		665	Well, why, indeed? It does, in a way very similar to other X
		666	applications. Most importantly, this means that if you or your OS loads
		667	resources into the X display (the right way to do it), rxvt-unicode will
		668	ignore any resource files in your home directory. It will only read
		669	F<$HOME/.Xdefaults> when no resources are attached to the display.
		670
		671	If you have or use an F<$HOME/.Xresources> file, chances are that
		672	resources are loaded into your X-server. In this case, you have to
		673	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		674
		675	Also consider the form resources have to use:
		676
		677	URxvt.resource: value
		678
		679	If you want to use another form (there are lots of different ways of
		680	specifying resources), make sure you understand wether and why it
		681	works. If unsure, use the form above.
		682
176	=item When I log-in to another system it tells me about missing terminfo data?	683	=head3 When I log-in to another system it tells me about missing terminfo data?
177		684
178	The terminal description used by rxvt-unicode is not as widely available	685	The terminal description used by rxvt-unicode is not as widely available
179	as that for xterm, or even rxvt (for which the same problem often arises).	686	as that for xterm, or even rxvt (for which the same problem often arises).
180		687
181	The correct solution for this problem is to install the terminfo, this can	688	The correct solution for this problem is to install the terminfo, this can
…		…
197	resource to set it:	704	resource to set it:
198		705
199	URxvt.termName: rxvt	706	URxvt.termName: rxvt
200		707
201	If you don't plan to use B<rxvt> (quite common...) you could also replace	708	If you don't plan to use B<rxvt> (quite common...) you could also replace
202	the rxvt terminfo file with the rxvt-unicode one.	709	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
203		710
204	=item C<tic> outputs some error when compiling the terminfo entry.	711	=head3 C<tic> outputs some error when compiling the terminfo entry.
205		712
206	Most likely it's the empty definition for C<enacs=>. Just replace it by	713	Most likely it's the empty definition for C<enacs=>. Just replace it by
207	C<enacs=\E[0@> and try again.	714	C<enacs=\E[0@> and try again.
208		715
209	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	716	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
210		717
		718	See next entry.
		719
211	=item I need a termcap file entry.	720	=head3 I need a termcap file entry.
212		721
213	One reason you might want this is that some distributions or operating	722	One reason you might want this is that some distributions or operating
214	systems still compile some programs using the long-obsoleted termcap	723	systems still compile some programs using the long-obsoleted termcap
215	library (Fedora Core's bash is one example) and rely on a termcap entry	724	library (Fedora Core's bash is one example) and rely on a termcap entry
216	for C<rxvt-unicode>.	725	for C<rxvt-unicode>.
…		…
242	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	751	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
243	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	752	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
244	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	753	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
245	:vs=\E[?25h:	754	:vs=\E[?25h:
246		755
247	=item Why does C<ls> no longer have coloured output?	756	=head3 Why does C<ls> no longer have coloured output?
248		757
249	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	758	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
250	decide wether a terminal has colour, but uses it's own configuration	759	decide wether a terminal has colour, but uses it's own configuration
251	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	760	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
252	with most other terminals supporting colour). Either add:	761	with most other terminals supporting colour). Either add:
…		…
257		766
258	alias ls='ls --color=auto'	767	alias ls='ls --color=auto'
259		768
260	to your C<.profile> or C<.bashrc>.	769	to your C<.profile> or C<.bashrc>.
261		770
262	=item Why doesn't vim/emacs etc. use the 88 colour mode?	771	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
263		772
		773	See next entry.
		774
264	=item Why doesn't vim/emacs etc. make use of italic?	775	=head3 Why doesn't vim/emacs etc. make use of italic?
265		776
		777	See next entry.
		778
266	=item Why are the secondary screen-related options not working properly?	779	=head3 Why are the secondary screen-related options not working properly?
267		780
268	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	781	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
269	distributions (most notably Debian GNU/Linux) break rxvt-unicode	782	distributions (most notably Debian GNU/Linux) break rxvt-unicode
270	by setting C<TERM> to C<rxvt>, which doesn't have these extra	783	by setting C<TERM> to C<rxvt>, which doesn't have these extra
271	features. Unfortunately, some of these (most notably, again, Debian	784	features. Unfortunately, some of these (most notably, again, Debian
272	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	785	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
273	file, so you will need to install it on your own (See the question B<When	786	file, so you will need to install it on your own (See the question B<When
274	I log-in to another system it tells me about missing terminfo data?> on	787	I log-in to another system it tells me about missing terminfo data?> on
275	how to do this).	788	how to do this).
276		789
277	=item My numerical keypad acts weird and generates differing output?
278		790
279	Some Debian GNUL/Linux users seem to have this problem, although no	791	=head2 Encoding / Locale / Input Method Issues
280	specific details were reported so far. It is possible that this is caused
281	by the wrong C<TERM> setting, although the details of wether and how
282	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
283	keymap. See the answer to the previous question, and please report if that
284	helped.
285		792
286	=item Rxvt-unicode does not seem to understand the selected encoding?	793	=head3 Rxvt-unicode does not seem to understand the selected encoding?
287		794
		795	See next entry.
		796
288	=item Unicode does not seem to work?	797	=head3 Unicode does not seem to work?
289		798
290	If you encounter strange problems like typing an accented character but	799	If you encounter strange problems like typing an accented character but
291	getting two unrelated other characters or similar, or if program output is	800	getting two unrelated other characters or similar, or if program output is
292	subtly garbled, then you should check your locale settings.	801	subtly garbled, then you should check your locale settings.
293		802
…		…
313		822
314	If nothing works and you are sure that everything is set correctly then	823	If nothing works and you are sure that everything is set correctly then
315	you will need to remember a little known fact: Some programs just don't	824	you will need to remember a little known fact: Some programs just don't
316	support locales :(	825	support locales :(
317		826
318	=item Why do some characters look so much different than others?	827	=head3 How does rxvt-unicode determine the encoding to use?
319		828
320	=item How does rxvt-unicode choose fonts?	829	See next entry.
321		830
322	Most fonts do not contain the full range of Unicode, which is	831	=head3 Is there an option to switch encodings?
323	fine. Chances are that the font you (or the admin/package maintainer of
324	your system/os) have specified does not cover all the characters you want
325	to display.
326		832
327	B<rxvt-unicode> makes a best-effort try at finding a replacement	833	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
328	font. Often the result is fine, but sometimes the chosen font looks	834	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
329	bad/ugly/wrong. Some fonts have totally strange characters that don't	835	UTF-8 or any other encodings with respect to terminal I/O.
330	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
331	intelligence to detect that a specific glyph is wrong: it has to believe
332	the font that the characters it claims to contain indeed look correct.
333		836
334	In that case, select a font of your taste and add it to the font list,	837	The reasons is that there exists a perfectly fine mechanism for selecting
335	e.g.:	838	the encoding, doing I/O and (most important) communicating this to all
336		839	applications so everybody agrees on character properties such as width
337	@@RXVT_NAME@@ -fn basefont,font2,font3...	840	and code number. This mechanism is the I<locale>. Applications not using
338		841	that info will have problems (for example, C<xterm> gets the width of
339	When rxvt-unicode sees a character, it will first look at the base	842	characters wrong as it uses it's own, locale-independent table under all
340	font. If the base font does not contain the character, it will go to the
341	next font, and so on. Specifying your own fonts will also speed up this
342	search and use less resources within rxvt-unicode and the X-server.
343
344	The only limitation is that none of the fonts may be larger than the base
345	font, as the base font defines the terminal character cell size, which
346	must be the same due to the way terminals work.
347
348	=item Why do some chinese characters look so different than others?
349
350	This is because there is a difference between script and language --
351	rxvt-unicode does not know which language the text that is output is,
352	as it only knows the unicode character codes. If rxvt-unicode first
353	sees a japanese/chinese character, it might choose a japanese font for
354	display. Subsequent japanese characters will use that font. Now, many
355	chinese characters aren't represented in japanese fonts, so when the first
356	non-japanese character comes up, rxvt-unicode will look for a chinese font
357	-- unfortunately at this point, it will still use the japanese font for
358	chinese characters that are also in the japanese font.
359
360	The workaround is easy: just tag a chinese font at the end of your font
361	list (see the previous question). The key is to view the font list as
362	a preference list: If you expect more japanese, list a japanese font
363	first. If you expect more chinese, put a chinese font first.
364
365	In the future it might be possible to switch language preferences at
366	runtime (the internal data structure has no problem with using different
367	fonts for the same character at the same time, but no interface for this
368	has been designed yet).
369
370	Until then, you might get away with switching fonts at runtime (see L<Can
371	I switch the fonts at runtime?> later in this document).
372
373	=item Why does rxvt-unicode sometimes leave pixel droppings?
374
375	Most fonts were not designed for terminal use, which means that character
376	size varies a lot. A font that is otherwise fine for terminal use might
377	contain some characters that are simply too wide. Rxvt-unicode will avoid
378	these characters. For characters that are just "a bit" too wide a special
379	"careful" rendering mode is used that redraws adjacent characters.
380
381	All of this requires that fonts do not lie about character sizes,
382	however: Xft fonts often draw glyphs larger than their acclaimed bounding
383	box, and rxvt-unicode has no way of detecting this (the correct way is to
384	ask for the character bounding box, which unfortunately is wrong in these
385	cases).	843	locales).
386		844
387	It's not clear (to me at least), wether this is a bug in Xft, freetype,	845	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
388	or the respective font. If you encounter this problem you might try using	846	programs doing the same (that is, most) will automatically agree in the
389	the C<-lsp> option to give the font more height. If that doesn't work, you	847	interpretation of characters.
390	might be forced to use a different font.
391		848
392	All of this is not a problem when using X11 core fonts, as their bounding	849	Unfortunately, there is no system-independent way to select locales, nor
393	box data is correct.	850	is there a standard on how locale specifiers will look like.
394		851
		852	On most systems, the content of the C<LC_CTYPE> environment variable
		853	contains an arbitrary string which corresponds to an already-installed
		854	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		855	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		856	(i.e. C<de> or C<german>) are also common.
		857
		858	Rxvt-unicode ignores all other locale categories, and except for
		859	the encoding, ignores country or language-specific settings,
		860	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		861	rxvt-unicode.
		862
		863	If you want to use a specific encoding you have to make sure you start
		864	rxvt-unicode with the correct C<LC_CTYPE> category.
		865
		866	=head3 Can I switch locales at runtime?
		867
		868	Yes, using an escape sequence. Try something like this, which sets
		869	rxvt-unicode's idea of C<LC_CTYPE>.
		870
		871	printf '\e]701;%s\007' ja_JP.SJIS
		872
		873	See also the previous answer.
		874
		875	Sometimes this capability is rather handy when you want to work in
		876	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		877	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		878	first switches to a locale supported by xjdic and back later:
		879
		880	printf '\e]701;%s\007' ja_JP.SJIS
		881	xjdic -js
		882	printf '\e]701;%s\007' de_DE.UTF-8
		883
		884	You can also use xterm's C<luit> program, which usually works fine, except
		885	for some locales where character width differs between program- and
		886	rxvt-unicode-locales.
		887
		888	=head3 I have problems getting my input method working.
		889
		890	Try a search engine, as this is slightly different for every input method server.
		891
		892	Here is a checklist:
		893
		894	=over 4
		895
		896	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		897
		898	Try C<locale -a> or check the documentation for your OS.
		899
		900	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		901
		902	For example, B<kinput2> does not support UTF-8 locales, you should use
		903	C<ja_JP.EUC-JP> or equivalent.
		904
		905	=item - Make sure your XIM server is actually running.
		906
		907	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		908
		909	When you want to use e.g. B<kinput2>, it must be set to
		910	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input
		911	method servers are running with this command:
		912
		913	xprop -root XIM_SERVERS
		914
		915	=item
		916
		917	=back
		918
		919	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		920
		921	You can specify separate locales for the input method and the rest of the
		922	terminal, using the resource C<imlocale>:
		923
		924	URxvt.imlocale: ja_JP.EUC-JP
		925
		926	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		927	use your input method. Please note, however, that, depending on your Xlib
		928	version, you may not be able to input characters outside C<EUC-JP> in a
		929	normal way then, as your input method limits you.
		930
		931	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		932
		933	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		934	design. Applications can avoid some crashes at the expense of memory
		935	leaks, and Input Methods can avoid some crashes by careful ordering at
		936	exit time. B<kinput2> (and derived input methods) generally succeeds,
		937	while B<SCIM> (or similar input methods) fails. In the end, however,
		938	crashes cannot be completely avoided even if both sides cooperate.
		939
		940	So the only workaround is not to kill your Input Method Servers.
		941
		942
		943	=head2 Operating Systems / Package Maintaining
		944
		945	=head3 I am using Debian GNU/Linux and have a problem...
		946
		947	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		948	patches that considerably change the behaviour of rxvt-unicode (but
		949	unfortunately this notice has been removed). Before reporting a bug to
		950	the original rxvt-unicode author please download and install the genuine
		951	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		952	the problem. If you cannot, chances are that the problems are specific to
		953	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		954	Tracking System (use C<reportbug> to report the bug).
		955
		956	For other problems that also affect the Debian package, you can and
		957	probably should use the Debian BTS, too, because, after all, it's also a
		958	bug in the Debian version and it serves as a reminder for other users that
		959	might encounter the same issue.
		960
		961	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		962
		963	You should build one binary with the default options. F<configure>
		964	now enables most useful options, and the trend goes to making them
		965	runtime-switchable, too, so there is usually no drawback to enbaling them,
		966	except higher disk and possibly memory usage. The perl interpreter should
		967	be enabled, as important functionality (menus, selection, likely more in
		968	the future) depends on it.
		969
		970	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		971	system-wide (except maybe with C<defaults>). This will result in useful
		972	behaviour. If your distribution aims at low memory, add an empty
		973	C<perl-ext-common> resource to the app-defaults file. This will keep the
		974	perl interpreter disabled until the user enables it.
		975
		976	If you can/want build more binaries, I recommend building a minimal
		977	one with C<--disable-everything> (very useful) and a maximal one with
		978	C<--enable-everything> (less useful, it will be very big due to a lot of
		979	encodings built-in that increase download times and are rarely used).
		980
		981	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		982
		983	It should be, starting with release 7.1. You are encouraged to properly
		984	install urxvt with privileges necessary for your OS now.
		985
		986	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		987	into a helper process for privileged operations (pty handling on some
		988	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		989	immediately. This is much safer than most other terminals that keep
		990	privileges while running (but is more relevant to urxvt, as it contains
		991	things as perl interpreters, which might be "helpful" to attackers).
		992
		993	This forking is done as the very first within main(), which is very early
		994	and reduces possible bugs to initialisation code run before main(), or
		995	things like the dynamic loader of your system, which should result in very
		996	little risk.
		997
395	=item On Solaris 9, many line-drawing characters are too wide.	998	=head3 On Solaris 9, many line-drawing characters are too wide.
396		999
397	Seems to be a known bug, read	1000	Seems to be a known bug, read
398	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1001	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
399	following ugly workaround to get non-double-wide-characters working:	1002	following ugly workaround to get non-double-wide-characters working:
400		1003
401	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1004	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
402		1005
403	=item My Compose (Multi_key) key is no longer working.
404
405	The most common causes for this are that either your locale is not set
406	correctly, or you specified a B<preeditStyle> that is not supported by
407	your input method. For example, if you specified B<OverTheSpot> and
408	your input method (e.g. the default input method handling Compose keys)
409	does not support this (for instance because it is not visual), then
410	rxvt-unicode will continue without an input method.
411
412	In this case either do not specify a B<preeditStyle> or specify more than
413	one pre-edit style, such as B<OverTheSpot,Root,None>.
414
415	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
416
417	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
418	international keyboards) or simply use ISO 14755 support to your
419	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
420	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
421	character and so on.
422
423	=item How can I keep rxvt-unicode from using reverse video so much?
424
425	First of all, make sure you are running with the right terminal settings
426	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
427	make sure you have specified colours for italic and bold, as otherwise
428	rxvt-unicode might use reverse video to simulate the effect:
429
430	URxvt.colorBD: white
431	URxvt.colorIT: green
432
433	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
434
435	For some unexplainable reason, some rare programs assume a very weird
436	colour palette when confronted with a terminal with more than the standard
437	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
438	these programs not to assume non-ISO colours without very good reasons.
439
440	In the meantime, you can either edit your C<rxvt-unicode> terminfo
441	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
442	fix colours but keep you from using other rxvt-unicode features.
443
444	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	1006	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
445		1007
446	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1008	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
447	in your compile environment, or an implementation that implements it,	1009	in your compile environment, or an implementation that implements it,
448	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1010	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
449	B<wchar_t> is represented as unicode.	1011	B<wchar_t> is represented as unicode.
…		…
471		1033
472	The rxvt-unicode author insists that the right way to fix this is in the	1034	The rxvt-unicode author insists that the right way to fix this is in the
473	system libraries once and for all, instead of forcing every app to carry	1035	system libraries once and for all, instead of forcing every app to carry
474	complete replacements for them :)	1036	complete replacements for them :)
475		1037
476	=item I use Solaris 9 and it doesn't compile/work/etc.	1038	=head3 I use Solaris 9 and it doesn't compile/work/etc.
477		1039
478	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1040	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
479	problems with C<wcwidth> and a compile problem.	1041	problems with C<wcwidth> and a compile problem.
480		1042
481	=item How can I use rxvt-unicode under cygwin?	1043	=head3 How can I use rxvt-unicode under cygwin?
482		1044
483	rxvt-unicode should compile and run out of the box on cygwin, using	1045	rxvt-unicode should compile and run out of the box on cygwin, using
484	the X11 libraries that come with cygwin. libW11 emulation is no	1046	the X11 libraries that come with cygwin. libW11 emulation is no
485	longer supported (and makes no sense, either, as it only supported a	1047	longer supported (and makes no sense, either, as it only supported a
486	single font). I recommend starting the X-server in C<-multiwindow> or	1048	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
489		1051
490	At the time of this writing, cygwin didn't seem to support any multi-byte	1052	At the time of this writing, cygwin didn't seem to support any multi-byte
491	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1053	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
492	to 8-bit encodings.	1054	to 8-bit encodings.
493		1055
494	=item How does rxvt-unicode determine the encoding to use?
495
496	=item Is there an option to switch encodings?
497
498	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
499	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
500	UTF-8 or any other encodings with respect to terminal I/O.
501
502	The reasons is that there exists a perfectly fine mechanism for selecting
503	the encoding, doing I/O and (most important) communicating this to all
504	applications so everybody agrees on character properties such as width
505	and code number. This mechanism is the I<locale>. Applications not using
506	that info will have problems (for example, C<xterm> gets the width of
507	characters wrong as it uses it's own, locale-independent table under all
508	locales).
509
510	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
511	programs doing the same (that is, most) will automatically agree in the
512	interpretation of characters.
513
514	Unfortunately, there is no system-independent way to select locales, nor
515	is there a standard on how locale specifiers will look like.
516
517	On most systems, the content of the C<LC_CTYPE> environment variable
518	contains an arbitrary string which corresponds to an already-installed
519	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
520	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
521	(i.e. C<de> or C<german>) are also common.
522
523	Rxvt-unicode ignores all other locale categories, and except for
524	the encoding, ignores country or language-specific settings,
525	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
526	rxvt-unicode.
527
528	If you want to use a specific encoding you have to make sure you start
529	rxvt-unicode with the correct C<LC_CTYPE> category.
530
531	=item Can I switch locales at runtime?
532
533	Yes, using an escape sequence. Try something like this, which sets
534	rxvt-unicode's idea of C<LC_CTYPE>.
535
536	printf '\e]701;%s\007' ja_JP.SJIS
537
538	See also the previous answer.
539
540	Sometimes this capability is rather handy when you want to work in
541	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
542	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
543	first switches to a locale supported by xjdic and back later:
544
545	printf '\e]701;%s\007' ja_JP.SJIS
546	xjdic -js
547	printf '\e]701;%s\007' de_DE.UTF-8
548
549	You can also use xterm's C<luit> program, which usually works fine, except
550	for some locales where character width differs between program- and
551	rxvt-unicode-locales.
552
553	=item Can I switch the fonts at runtime?
554
555	Yes, using an escape sequence. Try something like this, which has the same
556	effect as using the C<-fn> switch, and takes effect immediately:
557
558	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
559
560	This is useful if you e.g. work primarily with japanese (and prefer a
561	japanese font), but you have to switch to chinese temporarily, where
562	japanese fonts would only be in your way.
563
564	You can think of this as a kind of manual ISO-2022 switching.
565
566	=item Why do italic characters look as if clipped?
567
568	Many fonts have difficulties with italic characters and hinting. For
569	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
570	Mono> completely fails in it's italic face. A workaround might be to
571	enable freetype autohinting, i.e. like this:
572
573	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
574	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
575
576	=item My input method wants <some encoding> but I want UTF-8, what can I do?
577
578	You can specify separate locales for the input method and the rest of the
579	terminal, using the resource C<imlocale>:
580
581	URxvt*imlocale: ja_JP.EUC-JP
582
583	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
584	use your input method. Please note, however, that you will not be able to
585	input characters outside C<EUC-JP> in a normal way then, as your input
586	method limits you.
587
588	=item Rxvt-unicode crashes when the X Input Method changes or exits.
589
590	Unfortunately, this is unavoidable, as the XIM protocol is racy by
591	design. Applications can avoid some crashes at the expense of memory
592	leaks, and Input Methods can avoid some crashes by careful ordering at
593	exit time. B<kinput2> (and derived input methods) generally succeeds,
594	while B<SCIM> (or similar input methods) fails. In the end, however,
595	crashes cannot be completely avoided even if both sides cooperate.
596
597	So the only workaround is not to kill your Input Method Servers.
598
599	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
600
601	Rxvt-unicode tries to obey the rule of not charging you for something you
602	don't use. One thing you should try is to configure out all settings that
603	you don't need, for example, Xft support is a resource hog by design,
604	when used. Compiling it out ensures that no Xft font will be loaded
605	accidentally when rxvt-unicode tries to find a font for your characters.
606
607	Also, many people (me included) like large windows and even larger
608	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
609	6 bytes per screen cell. For a 160x?? window this amounts to almost a
610	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
611	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
612	rxvt-unicode then uses 8 bytes per screen cell.
613
614	=item Can I speed up Xft rendering somehow?
615
616	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
617	it is simply slow. If you still want Xft fonts you might try to disable
618	antialiasing (by appending C<:antialias=false>), which saves lots of
619	memory and also speeds up rendering considerably.
620
621	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
622
623	Rxvt-unicode will use whatever you specify as a font. If it needs to
624	fall back to it's default font search list it will prefer X11 core
625	fonts, because they are small and fast, and then use Xft fonts. It has
626	antialiasing disabled for most of them, because the author thinks they
627	look best that way.
628
629	If you want antialiasing, you have to specify the fonts manually.
630
631	=item Mouse cut/paste suddenly no longer works.
632
633	Make sure that mouse reporting is actually turned off since killing
634	some editors prematurely may leave the mouse in mouse report mode. I've
635	heard that tcsh may use mouse reporting unless it otherwise specified. A
636	quick check is to see if cut/paste works when the Alt or Shift keys are
637	depressed. See @@RXVT_NAME@@(7)
638
639	=item What's with this bold/blink stuff?
640
641	If no bold colour is set via C<colorBD:>, bold will invert text using the
642	standard foreground colour.
643
644	For the standard background colour, blinking will actually make the
645	text blink when compiled with C<--enable-blinking>. with standard
646	colours. Without C<--enable-blinking>, the blink attribute will be
647	ignored.
648
649	On ANSI colours, bold/blink attributes are used to set high-intensity
650	foreground/background colors.
651
652	color0-7 are the low-intensity colors.
653
654	color8-15 are the corresponding high-intensity colors.
655
656	=item I don't like the screen colors. How do I change them?
657
658	You can change the screen colors at run-time using F<~/.Xdefaults>
659	resources (or as long-options).
660
661	Here are values that are supposed to resemble a VGA screen,
662	including the murky brown that passes for low-intensity yellow:
663
664	URxvt.color0: #000000
665	URxvt.color1: #A80000
666	URxvt.color2: #00A800
667	URxvt.color3: #A8A800
668	URxvt.color4: #0000A8
669	URxvt.color5: #A800A8
670	URxvt.color6: #00A8A8
671	URxvt.color7: #A8A8A8
672
673	URxvt.color8: #000054
674	URxvt.color9: #FF0054
675	URxvt.color10: #00FF54
676	URxvt.color11: #FFFF54
677	URxvt.color12: #0000FF
678	URxvt.color13: #FF00FF
679	URxvt.color14: #00FFFF
680	URxvt.color15: #FFFFFF
681
682	And here is a more complete set of non-standard colors described (not by
683	me) as "pretty girly".
684
685	URxvt.cursorColor: #dc74d1
686	URxvt.pointerColor: #dc74d1
687	URxvt.background: #0e0e0e
688	URxvt.foreground: #4ad5e1
689	URxvt.color0: #000000
690	URxvt.color8: #8b8f93
691	URxvt.color1: #dc74d1
692	URxvt.color9: #dc74d1
693	URxvt.color2: #0eb8c7
694	URxvt.color10: #0eb8c7
695	URxvt.color3: #dfe37e
696	URxvt.color11: #dfe37e
697	URxvt.color5: #9e88f0
698	URxvt.color13: #9e88f0
699	URxvt.color6: #73f7ff
700	URxvt.color14: #73f7ff
701	URxvt.color7: #e1dddd
702	URxvt.color15: #e1dddd
703
704	=item How can I start @@RXVT_NAME@@d in a race-free way?
705
706	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
707	display, create the listening socket and then fork.
708
709	=item What's with the strange Backspace/Delete key behaviour?
710
711	Assuming that the physical Backspace key corresponds to the
712	BackSpace keysym (not likely for Linux ... see the following
713	question) there are two standard values that can be used for
714	Backspace: C<^H> and C<^?>.
715
716	Historically, either value is correct, but rxvt-unicode adopts the debian
717	policy of using C<^?> when unsure, because it's the one only only correct
718	choice :).
719
720	Rxvt-unicode tries to inherit the current stty settings and uses the value
721	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
722	started from a terminal (say, from a menu or by remote shell), then the
723	system value of `erase', which corresponds to CERASE in <termios.h>, will
724	be used (which may not be the same as your stty setting).
725
726	For starting a new rxvt-unicode:
727
728	# use Backspace = ^H
729	$ stty erase ^H
730	$ @@RXVT_NAME@@
731
732	# use Backspace = ^?
733	$ stty erase ^?
734	$ @@RXVT_NAME@@
735
736	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
737
738	For an existing rxvt-unicode:
739
740	# use Backspace = ^H
741	$ stty erase ^H
742	$ echo -n "^[[36h"
743
744	# use Backspace = ^?
745	$ stty erase ^?
746	$ echo -n "^[[36l"
747
748	This helps satisfy some of the Backspace discrepancies that occur, but
749	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
750	properly reflects that.
751
752	The Delete key is a another casualty of the ill-defined Backspace problem.
753	To avoid confusion between the Backspace and Delete keys, the Delete
754	key has been assigned an escape sequence to match the vt100 for Execute
755	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
756
757	Some other Backspace problems:
758
759	some editors use termcap/terminfo,
760	some editors (vim I'm told) expect Backspace = ^H,
761	GNU Emacs (and Emacs-like editors) use ^H for help.
762
763	Perhaps someday this will all be resolved in a consistent manner.
764
765	=item I don't like the key-bindings. How do I change them?
766
767	There are some compile-time selections available via configure. Unless
768	you have run "configure" with the C<--disable-resources> option you can
769	use the `keysym' resource to alter the keystrings associated with keysyms.
770
771	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
772
773	URxvt.keysym.Home: \033[1~
774	URxvt.keysym.End: \033[4~
775	URxvt.keysym.C-apostrophe: \033<C-'>
776	URxvt.keysym.C-slash: \033<C-/>
777	URxvt.keysym.C-semicolon: \033<C-;>
778	URxvt.keysym.C-grave: \033<C-`>
779	URxvt.keysym.C-comma: \033<C-,>
780	URxvt.keysym.C-period: \033<C-.>
781	URxvt.keysym.C-0x60: \033<C-`>
782	URxvt.keysym.C-Tab: \033<C-Tab>
783	URxvt.keysym.C-Return: \033<C-Return>
784	URxvt.keysym.S-Return: \033<S-Return>
785	URxvt.keysym.S-space: \033<S-Space>
786	URxvt.keysym.M-Up: \033<M-Up>
787	URxvt.keysym.M-Down: \033<M-Down>
788	URxvt.keysym.M-Left: \033<M-Left>
789	URxvt.keysym.M-Right: \033<M-Right>
790	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
791	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
792	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
793
794	See some more examples in the documentation for the B<keysym> resource.
795
796	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
797	How do I make use of them? For example, the Sun Keyboard type 4
798	has the following mappings that rxvt-unicode doesn't recognize.
799
800	KP_Insert == Insert
801	F22 == Print
802	F27 == Home
803	F29 == Prior
804	F33 == End
805	F35 == Next
806
807	Rather than have rxvt-unicode try to accommodate all the various possible
808	keyboard mappings, it is better to use `xmodmap' to remap the keys as
809	required for your particular machine.
810
811	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
812	I need this to decide about setting colors etc.
813
814	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
815	check and see if that is set. Note that several programs, JED, slrn,
816	Midnight Commander automatically check this variable to decide whether or
817	not to use color.
818
819	=item How do I set the correct, full IP address for the DISPLAY variable?
820
821	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
822	insecure mode then it is possible to use the following shell script
823	snippets to correctly set the display. If your version of rxvt-unicode
824	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
825	the COLORTERM variable can be used to distinguish rxvt-unicode from a
826	regular xterm.
827
828	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
829	snippets:
830
831	# Bourne/Korn/POSIX family of shells:
832	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
833	if [ ${TERM:-foo} = xterm ]; then
834	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
835	echo -n '^[Z'
836	read term_id
837	stty icanon echo
838	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
839	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
840	read DISPLAY # set it in our local shell
841	fi
842	fi
843
844	=item How do I compile the manual pages for myself?
845
846	You need to have a recent version of perl installed as F</usr/bin/perl>,
847	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
848	the doc subdirectory and enter C<make alldoc>.
849
850	=item My question isn't answered here, can I ask a human?
851
852	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
853	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
854	interested in learning about new and exciting problems (but not FAQs :).
855
856	=back
857
858	=head1 RXVT TECHNICAL REFERENCE	1056	=head1 RXVT-UNICODE TECHNICAL REFERENCE
859
860	=head1 DESCRIPTION
861		1057
862	The rest of this document describes various technical aspects of	1058	The rest of this document describes various technical aspects of
863	B<rxvt-unicode>. First the description of supported command sequences,	1059	B<rxvt-unicode>. First the description of supported command sequences,
864	followed by menu and pixmap support and last by a description of all	1060	followed by pixmap support and last by a description of all features
865	features selectable at C<configure> time.	1061	selectable at C<configure> time.
866		1062
867	=head1 Definitions	1063	=head2 Definitions
868		1064
869	=over 4	1065	=over 4
870		1066
871	=item B<< C<c> >>	1067	=item B<< C<c> >>
872		1068
…		…
890		1086
891	A text parameter composed of printable characters.	1087	A text parameter composed of printable characters.
892		1088
893	=back	1089	=back
894		1090
895	=head1 Values	1091	=head2 Values
896		1092
897	=over 4	1093	=over 4
898		1094
899	=item B<< C<ENQ> >>	1095	=item B<< C<ENQ> >>
900		1096
…		…
943		1139
944	Space Character	1140	Space Character
945		1141
946	=back	1142	=back
947		1143
948	=head1 Escape Sequences	1144	=head2 Escape Sequences
949		1145
950	=over 4	1146	=over 4
951		1147
952	=item B<< C<ESC # 8> >>	1148	=item B<< C<ESC # 8> >>
953		1149
…		…
1051		1247
1052	=back	1248	=back
1053		1249
1054	X<CSI>	1250	X<CSI>
1055		1251
1056	=head1 CSI (Command Sequence Introducer) Sequences	1252	=head2 CSI (Command Sequence Introducer) Sequences
1057		1253
1058	=over 4	1254	=over 4
1059		1255
1060	=item B<< C<ESC [ Ps @> >>	1256	=item B<< C<ESC [ Ps @> >>
1061		1257
…		…
1331		1527
1332	=back	1528	=back
1333		1529
1334	X<PrivateModes>	1530	X<PrivateModes>
1335		1531
1336	=head1 DEC Private Modes	1532	=head2 DEC Private Modes
1337		1533
1338	=over 4	1534	=over 4
1339		1535
1340	=item B<< C<ESC [ ? Pm h> >>	1536	=item B<< C<ESC [ ? Pm h> >>
1341		1537
…		…
1438	B<< C<h> >> Send Mouse X & Y on button press.	1634	B<< C<h> >> Send Mouse X & Y on button press.
1439	B<< C<l> >> No mouse reporting.	1635	B<< C<l> >> No mouse reporting.
1440		1636
1441	=end table	1637	=end table
1442		1638
1443	=item B<< C<Ps = 10> >> (B<rxvt>)
1444
1445	=begin table
1446
1447	B<< C<h> >> menuBar visible
1448	B<< C<l> >> menuBar invisible
1449
1450	=end table
1451
1452	=item B<< C<Ps = 25> >>	1639	=item B<< C<Ps = 25> >>
1453		1640
1454	=begin table	1641	=begin table
1455		1642
1456	B<< C<h> >> Visible cursor {cnorm/cvvis}	1643	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
1614		1801
1615	=back	1802	=back
1616		1803
1617	X<XTerm>	1804	X<XTerm>
1618		1805
1619	=head1 XTerm Operating System Commands	1806	=head2 XTerm Operating System Commands
1620		1807
1621	=over 4	1808	=over 4
1622		1809
1623	=item B<< C<ESC ] Ps;Pt ST> >>	1810	=item B<< C<ESC ] Ps;Pt ST> >>
1624		1811
…		…
1636	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	1823	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>
1637	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	1824	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>
1638	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	1825	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1639	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1826	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1640	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1827	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1641	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1828	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1642	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1829	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1643	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1830	B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM).
1644	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.	1831	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1645	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1832	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1646	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	1833	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1647	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> >>	1834	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> >>
1648	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1835	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1649	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).	1836	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).
1650	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).	1837	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>.
1651	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1838	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1652	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	1839	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
		1840	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		1841	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1653	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1842	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1654	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	1843	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1655	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	1844	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1656	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	1845	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1657	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).	1846	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
…		…
1660		1849
1661	=end table	1850	=end table
1662		1851
1663	=back	1852	=back
1664		1853
1665	X<menuBar>
1666
1667	=head1 menuBar
1668
1669	B<< The exact syntax used is I<almost> solidified. >>
1670	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1671	menuBar.
1672
1673	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1674	omitted: use B<./> to specify a menu relative to the current menu.
1675
1676	=head2 Overview of menuBar operation
1677
1678	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1679	of C<Pt> can be used for a variety of tasks:
1680
1681	At the top level is the current menuBar which is a member of a circular
1682	linked-list of other such menuBars.
1683
1684	The menuBar acts as a parent for the various drop-down menus, which in
1685	turn, may have labels, separator lines, menuItems and subMenus.
1686
1687	The menuItems are the useful bits: you can use them to mimic keyboard
1688	input or even to send text or escape sequences back to rxvt.
1689
1690	The menuBar syntax is intended to provide a simple yet robust method of
1691	constructing and manipulating menus and navigating through the
1692	menuBars.
1693
1694	The first step is to use the tag B<< [menu:I<name>] >> which creates
1695	the menuBar called I<name> and allows access. You may now or menus,
1696	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1697	menuBar access as B<readonly> to prevent accidental corruption of the
1698	menus. To re-access the current menuBar for alterations, use the tag
1699	B<[menu]>, make the alterations and then use B<[done]>
1700
1701	X<menuBarCommands>
1702
1703	=head2 Commands
1704
1705	=over 4
1706
1707	=item B<< [menu:+I<name>] >>
1708
1709	access the named menuBar for creation or alteration. If a new menuBar
1710	is created, it is called I<name> (max of 15 chars) and the current
1711	menuBar is pushed onto the stack
1712
1713	=item B<[menu]>
1714
1715	access the current menuBar for alteration
1716
1717	=item B<< [title:+I<string>] >>
1718
1719	set the current menuBar's title to I<string>, which may contain the
1720	following format specifiers:
1721
1722	B<%n> rxvt name (as per the B<-name> command-line option)
1723	B<%v> rxvt version
1724	B<%%> literal B<%> character
1725
1726	=item B<[done]>
1727
1728	set menuBar access as B<readonly>.
1729	End-of-file tag for B<< [read:+I<file>] >> operations.
1730
1731	=item B<< [read:+I<file>] >>
1732
1733	read menu commands directly from I<file> (extension ".menu" will be
1734	appended if required.) Start reading at a line with B<[menu]> or B<<
1735	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1736
1737	Blank and comment lines (starting with B<#>) are ignored. Actually,
1738	since any invalid menu commands are also ignored, almost anything could
1739	be construed as a comment line, but this may be tightened up in the
1740	future ... so don't count on it!.
1741
1742	=item B<< [read:+I<file>;+I<name>] >>
1743
1744	The same as B<< [read:+I<file>] >>, but start reading at a line with
1745	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1746	B<[done]> is encountered.
1747
1748	=item B<[dump]>
1749
1750	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1751	later rereading.
1752
1753	=item B<[rm:name]>
1754
1755	remove the named menuBar
1756
1757	=item B<[rm] [rm:]>
1758
1759	remove the current menuBar
1760
1761	=item B<[rm*] [rm:*]>
1762
1763	remove all menuBars
1764
1765	=item B<[swap]>
1766
1767	swap the top two menuBars
1768
1769	=item B<[prev]>
1770
1771	access the previous menuBar
1772
1773	=item B<[next]>
1774
1775	access the next menuBar
1776
1777	=item B<[show]>
1778
1779	Enable display of the menuBar
1780
1781	=item B<[hide]>
1782
1783	Disable display of the menuBar
1784
1785	=item B<< [pixmap:+I<name>] >>
1786
1787	=item B<< [pixmap:+I<name>;I<scaling>] >>
1788
1789	(set the background pixmap globally
1790
1791	B<< A Future implementation I<may> make this local to the menubar >>)
1792
1793	=item B<< [:+I<command>:] >>
1794
1795	ignore the menu readonly status and issue a I<command> to or a menu or
1796	menuitem or change the ; a useful shortcut for setting the quick arrows
1797	from a menuBar.
1798
1799	=back
1800
1801	X<menuBarAdd>
1802
1803	=head2 Adding and accessing menus
1804
1805	The following commands may also be B<+> prefixed.
1806
1807	=over 4
1808
1809	=item B</+>
1810
1811	access menuBar top level
1812
1813	=item B<./+>
1814
1815	access current menu level
1816
1817	=item B<../+>
1818
1819	access parent menu (1 level up)
1820
1821	=item B<../../>
1822
1823	access parent menu (multiple levels up)
1824
1825	=item B<< I</path/>menu >>
1826
1827	add/access menu
1828
1829	=item B<< I</path/>menu/* >>
1830
1831	add/access menu and clear it if it exists
1832
1833	=item B<< I</path/>{-} >>
1834
1835	add separator
1836
1837	=item B<< I</path/>{item} >>
1838
1839	add B<item> as a label
1840
1841	=item B<< I</path/>{item} action >>
1842
1843	add/alter I<menuitem> with an associated I<action>
1844
1845	=item B<< I</path/>{item}{right-text} >>
1846
1847	add/alter I<menuitem> with B<right-text> as the right-justified text
1848	and as the associated I<action>
1849
1850	=item B<< I</path/>{item}{rtext} action >>
1851
1852	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1853	the right-justified text.
1854
1855	=back
1856
1857	=over 4
1858
1859	=item Special characters in I<action> must be backslash-escaped:
1860
1861	B<\a \b \E \e \n \r \t \octal>
1862
1863	=item or in control-character notation:
1864
1865	B<^@, ^A .. ^Z .. ^_, ^?>
1866
1867	=back
1868
1869	To send a string starting with a B<NUL> (B<^@>) character to the
1870	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1871	the first of which will be stripped off and the balance directed to the
1872	program. Otherwise if I<action> begins with B<NUL> followed by
1873	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1874	balance is sent back to rxvt.
1875
1876	As a convenience for the many Emacs-type editors, I<action> may start
1877	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1878	appended if missed from B<M-x> commands.
1879
1880	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1881	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1882
1883	=over 4
1884
1885	=item For example,
1886
1887	B<M-xapropos> is equivalent to B<\Exapropos\r>
1888
1889	=item and
1890
1891	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1892
1893	=back
1894
1895	The option B<< {I<right-rtext>} >> will be right-justified. In the
1896	absence of a specified action, this text will be used as the I<action>
1897	as well.
1898
1899	=over 4
1900
1901	=item For example,
1902
1903	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1904
1905	=back
1906
1907	The left label I<is> necessary, since it's used for matching, but
1908	implicitly hiding the left label (by using same name for both left and
1909	right labels), or explicitly hiding the left label (by preceeding it
1910	with a dot), makes it possible to have right-justified text only.
1911
1912	=over 4
1913
1914	=item For example,
1915
1916	B</File/{Open}{Open} Open-File-Action>
1917
1918	=item or hiding it
1919
1920	B</File/{.anylabel}{Open} Open-File-Action>
1921
1922	=back
1923
1924	X<menuBarRemove>
1925
1926	=head2 Removing menus
1927
1928	=over 4
1929
1930	=item B<< -/*+ >>
1931
1932	remove all menus from the menuBar, the same as B<[clear]>
1933
1934	=item B<< -+I</path>menu+ >>
1935
1936	remove menu
1937
1938	=item B<< -+I</path>{item}+ >>
1939
1940	remove item
1941
1942	=item B<< -+I</path>{-} >>
1943
1944	remove separator)
1945
1946	=item B<-/path/menu/*>
1947
1948	remove all items, separators and submenus from menu
1949
1950	=back
1951
1952	X<menuBarArrows>
1953
1954	=head2 Quick Arrows
1955
1956	The menus also provide a hook for I<quick arrows> to provide easier
1957	user access. If nothing has been explicitly set, the default is to
1958	emulate the curror keys. The syntax permits each arrow to be altered
1959	individually or all four at once without re-entering their common
1960	beginning/end text. For example, to explicitly associate cursor actions
1961	with the arrows, any of the following forms could be used:
1962
1963	=over 4
1964
1965	=item B<< <r>+I<Right> >>
1966
1967	=item B<< <l>+I<Left> >>
1968
1969	=item B<< <u>+I<Up> >>
1970
1971	=item B<< <d>+I<Down> >>
1972
1973	Define actions for the respective arrow buttons
1974
1975	=item B<< <b>+I<Begin> >>
1976
1977	=item B<< <e>+I<End> >>
1978
1979	Define common beginning/end parts for I<quick arrows> which used in
1980	conjunction with the above <r> <l> <u> <d> constructs
1981
1982	=back
1983
1984	=over 4
1985
1986	=item For example, define arrows individually,
1987
1988	<u>\E[A
1989
1990	<d>\E[B
1991
1992	<r>\E[C
1993
1994	<l>\E[D
1995
1996	=item or all at once
1997
1998	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
1999
2000	=item or more compactly (factoring out common parts)
2001
2002	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
2003
2004	=back
2005
2006	X<menuBarSummary>
2007
2008	=head2 Command Summary
2009
2010	A short summary of the most I<common> commands:
2011
2012	=over 4
2013
2014	=item [menu:name]
2015
2016	use an existing named menuBar or start a new one
2017
2018	=item [menu]
2019
2020	use the current menuBar
2021
2022	=item [title:string]
2023
2024	set menuBar title
2025
2026	=item [done]
2027
2028	set menu access to readonly and, if reading from a file, signal EOF
2029
2030	=item [done:name]
2031
2032	if reading from a file using [read:file;name] signal EOF
2033
2034	=item [rm:name]
2035
2036	remove named menuBar(s)
2037
2038	=item [rm] [rm:]
2039
2040	remove current menuBar
2041
2042	=item [rm*] [rm:*]
2043
2044	remove all menuBar(s)
2045
2046	=item [swap]
2047
2048	swap top two menuBars
2049
2050	=item [prev]
2051
2052	access the previous menuBar
2053
2054	=item [next]
2055
2056	access the next menuBar
2057
2058	=item [show]
2059
2060	map menuBar
2061
2062	=item [hide]
2063
2064	unmap menuBar
2065
2066	=item [pixmap;file]
2067
2068	=item [pixmap;file;scaling]
2069
2070	set a background pixmap
2071
2072	=item [read:file]
2073
2074	=item [read:file;name]
2075
2076	read in a menu from a file
2077
2078	=item [dump]
2079
2080	dump out all menuBars to /tmp/rxvt-PID
2081
2082	=item /
2083
2084	access menuBar top level
2085
2086	=item ./
2087
2088	=item ../
2089
2090	=item ../../
2091
2092	access current or parent menu level
2093
2094	=item /path/menu
2095
2096	add/access menu
2097
2098	=item /path/{-}
2099
2100	add separator
2101
2102	=item /path/{item}{rtext} action
2103
2104	add/alter menu item
2105
2106	=item -/*
2107
2108	remove all menus from the menuBar
2109
2110	=item -/path/menu
2111
2112	remove menu items, separators and submenus from menu
2113
2114	=item -/path/menu
2115
2116	remove menu
2117
2118	=item -/path/{item}
2119
2120	remove item
2121
2122	=item -/path/{-}
2123
2124	remove separator
2125
2126	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
2127
2128	menu quick arrows
2129
2130	=back
2131	X<XPM>
2132
2133	=head1 XPM	1854	=head1 XPM
2134		1855
2135	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1856	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
2136	of B<< C<Pt> >> can be the name of the background pixmap followed by a	1857	of B<< C<Pt> >> can be the name of the background pixmap followed by a
2137	sequence of scaling/positioning commands separated by semi-colons. The	1858	sequence of scaling/positioning commands separated by semi-colons. The
…		…
2234	=begin table	1955	=begin table
2235		1956
2236	4 Shift	1957	4 Shift
2237	8 Meta	1958	8 Meta
2238	16 Control	1959	16 Control
2239	32 Double Click I<(Rxvt extension)>	1960	32 Double Click I<(rxvt extension)>
2240		1961
2241	=end table	1962	=end table
2242		1963
2243	Col = B<< C<< <x> - SPACE >> >>	1964	Col = B<< C<< <x> - SPACE >> >>
2244		1965
…		…
2382	alternative input methods (e.g. kinput2) and will also correctly	2103	alternative input methods (e.g. kinput2) and will also correctly
2383	set up the input for people using dead keys or compose keys.	2104	set up the input for people using dead keys or compose keys.
2384		2105
2385	=item --enable-unicode3 (default: off)	2106	=item --enable-unicode3 (default: off)
2386		2107
		2108	Recommended to stay off unless you really need non-BMP characters.
		2109
2387	Enable direct support for displaying unicode codepoints above	2110	Enable direct support for displaying unicode codepoints above
2388	65535 (the basic multilingual page). This increases storage	2111	65535 (the basic multilingual page). This increases storage
2389	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2112	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2390	support these extra characters, but Xft does.	2113	support these extra characters, but Xft does.
2391		2114
…		…
2401	composite characters. This is required for proper viewing of text	2124	composite characters. This is required for proper viewing of text
2402	where accents are encoded as seperate unicode characters. This is	2125	where accents are encoded as seperate unicode characters. This is
2403	done by using precomposited characters when available or creating	2126	done by using precomposited characters when available or creating
2404	new pseudo-characters when no precomposed form exists.	2127	new pseudo-characters when no precomposed form exists.
2405		2128
2406	Without --enable-unicode3, the number of additional precomposed characters	2129	Without --enable-unicode3, the number of additional precomposed
2407	is rather limited (2048, if this is full, rxvt-unicode will use the	2130	characters is somewhat limited (the 6400 private use characters will be
2408	private use area, extending the number of combinations to 8448). With
2409	--enable-unicode3, no practical limit exists.	2131	(ab-)used). With --enable-unicode3, no practical limit exists.
2410		2132
2411	This option will also enable storage (but not display) of characters	2133	This option will also enable storage (but not display) of characters
2412	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2134	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2413		2135
2414	The combining table also contains entries for arabic presentation forms,	2136	The combining table also contains entries for arabic presentation forms,
2415	but these are not currently used. Bug me if you want these to be used (and	2137	but these are not currently used. Bug me if you want these to be used (and
2416	tell me how these are to be used...).	2138	tell me how these are to be used...).
2417		2139
2418	=item --enable-fallback(=CLASS) (default: Rxvt)	2140	=item --enable-fallback(=CLASS) (default: Rxvt)
2419		2141
2420	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.	2142	When reading resource settings, also read settings for class CLASS. To
		2143	disable resource fallback use --disable-fallback.
2421		2144
2422	=item --with-res-name=NAME (default: urxvt)	2145	=item --with-res-name=NAME (default: urxvt)
2423		2146
2424	Use the given name as default application name when	2147	Use the given name as default application name when
2425	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2148	reading resources. Specify --with-res-name=rxvt to replace rxvt.
…		…
2462		2185
2463	=item --enable-tinting (default: on)	2186	=item --enable-tinting (default: on)
2464		2187
2465	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).	2188	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2466		2189
2467	=item --enable-menubar (default: off) [DEPRECATED]
2468
2469	Add support for our menu bar system (this interacts badly with dynamic
2470	locale switching currently). This option is DEPRECATED and will be removed
2471	in the future.
2472
2473	=item --enable-rxvt-scroll (default: on)	2190	=item --enable-rxvt-scroll (default: on)
2474		2191
2475	Add support for the original rxvt scrollbar.	2192	Add support for the original rxvt scrollbar.
2476		2193
2477	=item --enable-next-scroll (default: on)	2194	=item --enable-next-scroll (default: on)
…		…
2486		2203
2487	Add support for a very unobtrusive, plain-looking scrollbar that	2204	Add support for a very unobtrusive, plain-looking scrollbar that
2488	is the favourite of the rxvt-unicode author, having used it for	2205	is the favourite of the rxvt-unicode author, having used it for
2489	many years.	2206	many years.
2490		2207
2491	=item --enable-half-shadow (default: off)
2492
2493	Make shadows on the scrollbar only half the normal width & height.
2494	only applicable to rxvt scrollbars.
2495
2496	=item --enable-ttygid (default: off)	2208	=item --enable-ttygid (default: off)
2497		2209
2498	Change tty device setting to group "tty" - only use this if	2210	Change tty device setting to group "tty" - only use this if
2499	your system uses this type of security.	2211	your system uses this type of security.
2500		2212
…		…
2508	do it.	2220	do it.
2509		2221
2510	=item --disable-resources	2222	=item --disable-resources
2511		2223
2512	Removes any support for resource checking.	2224	Removes any support for resource checking.
2513
2514	=item --enable-xgetdefault
2515
2516	Make resources checking via XGetDefault() instead of our small
2517	version which only checks ~/.Xdefaults, or if that doesn't exist then
2518	~/.Xresources.
2519
2520	Please note that nowadays, things like XIM will automatically pull in and
2521	use the full X resource manager, so the overhead of using it might be very
2522	small, if nonexistant.
2523
2524	=item --enable-strings (default: off)
2525
2526	Add support for our possibly faster memset() function and other
2527	various routines, overriding your system's versions which may
2528	have been hand-crafted in assembly or may require extra libraries
2529	to link in. (this breaks ANSI-C rules and has problems on many
2530	GNU/Linux systems).
2531		2225
2532	=item --disable-swapscreen	2226	=item --disable-swapscreen
2533		2227
2534	Remove support for secondary/swap screen.	2228	Remove support for secondary/swap screen.
2535		2229
…		…
2544		2238
2545	MWM-hints	2239	MWM-hints
2546	EWMH-hints (pid, utf8 names) and protocols (ping)	2240	EWMH-hints (pid, utf8 names) and protocols (ping)
2547	seperate underline colour (-underlineColor)	2241	seperate underline colour (-underlineColor)
2548	settable border widths and borderless switch (-w, -b, -bl)	2242	settable border widths and borderless switch (-w, -b, -bl)
		2243	visual depth selection (-depth)
2549	settable extra linespacing /-lsp)	2244	settable extra linespacing /-lsp)
2550	iso-14755-2 and -3, and visual feedback	2245	iso-14755-2 and -3, and visual feedback
2551	backindex and forwardindex escape sequence
2552	window op and some xterm/OSC escape sequences
2553	tripleclickwords (-tcw)	2246	tripleclickwords (-tcw)
2554	settable insecure mode (-insecure)	2247	settable insecure mode (-insecure)
2555	keysym remapping support	2248	keysym remapping support
2556	cursor blinking and underline cursor (-cb, -uc)	2249	cursor blinking and underline cursor (-cb, -uc)
2557	XEmbed support (-embed)	2250	XEmbed support (-embed)
2558	user-pty (-pty-fd)	2251	user-pty (-pty-fd)
2559	hold on exit (-hold)	2252	hold on exit (-hold)
2560	skip builtin block graphics (-sbg)	2253	skip builtin block graphics (-sbg)
		2254
		2255	It also enabled some non-essential features otherwise disabled, such as:
		2256
		2257	some round-trip time optimisations
		2258	nearest color allocation on pseudocolor screens
		2259	UTF8_STRING supporr for selection
2561	sgr modes 90..97 and 100..107	2260	sgr modes 90..97 and 100..107
		2261	backindex and forwardindex escape sequences
		2262	view change/zero scorllback esacpe sequences
		2263	locale switching escape sequence
		2264	window op and some xterm/OSC escape sequences
		2265	rectangular selections
		2266	trailing space removal for selections
		2267	verbose X error handling
2562		2268
2563	=item --enable-iso14755 (default: on)	2269	=item --enable-iso14755 (default: on)
2564		2270
2565	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2271	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2566	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2272	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2587	Remove support for mouse selection style like that of xterm.	2293	Remove support for mouse selection style like that of xterm.
2588		2294
2589	=item --enable-dmalloc (default: off)	2295	=item --enable-dmalloc (default: off)
2590		2296
2591	Use Gray Watson's malloc - which is good for debugging See	2297	Use Gray Watson's malloc - which is good for debugging See
2592	http://www.letters.com/dmalloc/ for details If you use either this or the	2298	L<http://www.letters.com/dmalloc/> for details If you use either this or the
2593	next option, you may need to edit src/Makefile after compiling to point	2299	next option, you may need to edit src/Makefile after compiling to point
2594	DINCLUDE and DLIB to the right places.	2300	DINCLUDE and DLIB to the right places.
2595		2301
2596	You can only use either this option and the following (should	2302	You can only use either this option and the following (should
2597	you use either) .	2303	you use either) .
…		…
2609		2315
2610	=item --enable-pointer-blank (default: on)	2316	=item --enable-pointer-blank (default: on)
2611		2317
2612	Add support to have the pointer disappear when typing or inactive.	2318	Add support to have the pointer disappear when typing or inactive.
2613		2319
2614	=item --enable-perl (default: off)	2320	=item --enable-perl (default: on)
2615		2321
2616	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>	2322	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2617	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files	2323	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
2618	in F<src/perl-ext/> for the extensions that are installed by default. The	2324	in F<src/perl-ext/> for the extensions that are installed by default. The
2619	perl interpreter that is used can be specified via the C<PERL> environment	2325	perl interpreter that is used can be specified via the C<PERL> environment

Diff Legend

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