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.113 by root, Thu Feb 2 18:04:45 2006 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/*checkout*/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 wether 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<pod2html>. Then go to
		131	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 unreasnobaly 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, transparency isn't officially supported in rxvt-unicode, so
		215	you are mostly on your own. Do not bug the author about it (but you may
		216	bug everybody else). Also, if you can't get it working consider it a rite
		217	of passage: ... and you failed.
		218
		219	Here are four ways to get transparency. B<Do> read the manpage and option
		220	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
		221
		222	1. Use inheritPixmap:
		223
		224	Esetroot wallpaper.jpg
		225	@@URXVT_NAME@@ -ip -tint red -sh 40
		226
		227	That works. If you think it doesn't, you lack transparency and tinting
		228	support, or you are unable to read.
		229
		230	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		231	to use effects other than tinting and shading: Just shade/tint/whatever
		232	your picture with gimp or any other tool:
		233
		234	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		235	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
		236
		237	That works. If you think it doesn't, you lack XPM and Perl support, or you
		238	are unable to read.
		239
		240	3. Use an ARGB visual:
		241
		242	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		243
		244	This requires XFT support, and the support of your X-server. If that
		245	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		246	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		247	bugfixes and workarounds for Xft and Xlib to make it work, but that
		248	doesn't mean that your WM has the required kludges in place.
		249
		250	4. Use xcompmgr and let it do the job:
		251
		252	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		253	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		254
		255	Then click on a window you want to make transparent. Replace C<0xc0000000>
		256	by other values to change the degree of opacity. If it doesn't work and
		257	your server crashes, you got to keep the pieces.
		258
		259	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		260
		261	Most fonts were not designed for terminal use, which means that character
		262	size varies a lot. A font that is otherwise fine for terminal use might
		263	contain some characters that are simply too wide. Rxvt-unicode will avoid
		264	these characters. For characters that are just "a bit" too wide a special
		265	"careful" rendering mode is used that redraws adjacent characters.
		266
		267	All of this requires that fonts do not lie about character sizes,
		268	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		269	box, and rxvt-unicode has no way of detecting this (the correct way is to
		270	ask for the character bounding box, which unfortunately is wrong in these
		271	cases).
		272
		273	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		274	or the respective font. If you encounter this problem you might try using
		275	the C<-lsp> option to give the font more height. If that doesn't work, you
		276	might be forced to use a different font.
		277
		278	All of this is not a problem when using X11 core fonts, as their bounding
		279	box data is correct.
		280
		281	=head3 How can I keep rxvt-unicode from using reverse video so much?
		282
		283	First of all, make sure you are running with the right terminal settings
		284	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		285	make sure you have specified colours for italic and bold, as otherwise
		286	rxvt-unicode might use reverse video to simulate the effect:
		287
		288	URxvt.colorBD: white
		289	URxvt.colorIT: green
		290
		291	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		292
		293	For some unexplainable reason, some rare programs assume a very weird
		294	colour palette when confronted with a terminal with more than the standard
		295	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		296	these programs not to assume non-ISO colours without very good reasons.
		297
		298	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		299	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		300	fix colours but keep you from using other rxvt-unicode features.
		301
		302	=head3 Can I switch the fonts at runtime?
		303
		304	Yes, using an escape sequence. Try something like this, which has the same
		305	effect as using the C<-fn> switch, and takes effect immediately:
		306
		307	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		308
		309	This is useful if you e.g. work primarily with japanese (and prefer a
		310	japanese font), but you have to switch to chinese temporarily, where
		311	japanese fonts would only be in your way.
		312
		313	You can think of this as a kind of manual ISO-2022 switching.
		314
		315	=head3 Why do italic characters look as if clipped?
		316
		317	Many fonts have difficulties with italic characters and hinting. For
		318	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		319	Mono> completely fails in it's italic face. A workaround might be to
		320	enable freetype autohinting, i.e. like this:
		321
		322	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		323	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		324
		325	=head3 Can I speed up Xft rendering somehow?
		326
		327	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		328	it is simply slow. If you still want Xft fonts you might try to disable
		329	antialiasing (by appending C<:antialias=false>), which saves lots of
		330	memory and also speeds up rendering considerably.
		331
		332	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		333
		334	Rxvt-unicode will use whatever you specify as a font. If it needs to
		335	fall back to it's default font search list it will prefer X11 core
		336	fonts, because they are small and fast, and then use Xft fonts. It has
		337	antialiasing disabled for most of them, because the author thinks they
		338	look best that way.
		339
		340	If you want antialiasing, you have to specify the fonts manually.
		341
		342	=head3 What's with this bold/blink stuff?
		343
		344	If no bold colour is set via C<colorBD:>, bold will invert text using the
		345	standard foreground colour.
		346
		347	For the standard background colour, blinking will actually make the
		348	text blink when compiled with C<--enable-blinking>. with standard
		349	colours. Without C<--enable-blinking>, the blink attribute will be
		350	ignored.
		351
		352	On ANSI colours, bold/blink attributes are used to set high-intensity
		353	foreground/background colors.
		354
		355	color0-7 are the low-intensity colors.
		356
		357	color8-15 are the corresponding high-intensity colors.
		358
		359	=head3 I don't like the screen colors. How do I change them?
		360
		361	You can change the screen colors at run-time using F<~/.Xdefaults>
		362	resources (or as long-options).
		363
		364	Here are values that are supposed to resemble a VGA screen,
		365	including the murky brown that passes for low-intensity yellow:
		366
		367	URxvt.color0: #000000
		368	URxvt.color1: #A80000
		369	URxvt.color2: #00A800
		370	URxvt.color3: #A8A800
		371	URxvt.color4: #0000A8
		372	URxvt.color5: #A800A8
		373	URxvt.color6: #00A8A8
		374	URxvt.color7: #A8A8A8
		375
		376	URxvt.color8: #000054
		377	URxvt.color9: #FF0054
		378	URxvt.color10: #00FF54
		379	URxvt.color11: #FFFF54
		380	URxvt.color12: #0000FF
		381	URxvt.color13: #FF00FF
		382	URxvt.color14: #00FFFF
		383	URxvt.color15: #FFFFFF
		384
		385	And here is a more complete set of non-standard colors.
		386
		387	URxvt.cursorColor: #dc74d1
		388	URxvt.pointerColor: #dc74d1
		389	URxvt.background: #0e0e0e
		390	URxvt.foreground: #4ad5e1
		391	URxvt.color0: #000000
		392	URxvt.color8: #8b8f93
		393	URxvt.color1: #dc74d1
		394	URxvt.color9: #dc74d1
		395	URxvt.color2: #0eb8c7
		396	URxvt.color10: #0eb8c7
		397	URxvt.color3: #dfe37e
		398	URxvt.color11: #dfe37e
		399	URxvt.color5: #9e88f0
		400	URxvt.color13: #9e88f0
		401	URxvt.color6: #73f7ff
		402	URxvt.color14: #73f7ff
		403	URxvt.color7: #e1dddd
		404	URxvt.color15: #e1dddd
		405
		406	They have been described (not by me) as "pretty girly".
		407
		408	=head3 Why do some characters look so much different than others?
		409
		410	See next entry.
		411
		412	=head3 How does rxvt-unicode choose fonts?
		413
		414	Most fonts do not contain the full range of Unicode, which is
		415	fine. Chances are that the font you (or the admin/package maintainer of
		416	your system/os) have specified does not cover all the characters you want
		417	to display.
		418
		419	B<rxvt-unicode> makes a best-effort try at finding a replacement
		420	font. Often the result is fine, but sometimes the chosen font looks
		421	bad/ugly/wrong. Some fonts have totally strange characters that don't
		422	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		423	intelligence to detect that a specific glyph is wrong: it has to believe
		424	the font that the characters it claims to contain indeed look correct.
		425
		426	In that case, select a font of your taste and add it to the font list,
		427	e.g.:
		428
		429	@@URXVT_NAME@@ -fn basefont,font2,font3...
		430
		431	When rxvt-unicode sees a character, it will first look at the base
		432	font. If the base font does not contain the character, it will go to the
		433	next font, and so on. Specifying your own fonts will also speed up this
		434	search and use less resources within rxvt-unicode and the X-server.
		435
		436	The only limitation is that none of the fonts may be larger than the base
		437	font, as the base font defines the terminal character cell size, which
		438	must be the same due to the way terminals work.
		439
		440	=head3 Why do some chinese characters look so different than others?
		441
		442	This is because there is a difference between script and language --
		443	rxvt-unicode does not know which language the text that is output is,
		444	as it only knows the unicode character codes. If rxvt-unicode first
		445	sees a japanese/chinese character, it might choose a japanese font for
		446	display. Subsequent japanese characters will use that font. Now, many
		447	chinese characters aren't represented in japanese fonts, so when the first
		448	non-japanese character comes up, rxvt-unicode will look for a chinese font
		449	-- unfortunately at this point, it will still use the japanese font for
		450	chinese characters that are also in the japanese font.
		451
		452	The workaround is easy: just tag a chinese font at the end of your font
		453	list (see the previous question). The key is to view the font list as
		454	a preference list: If you expect more japanese, list a japanese font
		455	first. If you expect more chinese, put a chinese font first.
		456
		457	In the future it might be possible to switch language preferences at
		458	runtime (the internal data structure has no problem with using different
		459	fonts for the same character at the same time, but no interface for this
		460	has been designed yet).
		461
		462	Until then, you might get away with switching fonts at runtime (see L<Can
		463	I switch the fonts at runtime?> later in this document).
		464
		465	=head2 Keyboard, Mouse & User Interaction
		466
		467	=head3 The new selection selects pieces that are too big, how can I select single words?
		468
		469	If you want to select e.g. alphanumeric words, you can use the following
		470	setting:
		471
		472	URxvt.selection.pattern-0: ([[:word:]]+)
		473
		474	If you click more than twice, the selection will be extended
		475	more and more.
		476
		477	To get a selection that is very similar to the old code, try this pattern:
		478
		479	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		480
		481	Please also note that the I<LeftClick Shift-LeftClik> combination also
		482	selects words like the old code.
		483
		484	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		485
		486	You can disable the perl extension completely by setting the
		487	B<perl-ext-common> resource to the empty string, which also keeps
		488	rxvt-unicode from initialising perl, saving memory.
		489
		490	If you only want to disable specific features, you first have to
		491	identify which perl extension is responsible. For this, read the section
		492	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		493	example, to disable the B<selection-popup> and B<option-popup>, specify
		494	this B<perl-ext-common> resource:
		495
		496	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		497
		498	This will keep the default extensions, but disable the two popup
		499	extensions. Some extensions can also be configured, for example,
		500	scrollback search mode is triggered by B<M-s>. You can move it to any
		501	other combination either by setting the B<searchable-scrollback> resource:
		502
		503	URxvt.searchable-scrollback: CM-s
		504
		505	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		506
		507	See next entry.
		508
		509	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		510
		511	These are caused by the C<readline> perl extension. Under normal
		512	circumstances, it will move your cursor around when you click into the
		513	line that contains it. It tries hard not to do this at the wrong moment,
		514	but when running a program that doesn't parse cursor movements or in some
		515	cases during rlogin sessions, it fails to detect this properly.
		516
		517	You can permamently switch this feature off by disabling the C<readline>
		518	extension:
		519
		520	URxvt.perl-ext-common: default,-readline
		521
		522	=head3 My numerical keypad acts weird and generates differing output?
		523
		524	Some Debian GNUL/Linux users seem to have this problem, although no
		525	specific details were reported so far. It is possible that this is caused
		526	by the wrong C<TERM> setting, although the details of wether and how
		527	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		528	keymap. See the answer to the previous question, and please report if that
		529	helped.
		530
		531	=head3 My Compose (Multi_key) key is no longer working.
		532
		533	The most common causes for this are that either your locale is not set
		534	correctly, or you specified a B<preeditStyle> that is not supported by
		535	your input method. For example, if you specified B<OverTheSpot> and
		536	your input method (e.g. the default input method handling Compose keys)
		537	does not support this (for instance because it is not visual), then
		538	rxvt-unicode will continue without an input method.
		539
		540	In this case either do not specify a B<preeditStyle> or specify more than
		541	one pre-edit style, such as B<OverTheSpot,Root,None>.
		542
		543	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		544
		545	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		546	international keyboards) or simply use ISO 14755 support to your
		547	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		548	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		549	character and so on.
		550
		551	=head3 Mouse cut/paste suddenly no longer works.
		552
		553	Make sure that mouse reporting is actually turned off since killing
		554	some editors prematurely may leave the mouse in mouse report mode. I've
		555	heard that tcsh may use mouse reporting unless it otherwise specified. A
		556	quick check is to see if cut/paste works when the Alt or Shift keys are
		557	depressed.
		558
		559	=head3 What's with the strange Backspace/Delete key behaviour?
		560
		561	Assuming that the physical Backspace key corresponds to the
		562	BackSpace keysym (not likely for Linux ... see the following
		563	question) there are two standard values that can be used for
		564	Backspace: C<^H> and C<^?>.
		565
		566	Historically, either value is correct, but rxvt-unicode adopts the debian
		567	policy of using C<^?> when unsure, because it's the one only only correct
		568	choice :).
		569
		570	Rxvt-unicode tries to inherit the current stty settings and uses the value
		571	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		572	started from a terminal (say, from a menu or by remote shell), then the
		573	system value of `erase', which corresponds to CERASE in <termios.h>, will
		574	be used (which may not be the same as your stty setting).
		575
		576	For starting a new rxvt-unicode:
		577
		578	# use Backspace = ^H
		579	$ stty erase ^H
		580	$ @@URXVT_NAME@@
		581
		582	# use Backspace = ^?
		583	$ stty erase ^?
		584	$ @@URXVT_NAME@@
		585
		586	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		587
		588	For an existing rxvt-unicode:
		589
		590	# use Backspace = ^H
		591	$ stty erase ^H
		592	$ echo -n "^[[36h"
		593
		594	# use Backspace = ^?
		595	$ stty erase ^?
		596	$ echo -n "^[[36l"
		597
		598	This helps satisfy some of the Backspace discrepancies that occur, but
		599	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		600	properly reflects that.
		601
		602	The Delete key is a another casualty of the ill-defined Backspace problem.
		603	To avoid confusion between the Backspace and Delete keys, the Delete
		604	key has been assigned an escape sequence to match the vt100 for Execute
		605	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		606
		607	Some other Backspace problems:
		608
		609	some editors use termcap/terminfo,
		610	some editors (vim I'm told) expect Backspace = ^H,
		611	GNU Emacs (and Emacs-like editors) use ^H for help.
		612
		613	Perhaps someday this will all be resolved in a consistent manner.
		614
		615	=head3 I don't like the key-bindings. How do I change them?
		616
		617	There are some compile-time selections available via configure. Unless
		618	you have run "configure" with the C<--disable-resources> option you can
		619	use the `keysym' resource to alter the keystrings associated with keysyms.
		620
		621	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		622
		623	URxvt.keysym.Home: \033[1~
		624	URxvt.keysym.End: \033[4~
		625	URxvt.keysym.C-apostrophe: \033<C-'>
		626	URxvt.keysym.C-slash: \033<C-/>
		627	URxvt.keysym.C-semicolon: \033<C-;>
		628	URxvt.keysym.C-grave: \033<C-`>
		629	URxvt.keysym.C-comma: \033<C-,>
		630	URxvt.keysym.C-period: \033<C-.>
		631	URxvt.keysym.C-0x60: \033<C-`>
		632	URxvt.keysym.C-Tab: \033<C-Tab>
		633	URxvt.keysym.C-Return: \033<C-Return>
		634	URxvt.keysym.S-Return: \033<S-Return>
		635	URxvt.keysym.S-space: \033<S-Space>
		636	URxvt.keysym.M-Up: \033<M-Up>
		637	URxvt.keysym.M-Down: \033<M-Down>
		638	URxvt.keysym.M-Left: \033<M-Left>
		639	URxvt.keysym.M-Right: \033<M-Right>
		640	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		641	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		642	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		643
		644	See some more examples in the documentation for the B<keysym> resource.
		645
		646	=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
		647
		648	KP_Insert == Insert
		649	F22 == Print
		650	F27 == Home
		651	F29 == Prior
		652	F33 == End
		653	F35 == Next
		654
		655	Rather than have rxvt-unicode try to accommodate all the various possible
		656	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		657	required for your particular machine.
		658
		659
		660
		661	=head2 Terminal Configuration
		662
		663	=head3 Why doesn't rxvt-unicode read my resources?
		664
		665	Well, why, indeed? It does, in a way very similar to other X
		666	applications. Most importantly, this means that if you or your OS loads
		667	resources into the X display (the right way to do it), rxvt-unicode will
		668	ignore any resource files in your home directory. It will only read
		669	F<$HOME/.Xdefaults> when no resources are attached to the display.
		670
		671	If you have or use an F<$HOME/.Xresources> file, chances are that
		672	resources are loaded into your X-server. In this case, you have to
		673	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		674
		675	Also consider the form resources have to use:
		676
		677	URxvt.resource: value
		678
		679	If you want to use another form (there are lots of different ways of
		680	specifying resources), make sure you understand wether and why it
		681	works. If unsure, use the form above.
		682
49	=item When I log-in to another system it tells me about missing terminfo data?	683	=head3 When I log-in to another system it tells me about missing terminfo data?
50		684
51	The terminal description used by rxvt-unicode is not as widely available	685	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).	686	as that for xterm, or even rxvt (for which the same problem often arises).
53		687
54	The correct solution for this problem is to install the terminfo, this can	688	The correct solution for this problem is to install the terminfo, this can
…		…
70	resource to set it:	704	resource to set it:
71		705
72	URxvt.termName: rxvt	706	URxvt.termName: rxvt
73		707
74	If you don't plan to use B<rxvt> (quite common...) you could also replace	708	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.	709	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
76		710
		711	=head3 C<tic> outputs some error when compiling the terminfo entry.
		712
		713	Most likely it's the empty definition for C<enacs=>. Just replace it by
		714	C<enacs=\E[0@> and try again.
		715
77	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	716	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
78		717
		718	See next entry.
		719
79	=item I need a termcap file entry.	720	=head3 I need a termcap file entry.
80		721
81	One reason you might want this is that some distributions or operating	722	One reason you might want this is that some distributions or operating
82	systems still compile some programs using the long-obsoleted termcap	723	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	724	library (Fedora Core's bash is one example) and rely on a termcap entry
84	for C<rxvt-unicode>.	725	for C<rxvt-unicode>.
…		…
110	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	751	: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:\	752	: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:\	753	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
113	:vs=\E[?25h:	754	:vs=\E[?25h:
114		755
115	=item Why does C<ls> no longer have coloured output?	756	=head3 Why does C<ls> no longer have coloured output?
116		757
117	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	758	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	759	decide wether a terminal has colour, but uses it's own configuration
119	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	760	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
120	with most other terminals supporting colour). Either add:	761	with most other terminals supporting colour). Either add:
…		…
125		766
126	alias ls='ls --color=auto'	767	alias ls='ls --color=auto'
127		768
128	to your C<.profile> or C<.bashrc>.	769	to your C<.profile> or C<.bashrc>.
129		770
130	=item Why doesn't vim/emacs etc. use the 88 colour mode?	771	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
131		772
		773	See next entry.
		774
132	=item Why doesn't vim/emacs etc. make use of italic?	775	=head3 Why doesn't vim/emacs etc. make use of italic?
133		776
		777	See next entry.
		778
134	=item Why are the secondary screen-related options not working properly?	779	=head3 Why are the secondary screen-related options not working properly?
135		780
136	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	781	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
137	distributions (most notably Debian GNU/Linux) break rxvt-unicode	782	distributions (most notably Debian GNU/Linux) break rxvt-unicode
138	by setting C<TERM> to C<rxvt>, which doesn't have these extra	783	by setting C<TERM> to C<rxvt>, which doesn't have these extra
139	features. Unfortunately, some of these (most notably, again, Debian	784	features. Unfortunately, some of these (most notably, again, Debian
140	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	785	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	786	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	787	I log-in to another system it tells me about missing terminfo data?> on
143	how to do this).	788	how to do this).
144		789
145	=item My numerical keypad acts weird and generates differing output?
146		790
147	Some Debian GNUL/Linux users seem to have this problem, although no	791	=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		792
154	=item Rxvt-unicode does not seem to understand the selected encoding?	793	=head3 Rxvt-unicode does not seem to understand the selected encoding?
155		794
		795	See next entry.
		796
156	=item Unicode does not seem to work?	797	=head3 Unicode does not seem to work?
157		798
158	If you encounter strange problems like typing an accented character but	799	If you encounter strange problems like typing an accented character but
159	getting two unrelated other characters or similar, or if program output is	800	getting two unrelated other characters or similar, or if program output is
160	subtly garbled, then you should check your locale settings.	801	subtly garbled, then you should check your locale settings.
161		802
…		…
181		822
182	If nothing works and you are sure that everything is set correctly then	823	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	824	you will need to remember a little known fact: Some programs just don't
184	support locales :(	825	support locales :(
185		826
186	=item Why do some characters look so much different than others?	827	=head3 How does rxvt-unicode determine the encoding to use?
187		828
188	=item How does rxvt-unicode choose fonts?	829	See next entry.
189		830
190	Most fonts do not contain the full range of Unicode, which is	831	=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		832
195	B<rxvt-unicode> makes a best-effort try at finding a replacement	833	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	834	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	835	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		836
202	In that case, select a font of your taste and add it to the font list,	837	The reasons is that there exists a perfectly fine mechanism for selecting
203	e.g.:	838	the encoding, doing I/O and (most important) communicating this to all
204		839	applications so everybody agrees on character properties such as width
205	@@RXVT_NAME@@ -fn basefont,font2,font3...	840	and code number. This mechanism is the I<locale>. Applications not using
206		841	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	842	characters wrong as it uses it's 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).	843	locales).
254		844
255	It's not clear (to me at least), wether this is a bug in Xft, freetype,	845	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	846	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	847	interpretation of characters.
258	might be forced to use a different font.
259		848
260	All of this is not a problem when using X11 core fonts, as their bounding	849	Unfortunately, there is no system-independent way to select locales, nor
261	box data is correct.	850	is there a standard on how locale specifiers will look like.
262		851
		852	On most systems, the content of the C<LC_CTYPE> environment variable
		853	contains an arbitrary string which corresponds to an already-installed
		854	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		855	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		856	(i.e. C<de> or C<german>) are also common.
		857
		858	Rxvt-unicode ignores all other locale categories, and except for
		859	the encoding, ignores country or language-specific settings,
		860	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		861	rxvt-unicode.
		862
		863	If you want to use a specific encoding you have to make sure you start
		864	rxvt-unicode with the correct C<LC_CTYPE> category.
		865
		866	=head3 Can I switch locales at runtime?
		867
		868	Yes, using an escape sequence. Try something like this, which sets
		869	rxvt-unicode's idea of C<LC_CTYPE>.
		870
		871	printf '\e]701;%s\007' ja_JP.SJIS
		872
		873	See also the previous answer.
		874
		875	Sometimes this capability is rather handy when you want to work in
		876	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		877	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		878	first switches to a locale supported by xjdic and back later:
		879
		880	printf '\e]701;%s\007' ja_JP.SJIS
		881	xjdic -js
		882	printf '\e]701;%s\007' de_DE.UTF-8
		883
		884	You can also use xterm's C<luit> program, which usually works fine, except
		885	for some locales where character width differs between program- and
		886	rxvt-unicode-locales.
		887
		888	=head3 I have problems getting my input method working.
		889
		890	Try a search engine, as this is slightly different for every input method server.
		891
		892	Here is a checklist:
		893
		894	=over 4
		895
		896	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		897
		898	Try C<locale -a> or check the documentation for your OS.
		899
		900	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		901
		902	For example, B<kinput2> does not support UTF-8 locales, you should use
		903	C<ja_JP.EUC-JP> or equivalent.
		904
		905	=item - Make sure your XIM server is actually running.
		906
		907	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		908
		909	When you want to use e.g. B<kinput2>, it must be set to
		910	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input
		911	method servers are running with this command:
		912
		913	xprop -root XIM_SERVERS
		914
		915	=item
		916
		917	=back
		918
		919	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		920
		921	You can specify separate locales for the input method and the rest of the
		922	terminal, using the resource C<imlocale>:
		923
		924	URxvt.imlocale: ja_JP.EUC-JP
		925
		926	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		927	use your input method. Please note, however, that, depending on your Xlib
		928	version, you may not be able to input characters outside C<EUC-JP> in a
		929	normal way then, as your input method limits you.
		930
		931	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		932
		933	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		934	design. Applications can avoid some crashes at the expense of memory
		935	leaks, and Input Methods can avoid some crashes by careful ordering at
		936	exit time. B<kinput2> (and derived input methods) generally succeeds,
		937	while B<SCIM> (or similar input methods) fails. In the end, however,
		938	crashes cannot be completely avoided even if both sides cooperate.
		939
		940	So the only workaround is not to kill your Input Method Servers.
		941
		942
		943	=head2 Operating Systems / Package Maintaining
		944
		945	=head3 I am using Debian GNU/Linux and have a problem...
		946
		947	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		948	patches that considerably change the behaviour of rxvt-unicode (but
		949	unfortunately this notice has been removed). Before reporting a bug to
		950	the original rxvt-unicode author please download and install the genuine
		951	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		952	the problem. If you cannot, chances are that the problems are specific to
		953	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		954	Tracking System (use C<reportbug> to report the bug).
		955
		956	For other problems that also affect the Debian package, you can and
		957	probably should use the Debian BTS, too, because, after all, it's also a
		958	bug in the Debian version and it serves as a reminder for other users that
		959	might encounter the same issue.
		960
		961	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		962
		963	You should build one binary with the default options. F<configure>
		964	now enables most useful options, and the trend goes to making them
		965	runtime-switchable, too, so there is usually no drawback to enbaling them,
		966	except higher disk and possibly memory usage. The perl interpreter should
		967	be enabled, as important functionality (menus, selection, likely more in
		968	the future) depends on it.
		969
		970	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		971	system-wide (except maybe with C<defaults>). This will result in useful
		972	behaviour. If your distribution aims at low memory, add an empty
		973	C<perl-ext-common> resource to the app-defaults file. This will keep the
		974	perl interpreter disabled until the user enables it.
		975
		976	If you can/want build more binaries, I recommend building a minimal
		977	one with C<--disable-everything> (very useful) and a maximal one with
		978	C<--enable-everything> (less useful, it will be very big due to a lot of
		979	encodings built-in that increase download times and are rarely used).
		980
		981	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		982
		983	It should be, starting with release 7.1. You are encouraged to properly
		984	install urxvt with privileges necessary for your OS now.
		985
		986	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		987	into a helper process for privileged operations (pty handling on some
		988	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		989	immediately. This is much safer than most other terminals that keep
		990	privileges while running (but is more relevant to urxvt, as it contains
		991	things as perl interpreters, which might be "helpful" to attackers).
		992
		993	This forking is done as the very first within main(), which is very early
		994	and reduces possible bugs to initialisation code run before main(), or
		995	things like the dynamic loader of your system, which should result in very
		996	little risk.
		997
263	=item On Solaris 9, many line-drawing characters are too wide.	998	=head3 On Solaris 9, many line-drawing characters are too wide.
264		999
265	Seems to be a known bug, read	1000	Seems to be a known bug, read
266	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1001	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
267	following ugly workaround to get non-double-wide-characters working:	1002	following ugly workaround to get non-double-wide-characters working:
268		1003
269	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1004	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
270		1005
271	=item My Compose (Multi_key) key is no longer working.
272
273	The most common causes for this are that either your locale is not set
274	correctly, or you specified a B<preeditStyle> that is not supported by
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
280	In this case either do not specify a B<preeditStyle> or specify more than
281	one pre-edit style, such as B<OverTheSpot,Root,None>.
282
283	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
284
285	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
286	international keyboards) or simply use ISO 14755 support to your
287	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
288	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
289	character and so on.
290
291	=item How can I keep rxvt-unicode from using reverse video so much?
292
293	First of all, make sure you are running with the right terminal settings
294	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
295	make sure you have specified colours for italic and bold, as otherwise
296	rxvt-unicode might use reverse video to simulate the effect:
297
298	URxvt.colorBD: white
299	URxvt.colorIT: green
300
301	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
302
303	For some unexplainable reason, some rare programs assume a very weird
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
308	In the meantime, you can either edit your C<rxvt-unicode> terminfo
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
312	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	1006	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
313		1007
314	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1008	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
315	in your compile environment, or an implementation that implements it,	1009	in your compile environment, or an implementation that implements it,
316	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1010	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
317	B<wchar_t> is represented as unicode.	1011	B<wchar_t> is represented as unicode.
…		…
339		1033
340	The rxvt-unicode author insists that the right way to fix this is in the	1034	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	1035	system libraries once and for all, instead of forcing every app to carry
342	complete replacements for them :)	1036	complete replacements for them :)
343		1037
344	=item I use Solaris 9 and it doesn't compile/work/etc.	1038	=head3 I use Solaris 9 and it doesn't compile/work/etc.
345		1039
346	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1040	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
347	problems with C<wcwidth> and a compile problem.	1041	problems with C<wcwidth> and a compile problem.
348		1042
349	=item How can I use rxvt-unicode under cygwin?	1043	=head3 How can I use rxvt-unicode under cygwin?
350		1044
351	rxvt-unicode should compile and run out of the box on cygwin, using	1045	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	1046	the X11 libraries that come with cygwin. libW11 emulation is no
353	longer supported (and makes no sense, either, as it only supported a	1047	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	1048	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	1049	C<-rootless> mode instead, which will result in similar look&feel as the
356	old libW11 emulation.	1050	old libW11 emulation.
357		1051
358	At the time of this writing, cygwin didn't seem to support any multi-byte	1052	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.	1053	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		1054	to 8-bit encodings.
360		1055
361	=item How does rxvt-unicode determine the encoding to use?
362
363	=item Is there an option to switch encodings?
364
365	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
366	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
367	UTF-8 or any other encodings with respect to terminal I/O.
368
369	The reasons is that there exists a perfectly fine mechanism for selecting
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
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	1056	=head1 RXVT-UNICODE TECHNICAL REFERENCE
732
733	=head1 DESCRIPTION
734		1057
735	The rest of this document describes various technical aspects of	1058	The rest of this document describes various technical aspects of
736	B<rxvt-unicode>. First the description of supported command sequences,	1059	B<rxvt-unicode>. First the description of supported command sequences,
737	followed by menu and pixmap support and last by a description of all	1060	followed by pixmap support and last by a description of all features
738	features selectable at C<configure> time.	1061	selectable at C<configure> time.
739		1062
740	=head1 Definitions	1063	=head2 Definitions
741		1064
742	=over 4	1065	=over 4
743		1066
744	=item B<< C<c> >>	1067	=item B<< C<c> >>
745		1068
…		…
763		1086
764	A text parameter composed of printable characters.	1087	A text parameter composed of printable characters.
765		1088
766	=back	1089	=back
767		1090
768	=head1 Values	1091	=head2 Values
769		1092
770	=over 4	1093	=over 4
771		1094
772	=item B<< C<ENQ> >>	1095	=item B<< C<ENQ> >>
773		1096
…		…
816		1139
817	Space Character	1140	Space Character
818		1141
819	=back	1142	=back
820		1143
821	=head1 Escape Sequences	1144	=head2 Escape Sequences
822		1145
823	=over 4	1146	=over 4
824		1147
825	=item B<< C<ESC # 8> >>	1148	=item B<< C<ESC # 8> >>
826		1149
…		…
924		1247
925	=back	1248	=back
926		1249
927	X<CSI>	1250	X<CSI>
928		1251
929	=head1 CSI (Command Sequence Introducer) Sequences	1252	=head2 CSI (Command Sequence Introducer) Sequences
930		1253
931	=over 4	1254	=over 4
932		1255
933	=item B<< C<ESC [ Ps @> >>	1256	=item B<< C<ESC [ Ps @> >>
934		1257
…		…
1204		1527
1205	=back	1528	=back
1206		1529
1207	X<PrivateModes>	1530	X<PrivateModes>
1208		1531
1209	=head1 DEC Private Modes	1532	=head2 DEC Private Modes
1210		1533
1211	=over 4	1534	=over 4
1212		1535
1213	=item B<< C<ESC [ ? Pm h> >>	1536	=item B<< C<ESC [ ? Pm h> >>
1214		1537
…		…
1311	B<< C<h> >> Send Mouse X & Y on button press.	1634	B<< C<h> >> Send Mouse X & Y on button press.
1312	B<< C<l> >> No mouse reporting.	1635	B<< C<l> >> No mouse reporting.
1313		1636
1314	=end table	1637	=end table
1315		1638
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> >>	1639	=item B<< C<Ps = 25> >>
1326		1640
1327	=begin table	1641	=begin table
1328		1642
1329	B<< C<h> >> Visible cursor {cnorm/cvvis}	1643	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
1445	B<< C<h> >> Scroll to bottom when a key is pressed	1759	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	1760	B<< C<l> >> Don't scroll to bottom when a key is pressed
1447		1761
1448	=end table	1762	=end table
1449		1763
		1764	=item B<< C<Ps = 1021> >> (B<rxvt>)
		1765
		1766	=begin table
		1767
		1768	B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
		1769	B<< C<l> >> Font styles have no effect on intensity (Compile styles)
		1770
		1771	=end table
		1772
1450	=item B<< C<Ps = 1047> >>	1773	=item B<< C<Ps = 1047> >>
1451		1774
1452	=begin table	1775	=begin table
1453		1776
1454	B<< C<h> >> Use Alternate Screen Buffer	1777	B<< C<h> >> Use Alternate Screen Buffer
…		…
1478		1801
1479	=back	1802	=back
1480		1803
1481	X<XTerm>	1804	X<XTerm>
1482		1805
1483	=head1 XTerm Operating System Commands	1806	=head2 XTerm Operating System Commands
1484		1807
1485	=over 4	1808	=over 4
1486		1809
1487	=item B<< C<ESC ] Ps;Pt ST> >>	1810	=item B<< C<ESC ] Ps;Pt ST> >>
1488		1811
…		…
1500	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	1823	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)>	1824	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> >>	1825	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> >>	1826	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> >>	1827	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> >>	1828	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> >>	1829	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> >>	1830	B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM).
1508	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.	1831	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>	1832	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> >>.	1833	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> >>	1834	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> >>	1835	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).	1836	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).	1837	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> >>	1838	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).	1839	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
		1840	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		1841	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>.	1842	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).	1843	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).	1844	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).	1845	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).	1846	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).	1847	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1848	B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1523		1849
