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.5 by root, Thu Aug 12 22:29:28 2004 UTC vs.
Revision 1.87 by root, Tue Jan 17 16:22:41 2006 UTC

		1	=head1 NAME
		2
		3	RXVT REFERENCE - FAQ, command sequences and other background information
		4
		5	=head1 SYNOPSIS
		6
		7	# set a new font set
		8	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
		9
		10	# change the locale and tell rxvt-unicode about it
		11	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
		12
		13	# set window title
		14	printf '\33]2;%s\007' "new window title"
		15
		16	=head1 DESCRIPTION
		17
		18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
		19	all escape sequences, and other background information.
		20
		21	The newest version of this document is
		22	also available on the World Wide Web at
		23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
		24
		25	=head1 FREQUENTLY ASKED QUESTIONS
		26
		27	=over 4
		28
		29	=item The new selection selects pieces that are too big, how can I select
		30	single words?
		31
		32	Yes. For example, if you want to select alphanumeric words, you can use
		33	the following resource:
		34
		35	URxvt.selection.pattern-0: ([[:word:]]+)
		36
		37	If you click more than twice, the selection will be extended
		38	more and more.
		39
		40	To get a selection that is very similar to the old code, try this pattern:
		41
		42	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		43
		44	Please also note that the I<LeftClick Shift-LeftClik> combination also
		45	selects words like the old code.
		46
		47	=item I don't like the new selection/popups/hotkeys/perl, how do I
		48	change/disable it?
		49
		50	You can disable the perl extension completely by setting the
		51	B<perl-ext-common> resource to the empty string, which also keeps
		52	rxvt-unicode from initialising perl, saving memory.
		53
		54	If you only want to disable specific features, you first have to
		55	identify which perl extension is responsible. For this, read the section
		56	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For
		57	example, to disable the B<selection-popup> and B<option-popup>, specify
		58	this B<perl-ext-common> resource:
		59
		60	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		61
		62	This will keep the default extensions, but disable the two popup
		63	extensions. Some extensions can also be configured, for example,
		64	scrollback search mode is triggered by B<M-s>. You can move it to any
		65	other combination either by setting the B<searchable-scrollback> resource:
		66
		67	URxvt.searchable-scrollback: CM-s
		68
		69	=item Isn't rxvt supposed to be small? Don't all those features bloat?
		70
		71	I often get asked about this, and I think, no, they didn't cause extra
		72	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
		73	that the urxvt binary is larger (due to some encoding tables always being
		74	compiled in), but it actually uses less memory (RSS) after startup. Even
		75	with C<--disable-everything>, this comparison is a bit unfair, as many
		76	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		77	already in use in this mode.
		78
		79	text data bss drs rss filename
		80	98398 1664 24 15695 1824 rxvt --disable-everything
		81	188985 9048 66616 18222 1788 urxvt --disable-everything
		82
		83	When you C<--enable-everything> (which _is_ unfair, as this involves xft
		84	and full locale/XIM support which are quite bloaty inside libX11 and my
		85	libc), the two diverge, but not unreasnobaly so.
		86
		87	text data bss drs rss filename
		88	163431 2152 24 20123 2060 rxvt --enable-everything
		89	1035683 49680 66648 29096 3680 urxvt --enable-everything
		90
		91	The very large size of the text section is explained by the east-asian
		92	encoding tables, which, if unused, take up disk space but nothing else
		93	and can be compiled out unless you rely on X11 core fonts that use those
		94	encodings. The BSS size comes from the 64k emergency buffer that my c++
		95	compiler allocates (but of course doesn't use unless you are out of
		96	memory). Also, using an xft font instead of a core font immediately adds a
		97	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
		98	not used.
		99
		100	Of course, due to every character using two or four bytes instead of one,
		101	a large scrollback buffer will ultimately make rxvt-unicode use more
		102	memory.
		103
		104	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
		105	still fares rather well. And compared to some monsters like gnome-terminal
		106	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
		107	43180k in daemons that stay around after exit, plus half a minute of
		108	startup time, including the hundreds of warnings it spits out), it fares
		109	extremely well *g*.
		110
		111	=item Why C++, isn't that unportable/bloated/uncool?
		112
		113	Is this a question? :) It comes up very often. The simple answer is: I had
		114	to write it, and C++ allowed me to write and maintain it in a fraction
		115	of the time and effort (which is a scarce resource for me). Put even
		116	shorter: It simply wouldn't exist without C++.
		117
		118	My personal stance on this is that C++ is less portable than C, but in
		119	the case of rxvt-unicode this hardly matters, as its portability limits
		120	are defined by things like X11, pseudo terminals, locale support and unix
		121	domain sockets, which are all less portable than C++ itself.
		122
		123	Regarding the bloat, see the above question: It's easy to write programs
		124	in C that use gobs of memory, an certainly possible to write programs in
		125	C++ that don't. C++ also often comes with large libraries, but this is
		126	not necessarily the case with GCC. Here is what rxvt links against on my
		127	system with a minimal config:
		128
		129	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		130	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
		131	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
		132	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		133
		134	And here is rxvt-unicode:
		135
		136	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		137	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		138	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
		139	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
		140	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		141
		142	No large bloated libraries (of course, none were linked in statically),
		143	except maybe libX11 :)
		144
		145	=item Does it support tabs, can I have a tabbed rxvt-unicode?
		146
		147	rxvt-unicode does not directly support tabs. It will work fine with
		148	tabbing functionality of many window managers or similar tabbing programs,
		149	and its embedding-features allow it to be embedded into other programs,
		150	as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
		151	module, which features a tabbed urxvt (murxvt) terminal as an example
		152	embedding application.
		153
		154	=item How do I know which rxvt-unicode version I'm using?
		155
		156	The version number is displayed with the usage (-h). Also the escape
		157	sequence C<ESC [ 8 n> sets the window title to the version number. When
		158	using the @@RXVT_NAME@@c client, the version displayed is that of the
		159	daemon.
		160
		161	=item I am using Debian GNU/Linux and have a problem...
		162
		163	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		164	patches that considerably change the behaviour of rxvt-unicode. Before
		165	reporting a bug to the original rxvt-unicode author please download and
		166	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
		167	and try to reproduce the problem. If you cannot, chances are that the
		168	problems are specific to Debian GNU/Linux, in which case it should be
		169	reported via the Debian Bug Tracking System (use C<reportbug> to report
		170	the bug).
		171
		172	For other problems that also affect the Debian package, you can and
		173	probably should use the Debian BTS, too, because, after all, it's also a
		174	bug in the Debian version and it serves as a reminder for other users that
		175	might encounter the same issue.
		176
		177	=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		178
		179	You should build one binary with the default options. F<configure>
		180	now enables most useful options, and the trend goes to making them
		181	runtime-switchable, too, so there is usually no drawback to enbaling them,
		182	except higher disk and possibly memory usage. The perl interpreter should
		183	be enabled, as important functionality (menus, selection, likely more in
		184	the future) depends on it.
		185
		186	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		187	system-wide (except maybe with C<defaults>). This will result in useful
		188	behaviour. If your distribution aims at low memory, add an empty
		189	C<perl-ext-common> resource to the app-defaults file. This will keep the
		190	perl interpreter disabled until the user enables it.
		191
		192	If you can/want build more binaries, I recommend building a minimal
		193	one with C<--disable-everything> (very useful) and a maximal one with
		194	C<--enable-everything> (less useful, it will be very big due to a lot of
		195	encodings built-in that increase download times and are rarely used).
		196
		197	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		198
		199	It should be, starting with release 7.1. You are encouraged to properly
		200	install urxvt with privileges necessary for your OS now.
		201
		202	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		203	into a helper process for privileged operations (pty handling on some
		204	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		205	immediately. This is much safer than most other terminals that keep
		206	privileges while running (but is more relevant to urxvt, as it contains
		207	things as perl interpreters, which might be "helpful" to attackers).
		208
		209	This forking is done as the very first within main(), which is very early
		210	and reduces possible bugs to initialisation code run before main(), or
		211	things like the dynamic loader of your system, which should result in very
		212	little risk.
		213
		214	=item When I log-in to another system it tells me about missing terminfo data?
		215
		216	The terminal description used by rxvt-unicode is not as widely available
		217	as that for xterm, or even rxvt (for which the same problem often arises).
		218
		219	The correct solution for this problem is to install the terminfo, this can
		220	be done like this (with ncurses' infocmp):
		221
		222	REMOTE=remotesystem.domain
		223	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
		224
		225	... or by installing rxvt-unicode normally on the remote system,
		226
		227	If you cannot or do not want to do this, then you can simply set
		228	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
		229	problems arising, which includes wrong keymapping, less and different
		230	colours and some refresh errors in fullscreen applications. It's a nice
		231	quick-and-dirty workaround for rare cases, though.
		232
		233	If you always want to do this (and are fine with the consequences) you
		234	can either recompile rxvt-unicode with the desired TERM value or use a
		235	resource to set it:
		236
		237	URxvt.termName: rxvt
		238
		239	If you don't plan to use B<rxvt> (quite common...) you could also replace
		240	the rxvt terminfo file with the rxvt-unicode one.
		241
		242	=item C<tic> outputs some error when compiling the terminfo entry.
		243
		244	Most likely it's the empty definition for C<enacs=>. Just replace it by
		245	C<enacs=\E[0@> and try again.
		246
		247	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
		248
		249	=item I need a termcap file entry.
		250
		251	One reason you might want this is that some distributions or operating
		252	systems still compile some programs using the long-obsoleted termcap
		253	library (Fedora Core's bash is one example) and rely on a termcap entry
		254	for C<rxvt-unicode>.
		255
		256	You could use rxvt's termcap entry with resonable results in many cases.
		257	You can also create a termcap entry by using terminfo's infocmp program
		258	like this:
		259
		260	infocmp -C rxvt-unicode
		261
		262	Or you could use this termcap entry, generated by the command above:
		263
		264	rxvt-unicode|rxvt-unicode terminal (X Window System):\
		265	:am:bw:eo:km:mi:ms:xn:xo:\
		266	:co#80:it#8:li#24:lm#0:\
		267	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
		268	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
		269	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
		270	:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
		271	:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
		272	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
		273	:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
		274	:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
		275	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
		276	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
		277	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
		278	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
		279	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
		280	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
		281	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
		282	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
		283	:vs=\E[?25h:
		284
		285	=item Why does C<ls> no longer have coloured output?
		286
		287	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
		288	decide wether a terminal has colour, but uses it's own configuration
		289	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
		290	with most other terminals supporting colour). Either add:
		291
		292	TERM rxvt-unicode
		293
		294	to C</etc/DIR_COLORS> or simply add:
		295
		296	alias ls='ls --color=auto'
		297
		298	to your C<.profile> or C<.bashrc>.
		299
		300	=item Why doesn't vim/emacs etc. use the 88 colour mode?
		301
		302	=item Why doesn't vim/emacs etc. make use of italic?
		303
		304	=item Why are the secondary screen-related options not working properly?
		305
		306	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
		307	distributions (most notably Debian GNU/Linux) break rxvt-unicode
		308	by setting C<TERM> to C<rxvt>, which doesn't have these extra
		309	features. Unfortunately, some of these (most notably, again, Debian
		310	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
		311	file, so you will need to install it on your own (See the question B<When
		312	I log-in to another system it tells me about missing terminfo data?> on
		313	how to do this).
		314
		315	=item My numerical keypad acts weird and generates differing output?
		316
		317	Some Debian GNUL/Linux users seem to have this problem, although no
		318	specific details were reported so far. It is possible that this is caused
		319	by the wrong C<TERM> setting, although the details of wether and how
		320	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		321	keymap. See the answer to the previous question, and please report if that
		322	helped.
		323
		324	=item Rxvt-unicode does not seem to understand the selected encoding?
		325
		326	=item Unicode does not seem to work?
		327
		328	If you encounter strange problems like typing an accented character but
		329	getting two unrelated other characters or similar, or if program output is
		330	subtly garbled, then you should check your locale settings.
		331
		332	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
		333	programs. Often rxvt-unicode is started in the C<C> locale, while the
		334	login script running within the rxvt-unicode window changes the locale to
		335	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
		336
		337	The best thing is to fix your startup environment, as you will likely run
		338	into other problems. If nothing works you can try this in your .profile.
		339
		340	printf '\e]701;%s\007' "$LC_CTYPE"
		341
		342	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
		343	supported on your systems. Some systems have a C<locale> command which
		344	displays this (also, C<perl -e0> can be used to check locale settings, as
		345	it will complain loudly if it cannot set the locale). If it displays something
		346	like:
		347
		348	locale: Cannot set LC_CTYPE to default locale: ...
		349
		350	Then the locale you specified is not supported on your system.
		351
		352	If nothing works and you are sure that everything is set correctly then
		353	you will need to remember a little known fact: Some programs just don't
		354	support locales :(
		355
		356	=item Why do some characters look so much different than others?
		357
		358	=item How does rxvt-unicode choose fonts?
		359
		360	Most fonts do not contain the full range of Unicode, which is
		361	fine. Chances are that the font you (or the admin/package maintainer of
		362	your system/os) have specified does not cover all the characters you want
		363	to display.
		364
		365	B<rxvt-unicode> makes a best-effort try at finding a replacement
		366	font. Often the result is fine, but sometimes the chosen font looks
		367	bad/ugly/wrong. Some fonts have totally strange characters that don't
		368	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		369	intelligence to detect that a specific glyph is wrong: it has to believe
		370	the font that the characters it claims to contain indeed look correct.
		371
		372	In that case, select a font of your taste and add it to the font list,
		373	e.g.:
		374
		375	@@RXVT_NAME@@ -fn basefont,font2,font3...
		376
		377	When rxvt-unicode sees a character, it will first look at the base
		378	font. If the base font does not contain the character, it will go to the
		379	next font, and so on. Specifying your own fonts will also speed up this
		380	search and use less resources within rxvt-unicode and the X-server.
		381
		382	The only limitation is that none of the fonts may be larger than the base
		383	font, as the base font defines the terminal character cell size, which
		384	must be the same due to the way terminals work.
		385
		386	=item Why do some chinese characters look so different than others?
		387
		388	This is because there is a difference between script and language --
		389	rxvt-unicode does not know which language the text that is output is,
		390	as it only knows the unicode character codes. If rxvt-unicode first
		391	sees a japanese/chinese character, it might choose a japanese font for
		392	display. Subsequent japanese characters will use that font. Now, many
		393	chinese characters aren't represented in japanese fonts, so when the first
		394	non-japanese character comes up, rxvt-unicode will look for a chinese font
		395	-- unfortunately at this point, it will still use the japanese font for
		396	chinese characters that are also in the japanese font.
		397
		398	The workaround is easy: just tag a chinese font at the end of your font
		399	list (see the previous question). The key is to view the font list as
		400	a preference list: If you expect more japanese, list a japanese font
		401	first. If you expect more chinese, put a chinese font first.
		402
		403	In the future it might be possible to switch language preferences at
		404	runtime (the internal data structure has no problem with using different
		405	fonts for the same character at the same time, but no interface for this
		406	has been designed yet).
		407
		408	Until then, you might get away with switching fonts at runtime (see L<Can
		409	I switch the fonts at runtime?> later in this document).
		410
		411	=item Why does rxvt-unicode sometimes leave pixel droppings?
		412
		413	Most fonts were not designed for terminal use, which means that character
		414	size varies a lot. A font that is otherwise fine for terminal use might
		415	contain some characters that are simply too wide. Rxvt-unicode will avoid
		416	these characters. For characters that are just "a bit" too wide a special
		417	"careful" rendering mode is used that redraws adjacent characters.
		418
		419	All of this requires that fonts do not lie about character sizes,
		420	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		421	box, and rxvt-unicode has no way of detecting this (the correct way is to
		422	ask for the character bounding box, which unfortunately is wrong in these
		423	cases).
		424
		425	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		426	or the respective font. If you encounter this problem you might try using
		427	the C<-lsp> option to give the font more height. If that doesn't work, you
		428	might be forced to use a different font.
		429
		430	All of this is not a problem when using X11 core fonts, as their bounding
		431	box data is correct.
		432
		433	=item On Solaris 9, many line-drawing characters are too wide.
		434
		435	Seems to be a known bug, read
		436	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
		437	following ugly workaround to get non-double-wide-characters working:
		438
		439	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
		440
		441	=item My Compose (Multi_key) key is no longer working.
		442
		443	The most common causes for this are that either your locale is not set
		444	correctly, or you specified a B<preeditStyle> that is not supported by
		445	your input method. For example, if you specified B<OverTheSpot> and
		446	your input method (e.g. the default input method handling Compose keys)
		447	does not support this (for instance because it is not visual), then
		448	rxvt-unicode will continue without an input method.
		449
		450	In this case either do not specify a B<preeditStyle> or specify more than
		451	one pre-edit style, such as B<OverTheSpot,Root,None>.
		452
		453	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		454
		455	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		456	international keyboards) or simply use ISO 14755 support to your
		457	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		458	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		459	character and so on.
		460
		461	=item How can I keep rxvt-unicode from using reverse video so much?
		462
		463	First of all, make sure you are running with the right terminal settings
		464	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		465	make sure you have specified colours for italic and bold, as otherwise
		466	rxvt-unicode might use reverse video to simulate the effect:
		467
		468	URxvt.colorBD: white
		469	URxvt.colorIT: green
		470
		471	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
		472
		473	For some unexplainable reason, some rare programs assume a very weird
		474	colour palette when confronted with a terminal with more than the standard
		475	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		476	these programs not to assume non-ISO colours without very good reasons.
		477
		478	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		479	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		480	fix colours but keep you from using other rxvt-unicode features.
		481
		482	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
		483
		484	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
		485	in your compile environment, or an implementation that implements it,
		486	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
		487	B<wchar_t> is represented as unicode.
		488
		489	As you might have guessed, FreeBSD does neither define this symobl nor
		490	does it support it. Instead, it uses it's own internal representation of
		491	B<wchar_t>. This is, of course, completely fine with respect to standards.
		492
		493	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
		494	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
		495
		496	C<__STDC_ISO_10646__> is the only sane way to support multi-language
		497	apps in an OS, as using a locale-dependent (and non-standardized)
		498	representation of B<wchar_t> makes it impossible to convert between
		499	B<wchar_t> (as used by X11 and your applications) and any other encoding
		500	without implementing OS-specific-wrappers for each and every locale. There
		501	simply are no APIs to convert B<wchar_t> into anything except the current
		502	locale encoding.
		503
		504	Some applications (such as the formidable B<mlterm>) work around this
		505	by carrying their own replacement functions for character set handling
		506	with them, and either implementing OS-dependent hacks or doing multiple
		507	conversions (which is slow and unreliable in case the OS implements
		508	encodings slightly different than the terminal emulator).
		509
		510	The rxvt-unicode author insists that the right way to fix this is in the
		511	system libraries once and for all, instead of forcing every app to carry
		512	complete replacements for them :)
		513
		514	=item I use Solaris 9 and it doesn't compile/work/etc.
		515
		516	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
		517	problems with C<wcwidth> and a compile problem.
		518
		519	=item How can I use rxvt-unicode under cygwin?
		520
		521	rxvt-unicode should compile and run out of the box on cygwin, using
		522	the X11 libraries that come with cygwin. libW11 emulation is no
		523	longer supported (and makes no sense, either, as it only supported a
		524	single font). I recommend starting the X-server in C<-multiwindow> or
		525	C<-rootless> mode instead, which will result in similar look&feel as the
		526	old libW11 emulation.
		527
		528	At the time of this writing, cygwin didn't seem to support any multi-byte
		529	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		530	to 8-bit encodings.
		531
		532	=item How does rxvt-unicode determine the encoding to use?
		533
		534	=item Is there an option to switch encodings?
		535
		536	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		537	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
		538	UTF-8 or any other encodings with respect to terminal I/O.
		539
		540	The reasons is that there exists a perfectly fine mechanism for selecting
		541	the encoding, doing I/O and (most important) communicating this to all
		542	applications so everybody agrees on character properties such as width
		543	and code number. This mechanism is the I<locale>. Applications not using
		544	that info will have problems (for example, C<xterm> gets the width of
		545	characters wrong as it uses it's own, locale-independent table under all
		546	locales).
		547
		548	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
		549	programs doing the same (that is, most) will automatically agree in the
		550	interpretation of characters.
		551
		552	Unfortunately, there is no system-independent way to select locales, nor
		553	is there a standard on how locale specifiers will look like.
		554
		555	On most systems, the content of the C<LC_CTYPE> environment variable
		556	contains an arbitrary string which corresponds to an already-installed
		557	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		558	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		559	(i.e. C<de> or C<german>) are also common.
		560
		561	Rxvt-unicode ignores all other locale categories, and except for
		562	the encoding, ignores country or language-specific settings,
		563	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		564	rxvt-unicode.
		565
		566	If you want to use a specific encoding you have to make sure you start
		567	rxvt-unicode with the correct C<LC_CTYPE> category.
		568
		569	=item Can I switch locales at runtime?
		570
		571	Yes, using an escape sequence. Try something like this, which sets
		572	rxvt-unicode's idea of C<LC_CTYPE>.
		573
		574	printf '\e]701;%s\007' ja_JP.SJIS
		575
		576	See also the previous answer.
		577
		578	Sometimes this capability is rather handy when you want to work in
		579	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		580	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		581	first switches to a locale supported by xjdic and back later:
		582
		583	printf '\e]701;%s\007' ja_JP.SJIS
		584	xjdic -js
		585	printf '\e]701;%s\007' de_DE.UTF-8
		586
		587	You can also use xterm's C<luit> program, which usually works fine, except
		588	for some locales where character width differs between program- and
		589	rxvt-unicode-locales.
		590
		591	=item Can I switch the fonts at runtime?
		592
		593	Yes, using an escape sequence. Try something like this, which has the same
		594	effect as using the C<-fn> switch, and takes effect immediately:
		595
		596	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		597
		598	This is useful if you e.g. work primarily with japanese (and prefer a
		599	japanese font), but you have to switch to chinese temporarily, where
		600	japanese fonts would only be in your way.
		601
		602	You can think of this as a kind of manual ISO-2022 switching.
		603
		604	=item Why do italic characters look as if clipped?
		605
		606	Many fonts have difficulties with italic characters and hinting. For
		607	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		608	Mono> completely fails in it's italic face. A workaround might be to
		609	enable freetype autohinting, i.e. like this:
		610
		611	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		612	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		613
		614	=item My input method wants <some encoding> but I want UTF-8, what can I do?
		615
		616	You can specify separate locales for the input method and the rest of the
		617	terminal, using the resource C<imlocale>:
		618
		619	URxvt.imlocale: ja_JP.EUC-JP
		620
		621	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		622	use your input method. Please note, however, that you will not be able to
		623	input characters outside C<EUC-JP> in a normal way then, as your input
		624	method limits you.
		625
		626	=item Rxvt-unicode crashes when the X Input Method changes or exits.
		627
		628	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		629	design. Applications can avoid some crashes at the expense of memory
		630	leaks, and Input Methods can avoid some crashes by careful ordering at
		631	exit time. B<kinput2> (and derived input methods) generally succeeds,
		632	while B<SCIM> (or similar input methods) fails. In the end, however,
		633	crashes cannot be completely avoided even if both sides cooperate.
		634
		635	So the only workaround is not to kill your Input Method Servers.
		636
		637	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
		638
		639	Rxvt-unicode tries to obey the rule of not charging you for something you
		640	don't use. One thing you should try is to configure out all settings that
		641	you don't need, for example, Xft support is a resource hog by design,
		642	when used. Compiling it out ensures that no Xft font will be loaded
		643	accidentally when rxvt-unicode tries to find a font for your characters.
		644
		645	Also, many people (me included) like large windows and even larger
		646	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		647	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		648	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		649	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		650	rxvt-unicode then uses 8 bytes per screen cell.
		651
		652	=item Can I speed up Xft rendering somehow?
		653
		654	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		655	it is simply slow. If you still want Xft fonts you might try to disable
		656	antialiasing (by appending C<:antialias=false>), which saves lots of
		657	memory and also speeds up rendering considerably.
		658
		659	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		660
		661	Rxvt-unicode will use whatever you specify as a font. If it needs to
		662	fall back to it's default font search list it will prefer X11 core
		663	fonts, because they are small and fast, and then use Xft fonts. It has
		664	antialiasing disabled for most of them, because the author thinks they
		665	look best that way.
		666
		667	If you want antialiasing, you have to specify the fonts manually.
		668
		669	=item Mouse cut/paste suddenly no longer works.
		670
		671	Make sure that mouse reporting is actually turned off since killing
		672	some editors prematurely may leave the mouse in mouse report mode. I've
		673	heard that tcsh may use mouse reporting unless it otherwise specified. A
		674	quick check is to see if cut/paste works when the Alt or Shift keys are
		675	depressed.
		676
		677	=item What's with this bold/blink stuff?
		678
		679	If no bold colour is set via C<colorBD:>, bold will invert text using the
		680	standard foreground colour.
		681
		682	For the standard background colour, blinking will actually make the
		683	text blink when compiled with C<--enable-blinking>. with standard
		684	colours. Without C<--enable-blinking>, the blink attribute will be
		685	ignored.
		686
		687	On ANSI colours, bold/blink attributes are used to set high-intensity
		688	foreground/background colors.
		689
		690	color0-7 are the low-intensity colors.
		691
		692	color8-15 are the corresponding high-intensity colors.
		693
		694	=item I don't like the screen colors. How do I change them?
		695
		696	You can change the screen colors at run-time using F<~/.Xdefaults>
		697	resources (or as long-options).
		698
		699	Here are values that are supposed to resemble a VGA screen,
		700	including the murky brown that passes for low-intensity yellow:
		701
		702	URxvt.color0: #000000
		703	URxvt.color1: #A80000
		704	URxvt.color2: #00A800
		705	URxvt.color3: #A8A800
		706	URxvt.color4: #0000A8
		707	URxvt.color5: #A800A8
		708	URxvt.color6: #00A8A8
		709	URxvt.color7: #A8A8A8
		710
		711	URxvt.color8: #000054
		712	URxvt.color9: #FF0054
		713	URxvt.color10: #00FF54
		714	URxvt.color11: #FFFF54
		715	URxvt.color12: #0000FF
		716	URxvt.color13: #FF00FF
		717	URxvt.color14: #00FFFF
		718	URxvt.color15: #FFFFFF
		719
		720	And here is a more complete set of non-standard colors described (not by
		721	me) as "pretty girly".
		722
		723	URxvt.cursorColor: #dc74d1
		724	URxvt.pointerColor: #dc74d1
		725	URxvt.background: #0e0e0e
		726	URxvt.foreground: #4ad5e1
		727	URxvt.color0: #000000
		728	URxvt.color8: #8b8f93
		729	URxvt.color1: #dc74d1
		730	URxvt.color9: #dc74d1
		731	URxvt.color2: #0eb8c7
		732	URxvt.color10: #0eb8c7
		733	URxvt.color3: #dfe37e
		734	URxvt.color11: #dfe37e
		735	URxvt.color5: #9e88f0
		736	URxvt.color13: #9e88f0
		737	URxvt.color6: #73f7ff
		738	URxvt.color14: #73f7ff
		739	URxvt.color7: #e1dddd
		740	URxvt.color15: #e1dddd
		741
		742	=item How can I start @@RXVT_NAME@@d in a race-free way?
		743
		744	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
		745	display, create the listening socket and then fork.
		746
		747	=item What's with the strange Backspace/Delete key behaviour?
		748
		749	Assuming that the physical Backspace key corresponds to the
		750	BackSpace keysym (not likely for Linux ... see the following
		751	question) there are two standard values that can be used for
		752	Backspace: C<^H> and C<^?>.
		753
		754	Historically, either value is correct, but rxvt-unicode adopts the debian
		755	policy of using C<^?> when unsure, because it's the one only only correct
		756	choice :).
		757
		758	Rxvt-unicode tries to inherit the current stty settings and uses the value
		759	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		760	started from a terminal (say, from a menu or by remote shell), then the
		761	system value of `erase', which corresponds to CERASE in <termios.h>, will
		762	be used (which may not be the same as your stty setting).
		763
		764	For starting a new rxvt-unicode:
		765
		766	# use Backspace = ^H
		767	$ stty erase ^H
		768	$ @@RXVT_NAME@@
		769
		770	# use Backspace = ^?
		771	$ stty erase ^?
		772	$ @@RXVT_NAME@@
		773
		774	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		775
		776	For an existing rxvt-unicode:
		777
		778	# use Backspace = ^H
		779	$ stty erase ^H
		780	$ echo -n "^[[36h"
		781
		782	# use Backspace = ^?
		783	$ stty erase ^?
		784	$ echo -n "^[[36l"
		785
		786	This helps satisfy some of the Backspace discrepancies that occur, but
		787	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		788	properly reflects that.
		789
		790	The Delete key is a another casualty of the ill-defined Backspace problem.
		791	To avoid confusion between the Backspace and Delete keys, the Delete
		792	key has been assigned an escape sequence to match the vt100 for Execute
		793	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		794
		795	Some other Backspace problems:
		796
		797	some editors use termcap/terminfo,
		798	some editors (vim I'm told) expect Backspace = ^H,
		799	GNU Emacs (and Emacs-like editors) use ^H for help.
		800
		801	Perhaps someday this will all be resolved in a consistent manner.
		802
		803	=item I don't like the key-bindings. How do I change them?
		804
		805	There are some compile-time selections available via configure. Unless
		806	you have run "configure" with the C<--disable-resources> option you can
		807	use the `keysym' resource to alter the keystrings associated with keysyms.
		808
		809	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
		810
		811	URxvt.keysym.Home: \033[1~
		812	URxvt.keysym.End: \033[4~
		813	URxvt.keysym.C-apostrophe: \033<C-'>
		814	URxvt.keysym.C-slash: \033<C-/>
		815	URxvt.keysym.C-semicolon: \033<C-;>
		816	URxvt.keysym.C-grave: \033<C-`>
		817	URxvt.keysym.C-comma: \033<C-,>
		818	URxvt.keysym.C-period: \033<C-.>
		819	URxvt.keysym.C-0x60: \033<C-`>
		820	URxvt.keysym.C-Tab: \033<C-Tab>
		821	URxvt.keysym.C-Return: \033<C-Return>
		822	URxvt.keysym.S-Return: \033<S-Return>
		823	URxvt.keysym.S-space: \033<S-Space>
		824	URxvt.keysym.M-Up: \033<M-Up>
		825	URxvt.keysym.M-Down: \033<M-Down>
		826	URxvt.keysym.M-Left: \033<M-Left>
		827	URxvt.keysym.M-Right: \033<M-Right>
		828	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		829	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		830	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		831
		832	See some more examples in the documentation for the B<keysym> resource.
		833
		834	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
		835	How do I make use of them? For example, the Sun Keyboard type 4
		836	has the following mappings that rxvt-unicode doesn't recognize.
		837
		838	KP_Insert == Insert
		839	F22 == Print
		840	F27 == Home
		841	F29 == Prior
		842	F33 == End
		843	F35 == Next
		844
		845	Rather than have rxvt-unicode try to accommodate all the various possible
		846	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		847	required for your particular machine.
		848
		849	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
		850	I need this to decide about setting colors etc.
		851
		852	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
		853	check and see if that is set. Note that several programs, JED, slrn,
		854	Midnight Commander automatically check this variable to decide whether or
		855	not to use color.
		856
		857	=item How do I set the correct, full IP address for the DISPLAY variable?
		858
		859	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		860	insecure mode then it is possible to use the following shell script
		861	snippets to correctly set the display. If your version of rxvt-unicode
		862	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		863	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		864	regular xterm.
		865
		866	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		867	snippets:
		868
		869	# Bourne/Korn/POSIX family of shells:
		870	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		871	if [ ${TERM:-foo} = xterm ]; then
		872	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		873	echo -n '^[Z'
		874	read term_id
		875	stty icanon echo
		876	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		877	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		878	read DISPLAY # set it in our local shell
		879	fi
		880	fi
		881
		882	=item How do I compile the manual pages for myself?
		883
		884	You need to have a recent version of perl installed as F</usr/bin/perl>,
		885	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		886	the doc subdirectory and enter C<make alldoc>.
		887
		888	=item My question isn't answered here, can I ask a human?
		889
		890	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		891	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		892	interested in learning about new and exciting problems (but not FAQs :).
		893
		894	=back
		895
1	=head1 RXVT TECHNICAL REFERENCE	896	=head1 RXVT TECHNICAL REFERENCE
		897
		898	=head1 DESCRIPTION
		899
		900	The rest of this document describes various technical aspects of
		901	B<rxvt-unicode>. First the description of supported command sequences,
		902	followed by pixmap support and last by a description of all features
		903	selectable at C<configure> time.
2		904
3	=head1 Definitions	905	=head1 Definitions
4		906
5	=over 4	907	=over 4
6		908
…		…
135	Single Shift Select of G3 Character Set (SS3): affects next character	1037	Single Shift Select of G3 Character Set (SS3): affects next character
136	only I<unimplemented>	1038	only I<unimplemented>
137		1039
138	=item B<< C<ESC Z> >>	1040	=item B<< C<ESC Z> >>
139		1041
140	Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option>	1042	Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option>
141		1043
142	=item B<< C<ESC c> >>	1044	=item B<< C<ESC c> >>
143		1045
144	Full reset (RIS)	1046	Full reset (RIS)
145		1047
…		…
149		1051
150	=item B<< C<ESC o> >>	1052	=item B<< C<ESC o> >>
151		1053
152	Invoke the G3 Character Set (LS3)	1054	Invoke the G3 Character Set (LS3)
153		1055
154	=item B<< C<ESC>(C<C> >>	1056	=item B<< C<ESC ( C> >>
155		1057
156	Designate G0 Character Set (ISO 2022), see below for values of C<C>.	1058	Designate G0 Character Set (ISO 2022), see below for values of C<C>.
157		1059
158	=item B<< C<ESC>)C<C> >>	1060	=item B<< C<ESC ) C> >>
159		1061
160	Designate G1 Character Set (ISO 2022), see below for values of C<C>.	1062	Designate G1 Character Set (ISO 2022), see below for values of C<C>.
161		1063
162	=item B<< C<ESC * C> >>	1064	=item B<< C<ESC * C> >>
163		1065
…		…
187		1089
188	=back	1090	=back
189		1091
190	X<CSI>	1092	X<CSI>
191		1093
192	=head1 CSI (Code Sequence Introducer) Sequences	1094	=head1 CSI (Command Sequence Introducer) Sequences
193		1095
194	=over 4	1096	=over 4
195		1097
196	=item B<< C<ESC [ Ps @> >>	1098	=item B<< C<ESC [ Ps @> >>
197		1099
…		…
304		1206
305	=item B<< C<ESC [ Ps c> >>	1207	=item B<< C<ESC [ Ps c> >>
306		1208
307	Send Device Attributes (DA)	1209	Send Device Attributes (DA)
308	B<< C<Ps = 0> >> (or omitted): request attributes from terminal	1210	B<< C<Ps = 0> >> (or omitted): request attributes from terminal
309	returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video	1211	returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video
310	Option'')	1212	Option'')
311		1213
312	=item B<< C<ESC [ Ps d> >>	1214	=item B<< C<ESC [ Ps d> >>
313		1215
314	Cursor to Line B<< C<Ps> >> (VPA)	1216	Cursor to Line B<< C<Ps> >> (VPA)
…		…
330	B<< C<Ps = 0> >> Clear Current Column (default)	1232	B<< C<Ps = 0> >> Clear Current Column (default)
331	B<< C<Ps = 3> >> Clear All (TBC)	1233	B<< C<Ps = 3> >> Clear All (TBC)
332		1234
333	=end table	1235	=end table
334		1236
		1237	=item B<< C<ESC [ Pm h> >>
		1238
		1239	Set Mode (SM). See B<< C<ESC [ Pm l> >> sequence for description of C<Pm>.
		1240
335	=item B<< C<ESC [ Ps i> >>	1241	=item B<< C<ESC [ Ps i> >>
336		1242
337	Printing	1243	Printing. See also the C<print-pipe> resource.
338		1244
339	=begin table	1245	=begin table
340		1246
		1247	B<< C<Ps = 0> >> print screen (MC0)
341	B<< C<Ps = 4> >> disable transparent print mode (MC4)	1248	B<< C<Ps = 4> >> disable transparent print mode (MC4)
342	B<< C<Ps = 5> >> enable transparent print mode (MC5) I<unimplemented>	1249	B<< C<Ps = 5> >> enable transparent print mode (MC5)
343		1250
344	=end table	1251	=end table
345
346	=item B<< C<ESC [ Pm h> >>
347
348	Set Mode (SM). See next sequence for description of C<Pm>.
349		1252
350	=item B<< C<ESC [ Pm l> >>	1253	=item B<< C<ESC [ Pm l> >>
351		1254
352	Reset Mode (RM)	1255	Reset Mode (RM)
353		1256
…		…
360	B<< C<h> >> Insert Mode (SMIR)	1263	B<< C<h> >> Insert Mode (SMIR)
361	B<< C<l> >> Replace Mode (RMIR)	1264	B<< C<l> >> Replace Mode (RMIR)
362		1265
363	=end table	1266	=end table
364		1267
365	=item B<< C<Ps = 20> >> I<unimplemented>	1268	=item B<< C<Ps = 20> >> (partially implemented)
366		1269
367	=begin table	1270	=begin table
368		1271
369	B<< C<h> >> Automatic Newline (LNM)	1272	B<< C<h> >> Automatic Newline (LNM)
370	B<< C<h> >> Normal Linefeed (LNM)	1273	B<< C<l> >> Normal Linefeed (LNM)
371		1274
372	=end table	1275	=end table
373		1276
374	=back	1277	=back
375		1278
…		…
378	Character Attributes (SGR)	1281	Character Attributes (SGR)
379		1282
380	=begin table	1283	=begin table
381		1284
382	B<< C<Ps = 0> >> Normal (default)	1285	B<< C<Ps = 0> >> Normal (default)
383	B<< C<Ps = 1 / 22> >> On / Off Bold (bright fg)	1286	B<< C<Ps = 1 / 21> >> On / Off Bold (bright fg)
		1287	B<< C<Ps = 3 / 23> >> On / Off Italic
384	B<< C<Ps = 4 / 24> >> On / Off Underline	1288	B<< C<Ps = 4 / 24> >> On / Off Underline
385	B<< C<Ps = 5 / 25> >> On / Off Blink (bright bg)	1289	B<< C<Ps = 5 / 25> >> On / Off Slow Blink (bright bg)
		1290	B<< C<Ps = 6 / 26> >> On / Off Rapid Blink (bright bg)
386	B<< C<Ps = 7 / 27> >> On / Off Inverse	1291	B<< C<Ps = 7 / 27> >> On / Off Inverse
		1292	B<< C<Ps = 8 / 27> >> On / Off Invisible (NYI)
387	B<< C<Ps = 30 / 40> >> fg/bg Black	1293	B<< C<Ps = 30 / 40> >> fg/bg Black
388	B<< C<Ps = 31 / 41> >> fg/bg Red	1294	B<< C<Ps = 31 / 41> >> fg/bg Red
389	B<< C<Ps = 32 / 42> >> fg/bg Green	1295	B<< C<Ps = 32 / 42> >> fg/bg Green
390	B<< C<Ps = 33 / 43> >> fg/bg Yellow	1296	B<< C<Ps = 33 / 43> >> fg/bg Yellow
391	B<< C<Ps = 34 / 44> >> fg/bg Blue	1297	B<< C<Ps = 34 / 44> >> fg/bg Blue
392	B<< C<Ps = 35 / 45> >> fg/bg Magenta	1298	B<< C<Ps = 35 / 45> >> fg/bg Magenta
393	B<< C<Ps = 36 / 46> >> fg/bg Cyan	1299	B<< C<Ps = 36 / 46> >> fg/bg Cyan
		1300	B<< C<Ps = 38;5 / 48;5> >> set fg/bg to color #m (ISO 8613-6)
394	B<< C<Ps = 37 / 47> >> fg/bg White	1301	B<< C<Ps = 37 / 47> >> fg/bg White
395	B<< C<Ps = 39 / 49> >> fg/bg Default	1302	B<< C<Ps = 39 / 49> >> fg/bg Default
		1303	B<< C<Ps = 90 / 100> >> fg/bg Bright Black
		1304	B<< C<Ps = 91 / 101> >> fg/bg Bright Red
		1305	B<< C<Ps = 92 / 102> >> fg/bg Bright Green
		1306	B<< C<Ps = 93 / 103> >> fg/bg Bright Yellow
		1307	B<< C<Ps = 94 / 104> >> fg/bg Bright Blue
		1308	B<< C<Ps = 95 / 105> >> fg/bg Bright Magenta
		1309	B<< C<Ps = 96 / 106> >> fg/bg Bright Cyan
		1310	B<< C<Ps = 97 / 107> >> fg/bg Bright White
		1311	B<< C<Ps = 99 / 109> >> fg/bg Bright Default
396		1312
397	=end table	1313	=end table
398		1314
399	=item B<< C<ESC [ Ps n> >>	1315	=item B<< C<ESC [ Ps n> >>
400		1316
…		…
416		1332
417	=item B<< C<ESC [ s> >>	1333	=item B<< C<ESC [ s> >>
418		1334
419	Save Cursor (SC)	1335	Save Cursor (SC)
420		1336
		1337	=item B<< C<ESC [ Ps;Pt t> >>
		1338
		1339	Window Operations
		1340
		1341	=begin table
		1342
		1343	B<< C<Ps = 1> >> Deiconify (map) window
		1344	B<< C<Ps = 2> >> Iconify window
		1345	B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X|Y)
		1346	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
		1347	B<< C<Ps = 5> >> Raise window
		1348	B<< C<Ps = 6> >> Lower window
		1349	B<< C<Ps = 7> >> Refresh screen once
		1350	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
		1351	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
		1352	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
		1353	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
		1354	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
		1355	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
		1356	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
		1357	B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>)
		1358	B<< C<Ps = 24..> >> Set window height to C<Ps> rows
		1359
		1360	=end table
		1361
		1362	=item B<< C<ESC [ u> >>
		1363
		1364	Restore Cursor
		1365
421	=item B<< C<ESC [ Ps x> >>	1366	=item B<< C<ESC [ Ps x> >>
422		1367
423	Request Terminal Parameters (DECREQTPARM)	1368	Request Terminal Parameters (DECREQTPARM)
424
425	=item B<< C<ESC [ u> >>
426
427	Restore Cursor
428		1369
429	=back	1370	=back
430		1371
431	X<PrivateModes>	1372	X<PrivateModes>
432		1373
…		…
535	B<< C<h> >> Send Mouse X & Y on button press.	1476	B<< C<h> >> Send Mouse X & Y on button press.
536	B<< C<l> >> No mouse reporting.	1477	B<< C<l> >> No mouse reporting.
537		1478
538	=end table	1479	=end table
539		1480
540	X<Priv10>
541
542	=item B<< C<Ps = 10> >> (B<rxvt>)
543
544	=begin table
545
546	B<< C<h> >> visible
547	B<< C<l> >> invisible
548
549	=end table
550
551	=item B<< C<Ps = 25> >>	1481	=item B<< C<Ps = 25> >>
552		1482
553	=begin table	1483	=begin table
554		1484
555	B<< C<h> >> Visible cursor {cnorm/cvvis}	1485	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
653	B<< C<h> >> Use Hilite Mouse Tracking.	1583	B<< C<h> >> Use Hilite Mouse Tracking.
654	B<< C<l> >> No mouse reporting.	1584	B<< C<l> >> No mouse reporting.
655		1585
656	=end table	1586	=end table
657		1587
658	=item B<< C<Ps = 1010> >>	1588	=item B<< C<Ps = 1010> >> (B<rxvt>)
659		1589
660	=begin table	1590	=begin table
661		1591
662	B<< C<h> >> Don't scroll to bottom on TTY output	1592	B<< C<h> >> Don't scroll to bottom on TTY output
663	B<< C<l> >> Scroll to bottom on TTY output	1593	B<< C<l> >> Scroll to bottom on TTY output
664		1594
665	=end table	1595	=end table
666		1596
667	=item B<< C<Ps = 1011> >>	1597	=item B<< C<Ps = 1011> >> (B<rxvt>)
668		1598
669	=begin table	1599	=begin table
670		1600
671	B<< C<h> >> Scroll to bottom when a key is pressed	1601	B<< C<h> >> Scroll to bottom when a key is pressed
672	B<< C<l> >> Don't scroll to bottom when a key is pressed	1602	B<< C<l> >> Don't scroll to bottom when a key is pressed
673		1603
674	=end table	1604	=end table
675		1605
		1606	=item B<< C<Ps = 1021> >> (B<rxvt>)
		1607
		1608	=begin table
		1609
		1610	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
		1611	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
		1612
		1613	=end table
		1614
676	=item B<< C<Ps = 1047> >>	1615	=item B<< C<Ps = 1047> >>
677		1616
678	=begin table	1617	=begin table
679		1618
680	B<< C<h> >> Use Alternate Screen Buffer	1619	B<< C<h> >> Use Alternate Screen Buffer
…		…
686		1625
687	=begin table	1626	=begin table
688		1627
689	B<< C<h> >> Save cursor position	1628	B<< C<h> >> Save cursor position
690	B<< C<l> >> Restore cursor position	1629	B<< C<l> >> Restore cursor position
		1630
		1631	=end table
		1632
		1633	=item B<< C<Ps = 1049> >>
		1634
		1635	=begin table
		1636
		1637	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
		1638	B<< C<l> >> Use Normal Screen Buffer
691		1639
692	=end table	1640	=end table
693		1641
694	=back	1642	=back
695		1643
…		…
717	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	1665	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>
718	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	1666	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>
719	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	1667	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
720	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1668	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
721	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1669	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
722	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1670	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
723	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1671	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
724	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1672	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
725	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option>	1673	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
726	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1674	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
727	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>	1675	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
728	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> >>	1676	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> >>
729	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1677	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
730	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (@@RXVT_NAME@@ extension)	1678	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).
731	B<< C<Ps = 702> >> find font for character, used for debugging (@@RXVT_NAME@@ extension)	1679	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
732	B<< C<Ps = 703> >> command B<< C<Pt> >> I<rxvt compile-time option> (@@RXVT_NAME@@ extension)	1680	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
		1681	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		1682	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
		1683	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
		1684	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1685	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1686	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1687	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1688	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1689	B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
733		1690
734	=end table	1691	=end table
735		1692
736	=back	1693	=back
737		1694
738	X<menuBar>
739
740	=head1 menuBar
741
742	B<< The exact syntax used is I<almost> solidified. >>
743	In the menus, B<DON'T> try to use menuBar commands that add or remove a
744	menuBar.
745
746	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
747	omitted: use B<./> to specify a menu relative to the current menu.
748
749	=head2 Overview of menuBar operation
750
751	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
752	of C<Pt> can be used for a variety of tasks:
753
754	At the top level is the current menuBar which is a member of a circular
755	linked-list of other such menuBars.
756
757	The menuBar acts as a parent for the various drop-down menus, which in
758	turn, may have labels, separator lines, menuItems and subMenus.
759
760	The menuItems are the useful bits: you can use them to mimic keyboard
761	input or even to send text or escape sequences back to rxvt.
762
763	The menuBar syntax is intended to provide a simple yet robust method of
764	constructing and manipulating menus and navigating through the
765	menuBars.
766
767	The first step is to use the tag B<< [menu:I<name>] >> which creates
768	the menuBar called I<name> and allows access. You may now or menus,
769	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
770	menuBar access as B<readonly> to prevent accidental corruption of the
771	menus. To re-access the current menuBar for alterations, use the tag
772	B<[menu]>, make the alterations and then use B<[done]>
773
774	X<menuBarCommands>
775
776	=head2 Commands
777
778	=over 4
779
780	=item B<< [menu:+I<name>] >>
781
782	access the named menuBar for creation or alteration. If a new menuBar
783	is created, it is called I<name> (max of 15 chars) and the current
784	menuBar is pushed onto the stack
785
786	=item B<[menu]>
787
788	access the current menuBar for alteration
789
790	=item B<< [title:+I<string>] >>
791
792	set the current menuBar's title to I<string>, which may contain the
793	following format specifiers:
794	B<%%> : literal B<%> character
795	B<%n> : rxvt name (as per the B<-name> command-line option)
796	B<%v> : rxvt version
797
798	=item B<[done]>
799
800	set menuBar access as B<readonly>.
801	End-of-file tag for B<< [read:+I<file>] >> operations.
802
803	=item B<< [read:+I<file>] >>
804
805	read menu commands directly from I<file> (extension ".menu" will be
806	appended if required.) Start reading at a line with B<[menu]> or B<<
807	[menu:+I<name> >> and continuing until B<[done]> is encountered.
808
809	Blank and comment lines (starting with B<#>) are ignored. Actually,
810	since any invalid menu commands are also ignored, almost anything could
811	be construed as a comment line, but this may be tightened up in the
812	future ... so don't count on it!.
813
814	=item B<< [read:+I<file>;+I<name>] >>
815
816	The same as B<< [read:+I<file>] >>, but start reading at a line with
817	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
818	B<[done]> is encountered.
819
820	=item B<[dump]>
821
822	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
823	later rereading.
824
825	=item B<[rm:name]>
826
827	remove the named menuBar
828
829	=item B<[rm] [rm:]>
830
831	remove the current menuBar
832
833	=item B<[rm*] [rm:*]>
834
835	remove all menuBars
836
837	=item B<[swap]>
838
839	swap the top two menuBars
840
841	=item B<[prev]>
842
843	access the previous menuBar
844
845	=item B<[next]>
846
847	access the next menuBar
848
849	=item B<[show]>
850
851	Enable display of the menuBar
852
853	=item B<[hide]>
854
855	Disable display of the menuBar
856
857	=item B<< [pixmap:+I<name>] >>
858
859	=item B<< [pixmap:+I<name>;I<scaling>] >>
860
861	(set the background pixmap globally
862
863	B<< A Future implementation I<may> make this local to the menubar >>)
864
865	=item B<< [:+I<command>:] >>
866
867	ignore the menu readonly status and issue a I<command> to or a menu or
868	menuitem or change the ; a useful shortcut for setting the quick arrows
869	from a menuBar.
870
871	=back
872
873	X<menuBarAdd>
874
875	=head2 Adding and accessing menus
876
877	The following commands may also be B<+> prefixed.
878
879	=over 4
880
881	=item B</+>
882
883	access menuBar top level
884
885	=item B<./+>
886
887	access current menu level
888
889	=item B<../+>
890
891	access parent menu (1 level up)
892
893	=item B<../../>
894
895	access parent menu (multiple levels up)
896
897	=item B<< I</path/>menu >>
898
899	add/access menu
900
901	=item B<< I</path/>menu/* >>
902
903	add/access menu and clear it if it exists
904
905	=item B<< I</path/>{-} >>
906
907	add separator
908
909	=item B<< I</path/>{item} >>
910
911	add B<item> as a label
912
913	=item B<< I</path/>{item} action >>
914
915	add/alter I<menuitem> with an associated I<action>
916
917	=item B<< I</path/>{item}{right-text} >>
918
919	add/alter I<menuitem> with B<right-text> as the right-justified text
920	and as the associated I<action>
921
922	=item B<< I</path/>{item}{rtext} action >>
923
924	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
925	the right-justified text.
926
927	=back
928
929	=over 4
930
931	=item Special characters in I<action> must be backslash-escaped:
932
933	B<\a \b \E \e \n \r \t \octal>
934
935	=item or in control-character notation:
936
937	B<^@, ^A .. ^Z .. ^_, ^?>
938
939	=back
940
941	To send a string starting with a B<NUL> (B<^@>) character to the
942	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
943	the first of which will be stripped off and the balance directed to the
944	program. Otherwise if I<action> begins with B<NUL> followed by
945	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
946	balance is sent back to rxvt.
947
948	As a convenience for the many Emacs-type editors, I<action> may start
949	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
950	appended if missed from B<M-x> commands.
951
952	As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or
953	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
954
955	=over 4
956
957	=item For example,
958
959	B<M-xapropos> is equivalent to B<\Exapropos\r>
960
961	=item and
962
963	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
964
965	=back
966
967	The option B<< {I<right-rtext>} >> will be right-justified. In the
968	absence of a specified action, this text will be used as the I<action>
969	as well.
970
971	=over 4
972
973	=item For example,
974
975	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
976
977	=back
978
979	The left label I<is> necessary, since it's used for matching, but
980	implicitly hiding the left label (by using same name for both left and
981	right labels), or explicitly hiding the left label (by preceeding it
982	with a dot), makes it possible to have right-justified text only.
983
984	=over 4
985
986	=item For example,
987
988	B</File/{Open}{Open} Open-File-Action>
989
990	=item or hiding it
991
992	B</File/{.anylabel}{Open} Open-File-Action>
993
994	=back
995
996	X<menuBarRemove>
997
998	=head2 Removing menus
999
1000	=over 4
1001
1002	=item B<< -/*+ >>
1003
1004	remove all menus from the menuBar, the same as B<[clear]>
1005
1006	=item B<< -+I</path>menu+ >>
1007
1008	remove menu
1009
1010	=item B<< -+I</path>{item}+ >>
1011
1012	remove item
1013
1014	=item B<< -+I</path>{-} >>
1015
1016	remove separator)
1017
1018	=item B<-/path/menu/*>
1019
1020	remove all items, separators and submenus from menu
1021
1022	=back
1023
1024	X<menuBarArrows>
1025
1026	=head2 Quick Arrows
1027
1028	The menus also provide a hook for I<quick arrows> to provide easier
1029	user access. If nothing has been explicitly set, the default is to
1030	emulate the curror keys. The syntax permits each arrow to be altered
1031	individually or all four at once without re-entering their common
1032	beginning/end text. For example, to explicitly associate cursor actions
1033	with the arrows, any of the following forms could be used:
1034
1035	=over 4
1036
1037	=item B<< <r>+I<Right> >>
1038
1039	=item B<< <l>+I<Left> >>
1040
1041	=item B<< <u>+I<Up> >>
1042
1043	=item B<< <d>+I<Down> >>
1044
1045	Define actions for the respective arrow buttons
1046
1047	=item B<< <b>+I<Begin> >>
1048
1049	=item B<< <e>+I<End> >>
1050
1051	Define common beginning/end parts for I<quick arrows> which used in
1052	conjunction with the above <r> <l> <u> <d> constructs
1053
1054	=back
1055
1056	=over 4
1057
1058	=item For example, define arrows individually,
1059
1060	<u>\E[A
1061
1062	<d>\E[B
1063
1064	<r>\E[C
1065
1066	<l>\E[D
1067
1068	=item or all at once
1069
1070	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
1071
1072	=item or more compactly (factoring out common parts)
1073
1074	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
1075
1076	=back
1077
1078	X<menuBarSummary>
1079
1080	=head2 Command Summary
1081
1082	A short summary of the most I<common> commands:
1083
1084	=over 4
1085
1086	=item [menu:name]
1087
1088	use an existing named menuBar or start a new one
1089
1090	=item [menu]
1091
1092	use the current menuBar
1093
1094	=item [title:string]
1095
1096	set menuBar title
1097
1098	=item [done]
1099
1100	set menu access to readonly and, if reading from a file, signal EOF
1101
1102	=item [done:name]
1103
1104	if reading from a file using [read:file;name] signal EOF
1105
1106	=item [rm:name]
1107
1108	remove named menuBar(s)
1109
1110	=item [rm] [rm:]
1111
1112	remove current menuBar
1113
1114	=item [rm*] [rm:*]
1115
1116	remove all menuBar(s)
1117
1118	=item [swap]
1119
1120	swap top two menuBars
1121
1122	=item [prev]
1123
1124	access the previous menuBar
1125
1126	=item [next]
1127
1128	access the next menuBar
1129
1130	=item [show]
1131
1132	map menuBar
1133
1134	=item [hide]
1135
1136	unmap menuBar
1137
1138	=item [pixmap;file]
1139
1140	=item [pixmap;file;scaling]
1141
1142	set a background pixmap
1143
1144	=item [read:file]
1145
1146	=item [read:file;name]
1147
1148	read in a menu from a file
1149
1150	=item [dump]
1151
1152	dump out all menuBars to /tmp/rxvt-PID
1153
1154	=item /
1155
1156	access menuBar top level
1157
1158	=item ./
1159
1160	=item ../
1161
1162	=item ../../
1163
1164	access current or parent menu level
1165
1166	=item /path/menu
1167
1168	add/access menu
1169
1170	=item /path/{-}
1171
1172	add separator
1173
1174	=item /path/{item}{rtext} action
1175
1176	add/alter menu item
1177
1178	=item -/*
1179
1180	remove all menus from the menuBar
1181
1182	=item -/path/menu
1183
1184	remove menu items, separators and submenus from menu
1185
1186	=item -/path/menu
1187
1188	remove menu
1189
1190	=item -/path/{item}
1191
1192	remove item
1193
1194	=item -/path/{-}
1195
1196	remove separator
1197
1198	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
1199
1200	menu quick arrows
1201
1202	=back
1203	X<XPM>	1695	X<XPM>
1204		1696
1205	=head1 XPM	1697	=head1 XPM
1206		1698
1207	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1699	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
…		…
1390	XK_KP_8 8 ESC O x	1882	XK_KP_8 8 ESC O x
1391	XK_KP_9 9 ESC O y	1883	XK_KP_9 9 ESC O y
1392		1884
1393	=end table	1885	=end table
1394		1886
		1887	=head1 CONFIGURE OPTIONS
		1888
		1889	General hint: if you get compile errors, then likely your configuration
		1890	hasn't been tested well. Either try with C<--enable-everything> or use
		1891	the F<./reconf> script as a base for experiments. F<./reconf> is used by
		1892	myself, so it should generally be a working config. Of course, you should
		1893	always report when a combination doesn't work, so it can be fixed. Marc
		1894	Lehmann <rxvt@schmorp.de>.
		1895
		1896	All
		1897
		1898	=over 4
		1899
		1900	=item --enable-everything
		1901
		1902	Add (or remove) support for all non-multichoice options listed in "./configure
		1903	--help".
		1904
		1905	You can specify this and then disable options you do not like by
		1906	I<following> this with the appropriate C<--disable-...> arguments,
		1907	or you can start with a minimal configuration by specifying
		1908	C<--disable-everything> and than adding just the C<--enable-...> arguments
		1909	you want.
		1910
		1911	=item --enable-xft (default: enabled)
		1912
		1913	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
		1914	slower and require lots of memory, but as long as you don't use them, you
		1915	don't pay for them.
		1916
		1917	=item --enable-font-styles (default: on)
		1918
		1919	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
		1920	styles. The fonts can be set manually or automatically.
		1921
		1922	=item --with-codesets=NAME,... (default: all)
		1923
		1924	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
		1925	are always compiled in, which includes most 8-bit character sets). These
		1926	codeset tables are used for driving X11 core fonts, they are not required
		1927	for Xft fonts, although having them compiled in lets rxvt-unicode choose
		1928	replacement fonts more intelligently. Compiling them in will make your
		1929	binary bigger (all of together cost about 700kB), but it doesn't increase
		1930	memory usage unless you use a font requiring one of these encodings.
		1931
		1932	=begin table
		1933
		1934	all all available codeset groups
		1935	zh common chinese encodings
		1936	zh_ext rarely used but very big chinese encodigs
		1937	jp common japanese encodings
		1938	jp_ext rarely used but big japanese encodings
		1939	kr korean encodings
		1940
		1941	=end table
		1942
		1943	=item --enable-xim (default: on)
		1944
		1945	Add support for XIM (X Input Method) protocol. This allows using
		1946	alternative input methods (e.g. kinput2) and will also correctly
		1947	set up the input for people using dead keys or compose keys.
		1948
		1949	=item --enable-unicode3 (default: off)
		1950
		1951	Enable direct support for displaying unicode codepoints above
		1952	65535 (the basic multilingual page). This increases storage
		1953	requirements per character from 2 to 4 bytes. X11 fonts do not yet
		1954	support these extra characters, but Xft does.
		1955
		1956	Please note that rxvt-unicode can store unicode code points >65535
		1957	even without this flag, but the number of such characters is
		1958	limited to a view thousand (shared with combining characters,
		1959	see next switch), and right now rxvt-unicode cannot display them
		1960	(input/output and cut&paste still work, though).
		1961
		1962	=item --enable-combining (default: on)
		1963
		1964	Enable automatic composition of combining characters into
		1965	composite characters. This is required for proper viewing of text
		1966	where accents are encoded as seperate unicode characters. This is
		1967	done by using precomposited characters when available or creating
		1968	new pseudo-characters when no precomposed form exists.
		1969
		1970	Without --enable-unicode3, the number of additional precomposed characters
		1971	is rather limited (2048, if this is full, rxvt-unicode will use the
		1972	private use area, extending the number of combinations to 8448). With
		1973	--enable-unicode3, no practical limit exists.
		1974
		1975	This option will also enable storage (but not display) of characters
		1976	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
		1977
		1978	The combining table also contains entries for arabic presentation forms,
		1979	but these are not currently used. Bug me if you want these to be used (and
		1980	tell me how these are to be used...).
		1981
		1982	=item --enable-fallback(=CLASS) (default: Rxvt)
		1983
		1984	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.
		1985
		1986	=item --with-res-name=NAME (default: urxvt)
		1987
		1988	Use the given name as default application name when
		1989	reading resources. Specify --with-res-name=rxvt to replace rxvt.
		1990
		1991	=item --with-res-class=CLASS /default: URxvt)
		1992
		1993	Use the given class as default application class
		1994	when reading resources. Specify --with-res-class=Rxvt to replace
		1995	rxvt.
		1996
		1997	=item --enable-utmp (default: on)
		1998
		1999	Write user and tty to utmp file (used by programs like F<w>) at
		2000	start of rxvt execution and delete information when rxvt exits.
		2001
		2002	=item --enable-wtmp (default: on)
		2003
		2004	Write user and tty to wtmp file (used by programs like F<last>) at
		2005	start of rxvt execution and write logout when rxvt exits. This
		2006	option requires --enable-utmp to also be specified.
		2007
		2008	=item --enable-lastlog (default: on)
		2009
		2010	Write user and tty to lastlog file (used by programs like
		2011	F<lastlogin>) at start of rxvt execution. This option requires
		2012	--enable-utmp to also be specified.
		2013
		2014	=item --enable-xpm-background (default: on)
		2015
		2016	Add support for XPM background pixmaps.
		2017
		2018	=item --enable-transparency (default: on)
		2019
		2020	Add support for inheriting parent backgrounds thus giving a fake
		2021	transparency to the term.
		2022
		2023	=item --enable-fading (default: on)
		2024
		2025	Add support for fading the text when focus is lost (requires C<--enable-transparency>).
		2026
		2027	=item --enable-tinting (default: on)
		2028
		2029	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
		2030
		2031	=item --enable-rxvt-scroll (default: on)
		2032
		2033	Add support for the original rxvt scrollbar.
		2034
		2035	=item --enable-next-scroll (default: on)
		2036
		2037	Add support for a NeXT-like scrollbar.
		2038
		2039	=item --enable-xterm-scroll (default: on)
		2040
		2041	Add support for an Xterm-like scrollbar.
		2042
		2043	=item --enable-plain-scroll (default: on)
		2044
		2045	Add support for a very unobtrusive, plain-looking scrollbar that
		2046	is the favourite of the rxvt-unicode author, having used it for
		2047	many years.
		2048
		2049	=item --enable-ttygid (default: off)
		2050
		2051	Change tty device setting to group "tty" - only use this if
		2052	your system uses this type of security.
		2053
		2054	=item --disable-backspace-key
		2055
		2056	Removes any handling of the backspace key by us - let the X server do it.
		2057
		2058	=item --disable-delete-key
		2059
		2060	Removes any handling of the delete key by us - let the X server
		2061	do it.
		2062
		2063	=item --disable-resources
		2064
		2065	Removes any support for resource checking.
		2066
		2067	=item --disable-swapscreen
		2068
		2069	Remove support for secondary/swap screen.
		2070
		2071	=item --enable-frills (default: on)
		2072
		2073	Add support for many small features that are not essential but nice to
		2074	have. Normally you want this, but for very small binaries you may want to
		2075	disable this.
		2076
		2077	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
		2078	in combination with other switches) is:
		2079
		2080	MWM-hints
		2081	EWMH-hints (pid, utf8 names) and protocols (ping)
		2082	seperate underline colour (-underlineColor)
		2083	settable border widths and borderless switch (-w, -b, -bl)
		2084	settable extra linespacing /-lsp)
		2085	iso-14755-2 and -3, and visual feedback
		2086	backindex and forwardindex escape sequence
		2087	window op and some xterm/OSC escape sequences
		2088	tripleclickwords (-tcw)
		2089	settable insecure mode (-insecure)
		2090	keysym remapping support
		2091	cursor blinking and underline cursor (-cb, -uc)
		2092	XEmbed support (-embed)
		2093	user-pty (-pty-fd)
		2094	hold on exit (-hold)
		2095	skip builtin block graphics (-sbg)
		2096	sgr modes 90..97 and 100..107
		2097
		2098	=item --enable-iso14755 (default: on)
		2099
		2100	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
		2101	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
		2102	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
		2103	this switch.
		2104
		2105	=item --enable-keepscrolling (default: on)
		2106
		2107	Add support for continual scrolling of the display when you hold
		2108	the mouse button down on a scrollbar arrow.
		2109
		2110	=item --enable-mousewheel (default: on)
		2111
		2112	Add support for scrolling via mouse wheel or buttons 4 & 5.
		2113
		2114	=item --enable-slipwheeling (default: on)
		2115
		2116	Add support for continual scrolling (using the mouse wheel as an
		2117	accelerator) while the control key is held down. This option
		2118	requires --enable-mousewheel to also be specified.
		2119
		2120	=item --disable-new-selection
		2121
		2122	Remove support for mouse selection style like that of xterm.
		2123
		2124	=item --enable-dmalloc (default: off)
		2125
		2126	Use Gray Watson's malloc - which is good for debugging See
		2127	http://www.letters.com/dmalloc/ for details If you use either this or the
		2128	next option, you may need to edit src/Makefile after compiling to point
		2129	DINCLUDE and DLIB to the right places.
		2130
		2131	You can only use either this option and the following (should
		2132	you use either) .
		2133
		2134	=item --enable-dlmalloc (default: off)
		2135
		2136	Use Doug Lea's malloc - which is good for a production version
		2137	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
		2138
		2139	=item --enable-smart-resize (default: on)
		2140
		2141	Add smart growth/shrink behaviour when changing font size via hot
		2142	keys. This should keep the window corner which is closest to a corner of
		2143	the screen in a fixed position.
		2144
		2145	=item --enable-pointer-blank (default: on)
		2146
		2147	Add support to have the pointer disappear when typing or inactive.
		2148
		2149	=item --enable-perl (default: off)
		2150
		2151	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
		2152	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
		2153	in F<src/perl-ext/> for the extensions that are installed by default. The
		2154	perl interpreter that is used can be specified via the C<PERL> environment
		2155	variable when running configure.
		2156
		2157	=item --with-name=NAME (default: urxvt)
		2158
		2159	Set the basename for the installed binaries, resulting
		2160	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
		2161	C<rxvt>.
		2162
		2163	=item --with-term=NAME (default: rxvt-unicode)
		2164
		2165	Change the environmental variable for the terminal to NAME.
		2166
		2167	=item --with-terminfo=PATH
		2168
		2169	Change the environmental variable for the path to the terminfo tree to
		2170	PATH.
		2171
		2172	=item --with-x
		2173
		2174	Use the X Window System (pretty much default, eh?).
		2175
		2176	=item --with-xpm-includes=DIR
		2177
		2178	Look for the XPM includes in DIR.
		2179
		2180	=item --with-xpm-library=DIR
		2181
		2182	Look for the XPM library in DIR.
		2183
		2184	=item --with-xpm
		2185
		2186	Not needed - define via --enable-xpm-background.
		2187
		2188	=back
		2189
1395	=head1 AUTHORS	2190	=head1 AUTHORS
1396		2191
1397	Marc Lehmann <rxvt@schmorp.de> converted this document to pod and	2192	Marc Lehmann <rxvt@schmorp.de> converted this document to pod and
1398	reworked it from the original Rxvt documentation, which was done by Geoff	2193	reworked it from the original Rxvt documentation, which was done by Geoff
1399	Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other	2194	Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other

Diff Legend

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