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.79 by root, Thu Jan 12 23:11:23 2006 UTC vs.
Revision 1.113 by root, Thu Feb 2 18:04:45 2006 UTC

…		…
16	=head1 DESCRIPTION	16	=head1 DESCRIPTION
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is	21	The newest version of this document is also available on the World Wide Web at
22	also available on the World Wide Web at
23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
24		23
25	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		25
27	=over 4
28		26
29	=item The new selection selects pieces that are too big/too small, can I	27	=head2 Meta, Features & Commandline Issues
30	change this?
31		28
32	Yes. For example, if you want to select smaller pieces ("words") you can	29	=head3 My question isn't answered here, can I ask a human?
33	use the following resource:
34		30
35	URxvt.selection.pattern-0: ([[:word:]]+)	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 :).
36		34
37	If you click more than twice, the selection will be extended	35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
38	more and more.
39		36
40	To get a selection that is very similar to the old code, try this pattern:	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:
41		40
42	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)	41	@@URXVT_NAME@@ -pe tabbed
43		42
44	=item I don't like the new selection/popups/hotkeys/perl, how do I	43	URxvt.perl-ext-common: default,tabbed
45	change/disable it?
46		44
47	You can disable the perl extension completely by setting the	45	It will also work fine with tabbing functionality of many window managers
48	B<perl-ext-common> resource to the empty string, which also keeps	46	or similar tabbing programs, and its embedding-features allow it to be
49	rxvt-unicode from initialising perl, saving memory.	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		50
51	If you only want to disable specific features, you first have to	51	=head3 How do I know which rxvt-unicode version I'm using?
52	identify which perl extension is responsible. For this, read the section
53	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For
54	example, to disable the B<selection-popup> and B<option-popup>, specify
55	this B<perl-ext-common> resource:
56		52
57	URxvt.perl-ext-common: default,-selection-popup,-option-popup	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.
58		57
59	This will keep the default extensions, but disable the two popup	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
60	extensions. Some extensions can also be configured, for example,
61	scrollback search mode is triggered by B<M-s>. You can move it to any
62	other combination either by setting the B<searchable-scrollback> resource:
63		59
64	URxvt.searchable-scrollback: CM-s	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		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 wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
		96
		97	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
		98	so you can check and see if that is set. Note that several programs, JED,
		99	slrn, Midnight Commander automatically check this variable to decide
		100	whether or not to use color.
		101
		102	=head3 How do I set the correct, full IP address for the DISPLAY variable?
		103
		104	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		105	insecure mode then it is possible to use the following shell script
		106	snippets to correctly set the display. If your version of rxvt-unicode
		107	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		108	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		109	regular xterm.
		110
		111	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		112	snippets:
		113
		114	# Bourne/Korn/POSIX family of shells:
		115	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		116	if [ ${TERM:-foo} = xterm ]; then
		117	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		118	echo -n '^[Z'
		119	read term_id
		120	stty icanon echo
		121	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		122	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		123	read DISPLAY # set it in our local shell
		124	fi
		125	fi
		126
		127	=head3 How do I compile the manual pages on my own?
		128
		129	You need to have a recent version of perl installed as F</usr/bin/perl>,
		130	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		131	the doc subdirectory and enter C<make alldoc>.
		132