1524	=end table	1850	=end table
1525		1851
1526	=back	1852	=back
1527
1528	X<menuBar>
1529
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		1853
1996	=head1 XPM	1854	=head1 XPM
1997		1855
1998	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1856	For the XPM 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	1857	of B<< C<Pt> >> can be the name of the background pixmap followed by a
…		…
2097	=begin table	1955	=begin table
2098		1956
2099	4 Shift	1957	4 Shift
2100	8 Meta	1958	8 Meta
2101	16 Control	1959	16 Control
2102	32 Double Click I<(Rxvt extension)>	1960	32 Double Click I<(rxvt extension)>
2103		1961
2104	=end table	1962	=end table
2105		1963
2106	Col = B<< C<< <x> - SPACE >> >>	1964	Col = B<< C<< <x> - SPACE >> >>
2107		1965
…		…
2184	=end table	2042	=end table
2185		2043
2186	=head1 CONFIGURE OPTIONS	2044	=head1 CONFIGURE OPTIONS
2187		2045
2188	General hint: if you get compile errors, then likely your configuration	2046	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	2047	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,	2048	the F<./reconf> script as a base for experiments. F<./reconf> is used by
2191	so it should generally be a working config. Of course, you should always	2049	myself, so it should generally be a working config. Of course, you should
2192	report when a combination doesn't work, so it can be fixed. Marc Lehmann	2050	always report when a combination doesn't work, so it can be fixed. Marc
2193	<rxvt@schmorp.de>.	2051	Lehmann <rxvt@schmorp.de>.
		2052
		2053	All
