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.93 by root, Mon Jan 30 19:46:13 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, how can I select	27	=head2 Meta, Features & Commandline Issues
30	single words?
31		28
32	Yes. For example, if you want to select alphanumeric words, you can use	29	=head3 My question isn't answered here, can I ask a human?
33	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	Please also note that the I<LeftClick Shift-LeftClik> combination also	43	URxvt.perl-ext-common: default,tabbed
45	selects words like the old code.
46		44
47	=item I don't like the new selection/popups/hotkeys/perl, how do I	45	It will also work fine with tabbing functionality of many window managers
48	change/disable it?	46	or similar tabbing programs, and its embedding-features allow it to be
		47	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		48	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		49	(murxvt) terminal as an example embedding application.
49		50
50	You can disable the perl extension completely by setting the	51	=head3 How do I know which rxvt-unicode version I'm using?
51	B<perl-ext-common> resource to the empty string, which also keeps
52	rxvt-unicode from initialising perl, saving memory.
53		52
54	If you only want to disable specific features, you first have to	53	The version number is displayed with the usage (-h). Also the escape
55	identify which perl extension is responsible. For this, read the section	54	sequence C<ESC [ 8 n> sets the window title to the version number. When
56	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For	55	using the @@URXVT_NAME@@c client, the version displayed is that of the
57	example, to disable the B<selection-popup> and B<option-popup>, specify	56	daemon.
58	this B<perl-ext-common> resource:
59		57
60	URxvt.perl-ext-common: default,-selection-popup,-option-popup	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
61		59
62	This will keep the default extensions, but disable the two popup	60	Rxvt-unicode tries to obey the rule of not charging you for something you
63	extensions. Some extensions can also be configured, for example,	61	don't use. One thing you should try is to configure out all settings that
64	scrollback search mode is triggered by B<M-s>. You can move it to any	62	you don't need, for example, Xft support is a resource hog by design,
65	other combination either by setting the B<searchable-scrollback> resource:	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.
66		65
67	URxvt.searchable-scrollback: CM-s	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.
68		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
69	=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?
70		134
71	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
72	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
73	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
74	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
…		…
78		142
79	text data bss drs rss filename	143	text data bss drs rss filename
80	98398 1664 24 15695 1824 rxvt --disable-everything	144	98398 1664 24 15695 1824 rxvt --disable-everything
81	188985 9048 66616 18222 1788 urxvt --disable-everything	145	188985 9048 66616 18222 1788 urxvt --disable-everything
82		146
83	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
84	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
85	libc), the two diverge, but not unreasnobaly so.	149	libc), the two diverge, but not unreasnobaly so.
86		150
87	text data bss drs rss filename	151	text data bss drs rss filename
88	163431 2152 24 20123 2060 rxvt --enable-everything	152	163431 2152 24 20123 2060 rxvt --enable-everything
…		…
106	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
107	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
108	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
109	extremely well *g*.	173	extremely well *g*.
110		174
111	=item Why C++, isn't that unportable/bloated/uncool?	175	=head3 Why C++, isn't that unportable/bloated/uncool?
112		176
113	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
114	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
115	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
116	shorter: It simply wouldn't exist without C++.	180	shorter: It simply wouldn't exist without C++.
…		…
140	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
141		205
142	No large bloated libraries (of course, none were linked in statically),	206	No large bloated libraries (of course, none were linked in statically),
143	except maybe libX11 :)	207	except maybe libX11 :)
144		208
145	=item Does it support tabs, can I have a tabbed rxvt-unicode?
146		209
147	Beginning with version 7.3, there is a perl extension that implements a	210	=head2 Rendering, Font & Look and Feel Issues
148	simple tabbed terminal. It is installed by default, so any of these should
149	give you tabs:
150		211
151	@@RXVT_NAME@@ -pe tabbed	212	=head3 I can't get transparency working, what am I doing wrong?
152		213
		214	First of all, transparency isn't officially supported in rxvt-unicode, so
		215	you are mostly on your own. Do not bug the author about it (but you may
		216	bug everybody else). Also, if you can't get it working consider it a rite
		217	of passage: ... and you failed.
		218
		219	Here are four ways to get transparency. B<Do> read the manpage and option
		220	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
		221
		222	1. Use inheritPixmap:
		223
		224	Esetroot wallpaper.jpg
		225	@@URXVT_NAME@@ -ip -tint red -sh 40
		226
		227	That works. If you think it doesn't, you lack transparency and tinting
		228	support, or you are unable to read.
		229
		230	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		231	to use effects other than tinting and shading: Just shade/tint/whatever
		232	your picture with gimp or any other tool:
		233
		234	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		235	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
		236
		237	That works. If you think it doesn't, you lack XPM and Perl support, or you
		238	are unable to read.
		239
		240	3. Use an ARGB visual:
		241
		242	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		243
		244	This requires XFT support, and the support of your X-server. If that
		245	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		246	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		247	bugfixes and workarounds for Xft and Xlib to make it work, but that
		248	doesn't mean that your WM has the required kludges in place.
		249
		250	4. Use xcompmgr and let it do the job:
		251
		252	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		253	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		254
		255	Then click on a window you want to make transparent. Replace C<0xc0000000>
		256	by other values to change the degree of opacity. If it doesn't work and
		257	your server crashes, you got to keep the pieces.
		258
		259	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		260
		261	Most fonts were not designed for terminal use, which means that character
		262	size varies a lot. A font that is otherwise fine for terminal use might
		263	contain some characters that are simply too wide. Rxvt-unicode will avoid
		264	these characters. For characters that are just "a bit" too wide a special
		265	"careful" rendering mode is used that redraws adjacent characters.
		266
		267	All of this requires that fonts do not lie about character sizes,
		268	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		269	box, and rxvt-unicode has no way of detecting this (the correct way is to
		270	ask for the character bounding box, which unfortunately is wrong in these
		271	cases).
		272
		273	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		274	or the respective font. If you encounter this problem you might try using
		275	the C<-lsp> option to give the font more height. If that doesn't work, you
		276	might be forced to use a different font.
		277
		278	All of this is not a problem when using X11 core fonts, as their bounding
		279	box data is correct.
		280
		281	=head3 How can I keep rxvt-unicode from using reverse video so much?
		282
		283	First of all, make sure you are running with the right terminal settings
		284	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		285	make sure you have specified colours for italic and bold, as otherwise
		286	rxvt-unicode might use reverse video to simulate the effect:
		287
		288	URxvt.colorBD: white
		289	URxvt.colorIT: green
		290
		291	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		292
		293	For some unexplainable reason, some rare programs assume a very weird
		294	colour palette when confronted with a terminal with more than the standard
		295	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		296	these programs not to assume non-ISO colours without very good reasons.
		297
		298	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		299	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		300	fix colours but keep you from using other rxvt-unicode features.
		301
		302	=head3 Can I switch the fonts at runtime?
		303
		304	Yes, using an escape sequence. Try something like this, which has the same
		305	effect as using the C<-fn> switch, and takes effect immediately:
		306
		307	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		308
		309	This is useful if you e.g. work primarily with japanese (and prefer a
		310	japanese font), but you have to switch to chinese temporarily, where
		311	japanese fonts would only be in your way.
		312
		313	You can think of this as a kind of manual ISO-2022 switching.
		314
		315	=head3 Why do italic characters look as if clipped?
		316
		317	Many fonts have difficulties with italic characters and hinting. For
		318	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		319	Mono> completely fails in it's italic face. A workaround might be to
		320	enable freetype autohinting, i.e. like this:
		321
		322	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		323	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		324
		325	=head3 Can I speed up Xft rendering somehow?
		326
		327	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		328	it is simply slow. If you still want Xft fonts you might try to disable
		329	antialiasing (by appending C<:antialias=false>), which saves lots of
		330	memory and also speeds up rendering considerably.
		331
		332	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		333
		334	Rxvt-unicode will use whatever you specify as a font. If it needs to
		335	fall back to it's default font search list it will prefer X11 core
		336	fonts, because they are small and fast, and then use Xft fonts. It has
		337	antialiasing disabled for most of them, because the author thinks they
		338	look best that way.
		339
		340	If you want antialiasing, you have to specify the fonts manually.
		341
		342	=head3 What's with this bold/blink stuff?
		343
		344	If no bold colour is set via C<colorBD:>, bold will invert text using the
		345	standard foreground colour.
		346
		347	For the standard background colour, blinking will actually make the
		348	text blink when compiled with C<--enable-blinking>. with standard
		349	colours. Without C<--enable-blinking>, the blink attribute will be
		350	ignored.
		351
		352	On ANSI colours, bold/blink attributes are used to set high-intensity
		353	foreground/background colors.
		354
		355	color0-7 are the low-intensity colors.
		356
		357	color8-15 are the corresponding high-intensity colors.
		358
		359	=head3 I don't like the screen colors. How do I change them?
		360
		361	You can change the screen colors at run-time using F<~/.Xdefaults>
		362	resources (or as long-options).
		363
		364	Here are values that are supposed to resemble a VGA screen,
		365	including the murky brown that passes for low-intensity yellow:
		366
		367	URxvt.color0: #000000
		368	URxvt.color1: #A80000
		369	URxvt.color2: #00A800
		370	URxvt.color3: #A8A800
		371	URxvt.color4: #0000A8
		372	URxvt.color5: #A800A8
		373	URxvt.color6: #00A8A8
		374	URxvt.color7: #A8A8A8
		375
		376	URxvt.color8: #000054
		377	URxvt.color9: #FF0054
		378	URxvt.color10: #00FF54
		379	URxvt.color11: #FFFF54
		380	URxvt.color12: #0000FF
		381	URxvt.color13: #FF00FF
		382	URxvt.color14: #00FFFF
		383	URxvt.color15: #FFFFFF
		384
		385	And here is a more complete set of non-standard colors.
		386
		387	URxvt.cursorColor: #dc74d1
		388	URxvt.pointerColor: #dc74d1
		389	URxvt.background: #0e0e0e
		390	URxvt.foreground: #4ad5e1
		391	URxvt.color0: #000000
		392	URxvt.color8: #8b8f93
		393	URxvt.color1: #dc74d1
		394	URxvt.color9: #dc74d1
		395	URxvt.color2: #0eb8c7
		396	URxvt.color10: #0eb8c7
		397	URxvt.color3: #dfe37e
		398	URxvt.color11: #dfe37e
		399	URxvt.color5: #9e88f0
		400	URxvt.color13: #9e88f0
		401	URxvt.color6: #73f7ff
		402	URxvt.color14: #73f7ff
		403	URxvt.color7: #e1dddd
		404	URxvt.color15: #e1dddd
		405
		406	They have been described (not by me) as "pretty girly".
		407
		408	=head3 Why do some characters look so much different than others?
		409
		410	See next entry.
		411
		412	=head3 How does rxvt-unicode choose fonts?
		413
		414	Most fonts do not contain the full range of Unicode, which is
		415	fine. Chances are that the font you (or the admin/package maintainer of
		416	your system/os) have specified does not cover all the characters you want
		417	to display.
		418
		419	B<rxvt-unicode> makes a best-effort try at finding a replacement
		420	font. Often the result is fine, but sometimes the chosen font looks
		421	bad/ugly/wrong. Some fonts have totally strange characters that don't
		422	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		423	intelligence to detect that a specific glyph is wrong: it has to believe
		424	the font that the characters it claims to contain indeed look correct.
		425
		426	In that case, select a font of your taste and add it to the font list,
		427	e.g.:
		428
		429	@@URXVT_NAME@@ -fn basefont,font2,font3...
		430
		431	When rxvt-unicode sees a character, it will first look at the base
		432	font. If the base font does not contain the character, it will go to the
		433	next font, and so on. Specifying your own fonts will also speed up this
		434	search and use less resources within rxvt-unicode and the X-server.
		435
		436	The only limitation is that none of the fonts may be larger than the base
		437	font, as the base font defines the terminal character cell size, which
		438	must be the same due to the way terminals work.
		439
		440	=head3 Why do some chinese characters look so different than others?
		441
		442	This is because there is a difference between script and language --
		443	rxvt-unicode does not know which language the text that is output is,
		444	as it only knows the unicode character codes. If rxvt-unicode first
		445	sees a japanese/chinese character, it might choose a japanese font for
		446	display. Subsequent japanese characters will use that font. Now, many
		447	chinese characters aren't represented in japanese fonts, so when the first
		448	non-japanese character comes up, rxvt-unicode will look for a chinese font
		449	-- unfortunately at this point, it will still use the japanese font for
		450	chinese characters that are also in the japanese font.
		451
		452	The workaround is easy: just tag a chinese font at the end of your font
		453	list (see the previous question). The key is to view the font list as
		454	a preference list: If you expect more japanese, list a japanese font
		455	first. If you expect more chinese, put a chinese font first.
		456
		457	In the future it might be possible to switch language preferences at
		458	runtime (the internal data structure has no problem with using different
		459	fonts for the same character at the same time, but no interface for this
		460	has been designed yet).
		461
		462	Until then, you might get away with switching fonts at runtime (see L<Can
		463	I switch the fonts at runtime?> later in this document).
		464
		465	=head2 Keyboard, Mouse & User Interaction
		466
		467	=head3 The new selection selects pieces that are too big, how can I select single words?
		468
		469	If you want to select e.g. alphanumeric words, you can use the following
		470	setting:
		471
		472	URxvt.selection.pattern-0: ([[:word:]]+)
		473
		474	If you click more than twice, the selection will be extended
		475	more and more.
		476
		477	To get a selection that is very similar to the old code, try this pattern:
		478
		479	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		480
		481	Please also note that the I<LeftClick Shift-LeftClik> combination also
		482	selects words like the old code.
		483
		484	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		485
		486	You can disable the perl extension completely by setting the
		487	B<perl-ext-common> resource to the empty string, which also keeps
		488	rxvt-unicode from initialising perl, saving memory.
		489
		490	If you only want to disable specific features, you first have to
		491	identify which perl extension is responsible. For this, read the section
		492	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		493	example, to disable the B<selection-popup> and B<option-popup>, specify
		494	this B<perl-ext-common> resource:
		495
		496	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		497
		498	This will keep the default extensions, but disable the two popup
		499	extensions. Some extensions can also be configured, for example,
		500	scrollback search mode is triggered by B<M-s>. You can move it to any
		501	other combination either by setting the B<searchable-scrollback> resource:
		502
		503	URxvt.searchable-scrollback: CM-s
		504
		505	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		506
		507	See next entry.
		508
		509	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		510
		511	These are caused by the C<readline> perl extension. Under normal
		512	circumstances, it will move your cursor around when you click into the
		513	line that contains it. It tries hard not to do this at the wrong moment,
		514	but when running a program that doesn't parse cursor movements or in some
		515	cases during rlogin sessions, it fails to detect this properly.
		516
		517	You can permamently switch this feature off by disabling the C<readline>
		518	extension:
		519
