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.76 by root, Wed Jan 11 19:55:34 2006 UTC vs.
Revision 1.145 by root, Sun Sep 9 08:38:40 2007 UTC

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

Diff Legend

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