ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.55 by root, Sun Jun 26 20:11:22 2005 UTC vs.
Revision 1.151 by sasha, Thu Nov 15 18:40:10 2007 UTC

…		…
16	=head1 DESCRIPTION	16	=head1 DESCRIPTION
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is	21	The newest version of this document is also available on the World Wide Web at
22	also available on the World Wide Web at
23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://cvs.schmorp.de/browse/rxvt-unicode/doc/rxvt.7.html>.
24		23
25	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		25
27	=over 4
28		26
		27	=head2 Meta, Features & Commandline Issues
		28
		29	=head3 My question isn't answered here, can I ask a human?
		30
		31	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		32	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		33	interested in learning about new and exciting problems (but not FAQs :).
		34
		35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
		36
		37	Beginning with version 7.3, there is a perl extension that implements a
		38	simple tabbed terminal. It is installed by default, so any of these should
		39	give you tabs:
		40
		41	@@URXVT_NAME@@ -pe tabbed
		42
		43	URxvt.perl-ext-common: default,tabbed
		44
		45	It will also work fine with tabbing functionality of many window managers
		46	or similar tabbing programs, and its embedding-features allow it to be
		47	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		48	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		49	(murxvt) terminal as an example embedding application.
		50
29	=item How do I know which rxvt-unicode version I'm using?	51	=head3 How do I know which rxvt-unicode version I'm using?
30		52
31	The version number is displayed with the usage (-h). Also the escape	53	The version number is displayed with the usage (-h). Also the escape
32	sequence C<ESC [ 8 n> sets the window title to the version number.	54	sequence C<ESC [ 8 n> sets the window title to the version number. When
		55	using the @@URXVT_NAME@@c client, the version displayed is that of the
		56	daemon.
33		57
34	=item I am using Debian GNU/Linux and have a problem...	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
35		59
36	The Debian GNU/Linux package of rxvt-unicode contains large patches that	60	Rxvt-unicode tries to obey the rule of not charging you for something you
37	considerably change the behaviour of rxvt-unicode. Before reporting a	61	don't use. One thing you should try is to configure out all settings that
38	bug to the original rxvt-unicode author please download and install the	62	you don't need, for example, Xft support is a resource hog by design,
39	genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to	63	when used. Compiling it out ensures that no Xft font will be loaded
40	reproduce the problem. If you cannot, chances are that the problems are	64	accidentally when rxvt-unicode tries to find a font for your characters.
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		65
44	For other problems that also affect the Debian package, you can and	66	Also, many people (me included) like large windows and even larger
45	probably should use the Debian BTS, too, because, after all, it's also a	67	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
46	bug in the Debian version and it serves as a reminder for other users that	68	6 bytes per screen cell. For a 160x?? window this amounts to almost a
47	might encounter the same issue.	69	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		70	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		71	rxvt-unicode then uses 8 bytes per screen cell.
48		72
		73	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
		74
		75	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
		76	display, create the listening socket and then fork.
		77
		78	=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c?
		79
		80	If you want to start @@URXVT_NAME@@d automatically whenever you run
		81	@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
		82
		83	#!/bin/sh
		84	@@URXVT_NAME@@c "$@"
		85	if [ $? -eq 2 ]; then
		86	@@URXVT_NAME@@d -q -o -f
		87	@@URXVT_NAME@@c "$@"
		88	fi
		89
		90	This tries to create a new terminal, and if fails with exit status 2,
		91	meaning it couldn't connect to the daemon, it will start the daemon and
		92	re-run the command. Subsequent invocations of the script will re-use the
		93	existing daemon.
		94
		95	=head3 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
		96
		97	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
		98	so you can check and see if that is set. Note that several programs, JED,
		99	slrn, Midnight Commander automatically check this variable to decide
		100	whether or not to use color.
		101
		102	=head3 How do I set the correct, full IP address for the DISPLAY variable?
		103
		104	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		105	insecure mode then it is possible to use the following shell script
		106	snippets to correctly set the display. If your version of rxvt-unicode
		107	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		108	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		109	regular xterm.
		110
		111	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		112	snippets:
		113
		114	# Bourne/Korn/POSIX family of shells:
		115	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		116	if [ ${TERM:-foo} = xterm ]; then
		117	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		118	echo -n '^[Z'
		119	read term_id
		120	stty icanon echo
		121	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		122	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		123	read DISPLAY # set it in our local shell
		124	fi
		125	fi
		126
		127	=head3 How do I compile the manual pages on my own?
		128
		129	You need to have a recent version of perl installed as F</usr/bin/perl>,
		130	one that comes with F<pod2man>, F<pod2text> and F<pod2xhtml> (from
		131	F<Pod::Xhtml>). Then go to the doc subdirectory and enter C<make alldoc>.
		132
		133	=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
		134
		135	I often get asked about this, and I think, no, they didn't cause extra
		136	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
		137	that the urxvt binary is larger (due to some encoding tables always being
		138	compiled in), but it actually uses less memory (RSS) after startup. Even
		139	with C<--disable-everything>, this comparison is a bit unfair, as many
		140	features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
		141	already in use in this mode.
		142
		143	text data bss drs rss filename
		144	98398 1664 24 15695 1824 rxvt --disable-everything
		145	188985 9048 66616 18222 1788 urxvt --disable-everything
		146
		147	When you C<--enable-everything> (which I<is> unfair, as this involves xft
		148	and full locale/XIM support which are quite bloaty inside libX11 and my
		149	libc), the two diverge, but not unreasonably so.
		150
		151	text data bss drs rss filename
		152	163431 2152 24 20123 2060 rxvt --enable-everything
		153	1035683 49680 66648 29096 3680 urxvt --enable-everything
		154
		155	The very large size of the text section is explained by the east-asian
		156	encoding tables, which, if unused, take up disk space but nothing else
		157	and can be compiled out unless you rely on X11 core fonts that use those
		158	encodings. The BSS size comes from the 64k emergency buffer that my c++
		159	compiler allocates (but of course doesn't use unless you are out of
		160	memory). Also, using an xft font instead of a core font immediately adds a
		161	few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
		162	not used.
		163
		164	Of course, due to every character using two or four bytes instead of one,
		165	a large scrollback buffer will ultimately make rxvt-unicode use more
		166	memory.
		167
		168	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
		169	still fares rather well. And compared to some monsters like gnome-terminal
		170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
		171	43180k in daemons that stay around after exit, plus half a minute of
		172	startup time, including the hundreds of warnings it spits out), it fares
		173	extremely well *g*.
		174
		175	=head3 Why C++, isn't that unportable/bloated/uncool?
		176
		177	Is this a question? :) It comes up very often. The simple answer is: I had
		178	to write it, and C++ allowed me to write and maintain it in a fraction
		179	of the time and effort (which is a scarce resource for me). Put even
		180	shorter: It simply wouldn't exist without C++.
		181
		182	My personal stance on this is that C++ is less portable than C, but in
		183	the case of rxvt-unicode this hardly matters, as its portability limits
		184	are defined by things like X11, pseudo terminals, locale support and unix
		185	domain sockets, which are all less portable than C++ itself.
		186
		187	Regarding the bloat, see the above question: It's easy to write programs
		188	in C that use gobs of memory, an certainly possible to write programs in
		189	C++ that don't. C++ also often comes with large libraries, but this is
		190	not necessarily the case with GCC. Here is what rxvt links against on my
		191	system with a minimal config:
		192
		193	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		194	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
		195	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
		196	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		197
		198	And here is rxvt-unicode:
		199
		200	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
		201	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
		202	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
		203	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
		204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
		205
		206	No large bloated libraries (of course, none were linked in statically),
		207	except maybe libX11 :)
		208
		209
		210	=head2 Rendering, Font & Look and Feel Issues
		211
		212	=head3 I can't get transparency working, what am I doing wrong?
		213
		214	First of all, please address all transparency related issues to Sasha Vasko at
		215	sasha@aftercode.net and do not bug the author about it. Also, if you can't
		216	get it working consider it a rite of passage: ... and you failed.
		217
		218	Here are four ways to get transparency. B<Do> read the manpage and option
		219	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
		220
		221	1. Use transparent mode:
		222
		223	Esetroot wallpaper.jpg
		224	@@URXVT_NAME@@ -tr -tint red -sh 40
		225
		226	That works. If you think it doesn't, you lack transparency and tinting
		227	support, or you are unable to read.
		228
		229	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		230	to use effects other than tinting and shading: Just shade/tint/whatever
		231	your picture with gimp or any other tool:
		232
		233	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
		234	@@URXVT_NAME@@ -pixmap "background.jpg;:root"
		235
		236	That works. If you think it doesn't, you lack AfterImage support, or you
		237	are unable to read.
		238
		239	3. Use an ARGB visual:
		240
		241	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		242
		243	This requires XFT support, and the support of your X-server. If that
		244	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		245	there yet, no matter what they claim. Rxvt-Unicode contains the necessary
		246	bugfixes and workarounds for Xft and Xlib to make it work, but that
		247	doesn't mean that your WM has the required kludges in place.
		248
		249	4. Use xcompmgr and let it do the job:
		250
		251	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		252	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		253
		254	Then click on a window you want to make transparent. Replace C<0xc0000000>
		255	by other values to change the degree of opacity. If it doesn't work and
		256	your server crashes, you got to keep the pieces.
		257
		258	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		259
		260	Most fonts were not designed for terminal use, which means that character
		261	size varies a lot. A font that is otherwise fine for terminal use might
		262	contain some characters that are simply too wide. Rxvt-unicode will avoid
		263	these characters. For characters that are just "a bit" too wide a special
		264	"careful" rendering mode is used that redraws adjacent characters.
		265
		266	All of this requires that fonts do not lie about character sizes,
		267	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		268	box, and rxvt-unicode has no way of detecting this (the correct way is to
		269	ask for the character bounding box, which unfortunately is wrong in these
		270	cases).
		271
		272	It's not clear (to me at least), whether this is a bug in Xft, freetype,
		273	or the respective font. If you encounter this problem you might try using
		274	the C<-lsp> option to give the font more height. If that doesn't work, you
		275	might be forced to use a different font.
		276
		277	All of this is not a problem when using X11 core fonts, as their bounding
		278	box data is correct.
		279
		280	=head3 How can I keep rxvt-unicode from using reverse video so much?
		281
		282	First of all, make sure you are running with the right terminal settings
		283	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		284	make sure you have specified colours for italic and bold, as otherwise
		285	rxvt-unicode might use reverse video to simulate the effect:
		286
		287	URxvt.colorBD: white
		288	URxvt.colorIT: green
		289
		290	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		291
		292	For some unexplainable reason, some rare programs assume a very weird
		293	colour palette when confronted with a terminal with more than the standard
		294	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		295	these programs not to assume non-ISO colours without very good reasons.
		296
		297	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		298	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		299	fix colours but keep you from using other rxvt-unicode features.
		300
		301	=head3 Can I switch the fonts at runtime?
		302
		303	Yes, using an escape sequence. Try something like this, which has the same
		304	effect as using the C<-fn> switch, and takes effect immediately:
		305
		306	printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
		307
		308	This is useful if you e.g. work primarily with japanese (and prefer a
		309	japanese font), but you have to switch to chinese temporarily, where
		310	japanese fonts would only be in your way.
		311
		312	You can think of this as a kind of manual ISO-2022 switching.
		313
		314	=head3 Why do italic characters look as if clipped?
		315
		316	Many fonts have difficulties with italic characters and hinting. For
		317	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		318	Mono> completely fails in its italic face. A workaround might be to
		319	enable freetype autohinting, i.e. like this:
		320
		321	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		322	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		323
		324	=head3 Can I speed up Xft rendering somehow?
		325
		326	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		327	it is simply slow. If you still want Xft fonts you might try to disable
		328	antialiasing (by appending C<:antialias=false>), which saves lots of
		329	memory and also speeds up rendering considerably.
		330
		331	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		332
		333	Rxvt-unicode will use whatever you specify as a font. If it needs to
		334	fall back to its default font search list it will prefer X11 core
		335	fonts, because they are small and fast, and then use Xft fonts. It has
		336	antialiasing disabled for most of them, because the author thinks they
		337	look best that way.
		338
		339	If you want antialiasing, you have to specify the fonts manually.
		340
		341	=head3 What's with this bold/blink stuff?
		342
		343	If no bold colour is set via C<colorBD:>, bold will invert text using the
		344	standard foreground colour.
		345
		346	For the standard background colour, blinking will actually make the
		347	text blink when compiled with C<--enable-blinking>. with standard
		348	colours. Without C<--enable-blinking>, the blink attribute will be
		349	ignored.
		350
		351	On ANSI colours, bold/blink attributes are used to set high-intensity
		352	foreground/background colors.
		353
		354	color0-7 are the low-intensity colors.
		355
		356	color8-15 are the corresponding high-intensity colors.
		357
		358	=head3 I don't like the screen colors. How do I change them?
		359
		360	You can change the screen colors at run-time using F<~/.Xdefaults>
		361	resources (or as long-options).
		362
		363	Here are values that are supposed to resemble a VGA screen,
		364	including the murky brown that passes for low-intensity yellow:
		365
		366	URxvt.color0: #000000
		367	URxvt.color1: #A80000
		368	URxvt.color2: #00A800
		369	URxvt.color3: #A8A800
		370	URxvt.color4: #0000A8
		371	URxvt.color5: #A800A8
		372	URxvt.color6: #00A8A8
		373	URxvt.color7: #A8A8A8
		374
		375	URxvt.color8: #000054
		376	URxvt.color9: #FF0054
		377	URxvt.color10: #00FF54
		378	URxvt.color11: #FFFF54
		379	URxvt.color12: #0000FF
		380	URxvt.color13: #FF00FF
		381	URxvt.color14: #00FFFF
		382	URxvt.color15: #FFFFFF
		383
		384	And here is a more complete set of non-standard colors.
		385
		386	URxvt.cursorColor: #dc74d1
		387	URxvt.pointerColor: #dc74d1
		388	URxvt.background: #0e0e0e
		389	URxvt.foreground: #4ad5e1
		390	URxvt.color0: #000000
		391	URxvt.color8: #8b8f93
		392	URxvt.color1: #dc74d1
		393	URxvt.color9: #dc74d1
		394	URxvt.color2: #0eb8c7
		395	URxvt.color10: #0eb8c7
		396	URxvt.color3: #dfe37e
		397	URxvt.color11: #dfe37e
		398	URxvt.color5: #9e88f0
		399	URxvt.color13: #9e88f0
		400	URxvt.color6: #73f7ff
		401	URxvt.color14: #73f7ff
		402	URxvt.color7: #e1dddd
		403	URxvt.color15: #e1dddd
		404
		405	They have been described (not by me) as "pretty girly".
		406
		407	=head3 Why do some characters look so much different than others?
		408
		409	See next entry.
		410
		411	=head3 How does rxvt-unicode choose fonts?
		412
		413	Most fonts do not contain the full range of Unicode, which is
		414	fine. Chances are that the font you (or the admin/package maintainer of
		415	your system/os) have specified does not cover all the characters you want
		416	to display.
		417
		418	B<rxvt-unicode> makes a best-effort try at finding a replacement
		419	font. Often the result is fine, but sometimes the chosen font looks
		420	bad/ugly/wrong. Some fonts have totally strange characters that don't
		421	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		422	intelligence to detect that a specific glyph is wrong: it has to believe
		423	the font that the characters it claims to contain indeed look correct.
		424
		425	In that case, select a font of your taste and add it to the font list,
		426	e.g.:
		427
		428	@@URXVT_NAME@@ -fn basefont,font2,font3...
		429
		430	When rxvt-unicode sees a character, it will first look at the base
		431	font. If the base font does not contain the character, it will go to the
		432	next font, and so on. Specifying your own fonts will also speed up this
		433	search and use less resources within rxvt-unicode and the X-server.
		434
		435	The only limitation is that none of the fonts may be larger than the base
		436	font, as the base font defines the terminal character cell size, which
		437	must be the same due to the way terminals work.
		438
		439	=head3 Why do some chinese characters look so different than others?
		440
		441	This is because there is a difference between script and language --
		442	rxvt-unicode does not know which language the text that is output is,
		443	as it only knows the unicode character codes. If rxvt-unicode first
		444	sees a japanese/chinese character, it might choose a japanese font for
		445	display. Subsequent japanese characters will use that font. Now, many
		446	chinese characters aren't represented in japanese fonts, so when the first
		447	non-japanese character comes up, rxvt-unicode will look for a chinese font
		448	-- unfortunately at this point, it will still use the japanese font for
		449	chinese characters that are also in the japanese font.
		450
		451	The workaround is easy: just tag a chinese font at the end of your font
		452	list (see the previous question). The key is to view the font list as
		453	a preference list: If you expect more japanese, list a japanese font
		454	first. If you expect more chinese, put a chinese font first.
		455
		456	In the future it might be possible to switch language preferences at
		457	runtime (the internal data structure has no problem with using different
		458	fonts for the same character at the same time, but no interface for this
		459	has been designed yet).
		460
		461	Until then, you might get away with switching fonts at runtime (see L<Can
		462	I switch the fonts at runtime?> later in this document).
		463
		464	=head3 How can I make mplayer display video correctly?
		465
		466	We are working on it, in the meantime, as a workaround, use something like:
		467
		468	@@URXVT_NAME@@ -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		469
		470
		471	=head2 Keyboard, Mouse & User Interaction
		472
		473	=head3 The new selection selects pieces that are too big, how can I select single words?
		474
		475	If you want to select e.g. alphanumeric words, you can use the following
		476	setting:
		477
		478	URxvt.selection.pattern-0: ([[:word:]]+)
		479
		480	If you click more than twice, the selection will be extended
		481	more and more.
		482
		483	To get a selection that is very similar to the old code, try this pattern:
		484
		485	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		486
		487	Please also note that the I<LeftClick Shift-LeftClik> combination also
		488	selects words like the old code.
		489
		490	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		491
		492	You can disable the perl extension completely by setting the
		493	B<perl-ext-common> resource to the empty string, which also keeps
		494	rxvt-unicode from initialising perl, saving memory.
		495
		496	If you only want to disable specific features, you first have to
		497	identify which perl extension is responsible. For this, read the section
		498	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		499	example, to disable the B<selection-popup> and B<option-popup>, specify
		500	this B<perl-ext-common> resource:
		501
		502	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		503
		504	This will keep the default extensions, but disable the two popup
		505	extensions. Some extensions can also be configured, for example,
		506	scrollback search mode is triggered by B<M-s>. You can move it to any
		507	other combination either by setting the B<searchable-scrollback> resource:
		508
		509	URxvt.searchable-scrollback: CM-s
		510
		511	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		512
		513	See next entry.
		514
		515	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		516
		517	These are caused by the C<readline> perl extension. Under normal
		518	circumstances, it will move your cursor around when you click into the
		519	line that contains it. It tries hard not to do this at the wrong moment,
		520	but when running a program that doesn't parse cursor movements or in some
		521	cases during rlogin sessions, it fails to detect this properly.
		522
		523	You can permanently switch this feature off by disabling the C<readline>
		524	extension:
		525
		526	URxvt.perl-ext-common: default,-readline
		527
		528	=head3 My numerical keypad acts weird and generates differing output?
		529
		530	Some Debian GNUL/Linux users seem to have this problem, although no
		531	specific details were reported so far. It is possible that this is caused
		532	by the wrong C<TERM> setting, although the details of whether and how
		533	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		534	keymap. See the answer to the previous question, and please report if that
		535	helped.
		536
		537	=head3 My Compose (Multi_key) key is no longer working.
		538
		539	The most common causes for this are that either your locale is not set
		540	correctly, or you specified a B<preeditStyle> that is not supported by
		541	your input method. For example, if you specified B<OverTheSpot> and
		542	your input method (e.g. the default input method handling Compose keys)
		543	does not support this (for instance because it is not visual), then
		544	rxvt-unicode will continue without an input method.
		545
		546	In this case either do not specify a B<preeditStyle> or specify more than
		547	one pre-edit style, such as B<OverTheSpot,Root,None>.
		548
		549	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		550
		551	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		552	international keyboards) or simply use ISO 14755 support to your
		553	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		554	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		555	character and so on.
		556
		557	=head3 Mouse cut/paste suddenly no longer works.
		558
		559	Make sure that mouse reporting is actually turned off since killing
		560	some editors prematurely may leave the mouse in mouse report mode. I've
		561	heard that tcsh may use mouse reporting unless it otherwise specified. A
		562	quick check is to see if cut/paste works when the Alt or Shift keys are
		563	depressed.
		564
		565	=head3 What's with the strange Backspace/Delete key behaviour?
		566
		567	Assuming that the physical Backspace key corresponds to the
		568	Backspace keysym (not likely for Linux ... see the following
		569	question) there are two standard values that can be used for
		570	Backspace: C<^H> and C<^?>.
		571
		572	Historically, either value is correct, but rxvt-unicode adopts the debian
		573	policy of using C<^?> when unsure, because it's the one and only correct
		574	choice :).
		575
		576	Rxvt-unicode tries to inherit the current stty settings and uses the value
		577	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		578	started from a terminal (say, from a menu or by remote shell), then the
		579	system value of `erase', which corresponds to CERASE in <termios.h>, will
		580	be used (which may not be the same as your stty setting).
		581
		582	For starting a new rxvt-unicode:
		583
		584	# use Backspace = ^H
		585	$ stty erase ^H
		586	$ @@URXVT_NAME@@
		587
		588	# use Backspace = ^?
		589	$ stty erase ^?
		590	$ @@URXVT_NAME@@
		591
		592	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		593
		594	For an existing rxvt-unicode:
		595
		596	# use Backspace = ^H
		597	$ stty erase ^H
		598	$ echo -n "^[[36h"
		599
		600	# use Backspace = ^?
		601	$ stty erase ^?
		602	$ echo -n "^[[36l"
		603
		604	This helps satisfy some of the Backspace discrepancies that occur, but
		605	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		606	properly reflects that.
		607
		608	The Delete key is a another casualty of the ill-defined Backspace problem.
		609	To avoid confusion between the Backspace and Delete keys, the Delete
		610	key has been assigned an escape sequence to match the vt100 for Execute
		611	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		612
		613	Some other Backspace problems:
		614
		615	some editors use termcap/terminfo,
		616	some editors (vim I'm told) expect Backspace = ^H,
		617	GNU Emacs (and Emacs-like editors) use ^H for help.
		618
		619	Perhaps someday this will all be resolved in a consistent manner.
		620
		621	=head3 I don't like the key-bindings. How do I change them?
		622
		623	There are some compile-time selections available via configure. Unless
		624	you have run "configure" with the C<--disable-resources> option you can
		625	use the `keysym' resource to alter the keystrings associated with keysyms.
		626
		627	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		628
		629	URxvt.keysym.Home: \033[1~
		630	URxvt.keysym.End: \033[4~
		631	URxvt.keysym.C-apostrophe: \033<C-'>
		632	URxvt.keysym.C-slash: \033<C-/>
		633	URxvt.keysym.C-semicolon: \033<C-;>
		634	URxvt.keysym.C-grave: \033<C-`>
		635	URxvt.keysym.C-comma: \033<C-,>
		636	URxvt.keysym.C-period: \033<C-.>
		637	URxvt.keysym.C-0x60: \033<C-`>
		638	URxvt.keysym.C-Tab: \033<C-Tab>
		639	URxvt.keysym.C-Return: \033<C-Return>
		640	URxvt.keysym.S-Return: \033<S-Return>
		641	URxvt.keysym.S-space: \033<S-Space>
		642	URxvt.keysym.M-Up: \033<M-Up>
		643	URxvt.keysym.M-Down: \033<M-Down>
		644	URxvt.keysym.M-Left: \033<M-Left>
		645	URxvt.keysym.M-Right: \033<M-Right>
		646	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		647	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		648	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		649
		650	See some more examples in the documentation for the B<keysym> resource.
		651
		652	=head3 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map
		653
		654	KP_Insert == Insert
		655	F22 == Print
		656	F27 == Home
		657	F29 == Prior
		658	F33 == End
		659	F35 == Next
		660
		661	Rather than have rxvt-unicode try to accommodate all the various possible
		662	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		663	required for your particular machine.
		664
		665
		666	=head2 Terminal Configuration
		667
		668	=head3 Can I see a typical configuration?
		669
		670	The default configuration tries to be xterm-like, which I don't like that
		671	much, but it's least surprise to regular users.
		672
		673	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		674	time into customising your terminal. To get you started, here is the
		675	author's .Xdefaults entries, with comments on what they do. It's certainly
		676	not I<typical>, but what's typical...
		677
		678	URxvt.cutchars: "()*,<>[]{}|'
		679	URxvt.print-pipe: cat >/tmp/xxx
		680
		681	These are just for testing stuff.
		682
		683	URxvt.imLocale: ja_JP.UTF-8
		684	URxvt.preeditType: OnTheSpot,None
		685
		686	This tells rxvt-unicode to use a special locale when communicating with
		687	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		688	type, which requires the C<xim-onthespot> perl extension but rewards me
		689	with correct-looking fonts.
		690
		691	URxvt.perl-lib: /root/lib/urxvt
		692	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		693	URxvt.selection.pattern-0: ( at .*? line \\d+)
		694	URxvt.selection.pattern-1: ^(/[^:]+):\
		695	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		696	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		697
		698	This is my perl configuration. The first two set the perl library
		699	directory and also tells urxvt to use a large number of extensions. I
		700	develop for myself mostly, so I actually use most of the extensions I
		701	write.
		702
		703	The selection stuff mainly makes the selection perl-error-message aware
		704	and tells it to convert perl error messages into vi-commands to load the
		705	relevant file and go tot he error line number.
		706
		707	URxvt.scrollstyle: plain
		708	URxvt.secondaryScroll: true
		709
		710	As the documentation says: plain is the preferred scrollbar for the
		711	author. The C<secondaryScroll> configures urxvt to scroll in full-screen
		712	apps, like screen, so lines scrolled out of screen end up in urxvt's
		713	scrollback buffer.
		714
		715	URxvt.background: #000000
		716	URxvt.foreground: gray90
		717	URxvt.color7: gray90
		718	URxvt.colorBD: #ffffff
		719	URxvt.cursorColor: #e0e080
		720	URxvt.throughColor: #8080f0
		721	URxvt.highlightColor: #f0f0f0
		722
		723	Some colours. Not sure which ones are being used or even non-defaults, but
		724	these are in my .Xdefaults. Most notably, they set foreground/background
		725	to light gray/black, and also make sure that the colour 7 matches the
		726	default foreground colour.
		727
		728	URxvt.underlineColor: yellow
		729
		730	Another colour, makes underline lines look different. Sometimes hurts, but
		731	is mostly a nice effect.
		732
		733	URxvt.geometry: 154x36
		734	URxvt.loginShell: false
		735	URxvt.meta: ignore
		736	URxvt.utmpInhibit: true
		737
		738	Uh, well, should be mostly self-explanatory. By specifying some defaults
		739	manually, I can quickly switch them for testing.
		740
		741	URxvt.saveLines: 8192
		742
		743	A large scrollback buffer is essential. Really.
		744
		745	URxvt.mapAlert: true
		746
		747	The only case I use it is for my IRC window, which I like to keep
		748	iconified till people msg me (which beeps).
		749
		750	URxvt.visualBell: true
		751
		752	The audible bell is often annoying, especially when in a crowd.
		753
		754	URxvt.insecure: true
		755
		756	Please don't hack my mutt! Ooops...
		757
		758	URxvt.pastableTabs: false
		759
		760	I once thought this is a great idea.
		761
		762	urxvt.font: 9x15bold,\
		763	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		764	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		765	[codeset=JISX0208]xft:Kochi Gothic, \
		766	xft:Bitstream Vera Sans Mono:autohint=true, \
		767	xft:Code2000:antialias=false
		768	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		769	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		770	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		771
		772	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		773	overwhelmed. A special note: the C<9x15bold> mentioned above is actually
		774	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		775	font (different glyphs for C<;> and many other harmless characters),
		776	while the second font is actually the C<9x15bold> from XFree4/XOrg. The
		777	bold version has less chars than the medium version, so I use it for rare
		778	characters, too. When editing sources with vim, I use italic for comments
		779	and other stuff, which looks quite good with Bitstream Vera anti-aliased.
		780
		781	Terminus is a quite bad font (many very wrong glyphs), but for most of my
		782	purposes, it works, and gives a different look, as my normal (Non-bold)
		783	font is already bold, and I want to see a difference between bold and
		784	normal fonts.
		785
		786	Please note that I used the C<urxvt> instance name and not the C<URxvt>
		787	class name. Thats because I use different configs for different purposes,
		788	for example, my IRC window is started with C<-name IRC>, and uses these
		789	defaults:
		790
		791	IRC*title: IRC
		792	IRC*geometry: 87x12+535+542
		793	IRC*saveLines: 0
		794	IRC*mapAlert: true
		795	IRC*font: suxuseuro
		796	IRC*boldFont: suxuseuro
		797	IRC*colorBD: white
		798	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		799	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		800
		801	C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font
		802	sizes. C<suxuseuro> allows me to keep an eye (and actually read)
		803	stuff while keeping a very small window. If somebody pastes something
		804	complicated (e.g. japanese), I temporarily switch to a larger font.
		805
		806	The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor
		807	C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname>
		808	file for different hosts, for example, on ym main desktop, I use:
		809
		810	URxvt.keysym.C-M-q: command:\033[3;5;5t
		811	URxvt.keysym.C-M-y: command:\033[3;5;606t
		812	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		813	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		814	URxvt.keysym.C-M-p: perl:test
		815
		816	The first for keysym definitions allow me to quickly bring some windows
		817	in the layout I like most. Ion users might start laughing but will stop
		818	immediately when I tell them that I use my own Fvwm2 module for much the
		819	same effect as Ion provides, and I only very rarely use the above key
		820	combinations :->
		821
		822	=head3 Why doesn't rxvt-unicode read my resources?
		823
		824	Well, why, indeed? It does, in a way very similar to other X
		825	applications. Most importantly, this means that if you or your OS loads
		826	resources into the X display (the right way to do it), rxvt-unicode will
		827	ignore any resource files in your home directory. It will only read
		828	F<$HOME/.Xdefaults> when no resources are attached to the display.
		829
		830	If you have or use an F<$HOME/.Xresources> file, chances are that
		831	resources are loaded into your X-server. In this case, you have to
		832	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		833
		834	Also consider the form resources have to use:
		835
		836	URxvt.resource: value
		837
		838	If you want to use another form (there are lots of different ways of
		839	specifying resources), make sure you understand whether and why it
		840	works. If unsure, use the form above.
		841
49	=item When I log-in to another system it tells me about missing terminfo data?	842	=head3 When I log-in to another system it tells me about missing terminfo data?
50		843
51	The terminal description used by rxvt-unicode is not as widely available	844	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).	845	as that for xterm, or even rxvt (for which the same problem often arises).
53		846
54	The correct solution for this problem is to install the terminfo, this can	847	The correct solution for this problem is to install the terminfo, this can
55	be done like this (with ncurses' infocmp):	848	be done like this (with ncurses' infocmp and works as user and admin):
56		849
57	REMOTE=remotesystem.domain	850	REMOTE=remotesystem.domain
58	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	851	infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
59		852
60	... or by installing rxvt-unicode normally on the remote system,	853	... or by installing rxvt-unicode normally on the remote system,
		854
		855	One some systems you might need to set C<$TERMINFO> to the full path of
		856	F<$HOME/.terminfo> for this to work.
61		857
62	If you cannot or do not want to do this, then you can simply set	858	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	859	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	860	problems arising, which includes wrong keymapping, less and different
65	colours and some refresh errors in fullscreen applications. It's a nice	861	colours and some refresh errors in fullscreen applications. It's a nice
…		…
70	resource to set it:	866	resource to set it:
71		867
72	URxvt.termName: rxvt	868	URxvt.termName: rxvt
73		869
74	If you don't plan to use B<rxvt> (quite common...) you could also replace	870	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.	871	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
76		872
		873	=head3 C<tic> outputs some error when compiling the terminfo entry.
		874
		875	Most likely it's the empty definition for C<enacs=>. Just replace it by
		876	C<enacs=\E[0@> and try again.
		877
77	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	878	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
78		879
		880	See next entry.
		881
79	=item I need a termcap file entry.	882	=head3 I need a termcap file entry.
80		883
81	One reason you might want this is that some distributions or operating	884	One reason you might want this is that some distributions or operating
82	systems still compile some programs using the long-obsoleted termcap	885	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	886	library (Fedora Core's bash is one example) and rely on a termcap entry
84	for C<rxvt-unicode>.	887	for C<rxvt-unicode>.
85		888
86	You could use rxvt's termcap entry with resonable results in many cases.	889	You could use rxvt's termcap entry with reasonable results in many cases.
87	You can also create a termcap entry by using terminfo's infocmp program	890	You can also create a termcap entry by using terminfo's infocmp program
88	like this:	891	like this:
89		892
90	infocmp -C rxvt-unicode	893	infocmp -C rxvt-unicode
91		894
…		…
110	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	913	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
111	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	914	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
112	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	915	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
113	:vs=\E[?25h:	916	:vs=\E[?25h:
114		917
115	=item Why does C<ls> no longer have coloured output?	918	=head3 Why does C<ls> no longer have coloured output?
116		919
117	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	920	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
118	decide wether a terminal has colour, but uses it's own configuration	921	decide whether a terminal has colour, but uses its own configuration
119	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	922	file. Needless to say, C<rxvt-unicode> is not in its default file (among
120	with most other terminals supporting colour). Either add:	923	with most other terminals supporting colour). Either add:
121		924
122	TERM rxvt-unicode	925	TERM rxvt-unicode
123		926
124	to C</etc/DIR_COLORS> or simply add:	927	to C</etc/DIR_COLORS> or simply add:
125		928
126	alias ls='ls --color=auto'	929	alias ls='ls --color=auto'
127		930
128	to your C<.profile> or C<.bashrc>.	931	to your C<.profile> or C<.bashrc>.
129		932
130	=item Why doesn't vim/emacs etc. use the 88 colour mode?	933	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
131		934
		935	See next entry.
		936
132	=item Why doesn't vim/emacs etc. make use of italic?	937	=head3 Why doesn't vim/emacs etc. make use of italic?
133		938
		939	See next entry.
		940
134	=item Why are the secondary screen-related options not working properly?	941	=head3 Why are the secondary screen-related options not working properly?
135		942
136	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	943	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
137	distributions (most notably Debian GNU/Linux) break rxvt-unicode	944	distributions (most notably Debian GNU/Linux) break rxvt-unicode
138	by setting C<TERM> to C<rxvt>, which doesn't have these extra	945	by setting C<TERM> to C<rxvt>, which doesn't have these extra
139	features. Unfortunately, some of these (most notably, again, Debian	946	features. Unfortunately, some of these (most notably, again, Debian
140	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	947	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
141	file, so you will need to install it on your own (See the question B<When	948	file, so you will need to install it on your own (See the question B<When
142	I log-in to another system it tells me about missing terminfo data?> on	949	I log-in to another system it tells me about missing terminfo data?> on
143	how to do this).	950	how to do this).
144		951
145	=item My numerical keypad acts weird and generates differing output?
146		952
147	Some Debian GNUL/Linux users seem to have this problem, although no	953	=head2 Encoding / Locale / Input Method Issues
148	specific details were reported so far. It is possible that this is caused
149	by the wrong C<TERM> setting, although the details of wether and how
150	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
151	keymap. See the answer to the previous question, and please report if that
152	helped.
153		954
154	=item Rxvt-unicode does not seem to understand the selected encoding?	955	=head3 Rxvt-unicode does not seem to understand the selected encoding?
155		956
		957	See next entry.
		958
156	=item Unicode does not seem to work?	959	=head3 Unicode does not seem to work?
157		960
158	If you encounter strange problems like typing an accented character but	961	If you encounter strange problems like typing an accented character but
159	getting two unrelated other characters or similar, or if program output is	962	getting two unrelated other characters or similar, or if program output is
160	subtly garbled, then you should check your locale settings.	963	subtly garbled, then you should check your locale settings.
161		964
162	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	965	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
163	programs. Often rxvt-unicode is started in the C<C> locale, while the	966	programs running in it. Often rxvt-unicode is started in the C<C> locale,
164	login script running within the rxvt-unicode window changes the locale to	967	while the login script running within the rxvt-unicode window changes the
165	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.	968	locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is
		969	not going to work, and is the most common cause for problems.
166		970
167	The best thing is to fix your startup environment, as you will likely run	971	The best thing is to fix your startup environment, as you will likely run
168	into other problems. If nothing works you can try this in your .profile.	972	into other problems. If nothing works you can try this in your .profile.
169		973
170	printf '\e]701;%s\007' "$LC_CTYPE"	974	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
171		975
172	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	976	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
173	supported on your systems. Some systems have a C<locale> command which	977	supported on your systems. Some systems have a C<locale> command which
174	displays this (also, C<perl -e0> can be used to check locale settings, as	978	displays this (also, C<perl -e0> can be used to check locale settings, as
175	it will complain loudly if it cannot set the locale). If it displays something	979	it will complain loudly if it cannot set the locale). If it displays something
…		…
181		985
182	If nothing works and you are sure that everything is set correctly then	986	If nothing works and you are sure that everything is set correctly then
183	you will need to remember a little known fact: Some programs just don't	987	you will need to remember a little known fact: Some programs just don't
184	support locales :(	988	support locales :(
185		989
186	=item Why do some characters look so much different than others?	990	=head3 How does rxvt-unicode determine the encoding to use?
187		991
188	=item How does rxvt-unicode choose fonts?	992	See next entry.
189		993
190	Most fonts do not contain the full range of Unicode, which is	994	=head3 Is there an option to switch encodings?
191	fine. Chances are that the font you (or the admin/package maintainer of
192	your system/os) have specified does not cover all the characters you want
193	to display.
194		995
195	B<rxvt-unicode> makes a best-effort try at finding a replacement	996	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
196	font. Often the result is fine, but sometimes the chosen font looks	997	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
197	bad/ugly/wrong. Some fonts have totally strange characters that don't	998	UTF-8 or any other encodings with respect to terminal I/O.
198	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
199	intelligence to detect that a specific glyph is wrong: it has to believe
200	the font that the characters it claims to contain indeed look correct.
201		999
202	In that case, select a font of your taste and add it to the font list,	1000	The reasons is that there exists a perfectly fine mechanism for selecting
203	e.g.:	1001	the encoding, doing I/O and (most important) communicating this to all
204		1002	applications so everybody agrees on character properties such as width
205	@@RXVT_NAME@@ -fn basefont,font2,font3...	1003	and code number. This mechanism is the I<locale>. Applications not using
206		1004	that info will have problems (for example, C<xterm> gets the width of
207	When rxvt-unicode sees a character, it will first look at the base	1005	characters wrong as it uses its own, locale-independent table under all
208	font. If the base font does not contain the character, it will go to the
209	next font, and so on. Specifying your own fonts will also speed up this
210	search and use less resources within rxvt-unicode and the X-server.
211
212	The only limitation is that none of the fonts may be larger than the base
213	font, as the base font defines the terminal character cell size, which
214	must be the same due to the way terminals work.
215
216	=item Why do some chinese characters look so different than others?
217
218	This is because there is a difference between script and language --
219	rxvt-unicode does not know which language the text that is output is,
220	as it only knows the unicode character codes. If rxvt-unicode first
221	sees a japanese/chinese character, it might choose a japanese font for
222	display. Subsequent japanese characters will use that font. Now, many
223	chinese characters aren't represented in japanese fonts, so when the first
224	non-japanese character comes up, rxvt-unicode will look for a chinese font
225	-- unfortunately at this point, it will still use the japanese font for
226	chinese characters that are also in the japanese font.
227
228	The workaround is easy: just tag a chinese font at the end of your font
229	list (see the previous question). The key is to view the font list as
230	a preference list: If you expect more japanese, list a japanese font
231	first. If you expect more chinese, put a chinese font first.
232
233	In the future it might be possible to switch language preferences at
234	runtime (the internal data structure has no problem with using different
235	fonts for the same character at the same time, but no interface for this
236	has been designed yet).
237
238	Until then, you might get away with switching fonts at runtime (see L<Can
239	I switch the fonts at runtime?> later in this document).
240
241	=item Why does rxvt-unicode sometimes leave pixel droppings?
242
243	Most fonts were not designed for terminal use, which means that character
244	size varies a lot. A font that is otherwise fine for terminal use might
245	contain some characters that are simply too wide. Rxvt-unicode will avoid
246	these characters. For characters that are just "a bit" too wide a special
247	"careful" rendering mode is used that redraws adjacent characters.
248
249	All of this requires that fonts do not lie about character sizes,
250	however: Xft fonts often draw glyphs larger than their acclaimed bounding
251	box, and rxvt-unicode has no way of detecting this (the correct way is to
252	ask for the character bounding box, which unfortunately is wrong in these
253	cases).	1006	locales).
254		1007
255	It's not clear (to me at least), wether this is a bug in Xft, freetype,	1008	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
256	or the respective font. If you encounter this problem you might try using	1009	programs doing the same (that is, most) will automatically agree in the
257	the C<-lsp> option to give the font more height. If that doesn't work, you	1010	interpretation of characters.
258	might be forced to use a different font.
259		1011
260	All of this is not a problem when using X11 core fonts, as their bounding	1012	Unfortunately, there is no system-independent way to select locales, nor
261	box data is correct.	1013	is there a standard on how locale specifiers will look like.
262		1014
263	=item On Solaris 9, many line-drawing characters are too wide.	1015	On most systems, the content of the C<LC_CTYPE> environment variable
		1016	contains an arbitrary string which corresponds to an already-installed
		1017	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1018	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1019	(i.e. C<de> or C<german>) are also common.
264		1020
265	Seems to be a known bug, read	1021	Rxvt-unicode ignores all other locale categories, and except for
266	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1022	the encoding, ignores country or language-specific settings,
267	following ugly workaround to get non-double-wide-characters working:	1023	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		1024	rxvt-unicode.
268		1025
269	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1026	If you want to use a specific encoding you have to make sure you start
		1027	rxvt-unicode with the correct C<LC_CTYPE> category.
270		1028
271	=item My Compose (Multi_key) key is no longer working.	1029	=head3 Can I switch locales at runtime?
272		1030
273	The most common causes for this are that either your locale is not set	1031	Yes, using an escape sequence. Try something like this, which sets
274	correctly, or you specified a B<preeditStyle> that is not supported by	1032	rxvt-unicode's idea of C<LC_CTYPE>.
275	your input method. For example, if you specified B<OverTheSpot> and
276	your input method (e.g. the default input method handling Compose keys)
277	does not support this (for instance because it is not visual), then
278	rxvt-unicode will continue without an input method.
279		1033
280	In this case either do not specify a B<preeditStyle> or specify more than	1034	printf '\33]701;%s\007' ja_JP.SJIS
281	one pre-edit style, such as B<OverTheSpot,Root,None>.
282		1035
283	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755	1036	See also the previous answer.
284		1037
285	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on	1038	Sometimes this capability is rather handy when you want to work in
286	international keyboards) or simply use ISO 14755 support to your	1039	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
287	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other	1040	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
288	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape	1041	first switches to a locale supported by xjdic and back later:
289	character and so on.
290		1042
291	=item How can I keep rxvt-unicode from using reverse video so much?	1043	printf '\33]701;%s\007' ja_JP.SJIS
		1044	xjdic -js
		1045	printf '\33]701;%s\007' de_DE.UTF-8
292		1046
293	First of all, make sure you are running with the right terminal settings	1047	You can also use xterm's C<luit> program, which usually works fine, except
294	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then	1048	for some locales where character width differs between program- and
295	make sure you have specified colours for italic and bold, as otherwise	1049	rxvt-unicode-locales.
296	rxvt-unicode might use reverse video to simulate the effect:
297		1050
298	URxvt.colorBD: white	1051	=head3 I have problems getting my input method working.
299	URxvt.colorIT: green
300		1052
301	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?	1053	Try a search engine, as this is slightly different for every input method server.
302		1054
303	For some unexplainable reason, some rare programs assume a very weird	1055	Here is a checklist:
304	colour palette when confronted with a terminal with more than the standard
305	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
306	these programs not to assume non-ISO colours without very good reasons.
307		1056
308	In the meantime, you can either edit your C<rxvt-unicode> terminfo	1057	=over 4
309	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
310	fix colours but keep you from using other rxvt-unicode features.
311		1058
		1059	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		1060
		1061	Try C<locale -a> or check the documentation for your OS.
		1062
		1063	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		1064
		1065	For example, B<kinput2> does not support UTF-8 locales, you should use
		1066	C<ja_JP.EUC-JP> or equivalent.
		1067
		1068	=item - Make sure your XIM server is actually running.
		1069
		1070	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		1071
		1072	When you want to use e.g. B<kinput2>, it must be set to
		1073	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
		1074	method servers are running with this command:
		1075
		1076	xprop -root XIM_SERVERS
		1077
		1078	=item
		1079
		1080	=back
		1081
		1082	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		1083
		1084	You can specify separate locales for the input method and the rest of the
		1085	terminal, using the resource C<imlocale>:
		1086
		1087	URxvt.imlocale: ja_JP.EUC-JP
		1088
		1089	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1090	use your input method. Please note, however, that, depending on your Xlib
		1091	version, you may not be able to input characters outside C<EUC-JP> in a
		1092	normal way then, as your input method limits you.
		1093
		1094	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		1095
		1096	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1097	design. Applications can avoid some crashes at the expense of memory
		1098	leaks, and Input Methods can avoid some crashes by careful ordering at
		1099	exit time. B<kinput2> (and derived input methods) generally succeeds,
		1100	while B<SCIM> (or similar input methods) fails. In the end, however,
		1101	crashes cannot be completely avoided even if both sides cooperate.
		1102
		1103	So the only workaround is not to kill your Input Method Servers.
		1104
		1105
		1106	=head2 Operating Systems / Package Maintaining
		1107
		1108	=head3 I am using Debian GNU/Linux and have a problem...
		1109
		1110	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1111	patches that considerably change the behaviour of rxvt-unicode (but
		1112	unfortunately this notice has been removed). Before reporting a bug to
		1113	the original rxvt-unicode author please download and install the genuine
		1114	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1115	the problem. If you cannot, chances are that the problems are specific to
		1116	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1117	Tracking System (use C<reportbug> to report the bug).
		1118
		1119	For other problems that also affect the Debian package, you can and
		1120	probably should use the Debian BTS, too, because, after all, it's also a
		1121	bug in the Debian version and it serves as a reminder for other users that
		1122	might encounter the same issue.
		1123
		1124	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1125
		1126	You should build one binary with the default options. F<configure>
		1127	now enables most useful options, and the trend goes to making them
		1128	runtime-switchable, too, so there is usually no drawback to enabling them,
		1129	except higher disk and possibly memory usage. The perl interpreter should
		1130	be enabled, as important functionality (menus, selection, likely more in
		1131	the future) depends on it.
		1132
		1133	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		1134	system-wide (except maybe with C<defaults>). This will result in useful
		1135	behaviour. If your distribution aims at low memory, add an empty
		1136	C<perl-ext-common> resource to the app-defaults file. This will keep the
		1137	perl interpreter disabled until the user enables it.
		1138
		1139	If you can/want build more binaries, I recommend building a minimal
		1140	one with C<--disable-everything> (very useful) and a maximal one with
		1141	C<--enable-everything> (less useful, it will be very big due to a lot of
		1142	encodings built-in that increase download times and are rarely used).
		1143
		1144	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1145
		1146	It should be, starting with release 7.1. You are encouraged to properly
		1147	install urxvt with privileges necessary for your OS now.
		1148
		1149	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1150	into a helper process for privileged operations (pty handling on some
		1151	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1152	immediately. This is much safer than most other terminals that keep
		1153	privileges while running (but is more relevant to urxvt, as it contains
		1154	things as perl interpreters, which might be "helpful" to attackers).
		1155
		1156	This forking is done as the very first within main(), which is very early
		1157	and reduces possible bugs to initialisation code run before main(), or
		1158	things like the dynamic loader of your system, which should result in very
		1159	little risk.
		1160
312	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	1161	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
313		1162
314	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1163	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
315	in your compile environment, or an implementation that implements it,	1164	in your compile environment, or an implementation that implements it,
316	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1165	whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
317	B<wchar_t> is represented as unicode.	1166	B<wchar_t> is represented as unicode.
318		1167
319	As you might have guessed, FreeBSD does neither define this symobl nor	1168	As you might have guessed, FreeBSD does neither define this symbol nor
320	does it support it. Instead, it uses it's own internal representation of	1169	does it support it. Instead, it uses its own internal representation of
321	B<wchar_t>. This is, of course, completely fine with respect to standards.	1170	B<wchar_t>. This is, of course, completely fine with respect to standards.
322		1171
323	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and	1172	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
324	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.	1173	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
325		1174
…		…
339		1188
340	The rxvt-unicode author insists that the right way to fix this is in the	1189	The rxvt-unicode author insists that the right way to fix this is in the
341	system libraries once and for all, instead of forcing every app to carry	1190	system libraries once and for all, instead of forcing every app to carry
342	complete replacements for them :)	1191	complete replacements for them :)
343		1192
344	=item I use Solaris 9 and it doesn't compile/work/etc.	1193	=head3 How can I use rxvt-unicode under cygwin?
345		1194
346	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1195	rxvt-unicode should compile and run out of the box on cygwin, using
347	problems with C<wcwidth> and a compile problem.	1196	the X11 libraries that come with cygwin. libW11 emulation is no
		1197	longer supported (and makes no sense, either, as it only supported a
		1198	single font). I recommend starting the X-server in C<-multiwindow> or
		1199	C<-rootless> mode instead, which will result in similar look&feel as the
		1200	old libW11 emulation.
348		1201
349	=item How does rxvt-unicode determine the encoding to use?	1202	At the time of this writing, cygwin didn't seem to support any multi-byte
		1203	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		1204	to 8-bit encodings.
350		1205
351	=item Is there an option to switch encodings?	1206	=head3 Character widths are not correct.
352		1207
353	Unlike some other terminals, rxvt-unicode has no encoding switch, and no	1208	urxvt uses the system wcwidth function to know the information about
354	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about	1209	the width of characters, so on systems with incorrect locale data you
355	UTF-8 or any other encodings with respect to terminal I/O.	1210	will likely get bad results. Two notorious examples are Solaris 9,
		1211	where single-width characters like U+2514 are reported as double-width,
		1212	and Darwin 8, where combining chars are reported having width 1.
356		1213
357	The reasons is that there exists a perfectly fine mechanism for selecting	1214	The solution is to upgrade your system or switch to a better one. A
358	the encoding, doing I/O and (most important) communicating this to all	1215	possibly working workaround is to use a wcwidth implementation like
359	applications so everybody agrees on character properties such as width
360	and code number. This mechanism is the I<locale>. Applications not using
361	that info will have problems (for example, C<xterm> gets the width of
362	characters wrong as it uses it's own, locale-independent table under all
363	locales).
364		1216
365	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All	1217	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
366	programs doing the same (that is, most) will automatically agree in the
367	interpretation of characters.
368		1218
369	Unfortunately, there is no system-independent way to select locales, nor
370	is there a standard on how locale specifiers will look like.
371
372	On most systems, the content of the C<LC_CTYPE> environment variable
373	contains an arbitrary string which corresponds to an already-installed
374	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
375	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
376	(i.e. C<de> or C<german>) are also common.
377
378	Rxvt-unicode ignores all other locale categories, and except for
379	the encoding, ignores country or language-specific settings,
380	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
381	rxvt-unicode.
382
383	If you want to use a specific encoding you have to make sure you start
384	rxvt-unicode with the correct C<LC_CTYPE> category.
385
386	=item Can I switch locales at runtime?
387
388	Yes, using an escape sequence. Try something like this, which sets
389	rxvt-unicode's idea of C<LC_CTYPE>.
390
391	printf '\e]701;%s\007' ja_JP.SJIS
392
393	See also the previous answer.
394
395	Sometimes this capability is rather handy when you want to work in
396	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
397	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
398	first switches to a locale supported by xjdic and back later:
399
400	printf '\e]701;%s\007' ja_JP.SJIS
401	xjdic -js
402	printf '\e]701;%s\007' de_DE.UTF-8
403
404	You can also use xterm's C<luit> program, which usually works fine, except
405	for some locales where character width differs between program- and
406	rxvt-unicode-locales.
407
408	=item Can I switch the fonts at runtime?
409
410	Yes, using an escape sequence. Try something like this, which has the same
411	effect as using the C<-fn> switch, and takes effect immediately:
412
413	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
414
415	This is useful if you e.g. work primarily with japanese (and prefer a
416	japanese font), but you have to switch to chinese temporarily, where
417	japanese fonts would only be in your way.
418
419	You can think of this as a kind of manual ISO-2022 switching.
420
421	=item Why do italic characters look as if clipped?
422
423	Many fonts have difficulties with italic characters and hinting. For
424	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
425	Mono> completely fails in it's italic face. A workaround might be to
426	enable freetype autohinting, i.e. like this:
427
428	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
429	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
430
431	=item My input method wants <some encoding> but I want UTF-8, what can I do?
432
433	You can specify separate locales for the input method and the rest of the
434	terminal, using the resource C<imlocale>:
435
436	URxvt*imlocale: ja_JP.EUC-JP
437
438	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
439	use your input method. Please note, however, that you will not be able to
440	input characters outside C<EUC-JP> in a normal way then, as your input
441	method limits you.
442
443	=item Rxvt-unicode crashes when the X Input Method changes or exits.
444
445	Unfortunately, this is unavoidable, as the XIM protocol is racy by
446	design. Applications can avoid some crashes at the expense of memory
447	leaks, and Input Methods can avoid some crashes by careful ordering at
448	exit time. B<kinput2> (and derived input methods) generally succeeds,
449	while B<SCIM> (or similar input methods) fails. In the end, however,
450	crashes cannot be completely avoided even if both sides cooperate.
451
452	So the only workaround is not to kill your Input Method Servers.
453
454	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
455
456	Rxvt-unicode tries to obey the rule of not charging you for something you
457	don't use. One thing you should try is to configure out all settings that
458	you don't need, for example, Xft support is a resource hog by design,
459	when used. Compiling it out ensures that no Xft font will be loaded
460	accidentally when rxvt-unicode tries to find a font for your characters.
461
462	Also, many people (me included) like large windows and even larger
463	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
464	6 bytes per screen cell. For a 160x?? window this amounts to almost a
465	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
466	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
467	rxvt-unicode then uses 8 bytes per screen cell.
468
469	=item Can I speed up Xft rendering somehow?
470
471	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
472	it is simply slow. If you still want Xft fonts you might try to disable
473	antialiasing (by appending C<:antialiasing=false>), which saves lots of
474	memory and also speeds up rendering considerably.
475
476	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
477
478	Rxvt-unicode will use whatever you specify as a font. If it needs to
479	fall back to it's default font search list it will prefer X11 core
480	fonts, because they are small and fast, and then use Xft fonts. It has
481	antialiasing disabled for most of them, because the author thinks they
482	look best that way.
483
484	If you want antialiasing, you have to specify the fonts manually.
485
486	=item Mouse cut/paste suddenly no longer works.
487
488	Make sure that mouse reporting is actually turned off since killing
489	some editors prematurely may leave the mouse in mouse report mode. I've
490	heard that tcsh may use mouse reporting unless it otherwise specified. A
491	quick check is to see if cut/paste works when the Alt or Shift keys are
492	depressed. See @@RXVT_NAME@@(7)
493
494	=item What's with this bold/blink stuff?
495
496	If no bold colour is set via C<colorBD:>, bold will invert text using the
497	standard foreground colour.
498
499	For the standard background colour, blinking will actually make the
500	text blink when compiled with C<--enable-blinking>. with standard
501	colours. Without C<--enable-blinking>, the blink attribute will be
502	ignored.
503
504	On ANSI colours, bold/blink attributes are used to set high-intensity
505	foreground/background colors.
506
507	color0-7 are the low-intensity colors.
508
509	color8-15 are the corresponding high-intensity colors.
510
511	=item I don't like the screen colors. How do I change them?
512
513	You can change the screen colors at run-time using F<~/.Xdefaults>
514	resources (or as long-options).
515
516	Here are values that are supposed to resemble a VGA screen,
517	including the murky brown that passes for low-intensity yellow:
518
519	URxvt.color0: #000000
520	URxvt.color1: #A80000
521	URxvt.color2: #00A800
522	URxvt.color3: #A8A800
523	URxvt.color4: #0000A8
524	URxvt.color5: #A800A8
525	URxvt.color6: #00A8A8
526	URxvt.color7: #A8A8A8
527
528	URxvt.color8: #000054
529	URxvt.color9: #FF0054
530	URxvt.color10: #00FF54
531	URxvt.color11: #FFFF54
532	URxvt.color12: #0000FF
533	URxvt.color13: #FF00FF
534	URxvt.color14: #00FFFF
535	URxvt.color15: #FFFFFF
536
537	And here is a more complete set of non-standard colors described (not by
538	me) as "pretty girly".
539
540	URxvt.cursorColor: #dc74d1
541	URxvt.pointerColor: #dc74d1
542	URxvt.background: #0e0e0e
543	URxvt.foreground: #4ad5e1
544	URxvt.color0: #000000
545	URxvt.color8: #8b8f93
546	URxvt.color1: #dc74d1
547	URxvt.color9: #dc74d1
548	URxvt.color2: #0eb8c7
549	URxvt.color10: #0eb8c7
550	URxvt.color3: #dfe37e
551	URxvt.color11: #dfe37e
552	URxvt.color5: #9e88f0
553	URxvt.color13: #9e88f0
554	URxvt.color6: #73f7ff
555	URxvt.color14: #73f7ff
556	URxvt.color7: #e1dddd
557	URxvt.color15: #e1dddd
558
559	=item How can I start @@RXVT_NAME@@d in a race-free way?
560
561	Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a
562	server that answers @@RXVT_NAME@@c's requests, so it doesn't background
563	itself.
564
565	To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
566	following method to wait for the startup message before continuing:
567
568	{ @@RXVT_NAME@@d & } | read
569
570	=item What's with the strange Backspace/Delete key behaviour?
571
572	Assuming that the physical Backspace key corresponds to the
573	BackSpace keysym (not likely for Linux ... see the following
574	question) there are two standard values that can be used for
575	Backspace: C<^H> and C<^?>.
576
577	Historically, either value is correct, but rxvt-unicode adopts the debian
578	policy of using C<^?> when unsure, because it's the one only only correct
579	choice :).
580
581	Rxvt-unicode tries to inherit the current stty settings and uses the value
582	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
583	started from a terminal (say, from a menu or by remote shell), then the
584	system value of `erase', which corresponds to CERASE in <termios.h>, will
585	be used (which may not be the same as your stty setting).
586
587	For starting a new rxvt-unicode:
588
589	# use Backspace = ^H
590	$ stty erase ^H
591	$ @@RXVT_NAME@@
592
593	# use Backspace = ^?
594	$ stty erase ^?
595	$ @@RXVT_NAME@@
596
597	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
598
599	For an existing rxvt-unicode:
600
601	# use Backspace = ^H
602	$ stty erase ^H
603	$ echo -n "^[[36h"
604
605	# use Backspace = ^?
606	$ stty erase ^?
607	$ echo -n "^[[36l"
608
609	This helps satisfy some of the Backspace discrepancies that occur, but
610	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
611	properly reflects that.
612
613	The Delete key is a another casualty of the ill-defined Backspace problem.
614	To avoid confusion between the Backspace and Delete keys, the Delete
615	key has been assigned an escape sequence to match the vt100 for Execute
616	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
617
618	Some other Backspace problems:
619
620	some editors use termcap/terminfo,
621	some editors (vim I'm told) expect Backspace = ^H,
622	GNU Emacs (and Emacs-like editors) use ^H for help.
623
624	Perhaps someday this will all be resolved in a consistent manner.
625
626	=item I don't like the key-bindings. How do I change them?
627
628	There are some compile-time selections available via configure. Unless
629	you have run "configure" with the C<--disable-resources> option you can
630	use the `keysym' resource to alter the keystrings associated with keysyms.
631
632	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
633
634	URxvt.keysym.Home: \033[1~
635	URxvt.keysym.End: \033[4~
636	URxvt.keysym.C-apostrophe: \033<C-'>
637	URxvt.keysym.C-slash: \033<C-/>
638	URxvt.keysym.C-semicolon: \033<C-;>
639	URxvt.keysym.C-grave: \033<C-`>
640	URxvt.keysym.C-comma: \033<C-,>
641	URxvt.keysym.C-period: \033<C-.>
642	URxvt.keysym.C-0x60: \033<C-`>
643	URxvt.keysym.C-Tab: \033<C-Tab>
644	URxvt.keysym.C-Return: \033<C-Return>
645	URxvt.keysym.S-Return: \033<S-Return>
646	URxvt.keysym.S-space: \033<S-Space>
647	URxvt.keysym.M-Up: \033<M-Up>
648	URxvt.keysym.M-Down: \033<M-Down>
649	URxvt.keysym.M-Left: \033<M-Left>
650	URxvt.keysym.M-Right: \033<M-Right>
651	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
652	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
653	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
654
655	See some more examples in the documentation for the B<keysym> resource.
656
657	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
658	How do I make use of them? For example, the Sun Keyboard type 4
659	has the following mappings that rxvt-unicode doesn't recognize.
660
661	KP_Insert == Insert
662	F22 == Print
663	F27 == Home
664	F29 == Prior
665	F33 == End
666	F35 == Next
667
668	Rather than have rxvt-unicode try to accommodate all the various possible
669	keyboard mappings, it is better to use `xmodmap' to remap the keys as
670	required for your particular machine.
671
672	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
673	I need this to decide about setting colors etc.
674
675	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
676	check and see if that is set. Note that several programs, JED, slrn,
677	Midnight Commander automatically check this variable to decide whether or
678	not to use color.
679
680	=item How do I set the correct, full IP address for the DISPLAY variable?
681
682	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
683	insecure mode then it is possible to use the following shell script
684	snippets to correctly set the display. If your version of rxvt-unicode
685	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
686	the COLORTERM variable can be used to distinguish rxvt-unicode from a
687	regular xterm.
688
689	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
690	snippets:
691
692	# Bourne/Korn/POSIX family of shells:
693	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
694	if [ ${TERM:-foo} = xterm ]; then
695	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
696	echo -n '^[Z'
697	read term_id
698	stty icanon echo
699	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
700	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
701	read DISPLAY # set it in our local shell
702	fi
703	fi
704
705	=item How do I compile the manual pages for myself?
706
707	You need to have a recent version of perl installed as F</usr/bin/perl>,
708	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
709	the doc subdirectory and enter C<make alldoc>.
710
711	=item My question isn't answered here, can I ask a human?
712
713	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
714	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
715	interested in learning about new and exciting problems (but not FAQs :).
716
717	=back
718
719	=head1 RXVT TECHNICAL REFERENCE	1219	=head1 RXVT-UNICODE TECHNICAL REFERENCE
720
721	=head1 DESCRIPTION
722		1220
723	The rest of this document describes various technical aspects of	1221	The rest of this document describes various technical aspects of
724	B<rxvt-unicode>. First the description of supported command sequences,	1222	B<rxvt-unicode>. First the description of supported command sequences,
725	followed by menu and pixmap support and last by a description of all	1223	followed by pixmap support and last by a description of all features
726	features selectable at C<configure> time.	1224	selectable at C<configure> time.
727		1225
728	=head1 Definitions	1226	=head2 Definitions
729		1227
730	=over 4	1228	=over 4
731		1229
732	=item B<< C<c> >>	1230	=item B<< C<c> >>
733		1231
…		…
751		1249
752	A text parameter composed of printable characters.	1250	A text parameter composed of printable characters.
753		1251
754	=back	1252	=back
755		1253
756	=head1 Values	1254	=head2 Values
757		1255
758	=over 4	1256	=over 4
759		1257
760	=item B<< C<ENQ> >>	1258	=item B<< C<ENQ> >>
761		1259
…		…
804		1302
805	Space Character	1303	Space Character
806		1304
807	=back	1305	=back
808		1306
809	=head1 Escape Sequences	1307	=head2 Escape Sequences
810		1308
811	=over 4	1309	=over 4
812		1310
813	=item B<< C<ESC # 8> >>	1311	=item B<< C<ESC # 8> >>
814		1312
…		…
912		1410
913	=back	1411	=back
914		1412
915	X<CSI>	1413	X<CSI>
916		1414
917	=head1 CSI (Command Sequence Introducer) Sequences	1415	=head2 CSI (Command Sequence Introducer) Sequences
918		1416
919	=over 4	1417	=over 4
920		1418
921	=item B<< C<ESC [ Ps @> >>	1419	=item B<< C<ESC [ Ps @> >>
922		1420
…		…
1192		1690
1193	=back	1691	=back
1194		1692
1195	X<PrivateModes>	1693	X<PrivateModes>
1196		1694
1197	=head1 DEC Private Modes	1695	=head2 DEC Private Modes
1198		1696
1199	=over 4	1697	=over 4
1200		1698
1201	=item B<< C<ESC [ ? Pm h> >>	1699	=item B<< C<ESC [ ? Pm h> >>
1202		1700
…		…
1218		1716
1219	Toggle DEC Private Mode Values (rxvt extension). I<where>	1717	Toggle DEC Private Mode Values (rxvt extension). I<where>
1220		1718
1221	=over 4	1719	=over 4
1222		1720
1223	=item B<< C<Ps = 1> >> (DECCKM)	1721	=item B<< C<Pm = 1> >> (DECCKM)
1224		1722
1225	=begin table	1723	=begin table
1226		1724
1227	B<< C<h> >> Application Cursor Keys	1725	B<< C<h> >> Application Cursor Keys
1228	B<< C<l> >> Normal Cursor Keys	1726	B<< C<l> >> Normal Cursor Keys
1229		1727
1230	=end table	1728	=end table
1231		1729
1232	=item B<< C<Ps = 2> >> (ANSI/VT52 mode)	1730	=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1233		1731
1234	=begin table	1732	=begin table
1235		1733
1236	B<< C<h> >> Enter VT52 mode	1734	B<< C<h> >> Enter VT52 mode
1237	B<< C<l> >> Enter VT52 mode	1735	B<< C<l> >> Enter VT52 mode
1238		1736
1239	=end table	1737	=end table
1240		1738
1241	=item B<< C<Ps = 3> >>	1739	=item B<< C<Pm = 3> >>
1242		1740
1243	=begin table	1741	=begin table
1244		1742
1245	B<< C<h> >> 132 Column Mode (DECCOLM)	1743	B<< C<h> >> 132 Column Mode (DECCOLM)
1246	B<< C<l> >> 80 Column Mode (DECCOLM)	1744	B<< C<l> >> 80 Column Mode (DECCOLM)
1247		1745
1248	=end table	1746	=end table
1249		1747
1250	=item B<< C<Ps = 4> >>	1748	=item B<< C<Pm = 4> >>
1251		1749
1252	=begin table	1750	=begin table
1253		1751
1254	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)	1752	B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1255	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)	1753	B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1256		1754
1257	=end table	1755	=end table
1258		1756
1259	=item B<< C<Ps = 5> >>	1757	=item B<< C<Pm = 5> >>
1260		1758
1261	=begin table	1759	=begin table
1262		1760
1263	B<< C<h> >> Reverse Video (DECSCNM)	1761	B<< C<h> >> Reverse Video (DECSCNM)
1264	B<< C<l> >> Normal Video (DECSCNM)	1762	B<< C<l> >> Normal Video (DECSCNM)
1265		1763
1266	=end table	1764	=end table
1267		1765
1268	=item B<< C<Ps = 6> >>	1766	=item B<< C<Pm = 6> >>
1269		1767
1270	=begin table	1768	=begin table
1271		1769
1272	B<< C<h> >> Origin Mode (DECOM)	1770	B<< C<h> >> Origin Mode (DECOM)
1273	B<< C<l> >> Normal Cursor Mode (DECOM)	1771	B<< C<l> >> Normal Cursor Mode (DECOM)
1274		1772
1275	=end table	1773	=end table
1276		1774
1277	=item B<< C<Ps = 7> >>	1775	=item B<< C<Pm = 7> >>
1278		1776
1279	=begin table	1777	=begin table
1280		1778
1281	B<< C<h> >> Wraparound Mode (DECAWM)	1779	B<< C<h> >> Wraparound Mode (DECAWM)
1282	B<< C<l> >> No Wraparound Mode (DECAWM)	1780	B<< C<l> >> No Wraparound Mode (DECAWM)
1283		1781
1284	=end table	1782	=end table
1285		1783
1286	=item B<< C<Ps = 8> >> I<unimplemented>	1784	=item B<< C<Pm = 8> >> I<unimplemented>
1287		1785
1288	=begin table	1786	=begin table
1289		1787
1290	B<< C<h> >> Auto-repeat Keys (DECARM)	1788	B<< C<h> >> Auto-repeat Keys (DECARM)
1291	B<< C<l> >> No Auto-repeat Keys (DECARM)	1789	B<< C<l> >> No Auto-repeat Keys (DECARM)
1292		1790
1293	=end table	1791	=end table
1294		1792
1295	=item B<< C<Ps = 9> >> X10 XTerm	1793	=item B<< C<Pm = 9> >> X10 XTerm
1296		1794
1297	=begin table	1795	=begin table
1298		1796
1299	B<< C<h> >> Send Mouse X & Y on button press.	1797	B<< C<h> >> Send Mouse X & Y on button press.
1300	B<< C<l> >> No mouse reporting.	1798	B<< C<l> >> No mouse reporting.
1301		1799
1302	=end table	1800	=end table
1303		1801
1304	=item B<< C<Ps = 10> >> (B<rxvt>)
1305
1306	=begin table
1307
1308	B<< C<h> >> menuBar visible
1309	B<< C<l> >> menuBar invisible
1310
1311	=end table
1312
1313	=item B<< C<Ps = 25> >>	1802	=item B<< C<Pm = 25> >>
1314		1803
1315	=begin table	1804	=begin table
1316		1805
1317	B<< C<h> >> Visible cursor {cnorm/cvvis}	1806	B<< C<h> >> Visible cursor {cnorm/cvvis}
1318	B<< C<l> >> Invisible cursor {civis}	1807	B<< C<l> >> Invisible cursor {civis}
1319		1808
1320	=end table	1809	=end table
1321		1810
1322	=item B<< C<Ps = 30> >>	1811	=item B<< C<Pm = 30> >>
1323		1812
1324	=begin table	1813	=begin table
1325		1814
1326	B<< C<h> >> scrollBar visisble	1815	B<< C<h> >> scrollBar visisble
1327	B<< C<l> >> scrollBar invisisble	1816	B<< C<l> >> scrollBar invisisble
1328		1817
1329	=end table	1818	=end table
1330		1819
1331	=item B<< C<Ps = 35> >> (B<rxvt>)	1820	=item B<< C<Pm = 35> >> (B<rxvt>)
1332		1821
1333	=begin table	1822	=begin table
1334		1823
1335	B<< C<h> >> Allow XTerm Shift+key sequences	1824	B<< C<h> >> Allow XTerm Shift+key sequences
1336	B<< C<l> >> Disallow XTerm Shift+key sequences	1825	B<< C<l> >> Disallow XTerm Shift+key sequences
1337		1826
1338	=end table	1827	=end table
1339		1828
1340	=item B<< C<Ps = 38> >> I<unimplemented>	1829	=item B<< C<Pm = 38> >> I<unimplemented>
1341		1830
1342	Enter Tektronix Mode (DECTEK)	1831	Enter Tektronix Mode (DECTEK)
1343		1832
1344	=item B<< C<Ps = 40> >>	1833	=item B<< C<Pm = 40> >>
1345		1834
1346	=begin table	1835	=begin table
1347		1836
1348	B<< C<h> >> Allow 80/132 Mode	1837	B<< C<h> >> Allow 80/132 Mode
1349	B<< C<l> >> Disallow 80/132 Mode	1838	B<< C<l> >> Disallow 80/132 Mode
1350		1839
1351	=end table	1840	=end table
1352		1841
1353	=item B<< C<Ps = 44> >> I<unimplemented>	1842	=item B<< C<Pm = 44> >> I<unimplemented>
1354		1843
1355	=begin table	1844	=begin table
1356		1845
1357	B<< C<h> >> Turn On Margin Bell	1846	B<< C<h> >> Turn On Margin Bell
1358	B<< C<l> >> Turn Off Margin Bell	1847	B<< C<l> >> Turn Off Margin Bell
1359		1848
1360	=end table	1849	=end table
1361		1850
1362	=item B<< C<Ps = 45> >> I<unimplemented>	1851	=item B<< C<Pm = 45> >> I<unimplemented>
1363		1852
1364	=begin table	1853	=begin table
1365		1854
1366	B<< C<h> >> Reverse-wraparound Mode	1855	B<< C<h> >> Reverse-wraparound Mode
1367	B<< C<l> >> No Reverse-wraparound Mode	1856	B<< C<l> >> No Reverse-wraparound Mode
1368		1857
1369	=end table	1858	=end table
1370		1859
1371	=item B<< C<Ps = 46> >> I<unimplemented>	1860	=item B<< C<Pm = 46> >> I<unimplemented>
1372		1861
1373	=item B<< C<Ps = 47> >>	1862	=item B<< C<Pm = 47> >>
1374		1863
1375	=begin table	1864	=begin table
1376		1865
1377	B<< C<h> >> Use Alternate Screen Buffer	1866	B<< C<h> >> Use Alternate Screen Buffer
1378	B<< C<l> >> Use Normal Screen Buffer	1867	B<< C<l> >> Use Normal Screen Buffer
1379		1868
1380	=end table	1869	=end table
1381		1870
1382	X<Priv66>	1871	X<Priv66>
1383		1872
1384	=item B<< C<Ps = 66> >>	1873	=item B<< C<Pm = 66> >>
1385		1874
1386	=begin table	1875	=begin table
1387		1876
1388	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>	1877	B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1389	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>	1878	B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1390		1879
1391	=end table	1880	=end table
1392		1881
1393	=item B<< C<Ps = 67> >>	1882	=item B<< C<Pm = 67> >>
1394		1883
1395	=begin table	1884	=begin table
1396		1885
1397	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>	1886	B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1398	B<< C<l> >> Backspace key sends B<< C<DEL> >>	1887	B<< C<l> >> Backspace key sends B<< C<DEL> >>
1399		1888
1400	=end table	1889	=end table
1401		1890
1402	=item B<< C<Ps = 1000> >> (X11 XTerm)	1891	=item B<< C<Pm = 1000> >> (X11 XTerm)
1403		1892
1404	=begin table	1893	=begin table
1405		1894
1406	B<< C<h> >> Send Mouse X & Y on button press and release.	1895	B<< C<h> >> Send Mouse X & Y on button press and release.
1407	B<< C<l> >> No mouse reporting.	1896	B<< C<l> >> No mouse reporting.
1408		1897
1409	=end table	1898	=end table
1410		1899
1411	=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented>	1900	=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1412		1901
1413	=begin table	1902	=begin table
1414		1903
1415	B<< C<h> >> Use Hilite Mouse Tracking.	1904	B<< C<h> >> Use Hilite Mouse Tracking.
1416	B<< C<l> >> No mouse reporting.	1905	B<< C<l> >> No mouse reporting.
1417		1906
1418	=end table	1907	=end table
1419		1908
		1909	=item B<< C<Pm = 1002> >> (X11 XTerm)
		1910
		1911	=begin table
		1912
		1913	B<< C<h> >> Send Mouse X & Y on button press and release, and motion with a button pressed.
		1914	B<< C<l> >> No mouse reporting.
		1915
		1916	=end table
		1917
		1918	=item B<< C<Pm = 1003> >> (X11 XTerm)
		1919
		1920	=begin table
		1921
		1922	B<< C<h> >> Send Mouse X & Y on button press and release, and motion.
		1923	B<< C<l> >> No mouse reporting.
		1924
		1925	=end table
		1926
1420	=item B<< C<Ps = 1010> >> (B<rxvt>)	1927	=item B<< C<Pm = 1010> >> (B<rxvt>)
1421		1928
1422	=begin table	1929	=begin table
1423		1930
1424	B<< C<h> >> Don't scroll to bottom on TTY output	1931	B<< C<h> >> Don't scroll to bottom on TTY output
1425	B<< C<l> >> Scroll to bottom on TTY output	1932	B<< C<l> >> Scroll to bottom on TTY output
1426		1933
1427	=end table	1934	=end table
1428		1935
1429	=item B<< C<Ps = 1011> >> (B<rxvt>)	1936	=item B<< C<Pm = 1011> >> (B<rxvt>)
1430		1937
1431	=begin table	1938	=begin table
1432		1939
1433	B<< C<h> >> Scroll to bottom when a key is pressed	1940	B<< C<h> >> Scroll to bottom when a key is pressed
1434	B<< C<l> >> Don't scroll to bottom when a key is pressed	1941	B<< C<l> >> Don't scroll to bottom when a key is pressed
1435		1942
1436	=end table	1943	=end table
1437		1944
		1945	=item B<< C<Pm = 1021> >> (B<rxvt>)
		1946
		1947	=begin table
		1948
		1949	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
		1950	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
		1951
		1952	=end table
		1953
1438	=item B<< C<Ps = 1047> >>	1954	=item B<< C<Pm = 1047> >>
1439		1955
1440	=begin table	1956	=begin table
1441		1957
1442	B<< C<h> >> Use Alternate Screen Buffer	1958	B<< C<h> >> Use Alternate Screen Buffer
1443	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it	1959	B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1444		1960
1445	=end table	1961	=end table
1446		1962
1447	=item B<< C<Ps = 1048> >>	1963	=item B<< C<Pm = 1048> >>
1448		1964
1449	=begin table	1965	=begin table
1450		1966
1451	B<< C<h> >> Save cursor position	1967	B<< C<h> >> Save cursor position
1452	B<< C<l> >> Restore cursor position	1968	B<< C<l> >> Restore cursor position
1453		1969
1454	=end table	1970	=end table
1455		1971
1456	=item B<< C<Ps = 1049> >>	1972	=item B<< C<Pm = 1049> >>
1457		1973
1458	=begin table	1974	=begin table
1459		1975
1460	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it	1976	B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1461	B<< C<l> >> Use Normal Screen Buffer	1977	B<< C<l> >> Use Normal Screen Buffer
…		…
1466		1982
1467	=back	1983	=back
1468		1984
1469	X<XTerm>	1985	X<XTerm>
1470		1986
1471	=head1 XTerm Operating System Commands	1987	=head2 XTerm Operating System Commands
1472		1988
1473	=over 4	1989	=over 4
1474		1990
1475	=item B<< C<ESC ] Ps;Pt ST> >>	1991	=item B<< C<ESC ] Ps;Pt ST> >>
1476		1992
…		…
1488	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	2004	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>
1489	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	2005	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>
1490	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	2006	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1491	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	2007	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1492	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	2008	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1493	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	2009	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1494	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	2010	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1495	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	2011	B<< C<Ps = 20> >> Change background pixmap parameters (see section BACKGROUND IMAGE) (Compile AfterImage).
1496	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.	2012	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1497	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	2013	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1498	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	2014	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1499	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> >>	2015	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> >>
1500	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	2016	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1501	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).	2017	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).
1502	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).	2018	B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>.
1503	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	2019	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1504	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	2020	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
		2021	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		2022	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1505	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	2023	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1506	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	2024	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1507	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	2025	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1508	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	2026	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1509	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).	2027	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1510	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).	2028	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		2029	B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1511		2030
1512	=end table	2031	=end table
1513		2032
1514	=back	2033	=back
1515		2034
1516	X<menuBar>	2035	=head1 BACKGROUND IMAGE
1517		2036
1518	=head1 menuBar
1519
1520	B<< The exact syntax used is I<almost> solidified. >>
1521	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1522	menuBar.
1523
1524	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1525	omitted: use B<./> to specify a menu relative to the current menu.
1526
1527	=head2 Overview of menuBar operation
1528
1529	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1530	of C<Pt> can be used for a variety of tasks:
1531
1532	At the top level is the current menuBar which is a member of a circular
1533	linked-list of other such menuBars.
1534
1535	The menuBar acts as a parent for the various drop-down menus, which in
1536	turn, may have labels, separator lines, menuItems and subMenus.
1537
1538	The menuItems are the useful bits: you can use them to mimic keyboard
1539	input or even to send text or escape sequences back to rxvt.
1540
1541	The menuBar syntax is intended to provide a simple yet robust method of
1542	constructing and manipulating menus and navigating through the
1543	menuBars.
1544
1545	The first step is to use the tag B<< [menu:I<name>] >> which creates
1546	the menuBar called I<name> and allows access. You may now or menus,
1547	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1548	menuBar access as B<readonly> to prevent accidental corruption of the
1549	menus. To re-access the current menuBar for alterations, use the tag
1550	B<[menu]>, make the alterations and then use B<[done]>
1551
1552	X<menuBarCommands>
1553
1554	=head2 Commands
1555
1556	=over 4
1557
1558	=item B<< [menu:+I<name>] >>
1559
1560	access the named menuBar for creation or alteration. If a new menuBar
1561	is created, it is called I<name> (max of 15 chars) and the current
1562	menuBar is pushed onto the stack
1563
1564	=item B<[menu]>
1565
1566	access the current menuBar for alteration
1567
1568	=item B<< [title:+I<string>] >>
1569
1570	set the current menuBar's title to I<string>, which may contain the
1571	following format specifiers:
1572
1573	B<%n> rxvt name (as per the B<-name> command-line option)
1574	B<%v> rxvt version
1575	B<%%> literal B<%> character
1576
1577	=item B<[done]>
1578
1579	set menuBar access as B<readonly>.
1580	End-of-file tag for B<< [read:+I<file>] >> operations.
1581
1582	=item B<< [read:+I<file>] >>
1583
1584	read menu commands directly from I<file> (extension ".menu" will be
1585	appended if required.) Start reading at a line with B<[menu]> or B<<
1586	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1587
1588	Blank and comment lines (starting with B<#>) are ignored. Actually,
1589	since any invalid menu commands are also ignored, almost anything could
1590	be construed as a comment line, but this may be tightened up in the
1591	future ... so don't count on it!.
1592
1593	=item B<< [read:+I<file>;+I<name>] >>
1594
1595	The same as B<< [read:+I<file>] >>, but start reading at a line with
1596	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1597	B<[done]> is encountered.
1598
1599	=item B<[dump]>
1600
1601	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1602	later rereading.
1603
1604	=item B<[rm:name]>
1605
1606	remove the named menuBar
1607
1608	=item B<[rm] [rm:]>
1609
1610	remove the current menuBar
1611
1612	=item B<[rm*] [rm:*]>
1613
1614	remove all menuBars
1615
1616	=item B<[swap]>
1617
1618	swap the top two menuBars
1619
1620	=item B<[prev]>
1621
1622	access the previous menuBar
1623
1624	=item B<[next]>
1625
1626	access the next menuBar
1627
1628	=item B<[show]>
1629
1630	Enable display of the menuBar
1631
1632	=item B<[hide]>
1633
1634	Disable display of the menuBar
1635
1636	=item B<< [pixmap:+I<name>] >>
1637
1638	=item B<< [pixmap:+I<name>;I<scaling>] >>
1639
1640	(set the background pixmap globally
1641
1642	B<< A Future implementation I<may> make this local to the menubar >>)
1643
1644	=item B<< [:+I<command>:] >>
1645
1646	ignore the menu readonly status and issue a I<command> to or a menu or
1647	menuitem or change the ; a useful shortcut for setting the quick arrows
1648	from a menuBar.
1649
1650	=back
1651
1652	X<menuBarAdd>
1653
1654	=head2 Adding and accessing menus
1655
1656	The following commands may also be B<+> prefixed.
1657
1658	=over 4
1659
1660	=item B</+>
1661
1662	access menuBar top level
1663
1664	=item B<./+>
1665
1666	access current menu level
1667
1668	=item B<../+>
1669
1670	access parent menu (1 level up)
1671
1672	=item B<../../>
1673
1674	access parent menu (multiple levels up)
1675
1676	=item B<< I</path/>menu >>
1677
1678	add/access menu
1679
1680	=item B<< I</path/>menu/* >>
1681
1682	add/access menu and clear it if it exists
1683
1684	=item B<< I</path/>{-} >>
1685
1686	add separator
1687
1688	=item B<< I</path/>{item} >>
1689
1690	add B<item> as a label
1691
1692	=item B<< I</path/>{item} action >>
1693
1694	add/alter I<menuitem> with an associated I<action>
1695
1696	=item B<< I</path/>{item}{right-text} >>
1697
1698	add/alter I<menuitem> with B<right-text> as the right-justified text
1699	and as the associated I<action>
1700
1701	=item B<< I</path/>{item}{rtext} action >>
1702
1703	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1704	the right-justified text.
1705
1706	=back
1707
1708	=over 4
1709
1710	=item Special characters in I<action> must be backslash-escaped:
1711
1712	B<\a \b \E \e \n \r \t \octal>
1713
1714	=item or in control-character notation:
1715
1716	B<^@, ^A .. ^Z .. ^_, ^?>
1717
1718	=back
1719
1720	To send a string starting with a B<NUL> (B<^@>) character to the
1721	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1722	the first of which will be stripped off and the balance directed to the
1723	program. Otherwise if I<action> begins with B<NUL> followed by
1724	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1725	balance is sent back to rxvt.
1726
1727	As a convenience for the many Emacs-type editors, I<action> may start
1728	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1729	appended if missed from B<M-x> commands.
1730
1731	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1732	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1733
1734	=over 4
1735
1736	=item For example,
1737
1738	B<M-xapropos> is equivalent to B<\Exapropos\r>
1739
1740	=item and
1741
1742	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1743
1744	=back
1745
1746	The option B<< {I<right-rtext>} >> will be right-justified. In the
1747	absence of a specified action, this text will be used as the I<action>
1748	as well.
1749
1750	=over 4
1751
1752	=item For example,
1753
1754	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1755
1756	=back
1757
1758	The left label I<is> necessary, since it's used for matching, but
1759	implicitly hiding the left label (by using same name for both left and
1760	right labels), or explicitly hiding the left label (by preceeding it
1761	with a dot), makes it possible to have right-justified text only.
1762
1763	=over 4
1764
1765	=item For example,
1766
1767	B</File/{Open}{Open} Open-File-Action>
1768
1769	=item or hiding it
1770
1771	B</File/{.anylabel}{Open} Open-File-Action>
1772
1773	=back
1774
1775	X<menuBarRemove>
1776
1777	=head2 Removing menus
1778
1779	=over 4
1780
1781	=item B<< -/*+ >>
1782
1783	remove all menus from the menuBar, the same as B<[clear]>
1784
1785	=item B<< -+I</path>menu+ >>
1786
1787	remove menu
1788
1789	=item B<< -+I</path>{item}+ >>
1790
1791	remove item
1792
1793	=item B<< -+I</path>{-} >>
1794
1795	remove separator)
1796
1797	=item B<-/path/menu/*>
1798
1799	remove all items, separators and submenus from menu
1800
1801	=back
1802
1803	X<menuBarArrows>
1804
1805	=head2 Quick Arrows
1806
1807	The menus also provide a hook for I<quick arrows> to provide easier
1808	user access. If nothing has been explicitly set, the default is to
1809	emulate the curror keys. The syntax permits each arrow to be altered
1810	individually or all four at once without re-entering their common
1811	beginning/end text. For example, to explicitly associate cursor actions
1812	with the arrows, any of the following forms could be used:
1813
1814	=over 4
1815
1816	=item B<< <r>+I<Right> >>
1817
1818	=item B<< <l>+I<Left> >>
1819
1820	=item B<< <u>+I<Up> >>
1821
1822	=item B<< <d>+I<Down> >>
1823
1824	Define actions for the respective arrow buttons
1825
1826	=item B<< <b>+I<Begin> >>
1827
1828	=item B<< <e>+I<End> >>
1829
1830	Define common beginning/end parts for I<quick arrows> which used in
1831	conjunction with the above <r> <l> <u> <d> constructs
1832
1833	=back
1834
1835	=over 4
1836
1837	=item For example, define arrows individually,
1838
1839	<u>\E[A
1840
1841	<d>\E[B
1842
1843	<r>\E[C
1844
1845	<l>\E[D
1846
1847	=item or all at once
1848
1849	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
1850
1851	=item or more compactly (factoring out common parts)
1852
1853	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
1854
1855	=back
1856
1857	X<menuBarSummary>
1858
1859	=head2 Command Summary
1860
1861	A short summary of the most I<common> commands:
1862
1863	=over 4
1864
1865	=item [menu:name]
1866
1867	use an existing named menuBar or start a new one
1868
1869	=item [menu]
1870
1871	use the current menuBar
1872
1873	=item [title:string]
1874
1875	set menuBar title
1876
1877	=item [done]
1878
1879	set menu access to readonly and, if reading from a file, signal EOF
1880
1881	=item [done:name]
1882
1883	if reading from a file using [read:file;name] signal EOF
1884
1885	=item [rm:name]
1886
1887	remove named menuBar(s)
1888
1889	=item [rm] [rm:]
1890
1891	remove current menuBar
1892
1893	=item [rm*] [rm:*]
1894
1895	remove all menuBar(s)
1896
1897	=item [swap]
1898
1899	swap top two menuBars
1900
1901	=item [prev]
1902
1903	access the previous menuBar
1904
1905	=item [next]
1906
1907	access the next menuBar
1908
1909	=item [show]
1910
1911	map menuBar
1912
1913	=item [hide]
1914
1915	unmap menuBar
1916
1917	=item [pixmap;file]
1918
1919	=item [pixmap;file;scaling]
1920
1921	set a background pixmap
1922
1923	=item [read:file]
1924
1925	=item [read:file;name]
1926
1927	read in a menu from a file
1928
1929	=item [dump]
1930
1931	dump out all menuBars to /tmp/rxvt-PID
1932
1933	=item /
1934
1935	access menuBar top level
1936
1937	=item ./
1938
1939	=item ../
1940
1941	=item ../../
1942
1943	access current or parent menu level
1944
1945	=item /path/menu
1946
1947	add/access menu
1948
1949	=item /path/{-}
1950
1951	add separator
1952
1953	=item /path/{item}{rtext} action
1954
1955	add/alter menu item
1956
1957	=item -/*
1958
1959	remove all menus from the menuBar
1960
1961	=item -/path/menu
1962
1963	remove menu items, separators and submenus from menu
1964
1965	=item -/path/menu
1966
1967	remove menu
1968
1969	=item -/path/{item}
1970
1971	remove item
1972
1973	=item -/path/{-}
1974
1975	remove separator
1976
1977	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
1978
1979	menu quick arrows
1980
1981	=back
1982	X<XPM>
1983
1984	=head1 XPM
1985
1986	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	2037	For the BACGROUND IMAGE XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1987	of B<< C<Pt> >> can be the name of the background pixmap followed by a	2038	of B<< C<Pt> >> can be the name of the background image file followed by a
1988	sequence of scaling/positioning commands separated by semi-colons. The	2039	sequence of scaling/positioning commands separated by semi-colons. The
1989	scaling/positioning commands are as follows:	2040	scaling/positioning commands are as follows:
1990		2041
1991	=over 4	2042	=over 4
1992		2043
…		…
2030		2081
2031	For example:	2082	For example:
2032		2083
2033	=over 4	2084	=over 4
2034		2085
2035	=item B<\E]20;funky\a>	2086	=item B<\E]20;funky.jpg\a>
2036		2087
2037	load B<funky.xpm> as a tiled image	2088	load B<funky.jpg> as a tiled image
2038		2089
2039	=item B<\E]20;mona;100\a>	2090	=item B<\E]20;mona.jpg;100\a>
2040		2091
2041	load B<mona.xpm> with a scaling of 100%	2092	load B<mona.jpg> with a scaling of 100%
2042		2093
2043	=item B<\E]20;;200;?\a>	2094	=item B<\E]20;;200;?\a>
2044		2095
2045	rescale the current pixmap to 200% and display the image geometry in	2096	rescale the current pixmap to 200% and display the image geometry in
2046	the title	2097	the title
…		…
2085	=begin table	2136	=begin table
2086		2137
2087	4 Shift	2138	4 Shift
2088	8 Meta	2139	8 Meta
2089	16 Control	2140	16 Control
2090	32 Double Click I<(Rxvt extension)>	2141	32 Double Click I<(rxvt extension)>
2091		2142
2092	=end table	2143	=end table
2093		2144
2094	Col = B<< C<< <x> - SPACE >> >>	2145	Col = B<< C<< <x> - SPACE >> >>
2095		2146
…		…
2172	=end table	2223	=end table
2173		2224
2174	=head1 CONFIGURE OPTIONS	2225	=head1 CONFIGURE OPTIONS
2175		2226
2176	General hint: if you get compile errors, then likely your configuration	2227	General hint: if you get compile errors, then likely your configuration
2177	hasn't been tested well. Either try with --enable-everything or use the	2228	hasn't been tested well. Either try with C<--enable-everything> or use
2178	./reconf script as a base for experiments. ./reconf is used by myself,	2229	the default configuration (i.e. no C<--enable-xxx> or C<--disable-xxx>
2179	so it should generally be a working config. Of course, you should always	2230	switches). Of course, you should always report when a combination doesn't
2180	report when a combination doesn't work, so it can be fixed. Marc Lehmann	2231	work, so it can be fixed. Marc Lehmann <rxvt@schmorp.de>.
2181	<rxvt@schmorp.de>.	2232
		2233	All
2182		2234
2183	=over 4	2235	=over 4
2184		2236
2185	=item --enable-everything	2237	=item --enable-everything
2186		2238
2187	Add support for all non-multichoice options listed in "./configure	2239	Add (or remove) support for all non-multichoice options listed in "./configure
2188	--help". Note that unlike other enable options this is order dependant.	2240	--help".
		2241
2189	You can specify this and then disable options which this enables by	2242	You can specify this and then disable options you do not like by
2190	I<following> this with the appropriate commands.	2243	I<following> this with the appropriate C<--disable-...> arguments,
		2244	or you can start with a minimal configuration by specifying
		2245	C<--disable-everything> and than adding just the C<--enable-...> arguments
		2246	you want.
2191		2247
2192	=item --enable-xft	2248	=item --enable-xft (default: enabled)
2193		2249
2194	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2250	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
2195	slower and require lots of memory, but as long as you don't use them, you	2251	slower and require lots of memory, but as long as you don't use them, you
2196	don't pay for them.	2252	don't pay for them.
2197		2253
2198	=item --enable-font-styles	2254	=item --enable-font-styles (default: on)
2199		2255
2200	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2256	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2201	styles. The fonts can be set manually or automatically.	2257	styles. The fonts can be set manually or automatically.
2202		2258
2203	=item --with-codesets=NAME,...	2259	=item --with-codesets=NAME,... (default: all)
2204		2260
2205	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>	2261	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2206	are always compiled in, which includes most 8-bit character sets). These	2262	are always compiled in, which includes most 8-bit character sets). These
2207	codeset tables are used for driving X11 core fonts, they are not required	2263	codeset tables are used for driving X11 core fonts, they are not required
2208	for Xft fonts, although having them compiled in lets rxvt-unicode choose	2264	for Xft fonts, although having them compiled in lets rxvt-unicode choose
…		…
2212		2268
2213	=begin table	2269	=begin table
2214		2270
2215	all all available codeset groups	2271	all all available codeset groups
2216	zh common chinese encodings	2272	zh common chinese encodings
2217	zh_ext rarely used but very big chinese encodigs	2273	zh_ext rarely used but very big chinese encodings
2218	jp common japanese encodings	2274	jp common japanese encodings
2219	jp_ext rarely used but big japanese encodings	2275	jp_ext rarely used but big japanese encodings
2220	kr korean encodings	2276	kr korean encodings
2221		2277
2222	=end table	2278	=end table
2223		2279
2224	=item --enable-xim	2280	=item --enable-xim (default: on)
2225		2281
2226	Add support for XIM (X Input Method) protocol. This allows using	2282	Add support for XIM (X Input Method) protocol. This allows using
2227	alternative input methods (e.g. kinput2) and will also correctly	2283	alternative input methods (e.g. kinput2) and will also correctly
2228	set up the input for people using dead keys or compose keys.	2284	set up the input for people using dead keys or compose keys.
2229		2285
2230	=item --enable-unicode3	2286	=item --enable-unicode3 (default: off)
		2287
		2288	Recommended to stay off unless you really need non-BMP characters.
2231		2289
2232	Enable direct support for displaying unicode codepoints above	2290	Enable direct support for displaying unicode codepoints above
2233	65535 (the basic multilingual page). This increases storage	2291	65535 (the basic multilingual page). This increases storage
2234	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2292	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2235	support these extra characters, but Xft does.	2293	support these extra characters, but Xft does.
2236		2294
2237	Please note that rxvt-unicode can store unicode code points >65535	2295	Please note that rxvt-unicode can store unicode code points >65535
2238	even without this flag, but the number of such characters is	2296	even without this flag, but the number of such characters is
2239	limited to a view thousand (shared with combining characters,	2297	limited to a few thousand (shared with combining characters,
2240	see next switch), and right now rxvt-unicode cannot display them	2298	see next switch), and right now rxvt-unicode cannot display them
2241	(input/output and cut&paste still work, though).	2299	(input/output and cut&paste still work, though).
2242		2300
2243	=item --enable-combining	2301	=item --enable-combining (default: on)
2244		2302
2245	Enable automatic composition of combining characters into	2303	Enable automatic composition of combining characters into
2246	composite characters. This is required for proper viewing of text	2304	composite characters. This is required for proper viewing of text
2247	where accents are encoded as seperate unicode characters. This is	2305	where accents are encoded as seperate unicode characters. This is
2248	done by using precomposited characters when available or creating	2306	done by using precomposited characters when available or creating
2249	new pseudo-characters when no precomposed form exists.	2307	new pseudo-characters when no precomposed form exists.
2250		2308
2251	Without --enable-unicode3, the number of additional precomposed characters	2309	Without --enable-unicode3, the number of additional precomposed
2252	is rather limited (2048, if this is full, rxvt-unicode will use the	2310	characters is somewhat limited (the 6400 private use characters will be
2253	private use area, extending the number of combinations to 8448). With
2254	--enable-unicode3, no practical limit exists.	2311	(ab-)used). With --enable-unicode3, no practical limit exists.
2255		2312
2256	This option will also enable storage (but not display) of characters	2313	This option will also enable storage (but not display) of characters
2257	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2314	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2258		2315
2259	The combining table also contains entries for arabic presentation forms,	2316	The combining table also contains entries for arabic presentation forms,
2260	but these are not currently used. Bug me if you want these to be used (and	2317	but these are not currently used. Bug me if you want these to be used (and
2261	tell me how these are to be used...).	2318	tell me how these are to be used...).
2262		2319
2263	=item --enable-fallback(=CLASS)	2320	=item --enable-fallback(=CLASS) (default: Rxvt)
2264		2321
2265	When reading resource settings, also read settings for class CLASS	2322	When reading resource settings, also read settings for class CLASS. To
2266	(default: Rxvt). To disable resource fallback use --disable-fallback.	2323	disable resource fallback use --disable-fallback.
2267		2324
2268	=item --with-res-name=NAME	2325	=item --with-res-name=NAME (default: urxvt)
2269		2326
2270	Use the given name (default: urxvt) as default application name when	2327	Use the given name as default application name when
2271	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2328	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2272		2329
2273	=item --with-res-class=CLASS	2330	=item --with-res-class=CLASS /default: URxvt)
2274		2331
2275	Use the given class (default: URxvt) as default application class	2332	Use the given class as default application class
2276	when reading resources. Specify --with-res-class=Rxvt to replace	2333	when reading resources. Specify --with-res-class=Rxvt to replace
2277	rxvt.	2334	rxvt.
2278		2335
2279	=item --enable-utmp	2336	=item --enable-utmp (default: on)
2280		2337
2281	Write user and tty to utmp file (used by programs like F<w>) at	2338	Write user and tty to utmp file (used by programs like F<w>) at
2282	start of rxvt execution and delete information when rxvt exits.	2339	start of rxvt execution and delete information when rxvt exits.
2283		2340
2284	=item --enable-wtmp	2341	=item --enable-wtmp (default: on)
2285		2342
2286	Write user and tty to wtmp file (used by programs like F<last>) at	2343	Write user and tty to wtmp file (used by programs like F<last>) at
2287	start of rxvt execution and write logout when rxvt exits. This	2344	start of rxvt execution and write logout when rxvt exits. This
2288	option requires --enable-utmp to also be specified.	2345	option requires --enable-utmp to also be specified.
2289		2346
2290	=item --enable-lastlog	2347	=item --enable-lastlog (default: on)
2291		2348
2292	Write user and tty to lastlog file (used by programs like	2349	Write user and tty to lastlog file (used by programs like
2293	F<lastlogin>) at start of rxvt execution. This option requires	2350	F<lastlogin>) at start of rxvt execution. This option requires
2294	--enable-utmp to also be specified.	2351	--enable-utmp to also be specified.
2295		2352
2296	=item --enable-xpm-background	2353	=item --enable-afterimage (default: on)
2297		2354
2298	Add support for XPM background pixmaps.	2355	Add support for libAfterImage to be used for transparency and background
		2356	images. It adds support for many file formats including JPG, PNG,
		2357	SVG, TIFF, GIF, XPM, BMP, ICO, XCF, TGA and AfterStep image XML
		2358	(L<http://www.afterstep.org/visualdoc.php?show=asimagexml>).
2299		2359
		2360	This option also adds such eye candy as blending an image over the root
		2361	background, as well as dynamic scaling and bluring of background images.
		2362
		2363	Note that with this option enabled, @@RXVT_NAME@@'s memory footprint might
		2364	increase by a few megabytes even if no extra features are used (mostly due
		2365	to third-party libraries used by libAI). Memory footprint may somewhat be
		2366	lowered if libAfterImage is configured without support for SVG.
		2367
2300	=item --enable-transparency	2368	=item --enable-transparency (default: on)
2301		2369
2302	Add support for inheriting parent backgrounds thus giving a fake	2370	Add support for backgrounds, creating illusion of transparency in the term.
2303	transparency to the term.
2304		2371
2305	=item --enable-fading	2372	=item --enable-fading (default: on)
2306		2373
2307	Add support for fading the text when focus is lost.	2374	Add support for fading the text when focus is lost.
2308		2375
2309	=item --enable-tinting
2310
2311	Add support for tinting of transparent backgrounds.
2312
2313	=item --enable-menubar
2314
2315	Add support for our menu bar system (this interacts badly with
2316	dynamic locale switching currently).
2317
2318	=item --enable-rxvt-scroll	2376	=item --enable-rxvt-scroll (default: on)
2319		2377
2320	Add support for the original rxvt scrollbar.	2378	Add support for the original rxvt scrollbar.
2321		2379
2322	=item --enable-next-scroll	2380	=item --enable-next-scroll (default: on)
2323		2381
2324	Add support for a NeXT-like scrollbar.	2382	Add support for a NeXT-like scrollbar.
2325		2383
2326	=item --enable-xterm-scroll	2384	=item --enable-xterm-scroll (default: on)
2327		2385
2328	Add support for an Xterm-like scrollbar.	2386	Add support for an Xterm-like scrollbar.
2329		2387
2330	=item --enable-plain-scroll	2388	=item --enable-plain-scroll (default: on)
2331		2389
2332	Add support for a very unobtrusive, plain-looking scrollbar that	2390	Add support for a very unobtrusive, plain-looking scrollbar that
2333	is the favourite of the rxvt-unicode author, having used it for	2391	is the favourite of the rxvt-unicode author, having used it for
2334	many years.	2392	many years.
2335		2393
2336	=item --enable-half-shadow	2394	=item --enable-ttygid (default: off)
2337
2338	Make shadows on the scrollbar only half the normal width & height.
2339	only applicable to rxvt scrollbars.
2340
2341	=item --enable-ttygid
2342		2395
2343	Change tty device setting to group "tty" - only use this if	2396	Change tty device setting to group "tty" - only use this if
2344	your system uses this type of security.	2397	your system uses this type of security.
2345		2398
2346	=item --disable-backspace-key	2399	=item --disable-backspace-key
2347		2400
2348	Disable any handling of the backspace key by us - let the X server	2401	Removes any handling of the backspace key by us - let the X server do it.
		2402
		2403	=item --disable-delete-key
		2404
		2405	Removes any handling of the delete key by us - let the X server
2349	do it.	2406	do it.
2350		2407
2351	=item --disable-delete-key
2352
2353	Disable any handling of the delete key by us - let the X server
2354	do it.
2355
2356	=item --disable-resources	2408	=item --disable-resources
2357		2409
2358	Remove all resources checking.	2410	Removes any support for resource checking.
2359
2360	=item --enable-xgetdefault
2361
2362	Make resources checking via XGetDefault() instead of our small
2363	version which only checks ~/.Xdefaults, or if that doesn't exist then
2364	~/.Xresources.
2365
2366	Please note that nowadays, things like XIM will automatically pull in and
2367	use the full X resource manager, so the overhead of using it might be very
2368	small, if nonexistant.
2369
2370	=item --enable-strings
2371
2372	Add support for our possibly faster memset() function and other
2373	various routines, overriding your system's versions which may
2374	have been hand-crafted in assembly or may require extra libraries
2375	to link in. (this breaks ANSI-C rules and has problems on many
2376	GNU/Linux systems).
2377		2411
2378	=item --disable-swapscreen	2412	=item --disable-swapscreen
2379		2413
2380	Remove support for swap screen.	2414	Remove support for secondary/swap screen.
2381		2415
2382	=item --enable-frills	2416	=item --enable-frills (default: on)
2383		2417
2384	Add support for many small features that are not essential but nice to	2418	Add support for many small features that are not essential but nice to
2385	have. Normally you want this, but for very small binaries you may want to	2419	have. Normally you want this, but for very small binaries you may want to
2386	disable this.	2420	disable this.
2387		2421
2388	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2422	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2389	in combination with other switches) is:	2423	in combination with other switches) is:
2390		2424
2391	MWM-hints	2425	MWM-hints
2392	EWMH-hints (pid, utf8 names) and protocols (ping)	2426	EWMH-hints (pid, utf8 names) and protocols (ping)
		2427	urgency hint
2393	seperate underline colour	2428	seperate underline colour (-underlineColor)
2394	settable border widths and borderless switch	2429	settable border widths and borderless switch (-w, -b, -bl)
		2430	visual depth selection (-depth)
2395	settable extra linespacing	2431	settable extra linespacing /-lsp)
2396	iso-14755-2 and -3, and visual feedback	2432	iso-14755 5.1 (basic) support
		2433	tripleclickwords (-tcw)
		2434	settable insecure mode (-insecure)
		2435	keysym remapping support
		2436	cursor blinking and underline cursor (-cb, -uc)
		2437	XEmbed support (-embed)
		2438	user-pty (-pty-fd)
		2439	hold on exit (-hold)
		2440	skip builtin block graphics (-sbg)
		2441	separate highlightcolor support (-hc)
		2442
		2443	It also enables some non-essential features otherwise disabled, such as:
		2444
		2445	some round-trip time optimisations
		2446	nearest color allocation on pseudocolor screens
		2447	UTF8_STRING support for selection
		2448	sgr modes 90..97 and 100..107
2397	backindex and forwardindex escape sequence	2449	backindex and forwardindex escape sequences
		2450	view change/zero scrollback escape sequences
		2451	locale switching escape sequence
2398	window op and some xterm/OSC escape sequences	2452	window op and some xterm/OSC escape sequences
2399	tripleclickwords	2453	rectangular selections
2400	settable insecure mode	2454	trailing space removal for selections
2401	keysym remapping support	2455	verbose X error handling
2402	cursor blinking and underline cursor
2403	-embed and -pty-fd options
2404		2456
2405	=item --enable-iso14755	2457	=item --enable-iso14755 (default: on)
2406		2458
2407	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2459	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2408	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2460	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
2409	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with	2461	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2410	this switch.	2462	this switch.
2411		2463
2412	=item --enable-keepscrolling	2464	=item --enable-keepscrolling (default: on)
2413		2465
2414	Add support for continual scrolling of the display when you hold	2466	Add support for continual scrolling of the display when you hold
2415	the mouse button down on a scrollbar arrow.	2467	the mouse button down on a scrollbar arrow.
2416		2468
		2469	=item --enable-selectionscrolling (default: on)
		2470
		2471	Add support for scrolling when the selection moves to the top or
		2472	bottom of the screen.
		2473
2417	=item --enable-mousewheel	2474	=item --enable-mousewheel (default: on)
2418		2475
2419	Add support for scrolling via mouse wheel or buttons 4 & 5.	2476	Add support for scrolling via mouse wheel or buttons 4 & 5.
2420		2477
2421	=item --enable-slipwheeling	2478	=item --enable-slipwheeling (default: on)
2422		2479
2423	Add support for continual scrolling (using the mouse wheel as an	2480	Add support for continual scrolling (using the mouse wheel as an
2424	accelerator) while the control key is held down. This option	2481	accelerator) while the control key is held down. This option
2425	requires --enable-mousewheel to also be specified.	2482	requires --enable-mousewheel to also be specified.
2426		2483
2427	=item --disable-new-selection
2428
2429	Remove support for mouse selection style like that of xterm.
2430
2431	=item --enable-dmalloc
2432
2433	Use Gray Watson's malloc - which is good for debugging See
2434	http://www.letters.com/dmalloc/ for details If you use either this or the
2435	next option, you may need to edit src/Makefile after compiling to point
2436	DINCLUDE and DLIB to the right places.
2437
2438	You can only use either this option and the following (should
2439	you use either) .
2440
2441	=item --enable-dlmalloc
2442
2443	Use Doug Lea's malloc - which is good for a production version
2444	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2445
2446	=item --enable-smart-resize	2484	=item --enable-smart-resize (default: off)
2447		2485
2448	Add smart growth/shrink behaviour when changing font size via from hot	2486	Add smart growth/shrink behaviour when resizing.
2449	keys. This should keep in a fixed position the rxvt corner which is	2487	This should keep the window corner which is closest to a corner of
2450	closest to a corner of the screen.	2488	the screen in a fixed position.
2451		2489
2452	=item --enable-pointer-blank	2490	=item --enable-pointer-blank (default: on)
2453		2491
2454	Add support to have the pointer disappear when typing or inactive.	2492	Add support to have the pointer disappear when typing or inactive.
2455		2493
2456	=item --with-name=NAME	2494	=item --enable-perl (default: on)
2457		2495
		2496	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
		2497	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the
		2498	files in F<src/perl-ext/> for the extensions that are installed by
		2499	default. The perl interpreter that is used can be specified via the
		2500	C<PERL> environment variable when running configure. Even when compiled
		2501	in, perl will I<not> be initialised when all extensions have been disabled
		2502	C<-pe "" --perl-ext-common "">, so it should be safe to enable from a
		2503	resource standpoint.
		2504
		2505	=item --with-afterimage-config=DIR
		2506
		2507	Look for the libAfterImage config script in DIR.
		2508
		2509	=item --with-name=NAME (default: urxvt)
		2510
2458	Set the basename for the installed binaries (default: C<urxvt>, resulting	2511	Set the basename for the installed binaries, resulting
2459	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2512	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
2460	C<rxvt>.	2513	C<rxvt>.
2461		2514
2462	=item --with-term=NAME	2515	=item --with-term=NAME (default: rxvt-unicode)
2463		2516
2464	Change the environmental variable for the terminal to NAME (default	2517	Change the environmental variable for the terminal to NAME.
2465	C<rxvt-unicode>)
2466		2518
2467	=item --with-terminfo=PATH	2519	=item --with-terminfo=PATH
2468		2520
2469	Change the environmental variable for the path to the terminfo tree to	2521	Change the environmental variable for the path to the terminfo tree to
2470	PATH.	2522	PATH.
2471		2523
2472	=item --with-x	2524	=item --with-x
2473		2525
2474	Use the X Window System (pretty much default, eh?).	2526	Use the X Window System (pretty much default, eh?).
2475
2476	=item --with-xpm-includes=DIR
2477
2478	Look for the XPM includes in DIR.
2479
2480	=item --with-xpm-library=DIR
2481
2482	Look for the XPM library in DIR.
2483
2484	=item --with-xpm
2485
2486	Not needed - define via --enable-xpm-background.
2487		2527
2488	=back	2528	=back
2489		2529
2490	=head1 AUTHORS	2530	=head1 AUTHORS
2491		2531

Diff Legend

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