153	URxvt.perl-ext-common: default,tabbed	520	URxvt.perl-ext-common: default,-readline
154		521
155	It will also work fine with tabbing functionality of many window managers	522	=head3 My numerical keypad acts weird and generates differing output?
156	or similar tabbing programs, and its embedding-features allow it to be
157	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
158	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
159	(murxvt) terminal as an example embedding application.
160		523
161	=item How do I know which rxvt-unicode version I'm using?	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.
162		530
163	The version number is displayed with the usage (-h). Also the escape	531	=head3 My Compose (Multi_key) key is no longer working.
164	sequence C<ESC [ 8 n> sets the window title to the version number. When
165	using the @@RXVT_NAME@@c client, the version displayed is that of the
166	daemon.
167		532
168	=item I am using Debian GNU/Linux and have a problem...	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.
169		539
170	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	540	In this case either do not specify a B<preeditStyle> or specify more than
171	patches that considerably change the behaviour of rxvt-unicode (but	541	one pre-edit style, such as B<OverTheSpot,Root,None>.
172	unfortunately this notice has been removed). Before reporting a bug to
173	the original rxvt-unicode author please download and install the genuine
174	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
175	the problem. If you cannot, chances are that the problems are specific to
176	Debian GNU/Linux, in which case it should be reported via the Debian Bug
177	Tracking System (use C<reportbug> to report the bug).
178		542
179	For other problems that also affect the Debian package, you can and	543	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
180	probably should use the Debian BTS, too, because, after all, it's also a
181	bug in the Debian version and it serves as a reminder for other users that
182	might encounter the same issue.
183		544
184	=item I am maintaining rxvt-unicode for distribution/OS XXX, any	545	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
185	recommendation?	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.
186		550
187	You should build one binary with the default options. F<configure>	551	=head3 Mouse cut/paste suddenly no longer works.
188	now enables most useful options, and the trend goes to making them
189	runtime-switchable, too, so there is usually no drawback to enbaling them,
190	except higher disk and possibly memory usage. The perl interpreter should
191	be enabled, as important functionality (menus, selection, likely more in
192	the future) depends on it.
193		552
194	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	553	Make sure that mouse reporting is actually turned off since killing
195	system-wide (except maybe with C<defaults>). This will result in useful	554	some editors prematurely may leave the mouse in mouse report mode. I've
196	behaviour. If your distribution aims at low memory, add an empty	555	heard that tcsh may use mouse reporting unless it otherwise specified. A
197	C<perl-ext-common> resource to the app-defaults file. This will keep the	556	quick check is to see if cut/paste works when the Alt or Shift keys are
198	perl interpreter disabled until the user enables it.	557	depressed.
199		558
200	If you can/want build more binaries, I recommend building a minimal	559	=head3 What's with the strange Backspace/Delete key behaviour?
201	one with C<--disable-everything> (very useful) and a maximal one with
202	C<--enable-everything> (less useful, it will be very big due to a lot of
203	encodings built-in that increase download times and are rarely used).
204		560
205	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	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<^?>.
206		565
207	It should be, starting with release 7.1. You are encouraged to properly	566	Historically, either value is correct, but rxvt-unicode adopts the debian
208	install urxvt with privileges necessary for your OS now.	567	policy of using C<^?> when unsure, because it's the one only only correct
		568	choice :).