2194		2054
2195	=over 4	2055	=over 4
2196		2056
2197	=item --enable-everything	2057	=item --enable-everything
2198		2058
2199	Add support for all non-multichoice options listed in "./configure	2059	Add (or remove) support for all non-multichoice options listed in "./configure
2200	--help". Note that unlike other enable options this is order dependant.	2060	--help".
		2061
2201	You can specify this and then disable options which this enables by	2062	You can specify this and then disable options you do not like by
2202	I<following> this with the appropriate commands.	2063	I<following> this with the appropriate C<--disable-...> arguments,
		2064	or you can start with a minimal configuration by specifying
		2065	C<--disable-everything> and than adding just the C<--enable-...> arguments
		2066	you want.
2203		2067
2204	=item --enable-xft	2068	=item --enable-xft (default: enabled)
2205		2069
2206	Add support for Xft (anti-aliases, among others) fonts. Xft fonts are	2070	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	2071	slower and require lots of memory, but as long as you don't use them, you
2208	don't pay for them.	2072	don't pay for them.
2209		2073
2210	=item --enable-font-styles	2074	=item --enable-font-styles (default: on)
2211		2075
2212	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2076	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2213	styles. The fonts can be set manually or automatically.	2077	styles. The fonts can be set manually or automatically.
2214		2078
2215	=item --with-codesets=NAME,...	2079	=item --with-codesets=NAME,... (default: all)
2216		2080
2217	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>	2081	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	2082	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	2083	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	2084	for Xft fonts, although having them compiled in lets rxvt-unicode choose
…		…
2231	jp_ext rarely used but big japanese encodings	2095	jp_ext rarely used but big japanese encodings
2232	kr korean encodings	2096	kr korean encodings
2233		2097
2234	=end table	2098	=end table
2235		2099
2236	=item --enable-xim	2100	=item --enable-xim (default: on)
2237		2101
2238	Add support for XIM (X Input Method) protocol. This allows using	2102	Add support for XIM (X Input Method) protocol. This allows using
2239	alternative input methods (e.g. kinput2) and will also correctly	2103	alternative input methods (e.g. kinput2) and will also correctly
2240	set up the input for people using dead keys or compose keys.	2104	set up the input for people using dead keys or compose keys.
2241		2105
2242	=item --enable-unicode3	2106	=item --enable-unicode3 (default: off)
		2107
		2108	Recommended to stay off unless you really need non-BMP characters.
