[ViewVC] Diff of: 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.33 by root, Sun Jan 16 18:48:04 2005 UTC

…		…
		1	=head1 NAME
		2
		3	RXVT REFERENCE - FAQ, command sequences and other background information
		4
		5	=head1 FREQUENTLY ASKED QUESTIONS
		6
		7	=over 4
		8
		9	=item How do I know which rxvt-unicode version I'm using?
		10
		11	The version number is displayed with the usage (-h). Also the escape
		12	sequence C<ESC[8n> sets the window title to the version number.
		13
		14	=item When I log-in to another system it tells me about missing terminfo data?
		15
		16	The terminal description used by rxvt-unicode is not as widely available
		17	as that for xterm, or even rxvt (for which the same problem often arises).
		18
		19	The correct solution for this problem is to install the terminfo, this can
		20	be done like this (with ncurses' infocmp):
		21
		22	REMOTE=remotesystem.domain
		23	infocmp rxvt-unicode \| ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
		24
		25	... or by installing rxvt-unicode normally on the remote system,
		26
		27	If you cannot or do not want to do this, then you can simply set
		28	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
		29	problems arising, which includes wrong keymapping, less and different
		30	colours and some refresh errors in fullscreen applications. It's a nice
		31	quick-and-dirty workaround for rare cases, though.
		32
		33	If you always want to do this you can either recompile rxvt-unicode with
		34	the desired TERM value or use a resource to set it:
		35
		36	URxvt.termName: rxvt
		37
		38	If you don't plan to use B<rxvt> (quite common...) you could also replace
		39	the rxvt terminfo file with the rxvt-unicode one.
		40
		41	=item I need a termcap file entry.
		42
		43	You could use rxvt's termcap entry with resonable results in many cases.
		44	You can also create a termcap entry by using terminfo's infocmp program
		45	like this:
		46
		47	infocmp -C rxvt-unicode
		48
		49	OR you could this termcap entry:
		50
		51	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
		52	:am:bw:eo:km:mi:ms:xn:xo:\
		53	:co#80:it#8:li#24:\
		54	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
		55	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
		56	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\
		57	:as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\
		58	:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\
		59	:ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\
		60	:im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
		61	:k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\
		62	:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\
		63	:kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\
		64	:ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\
		65	:ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\
		66	:nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\
		67	:st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\
		68	:up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
		69	:vs=\E[?25h:
		70
		71	=item Why does C<ls> no longer have coloured output?
		72
		73	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
		74	decide wether a terminal has colour, but uses it's own configuration
		75	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
		76	with most other terminals supporting colour). Either add:
		77
		78	TERM rxvt-unicode
		79
		80	to C</etc/DIR_COLORS> or simply add:
		81
		82	alias ls='ls --color=auto'
		83
		84	to your C<.profile> or C<.bashrc>.
		85
		86	=item Why doesn't vim/emacs etc. use the 88 colour mode?
		87
		88	=item Why doesn't vim/emacs etc. make use of italic?
		89
		90	=item Why are the secondary screen-related options not working properly?
		91
		92	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
		93	distributions (most notably Debian GNU/Linux) break rxvt-unicode
		94	by setting C<TERM> to C<rxvt>, which doesn't have these extra
		95	features. Unfortunately, some of these (most notably, again, Debian
		96	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
		97	file, so you will need to install it on your own (See the question B<When
		98	I log-in to another system it tells me about missing terminfo data?> on
		99	how to do this).
		100
		101	=item Rxvt-unicode does not seem to understand the selected encoding?
		102
		103	=item Unicode does not seem to work?
		104
		105	If you encounter strange problems like typing an accented character but
		106	getting two unrelated other characters or similar, or if program output is
		107	subtly garbled, then you should check your locale settings.
		108
		109	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
		110	programs. Often rxvt-unicode is started in the C<C> locale, while the
		111	login script running within the rxvt-unicode window changes the locale to
		112	sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work.
		113
		114	The best thing is to fix your startup environment, as you will likely run
		115	into other problems. If nothing works you can try this in your .profile.
		116
		117	printf '\e]701;%s\007' "$LC_CTYPE"
		118
		119	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
		120	supported on your systems. Some systems have a C<locale> command which
		121	displays this. If it displays sth. like:
		122
		123	locale: Cannot set LC_CTYPE to default locale: ...
		124
		125	Then the locale you specified is not supported on your system.
		126
		127	If nothing works and you are sure that everything is set correctly then
		128	you will need to remember a little known fact: Some programs just don't
		129	support locales :(
		130
		131	=item Why do some characters look so much different than others?
		132
		133	=item How does rxvt-unicode choose fonts?
		134
		135	Most fonts do not contain the full range of Unicode, which is
		136	fine. Chances are that the font you (or the admin/package maintainer of
		137	your system/os) have specified does not cover all the characters you want
		138	to display.
		139
		140	B<rxvt-unicode> makes a best-effort try at finding a replacement
		141	font. Often the result is fine, but sometimes the chosen font looks
		142	bad. Many fonts have totally strange characters that don't resemble the
		143	correct glyph at all, and rxvt-unicode lacks the artificial intelligence
		144	to detect that a specific glyph is wrong: it has to believe the font that
		145	the characters it contains indeed look correct.
		146
		147	In that case, select a font of your taste and add it to the font list,
		148	e.g.:
		149
		150	@@RXVT_NAME@@ -fn basefont,font2,font3...
		151
		152	When rxvt-unicode sees a character, it will first look at the base
		153	font. If the base font does not contain the character, it will go to the
		154	next font, and so on. Specifying your own fonts will also speed up this
		155	search and use less resources within rxvt-unicode and the X-server.
		156
		157	The only limitation is that all the fonts must not be larger than the base
		158	font, as the base font defines the principal cell size, which must be the
		159	same due to the way terminals work.
		160
		161	=item Why do some chinese characters look so different than others?
		162
		163	This is because there is a difference between script and language --
		164	rxvt-unicode does not know which language the text that is output
		165	is, as it only knows the unicode character codes. If rxvt-unicode
		166	first sees a japanese character, it might choose a japanese font for
		167	it. Subsequent japanese characters will take that font. Now, many chinese
		168	characters aren't represented in japanese fonts, so when the first
		169	non-japanese character comes up, rxvt-unicode will look for a chinese font
		170	-- unfortunately at this point, it will still use the japanese font for
		171	japanese characters that are also chinese.
		172
		173	The workaround is easy: just tag a chinese font at the end of your font
		174	list (see the previous question). The key is to view the font list as
		175	a preference list: If you expect more japanese, list a japanese font
		176	first. If you expect more chinese, put a chinese font first.
		177
		178	In the future it might be possible to switch preferences at runtime (the
		179	internal data structure has no problem with using different fonts for
		180	the same character at the same time, but no interface for this has been
		181	designed yet).
		182
		183	=item Why does rxvt-unicode sometimes leave pixel droppings?
		184
		185	Most fonts were not designed for terminal use, which means that character
		186	size varies a lot. A font that is otherwise fine for terminal use might
		187	contain some characters that are simply too wide. Rxvt-unicode will avoid
		188	these characters. For characters that are just "a bit" too wide a special
		189	"careful" rendering mode is used that redraws adjacent characters.
		190
		191	All of this requires that fonts do not lie about character sizes,
		192	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		193	box, and rxvt-unicode has no way of detecting this (the correct way is to
		194	ask for the character bounding box, which unfortunately is wrong in these
		195	cases).
		196
		197	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		198	or the respective font. If you encounter this problem you might try using
		199	the C<-lsp> option to give the font more height. If that doesn't work, you
		200	might be forced to use a different font.
		201
		202	All of this is not a problem when using X11 core fonts, as their bounding
		203	box data is correct.
		204
		205	=item My Compose (Multi_key) key is no longer working.
		206
		207	The most common causes for this are that either your locale is not set
		208	correctly, or you specified a B<preeditStyle> that is not supported by
		209	your input method. For example, if you specified B<OverTheSpot> and
		210	your input method (e.g. the default input method handling Compose keys)
		211	does not support this (for instance because it is not visual), then
		212	rxvt-unicode will continue without an input method.
		213
		214	In this case either do not specify a B<preeditStyle> or specify more than
		215	one pre-edit style, such as B<OverTheSpot,Root,None>.
		216
		217	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		218
		219	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		220	international keyboards) or simply use ISO 14755 support to your
		221	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		222	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		223	character and so on.
		224
		225	=item How can I keep rxvt-unicode from using reverse video so much?
		226
		227	First of all, make sure you are running with the right terminfo
		228	(C<urxvt>), which will get rid of most of these effects. Then make sure
		229	you have specified colours for italic and bold, as otherwise rxvt-unicode
		230	might use reverse video to simulate the effect:
		231
		232	URxvt*colorBD: white
		233	URxvt*colorIT: green
		234
		235	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
		236
		237	For some unexplainable reason, some programs (i.e. irssi) assume a very
		238	weird colour palette when confronted with a terminal with more than the
		239	standard 8 colours (rxvt-unicode supports 88). The right fix is, of
		240	course, to fix these programs not to assume non-ISO colours without very
		241	good reasons.
		242
		243	In the meantime, you can either edit your C<urxvt> terminfo definition to
		244	only claim 8 colour support or use C<TERM=rxvt>, which will fix colours
		245	but keep you from using other rxvt-unicode features.
		246
		247	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
		248
		249	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
		250	in your compile environment, or an implementation that implements it,
		251	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
		252	B<wchar_t> is represented as unicode.
		253
		254	As you might have guessed, FreeBSD does neither define this symobl nor
		255	does it support it. Instead, it uses it's own internal representation of
		256	B<wchar_t>. This is, of course, completely legal.
		257
		258	However, C<__STDC_ISO_10646__> is the only sane way to support
		259	multi-language apps in an OS, as using a locale-dependent (and
		260	non-standardized) representation of B<wchar_t> makes it impossible to
		261	convert between B<wchar_t> (as used by X11 and your applications) and any
		262	other encoding without implementing OS-specific-wrappers for each and
		263	every locale. There simply are no APIs to convert B<wchar_t> into anything
		264	except the current locale encoding.
		265
		266	Some applications (such as the formidable B<mlterm>) work around this
		267	by carrying their own replacement functions for character set handling
		268	with them, and either implementing OS-dependent hacks or doing multiple
		269	conversions (which is slow and unreliable in case the OS implements
		270	encodings slightly different than the terminal emulator).
		271
		272	The rxvt-unicode author insists that the right way to fix this is in the
		273	system libraries once and for all, instead of forcing every app to carry
		274	complete replacements.
		275
		276	=item How does rxvt-unicode determine the encoding to use?
		277
		278	=item Is there an option to switch encodings?
		279
		280	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		281	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
		282	UTF-8 or any other encodings with respect to terminal I/O.
		283
		284	The reasons is that there exists a perfectly fine mechanism for selecting
		285	the encoding, doing I/O and (most important) communicating this to all
		286	applications so everybody agrees on character properties such as width and
		287	code number. This mechanism is the I<locale>.
		288
		289	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
		290	programs doing the same (that is, most) will automatically agree in the
		291	interpretation of characters.
		292
		293	Unfortunately, there is no system-independent way to select locales, nor
		294	is there a standard on how locale specifiers will look like.
		295
		296	On most systems, the content of the C<LC_CTYPE> environment variable
		297	contains an arbitrary string which corresponds to an already-installed
		298	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		299	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		300	(i.e. C<de> or C<german>) are also common.
		301
		302	Rxvt-unicode ignores all other locale categories, and except for
		303	the encoding, ignores country or language-specific settings,
		304	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode.
		305
		306	If you want to use a specific encoding you have to make sure you start
		307	rxvt-unicode with the correct C<LC_CTYPE> category.
		308
		309	=item Can I switch locales at runtime?
		310
		311	Yes, using an escape sequence. Try sth. like this, which sets
		312	rxvt-unicode's idea of C<LC_CTYPE>.
		313
		314	printf '\e]701;%s\007' ja_JP.SJIS
		315
		316	See also the previous question.
		317
		318	Sometimes this capability is rather handy when you want to work in one
		319	locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For
		320	example, I use this script to start C<xjdic>, which first switches to a
		321	locale supported by xjdic and back later:
		322
		323	printf '\e]701;%s\007' ja_JP.SJIS
		324	xjdic -js
		325	printf '\e]701;%s\007' de_DE.UTF-8
		326
		327	=item Can I switch the fonts at runtime?
		328
		329	Yes, using an escape sequence. Try sth. like this, which has the same
		330	effect as using the C<-fn> switch, and takes effect immediately:
		331
		332	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		333
		334	This is useful if you e.g. work primarily with japanese (and prefer a
		335	japanese font), but you have to switch to chinese temporarily, where
		336	japanese fonts would only be in your way.
		337
		338	You can think of this as a kind of manual ISO-2022 switching.
		339
		340	=item Why do italic characters look as if clipped?
		341
		342	Many fonts have difficulties with italic characters and hinting. For
		343	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		344	Mono> completely fails in it's italic face. A workaround is to enable
		345	freetype autohinting, i.e. like this:
		346
		347	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		348	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		349
		350	=item My input method wants <some encoding> but I want UTF-8, what can I do?
		351
		352	You can specify separate locales for the input method and the rest of the
		353	terminal, using the resource C<imlocale>:
		354
		355	URxvt*imlocale: ja_JP.EUC-JP
		356
		357	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		358	use your input method. Please note, however, that you will not be able to
		359	input characters outside C<EUC-JP> in a normal way then, as your input
		360	method limits you.
		361
		362	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
		363
		364	Rxvt-unicode tries to obey the rule of not charging you for sth. you
		365	don't use. One thing you should try is to configure out all settings that
		366	you don't need, for example, Xft support is a resource hog by design,
		367	when used. Compiling it out ensures that no Xft font will be loaded
		368	accidentally when rxvt-unicode tries to find a font for your characters.
		369
		370	Also, many people (me included) like large windows and even larger
		371	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		372	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		373	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		374	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		375	rxvt-unicode then uses 8 bytes per screen cell.
		376
		377	=item Can I speed up Xft rendering somehow?
		378
		379	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		380	it is simply slow. If you still want Xft fonts you might try to disable
		381	antialiasing (by appending C<:antialiasing=false>), which saves lots of
		382	memory and also speeds up rendering considerably.
		383
		384	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		385
		386	Rxvt-unicode will use whatever you specify as a font. If it needs to
		387	fall back to it's default font search list it will prefer X11 core
		388	fonts, because they are small and fast, and then use Xft fonts. It has
		389	antialiasing disabled for most of them, because the author thinks they
		390	look best that way.
		391
		392	If you want antialiasing, you have to specify the fonts manually.
		393
		394	=item Mouse cut/paste suddenly no longer works.
		395
		396	Make sure that mouse reporting is actually turned off since killing
		397	some editors prematurely may leave the mouse in mouse report mode. I've
		398	heard that tcsh may use mouse reporting unless it otherwise specified. A
		399	quick check is to see if cut/paste works when the Alt or Shift keys are
		400	depressed. See @@RXVT_NAME@@(7)
		401
		402	=item What's with this bold/blink stuff?
		403
		404	If no bold colour is set via C<colorBD:>, bold will invert text using the
		405	standard foreground colour.
		406
		407	For the standard background colour, blinking will actually make the
		408	text blink when compiled with C<--enable-blinking>. with standard
		409	colours. Without C<--enable-blinking>, the blink attribute will be
		410	ignored.
		411
		412	On ANSI colours, bold/blink attributes are used to set high-intensity
		413	foreground/background colors.
		414
		415	color0-7 are the low-intensity colors.
		416
		417	color8-15 are the corresponding high-intensity colors.
		418
		419	=item I don't like the screen colors. How do I change them?
		420
		421	You can change the screen colors at run-time using F<~/.Xdefaults>
		422	resources (or as long-options).
		423
		424	Here are values that are supposed to resemble a VGA screen,
		425	including the murky brown that passes for low-intensity yellow:
		426
		427	URxvt*color0: #000000
		428	URxvt*color1: #A80000
		429	URxvt*color2: #00A800
		430	URxvt*color3: #A8A800
		431	URxvt*color4: #0000A8
		432	URxvt*color5: #A800A8
		433	URxvt*color6: #00A8A8
		434	URxvt*color7: #A8A8A8
		435
		436	URxvt*color8: #000054
		437	URxvt*color9: #FF0054
		438	URxvt*color10: #00FF54
		439	URxvt*color11: #FFFF54
		440	URxvt*color12: #0000FF
		441	URxvt*color13: #FF00FF
		442	URxvt*color14: #00FFFF
		443	URxvt*color15: #FFFFFF
		444
		445	And here is a more complete set of non-standard colors described as
		446	"pretty girly":
		447
		448	URxvt.cursorColor: #dc74d1
		449	URxvt.pointerColor: #dc74d1
		450	URxvt.background: #0e0e0e
		451	URxvt.foreground: #4ad5e1
		452	URxvt.color0: #000000
		453	URxvt.color8: #8b8f93
		454	URxvt.color1: #dc74d1
		455	URxvt.color9: #dc74d1
		456	URxvt.color2: #0eb8c7
		457	URxvt.color10: #0eb8c7
		458	URxvt.color3: #dfe37e
		459	URxvt.color11: #dfe37e
		460	URxvt.color5: #9e88f0
		461	URxvt.color13: #9e88f0
		462	URxvt.color6: #73f7ff
		463	URxvt.color14: #73f7ff
		464	URxvt.color7: #e1dddd
		465	URxvt.color15: #e1dddd
		466
		467	=item What's with the strange Backspace/Delete key behaviour?
		468
		469	Assuming that the physical Backspace key corresponds to the
		470	BackSpace keysym (not likely for Linux ... see the following
		471	question) there are two standard values that can be used for
		472	Backspace: C<^H> and C<^?>.
		473
		474	Historically, either value is correct, but rxvt-unicode adopts the debian
		475	policy of using C<^?> when unsure, because it's the one only only correct
		476	choice :).
		477
		478	Rxvt-unicode tries to inherit the current stty settings and uses the value
		479	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		480	started from a terminal (say, from a menu or by remote shell), then the
		481	system value of `erase', which corresponds to CERASE in <termios.h>, will
		482	be used (which may not be the same as your stty setting).
		483
		484	For starting a new rxvt-unicode:
		485
		486	# use Backspace = ^H
		487	$ stty erase ^H
		488	$ @@RXVT_NAME@@
		489
		490	# use Backspace = ^?
		491	$ stty erase ^?
		492	$ @@RXVT_NAME@@
		493
		494	Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).
		495
		496	For an existing rxvt-unicode:
		497
		498	# use Backspace = ^H
		499	$ stty erase ^H
		500	$ echo -n "^[[36h"
		501
		502	# use Backspace = ^?
		503	$ stty erase ^?
		504	$ echo -n "^[[36l"
		505
		506	This helps satisfy some of the Backspace discrepancies that occur, but
		507	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		508	properly reflects that.
		509
		510	The Delete key is a another casualty of the ill-defined Backspace problem.
		511	To avoid confusion between the Backspace and Delete keys, the Delete
		512	key has been assigned an escape sequence to match the vt100 for Execute
		513	(ESC[3~) and is in the supplied termcap/terminfo.
		514
		515	Some other Backspace problems:
		516
		517	some editors use termcap/terminfo,
		518	some editors (vim I'm told) expect Backspace = ^H,
		519	GNU Emacs (and Emacs-like editors) use ^H for help.
		520
		521	Perhaps someday this will all be resolved in a consistent manner.
		522
		523	=item I don't like the key-bindings. How do I change them?
		524
		525	There are some compile-time selections available via configure. Unless
		526	you have run "configure" with the C<--disable-resources> option you can
		527	use the `keysym' resource to alter the keystrings associated with keysyms.
		528
		529	Here's an example for a URxvt session started using `@@RXVT_NAME@@ -name URxvt'
		530
		531	URxvt*keysym.Home: \e[1~
		532	URxvt*keysym.End: \e[4~
		533	URxvt*keysym.C-apostrophe: \e<C-'>
		534	URxvt*keysym.C-slash: \e<C-/>
		535	URxvt*keysym.C-semicolon: \e<C-;>
		536	URxvt*keysym.C-grave: \e<C-`>
		537	URxvt*keysym.C-comma: \e<C-,>
		538	URxvt*keysym.C-period: \e<C-.>
		539	URxvt*keysym.C-0x60: \e<C-`>
		540	URxvt*keysym.C-Tab: \e<C-Tab>
		541	URxvt*keysym.C-Return: \e<C-Return>
		542	URxvt*keysym.S-Return: \e<S-Return>
		543	URxvt*keysym.S-space: \e<S-Space>
		544	URxvt*keysym.M-Up: \e<M-Up>
		545	URxvt*keysym.M-Down: \e<M-Down>
		546	URxvt*keysym.M-Left: \e<M-Left>
		547	URxvt*keysym.M-Right: \e<M-Right>
		548	URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.>
		549	URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.>
		550	URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007
		551
		552	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
		553	How do I make use of them? For example, the Sun Keyboard type 4
		554	has the following mappings that rxvt-unicode doesn't recognize.
		555
		556	KP_Insert == Insert
		557	F22 == Print
		558	F27 == Home
		559	F29 == Prior
		560	F33 == End
		561	F35 == Next
		562
		563	Rather than have rxvt-unicode try to accommodate all the various possible keyboard
		564	mappings, it is better to use `xmodmap' to remap the keys as required for
		565	your particular machine.
		566
		567	=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?
		568	I need this to decide about setting colors etc.
		569
		570	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
		571	check and see if that is set. Note that several programs, JED, slrn,
		572	Midnight Commander automatically check this variable to decide whether or
		573	not to use color.
		574
		575	=item How do I set the correct, full IP address for the DISPLAY variable?
		576
		577	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		578	insecure mode then it is possible to use the following shell script
		579	snippets to correctly set the display. If your version of rxvt-unicode
		580	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		581	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		582	regular xterm.
		583
		584	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		585	snippets:
		586
		587	# Bourne/Korn/POSIX family of shells:
		588	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		589	if [ ${TERM:-foo} = xterm ]; then
		590	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		591	echo -n '^[Z'
		592	read term_id
		593	stty icanon echo
		594	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		595	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		596	read DISPLAY # set it in our local shell
		597	fi
		598	fi
		599
		600	=item How do I compile the manual pages for myself?
		601
		602	You need to have a recent version of perl installed as F</usr/bin/perl>,
		603	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		604	the doc subdirectory and enter C<make alldoc>.
		605
		606	=item My question isn't answered here, can I ask a human?
		607
		608	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		609	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		610	interested in learning about new and exciting problems (but not FAQs :).
		611
		612	=back
		613
		614	=head1 SYNOPSIS
		615
		616	# set a new font set
		617	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
		618
		619	# change the locale and tell rxvt-unicode about it
		620	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
		621
		622	# set window title
		623	printf '\33]2;%s\007' "new window title"
		624
		625	=head1 DESCRIPTION
		626
		627	The rest of this document describes various technical aspects of
		628	B<rxvt-unicode>. First the description of supported command sequences,
		629	followed by menu and pixmap support and last by a description of all
		630	features selectable at C<configure> time.
		631
1	=head1 RXVT TECHNICAL REFERENCE	632	=head1 RXVT TECHNICAL REFERENCE
2		633
3	=head1 Definitions	634	=head1 Definitions
4		635
5	=over 4	636	=over 4
149		780
150	=item B<< C<ESC o> >>	781	=item B<< C<ESC o> >>
151		782
152	Invoke the G3 Character Set (LS3)	783	Invoke the G3 Character Set (LS3)
153		784
154	=item B<< C<ESC>(C<C> >>	785	=item B<< C<ESC> ( C> >>
155		786
156	Designate G0 Character Set (ISO 2022), see below for values of C<C>.	787	Designate G0 Character Set (ISO 2022), see below for values of C<C>.
157		788
158	=item B<< C<ESC>)C<C> >>	789	=item B<< C<ESC> ) C> >>
159		790
160	Designate G1 Character Set (ISO 2022), see below for values of C<C>.	791	Designate G1 Character Set (ISO 2022), see below for values of C<C>.
161		792
162	=item B<< C<ESC * C> >>	793	=item B<< C<ESC * C> >>
163		794
…		…
187		818
188	=back	819	=back
189		820
190	X<CSI>	821	X<CSI>
191		822
192	=head1 CSI (Code Sequence Introducer) Sequences	823	=head1 CSI (Command Sequence Introducer) Sequences
193		824
194	=over 4	825	=over 4
195		826
196	=item B<< C<ESC [ Ps @> >>	827	=item B<< C<ESC [ Ps @> >>
197		828
…		…
330	B<< C<Ps = 0> >> Clear Current Column (default)	961	B<< C<Ps = 0> >> Clear Current Column (default)
331	B<< C<Ps = 3> >> Clear All (TBC)	962	B<< C<Ps = 3> >> Clear All (TBC)
332		963
333	=end table	964	=end table
334		965
		966	=item B<< C<ESC [ Pm h> >>
		967
		968	Set Mode (SM). See B<< C<ESC [ Pm l> >> sequence for description of C<Pm>.
		969
335	=item B<< C<ESC [ Ps i> >>	970	=item B<< C<ESC [ Ps i> >>
336		971
337	Printing	972	Printing. See also the C<print-pipe> resource.
338		973
339	=begin table	974	=begin table
340		975
		976	B<< C<Ps = 0> >> print screen (MC0)
341	B<< C<Ps = 4> >> disable transparent print mode (MC4)	977	B<< C<Ps = 4> >> disable transparent print mode (MC4)
342	B<< C<Ps = 5> >> enable transparent print mode (MC5) I<unimplemented>	978	B<< C<Ps = 5> >> enable transparent print mode (MC5)
343		979
344	=end table	980	=end table
345
346	=item B<< C<ESC [ Pm h> >>
347
348	Set Mode (SM). See next sequence for description of C<Pm>.
349		981
350	=item B<< C<ESC [ Pm l> >>	982	=item B<< C<ESC [ Pm l> >>
351		983
352	Reset Mode (RM)	984	Reset Mode (RM)
353		985
…		…
360	B<< C<h> >> Insert Mode (SMIR)	992	B<< C<h> >> Insert Mode (SMIR)
361	B<< C<l> >> Replace Mode (RMIR)	993	B<< C<l> >> Replace Mode (RMIR)
362		994
363	=end table	995	=end table
364		996
365	=item B<< C<Ps = 20> >> I<unimplemented>	997	=item B<< C<Ps = 20> >> (partially implemented)
366		998
367	=begin table	999	=begin table
368		1000
369	B<< C<h> >> Automatic Newline (LNM)	1001	B<< C<h> >> Automatic Newline (LNM)
370	B<< C<h> >> Normal Linefeed (LNM)	1002	B<< C<l> >> Normal Linefeed (LNM)
371		1003
372	=end table	1004	=end table
373		1005
374	=back	1006	=back
375		1007
…		…
378	Character Attributes (SGR)	1010	Character Attributes (SGR)
379		1011
380	=begin table	1012	=begin table
381		1013
382	B<< C<Ps = 0> >> Normal (default)	1014	B<< C<Ps = 0> >> Normal (default)
383	B<< C<Ps = 1 / 22> >> On / Off Bold (bright fg)	1015	B<< C<Ps = 1 / 21> >> On / Off Bold (bright fg)
		1016	B<< C<Ps = 3 / 23> >> On / Off Italic
384	B<< C<Ps = 4 / 24> >> On / Off Underline	1017	B<< C<Ps = 4 / 24> >> On / Off Underline
385	B<< C<Ps = 5 / 25> >> On / Off Blink (bright bg)	1018	B<< C<Ps = 5 / 25> >> On / Off Slow Blink (bright bg)
		1019	B<< C<Ps = 6 / 26> >> On / Off Rapid Blink (bright bg)
386	B<< C<Ps = 7 / 27> >> On / Off Inverse	1020	B<< C<Ps = 7 / 27> >> On / Off Inverse
		1021	B<< C<Ps = 8 / 27> >> On / Off Invisible (NYI)
387	B<< C<Ps = 30 / 40> >> fg/bg Black	1022	B<< C<Ps = 30 / 40> >> fg/bg Black
388	B<< C<Ps = 31 / 41> >> fg/bg Red	1023	B<< C<Ps = 31 / 41> >> fg/bg Red
389	B<< C<Ps = 32 / 42> >> fg/bg Green	1024	B<< C<Ps = 32 / 42> >> fg/bg Green
390	B<< C<Ps = 33 / 43> >> fg/bg Yellow	1025	B<< C<Ps = 33 / 43> >> fg/bg Yellow
391	B<< C<Ps = 34 / 44> >> fg/bg Blue	1026	B<< C<Ps = 34 / 44> >> fg/bg Blue
392	B<< C<Ps = 35 / 45> >> fg/bg Magenta	1027	B<< C<Ps = 35 / 45> >> fg/bg Magenta
393	B<< C<Ps = 36 / 46> >> fg/bg Cyan	1028	B<< C<Ps = 36 / 46> >> fg/bg Cyan
		1029	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	1030	B<< C<Ps = 37 / 47> >> fg/bg White
395	B<< C<Ps = 39 / 49> >> fg/bg Default	1031	B<< C<Ps = 39 / 49> >> fg/bg Default
		1032	B<< C<Ps = 90 / 100> >> fg/bg Bright Black
		1033	B<< C<Ps = 91 / 101> >> fg/bg Bright Red
		1034	B<< C<Ps = 92 / 102> >> fg/bg Bright Green
		1035	B<< C<Ps = 93 / 103> >> fg/bg Bright Yellow
		1036	B<< C<Ps = 94 / 104> >> fg/bg Bright Blue
		1037	B<< C<Ps = 95 / 105> >> fg/bg Bright Magenta
		1038	B<< C<Ps = 96 / 106> >> fg/bg Bright Cyan
		1039	B<< C<Ps = 97 / 107> >> fg/bg Bright White
		1040	B<< C<Ps = 99 / 109> >> fg/bg Bright Default
396		1041
397	=end table	1042	=end table
398		1043
399	=item B<< C<ESC [ Ps n> >>	1044	=item B<< C<ESC [ Ps n> >>
400		1045
…		…
535	B<< C<h> >> Send Mouse X & Y on button press.	1180	B<< C<h> >> Send Mouse X & Y on button press.
536	B<< C<l> >> No mouse reporting.	1181	B<< C<l> >> No mouse reporting.
537		1182
538	=end table	1183	=end table
539		1184
540	X<Priv10>
541
542	=item B<< C<Ps = 10> >> (B<rxvt>)	1185	=item B<< C<Ps = 10> >> (B<rxvt>)
543		1186
544	=begin table	1187	=begin table
545		1188
546	B<< C<h> >> visible	1189	B<< C<h> >> menuBar visible
547	B<< C<l> >> invisible	1190	B<< C<l> >> menuBar invisible
548		1191
549	=end table	1192	=end table
550		1193
551	=item B<< C<Ps = 25> >>	1194	=item B<< C<Ps = 25> >>
552		1195
…		…
653	B<< C<h> >> Use Hilite Mouse Tracking.	1296	B<< C<h> >> Use Hilite Mouse Tracking.
654	B<< C<l> >> No mouse reporting.	1297	B<< C<l> >> No mouse reporting.
655		1298
656	=end table	1299	=end table
657		1300
658	=item B<< C<Ps = 1010> >>	1301	=item B<< C<Ps = 1010> >> (B<rxvt>)
659		1302
660	=begin table	1303	=begin table
661		1304
662	B<< C<h> >> Don't scroll to bottom on TTY output	1305	B<< C<h> >> Don't scroll to bottom on TTY output
663	B<< C<l> >> Scroll to bottom on TTY output	1306	B<< C<l> >> Scroll to bottom on TTY output
664		1307
665	=end table	1308	=end table
666		1309
667	=item B<< C<Ps = 1011> >>	1310	=item B<< C<Ps = 1011> >> (B<rxvt>)
668		1311
669	=begin table	1312	=begin table
670		1313
671	B<< C<h> >> Scroll to bottom when a key is pressed	1314	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	1315	B<< C<l> >> Don't scroll to bottom when a key is pressed
…		…
686		1329
687	=begin table	1330	=begin table
688		1331
689	B<< C<h> >> Save cursor position	1332	B<< C<h> >> Save cursor position
690	B<< C<l> >> Restore cursor position	1333	B<< C<l> >> Restore cursor position
		1334
		1335	=end table
		1336
		1337	=item B<< C<Ps = 1049> >>
		1338
		1339	=begin table
		1340
		1341	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
		1342	B<< C<l> >> Use Normal Screen Buffer
691		1343
692	=end table	1344	=end table
693		1345
694	=back	1346	=back
695		1347
…		…
726	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1378	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>	1379	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>
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> >>	1380	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> >>	1381	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)	1382	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)
731	B<< C<Ps = 702> >> find font for character, used for debugging (@@RXVT_NAME@@ extension)
732	B<< C<Ps = 703> >> command B<< C<Pt> >> I<rxvt compile-time option> (@@RXVT_NAME@@ extension)	1383	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)
		1384	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
		1385	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>
		1386	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
		1387	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
		1388	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
		1389	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
733		1390
734	=end table	1391	=end table
735		1392
736	=back	1393	=back
737		1394
…		…
1390	XK_KP_8 8 ESC O x	2047	XK_KP_8 8 ESC O x
1391	XK_KP_9 9 ESC O y	2048	XK_KP_9 9 ESC O y
1392		2049
1393	=end table	2050	=end table
1394		2051
		2052	=head1 CONFIGURE OPTIONS
		2053
		2054	General hint: if you get compile errors, then likely your configuration
		2055	hasn't been tested well. Either try with --enable-everything or use the
		2056	./reconf script as a base for experiments. ./reconf is used by myself,
		2057	so it should generally be a working config. Of course, you should always
		2058	report when a combination doesn't work, so it can be fixed. Marc Lehmann
		2059	<rxvt@schmorp.de>.
		2060
		2061	=over 4
		2062
		2063	=item --enable-everything
		2064
		2065	Add support for all non-multichoice options listed in "./configure
		2066	--help". Note that unlike other enable options this is order dependant.
		2067	You can specify this and then disable options which this enables by
		2068	I<following> this with the appropriate commands.
		2069
		2070	=item --enable-xft
		2071
		2072	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
		2073	slower and require lots of memory, but as long as you don't use them, you
		2074	don't pay for them.
		2075
		2076	=item --enable-font-styles
		2077
		2078	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
		2079	styles. The fonts can be set manually or automatically.
		2080
		2081	=item --with-codesets=NAME,...
		2082
		2083	Compile in support for additional codeset (encoding) groups (eu, vn are
		2084	always compiled in, which includes most 8-bit character sets). These
		2085	codeset tables are currently only used for driving X11 core fonts, they
		2086	are not required for Xft fonts. Compiling them in will make your binary
		2087	bigger (together about 700kB), but it doesn't increase memory usage unless
		2088	you use an X11 font requiring one of these encodings.
		2089
		2090	=begin table
		2091
		2092	all all available codeset groups
		2093	zh common chinese encodings
		2094	zh_ext rarely used but very big chinese encodigs
		2095	jp common japanese encodings
		2096	jp_ext rarely used but big japanese encodings
		2097	kr korean encodings
		2098
		2099	=end table
		2100
		2101	=item --enable-xim
		2102
		2103	Add support for XIM (X Input Method) protocol. This allows using
		2104	alternative input methods (e.g. kinput2) and will also correctly
		2105	set up the input for people using dead keys or compose keys.
		2106
		2107	=item --enable-unicode3
		2108
		2109	Enable direct support for displaying unicode codepoints above
		2110	65535 (the basic multilingual page). This increases storage
		2111	requirements per character from 2 to 4 bytes. X11 fonts do not yet
		2112	support these extra characters, but Xft does.
		2113
		2114	Please note that rxvt-unicode can store unicode code points >65535
		2115	even without this flag, but the number of such characters is
		2116	limited to a view thousand (shared with combining characters,
		2117	see next switch), and right now rxvt-unicode cannot display them
		2118	(input/output and cut&paste still work, though).
		2119
		2120	=item --enable-combining
		2121
		2122	Enable automatic composition of combining characters into
		2123	composite characters. This is required for proper viewing of text
		2124	where accents are encoded as seperate unicode characters. This is
		2125	done by using precomposited characters when available or creating
		2126	new pseudo-characters when no precomposed form exists.
		2127
		2128	Without --enable-unicode3, the number of additional precomposed
		2129	characters is rather limited (2048, if this is full, rxvt will use the
		2130	private use area, extending the number of combinations to 8448). With
		2131	--enable-unicode3, no practical limit exists. This will also enable
		2132	storage of characters >65535.
		2133
		2134	The combining table also contains entries for arabic presentation forms,
		2135	but these are not currently used. Bug me if you want these to be used.
		2136
		2137	=item --enable-fallback(=CLASS)
		2138
		2139	When reading resource settings, also read settings for class CLASS
		2140	(default: Rxvt). To disable resource fallback use --disable-fallback.
		2141
		2142	=item --with-res-name=NAME
		2143
		2144	Use the given name (default: urxvt) as default application name when
		2145	reading resources. Specify --with-res-name=rxvt to replace rxvt.
		2146
		2147	=item --with-res-class=CLASS
		2148
		2149	Use the given class (default: URxvt) as default application class
		2150	when reading resources. Specify --with-res-class=Rxvt to replace
		2151	rxvt.
		2152
		2153	=item --enable-utmp
		2154
		2155	Write user and tty to utmp file (used by programs like F<w>) at
		2156	start of rxvt execution and delete information when rxvt exits.
		2157
		2158	=item --enable-wtmp
		2159
		2160	Write user and tty to wtmp file (used by programs like F<last>) at
		2161	start of rxvt execution and write logout when rxvt exits. This
		2162	option requires --enable-utmp to also be specified.
		2163
		2164	=item --enable-lastlog
		2165
		2166	Write user and tty to lastlog file (used by programs like
		2167	F<lastlogin>) at start of rxvt execution. This option requires
		2168	--enable-utmp to also be specified.
		2169
		2170	=item --enable-xpm-background
		2171
		2172	Add support for XPM background pixmaps.
		2173
		2174	=item --enable-transparency
		2175
		2176	Add support for inheriting parent backgrounds thus giving a fake
		2177	transparency to the term.
		2178
		2179	=item --enable-fading
		2180
		2181	Add support for fading the text when focus is lost.
		2182
		2183	=item --enable-tinting
		2184
		2185	Add support for tinting of transparent backgrounds.
		2186
		2187	=item --enable-menubar
		2188
		2189	Add support for our menu bar system (this interacts badly with
		2190	dynamic locale switching currently).
		2191
		2192	=item --enable-rxvt-scroll
		2193
		2194	Add support for the original rxvt scrollbar.
		2195
		2196	=item --enable-next-scroll
		2197
		2198	Add support for a NeXT-like scrollbar.
		2199
		2200	=item --enable-xterm-scroll
		2201
		2202	Add support for an Xterm-like scrollbar.
		2203
		2204	=item --enable-plain-scroll
		2205
		2206	Add support for a very unobtrusive, plain-looking scrollbar that
		2207	is the favourite of the rxvt-unicode author, having used it for
		2208	many years.
		2209
		2210	=item --enable-half-shadow
		2211
		2212	Make shadows on the scrollbar only half the normal width & height.
		2213	only applicable to rxvt scrollbars.
		2214
		2215	=item --enable-ttygid
		2216
		2217	Change tty device setting to group "tty" - only use this if
		2218	your system uses this type of security.
		2219
		2220	=item --disable-backspace-key
		2221
		2222	Disable any handling of the backspace key by us - let the X server
		2223	do it.
		2224
		2225	=item --disable-delete-key
		2226
		2227	Disable any handling of the delete key by us - let the X server
		2228	do it.
		2229
		2230	=item --disable-resources
		2231
		2232	Remove all resources checking.
		2233
		2234	=item --enable-xgetdefault
		2235
		2236	Make resources checking via XGetDefault() instead of our small
		2237	version which only checks ~/.Xdefaults, or if that doesn't exist
		2238	then ~/.Xresources.
		2239
		2240	=item --enable-strings
		2241
		2242	Add support for our possibly faster memset() function and other
		2243	various routines, overriding your system's versions which may
		2244	have been hand-crafted in assembly or may require extra libraries
		2245	to link in. (this breaks ANSI-C rules and has problems on many
		2246	GNU/Linux systems).
		2247
		2248	=item --disable-swapscreen
		2249
		2250	Remove support for swap screen.
		2251
		2252	=item --enable-frills
		2253
		2254	Add support for many small features that are not essential but nice to
		2255	have. Normally you want this, but for very small binaries you may want to
		2256	disable this.
		2257
		2258	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
		2259	in combination with other switches) is:
		2260
		2261	MWM-hints
		2262	seperate underline colour
		2263	settable border widths and borderless switch
		2264	settable extra linespacing
		2265	extra window properties (e.g. UTF-8 window names and PID)
		2266	iso-14755-2 and -3, and visual feedback
		2267	backindex and forwardindex escape sequence
		2268	window op and locale change escape sequences
		2269	tripleclickwords
		2270	settable insecure mode
		2271
		2272	=item --enable-iso14755
		2273
		2274	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
		2275	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
		2276	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
		2277	this switch.
		2278
		2279	=item --enable-keepscrolling
		2280
		2281	Add support for continual scrolling of the display when you hold
		2282	the mouse button down on a scrollbar arrow.
		2283
		2284	=item --enable-mousewheel
		2285
		2286	Add support for scrolling via mouse wheel or buttons 4 & 5.
		2287
		2288	=item --enable-slipwheeling
		2289
		2290	Add support for continual scrolling (using the mouse wheel as an
		2291	accelerator) while the control key is held down. This option
		2292	requires --enable-mousewheel to also be specified.
		2293
		2294	=item --disable-new-selection
		2295
		2296	Remove support for mouse selection style like that of xterm.
		2297
		2298	=item --enable-dmalloc
		2299
		2300	Use Gray Watson's malloc - which is good for debugging See
		2301	http://www.letters.com/dmalloc/ for details If you use either this or the
		2302	next option, you may need to edit src/Makefile after compiling to point
		2303	DINCLUDE and DLIB to the right places.
		2304
		2305	You can only use either this option and the following (should
		2306	you use either) .
		2307
		2308	=item --enable-dlmalloc
		2309
		2310	Use Doug Lea's malloc - which is good for a production version
		2311	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
		2312
		2313	=item --enable-smart-resize
		2314
		2315	Add smart growth/shrink behaviour when changing font size via from hot
		2316	keys. This should keep in a fixed position the rxvt corner which is
		2317	closest to a corner of the screen.
		2318
		2319	=item --enable-cursor-blink
		2320
		2321	Add support for a blinking cursor.
		2322
		2323	=item --enable-pointer-blank
		2324
		2325	Add support to have the pointer disappear when typing or inactive.
		2326
		2327	=item --with-name=NAME
		2328
		2329	Set the basename for the installed binaries (default: C<urxvt>, resulting
		2330	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
		2331	C<rxvt>.
		2332
		2333	=item --with-term=NAME
		2334
		2335	Change the environmental variable for the terminal to NAME (default
		2336	C<rxvt-unicode>)
		2337
		2338	=item --with-terminfo=PATH
		2339
		2340	Change the environmental variable for the path to the terminfo tree to
		2341	PATH.
		2342
		2343	=item --with-x
		2344
		2345	Use the X Window System (pretty much default, eh?).
		2346
		2347	=item --with-xpm-includes=DIR
		2348
		2349	Look for the XPM includes in DIR.
		2350
		2351	=item --with-xpm-library=DIR
		2352
		2353	Look for the XPM library in DIR.
		2354
		2355	=item --with-xpm
		2356
		2357	Not needed - define via --enable-xpm-background.
		2358
		2359	=back
		2360
1395	=head1 AUTHORS	2361	=head1 AUTHORS
1396		2362
1397	Marc Lehmann <rxvt@schmorp.de> converted this document to pod and	2363	Marc Lehmann <rxvt@schmorp.de> converted this document to pod and
1398	reworked it from the original Rxvt documentation, which was done by Geoff	2364	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	2365	Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other

Diff Legend

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

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.33 by root, Sun Jan 16 18:48:04 2005 UTC

Diff Legend

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.33 by root, Sun Jan 16 18:48:04 2005 UTC