209		569
210	When rxvt-unicode detects that it runs setuid or setgid, it will fork	570	Rxvt-unicode tries to inherit the current stty settings and uses the value
211	into a helper process for privileged operations (pty handling on some	571	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
212	systems, utmp/wtmp/lastlog handling on others) and drop privileges	572	started from a terminal (say, from a menu or by remote shell), then the
213	immediately. This is much safer than most other terminals that keep	573	system value of `erase', which corresponds to CERASE in <termios.h>, will
214	privileges while running (but is more relevant to urxvt, as it contains	574	be used (which may not be the same as your stty setting).
215	things as perl interpreters, which might be "helpful" to attackers).
216		575
217	This forking is done as the very first within main(), which is very early	576	For starting a new rxvt-unicode:
218	and reduces possible bugs to initialisation code run before main(), or
219	things like the dynamic loader of your system, which should result in very
220	little risk.
221		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
222	=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?
223		684
224	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
225	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).
226		687
227	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
…		…
243	resource to set it:	704	resource to set it:
244		705
245	URxvt.termName: rxvt	706	URxvt.termName: rxvt
246		707
247	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
248	the rxvt terminfo file with the rxvt-unicode one.	709	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
249		710
250	=item C<tic> outputs some error when compiling the terminfo entry.	711	=head3 C<tic> outputs some error when compiling the terminfo entry.
251		712
252	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
253	C<enacs=\E[0@> and try again.	714	C<enacs=\E[0@> and try again.
254		715
255	=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@@.
256		717
		718	See next entry.
		719
257	=item I need a termcap file entry.	720	=head3 I need a termcap file entry.
258		721
259	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
260	systems still compile some programs using the long-obsoleted termcap	723	systems still compile some programs using the long-obsoleted termcap
261	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
262	for C<rxvt-unicode>.	725	for C<rxvt-unicode>.
…		…
288	: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:\
289	: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:\
290	: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:\
291	:vs=\E[?25h:	754	:vs=\E[?25h:
292		755
293	=item Why does C<ls> no longer have coloured output?	756	=head3 Why does C<ls> no longer have coloured output?
294		757
295	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
296	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
297	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
298	with most other terminals supporting colour). Either add:	761	with most other terminals supporting colour). Either add:
…		…
303		766
304	alias ls='ls --color=auto'	767	alias ls='ls --color=auto'
305		768
306	to your C<.profile> or C<.bashrc>.	769	to your C<.profile> or C<.bashrc>.
307		770
308	=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?
309		772
		773	See next entry.
		774
310	=item Why doesn't vim/emacs etc. make use of italic?	775	=head3 Why doesn't vim/emacs etc. make use of italic?
311		776
		777	See next entry.
		778
312	=item Why are the secondary screen-related options not working properly?	779	=head3 Why are the secondary screen-related options not working properly?
313		780
314	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
315	distributions (most notably Debian GNU/Linux) break rxvt-unicode	782	distributions (most notably Debian GNU/Linux) break rxvt-unicode
316	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
317	features. Unfortunately, some of these (most notably, again, Debian	784	features. Unfortunately, some of these (most notably, again, Debian
318	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
319	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
320	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
321	how to do this).	788	how to do this).
322		789
323	=item My numerical keypad acts weird and generates differing output?
324		790
325	Some Debian GNUL/Linux users seem to have this problem, although no	791	=head2 Encoding / Locale / Input Method Issues
326	specific details were reported so far. It is possible that this is caused
327	by the wrong C<TERM> setting, although the details of wether and how
328	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
329	keymap. See the answer to the previous question, and please report if that
330	helped.
331		792
332	=item Rxvt-unicode does not seem to understand the selected encoding?	793	=head3 Rxvt-unicode does not seem to understand the selected encoding?
333		794
		795	See next entry.
		796
334	=item Unicode does not seem to work?	797	=head3 Unicode does not seem to work?
335		798
336	If you encounter strange problems like typing an accented character but	799	If you encounter strange problems like typing an accented character but
337	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
338	subtly garbled, then you should check your locale settings.	801	subtly garbled, then you should check your locale settings.
339		802
…		…
359		822
360	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
361	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
362	support locales :(	825	support locales :(
363		826
364	=item Why do some characters look so much different than others?	827	=head3 How does rxvt-unicode determine the encoding to use?
365		828
366	=item How does rxvt-unicode choose fonts?	829	See next entry.
367		830
368	Most fonts do not contain the full range of Unicode, which is	831	=head3 Is there an option to switch encodings?
369	fine. Chances are that the font you (or the admin/package maintainer of
370	your system/os) have specified does not cover all the characters you want
371	to display.
372		832
373	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
374	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
375	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.
376	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
377	intelligence to detect that a specific glyph is wrong: it has to believe
378	the font that the characters it claims to contain indeed look correct.
379		836
380	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
381	e.g.:	838	the encoding, doing I/O and (most important) communicating this to all
382		839	applications so everybody agrees on character properties such as width
383	@@RXVT_NAME@@ -fn basefont,font2,font3...	840	and code number. This mechanism is the I<locale>. Applications not using
384		841	that info will have problems (for example, C<xterm> gets the width of
385	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
386	font. If the base font does not contain the character, it will go to the
387	next font, and so on. Specifying your own fonts will also speed up this
388	search and use less resources within rxvt-unicode and the X-server.
389
390	The only limitation is that none of the fonts may be larger than the base
391	font, as the base font defines the terminal character cell size, which
392	must be the same due to the way terminals work.
393
394	=item Why do some chinese characters look so different than others?
395
396	This is because there is a difference between script and language --
397	rxvt-unicode does not know which language the text that is output is,
398	as it only knows the unicode character codes. If rxvt-unicode first
399	sees a japanese/chinese character, it might choose a japanese font for
400	display. Subsequent japanese characters will use that font. Now, many
401	chinese characters aren't represented in japanese fonts, so when the first
402	non-japanese character comes up, rxvt-unicode will look for a chinese font
403	-- unfortunately at this point, it will still use the japanese font for
404	chinese characters that are also in the japanese font.
405
406	The workaround is easy: just tag a chinese font at the end of your font
407	list (see the previous question). The key is to view the font list as
408	a preference list: If you expect more japanese, list a japanese font
409	first. If you expect more chinese, put a chinese font first.
410
411	In the future it might be possible to switch language preferences at
412	runtime (the internal data structure has no problem with using different
413	fonts for the same character at the same time, but no interface for this
414	has been designed yet).
415
416	Until then, you might get away with switching fonts at runtime (see L<Can
417	I switch the fonts at runtime?> later in this document).
418
419	=item Why does rxvt-unicode sometimes leave pixel droppings?
420
421	Most fonts were not designed for terminal use, which means that character
422	size varies a lot. A font that is otherwise fine for terminal use might
423	contain some characters that are simply too wide. Rxvt-unicode will avoid
424	these characters. For characters that are just "a bit" too wide a special
425	"careful" rendering mode is used that redraws adjacent characters.
426
427	All of this requires that fonts do not lie about character sizes,
428	however: Xft fonts often draw glyphs larger than their acclaimed bounding
429	box, and rxvt-unicode has no way of detecting this (the correct way is to
430	ask for the character bounding box, which unfortunately is wrong in these
431	cases).	843	locales).
432		844
433	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
434	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
435	the C<-lsp> option to give the font more height. If that doesn't work, you	847	interpretation of characters.
436	might be forced to use a different font.
437		848
438	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
439	box data is correct.	850	is there a standard on how locale specifiers will look like.
440		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
441	=item On Solaris 9, many line-drawing characters are too wide.	998	=head3 On Solaris 9, many line-drawing characters are too wide.
442		999
443	Seems to be a known bug, read	1000	Seems to be a known bug, read
444	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
445	following ugly workaround to get non-double-wide-characters working:	1002	following ugly workaround to get non-double-wide-characters working:
446		1003
447	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1004	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
448		1005
449	=item My Compose (Multi_key) key is no longer working.
450
451	The most common causes for this are that either your locale is not set
452	correctly, or you specified a B<preeditStyle> that is not supported by
453	your input method. For example, if you specified B<OverTheSpot> and
454	your input method (e.g. the default input method handling Compose keys)
455	does not support this (for instance because it is not visual), then
456	rxvt-unicode will continue without an input method.
457
458	In this case either do not specify a B<preeditStyle> or specify more than
459	one pre-edit style, such as B<OverTheSpot,Root,None>.
460
461	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
462
463	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
464	international keyboards) or simply use ISO 14755 support to your
465	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
466	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
467	character and so on.
468
469	=item How can I keep rxvt-unicode from using reverse video so much?
470
471	First of all, make sure you are running with the right terminal settings
472	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
473	make sure you have specified colours for italic and bold, as otherwise
474	rxvt-unicode might use reverse video to simulate the effect:
475
476	URxvt.colorBD: white
477	URxvt.colorIT: green
478
479	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
480
481	For some unexplainable reason, some rare programs assume a very weird
482	colour palette when confronted with a terminal with more than the standard
483	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
484	these programs not to assume non-ISO colours without very good reasons.
485
486	In the meantime, you can either edit your C<rxvt-unicode> terminfo
487	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
488	fix colours but keep you from using other rxvt-unicode features.
489
490	=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.
491		1007
492	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
493	in your compile environment, or an implementation that implements it,	1009	in your compile environment, or an implementation that implements it,
494	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
495	B<wchar_t> is represented as unicode.	1011	B<wchar_t> is represented as unicode.
…		…
517		1033
518	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
519	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
520	complete replacements for them :)	1036	complete replacements for them :)
521		1037
522	=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.
523		1039
524	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
525	problems with C<wcwidth> and a compile problem.	1041	problems with C<wcwidth> and a compile problem.
526		1042
527	=item How can I use rxvt-unicode under cygwin?	1043	=head3 How can I use rxvt-unicode under cygwin?
528		1044
529	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
530	the X11 libraries that come with cygwin. libW11 emulation is no	1046	the X11 libraries that come with cygwin. libW11 emulation is no
531	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
532	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
…		…
535		1051
536	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
537	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
538	to 8-bit encodings.	1054	to 8-bit encodings.
539		1055
540	=item How does rxvt-unicode determine the encoding to use?
541
542	=item Is there an option to switch encodings?
543
544	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
545	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
546	UTF-8 or any other encodings with respect to terminal I/O.
547
548	The reasons is that there exists a perfectly fine mechanism for selecting
549	the encoding, doing I/O and (most important) communicating this to all
550	applications so everybody agrees on character properties such as width
551	and code number. This mechanism is the I<locale>. Applications not using
552	that info will have problems (for example, C<xterm> gets the width of
553	characters wrong as it uses it's own, locale-independent table under all
554	locales).
555
556	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
557	programs doing the same (that is, most) will automatically agree in the
558	interpretation of characters.
559
560	Unfortunately, there is no system-independent way to select locales, nor
561	is there a standard on how locale specifiers will look like.
562
563	On most systems, the content of the C<LC_CTYPE> environment variable
564	contains an arbitrary string which corresponds to an already-installed
565	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
566	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
567	(i.e. C<de> or C<german>) are also common.
568
569	Rxvt-unicode ignores all other locale categories, and except for
570	the encoding, ignores country or language-specific settings,
571	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
572	rxvt-unicode.
573
574	If you want to use a specific encoding you have to make sure you start
575	rxvt-unicode with the correct C<LC_CTYPE> category.
576
577	=item Can I switch locales at runtime?
578
579	Yes, using an escape sequence. Try something like this, which sets
580	rxvt-unicode's idea of C<LC_CTYPE>.
581
582	printf '\e]701;%s\007' ja_JP.SJIS
583
584	See also the previous answer.
585
586	Sometimes this capability is rather handy when you want to work in
587	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
588	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
589	first switches to a locale supported by xjdic and back later:
590
591	printf '\e]701;%s\007' ja_JP.SJIS
592	xjdic -js
593	printf '\e]701;%s\007' de_DE.UTF-8
594
595	You can also use xterm's C<luit> program, which usually works fine, except
596	for some locales where character width differs between program- and
597	rxvt-unicode-locales.
598
599	=item Can I switch the fonts at runtime?
600
601	Yes, using an escape sequence. Try something like this, which has the same
602	effect as using the C<-fn> switch, and takes effect immediately:
603
604	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
605
606	This is useful if you e.g. work primarily with japanese (and prefer a
607	japanese font), but you have to switch to chinese temporarily, where
608	japanese fonts would only be in your way.
609
610	You can think of this as a kind of manual ISO-2022 switching.
611
612	=item Why do italic characters look as if clipped?
613
614	Many fonts have difficulties with italic characters and hinting. For
615	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
616	Mono> completely fails in it's italic face. A workaround might be to
617	enable freetype autohinting, i.e. like this:
618
619	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
620	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
621
622	=item My input method wants <some encoding> but I want UTF-8, what can I do?
623
624	You can specify separate locales for the input method and the rest of the
625	terminal, using the resource C<imlocale>:
626
627	URxvt.imlocale: ja_JP.EUC-JP
628
629	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
630	use your input method. Please note, however, that you will not be able to
631	input characters outside C<EUC-JP> in a normal way then, as your input
632	method limits you.
633
634	=item Rxvt-unicode crashes when the X Input Method changes or exits.
635
636	Unfortunately, this is unavoidable, as the XIM protocol is racy by
637	design. Applications can avoid some crashes at the expense of memory
638	leaks, and Input Methods can avoid some crashes by careful ordering at
639	exit time. B<kinput2> (and derived input methods) generally succeeds,
640	while B<SCIM> (or similar input methods) fails. In the end, however,
641	crashes cannot be completely avoided even if both sides cooperate.
642
643	So the only workaround is not to kill your Input Method Servers.
644
645	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
646
647	Rxvt-unicode tries to obey the rule of not charging you for something you
648	don't use. One thing you should try is to configure out all settings that
649	you don't need, for example, Xft support is a resource hog by design,
650	when used. Compiling it out ensures that no Xft font will be loaded
651	accidentally when rxvt-unicode tries to find a font for your characters.
652
653	Also, many people (me included) like large windows and even larger
654	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
655	6 bytes per screen cell. For a 160x?? window this amounts to almost a
656	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
657	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
658	rxvt-unicode then uses 8 bytes per screen cell.
659
660	=item Can I speed up Xft rendering somehow?
661
662	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
663	it is simply slow. If you still want Xft fonts you might try to disable
664	antialiasing (by appending C<:antialias=false>), which saves lots of
665	memory and also speeds up rendering considerably.
666
667	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
668
669	Rxvt-unicode will use whatever you specify as a font. If it needs to
670	fall back to it's default font search list it will prefer X11 core
671	fonts, because they are small and fast, and then use Xft fonts. It has
672	antialiasing disabled for most of them, because the author thinks they
673	look best that way.
674
675	If you want antialiasing, you have to specify the fonts manually.
676
677	=item Mouse cut/paste suddenly no longer works.
678
679	Make sure that mouse reporting is actually turned off since killing
680	some editors prematurely may leave the mouse in mouse report mode. I've
681	heard that tcsh may use mouse reporting unless it otherwise specified. A
682	quick check is to see if cut/paste works when the Alt or Shift keys are
683	depressed.
684
685	=item What's with this bold/blink stuff?
686
687	If no bold colour is set via C<colorBD:>, bold will invert text using the
688	standard foreground colour.
689
690	For the standard background colour, blinking will actually make the
691	text blink when compiled with C<--enable-blinking>. with standard
692	colours. Without C<--enable-blinking>, the blink attribute will be
693	ignored.
694
695	On ANSI colours, bold/blink attributes are used to set high-intensity
696	foreground/background colors.
697
698	color0-7 are the low-intensity colors.
699
700	color8-15 are the corresponding high-intensity colors.
701
702	=item I don't like the screen colors. How do I change them?
703
704	You can change the screen colors at run-time using F<~/.Xdefaults>
705	resources (or as long-options).
706
707	Here are values that are supposed to resemble a VGA screen,
708	including the murky brown that passes for low-intensity yellow:
709
710	URxvt.color0: #000000
711	URxvt.color1: #A80000
712	URxvt.color2: #00A800
713	URxvt.color3: #A8A800
714	URxvt.color4: #0000A8
715	URxvt.color5: #A800A8
716	URxvt.color6: #00A8A8
717	URxvt.color7: #A8A8A8
718
719	URxvt.color8: #000054
720	URxvt.color9: #FF0054
721	URxvt.color10: #00FF54
722	URxvt.color11: #FFFF54
723	URxvt.color12: #0000FF
724	URxvt.color13: #FF00FF
725	URxvt.color14: #00FFFF
726	URxvt.color15: #FFFFFF
727
728	And here is a more complete set of non-standard colors described (not by
729	me) as "pretty girly".
730
731	URxvt.cursorColor: #dc74d1
732	URxvt.pointerColor: #dc74d1
733	URxvt.background: #0e0e0e
734	URxvt.foreground: #4ad5e1
735	URxvt.color0: #000000
736	URxvt.color8: #8b8f93
737	URxvt.color1: #dc74d1
738	URxvt.color9: #dc74d1
739	URxvt.color2: #0eb8c7
740	URxvt.color10: #0eb8c7
741	URxvt.color3: #dfe37e
742	URxvt.color11: #dfe37e
743	URxvt.color5: #9e88f0
744	URxvt.color13: #9e88f0
745	URxvt.color6: #73f7ff
746	URxvt.color14: #73f7ff
747	URxvt.color7: #e1dddd
748	URxvt.color15: #e1dddd
749
750	=item How can I start @@RXVT_NAME@@d in a race-free way?
751
752	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
753	display, create the listening socket and then fork.
754
755	=item What's with the strange Backspace/Delete key behaviour?
756
757	Assuming that the physical Backspace key corresponds to the
758	BackSpace keysym (not likely for Linux ... see the following
759	question) there are two standard values that can be used for
760	Backspace: C<^H> and C<^?>.
761
762	Historically, either value is correct, but rxvt-unicode adopts the debian
763	policy of using C<^?> when unsure, because it's the one only only correct
764	choice :).
765
766	Rxvt-unicode tries to inherit the current stty settings and uses the value
767	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
768	started from a terminal (say, from a menu or by remote shell), then the
769	system value of `erase', which corresponds to CERASE in <termios.h>, will
770	be used (which may not be the same as your stty setting).
771
772	For starting a new rxvt-unicode:
773
774	# use Backspace = ^H
775	$ stty erase ^H
776	$ @@RXVT_NAME@@
777
778	# use Backspace = ^?
779	$ stty erase ^?
780	$ @@RXVT_NAME@@
781
782	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
783
784	For an existing rxvt-unicode:
785
786	# use Backspace = ^H
787	$ stty erase ^H
788	$ echo -n "^[[36h"
789
790	# use Backspace = ^?
791	$ stty erase ^?
792	$ echo -n "^[[36l"
793
794	This helps satisfy some of the Backspace discrepancies that occur, but
795	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
796	properly reflects that.
797
798	The Delete key is a another casualty of the ill-defined Backspace problem.
799	To avoid confusion between the Backspace and Delete keys, the Delete
800	key has been assigned an escape sequence to match the vt100 for Execute
801	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
802
803	Some other Backspace problems:
804
805	some editors use termcap/terminfo,
806	some editors (vim I'm told) expect Backspace = ^H,
807	GNU Emacs (and Emacs-like editors) use ^H for help.
808
809	Perhaps someday this will all be resolved in a consistent manner.
810
811	=item I don't like the key-bindings. How do I change them?
812
813	There are some compile-time selections available via configure. Unless
814	you have run "configure" with the C<--disable-resources> option you can
815	use the `keysym' resource to alter the keystrings associated with keysyms.
816
817	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
818
819	URxvt.keysym.Home: \033[1~
820	URxvt.keysym.End: \033[4~
821	URxvt.keysym.C-apostrophe: \033<C-'>
822	URxvt.keysym.C-slash: \033<C-/>
823	URxvt.keysym.C-semicolon: \033<C-;>
824	URxvt.keysym.C-grave: \033<C-`>
825	URxvt.keysym.C-comma: \033<C-,>
826	URxvt.keysym.C-period: \033<C-.>
827	URxvt.keysym.C-0x60: \033<C-`>
828	URxvt.keysym.C-Tab: \033<C-Tab>
829	URxvt.keysym.C-Return: \033<C-Return>
830	URxvt.keysym.S-Return: \033<S-Return>
831	URxvt.keysym.S-space: \033<S-Space>
832	URxvt.keysym.M-Up: \033<M-Up>
833	URxvt.keysym.M-Down: \033<M-Down>
834	URxvt.keysym.M-Left: \033<M-Left>
835	URxvt.keysym.M-Right: \033<M-Right>
836	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
837	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
838	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
839
840	See some more examples in the documentation for the B<keysym> resource.
841
842	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
843	How do I make use of them? For example, the Sun Keyboard type 4
844	has the following mappings that rxvt-unicode doesn't recognize.
845
846	KP_Insert == Insert
847	F22 == Print
848	F27 == Home
849	F29 == Prior
850	F33 == End
851	F35 == Next
852
853	Rather than have rxvt-unicode try to accommodate all the various possible
854	keyboard mappings, it is better to use `xmodmap' to remap the keys as
855	required for your particular machine.
856
857	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
858	I need this to decide about setting colors etc.
859
860	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
861	check and see if that is set. Note that several programs, JED, slrn,
862	Midnight Commander automatically check this variable to decide whether or
863	not to use color.
864
865	=item How do I set the correct, full IP address for the DISPLAY variable?
866
867	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
868	insecure mode then it is possible to use the following shell script
869	snippets to correctly set the display. If your version of rxvt-unicode
870	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
871	the COLORTERM variable can be used to distinguish rxvt-unicode from a
872	regular xterm.
873
874	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
875	snippets:
876
877	# Bourne/Korn/POSIX family of shells:
878	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
879	if [ ${TERM:-foo} = xterm ]; then
880	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
881	echo -n '^[Z'
882	read term_id
883	stty icanon echo
884	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
885	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
886	read DISPLAY # set it in our local shell
887	fi
888	fi
889
890	=item How do I compile the manual pages for myself?
891
892	You need to have a recent version of perl installed as F</usr/bin/perl>,
893	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
894	the doc subdirectory and enter C<make alldoc>.
895
896	=item My question isn't answered here, can I ask a human?
897
898	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
899	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
900	interested in learning about new and exciting problems (but not FAQs :).
901
902	=back
903
904	=head1 RXVT TECHNICAL REFERENCE	1056	=head1 RXVT-UNICODE TECHNICAL REFERENCE
905
906	=head1 DESCRIPTION
907		1057
908	The rest of this document describes various technical aspects of	1058	The rest of this document describes various technical aspects of
909	B<rxvt-unicode>. First the description of supported command sequences,	1059	B<rxvt-unicode>. First the description of supported command sequences,
910	followed by pixmap support and last by a description of all features	1060	followed by pixmap support and last by a description of all features
911	selectable at C<configure> time.	1061	selectable at C<configure> time.
912		1062
913	=head1 Definitions	1063	=head2 Definitions
914		1064
915	=over 4	1065	=over 4
916		1066
917	=item B<< C<c> >>	1067	=item B<< C<c> >>
918		1068
…		…
936		1086
937	A text parameter composed of printable characters.	1087	A text parameter composed of printable characters.
938		1088
939	=back	1089	=back
940		1090
941	=head1 Values	1091	=head2 Values
942		1092
943	=over 4	1093	=over 4
944		1094
945	=item B<< C<ENQ> >>	1095	=item B<< C<ENQ> >>
946		1096
…		…
989		1139
990	Space Character	1140	Space Character
991		1141
992	=back	1142	=back
993		1143
994	=head1 Escape Sequences	1144	=head2 Escape Sequences
995		1145
996	=over 4	1146	=over 4
997		1147
998	=item B<< C<ESC # 8> >>	1148	=item B<< C<ESC # 8> >>
999		1149
…		…
1097		1247
1098	=back	1248	=back
1099		1249
1100	X<CSI>	1250	X<CSI>
1101		1251
1102	=head1 CSI (Command Sequence Introducer) Sequences	1252	=head2 CSI (Command Sequence Introducer) Sequences
1103		1253
1104	=over 4	1254	=over 4
1105		1255
1106	=item B<< C<ESC [ Ps @> >>	1256	=item B<< C<ESC [ Ps @> >>
1107		1257
…		…
1377		1527
1378	=back	1528	=back
1379		1529
1380	X<PrivateModes>	1530	X<PrivateModes>
1381		1531
1382	=head1 DEC Private Modes	1532	=head2 DEC Private Modes
1383		1533
1384	=over 4	1534	=over 4
1385		1535
1386	=item B<< C<ESC [ ? Pm h> >>	1536	=item B<< C<ESC [ ? Pm h> >>
1387		1537
…		…
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
…		…
1699		1849
1700	=end table	1850	=end table
1701		1851
1702	=back	1852	=back
1703		1853
1704	X<XPM>
1705
1706	=head1 XPM	1854	=head1 XPM
1707		1855
1708	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
1709	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
1710	sequence of scaling/positioning commands separated by semi-colons. The	1858	sequence of scaling/positioning commands separated by semi-colons. The
…		…
1807	=begin table	1955	=begin table
1808		1956
1809	4 Shift	1957	4 Shift
1810	8 Meta	1958	8 Meta
1811	16 Control	1959	16 Control
1812	32 Double Click I<(Rxvt extension)>	1960	32 Double Click I<(rxvt extension)>
1813		1961
1814	=end table	1962	=end table
1815		1963
1816	Col = B<< C<< <x> - SPACE >> >>	1964	Col = B<< C<< <x> - SPACE >> >>
1817		1965
…		…
2090		2238
2091	MWM-hints	2239	MWM-hints
2092	EWMH-hints (pid, utf8 names) and protocols (ping)	2240	EWMH-hints (pid, utf8 names) and protocols (ping)
2093	seperate underline colour (-underlineColor)	2241	seperate underline colour (-underlineColor)
2094	settable border widths and borderless switch (-w, -b, -bl)	2242	settable border widths and borderless switch (-w, -b, -bl)
2095	visual selection (-depth)	2243	visual depth selection (-depth)
2096	settable extra linespacing /-lsp)	2244	settable extra linespacing /-lsp)
2097	iso-14755-2 and -3, and visual feedback	2245	iso-14755-2 and -3, and visual feedback
2098	backindex and forwardindex escape sequence
2099	window op and some xterm/OSC escape sequences
2100	tripleclickwords (-tcw)	2246	tripleclickwords (-tcw)
2101	settable insecure mode (-insecure)	2247	settable insecure mode (-insecure)
2102	keysym remapping support	2248	keysym remapping support
2103	cursor blinking and underline cursor (-cb, -uc)	2249	cursor blinking and underline cursor (-cb, -uc)
2104	XEmbed support (-embed)	2250	XEmbed support (-embed)
2105	user-pty (-pty-fd)	2251	user-pty (-pty-fd)
2106	hold on exit (-hold)	2252	hold on exit (-hold)
2107	skip builtin block graphics (-sbg)	2253	skip builtin block graphics (-sbg)
2108	sgr modes 90..97 and 100..107
2109		2254
2110	It also enabled some non-essential features otherwise disabled, such as:	2255	It also enabled some non-essential features otherwise disabled, such as:
2111		2256
2112	some round-trip time optimisations	2257	some round-trip time optimisations
2113	nearest color allocation on pseudocolor screens	2258	nearest color allocation on pseudocolor screens
		2259	UTF8_STRING supporr for selection
		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
2114		2268
2115	=item --enable-iso14755 (default: on)	2269	=item --enable-iso14755 (default: on)
2116		2270
2117	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2271	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2118	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
…		…
2139	Remove support for mouse selection style like that of xterm.	2293	Remove support for mouse selection style like that of xterm.
2140		2294
2141	=item --enable-dmalloc (default: off)	2295	=item --enable-dmalloc (default: off)
2142		2296
2143	Use Gray Watson's malloc - which is good for debugging See	2297	Use Gray Watson's malloc - which is good for debugging See
2144	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
2145	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
2146	DINCLUDE and DLIB to the right places.	2300	DINCLUDE and DLIB to the right places.
2147		2301
2148	You can only use either this option and the following (should	2302	You can only use either this option and the following (should
2149	you use either) .	2303	you use either) .

Diff Legend

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