2243		2109
2244	Enable direct support for displaying unicode codepoints above	2110	Enable direct support for displaying unicode codepoints above
2245	65535 (the basic multilingual page). This increases storage	2111	65535 (the basic multilingual page). This increases storage
2246	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2112	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2247	support these extra characters, but Xft does.	2113	support these extra characters, but Xft does.
…		…
2250	even without this flag, but the number of such characters is	2116	even without this flag, but the number of such characters is
2251	limited to a view thousand (shared with combining characters,	2117	limited to a view thousand (shared with combining characters,
2252	see next switch), and right now rxvt-unicode cannot display them	2118	see next switch), and right now rxvt-unicode cannot display them
2253	(input/output and cut&paste still work, though).	2119	(input/output and cut&paste still work, though).
2254		2120
2255	=item --enable-combining	2121	=item --enable-combining (default: on)
2256		2122
2257	Enable automatic composition of combining characters into	2123	Enable automatic composition of combining characters into
2258	composite characters. This is required for proper viewing of text	2124	composite characters. This is required for proper viewing of text
2259	where accents are encoded as seperate unicode characters. This is	2125	where accents are encoded as seperate unicode characters. This is
2260	done by using precomposited characters when available or creating	2126	done by using precomposited characters when available or creating
2261	new pseudo-characters when no precomposed form exists.	2127	new pseudo-characters when no precomposed form exists.
2262		2128
2263	Without --enable-unicode3, the number of additional precomposed characters	2129	Without --enable-unicode3, the number of additional precomposed
2264	is rather limited (2048, if this is full, rxvt-unicode will use the	2130	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.	2131	(ab-)used). With --enable-unicode3, no practical limit exists.
2267		2132
2268	This option will also enable storage (but not display) of characters	2133	This option will also enable storage (but not display) of characters
2269	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2134	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2270		2135
2271	The combining table also contains entries for arabic presentation forms,	2136	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	2137	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...).	2138	tell me how these are to be used...).
2274		2139
2275	=item --enable-fallback(=CLASS)	2140	=item --enable-fallback(=CLASS) (default: Rxvt)
2276		2141
2277	When reading resource settings, also read settings for class CLASS	2142	When reading resource settings, also read settings for class CLASS. To
2278	(default: Rxvt). To disable resource fallback use --disable-fallback.	2143	disable resource fallback use --disable-fallback.
2279		2144
2280	=item --with-res-name=NAME	2145	=item --with-res-name=NAME (default: urxvt)
2281		2146
2282	Use the given name (default: urxvt) as default application name when	2147	Use the given name as default application name when
2283	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2148	reading resources. Specify --with-res-name=rxvt to replace rxvt.
2284		2149
2285	=item --with-res-class=CLASS	2150	=item --with-res-class=CLASS /default: URxvt)
2286		2151
2287	Use the given class (default: URxvt) as default application class	2152	Use the given class as default application class
2288	when reading resources. Specify --with-res-class=Rxvt to replace	2153	when reading resources. Specify --with-res-class=Rxvt to replace
2289	rxvt.	2154	rxvt.
2290		2155
2291	=item --enable-utmp	2156	=item --enable-utmp (default: on)
2292		2157
2293	Write user and tty to utmp file (used by programs like F<w>) at	2158	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.	2159	start of rxvt execution and delete information when rxvt exits.
2295		2160
2296	=item --enable-wtmp	2161	=item --enable-wtmp (default: on)
2297		2162
2298	Write user and tty to wtmp file (used by programs like F<last>) at	2163	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	2164	start of rxvt execution and write logout when rxvt exits. This
2300	option requires --enable-utmp to also be specified.	2165	option requires --enable-utmp to also be specified.
2301		2166
2302	=item --enable-lastlog	2167	=item --enable-lastlog (default: on)
2303		2168
2304	Write user and tty to lastlog file (used by programs like	2169	Write user and tty to lastlog file (used by programs like
2305	F<lastlogin>) at start of rxvt execution. This option requires	2170	F<lastlogin>) at start of rxvt execution. This option requires
2306	--enable-utmp to also be specified.	2171	--enable-utmp to also be specified.
2307		2172
2308	=item --enable-xpm-background	2173	=item --enable-xpm-background (default: on)
2309		2174
2310	Add support for XPM background pixmaps.	2175	Add support for XPM background pixmaps.
2311		2176
2312	=item --enable-transparency	2177	=item --enable-transparency (default: on)
2313		2178
2314	Add support for inheriting parent backgrounds thus giving a fake	2179	Add support for inheriting parent backgrounds thus giving a fake
2315	transparency to the term.	2180	transparency to the term.
2316		2181
2317	=item --enable-fading	2182	=item --enable-fading (default: on)
2318		2183
2319	Add support for fading the text when focus is lost.	2184	Add support for fading the text when focus is lost (requires C<--enable-transparency>).
2320		2185
2321	=item --enable-tinting	2186	=item --enable-tinting (default: on)
2322		2187
2323	Add support for tinting of transparent backgrounds.	2188	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2324		2189
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	2190	=item --enable-rxvt-scroll (default: on)
2331		2191
2332	Add support for the original rxvt scrollbar.	2192	Add support for the original rxvt scrollbar.
2333		2193
2334	=item --enable-next-scroll	2194	=item --enable-next-scroll (default: on)
2335		2195
2336	Add support for a NeXT-like scrollbar.	2196	Add support for a NeXT-like scrollbar.
2337		2197
2338	=item --enable-xterm-scroll	2198	=item --enable-xterm-scroll (default: on)
2339		2199
2340	Add support for an Xterm-like scrollbar.	2200	Add support for an Xterm-like scrollbar.
2341		2201
2342	=item --enable-plain-scroll	2202	=item --enable-plain-scroll (default: on)
2343		2203
2344	Add support for a very unobtrusive, plain-looking scrollbar that	2204	Add support for a very unobtrusive, plain-looking scrollbar that
2345	is the favourite of the rxvt-unicode author, having used it for	2205	is the favourite of the rxvt-unicode author, having used it for
2346	many years.	2206	many years.
2347		2207
2348	=item --enable-half-shadow	2208	=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		2209
2355	Change tty device setting to group "tty" - only use this if	2210	Change tty device setting to group "tty" - only use this if
2356	your system uses this type of security.	2211	your system uses this type of security.
2357		2212
2358	=item --disable-backspace-key	2213	=item --disable-backspace-key
2359		2214
2360	Disable any handling of the backspace key by us - let the X server	2215	Removes any handling of the backspace key by us - let the X server do it.
		2216
		2217	=item --disable-delete-key
		2218
		2219	Removes any handling of the delete key by us - let the X server
