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

Diff Legend

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