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

Diff Legend

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