2361	do it.	2220	do it.
2362		2221
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	2222	=item --disable-resources
2369		2223
2370	Remove all resources checking.	2224	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		2225
2390	=item --disable-swapscreen	2226	=item --disable-swapscreen
2391		2227
2392	Remove support for swap screen.	2228	Remove support for secondary/swap screen.
2393		2229
2394	=item --enable-frills	2230	=item --enable-frills (default: on)
2395		2231
2396	Add support for many small features that are not essential but nice to	2232	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	2233	have. Normally you want this, but for very small binaries you may want to
2398	disable this.	2234	disable this.
2399		2235
2400	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2236	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2401	in combination with other switches) is:	2237	in combination with other switches) is:
2402		2238
2403	MWM-hints	2239	MWM-hints
2404	EWMH-hints (pid, utf8 names) and protocols (ping)	2240	EWMH-hints (pid, utf8 names) and protocols (ping)
2405	seperate underline colour	2241	seperate underline colour (-underlineColor)
2406	settable border widths and borderless switch	2242	settable border widths and borderless switch (-w, -b, -bl)
		2243	visual depth selection (-depth)
2407	settable extra linespacing	2244	settable extra linespacing /-lsp)
2408	iso-14755-2 and -3, and visual feedback	2245	iso-14755-2 and -3, and visual feedback
		2246	tripleclickwords (-tcw)
		2247	settable insecure mode (-insecure)
		2248	keysym remapping support
		2249	cursor blinking and underline cursor (-cb, -uc)
		2250	XEmbed support (-embed)
		2251	user-pty (-pty-fd)
		2252	hold on exit (-hold)
		2253	skip builtin block graphics (-sbg)
		2254
		2255	It also enabled some non-essential features otherwise disabled, such as:
		2256
		2257	some round-trip time optimisations
		2258	nearest color allocation on pseudocolor screens
		2259	UTF8_STRING supporr for selection
		2260	sgr modes 90..97 and 100..107
