[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.12 by root, Mon Aug 16 00:17:27 2004 UTC vs.
Revision 1.47 by root, Mon Feb 14 10:48:44 2005 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 How do I know which rxvt-unicode version I'm using?
		30
		31	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.
		33
		34	=item I am using Debian GNU/Linux and have a problem...
		35
		36	The Debian GNU/Linux package of rxvt-unicode contains large patches that
		37	considerably change the behaviour of rxvt-unicode. Before reporting a
		38	bug to the original rxvt-unicode author please download and install the
		39	genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to
		40	reproduce the problem. If you cannot, chances are that the problems are
		41	specific to Debian GNU/Linux, in which case it should be reported via the
		42	Debian Bug Tracking System (use C<reportbug> to report the bug).
		43
		44	For other problems that also affect the Debian package, you can and
		45	probably should use the Debian BTS, too, because, after all, it's also a
		46	bug in the Debian version and it serves as a reminder for other users that
		47	might encounter the same issue.
		48
		49	=item When I log-in to another system it tells me about missing terminfo data?
		50
		51	The terminal description used by rxvt-unicode is not as widely available
		52	as that for xterm, or even rxvt (for which the same problem often arises).
		53
		54	The correct solution for this problem is to install the terminfo, this can
		55	be done like this (with ncurses' infocmp):
		56
		57	REMOTE=remotesystem.domain
		58	infocmp rxvt-unicode \| ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
		59
		60	... or by installing rxvt-unicode normally on the remote system,
		61
		62	If you cannot or do not want to do this, then you can simply set
		63	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
		64	problems arising, which includes wrong keymapping, less and different
		65	colours and some refresh errors in fullscreen applications. It's a nice
		66	quick-and-dirty workaround for rare cases, though.
		67
		68	If you always want to do this (and are fine with the consequences) you
		69	can either recompile rxvt-unicode with the desired TERM value or use a
		70	resource to set it:
		71
		72	URxvt.termName: rxvt
		73
		74	If you don't plan to use B<rxvt> (quite common...) you could also replace
		75	the rxvt terminfo file with the rxvt-unicode one.
		76
		77	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
		78
		79	=item I need a termcap file entry.
		80
		81	One reason you might want this is that some distributions or operating
		82	systems still compile some programs using the long-obsoleted termcap
		83	library (Fedora Core's bash is one example) and rely on a termcap entry
		84	for C<rxvt-unicode>.
		85
		86	You could use rxvt's termcap entry with resonable results in many cases.
		87	You can also create a termcap entry by using terminfo's infocmp program
		88	like this:
		89
		90	infocmp -C rxvt-unicode
		91
		92	Or you could use this termcap entry, generated by the command above:
		93
		94	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
		95	:am:bw:eo:km:mi:ms:xn:xo:\
		96	:co#80:it#8:li#24:lm#0:\
		97	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
		98	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
		99	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\
		100	:as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\
		101	:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\
		102	:ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\
		103	:im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
		104	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
		105	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
		106	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
		107	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
		108	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
		109	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
		110	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
		111	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
		112	:vs=\E[?25h:
		113
		114	=item Why does C<ls> no longer have coloured output?
		115
		116	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
		117	decide wether a terminal has colour, but uses it's own configuration
		118	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
		119	with most other terminals supporting colour). Either add:
		120
		121	TERM rxvt-unicode
		122
		123	to C</etc/DIR_COLORS> or simply add:
		124
		125	alias ls='ls --color=auto'
		126
		127	to your C<.profile> or C<.bashrc>.
		128
		129	=item Why doesn't vim/emacs etc. use the 88 colour mode?
		130
		131	=item Why doesn't vim/emacs etc. make use of italic?
		132
		133	=item Why are the secondary screen-related options not working properly?
		134
		135	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
		136	distributions (most notably Debian GNU/Linux) break rxvt-unicode
		137	by setting C<TERM> to C<rxvt>, which doesn't have these extra
		138	features. Unfortunately, some of these (most notably, again, Debian
		139	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
		140	file, so you will need to install it on your own (See the question B<When
		141	I log-in to another system it tells me about missing terminfo data?> on
		142	how to do this).
		143
		144	=item My numerical keypad acts weird and generates differing output?
		145
		146	Some Debian GNUL/Linux users seem to have this problem, although no
		147	specific details were reported so far. It is possible that this is caused
		148	by the wrong C<TERM> setting, although the details of wether and how
		149	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		150	keymap. See the answer to the previous question, and please report if that
		151	helped.
		152
		153	=item Rxvt-unicode does not seem to understand the selected encoding?
		154
		155	=item Unicode does not seem to work?
		156
		157	If you encounter strange problems like typing an accented character but
		158	getting two unrelated other characters or similar, or if program output is
		159	subtly garbled, then you should check your locale settings.
		160
		161	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
		162	programs. Often rxvt-unicode is started in the C<C> locale, while the
		163	login script running within the rxvt-unicode window changes the locale to
		164	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
		165
		166	The best thing is to fix your startup environment, as you will likely run
		167	into other problems. If nothing works you can try this in your .profile.
		168
		169	printf '\e]701;%s\007' "$LC_CTYPE"
		170
		171	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
		172	supported on your systems. Some systems have a C<locale> command which
		173	displays this (also, C<perl -e0> can be used to check locale settings, as
		174	it will complain loudly if it cannot set the locale). If it displays something
		175	like:
		176
		177	locale: Cannot set LC_CTYPE to default locale: ...
		178
		179	Then the locale you specified is not supported on your system.
		180
		181	If nothing works and you are sure that everything is set correctly then
		182	you will need to remember a little known fact: Some programs just don't
		183	support locales :(
		184
		185	=item Why do some characters look so much different than others?
		186
		187	=item How does rxvt-unicode choose fonts?
		188
		189	Most fonts do not contain the full range of Unicode, which is
		190	fine. Chances are that the font you (or the admin/package maintainer of
		191	your system/os) have specified does not cover all the characters you want
		192	to display.
		193
		194	B<rxvt-unicode> makes a best-effort try at finding a replacement
		195	font. Often the result is fine, but sometimes the chosen font looks
		196	bad/ugly/wrong. Some fonts have totally strange characters that don't
		197	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		198	intelligence to detect that a specific glyph is wrong: it has to believe
		199	the font that the characters it claims to contain indeed look correct.
		200
		201	In that case, select a font of your taste and add it to the font list,
		202	e.g.:
		203
		204	@@RXVT_NAME@@ -fn basefont,font2,font3...
		205
		206	When rxvt-unicode sees a character, it will first look at the base
		207	font. If the base font does not contain the character, it will go to the
		208	next font, and so on. Specifying your own fonts will also speed up this
		209	search and use less resources within rxvt-unicode and the X-server.
		210
		211	The only limitation is that none of the fonts may be larger than the base
		212	font, as the base font defines the terminal character cell size, which
		213	must be the same due to the way terminals work.
		214
		215	=item Why do some chinese characters look so different than others?
		216
		217	This is because there is a difference between script and language --
		218	rxvt-unicode does not know which language the text that is output is,
		219	as it only knows the unicode character codes. If rxvt-unicode first
		220	sees a japanese/chinese character, it might choose a japanese font for
		221	display. Subsequent japanese characters will use that font. Now, many
		222	chinese characters aren't represented in japanese fonts, so when the first
		223	non-japanese character comes up, rxvt-unicode will look for a chinese font
		224	-- unfortunately at this point, it will still use the japanese font for
		225	chinese characters that are also in the japanese font.
		226
		227	The workaround is easy: just tag a chinese font at the end of your font
		228	list (see the previous question). The key is to view the font list as
		229	a preference list: If you expect more japanese, list a japanese font
		230	first. If you expect more chinese, put a chinese font first.
		231
		232	In the future it might be possible to switch language preferences at
		233	runtime (the internal data structure has no problem with using different
		234	fonts for the same character at the same time, but no interface for this
		235	has been designed yet).
		236
		237	Until then, you might get away with switching fonts at runtime (see L<Can
		238	I switch the fonts at runtime?> later in this document).
		239
		240	=item Why does rxvt-unicode sometimes leave pixel droppings?
		241
		242	Most fonts were not designed for terminal use, which means that character
		243	size varies a lot. A font that is otherwise fine for terminal use might
		244	contain some characters that are simply too wide. Rxvt-unicode will avoid
		245	these characters. For characters that are just "a bit" too wide a special
		246	"careful" rendering mode is used that redraws adjacent characters.
		247
		248	All of this requires that fonts do not lie about character sizes,
		249	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		250	box, and rxvt-unicode has no way of detecting this (the correct way is to
		251	ask for the character bounding box, which unfortunately is wrong in these
		252	cases).
		253
		254	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		255	or the respective font. If you encounter this problem you might try using
		256	the C<-lsp> option to give the font more height. If that doesn't work, you
		257	might be forced to use a different font.
		258
		259	All of this is not a problem when using X11 core fonts, as their bounding
		260	box data is correct.
		261
		262	=item My Compose (Multi_key) key is no longer working.
		263
		264	The most common causes for this are that either your locale is not set
		265	correctly, or you specified a B<preeditStyle> that is not supported by
		266	your input method. For example, if you specified B<OverTheSpot> and
		267	your input method (e.g. the default input method handling Compose keys)
		268	does not support this (for instance because it is not visual), then
		269	rxvt-unicode will continue without an input method.
		270
		271	In this case either do not specify a B<preeditStyle> or specify more than
		272	one pre-edit style, such as B<OverTheSpot,Root,None>.
		273
		274	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		275
		276	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		277	international keyboards) or simply use ISO 14755 support to your
		278	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		279	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		280	character and so on.
		281
		282	=item How can I keep rxvt-unicode from using reverse video so much?
		283
		284	First of all, make sure you are running with the right terminal settings
		285	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		286	make sure you have specified colours for italic and bold, as otherwise
		287	rxvt-unicode might use reverse video to simulate the effect:
		288
		289	URxvt.colorBD: white
		290	URxvt.colorIT: green
		291
		292	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
		293
		294	For some unexplainable reason, some rare programs assume a very weird
		295	colour palette when confronted with a terminal with more than the standard
		296	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		297	these programs not to assume non-ISO colours without very good reasons.
		298
		299	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		300	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		301	fix colours but keep you from using other rxvt-unicode features.
		302
		303	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
		304
		305	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
		306	in your compile environment, or an implementation that implements it,
		307	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
		308	B<wchar_t> is represented as unicode.
		309
		310	As you might have guessed, FreeBSD does neither define this symobl nor
		311	does it support it. Instead, it uses it's own internal representation of
		312	B<wchar_t>. This is, of course, completely fine with respect to standards.
		313
		314	However, C<__STDC_ISO_10646__> is the only sane way to support
		315	multi-language apps in an OS, as using a locale-dependent (and
		316	non-standardized) representation of B<wchar_t> makes it impossible to
		317	convert between B<wchar_t> (as used by X11 and your applications) and any
		318	other encoding without implementing OS-specific-wrappers for each and
		319	every locale. There simply are no APIs to convert B<wchar_t> into anything
		320	except the current locale encoding.
		321
		322	Some applications (such as the formidable B<mlterm>) work around this
		323	by carrying their own replacement functions for character set handling
		324	with them, and either implementing OS-dependent hacks or doing multiple
		325	conversions (which is slow and unreliable in case the OS implements
		326	encodings slightly different than the terminal emulator).
		327
		328	The rxvt-unicode author insists that the right way to fix this is in the
		329	system libraries once and for all, instead of forcing every app to carry
		330	complete replacements for them :)
		331
		332	=item How does rxvt-unicode determine the encoding to use?
		333
		334	=item Is there an option to switch encodings?
		335
		336	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		337	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
		338	UTF-8 or any other encodings with respect to terminal I/O.
		339
		340	The reasons is that there exists a perfectly fine mechanism for selecting
		341	the encoding, doing I/O and (most important) communicating this to all
		342	applications so everybody agrees on character properties such as width
		343	and code number. This mechanism is the I<locale>. Applications not using
		344	that info will have problems (for example, C<xterm> gets the width of
		345	characters wrong as it uses it's own, locale-independent table under all
		346	locales).
		347
		348	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
		349	programs doing the same (that is, most) will automatically agree in the
		350	interpretation of characters.
		351
		352	Unfortunately, there is no system-independent way to select locales, nor
		353	is there a standard on how locale specifiers will look like.
		354
		355	On most systems, the content of the C<LC_CTYPE> environment variable
		356	contains an arbitrary string which corresponds to an already-installed
		357	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		358	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		359	(i.e. C<de> or C<german>) are also common.
		360
		361	Rxvt-unicode ignores all other locale categories, and except for
		362	the encoding, ignores country or language-specific settings,
		363	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		364	rxvt-unicode.
		365
		366	If you want to use a specific encoding you have to make sure you start
		367	rxvt-unicode with the correct C<LC_CTYPE> category.
		368
		369	=item Can I switch locales at runtime?
		370
		371	Yes, using an escape sequence. Try something like this, which sets
		372	rxvt-unicode's idea of C<LC_CTYPE>.
		373
		374	printf '\e]701;%s\007' ja_JP.SJIS
		375
		376	See also the previous answer.
		377
		378	Sometimes this capability is rather handy when you want to work in
		379	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		380	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		381	first switches to a locale supported by xjdic and back later:
		382
		383	printf '\e]701;%s\007' ja_JP.SJIS
		384	xjdic -js
		385	printf '\e]701;%s\007' de_DE.UTF-8
		386
		387	You can also use xterm's C<luit> program, which usually works fine, except
		388	for some locales where character width differs between program- and
		389	rxvt-unicode-locales.
		390
		391	=item Can I switch the fonts at runtime?
		392
		393	Yes, using an escape sequence. Try something like this, which has the same
		394	effect as using the C<-fn> switch, and takes effect immediately:
		395
		396	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		397
		398	This is useful if you e.g. work primarily with japanese (and prefer a
		399	japanese font), but you have to switch to chinese temporarily, where
		400	japanese fonts would only be in your way.
		401
		402	You can think of this as a kind of manual ISO-2022 switching.
		403
		404	=item Why do italic characters look as if clipped?
		405
		406	Many fonts have difficulties with italic characters and hinting. For
		407	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		408	Mono> completely fails in it's italic face. A workaround might be to
		409	enable freetype autohinting, i.e. like this:
		410
		411	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		412	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		413
		414	=item My input method wants <some encoding> but I want UTF-8, what can I do?
		415
		416	You can specify separate locales for the input method and the rest of the
		417	terminal, using the resource C<imlocale>:
		418
		419	URxvt*imlocale: ja_JP.EUC-JP
		420
		421	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		422	use your input method. Please note, however, that you will not be able to
		423	input characters outside C<EUC-JP> in a normal way then, as your input
		424	method limits you.
		425
		426	=item Rxvt-unicode crashes when the X Input Method changes or exits.
		427
		428	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		429	design. Applications can avoid some crashes at the expense of memory
		430	leaks, and Input Methods can avoid some crashes by careful ordering at
		431	exit time. B<kinput2> (and derived input methods) generally succeeds,
		432	while B<SCIM> (or similar input methods) fails. In the end, however,
		433	crashes cannot be completely avoided even if both sides cooperate.
		434
		435	So the only workaround is not to kill your Input Method Servers.
		436
		437	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
		438
		439	Rxvt-unicode tries to obey the rule of not charging you for something you
		440	don't use. One thing you should try is to configure out all settings that
		441	you don't need, for example, Xft support is a resource hog by design,
		442	when used. Compiling it out ensures that no Xft font will be loaded
		443	accidentally when rxvt-unicode tries to find a font for your characters.
		444
		445	Also, many people (me included) like large windows and even larger
		446	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		447	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		448	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		449	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		450	rxvt-unicode then uses 8 bytes per screen cell.
		451
		452	=item Can I speed up Xft rendering somehow?
		453
		454	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		455	it is simply slow. If you still want Xft fonts you might try to disable
		456	antialiasing (by appending C<:antialiasing=false>), which saves lots of
		457	memory and also speeds up rendering considerably.
		458
		459	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		460
		461	Rxvt-unicode will use whatever you specify as a font. If it needs to
		462	fall back to it's default font search list it will prefer X11 core
		463	fonts, because they are small and fast, and then use Xft fonts. It has
		464	antialiasing disabled for most of them, because the author thinks they
		465	look best that way.
		466
		467	If you want antialiasing, you have to specify the fonts manually.
		468
		469	=item Mouse cut/paste suddenly no longer works.
		470
		471	Make sure that mouse reporting is actually turned off since killing
		472	some editors prematurely may leave the mouse in mouse report mode. I've
		473	heard that tcsh may use mouse reporting unless it otherwise specified. A
		474	quick check is to see if cut/paste works when the Alt or Shift keys are
		475	depressed. See @@RXVT_NAME@@(7)
		476
		477	=item What's with this bold/blink stuff?
		478
		479	If no bold colour is set via C<colorBD:>, bold will invert text using the
		480	standard foreground colour.
		481
		482	For the standard background colour, blinking will actually make the
		483	text blink when compiled with C<--enable-blinking>. with standard
		484	colours. Without C<--enable-blinking>, the blink attribute will be
		485	ignored.
		486
		487	On ANSI colours, bold/blink attributes are used to set high-intensity
		488	foreground/background colors.
		489
		490	color0-7 are the low-intensity colors.
		491
		492	color8-15 are the corresponding high-intensity colors.
		493
		494	=item I don't like the screen colors. How do I change them?
		495
		496	You can change the screen colors at run-time using F<~/.Xdefaults>
		497	resources (or as long-options).
		498
		499	Here are values that are supposed to resemble a VGA screen,
		500	including the murky brown that passes for low-intensity yellow:
		501
		502	URxvt.color0: #000000
		503	URxvt.color1: #A80000
		504	URxvt.color2: #00A800
		505	URxvt.color3: #A8A800
		506	URxvt.color4: #0000A8
		507	URxvt.color5: #A800A8
		508	URxvt.color6: #00A8A8
		509	URxvt.color7: #A8A8A8
		510
		511	URxvt.color8: #000054
		512	URxvt.color9: #FF0054
		513	URxvt.color10: #00FF54
		514	URxvt.color11: #FFFF54
		515	URxvt.color12: #0000FF
		516	URxvt.color13: #FF00FF
		517	URxvt.color14: #00FFFF
		518	URxvt.color15: #FFFFFF
		519
		520	And here is a more complete set of non-standard colors described (not by
		521	me) as "pretty girly".
		522
		523	URxvt.cursorColor: #dc74d1
		524	URxvt.pointerColor: #dc74d1
		525	URxvt.background: #0e0e0e
		526	URxvt.foreground: #4ad5e1
		527	URxvt.color0: #000000
		528	URxvt.color8: #8b8f93
		529	URxvt.color1: #dc74d1
		530	URxvt.color9: #dc74d1
		531	URxvt.color2: #0eb8c7
		532	URxvt.color10: #0eb8c7
		533	URxvt.color3: #dfe37e
		534	URxvt.color11: #dfe37e
		535	URxvt.color5: #9e88f0
		536	URxvt.color13: #9e88f0
		537	URxvt.color6: #73f7ff
		538	URxvt.color14: #73f7ff
		539	URxvt.color7: #e1dddd
		540	URxvt.color15: #e1dddd
		541
		542	=item How can I start @@RXVT_NAME@@d in a race-free way?
		543
		544	Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a
		545	server that answers @@RXVT_NAME@@c's requests, so it doesn't background
		546	itself.
		547
		548	To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
		549	following method to wait for the startup message before continuing:
		550
		551	{ @@RXVT_NAME@@d & } \| read
		552
		553	=item What's with the strange Backspace/Delete key behaviour?
		554
		555	Assuming that the physical Backspace key corresponds to the
		556	BackSpace keysym (not likely for Linux ... see the following
		557	question) there are two standard values that can be used for
		558	Backspace: C<^H> and C<^?>.
		559
		560	Historically, either value is correct, but rxvt-unicode adopts the debian
		561	policy of using C<^?> when unsure, because it's the one only only correct
		562	choice :).
		563
		564	Rxvt-unicode tries to inherit the current stty settings and uses the value
		565	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		566	started from a terminal (say, from a menu or by remote shell), then the
		567	system value of `erase', which corresponds to CERASE in <termios.h>, will
		568	be used (which may not be the same as your stty setting).
		569
		570	For starting a new rxvt-unicode:
		571
		572	# use Backspace = ^H
		573	$ stty erase ^H
		574	$ @@RXVT_NAME@@
		575
		576	# use Backspace = ^?
		577	$ stty erase ^?
		578	$ @@RXVT_NAME@@
		579
		580	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
		581
		582	For an existing rxvt-unicode:
		583
		584	# use Backspace = ^H
		585	$ stty erase ^H
		586	$ echo -n "^[[36h"
		587
		588	# use Backspace = ^?
		589	$ stty erase ^?
		590	$ echo -n "^[[36l"
		591
		592	This helps satisfy some of the Backspace discrepancies that occur, but
		593	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		594	properly reflects that.
		595
		596	The Delete key is a another casualty of the ill-defined Backspace problem.
		597	To avoid confusion between the Backspace and Delete keys, the Delete
		598	key has been assigned an escape sequence to match the vt100 for Execute
		599	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		600
		601	Some other Backspace problems:
		602
		603	some editors use termcap/terminfo,
		604	some editors (vim I'm told) expect Backspace = ^H,
		605	GNU Emacs (and Emacs-like editors) use ^H for help.
		606
		607	Perhaps someday this will all be resolved in a consistent manner.
		608
		609	=item I don't like the key-bindings. How do I change them?
		610
		611	There are some compile-time selections available via configure. Unless
		612	you have run "configure" with the C<--disable-resources> option you can
		613	use the `keysym' resource to alter the keystrings associated with keysyms.
		614
		615	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
		616
		617	URxvt.keysym.Home: \033[1~
		618	URxvt.keysym.End: \033[4~
		619	URxvt.keysym.C-apostrophe: \033<C-'>
		620	URxvt.keysym.C-slash: \033<C-/>
		621	URxvt.keysym.C-semicolon: \033<C-;>
		622	URxvt.keysym.C-grave: \033<C-`>
		623	URxvt.keysym.C-comma: \033<C-,>
		624	URxvt.keysym.C-period: \033<C-.>
		625	URxvt.keysym.C-0x60: \033<C-`>
		626	URxvt.keysym.C-Tab: \033<C-Tab>
		627	URxvt.keysym.C-Return: \033<C-Return>
		628	URxvt.keysym.S-Return: \033<S-Return>
		629	URxvt.keysym.S-space: \033<S-Space>
		630	URxvt.keysym.M-Up: \033<M-Up>
		631	URxvt.keysym.M-Down: \033<M-Down>
		632	URxvt.keysym.M-Left: \033<M-Left>
		633	URxvt.keysym.M-Right: \033<M-Right>
		634	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		635	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		636	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		637
		638	See some more examples in the documentation for the B<keysym> resource.
		639
		640	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
		641	How do I make use of them? For example, the Sun Keyboard type 4
		642	has the following mappings that rxvt-unicode doesn't recognize.
		643
		644	KP_Insert == Insert
		645	F22 == Print
		646	F27 == Home
		647	F29 == Prior
		648	F33 == End
		649	F35 == Next
		650
		651	Rather than have rxvt-unicode try to accommodate all the various possible
		652	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		653	required for your particular machine.
		654
		655	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
		656	I need this to decide about setting colors etc.
		657
		658	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
		659	check and see if that is set. Note that several programs, JED, slrn,
		660	Midnight Commander automatically check this variable to decide whether or
		661	not to use color.
		662
		663	=item How do I set the correct, full IP address for the DISPLAY variable?
		664
		665	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		666	insecure mode then it is possible to use the following shell script
		667	snippets to correctly set the display. If your version of rxvt-unicode
		668	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		669	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		670	regular xterm.
		671
		672	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		673	snippets:
		674
		675	# Bourne/Korn/POSIX family of shells:
		676	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		677	if [ ${TERM:-foo} = xterm ]; then
		678	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		679	echo -n '^[Z'
		680	read term_id
		681	stty icanon echo
		682	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		683	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		684	read DISPLAY # set it in our local shell
		685	fi
		686	fi
		687
		688	=item How do I compile the manual pages for myself?
		689
		690	You need to have a recent version of perl installed as F</usr/bin/perl>,
		691	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		692	the doc subdirectory and enter C<make alldoc>.
		693
		694	=item My question isn't answered here, can I ask a human?
		695
		696	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		697	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		698	interested in learning about new and exciting problems (but not FAQs :).
		699
		700	=back
		701
1	=head1 RXVT TECHNICAL REFERENCE	702	=head1 RXVT TECHNICAL REFERENCE
		703
		704	=head1 DESCRIPTION
		705
		706	The rest of this document describes various technical aspects of
		707	B<rxvt-unicode>. First the description of supported command sequences,
		708	followed by menu and pixmap support and last by a description of all
		709	features selectable at C<configure> time.
2		710
3	=head1 Definitions	711	=head1 Definitions
4		712
5	=over 4	713	=over 4
6		714
135	Single Shift Select of G3 Character Set (SS3): affects next character	843	Single Shift Select of G3 Character Set (SS3): affects next character
136	only I<unimplemented>	844	only I<unimplemented>
137		845
138	=item B<< C<ESC Z> >>	846	=item B<< C<ESC Z> >>
139		847
140	Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option>	848	Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option>
141		849
142	=item B<< C<ESC c> >>	850	=item B<< C<ESC c> >>
143		851
144	Full reset (RIS)	852	Full reset (RIS)
145		853
…		…
149		857
150	=item B<< C<ESC o> >>	858	=item B<< C<ESC o> >>
151		859
152	Invoke the G3 Character Set (LS3)	860	Invoke the G3 Character Set (LS3)
153		861
154	=item B<< C<ESC>(C<C> >>	862	=item B<< C<ESC ( C> >>
155		863
156	Designate G0 Character Set (ISO 2022), see below for values of C<C>.	864	Designate G0 Character Set (ISO 2022), see below for values of C<C>.
157		865
158	=item B<< C<ESC>)C<C> >>	866	=item B<< C<ESC ) C> >>
159		867
160	Designate G1 Character Set (ISO 2022), see below for values of C<C>.	868	Designate G1 Character Set (ISO 2022), see below for values of C<C>.
161		869
162	=item B<< C<ESC * C> >>	870	=item B<< C<ESC * C> >>
163		871
…		…
304		1012
305	=item B<< C<ESC [ Ps c> >>	1013	=item B<< C<ESC [ Ps c> >>
306		1014
307	Send Device Attributes (DA)	1015	Send Device Attributes (DA)
308	B<< C<Ps = 0> >> (or omitted): request attributes from terminal	1016	B<< C<Ps = 0> >> (or omitted): request attributes from terminal
309	returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video	1017	returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video
310	Option'')	1018	Option'')
311		1019
312	=item B<< C<ESC [ Ps d> >>	1020	=item B<< C<ESC [ Ps d> >>
313		1021
314	Cursor to Line B<< C<Ps> >> (VPA)	1022	Cursor to Line B<< C<Ps> >> (VPA)
…		…
330	B<< C<Ps = 0> >> Clear Current Column (default)	1038	B<< C<Ps = 0> >> Clear Current Column (default)
331	B<< C<Ps = 3> >> Clear All (TBC)	1039	B<< C<Ps = 3> >> Clear All (TBC)
332		1040
333	=end table	1041	=end table
334		1042
		1043	=item B<< C<ESC [ Pm h> >>
		1044
		1045	Set Mode (SM). See B<< C<ESC [ Pm l> >> sequence for description of C<Pm>.
		1046
335	=item B<< C<ESC [ Ps i> >>	1047	=item B<< C<ESC [ Ps i> >>
336		1048
337	Printing	1049	Printing. See also the C<print-pipe> resource.
338		1050
339	=begin table	1051	=begin table
340		1052
		1053	B<< C<Ps = 0> >> print screen (MC0)
341	B<< C<Ps = 4> >> disable transparent print mode (MC4)	1054	B<< C<Ps = 4> >> disable transparent print mode (MC4)
342	B<< C<Ps = 5> >> enable transparent print mode (MC5) I<unimplemented>	1055	B<< C<Ps = 5> >> enable transparent print mode (MC5)
343		1056
344	=end table	1057	=end table
345
346	=item B<< C<ESC [ Pm h> >>
347
348	Set Mode (SM). See next sequence for description of C<Pm>.
349		1058
350	=item B<< C<ESC [ Pm l> >>	1059	=item B<< C<ESC [ Pm l> >>
351		1060
352	Reset Mode (RM)	1061	Reset Mode (RM)
353		1062
…		…
379		1088
380	=begin table	1089	=begin table
381		1090
382	B<< C<Ps = 0> >> Normal (default)	1091	B<< C<Ps = 0> >> Normal (default)
383	B<< C<Ps = 1 / 21> >> On / Off Bold (bright fg)	1092	B<< C<Ps = 1 / 21> >> On / Off Bold (bright fg)
384	B<< C<Ps = 3 / 23> >> On / Off Italic (NYI)	1093	B<< C<Ps = 3 / 23> >> On / Off Italic
385	B<< C<Ps = 4 / 24> >> On / Off Underline	1094	B<< C<Ps = 4 / 24> >> On / Off Underline
386	B<< C<Ps = 5 / 25> >> On / Off Slow Blink (bright bg)	1095	B<< C<Ps = 5 / 25> >> On / Off Slow Blink (bright bg)
387	B<< C<Ps = 6 / 26> >> On / Off Rapid Blink (bright bg)	1096	B<< C<Ps = 6 / 26> >> On / Off Rapid Blink (bright bg)
		1097	B<< C<Ps = 7 / 27> >> On / Off Inverse
388	B<< C<Ps = 7 / 27> >> On / Off Invisible (NYI)	1098	B<< C<Ps = 8 / 27> >> On / Off Invisible (NYI)
389	B<< C<Ps = 8 / 27> >> On / Off Inverse
390	B<< C<Ps = 30 / 40> >> fg/bg Black	1099	B<< C<Ps = 30 / 40> >> fg/bg Black
391	B<< C<Ps = 31 / 41> >> fg/bg Red	1100	B<< C<Ps = 31 / 41> >> fg/bg Red
392	B<< C<Ps = 32 / 42> >> fg/bg Green	1101	B<< C<Ps = 32 / 42> >> fg/bg Green
393	B<< C<Ps = 33 / 43> >> fg/bg Yellow	1102	B<< C<Ps = 33 / 43> >> fg/bg Yellow
394	B<< C<Ps = 34 / 44> >> fg/bg Blue	1103	B<< C<Ps = 34 / 44> >> fg/bg Blue
395	B<< C<Ps = 35 / 45> >> fg/bg Magenta	1104	B<< C<Ps = 35 / 45> >> fg/bg Magenta
396	B<< C<Ps = 36 / 46> >> fg/bg Cyan	1105	B<< C<Ps = 36 / 46> >> fg/bg Cyan
		1106	B<< C<Ps = 38;5 / 48;5> >> set fg/bg to color #m (ISO 8613-6)
397	B<< C<Ps = 37 / 47> >> fg/bg White	1107	B<< C<Ps = 37 / 47> >> fg/bg White
398	B<< C<Ps = 39 / 49> >> fg/bg Default	1108	B<< C<Ps = 39 / 49> >> fg/bg Default
399	B<< C<Ps = 90 / 100> >> fg/bg Bright Black	1109	B<< C<Ps = 90 / 100> >> fg/bg Bright Black
400	B<< C<Ps = 91 / 101> >> fg/bg Bright Red	1110	B<< C<Ps = 91 / 101> >> fg/bg Bright Red
401	B<< C<Ps = 92 / 102> >> fg/bg Bright Green	1111	B<< C<Ps = 92 / 102> >> fg/bg Bright Green
…		…
428		1138
429	=item B<< C<ESC [ s> >>	1139	=item B<< C<ESC [ s> >>
430		1140
431	Save Cursor (SC)	1141	Save Cursor (SC)
432		1142
		1143	=item B<< C<ESC [ Ps;Pt t> >>
		1144
		1145	Window Operations
		1146
		1147	=begin table
		1148
		1149	B<< C<Ps = 1> >> Deiconify (map) window
		1150	B<< C<Ps = 2> >> Iconify window
		1151	B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X\|Y)
		1152	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
		1153	B<< C<Ps = 5> >> Raise window
		1154	B<< C<Ps = 6> >> Lower window
		1155	B<< C<Ps = 7> >> Refresh screen once
		1156	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
		1157	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
		1158	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
		1159	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
		1160	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
		1161	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
		1162	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
		1163	B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>)
		1164	B<< C<Ps = 24..> >> Set window height to C<Ps> rows
		1165
		1166	=end table
		1167
		1168	=item B<< C<ESC [ u> >>
		1169
		1170	Restore Cursor
		1171
433	=item B<< C<ESC [ Ps x> >>	1172	=item B<< C<ESC [ Ps x> >>
434		1173
435	Request Terminal Parameters (DECREQTPARM)	1174	Request Terminal Parameters (DECREQTPARM)
436
437	=item B<< C<ESC [ u> >>
438
439	Restore Cursor
440		1175
441	=back	1176	=back
442		1177
443	X<PrivateModes>	1178	X<PrivateModes>
444		1179
…		…
745	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1480	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
746	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>	1481	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>
747	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> >>	1482	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> >>
748	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1483	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
749	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)	1484	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)
750	B<< C<Ps = 702> >> find font for character, used for debugging (@@RXVT_NAME@@ extension)
751	B<< C<Ps = 703> >> menubar command B<< C<Pt> >> I<rxvt compile-time option> (@@RXVT_NAME@@ extension)	1485	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)
		1486	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
		1487	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>
		1488	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
		1489	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
		1490	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
		1491	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
752		1492
753	=end table	1493	=end table
754		1494
755	=back	1495	=back
756		1496
…		…
808		1548
809	=item B<< [title:+I<string>] >>	1549	=item B<< [title:+I<string>] >>
810		1550
811	set the current menuBar's title to I<string>, which may contain the	1551	set the current menuBar's title to I<string>, which may contain the
812	following format specifiers:	1552	following format specifiers:
813	B<%%> : literal B<%> character	1553
814	B<%n> : rxvt name (as per the B<-name> command-line option)	1554	B<%n> rxvt name (as per the B<-name> command-line option)
815	B<%v> : rxvt version	1555	B<%v> rxvt version
		1556	B<%%> literal B<%> character
816		1557
817	=item B<[done]>	1558	=item B<[done]>
818		1559
819	set menuBar access as B<readonly>.	1560	set menuBar access as B<readonly>.
820	End-of-file tag for B<< [read:+I<file>] >> operations.	1561	End-of-file tag for B<< [read:+I<file>] >> operations.
…		…
966		1707
967	As a convenience for the many Emacs-type editors, I<action> may start	1708	As a convenience for the many Emacs-type editors, I<action> may start
968	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be	1709	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
969	appended if missed from B<M-x> commands.	1710	appended if missed from B<M-x> commands.
970		1711
971	As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or	1712	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
972	quick arrow), a B<BEL> (B<^G>) will be appended if needed.	1713	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
973		1714
974	=over 4	1715	=over 4
975		1716
976	=item For example,	1717	=item For example,
…		…
1433		2174
1434	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2175	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
1435	slower and require lots of memory, but as long as you don't use them, you	2176	slower and require lots of memory, but as long as you don't use them, you
1436	don't pay for them.	2177	don't pay for them.
1437		2178
		2179	=item --enable-font-styles
		2180
		2181	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
		2182	styles. The fonts can be set manually or automatically.
		2183
1438	=item --with-codesets=NAME,...	2184	=item --with-codesets=NAME,...
1439		2185
1440	Compile in support for additional codeset (encoding) groups. These codeset	2186	Compile in support for additional codeset (encoding) groups (eu, vn are
		2187	always compiled in, which includes most 8-bit character sets). These
1441	tables are currently only used for driving X11 core fonts, they are not	2188	codeset tables are currently only used for driving X11 core fonts, they
1442	required for Xft fonts. Compiling them in will make your binary bigger	2189	are not required for Xft fonts. Compiling them in will make your binary
1443	(together about 700kB), but it doesn't increase memory usage unless you	2190	bigger (together about 700kB), but it doesn't increase memory usage unless
1444	use an X11 font requiring one of these encodings.	2191	you use an X11 font requiring one of these encodings.
1445		2192
1446	=begin table	2193	=begin table
1447		2194
1448	all all available codeset groups	2195	all all available codeset groups
1449	cn common chinese encodings	2196	zh common chinese encodings
1450	cn_ext rarely used but very big chinese encodigs	2197	zh_ext rarely used but very big chinese encodigs
1451	jp common japanese encodings	2198	jp common japanese encodings
1452	jp_ext rarely used but big japanese encodings	2199	jp_ext rarely used but big japanese encodings
1453	kr korean encodings	2200	kr korean encodings
1454		2201
1455	=end table	2202	=end table
…		…
1479	composite characters. This is required for proper viewing of text	2226	composite characters. This is required for proper viewing of text
1480	where accents are encoded as seperate unicode characters. This is	2227	where accents are encoded as seperate unicode characters. This is
1481	done by using precomposited characters when available or creating	2228	done by using precomposited characters when available or creating
1482	new pseudo-characters when no precomposed form exists.	2229	new pseudo-characters when no precomposed form exists.
1483		2230
1484	Without --enable-unicode3, the number of additional precomposed	2231	Without --enable-unicode3, the number of additional precomposed characters
1485	characters is rather limited (2048, if this is full, rxvt will use the	2232	is rather limited (2048, if this is full, rxvt-unicode will use the
1486	private use area, extending the number of combinations to 8448). With	2233	private use area, extending the number of combinations to 8448). With
1487	--enable-unicode3, no practical limit exists. This will also enable	2234	--enable-unicode3, no practical limit exists.
1488	storage of characters >65535.	2235
		2236	This option will also enable storage (but not display) of characters
		2237	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
1489		2238
1490	The combining table also contains entries for arabic presentation forms,	2239	The combining table also contains entries for arabic presentation forms,
1491	but these are not currently used. Bug me if you want these to be used.	2240	but these are not currently used. Bug me if you want these to be used (and
		2241	tell me how these are to be used...).
1492		2242
1493	=item --enable-fallback(=CLASS)	2243	=item --enable-fallback(=CLASS)
1494		2244
1495	When reading resource settings, also read settings for class CLASS	2245	When reading resource settings, also read settings for class CLASS
1496	(default: Rxvt). To disable resource fallback use --disable-fallback.	2246	(default: Rxvt). To disable resource fallback use --disable-fallback.
…		…
1588	Remove all resources checking.	2338	Remove all resources checking.
1589		2339
1590	=item --enable-xgetdefault	2340	=item --enable-xgetdefault
1591		2341
1592	Make resources checking via XGetDefault() instead of our small	2342	Make resources checking via XGetDefault() instead of our small
1593	version which only checks ~/.Xdefaults, or if that doesn't exist	2343	version which only checks ~/.Xdefaults, or if that doesn't exist then
1594	then ~/.Xresources.	2344	~/.Xresources.
		2345
		2346	Please note that nowadays, things like XIM will automatically pull in and
		2347	use the full X resource manager, so the overhead of using it might be very
		2348	small, if nonexistant.
1595		2349
1596	=item --enable-strings	2350	=item --enable-strings
1597		2351
1598	Add support for our possibly faster memset() function and other	2352	Add support for our possibly faster memset() function and other
1599	various routines, overriding your system's versions which may	2353	various routines, overriding your system's versions which may
…		…
1609		2363
1610	Add support for many small features that are not essential but nice to	2364	Add support for many small features that are not essential but nice to
1611	have. Normally you want this, but for very small binaries you may want to	2365	have. Normally you want this, but for very small binaries you may want to
1612	disable this.	2366	disable this.
1613		2367
		2368	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
		2369	in combination with other switches) is:
		2370
		2371	MWM-hints
		2372	seperate underline colour
		2373	settable border widths and borderless switch
		2374	settable extra linespacing
		2375	extra window properties (e.g. UTF-8 window names and PID)
		2376	iso-14755-2 and -3, and visual feedback
		2377	backindex and forwardindex escape sequence
		2378	window op and locale change escape sequences
		2379	tripleclickwords
		2380	settable insecure mode
		2381	keysym remapping support
		2382
1614	=item --enable-iso14755	2383	=item --enable-iso14755
1615		2384
1616	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2385	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
1617	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2386	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
1618	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with	2387	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
1619	this switch.	2388	this switch.
1620		2389
1621	=item --enable-linespace
1622
1623	Add support to provide user specified line spacing between text rows.
1624
1625	=item --enable-keepscrolling	2390	=item --enable-keepscrolling
1626		2391
1627	Add support for continual scrolling of the display when you hold	2392	Add support for continual scrolling of the display when you hold
1628	the mouse button down on a scrollbar arrow.	2393	the mouse button down on a scrollbar arrow.
1629		2394
…		…
1660		2425
1661	Add smart growth/shrink behaviour when changing font size via from hot	2426	Add smart growth/shrink behaviour when changing font size via from hot
1662	keys. This should keep in a fixed position the rxvt corner which is	2427	keys. This should keep in a fixed position the rxvt corner which is
1663	closest to a corner of the screen.	2428	closest to a corner of the screen.
1664		2429
1665	=item --enable-256-color
1666
1667	Add support for 256 colours rather than the base 16 colours.
1668
1669	This option will likely go away in the future. Speak up if you don't want
1670	this.
1671
1672	=item --enable-cursor-blink	2430	=item --enable-cursor-blink
1673		2431
1674	Add support for a blinking cursor.	2432	Add support for a blinking cursor.
1675		2433
1676	=item --enable-pointer-blank	2434	=item --enable-pointer-blank
1677		2435
1678	Add support to have the pointer disappear when typing or inactive.	2436	Add support to have the pointer disappear when typing or inactive.
1679		2437
1680	=item --with-name=NAME	2438	=item --with-name=NAME
1681		2439
1682	Set the basename for the installed binaries (default: urxvt, resulting in	2440	Set the basename for the installed binaries (default: C<urxvt>, resulting
1683	urxvt, urxvtd etc.). Specify --with-name=rxvt to replace rxvt.	2441	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
		2442	C<rxvt>.
1684		2443
1685	=item --with-term=NAME	2444	=item --with-term=NAME
1686		2445
1687	Change the environmental variable for the terminal to NAME (default	2446	Change the environmental variable for the terminal to NAME (default
1688	"rxvt")	2447	C<rxvt-unicode>)
1689		2448
1690	=item --with-terminfo=PATH	2449	=item --with-terminfo=PATH
1691		2450
1692	Change the environmental variable for the path to the terminfo tree to	2451	Change the environmental variable for the path to the terminfo tree to
1693	PATH.	2452	PATH.

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.12 by root, Mon Aug 16 00:17:27 2004 UTC vs. Revision 1.47 by root, Mon Feb 14 10:48:44 2005 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.12 by root, Mon Aug 16 00:17:27 2004 UTC vs.
Revision 1.47 by root, Mon Feb 14 10:48:44 2005 UTC