66	=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?
67		134
68	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
69	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
70	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
71	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
…		…
75		142
76	text data bss drs rss filename	143	text data bss drs rss filename
77	98398 1664 24 15695 1824 rxvt --disable-everything	144	98398 1664 24 15695 1824 rxvt --disable-everything
78	188985 9048 66616 18222 1788 urxvt --disable-everything	145	188985 9048 66616 18222 1788 urxvt --disable-everything
79		146
80	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
81	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
82	libc), the two diverge, but not unreasnobaly so.	149	libc), the two diverge, but not unreasnobaly so.
83		150
84	text data bss drs rss filename	151	text data bss drs rss filename
85	163431 2152 24 20123 2060 rxvt --enable-everything	152	163431 2152 24 20123 2060 rxvt --enable-everything
…		…
103	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
104	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
105	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
106	extremely well *g*.	173	extremely well *g*.
107		174
108	=item Why C++, isn't that unportable/bloated/uncool?	175	=head3 Why C++, isn't that unportable/bloated/uncool?
109		176
110	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
111	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
112	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
113	shorter: It simply wouldn't exist without C++.	180	shorter: It simply wouldn't exist without C++.
…		…
137	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
138		205
139	No large bloated libraries (of course, none were linked in statically),	206	No large bloated libraries (of course, none were linked in statically),
140	except maybe libX11 :)	207	except maybe libX11 :)
141		208
142	=item Does it support tabs, can I have a tabbed rxvt-unicode?
143		209
144	rxvt-unicode does not directly support tabs. It will work fine with	210	=head2 Rendering, Font & Look and Feel Issues
145	tabbing functionality of many window managers or similar tabbing programs,
146	and its embedding-features allow it to be embedded into other programs,
147	as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
148	module, which features a tabbed urxvt (murxvt) terminal as an example
149	embedding application.
150		211
151	=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?
152		213
153	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
154	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
155	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
156	daemon.	217	of passage: ... and you failed.
157		218
158	=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!
159		221
160	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	222	1. Use inheritPixmap:
161	patches that considerably change the behaviour of rxvt-unicode. Before
162	reporting a bug to the original rxvt-unicode author please download and
163	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
164	and try to reproduce the problem. If you cannot, chances are that the
165	problems are specific to Debian GNU/Linux, in which case it should be
166	reported via the Debian Bug Tracking System (use C<reportbug> to report
167	the bug).
168		223
169	For other problems that also affect the Debian package, you can and	224	Esetroot wallpaper.jpg
170	probably should use the Debian BTS, too, because, after all, it's also a	225	@@URXVT_NAME@@ -ip -tint red -sh 40
171	bug in the Debian version and it serves as a reminder for other users that
172	might encounter the same issue.
173		226
174	=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.
175		229
176	You should build one binary with the default options. F<configure>	230	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
177	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
178	runtime-switchable, too, so there is usually no drawback to enbaling them,	232	your picture with gimp or any other tool:
179	except higher disk and possibly memory usage. The perl interpreter should
180	be enabled, as important functionality (menus, selection, likely more in
181	the future) depends on it.
182		233
183	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	234	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
184	system-wide (except maybe with C<defaults>). This will result in useful	235	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
185	behaviour. If your distribution aims at low memory, add an empty
186	C<perl-ext-common> resource to the app-defaults file. This will keep the
187	perl interpreter disabled until the user enables it.
188		236
189	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
190	one with C<--disable-everything> (very useful) and a maximal one with	238	are unable to read.
191	C<--enable-everything> (less useful, it will be very big due to a lot of
192	encodings built-in that increase download times and are rarely used).
193		239
194	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	240	3. Use an ARGB visual:
195		241
196	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
197	bad at it, I think it is simply unreasonable to expect all of freetype
198	+ fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be
199	secure. Also, rxvt-unicode disables some options when it detects that it
200	runs setuid or setgid, which is not nice. Besides, with the embedded perl
201	interpreter the possibility for security problems easily multiplies.
202		243
203	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
204	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
205	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 neccessary
206	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.
207		249
208	So, while setuid/setgid operation is supported and not a problem on your	250	4. Use xcompmgr and let it do the job:
209	typical single-user-no-other-logins unix desktop, always remember that
210	its an awful lot of code, most of which isn't checked for security issues
211	regularly.
212		251
		252	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		253	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		254
		255	Then click on a window you want to make transparent. Replace C<0xc0000000>
		256	by other values to change the degree of opacity. If it doesn't work and
		257	your server crashes, you got to keep the pieces.
		258
		259	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		260
		261	Most fonts were not designed for terminal use, which means that character
		262	size varies a lot. A font that is otherwise fine for terminal use might
		263	contain some characters that are simply too wide. Rxvt-unicode will avoid
		264	these characters. For characters that are just "a bit" too wide a special
		265	"careful" rendering mode is used that redraws adjacent characters.
		266
		267	All of this requires that fonts do not lie about character sizes,
		268	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		269	box, and rxvt-unicode has no way of detecting this (the correct way is to
		270	ask for the character bounding box, which unfortunately is wrong in these
		271	cases).
		272
		273	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		274	or the respective font. If you encounter this problem you might try using
		275	the C<-lsp> option to give the font more height. If that doesn't work, you
		276	might be forced to use a different font.
		277
		278	All of this is not a problem when using X11 core fonts, as their bounding
		279	box data is correct.
		280
		281	=head3 How can I keep rxvt-unicode from using reverse video so much?
		282
		283	First of all, make sure you are running with the right terminal settings
		284	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		285	make sure you have specified colours for italic and bold, as otherwise
		286	rxvt-unicode might use reverse video to simulate the effect:
		287
		288	URxvt.colorBD: white
		289	URxvt.colorIT: green
		290
		291	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		292
		293	For some unexplainable reason, some rare programs assume a very weird
		294	colour palette when confronted with a terminal with more than the standard
		295	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		296	these programs not to assume non-ISO colours without very good reasons.
		297
		298	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		299	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		300	fix colours but keep you from using other rxvt-unicode features.
		301
		302	=head3 Can I switch the fonts at runtime?
		303
		304	Yes, using an escape sequence. Try something like this, which has the same
		305	effect as using the C<-fn> switch, and takes effect immediately:
		306
		307	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		308
		309	This is useful if you e.g. work primarily with japanese (and prefer a
		310	japanese font), but you have to switch to chinese temporarily, where
		311	japanese fonts would only be in your way.
		312
		313	You can think of this as a kind of manual ISO-2022 switching.
		314
		315	=head3 Why do italic characters look as if clipped?
		316
		317	Many fonts have difficulties with italic characters and hinting. For
		318	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		319	Mono> completely fails in it's italic face. A workaround might be to
		320	enable freetype autohinting, i.e. like this:
		321
		322	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		323	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		324
		325	=head3 Can I speed up Xft rendering somehow?
		326
		327	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		328	it is simply slow. If you still want Xft fonts you might try to disable
		329	antialiasing (by appending C<:antialias=false>), which saves lots of
		330	memory and also speeds up rendering considerably.
		331
		332	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		333
		334	Rxvt-unicode will use whatever you specify as a font. If it needs to
		335	fall back to it's default font search list it will prefer X11 core
		336	fonts, because they are small and fast, and then use Xft fonts. It has
		337	antialiasing disabled for most of them, because the author thinks they
		338	look best that way.
		339
		340	If you want antialiasing, you have to specify the fonts manually.
		341
		342	=head3 What's with this bold/blink stuff?
		343
		344	If no bold colour is set via C<colorBD:>, bold will invert text using the
		345	standard foreground colour.
		346
		347	For the standard background colour, blinking will actually make the
		348	text blink when compiled with C<--enable-blinking>. with standard
		349	colours. Without C<--enable-blinking>, the blink attribute will be
		350	ignored.
		351
		352	On ANSI colours, bold/blink attributes are used to set high-intensity
		353	foreground/background colors.
		354
		355	color0-7 are the low-intensity colors.
		356
		357	color8-15 are the corresponding high-intensity colors.
		358
		359	=head3 I don't like the screen colors. How do I change them?
		360
		361	You can change the screen colors at run-time using F<~/.Xdefaults>
		362	resources (or as long-options).
		363
		364	Here are values that are supposed to resemble a VGA screen,
		365	including the murky brown that passes for low-intensity yellow:
		366
		367	URxvt.color0: #000000
		368	URxvt.color1: #A80000
		369	URxvt.color2: #00A800
		370	URxvt.color3: #A8A800
		371	URxvt.color4: #0000A8
		372	URxvt.color5: #A800A8
		373	URxvt.color6: #00A8A8
		374	URxvt.color7: #A8A8A8
		375
		376	URxvt.color8: #000054
		377	URxvt.color9: #FF0054
		378	URxvt.color10: #00FF54
		379	URxvt.color11: #FFFF54
		380	URxvt.color12: #0000FF
		381	URxvt.color13: #FF00FF
		382	URxvt.color14: #00FFFF
		383	URxvt.color15: #FFFFFF
		384
		385	And here is a more complete set of non-standard colors.
		386
		387	URxvt.cursorColor: #dc74d1
		388	URxvt.pointerColor: #dc74d1
		389	URxvt.background: #0e0e0e
		390	URxvt.foreground: #4ad5e1
		391	URxvt.color0: #000000
		392	URxvt.color8: #8b8f93
		393	URxvt.color1: #dc74d1
		394	URxvt.color9: #dc74d1
		395	URxvt.color2: #0eb8c7
		396	URxvt.color10: #0eb8c7
		397	URxvt.color3: #dfe37e
		398	URxvt.color11: #dfe37e
		399	URxvt.color5: #9e88f0
		400	URxvt.color13: #9e88f0
		401	URxvt.color6: #73f7ff
		402	URxvt.color14: #73f7ff
		403	URxvt.color7: #e1dddd
		404	URxvt.color15: #e1dddd
		405
		406	They have been described (not by me) as "pretty girly".
		407
		408	=head3 Why do some characters look so much different than others?
		409
		410	See next entry.
		411
		412	=head3 How does rxvt-unicode choose fonts?
		413
		414	Most fonts do not contain the full range of Unicode, which is
		415	fine. Chances are that the font you (or the admin/package maintainer of
		416	your system/os) have specified does not cover all the characters you want
		417	to display.
		418
		419	B<rxvt-unicode> makes a best-effort try at finding a replacement
		420	font. Often the result is fine, but sometimes the chosen font looks
		421	bad/ugly/wrong. Some fonts have totally strange characters that don't
		422	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		423	intelligence to detect that a specific glyph is wrong: it has to believe
		424	the font that the characters it claims to contain indeed look correct.
		425
		426	In that case, select a font of your taste and add it to the font list,
		427	e.g.:
		428
		429	@@URXVT_NAME@@ -fn basefont,font2,font3...
		430
		431	When rxvt-unicode sees a character, it will first look at the base
		432	font. If the base font does not contain the character, it will go to the
		433	next font, and so on. Specifying your own fonts will also speed up this
		434	search and use less resources within rxvt-unicode and the X-server.
		435
		436	The only limitation is that none of the fonts may be larger than the base
		437	font, as the base font defines the terminal character cell size, which
		438	must be the same due to the way terminals work.
		439
		440	=head3 Why do some chinese characters look so different than others?
		441
		442	This is because there is a difference between script and language --
		443	rxvt-unicode does not know which language the text that is output is,
		444	as it only knows the unicode character codes. If rxvt-unicode first
		445	sees a japanese/chinese character, it might choose a japanese font for
		446	display. Subsequent japanese characters will use that font. Now, many
		447	chinese characters aren't represented in japanese fonts, so when the first
		448	non-japanese character comes up, rxvt-unicode will look for a chinese font
		449	-- unfortunately at this point, it will still use the japanese font for
		450	chinese characters that are also in the japanese font.
		451
		452	The workaround is easy: just tag a chinese font at the end of your font
		453	list (see the previous question). The key is to view the font list as
		454	a preference list: If you expect more japanese, list a japanese font
		455	first. If you expect more chinese, put a chinese font first.
		456
		457	In the future it might be possible to switch language preferences at
		458	runtime (the internal data structure has no problem with using different
		459	fonts for the same character at the same time, but no interface for this
		460	has been designed yet).
		461
		462	Until then, you might get away with switching fonts at runtime (see L<Can
		463	I switch the fonts at runtime?> later in this document).
		464
		465	=head2 Keyboard, Mouse & User Interaction
		466
		467	=head3 The new selection selects pieces that are too big, how can I select single words?
		468
		469	If you want to select e.g. alphanumeric words, you can use the following
		470	setting:
		471
		472	URxvt.selection.pattern-0: ([[:word:]]+)
		473
		474	If you click more than twice, the selection will be extended
		475	more and more.
		476
		477	To get a selection that is very similar to the old code, try this pattern:
		478
		479	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		480
		481	Please also note that the I<LeftClick Shift-LeftClik> combination also
		482	selects words like the old code.
		483
		484	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		485
		486	You can disable the perl extension completely by setting the
		487	B<perl-ext-common> resource to the empty string, which also keeps
		488	rxvt-unicode from initialising perl, saving memory.
		489
		490	If you only want to disable specific features, you first have to
		491	identify which perl extension is responsible. For this, read the section
		492	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		493	example, to disable the B<selection-popup> and B<option-popup>, specify
		494	this B<perl-ext-common> resource:
		495
		496	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		497
		498	This will keep the default extensions, but disable the two popup
		499	extensions. Some extensions can also be configured, for example,
		500	scrollback search mode is triggered by B<M-s>. You can move it to any
		501	other combination either by setting the B<searchable-scrollback> resource:
		502
		503	URxvt.searchable-scrollback: CM-s
		504
		505	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		506
		507	See next entry.
		508
		509	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		510
		511	These are caused by the C<readline> perl extension. Under normal
		512	circumstances, it will move your cursor around when you click into the
		513	line that contains it. It tries hard not to do this at the wrong moment,
		514	but when running a program that doesn't parse cursor movements or in some
		515	cases during rlogin sessions, it fails to detect this properly.
		516
		517	You can permamently switch this feature off by disabling the C<readline>
		518	extension:
		519
		520	URxvt.perl-ext-common: default,-readline
		521
		522	=head3 My numerical keypad acts weird and generates differing output?
		523
		524	Some Debian GNUL/Linux users seem to have this problem, although no
		525	specific details were reported so far. It is possible that this is caused
		526	by the wrong C<TERM> setting, although the details of wether and how
		527	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		528	keymap. See the answer to the previous question, and please report if that
		529	helped.
		530
		531	=head3 My Compose (Multi_key) key is no longer working.
		532
		533	The most common causes for this are that either your locale is not set
		534	correctly, or you specified a B<preeditStyle> that is not supported by
		535	your input method. For example, if you specified B<OverTheSpot> and
		536	your input method (e.g. the default input method handling Compose keys)
		537	does not support this (for instance because it is not visual), then
		538	rxvt-unicode will continue without an input method.
		539
		540	In this case either do not specify a B<preeditStyle> or specify more than
		541	one pre-edit style, such as B<OverTheSpot,Root,None>.
		542
		543	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		544
		545	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		546	international keyboards) or simply use ISO 14755 support to your
		547	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		548	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		549	character and so on.
		550
		551	=head3 Mouse cut/paste suddenly no longer works.
		552
		553	Make sure that mouse reporting is actually turned off since killing
		554	some editors prematurely may leave the mouse in mouse report mode. I've
		555	heard that tcsh may use mouse reporting unless it otherwise specified. A
		556	quick check is to see if cut/paste works when the Alt or Shift keys are
		557	depressed.
		558
		559	=head3 What's with the strange Backspace/Delete key behaviour?
		560
		561	Assuming that the physical Backspace key corresponds to the
		562	BackSpace keysym (not likely for Linux ... see the following
		563	question) there are two standard values that can be used for
		564	Backspace: C<^H> and C<^?>.
		565
		566	Historically, either value is correct, but rxvt-unicode adopts the debian
		567	policy of using C<^?> when unsure, because it's the one only only correct
		568	choice :).
		569
		570	Rxvt-unicode tries to inherit the current stty settings and uses the value
		571	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		572	started from a terminal (say, from a menu or by remote shell), then the
		573	system value of `erase', which corresponds to CERASE in <termios.h>, will
		574	be used (which may not be the same as your stty setting).
		575
		576	For starting a new rxvt-unicode:
		577
		578	# use Backspace = ^H
		579	$ stty erase ^H
		580	$ @@URXVT_NAME@@
		581
		582	# use Backspace = ^?
		583	$ stty erase ^?
		584	$ @@URXVT_NAME@@
		585
		586	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		587
		588	For an existing rxvt-unicode:
		589
		590	# use Backspace = ^H
		591	$ stty erase ^H
		592	$ echo -n "^[[36h"
		593
		594	# use Backspace = ^?
		595	$ stty erase ^?
		596	$ echo -n "^[[36l"
		597
		598	This helps satisfy some of the Backspace discrepancies that occur, but
		599	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		600	properly reflects that.
		601
		602	The Delete key is a another casualty of the ill-defined Backspace problem.
		603	To avoid confusion between the Backspace and Delete keys, the Delete
		604	key has been assigned an escape sequence to match the vt100 for Execute
		605	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		606
		607	Some other Backspace problems:
		608
		609	some editors use termcap/terminfo,
		610	some editors (vim I'm told) expect Backspace = ^H,
		611	GNU Emacs (and Emacs-like editors) use ^H for help.
		612
		613	Perhaps someday this will all be resolved in a consistent manner.
		614
		615	=head3 I don't like the key-bindings. How do I change them?
		616
		617	There are some compile-time selections available via configure. Unless
		618	you have run "configure" with the C<--disable-resources> option you can
		619	use the `keysym' resource to alter the keystrings associated with keysyms.
		620
		621	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		622
		623	URxvt.keysym.Home: \033[1~
		624	URxvt.keysym.End: \033[4~
		625	URxvt.keysym.C-apostrophe: \033<C-'>
		626	URxvt.keysym.C-slash: \033<C-/>
		627	URxvt.keysym.C-semicolon: \033<C-;>
		628	URxvt.keysym.C-grave: \033<C-`>
		629	URxvt.keysym.C-comma: \033<C-,>
		630	URxvt.keysym.C-period: \033<C-.>
		631	URxvt.keysym.C-0x60: \033<C-`>
		632	URxvt.keysym.C-Tab: \033<C-Tab>
		633	URxvt.keysym.C-Return: \033<C-Return>
		634	URxvt.keysym.S-Return: \033<S-Return>
		635	URxvt.keysym.S-space: \033<S-Space>
		636	URxvt.keysym.M-Up: \033<M-Up>
		637	URxvt.keysym.M-Down: \033<M-Down>
		638	URxvt.keysym.M-Left: \033<M-Left>
		639	URxvt.keysym.M-Right: \033<M-Right>
		640	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		641	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		642	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		643
		644	See some more examples in the documentation for the B<keysym> resource.
		645
		646	=head3 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map
		647
		648	KP_Insert == Insert
		649	F22 == Print
		650	F27 == Home
		651	F29 == Prior
		652	F33 == End
		653	F35 == Next
		654
		655	Rather than have rxvt-unicode try to accommodate all the various possible
		656	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		657	required for your particular machine.
		658
		659
		660
		661	=head2 Terminal Configuration
		662
		663	=head3 Why doesn't rxvt-unicode read my resources?
		664
		665	Well, why, indeed? It does, in a way very similar to other X
		666	applications. Most importantly, this means that if you or your OS loads
		667	resources into the X display (the right way to do it), rxvt-unicode will
		668	ignore any resource files in your home directory. It will only read
		669	F<$HOME/.Xdefaults> when no resources are attached to the display.
		670
		671	If you have or use an F<$HOME/.Xresources> file, chances are that
		672	resources are loaded into your X-server. In this case, you have to
		673	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		674
		675	Also consider the form resources have to use:
		676
		677	URxvt.resource: value
		678
		679	If you want to use another form (there are lots of different ways of
		680	specifying resources), make sure you understand wether and why it
		681	works. If unsure, use the form above.
		682
213	=item When I log-in to another system it tells me about missing terminfo data?	683	=head3 When I log-in to another system it tells me about missing terminfo data?
214		684
215	The terminal description used by rxvt-unicode is not as widely available	685	The terminal description used by rxvt-unicode is not as widely available
216	as that for xterm, or even rxvt (for which the same problem often arises).	686	as that for xterm, or even rxvt (for which the same problem often arises).
217		687
218	The correct solution for this problem is to install the terminfo, this can	688	The correct solution for this problem is to install the terminfo, this can
…		…
234	resource to set it:	704	resource to set it:
235		705
236	URxvt.termName: rxvt	706	URxvt.termName: rxvt
237		707
238	If you don't plan to use B<rxvt> (quite common...) you could also replace	708	If you don't plan to use B<rxvt> (quite common...) you could also replace
239	the rxvt terminfo file with the rxvt-unicode one.	709	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
240		710
241	=item C<tic> outputs some error when compiling the terminfo entry.	711	=head3 C<tic> outputs some error when compiling the terminfo entry.
242		712
243	Most likely it's the empty definition for C<enacs=>. Just replace it by	713	Most likely it's the empty definition for C<enacs=>. Just replace it by
244	C<enacs=\E[0@> and try again.	714	C<enacs=\E[0@> and try again.
245		715
246	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	716	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
247		717
		718	See next entry.
		719
248	=item I need a termcap file entry.	720	=head3 I need a termcap file entry.
249		721
250	One reason you might want this is that some distributions or operating	722	One reason you might want this is that some distributions or operating
251	systems still compile some programs using the long-obsoleted termcap	723	systems still compile some programs using the long-obsoleted termcap
252	library (Fedora Core's bash is one example) and rely on a termcap entry	724	library (Fedora Core's bash is one example) and rely on a termcap entry
253	for C<rxvt-unicode>.	725	for C<rxvt-unicode>.
…		…
279	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	751	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
280	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	752	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
281	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	753	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
282	:vs=\E[?25h:	754	:vs=\E[?25h:
283		755
284	=item Why does C<ls> no longer have coloured output?	756	=head3 Why does C<ls> no longer have coloured output?
285		757
286	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	758	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
287	decide wether a terminal has colour, but uses it's own configuration	759	decide wether a terminal has colour, but uses it's own configuration
288	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	760	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
289	with most other terminals supporting colour). Either add:	761	with most other terminals supporting colour). Either add:
…		…
294		766
295	alias ls='ls --color=auto'	767	alias ls='ls --color=auto'
296		768
297	to your C<.profile> or C<.bashrc>.	769	to your C<.profile> or C<.bashrc>.
298		770
299	=item Why doesn't vim/emacs etc. use the 88 colour mode?	771	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
300		772
		773	See next entry.
		774
301	=item Why doesn't vim/emacs etc. make use of italic?	775	=head3 Why doesn't vim/emacs etc. make use of italic?
302		776
		777	See next entry.
		778
303	=item Why are the secondary screen-related options not working properly?	779	=head3 Why are the secondary screen-related options not working properly?
304		780
305	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	781	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
306	distributions (most notably Debian GNU/Linux) break rxvt-unicode	782	distributions (most notably Debian GNU/Linux) break rxvt-unicode
307	by setting C<TERM> to C<rxvt>, which doesn't have these extra	783	by setting C<TERM> to C<rxvt>, which doesn't have these extra
308	features. Unfortunately, some of these (most notably, again, Debian	784	features. Unfortunately, some of these (most notably, again, Debian
309	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	785	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
310	file, so you will need to install it on your own (See the question B<When	786	file, so you will need to install it on your own (See the question B<When
311	I log-in to another system it tells me about missing terminfo data?> on	787	I log-in to another system it tells me about missing terminfo data?> on
312	how to do this).	788	how to do this).
313		789
314	=item My numerical keypad acts weird and generates differing output?
315		790
316	Some Debian GNUL/Linux users seem to have this problem, although no	791	=head2 Encoding / Locale / Input Method Issues
317	specific details were reported so far. It is possible that this is caused
318	by the wrong C<TERM> setting, although the details of wether and how
319	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
320	keymap. See the answer to the previous question, and please report if that
321	helped.
322		792
323	=item Rxvt-unicode does not seem to understand the selected encoding?	793	=head3 Rxvt-unicode does not seem to understand the selected encoding?
324		794
		795	See next entry.
		796
325	=item Unicode does not seem to work?	797	=head3 Unicode does not seem to work?
326		798
327	If you encounter strange problems like typing an accented character but	799	If you encounter strange problems like typing an accented character but
328	getting two unrelated other characters or similar, or if program output is	800	getting two unrelated other characters or similar, or if program output is
329	subtly garbled, then you should check your locale settings.	801	subtly garbled, then you should check your locale settings.
330		802
…		…
350		822
351	If nothing works and you are sure that everything is set correctly then	823	If nothing works and you are sure that everything is set correctly then
352	you will need to remember a little known fact: Some programs just don't	824	you will need to remember a little known fact: Some programs just don't
353	support locales :(	825	support locales :(
354		826
355	=item Why do some characters look so much different than others?	827	=head3 How does rxvt-unicode determine the encoding to use?
356		828
357	=item How does rxvt-unicode choose fonts?	829	See next entry.
358		830
359	Most fonts do not contain the full range of Unicode, which is	831	=head3 Is there an option to switch encodings?
360	fine. Chances are that the font you (or the admin/package maintainer of
361	your system/os) have specified does not cover all the characters you want
362	to display.
363		832
364	B<rxvt-unicode> makes a best-effort try at finding a replacement	833	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
365	font. Often the result is fine, but sometimes the chosen font looks	834	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
366	bad/ugly/wrong. Some fonts have totally strange characters that don't	835	UTF-8 or any other encodings with respect to terminal I/O.
367	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
368	intelligence to detect that a specific glyph is wrong: it has to believe
369	the font that the characters it claims to contain indeed look correct.
370		836
371	In that case, select a font of your taste and add it to the font list,	837	The reasons is that there exists a perfectly fine mechanism for selecting
372	e.g.:	838	the encoding, doing I/O and (most important) communicating this to all
373		839	applications so everybody agrees on character properties such as width
374	@@RXVT_NAME@@ -fn basefont,font2,font3...	840	and code number. This mechanism is the I<locale>. Applications not using
375		841	that info will have problems (for example, C<xterm> gets the width of
376	When rxvt-unicode sees a character, it will first look at the base	842	characters wrong as it uses it's own, locale-independent table under all
377	font. If the base font does not contain the character, it will go to the
378	next font, and so on. Specifying your own fonts will also speed up this
379	search and use less resources within rxvt-unicode and the X-server.
380
381	The only limitation is that none of the fonts may be larger than the base
382	font, as the base font defines the terminal character cell size, which
383	must be the same due to the way terminals work.
384
385	=item Why do some chinese characters look so different than others?
386
387	This is because there is a difference between script and language --
388	rxvt-unicode does not know which language the text that is output is,
389	as it only knows the unicode character codes. If rxvt-unicode first
390	sees a japanese/chinese character, it might choose a japanese font for
391	display. Subsequent japanese characters will use that font. Now, many
392	chinese characters aren't represented in japanese fonts, so when the first
393	non-japanese character comes up, rxvt-unicode will look for a chinese font
394	-- unfortunately at this point, it will still use the japanese font for
395	chinese characters that are also in the japanese font.
396
397	The workaround is easy: just tag a chinese font at the end of your font
398	list (see the previous question). The key is to view the font list as
399	a preference list: If you expect more japanese, list a japanese font
400	first. If you expect more chinese, put a chinese font first.
401
402	In the future it might be possible to switch language preferences at
403	runtime (the internal data structure has no problem with using different
404	fonts for the same character at the same time, but no interface for this
405	has been designed yet).
406
407	Until then, you might get away with switching fonts at runtime (see L<Can
408	I switch the fonts at runtime?> later in this document).
409
410	=item Why does rxvt-unicode sometimes leave pixel droppings?
411
412	Most fonts were not designed for terminal use, which means that character
413	size varies a lot. A font that is otherwise fine for terminal use might
414	contain some characters that are simply too wide. Rxvt-unicode will avoid
415	these characters. For characters that are just "a bit" too wide a special
416	"careful" rendering mode is used that redraws adjacent characters.
417
418	All of this requires that fonts do not lie about character sizes,
419	however: Xft fonts often draw glyphs larger than their acclaimed bounding
420	box, and rxvt-unicode has no way of detecting this (the correct way is to
421	ask for the character bounding box, which unfortunately is wrong in these
422	cases).	843	locales).
423		844
424	It's not clear (to me at least), wether this is a bug in Xft, freetype,	845	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
425	or the respective font. If you encounter this problem you might try using	846	programs doing the same (that is, most) will automatically agree in the
426	the C<-lsp> option to give the font more height. If that doesn't work, you	847	interpretation of characters.
427	might be forced to use a different font.
428		848
429	All of this is not a problem when using X11 core fonts, as their bounding	849	Unfortunately, there is no system-independent way to select locales, nor
430	box data is correct.	850	is there a standard on how locale specifiers will look like.
431		851
		852	On most systems, the content of the C<LC_CTYPE> environment variable
		853	contains an arbitrary string which corresponds to an already-installed
		854	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		855	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		856	(i.e. C<de> or C<german>) are also common.
		857
		858	Rxvt-unicode ignores all other locale categories, and except for
		859	the encoding, ignores country or language-specific settings,
		860	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		861	rxvt-unicode.
		862
		863	If you want to use a specific encoding you have to make sure you start
		864	rxvt-unicode with the correct C<LC_CTYPE> category.
		865
		866	=head3 Can I switch locales at runtime?
		867
		868	Yes, using an escape sequence. Try something like this, which sets
		869	rxvt-unicode's idea of C<LC_CTYPE>.
		870
		871	printf '\e]701;%s\007' ja_JP.SJIS
		872
		873	See also the previous answer.
		874
		875	Sometimes this capability is rather handy when you want to work in
		876	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		877	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		878	first switches to a locale supported by xjdic and back later:
		879
		880	printf '\e]701;%s\007' ja_JP.SJIS
		881	xjdic -js
		882	printf '\e]701;%s\007' de_DE.UTF-8
		883
		884	You can also use xterm's C<luit> program, which usually works fine, except
		885	for some locales where character width differs between program- and
		886	rxvt-unicode-locales.
		887
		888	=head3 I have problems getting my input method working.
		889
		890	Try a search engine, as this is slightly different for every input method server.
		891
		892	Here is a checklist:
		893
		894	=over 4
		895
		896	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		897
		898	Try C<locale -a> or check the documentation for your OS.
		899
		900	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		901
		902	For example, B<kinput2> does not support UTF-8 locales, you should use
		903	C<ja_JP.EUC-JP> or equivalent.
		904
		905	=item - Make sure your XIM server is actually running.
		906
		907	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		908
		909	When you want to use e.g. B<kinput2>, it must be set to
		910	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input
		911	method servers are running with this command:
		912
		913	xprop -root XIM_SERVERS
		914
		915	=item
		916
		917	=back
		918
		919	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		920
		921	You can specify separate locales for the input method and the rest of the
		922	terminal, using the resource C<imlocale>:
		923
		924	URxvt.imlocale: ja_JP.EUC-JP
		925
		926	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		927	use your input method. Please note, however, that, depending on your Xlib
		928	version, you may not be able to input characters outside C<EUC-JP> in a
		929	normal way then, as your input method limits you.
		930
		931	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		932
		933	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		934	design. Applications can avoid some crashes at the expense of memory
		935	leaks, and Input Methods can avoid some crashes by careful ordering at
		936	exit time. B<kinput2> (and derived input methods) generally succeeds,
		937	while B<SCIM> (or similar input methods) fails. In the end, however,
		938	crashes cannot be completely avoided even if both sides cooperate.
		939
		940	So the only workaround is not to kill your Input Method Servers.
		941
		942
		943	=head2 Operating Systems / Package Maintaining
		944
		945	=head3 I am using Debian GNU/Linux and have a problem...
		946
		947	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		948	patches that considerably change the behaviour of rxvt-unicode (but
		949	unfortunately this notice has been removed). Before reporting a bug to
		950	the original rxvt-unicode author please download and install the genuine
		951	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		952	the problem. If you cannot, chances are that the problems are specific to
		953	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		954	Tracking System (use C<reportbug> to report the bug).
		955
		956	For other problems that also affect the Debian package, you can and
		957	probably should use the Debian BTS, too, because, after all, it's also a
		958	bug in the Debian version and it serves as a reminder for other users that
		959	might encounter the same issue.
		960
		961	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		962
		963	You should build one binary with the default options. F<configure>
		964	now enables most useful options, and the trend goes to making them
		965	runtime-switchable, too, so there is usually no drawback to enbaling them,
		966	except higher disk and possibly memory usage. The perl interpreter should
		967	be enabled, as important functionality (menus, selection, likely more in
		968	the future) depends on it.
		969
		970	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		971	system-wide (except maybe with C<defaults>). This will result in useful
		972	behaviour. If your distribution aims at low memory, add an empty
		973	C<perl-ext-common> resource to the app-defaults file. This will keep the
		974	perl interpreter disabled until the user enables it.
		975
		976	If you can/want build more binaries, I recommend building a minimal
		977	one with C<--disable-everything> (very useful) and a maximal one with
		978	C<--enable-everything> (less useful, it will be very big due to a lot of
		979	encodings built-in that increase download times and are rarely used).
		980
		981	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		982
		983	It should be, starting with release 7.1. You are encouraged to properly
		984	install urxvt with privileges necessary for your OS now.
		985
		986	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		987	into a helper process for privileged operations (pty handling on some
		988	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		989	immediately. This is much safer than most other terminals that keep
		990	privileges while running (but is more relevant to urxvt, as it contains
		991	things as perl interpreters, which might be "helpful" to attackers).
		992
		993	This forking is done as the very first within main(), which is very early
		994	and reduces possible bugs to initialisation code run before main(), or
		995	things like the dynamic loader of your system, which should result in very
		996	little risk.
		997
432	=item On Solaris 9, many line-drawing characters are too wide.	998	=head3 On Solaris 9, many line-drawing characters are too wide.
433		999
434	Seems to be a known bug, read	1000	Seems to be a known bug, read
435	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1001	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
436	following ugly workaround to get non-double-wide-characters working:	1002	following ugly workaround to get non-double-wide-characters working:
437		1003
438	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1004	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
439		1005
440	=item My Compose (Multi_key) key is no longer working.
441
442	The most common causes for this are that either your locale is not set
443	correctly, or you specified a B<preeditStyle> that is not supported by
444	your input method. For example, if you specified B<OverTheSpot> and
445	your input method (e.g. the default input method handling Compose keys)
446	does not support this (for instance because it is not visual), then
447	rxvt-unicode will continue without an input method.
448
449	In this case either do not specify a B<preeditStyle> or specify more than
450	one pre-edit style, such as B<OverTheSpot,Root,None>.
451
452	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
453
454	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
455	international keyboards) or simply use ISO 14755 support to your
456	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
457	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
458	character and so on.
459
460	=item How can I keep rxvt-unicode from using reverse video so much?
461
462	First of all, make sure you are running with the right terminal settings
463	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
464	make sure you have specified colours for italic and bold, as otherwise
465	rxvt-unicode might use reverse video to simulate the effect:
466
467	URxvt.colorBD: white
468	URxvt.colorIT: green
469
470	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
471
472	For some unexplainable reason, some rare programs assume a very weird
473	colour palette when confronted with a terminal with more than the standard
474	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
475	these programs not to assume non-ISO colours without very good reasons.
476
477	In the meantime, you can either edit your C<rxvt-unicode> terminfo
478	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
479	fix colours but keep you from using other rxvt-unicode features.
480
481	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	1006	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
482		1007
483	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1008	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
484	in your compile environment, or an implementation that implements it,	1009	in your compile environment, or an implementation that implements it,
485	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1010	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
486	B<wchar_t> is represented as unicode.	1011	B<wchar_t> is represented as unicode.
…		…
508		1033
509	The rxvt-unicode author insists that the right way to fix this is in the	1034	The rxvt-unicode author insists that the right way to fix this is in the
510	system libraries once and for all, instead of forcing every app to carry	1035	system libraries once and for all, instead of forcing every app to carry
511	complete replacements for them :)	1036	complete replacements for them :)
512		1037
513	=item I use Solaris 9 and it doesn't compile/work/etc.	1038	=head3 I use Solaris 9 and it doesn't compile/work/etc.
514		1039
515	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1040	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
516	problems with C<wcwidth> and a compile problem.	1041	problems with C<wcwidth> and a compile problem.
517		1042
518	=item How can I use rxvt-unicode under cygwin?	1043	=head3 How can I use rxvt-unicode under cygwin?
519		1044
520	rxvt-unicode should compile and run out of the box on cygwin, using	1045	rxvt-unicode should compile and run out of the box on cygwin, using
521	the X11 libraries that come with cygwin. libW11 emulation is no	1046	the X11 libraries that come with cygwin. libW11 emulation is no
522	longer supported (and makes no sense, either, as it only supported a	1047	longer supported (and makes no sense, either, as it only supported a
523	single font). I recommend starting the X-server in C<-multiwindow> or	1048	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
526		1051
527	At the time of this writing, cygwin didn't seem to support any multi-byte	1052	At the time of this writing, cygwin didn't seem to support any multi-byte
528	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1053	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
529	to 8-bit encodings.	1054	to 8-bit encodings.
530		1055
531	=item How does rxvt-unicode determine the encoding to use?
532
533	=item Is there an option to switch encodings?
534
535	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
536	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
537	UTF-8 or any other encodings with respect to terminal I/O.
538
539	The reasons is that there exists a perfectly fine mechanism for selecting
540	the encoding, doing I/O and (most important) communicating this to all
541	applications so everybody agrees on character properties such as width
542	and code number. This mechanism is the I<locale>. Applications not using
543	that info will have problems (for example, C<xterm> gets the width of
544	characters wrong as it uses it's own, locale-independent table under all
545	locales).
546
547	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
548	programs doing the same (that is, most) will automatically agree in the
549	interpretation of characters.
550
551	Unfortunately, there is no system-independent way to select locales, nor
552	is there a standard on how locale specifiers will look like.
553
554	On most systems, the content of the C<LC_CTYPE> environment variable
555	contains an arbitrary string which corresponds to an already-installed
556	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
557	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
558	(i.e. C<de> or C<german>) are also common.
559
560	Rxvt-unicode ignores all other locale categories, and except for
561	the encoding, ignores country or language-specific settings,
562	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
563	rxvt-unicode.
564
565	If you want to use a specific encoding you have to make sure you start
566	rxvt-unicode with the correct C<LC_CTYPE> category.
567
568	=item Can I switch locales at runtime?
569
570	Yes, using an escape sequence. Try something like this, which sets
571	rxvt-unicode's idea of C<LC_CTYPE>.
572
573	printf '\e]701;%s\007' ja_JP.SJIS
574
575	See also the previous answer.
576
577	Sometimes this capability is rather handy when you want to work in
578	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
579	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
580	first switches to a locale supported by xjdic and back later:
581
582	printf '\e]701;%s\007' ja_JP.SJIS
583	xjdic -js
584	printf '\e]701;%s\007' de_DE.UTF-8
585
586	You can also use xterm's C<luit> program, which usually works fine, except
587	for some locales where character width differs between program- and
588	rxvt-unicode-locales.
589
590	=item Can I switch the fonts at runtime?
591
592	Yes, using an escape sequence. Try something like this, which has the same
593	effect as using the C<-fn> switch, and takes effect immediately:
594
595	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
596
597	This is useful if you e.g. work primarily with japanese (and prefer a
598	japanese font), but you have to switch to chinese temporarily, where
599	japanese fonts would only be in your way.
600
601	You can think of this as a kind of manual ISO-2022 switching.
602
603	=item Why do italic characters look as if clipped?
604
605	Many fonts have difficulties with italic characters and hinting. For
606	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
607	Mono> completely fails in it's italic face. A workaround might be to
608	enable freetype autohinting, i.e. like this:
609
610	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
611	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
612
613	=item My input method wants <some encoding> but I want UTF-8, what can I do?
614
615	You can specify separate locales for the input method and the rest of the
616	terminal, using the resource C<imlocale>:
617
618	URxvt*imlocale: ja_JP.EUC-JP
619
620	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
621	use your input method. Please note, however, that you will not be able to
622	input characters outside C<EUC-JP> in a normal way then, as your input
623	method limits you.
624
625	=item Rxvt-unicode crashes when the X Input Method changes or exits.
626
627	Unfortunately, this is unavoidable, as the XIM protocol is racy by
628	design. Applications can avoid some crashes at the expense of memory
629	leaks, and Input Methods can avoid some crashes by careful ordering at
630	exit time. B<kinput2> (and derived input methods) generally succeeds,
631	while B<SCIM> (or similar input methods) fails. In the end, however,
632	crashes cannot be completely avoided even if both sides cooperate.
633
634	So the only workaround is not to kill your Input Method Servers.
635
636	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
637
638	Rxvt-unicode tries to obey the rule of not charging you for something you
639	don't use. One thing you should try is to configure out all settings that
640	you don't need, for example, Xft support is a resource hog by design,
641	when used. Compiling it out ensures that no Xft font will be loaded
642	accidentally when rxvt-unicode tries to find a font for your characters.
643
644	Also, many people (me included) like large windows and even larger
645	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
646	6 bytes per screen cell. For a 160x?? window this amounts to almost a
647	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
648	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
649	rxvt-unicode then uses 8 bytes per screen cell.
650
651	=item Can I speed up Xft rendering somehow?
652
653	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
654	it is simply slow. If you still want Xft fonts you might try to disable
655	antialiasing (by appending C<:antialias=false>), which saves lots of
656	memory and also speeds up rendering considerably.
657
658	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
659
660	Rxvt-unicode will use whatever you specify as a font. If it needs to
661	fall back to it's default font search list it will prefer X11 core
662	fonts, because they are small and fast, and then use Xft fonts. It has
663	antialiasing disabled for most of them, because the author thinks they
664	look best that way.
665
666	If you want antialiasing, you have to specify the fonts manually.
667
668	=item Mouse cut/paste suddenly no longer works.
669
670	Make sure that mouse reporting is actually turned off since killing
671	some editors prematurely may leave the mouse in mouse report mode. I've
672	heard that tcsh may use mouse reporting unless it otherwise specified. A
673	quick check is to see if cut/paste works when the Alt or Shift keys are
674	depressed. See @@RXVT_NAME@@(7)
675
676	=item What's with this bold/blink stuff?
677
678	If no bold colour is set via C<colorBD:>, bold will invert text using the
679	standard foreground colour.
680
681	For the standard background colour, blinking will actually make the
682	text blink when compiled with C<--enable-blinking>. with standard
683	colours. Without C<--enable-blinking>, the blink attribute will be
684	ignored.
685
686	On ANSI colours, bold/blink attributes are used to set high-intensity
687	foreground/background colors.
688
689	color0-7 are the low-intensity colors.
690
691	color8-15 are the corresponding high-intensity colors.
692
693	=item I don't like the screen colors. How do I change them?
694
695	You can change the screen colors at run-time using F<~/.Xdefaults>
696	resources (or as long-options).
697
698	Here are values that are supposed to resemble a VGA screen,
699	including the murky brown that passes for low-intensity yellow:
700
701	URxvt.color0: #000000
702	URxvt.color1: #A80000
703	URxvt.color2: #00A800
704	URxvt.color3: #A8A800
705	URxvt.color4: #0000A8
706	URxvt.color5: #A800A8
707	URxvt.color6: #00A8A8
708	URxvt.color7: #A8A8A8
709
710	URxvt.color8: #000054
711	URxvt.color9: #FF0054
712	URxvt.color10: #00FF54
713	URxvt.color11: #FFFF54
714	URxvt.color12: #0000FF
715	URxvt.color13: #FF00FF
716	URxvt.color14: #00FFFF
717	URxvt.color15: #FFFFFF
718
719	And here is a more complete set of non-standard colors described (not by
720	me) as "pretty girly".
721
722	URxvt.cursorColor: #dc74d1
723	URxvt.pointerColor: #dc74d1
724	URxvt.background: #0e0e0e
725	URxvt.foreground: #4ad5e1
726	URxvt.color0: #000000
727	URxvt.color8: #8b8f93
728	URxvt.color1: #dc74d1
729	URxvt.color9: #dc74d1
730	URxvt.color2: #0eb8c7
731	URxvt.color10: #0eb8c7
732	URxvt.color3: #dfe37e
733	URxvt.color11: #dfe37e
734	URxvt.color5: #9e88f0
735	URxvt.color13: #9e88f0
736	URxvt.color6: #73f7ff
737	URxvt.color14: #73f7ff
738	URxvt.color7: #e1dddd
739	URxvt.color15: #e1dddd
740
741	=item How can I start @@RXVT_NAME@@d in a race-free way?
742
743	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
744	display, create the listening socket and then fork.
745
746	=item What's with the strange Backspace/Delete key behaviour?
747
748	Assuming that the physical Backspace key corresponds to the
749	BackSpace keysym (not likely for Linux ... see the following
750	question) there are two standard values that can be used for
751	Backspace: C<^H> and C<^?>.
752
753	Historically, either value is correct, but rxvt-unicode adopts the debian
754	policy of using C<^?> when unsure, because it's the one only only correct
755	choice :).
756
757	Rxvt-unicode tries to inherit the current stty settings and uses the value
758	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
759	started from a terminal (say, from a menu or by remote shell), then the
760	system value of `erase', which corresponds to CERASE in <termios.h>, will
761	be used (which may not be the same as your stty setting).
762
763	For starting a new rxvt-unicode:
764
765	# use Backspace = ^H
766	$ stty erase ^H
767	$ @@RXVT_NAME@@
768
769	# use Backspace = ^?
770	$ stty erase ^?
771	$ @@RXVT_NAME@@
772
773	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
774
775	For an existing rxvt-unicode:
776
777	# use Backspace = ^H
778	$ stty erase ^H
779	$ echo -n "^[[36h"
780
781	# use Backspace = ^?
782	$ stty erase ^?
783	$ echo -n "^[[36l"
784
785	This helps satisfy some of the Backspace discrepancies that occur, but
786	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
787	properly reflects that.
788
789	The Delete key is a another casualty of the ill-defined Backspace problem.
790	To avoid confusion between the Backspace and Delete keys, the Delete
791	key has been assigned an escape sequence to match the vt100 for Execute
792	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
793
794	Some other Backspace problems:
795
796	some editors use termcap/terminfo,
797	some editors (vim I'm told) expect Backspace = ^H,
798	GNU Emacs (and Emacs-like editors) use ^H for help.
799
800	Perhaps someday this will all be resolved in a consistent manner.
801
802	=item I don't like the key-bindings. How do I change them?
803
804	There are some compile-time selections available via configure. Unless
805	you have run "configure" with the C<--disable-resources> option you can
806	use the `keysym' resource to alter the keystrings associated with keysyms.
807
808	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
809
810	URxvt.keysym.Home: \033[1~
811	URxvt.keysym.End: \033[4~
812	URxvt.keysym.C-apostrophe: \033<C-'>
813	URxvt.keysym.C-slash: \033<C-/>
814	URxvt.keysym.C-semicolon: \033<C-;>
815	URxvt.keysym.C-grave: \033<C-`>
816	URxvt.keysym.C-comma: \033<C-,>
817	URxvt.keysym.C-period: \033<C-.>
818	URxvt.keysym.C-0x60: \033<C-`>
819	URxvt.keysym.C-Tab: \033<C-Tab>
820	URxvt.keysym.C-Return: \033<C-Return>
821	URxvt.keysym.S-Return: \033<S-Return>
822	URxvt.keysym.S-space: \033<S-Space>
823	URxvt.keysym.M-Up: \033<M-Up>
824	URxvt.keysym.M-Down: \033<M-Down>
825	URxvt.keysym.M-Left: \033<M-Left>
826	URxvt.keysym.M-Right: \033<M-Right>
827	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
828	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
829	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
830
831	See some more examples in the documentation for the B<keysym> resource.
832
833	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
834	How do I make use of them? For example, the Sun Keyboard type 4
835	has the following mappings that rxvt-unicode doesn't recognize.
836
837	KP_Insert == Insert
838	F22 == Print
839	F27 == Home
840	F29 == Prior
841	F33 == End
842	F35 == Next
843
844	Rather than have rxvt-unicode try to accommodate all the various possible
845	keyboard mappings, it is better to use `xmodmap' to remap the keys as
846	required for your particular machine.
847
848	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
849	I need this to decide about setting colors etc.
850
851	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
852	check and see if that is set. Note that several programs, JED, slrn,
853	Midnight Commander automatically check this variable to decide whether or
854	not to use color.
855
856	=item How do I set the correct, full IP address for the DISPLAY variable?
857
858	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
859	insecure mode then it is possible to use the following shell script
860	snippets to correctly set the display. If your version of rxvt-unicode
861	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
862	the COLORTERM variable can be used to distinguish rxvt-unicode from a
863	regular xterm.
864
865	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
866	snippets:
867
868	# Bourne/Korn/POSIX family of shells:
869	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
870	if [ ${TERM:-foo} = xterm ]; then
871	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
872	echo -n '^[Z'
873	read term_id
874	stty icanon echo
875	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
876	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
877	read DISPLAY # set it in our local shell
878	fi
879	fi
880
881	=item How do I compile the manual pages for myself?
882
883	You need to have a recent version of perl installed as F</usr/bin/perl>,
884	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
885	the doc subdirectory and enter C<make alldoc>.
886
887	=item My question isn't answered here, can I ask a human?
888
889	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
890	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
891	interested in learning about new and exciting problems (but not FAQs :).
892
893	=back
894
895	=head1 RXVT TECHNICAL REFERENCE	1056	=head1 RXVT-UNICODE TECHNICAL REFERENCE
896
897	=head1 DESCRIPTION
898		1057
899	The rest of this document describes various technical aspects of	1058	The rest of this document describes various technical aspects of
900	B<rxvt-unicode>. First the description of supported command sequences,	1059	B<rxvt-unicode>. First the description of supported command sequences,
901	followed by menu and pixmap support and last by a description of all	1060	followed by pixmap support and last by a description of all features
902	features selectable at C<configure> time.	1061	selectable at C<configure> time.
903		1062
904	=head1 Definitions	1063	=head2 Definitions
905		1064
906	=over 4	1065	=over 4
907		1066
908	=item B<< C<c> >>	1067	=item B<< C<c> >>
909		1068
…		…
927		1086
928	A text parameter composed of printable characters.	1087	A text parameter composed of printable characters.
929		1088
930	=back	1089	=back
931		1090
932	=head1 Values	1091	=head2 Values
933		1092
934	=over 4	1093	=over 4
935		1094
936	=item B<< C<ENQ> >>	1095	=item B<< C<ENQ> >>
937		1096
…		…
980		1139
981	Space Character	1140	Space Character
982		1141
983	=back	1142	=back
984		1143
985	=head1 Escape Sequences	1144	=head2 Escape Sequences
986		1145
987	=over 4	1146	=over 4
988		1147
989	=item B<< C<ESC # 8> >>	1148	=item B<< C<ESC # 8> >>
990		1149
…		…
1088		1247
1089	=back	1248	=back
1090		1249
1091	X<CSI>	1250	X<CSI>
1092		1251
1093	=head1 CSI (Command Sequence Introducer) Sequences	1252	=head2 CSI (Command Sequence Introducer) Sequences
1094		1253
1095	=over 4	1254	=over 4
1096		1255
1097	=item B<< C<ESC [ Ps @> >>	1256	=item B<< C<ESC [ Ps @> >>
1098		1257
…		…
1368		1527
1369	=back	1528	=back
1370		1529
1371	X<PrivateModes>	1530	X<PrivateModes>
1372		1531
1373	=head1 DEC Private Modes	1532	=head2 DEC Private Modes
1374		1533
1375	=over 4	1534	=over 4
1376		1535
1377	=item B<< C<ESC [ ? Pm h> >>	1536	=item B<< C<ESC [ ? Pm h> >>
1378		1537
…		…
1475	B<< C<h> >> Send Mouse X & Y on button press.	1634	B<< C<h> >> Send Mouse X & Y on button press.
1476	B<< C<l> >> No mouse reporting.	1635	B<< C<l> >> No mouse reporting.
1477		1636
1478	=end table	1637	=end table
1479		1638
1480	=item B<< C<Ps = 10> >> (B<rxvt>)
1481
1482	=begin table
1483
1484	B<< C<h> >> menuBar visible
1485	B<< C<l> >> menuBar invisible
1486
1487	=end table
1488
1489	=item B<< C<Ps = 25> >>	1639	=item B<< C<Ps = 25> >>
1490		1640
1491	=begin table	1641	=begin table
1492		1642
1493	B<< C<h> >> Visible cursor {cnorm/cvvis}	1643	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
1651		1801
1652	=back	1802	=back
1653		1803
1654	X<XTerm>	1804	X<XTerm>
1655		1805
1656	=head1 XTerm Operating System Commands	1806	=head2 XTerm Operating System Commands
1657		1807
1658	=over 4	1808	=over 4
1659		1809
1660	=item B<< C<ESC ] Ps;Pt ST> >>	1810	=item B<< C<ESC ] Ps;Pt ST> >>
1661		1811
…		…
1675	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	1825	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1676	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1826	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1677	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1827	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1678	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]	1828	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1679	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]	1829	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1680	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1830	B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM).
1681	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.	1831	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1682	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1832	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1683	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	1833	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1684	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>	1834	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>
1685	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1835	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1686	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).	1836	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).
1687	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).	1837	B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>.
1688	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1838	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1689	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	1839	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1690	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>	1840	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
1691	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>	1841	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1692	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1842	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
…		…
1699		1849
1700	=end table	1850	=end table
1701		1851
1702	=back	1852	=back
1703		1853
1704	X<menuBar>
1705
1706	=head1 menuBar
1707
1708	B<< The exact syntax used is I<almost> solidified. >>
1709	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1710	menuBar.
1711
1712	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1713	omitted: use B<./> to specify a menu relative to the current menu.
1714
1715	=head2 Overview of menuBar operation
1716
1717	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1718	of C<Pt> can be used for a variety of tasks:
1719
1720	At the top level is the current menuBar which is a member of a circular
1721	linked-list of other such menuBars.
1722
1723	The menuBar acts as a parent for the various drop-down menus, which in
1724	turn, may have labels, separator lines, menuItems and subMenus.
1725
1726	The menuItems are the useful bits: you can use them to mimic keyboard
1727	input or even to send text or escape sequences back to rxvt.
1728
1729	The menuBar syntax is intended to provide a simple yet robust method of
1730	constructing and manipulating menus and navigating through the
1731	menuBars.
1732
1733	The first step is to use the tag B<< [menu:I<name>] >> which creates
1734	the menuBar called I<name> and allows access. You may now or menus,
1735	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1736	menuBar access as B<readonly> to prevent accidental corruption of the
1737	menus. To re-access the current menuBar for alterations, use the tag
1738	B<[menu]>, make the alterations and then use B<[done]>
1739
1740	X<menuBarCommands>
1741
1742	=head2 Commands
1743
1744	=over 4
1745
1746	=item B<< [menu:+I<name>] >>
1747
1748	access the named menuBar for creation or alteration. If a new menuBar
1749	is created, it is called I<name> (max of 15 chars) and the current
1750	menuBar is pushed onto the stack
1751
1752	=item B<[menu]>
1753
1754	access the current menuBar for alteration
1755
1756	=item B<< [title:+I<string>] >>
1757
1758	set the current menuBar's title to I<string>, which may contain the
1759	following format specifiers:
1760
1761	B<%n> rxvt name (as per the B<-name> command-line option)
1762	B<%v> rxvt version
1763	B<%%> literal B<%> character
1764
1765	=item B<[done]>
1766
1767	set menuBar access as B<readonly>.
1768	End-of-file tag for B<< [read:+I<file>] >> operations.
1769
1770	=item B<< [read:+I<file>] >>
1771
1772	read menu commands directly from I<file> (extension ".menu" will be
1773	appended if required.) Start reading at a line with B<[menu]> or B<<
1774	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1775
1776	Blank and comment lines (starting with B<#>) are ignored. Actually,
1777	since any invalid menu commands are also ignored, almost anything could
1778	be construed as a comment line, but this may be tightened up in the
1779	future ... so don't count on it!.
1780
1781	=item B<< [read:+I<file>;+I<name>] >>
1782
1783	The same as B<< [read:+I<file>] >>, but start reading at a line with
1784	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1785	B<[done]> is encountered.
1786
1787	=item B<[dump]>
1788
1789	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1790	later rereading.
1791
1792	=item B<[rm:name]>
1793
1794	remove the named menuBar
1795
1796	=item B<[rm] [rm:]>
1797
1798	remove the current menuBar
1799
1800	=item B<[rm*] [rm:*]>
1801
1802	remove all menuBars
1803
1804	=item B<[swap]>
1805
1806	swap the top two menuBars
1807
1808	=item B<[prev]>
1809
1810	access the previous menuBar
1811
1812	=item B<[next]>
1813
1814	access the next menuBar
1815
1816	=item B<[show]>
1817
1818	Enable display of the menuBar
1819
1820	=item B<[hide]>
1821
1822	Disable display of the menuBar
1823
1824	=item B<< [pixmap:+I<name>] >>
1825
1826	=item B<< [pixmap:+I<name>;I<scaling>] >>
1827
1828	(set the background pixmap globally
1829
1830	B<< A Future implementation I<may> make this local to the menubar >>)
1831
1832	=item B<< [:+I<command>:] >>
1833
1834	ignore the menu readonly status and issue a I<command> to or a menu or
1835	menuitem or change the ; a useful shortcut for setting the quick arrows
1836	from a menuBar.
1837
1838	=back
1839
1840	X<menuBarAdd>
1841
1842	=head2 Adding and accessing menus
1843
1844	The following commands may also be B<+> prefixed.
1845
1846	=over 4
1847
1848	=item B</+>
1849
1850	access menuBar top level
1851
1852	=item B<./+>
1853
1854	access current menu level
1855
1856	=item B<../+>
1857
1858	access parent menu (1 level up)
1859
1860	=item B<../../>
1861
1862	access parent menu (multiple levels up)
1863
1864	=item B<< I</path/>menu >>
1865
1866	add/access menu
1867
1868	=item B<< I</path/>menu/* >>
1869
1870	add/access menu and clear it if it exists
1871
1872	=item B<< I</path/>{-} >>
1873
1874	add separator
1875
1876	=item B<< I</path/>{item} >>
1877
1878	add B<item> as a label
1879
1880	=item B<< I</path/>{item} action >>
1881
1882	add/alter I<menuitem> with an associated I<action>
1883
1884	=item B<< I</path/>{item}{right-text} >>
1885
1886	add/alter I<menuitem> with B<right-text> as the right-justified text
1887	and as the associated I<action>
1888
1889	=item B<< I</path/>{item}{rtext} action >>
1890
1891	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1892	the right-justified text.
1893
1894	=back
1895
1896	=over 4
1897
1898	=item Special characters in I<action> must be backslash-escaped:
1899
1900	B<\a \b \E \e \n \r \t \octal>
1901
1902	=item or in control-character notation:
1903
1904	B<^@, ^A .. ^Z .. ^_, ^?>
1905
1906	=back
1907
1908	To send a string starting with a B<NUL> (B<^@>) character to the
1909	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1910	the first of which will be stripped off and the balance directed to the
1911	program. Otherwise if I<action> begins with B<NUL> followed by
1912	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1913	balance is sent back to rxvt.
1914
1915	As a convenience for the many Emacs-type editors, I<action> may start
1916	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1917	appended if missed from B<M-x> commands.
1918
1919	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1920	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1921
1922	=over 4
1923
1924	=item For example,
1925
1926	B<M-xapropos> is equivalent to B<\Exapropos\r>
1927
1928	=item and
1929
1930	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1931
1932	=back
1933
1934	The option B<< {I<right-rtext>} >> will be right-justified. In the
1935	absence of a specified action, this text will be used as the I<action>
1936	as well.
1937
1938	=over 4
1939
1940	=item For example,
1941
1942	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1943
1944	=back
1945
1946	The left label I<is> necessary, since it's used for matching, but
1947	implicitly hiding the left label (by using same name for both left and
1948	right labels), or explicitly hiding the left label (by preceeding it
1949	with a dot), makes it possible to have right-justified text only.
1950
1951	=over 4
1952
1953	=item For example,
1954
1955	B</File/{Open}{Open} Open-File-Action>
1956
1957	=item or hiding it
1958
1959	B</File/{.anylabel}{Open} Open-File-Action>
1960
1961	=back
1962
1963	X<menuBarRemove>
1964
1965	=head2 Removing menus
1966
1967	=over 4
1968
1969	=item B<< -/*+ >>
1970
1971	remove all menus from the menuBar, the same as B<[clear]>
1972
1973	=item B<< -+I</path>menu+ >>
1974
1975	remove menu
1976
1977	=item B<< -+I</path>{item}+ >>
1978
1979	remove item
1980
1981	=item B<< -+I</path>{-} >>
1982
1983	remove separator)
1984
1985	=item B<-/path/menu/*>
1986
1987	remove all items, separators and submenus from menu
1988
1989	=back
1990
1991	X<menuBarArrows>
1992
1993	=head2 Quick Arrows
1994
1995	The menus also provide a hook for I<quick arrows> to provide easier
1996	user access. If nothing has been explicitly set, the default is to
1997	emulate the curror keys. The syntax permits each arrow to be altered
1998	individually or all four at once without re-entering their common
1999	beginning/end text. For example, to explicitly associate cursor actions
2000	with the arrows, any of the following forms could be used:
2001
2002	=over 4
2003
2004	=item B<< <r>+I<Right> >>
2005
2006	=item B<< <l>+I<Left> >>
2007
2008	=item B<< <u>+I<Up> >>
2009
2010	=item B<< <d>+I<Down> >>
2011
2012	Define actions for the respective arrow buttons
2013
2014	=item B<< <b>+I<Begin> >>
2015
2016	=item B<< <e>+I<End> >>
2017
2018	Define common beginning/end parts for I<quick arrows> which used in
2019	conjunction with the above <r> <l> <u> <d> constructs
2020
2021	=back
2022
2023	=over 4
2024
2025	=item For example, define arrows individually,
2026
2027	<u>\E[A
2028
2029	<d>\E[B
2030
2031	<r>\E[C
2032
2033	<l>\E[D
2034
2035	=item or all at once
2036
2037	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
2038
2039	=item or more compactly (factoring out common parts)
2040
2041	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
2042
2043	=back
2044
2045	X<menuBarSummary>
2046
2047	=head2 Command Summary
2048
2049	A short summary of the most I<common> commands:
2050
2051	=over 4
2052
2053	=item [menu:name]
2054
2055	use an existing named menuBar or start a new one
2056
2057	=item [menu]
2058
2059	use the current menuBar
2060
2061	=item [title:string]
2062
2063	set menuBar title
2064
2065	=item [done]
2066
2067	set menu access to readonly and, if reading from a file, signal EOF
2068
2069	=item [done:name]
2070
2071	if reading from a file using [read:file;name] signal EOF
2072
2073	=item [rm:name]
2074
2075	remove named menuBar(s)
2076
2077	=item [rm] [rm:]
2078
2079	remove current menuBar
2080
2081	=item [rm*] [rm:*]
2082
2083	remove all menuBar(s)
2084
2085	=item [swap]
2086
2087	swap top two menuBars
2088
2089	=item [prev]
2090
2091	access the previous menuBar
2092
2093	=item [next]
2094
2095	access the next menuBar
2096
2097	=item [show]
2098
2099	map menuBar
2100
2101	=item [hide]
2102
2103	unmap menuBar
2104
2105	=item [pixmap;file]
2106
2107	=item [pixmap;file;scaling]
2108
2109	set a background pixmap
2110
2111	=item [read:file]
2112
2113	=item [read:file;name]
2114
2115	read in a menu from a file
2116
2117	=item [dump]
2118
2119	dump out all menuBars to /tmp/rxvt-PID
2120
2121	=item /
2122
2123	access menuBar top level
2124
2125	=item ./
2126
2127	=item ../
2128
2129	=item ../../
2130
2131	access current or parent menu level
2132
2133	=item /path/menu
2134
2135	add/access menu
2136
2137	=item /path/{-}
2138
2139	add separator
2140
2141	=item /path/{item}{rtext} action
2142
2143	add/alter menu item
2144
2145	=item -/*
2146
2147	remove all menus from the menuBar
2148
2149	=item -/path/menu
2150
2151	remove menu items, separators and submenus from menu
2152
2153	=item -/path/menu
2154
2155	remove menu
2156
2157	=item -/path/{item}
2158
2159	remove item
2160
2161	=item -/path/{-}
2162
2163	remove separator
2164
2165	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
2166
2167	menu quick arrows
2168
2169	=back
2170	X<XPM>
2171
2172	=head1 XPM	1854	=head1 XPM
2173		1855
2174	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1856	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
2175	of B<< C<Pt> >> can be the name of the background pixmap followed by a	1857	of B<< C<Pt> >> can be the name of the background pixmap followed by a
2176	sequence of scaling/positioning commands separated by semi-colons. The	1858	sequence of scaling/positioning commands separated by semi-colons. The
…		…
2273	=begin table	1955	=begin table
2274		1956
2275	4 Shift	1957	4 Shift
2276	8 Meta	1958	8 Meta
2277	16 Control	1959	16 Control
2278	32 Double Click I<(Rxvt extension)>	1960	32 Double Click I<(rxvt extension)>
2279		1961
2280	=end table	1962	=end table
2281		1963
2282	Col = B<< C<< <x> - SPACE >> >>	1964	Col = B<< C<< <x> - SPACE >> >>
2283		1965
…		…
2421	alternative input methods (e.g. kinput2) and will also correctly	2103	alternative input methods (e.g. kinput2) and will also correctly
2422	set up the input for people using dead keys or compose keys.	2104	set up the input for people using dead keys or compose keys.
2423		2105
2424	=item --enable-unicode3 (default: off)	2106	=item --enable-unicode3 (default: off)
2425		2107
		2108	Recommended to stay off unless you really need non-BMP characters.
		2109
2426	Enable direct support for displaying unicode codepoints above	2110	Enable direct support for displaying unicode codepoints above
2427	65535 (the basic multilingual page). This increases storage	2111	65535 (the basic multilingual page). This increases storage
2428	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2112	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2429	support these extra characters, but Xft does.	2113	support these extra characters, but Xft does.
2430		2114
…		…
2440	composite characters. This is required for proper viewing of text	2124	composite characters. This is required for proper viewing of text
2441	where accents are encoded as seperate unicode characters. This is	2125	where accents are encoded as seperate unicode characters. This is
2442	done by using precomposited characters when available or creating	2126	done by using precomposited characters when available or creating
2443	new pseudo-characters when no precomposed form exists.	2127	new pseudo-characters when no precomposed form exists.
2444		2128
2445	Without --enable-unicode3, the number of additional precomposed characters	2129	Without --enable-unicode3, the number of additional precomposed
2446	is rather limited (2048, if this is full, rxvt-unicode will use the	2130	characters is somewhat limited (the 6400 private use characters will be
2447	private use area, extending the number of combinations to 8448). With
2448	--enable-unicode3, no practical limit exists.	2131	(ab-)used). With --enable-unicode3, no practical limit exists.
2449		2132
2450	This option will also enable storage (but not display) of characters	2133	This option will also enable storage (but not display) of characters
2451	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2134	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2452		2135
2453	The combining table also contains entries for arabic presentation forms,	2136	The combining table also contains entries for arabic presentation forms,
2454	but these are not currently used. Bug me if you want these to be used (and	2137	but these are not currently used. Bug me if you want these to be used (and
2455	tell me how these are to be used...).	2138	tell me how these are to be used...).
2456		2139
2457	=item --enable-fallback(=CLASS) (default: Rxvt)	2140	=item --enable-fallback(=CLASS) (default: Rxvt)
2458		2141
2459	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.	2142	When reading resource settings, also read settings for class CLASS. To
		2143	disable resource fallback use --disable-fallback.
2460		2144
2461	=item --with-res-name=NAME (default: urxvt)	2145	=item --with-res-name=NAME (default: urxvt)
2462		2146
2463	Use the given name as default application name when	2147	Use the given name as default application name when
2464	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2148	reading resources. Specify --with-res-name=rxvt to replace rxvt.
…		…
2501		2185
2502	=item --enable-tinting (default: on)	2186	=item --enable-tinting (default: on)
2503		2187
2504	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).	2188	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2505		2189
2506	=item --enable-menubar (default: off) [DEPRECATED]
2507
2508	Add support for our menu bar system (this interacts badly with dynamic
2509	locale switching currently). This option is DEPRECATED and will be removed
2510	in the future.
2511
2512	=item --enable-rxvt-scroll (default: on)	2190	=item --enable-rxvt-scroll (default: on)
2513		2191
2514	Add support for the original rxvt scrollbar.	2192	Add support for the original rxvt scrollbar.
2515		2193
2516	=item --enable-next-scroll (default: on)	2194	=item --enable-next-scroll (default: on)
…		…
2525		2203
2526	Add support for a very unobtrusive, plain-looking scrollbar that	2204	Add support for a very unobtrusive, plain-looking scrollbar that
2527	is the favourite of the rxvt-unicode author, having used it for	2205	is the favourite of the rxvt-unicode author, having used it for
2528	many years.	2206	many years.
2529		2207
2530	=item --enable-half-shadow (default: off)
2531
2532	Make shadows on the scrollbar only half the normal width & height.
2533	only applicable to rxvt scrollbars.
2534
2535	=item --enable-ttygid (default: off)	2208	=item --enable-ttygid (default: off)
2536		2209
2537	Change tty device setting to group "tty" - only use this if	2210	Change tty device setting to group "tty" - only use this if
2538	your system uses this type of security.	2211	your system uses this type of security.
2539		2212
…		…
2547	do it.	2220	do it.
2548		2221
2549	=item --disable-resources	2222	=item --disable-resources
2550		2223
2551	Removes any support for resource checking.	2224	Removes any support for resource checking.
2552
2553	=item --enable-strings (default: off)
2554
2555	Add support for our possibly faster memset() function and other
2556	various routines, overriding your system's versions which may
2557	have been hand-crafted in assembly or may require extra libraries
2558	to link in. (this breaks ANSI-C rules and has problems on many
2559	GNU/Linux systems).
2560		2225
2561	=item --disable-swapscreen	2226	=item --disable-swapscreen
2562		2227
2563	Remove support for secondary/swap screen.	2228	Remove support for secondary/swap screen.
2564		2229
…		…
2573		2238
2574	MWM-hints	2239	MWM-hints
2575	EWMH-hints (pid, utf8 names) and protocols (ping)	2240	EWMH-hints (pid, utf8 names) and protocols (ping)
2576	seperate underline colour (-underlineColor)	2241	seperate underline colour (-underlineColor)
2577	settable border widths and borderless switch (-w, -b, -bl)	2242	settable border widths and borderless switch (-w, -b, -bl)
		2243	visual depth selection (-depth)
2578	settable extra linespacing /-lsp)	2244	settable extra linespacing /-lsp)
2579	iso-14755-2 and -3, and visual feedback	2245	iso-14755-2 and -3, and visual feedback
2580	backindex and forwardindex escape sequence
2581	window op and some xterm/OSC escape sequences
2582	tripleclickwords (-tcw)	2246	tripleclickwords (-tcw)
2583	settable insecure mode (-insecure)	2247	settable insecure mode (-insecure)
2584	keysym remapping support	2248	keysym remapping support
2585	cursor blinking and underline cursor (-cb, -uc)	2249	cursor blinking and underline cursor (-cb, -uc)
2586	XEmbed support (-embed)	2250	XEmbed support (-embed)
2587	user-pty (-pty-fd)	2251	user-pty (-pty-fd)
2588	hold on exit (-hold)	2252	hold on exit (-hold)
2589	skip builtin block graphics (-sbg)	2253	skip builtin block graphics (-sbg)
		2254
		2255	It also enabled some non-essential features otherwise disabled, such as:
		2256
		2257	some round-trip time optimisations
		2258	nearest color allocation on pseudocolor screens
		2259	UTF8_STRING supporr for selection
2590	sgr modes 90..97 and 100..107	2260	sgr modes 90..97 and 100..107
		2261	backindex and forwardindex escape sequences
		2262	view change/zero scorllback esacpe sequences
		2263	locale switching escape sequence
		2264	window op and some xterm/OSC escape sequences
		2265	rectangular selections
		2266	trailing space removal for selections
		2267	verbose X error handling
2591		2268
2592	=item --enable-iso14755 (default: on)	2269	=item --enable-iso14755 (default: on)
2593		2270
2594	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2271	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2595	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2272	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2616	Remove support for mouse selection style like that of xterm.	2293	Remove support for mouse selection style like that of xterm.
2617		2294
2618	=item --enable-dmalloc (default: off)	2295	=item --enable-dmalloc (default: off)
2619		2296
2620	Use Gray Watson's malloc - which is good for debugging See	2297	Use Gray Watson's malloc - which is good for debugging See
2621	http://www.letters.com/dmalloc/ for details If you use either this or the	2298	L<http://www.letters.com/dmalloc/> for details If you use either this or the
2622	next option, you may need to edit src/Makefile after compiling to point	2299	next option, you may need to edit src/Makefile after compiling to point
2623	DINCLUDE and DLIB to the right places.	2300	DINCLUDE and DLIB to the right places.
2624		2301
2625	You can only use either this option and the following (should	2302	You can only use either this option and the following (should
2626	you use either) .	2303	you use either) .
…		…
2638		2315
2639	=item --enable-pointer-blank (default: on)	2316	=item --enable-pointer-blank (default: on)
2640		2317
2641	Add support to have the pointer disappear when typing or inactive.	2318	Add support to have the pointer disappear when typing or inactive.
2642		2319
2643	=item --enable-perl (default: off)	2320	=item --enable-perl (default: on)
2644		2321
2645	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>	2322	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2646	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files	2323	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
2647	in F<src/perl-ext/> for the extensions that are installed by default. The	2324	in F<src/perl-ext/> for the extensions that are installed by default. The
2648	perl interpreter that is used can be specified via the C<PERL> environment	2325	perl interpreter that is used can be specified via the C<PERL> environment

Diff Legend

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