2409	backindex and forwardindex escape sequence	2261	backindex and forwardindex escape sequences
		2262	view change/zero scorllback esacpe sequences
		2263	locale switching escape sequence
2410	window op and some xterm/OSC escape sequences	2264	window op and some xterm/OSC escape sequences
2411	tripleclickwords	2265	rectangular selections
2412	settable insecure mode	2266	trailing space removal for selections
2413	keysym remapping support	2267	verbose X error handling
2414	cursor blinking and underline cursor
2415	-embed and -pty-fd options
2416		2268
2417	=item --enable-iso14755	2269	=item --enable-iso14755 (default: on)
2418		2270
2419	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2271	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2420	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2272	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	2273	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2422	this switch.	2274	this switch.
2423		2275
2424	=item --enable-keepscrolling	2276	=item --enable-keepscrolling (default: on)
2425		2277
2426	Add support for continual scrolling of the display when you hold	2278	Add support for continual scrolling of the display when you hold
2427	the mouse button down on a scrollbar arrow.	2279	the mouse button down on a scrollbar arrow.
2428		2280
2429	=item --enable-mousewheel	2281	=item --enable-mousewheel (default: on)
2430		2282
2431	Add support for scrolling via mouse wheel or buttons 4 & 5.	2283	Add support for scrolling via mouse wheel or buttons 4 & 5.
2432		2284
2433	=item --enable-slipwheeling	2285	=item --enable-slipwheeling (default: on)
2434		2286
2435	Add support for continual scrolling (using the mouse wheel as an	2287	Add support for continual scrolling (using the mouse wheel as an
2436	accelerator) while the control key is held down. This option	2288	accelerator) while the control key is held down. This option
2437	requires --enable-mousewheel to also be specified.	2289	requires --enable-mousewheel to also be specified.
2438		2290
2439	=item --disable-new-selection	2291	=item --disable-new-selection
2440		2292
2441	Remove support for mouse selection style like that of xterm.	2293	Remove support for mouse selection style like that of xterm.
2442		2294
2443	=item --enable-dmalloc	2295	=item --enable-dmalloc (default: off)
2444		2296
2445	Use Gray Watson's malloc - which is good for debugging See	2297	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	2298	L<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	2299	next option, you may need to edit src/Makefile after compiling to point
2448	DINCLUDE and DLIB to the right places.	2300	DINCLUDE and DLIB to the right places.
2449		2301
2450	You can only use either this option and the following (should	2302	You can only use either this option and the following (should
2451	you use either) .	2303	you use either) .
2452		2304
2453	=item --enable-dlmalloc	2305	=item --enable-dlmalloc (default: off)
2454		2306
2455	Use Doug Lea's malloc - which is good for a production version	2307	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.	2308	See L<http://g.oswego.edu/dl/html/malloc.html> for details.
2457		2309
2458	=item --enable-smart-resize	2310	=item --enable-smart-resize (default: on)
2459		2311
2460	Add smart growth/shrink behaviour when changing font size via from hot	2312	Add smart growth/shrink behaviour when changing font size via hot
2461	keys. This should keep in a fixed position the rxvt corner which is	2313	keys. This should keep the window corner which is closest to a corner of
2462	closest to a corner of the screen.	2314	the screen in a fixed position.
2463		2315
2464	=item --enable-pointer-blank	2316	=item --enable-pointer-blank (default: on)
2465		2317
2466	Add support to have the pointer disappear when typing or inactive.	2318	Add support to have the pointer disappear when typing or inactive.
2467		2319
2468	=item --with-name=NAME	2320	=item --enable-perl (default: on)
2469		2321
		2322	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
		2323	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
		2324	in F<src/perl-ext/> for the extensions that are installed by default. The
		2325	perl interpreter that is used can be specified via the C<PERL> environment
		2326	variable when running configure.
		2327
		2328	=item --with-name=NAME (default: urxvt)
		2329
2470	Set the basename for the installed binaries (default: C<urxvt>, resulting	2330	Set the basename for the installed binaries, resulting
2471	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2331	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
2472	C<rxvt>.	2332	C<rxvt>.
2473		2333
2474	=item --with-term=NAME	2334	=item --with-term=NAME (default: rxvt-unicode)
2475		2335
2476	Change the environmental variable for the terminal to NAME (default	2336	Change the environmental variable for the terminal to NAME.
2477	C<rxvt-unicode>)
2478		2337
2479	=item --with-terminfo=PATH	2338	=item --with-terminfo=PATH
2480		2339
2481	Change the environmental variable for the path to the terminfo tree to	2340	Change the environmental variable for the path to the terminfo tree to
2482	PATH.	2341	PATH.

Diff Legend

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