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.96 by root, Tue Jan 31 00:25:16 2006 UTC vs.
Revision 1.115 by root, Tue Feb 21 01:01:33 2006 UTC

…		…
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 also available on the World Wide Web at	21	The newest version of this document is also available on the World Wide Web at
22	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>.
23		23
24	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
25		25
26	=over 4
27		26
28	=item The new selection selects pieces that are too big, how can I select	27	=head2 Meta, Features & Commandline Issues
29	single words?
30		28
31	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?
32	the following resource:
33		30
34	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 :).
35		34
36	If you click more than twice, the selection will be extended	35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
37	more and more.
38		36
39	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:
40		40
41	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)	41	@@URXVT_NAME@@ -pe tabbed
42		42
43	Please also note that the I<LeftClick Shift-LeftClik> combination also	43	URxvt.perl-ext-common: default,tabbed
44	selects words like the old code.
45		44
46	=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
47	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.
48		50
49	You can disable the perl extension completely by setting the	51	=head3 How do I know which rxvt-unicode version I'm using?
50	B<perl-ext-common> resource to the empty string, which also keeps
51	rxvt-unicode from initialising perl, saving memory.
52		52
53	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
54	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
55	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
56	example, to disable the B<selection-popup> and B<option-popup>, specify	56	daemon.
57	this B<perl-ext-common> resource:
58		57
59	URxvt.perl-ext-common: default,-selection-popup,-option-popup	58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
60		59
61	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
62	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
63	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,
64	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.
65		65
66	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.
67		72
68	=item Why doesn't rxvt-unicode read my resources?	73	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
69		74
70	Well, why, indeed? It does, in a way very similar to other X	75	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
71	applications. Most importantly, this means that if you or your OS loads	76	display, create the listening socket and then fork.
72	resources into the X display (the right way to do it), rxvt-unicode will
73	ignore any resource files in your home directory. It will only read
74	F<$HOME/.Xdefaults> when no resources are attached to the display.
75		77
76	If you have or use an F<$HOME/.Xresources> file, chances are that	78	=head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?
77	resources are loaded into your X-server. In this case, you have to
78	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
79		79
80	Also consider the form resources have to use:	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:
81		82
82	URxvt.resource: value	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
83		89
84	If you want to use another form (there are lots of different ways of	90	This tries to create a new terminal, and if fails with exit status 2,
85	specifying resources), make sure you understand wether and why it	91	meaning it couldn't connect to the daemon, it will start the daemon and
86	works. If unsure, use the form above.	92	re-run the command. Subsequent invocations of the script will re-use the
		93	existing daemon.
87		94
88	=item I can't get transparency working, what am I doing wrong?	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.
89		96
90	First of all, transparency isn't officially supported in rxvt-unicode, so	97	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
91	you are mostly on your own. Do not bug the author about it (but you may	98	so you can check and see if that is set. Note that several programs, JED,
92	bug everybody else). Also, if you can't get it working consider it a rite	99	slrn, Midnight Commander automatically check this variable to decide
93	of passage: ... and you failed.	100	whether or not to use color.
94		101
95	Here are four ways to get transparency. B<Do> read the manpage and option	102	=head3 How do I set the correct, full IP address for the DISPLAY variable?
96	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
97		103
98	1. Use inheritPixmap:	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.
99		110
100	Esetroot wallpaper.jpg	111	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
101	@@RXVT_NAME@@ -ip -tint red -sh 40	112	snippets:
102		113
103	That works. If you think it doesn't, you lack transparency and tinting	114	# Bourne/Korn/POSIX family of shells:
104	support, or you are unable to read.	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
105		126
106	2. Use a simple pixmap and emulate pseudo-transparency. This enables you	127	=head3 How do I compile the manual pages on my own?
107	to use effects other than tinting and shading: Just shade/tint/whatever
108	your picture with gimp:
109		128
110	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	129	You need to have a recent version of perl installed as F</usr/bin/perl>,
111	@@RXVT_NAME@@ -pixmap background.xpm -pe automove-background	130	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		131	the doc subdirectory and enter C<make alldoc>.
112		132
113	That works. If you think it doesn't, you lack XPM and Perl support, or you
114	are unable to read.
115
116	3. Use an ARGB visual:
117
118	@@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
119
120	This requires XFT support, and the support of your X-server. If that
121	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
122	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
123	bugfixes and workarounds for Xft and Xlib to make it work, but that
124	doesn't mean that your WM has the required kludges in place.
125
126	4. Use xcompmgr and let it do the job:
127
128	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
129	-set _NET_WM_WINDOW_OPACITY 0xc0000000
130
131	Then click on a window you want to make transparent. Replace C<0xc0000000>
132	by other values to change the degree of opacity. If it doesn't work and
133	your server crashes, you got to keep the pieces.
134
135	=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?
136		134
137	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
138	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
139	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
140	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
…		…
144		142
145	text data bss drs rss filename	143	text data bss drs rss filename
146	98398 1664 24 15695 1824 rxvt --disable-everything	144	98398 1664 24 15695 1824 rxvt --disable-everything
147	188985 9048 66616 18222 1788 urxvt --disable-everything	145	188985 9048 66616 18222 1788 urxvt --disable-everything
148		146
149	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
150	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
151	libc), the two diverge, but not unreasnobaly so.	149	libc), the two diverge, but not unreasnobaly so.
152		150
153	text data bss drs rss filename	151	text data bss drs rss filename
154	163431 2152 24 20123 2060 rxvt --enable-everything	152	163431 2152 24 20123 2060 rxvt --enable-everything
…		…
172	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	170	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
173	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
174	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
175	extremely well *g*.	173	extremely well *g*.
176		174
177	=item Why C++, isn't that unportable/bloated/uncool?	175	=head3 Why C++, isn't that unportable/bloated/uncool?
178		176
179	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
180	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
181	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
182	shorter: It simply wouldn't exist without C++.	180	shorter: It simply wouldn't exist without C++.
…		…
206	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	204	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
207		205
208	No large bloated libraries (of course, none were linked in statically),	206	No large bloated libraries (of course, none were linked in statically),
209	except maybe libX11 :)	207	except maybe libX11 :)
210		208
211	=item Does it support tabs, can I have a tabbed rxvt-unicode?
212		209
213	Beginning with version 7.3, there is a perl extension that implements a	210	=head2 Rendering, Font & Look and Feel Issues
214	simple tabbed terminal. It is installed by default, so any of these should
215	give you tabs:
216		211
217	@@RXVT_NAME@@ -pe tabbed	212	=head3 I can't get transparency working, what am I doing wrong?
218		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
219	URxvt.perl-ext-common: default,tabbed	520	URxvt.perl-ext-common: default,-readline
220		521
221	It will also work fine with tabbing functionality of many window managers	522	=head3 My numerical keypad acts weird and generates differing output?
222	or similar tabbing programs, and its embedding-features allow it to be
223	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
224	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
225	(murxvt) terminal as an example embedding application.
226		523
227	=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.
228		530
229	The version number is displayed with the usage (-h). Also the escape	531	=head3 My Compose (Multi_key) key is no longer working.
230	sequence C<ESC [ 8 n> sets the window title to the version number. When
231	using the @@RXVT_NAME@@c client, the version displayed is that of the
232	daemon.
233		532
234	=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.
235		539
236	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
237	patches that considerably change the behaviour of rxvt-unicode (but	541	one pre-edit style, such as B<OverTheSpot,Root,None>.
238	unfortunately this notice has been removed). Before reporting a bug to
239	the original rxvt-unicode author please download and install the genuine
240	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
241	the problem. If you cannot, chances are that the problems are specific to
242	Debian GNU/Linux, in which case it should be reported via the Debian Bug
243	Tracking System (use C<reportbug> to report the bug).
244		542
245	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
246	probably should use the Debian BTS, too, because, after all, it's also a
247	bug in the Debian version and it serves as a reminder for other users that
248	might encounter the same issue.
249		544
250	=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
251	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.
252		550
253	You should build one binary with the default options. F<configure>	551	=head3 Mouse cut/paste suddenly no longer works.
254	now enables most useful options, and the trend goes to making them
255	runtime-switchable, too, so there is usually no drawback to enbaling them,
256	except higher disk and possibly memory usage. The perl interpreter should
257	be enabled, as important functionality (menus, selection, likely more in
258	the future) depends on it.
259		552
260	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
261	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
262	behaviour. If your distribution aims at low memory, add an empty	555	heard that tcsh may use mouse reporting unless it otherwise specified. A
263	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
264	perl interpreter disabled until the user enables it.	557	depressed.
265		558
266	If you can/want build more binaries, I recommend building a minimal	559	=head3 What's with the strange Backspace/Delete key behaviour?
267	one with C<--disable-everything> (very useful) and a maximal one with
268	C<--enable-everything> (less useful, it will be very big due to a lot of
269	encodings built-in that increase download times and are rarely used).
270		560
271	=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<^?>.
272		565
273	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
274	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 :).
275		569
276	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
277	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
278	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
279	immediately. This is much safer than most other terminals that keep	573	system value of `erase', which corresponds to CERASE in <termios.h>, will
280	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).
281	things as perl interpreters, which might be "helpful" to attackers).
282		575
283	This forking is done as the very first within main(), which is very early	576	For starting a new rxvt-unicode:
284	and reduces possible bugs to initialisation code run before main(), or
285	things like the dynamic loader of your system, which should result in very
286	little risk.
287		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 Can I see a typical configuration?
		664
		665	The default configuration tries to be xterm-like, which I don't like that
		666	much, but it's least surprise to regular users.
		667
		668	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		669	time into customising your terminal. To get you started, here is the
		670	author's .Xdefaults entries, with comments on what they do. It's certainly
		671	not I<typical>, but what's typical...
		672
		673	URxvt.cutchars: "()*,<>[]{}|'
		674	URxvt.print-pipe: cat >/tmp/xxx
		675
		676	These are just for testing stuff.
		677
		678	URxvt.imLocale: ja_JP.UTF-8
		679	URxvt.preeditType: OnTheSpot,None
		680
		681	This tells rxvt-unicode to use a special locale when communicating with
		682	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		683	type, which requires the C<xim-onthespot> perl extension but rewards me
		684	with correct-looking fonts.
		685
		686	URxvt.perl-lib: /root/lib/urxvt
		687	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		688	URxvt.selection.pattern-0: ( at .*? line \\d+)
		689	URxvt.selection.pattern-1: ^(/[^:]+):\
		690	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		691	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		692
		693	This is my perl configuration. The first two set the perl library
		694	directory and also tells urxvt to use a large number of extensions. I
		695	develop for myself mostly, so I actually use most of the extensions I
		696	write.
		697
		698	The selection stuff mainly makes the selection perl-error-message aware
		699	and tells it to convert pelr error mssages into vi-commands to load the
		700	relevant file and go tot he error line number.
		701
		702	URxvt.scrollstyle: plain
		703	URxvt.secondaryScroll: true
		704
		705	As the documentation says: plain is the preferred scrollbar for the
		706	author. The C<secondaryScroll> confgiures urxvt to scroll in full-screen
		707	apps, like screen, so lines scorlled out of screen end up in urxvt's
		708	scrollback buffer.
		709
		710	URxvt.background: #000000
		711	URxvt.foreground: gray90
		712	URxvt.color7: gray90
		713	URxvt.colorBD: #ffffff
		714	URxvt.cursorColor: #e0e080
		715	URxvt.throughColor: #8080f0
		716	URxvt.highlightColor: #f0f0f0
		717
		718	Some colours. Not sure which ones are being used or even non-defaults, but
		719	these are in my .Xdefaults. Most notably, they set foreground/background
		720	to light gray/black, and also make sure that the colour 7 matches the
		721	default foreground colour.
		722
		723	URxvt.underlineColor: yellow
		724
		725	Another colour, makes underline lines look different. Sometimes hurts, but
		726	is mostly a nice effect.
		727
		728	URxvt.geometry: 154x36
		729	URxvt.loginShell: false
		730	URxvt.meta: ignore
		731	URxvt.utmpInhibit: true
		732
		733	Uh, well, should be mostly self-explanatory. By specifying some defaults
		734	manually, I can quickly switch them for testing.
		735
		736	URxvt.saveLines: 8192
		737
		738	A large scrollback buffer is essential. Really.
		739
		740	URxvt.mapAlert: true
		741
		742	The only case I use it is for my IRC window, which I like to keep
		743	iconified till people msg me (which beeps).
		744
		745	URxvt.visualBell: true
		746
		747	The audible bell is often annoying, especially when in a crowd.
		748
		749	URxvt.insecure: true
		750
		751	Please don't hack my mutt! Ooops...
		752
		753	URxvt.pastableTabs: false
		754
		755	I once thought this is a great idea.
		756
		757	urxvt.font: 9x15bold,\
		758	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		759	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		760	[codeset=JISX0208]xft:Kochi Gothic, \
		761	xft:Bitstream Vera Sans Mono:autohint=true, \
		762	xft:Code2000:antialias=false
		763	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		764	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		765	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		766
		767	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		768	overwhelmed. A special note: the C<9x15bold> mentioend above is actually
		769	the version from XFree-3.3, as XFree-4 replaced it by a totally different
		770	font (different glyphs for C<;> and many other harmless characters),
		771	while the second font is actually the C<9x15bold> from XFree4/XOrg. The
		772	bold version has less chars than the medium version, so I use it for rare
		773	characters, too. Whene ditign sources with vim, I use italic for comments
		774	and other stuff, which looks quite good with Bitstream Vera anti-aliased.
		775
		776	Terminus is a quite bad font (many very wrong glyphs), but for most of my
		777	purposes, it works, and gives a different look, as my normal (Non-bold)
		778	font is already bold, and I want to see a difference between bold and
		779	normal fonts.
		780
		781	Please note that I used the C<urxvt> instance name and not the C<URxvt>
		782	class name. Thats because I use different configs for different purposes,
		783	for example, my IRC window is started with C<-name IRC>, and uses these
		784	defaults:
		785
		786	IRC*title: IRC
		787	IRC*geometry: 87x12+535+542
		788	IRC*saveLines: 0
		789	IRC*mapAlert: true
		790	IRC*font: suxuseuro
		791	IRC*boldFont: suxuseuro
		792	IRC*colorBD: white
		793	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		794	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		795
		796	C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font
		797	sizes. C<suxuseuro> allows me to keep an eye (and actually read)
		798	stuff while keeping a very small window. If somebody pastes something
		799	complicated (e.g. japanese), I temporarily switch to a larger font.
		800
		801	The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor
		802	C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname>
		803	file for different hosts, for example, on ym main desktop, I use:
		804
		805	URxvt.keysym.C-M-q: command:\033[3;5;5t
		806	URxvt.keysym.C-M-y: command:\033[3;5;606t
		807	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		808	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		809	URxvt.keysym.C-M-p: perl:test
		810
		811	The first for keysym definitions allow me to quickly bring some windows
		812	in the layout I like most. Ion users might start laughing but will stop
		813	immediately when I tell them that I use my own Fvwm2 module for much the
		814	same effect as Ion provides, and I only very rarely use the above key
		815	combinations :->
		816
		817	=head3 Why doesn't rxvt-unicode read my resources?
		818
		819	Well, why, indeed? It does, in a way very similar to other X
		820	applications. Most importantly, this means that if you or your OS loads
		821	resources into the X display (the right way to do it), rxvt-unicode will
		822	ignore any resource files in your home directory. It will only read
		823	F<$HOME/.Xdefaults> when no resources are attached to the display.
		824
		825	If you have or use an F<$HOME/.Xresources> file, chances are that
		826	resources are loaded into your X-server. In this case, you have to
		827	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		828
		829	Also consider the form resources have to use:
		830
		831	URxvt.resource: value
		832
		833	If you want to use another form (there are lots of different ways of
		834	specifying resources), make sure you understand wether and why it
		835	works. If unsure, use the form above.
		836
288	=item When I log-in to another system it tells me about missing terminfo data?	837	=head3 When I log-in to another system it tells me about missing terminfo data?
289		838
290	The terminal description used by rxvt-unicode is not as widely available	839	The terminal description used by rxvt-unicode is not as widely available
291	as that for xterm, or even rxvt (for which the same problem often arises).	840	as that for xterm, or even rxvt (for which the same problem often arises).
292		841
293	The correct solution for this problem is to install the terminfo, this can	842	The correct solution for this problem is to install the terminfo, this can
…		…
309	resource to set it:	858	resource to set it:
310		859
311	URxvt.termName: rxvt	860	URxvt.termName: rxvt
312		861
313	If you don't plan to use B<rxvt> (quite common...) you could also replace	862	If you don't plan to use B<rxvt> (quite common...) you could also replace
314	the rxvt terminfo file with the rxvt-unicode one.	863	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
315		864
316	=item C<tic> outputs some error when compiling the terminfo entry.	865	=head3 C<tic> outputs some error when compiling the terminfo entry.
317		866
318	Most likely it's the empty definition for C<enacs=>. Just replace it by	867	Most likely it's the empty definition for C<enacs=>. Just replace it by
319	C<enacs=\E[0@> and try again.	868	C<enacs=\E[0@> and try again.
320		869
321	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	870	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
322		871
		872	See next entry.
		873
323	=item I need a termcap file entry.	874	=head3 I need a termcap file entry.
324		875
325	One reason you might want this is that some distributions or operating	876	One reason you might want this is that some distributions or operating
326	systems still compile some programs using the long-obsoleted termcap	877	systems still compile some programs using the long-obsoleted termcap
327	library (Fedora Core's bash is one example) and rely on a termcap entry	878	library (Fedora Core's bash is one example) and rely on a termcap entry
328	for C<rxvt-unicode>.	879	for C<rxvt-unicode>.
…		…
354	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	905	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
355	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	906	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
356	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	907	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
357	:vs=\E[?25h:	908	:vs=\E[?25h:
358		909
359	=item Why does C<ls> no longer have coloured output?	910	=head3 Why does C<ls> no longer have coloured output?
360		911
361	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	912	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
362	decide wether a terminal has colour, but uses it's own configuration	913	decide wether a terminal has colour, but uses it's own configuration
363	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	914	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
364	with most other terminals supporting colour). Either add:	915	with most other terminals supporting colour). Either add:
…		…
369		920
370	alias ls='ls --color=auto'	921	alias ls='ls --color=auto'
371		922
372	to your C<.profile> or C<.bashrc>.	923	to your C<.profile> or C<.bashrc>.
373		924
374	=item Why doesn't vim/emacs etc. use the 88 colour mode?	925	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
375		926
		927	See next entry.
		928
376	=item Why doesn't vim/emacs etc. make use of italic?	929	=head3 Why doesn't vim/emacs etc. make use of italic?
377		930
		931	See next entry.
		932
378	=item Why are the secondary screen-related options not working properly?	933	=head3 Why are the secondary screen-related options not working properly?
379		934
380	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	935	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
381	distributions (most notably Debian GNU/Linux) break rxvt-unicode	936	distributions (most notably Debian GNU/Linux) break rxvt-unicode
382	by setting C<TERM> to C<rxvt>, which doesn't have these extra	937	by setting C<TERM> to C<rxvt>, which doesn't have these extra
383	features. Unfortunately, some of these (most notably, again, Debian	938	features. Unfortunately, some of these (most notably, again, Debian
384	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	939	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
385	file, so you will need to install it on your own (See the question B<When	940	file, so you will need to install it on your own (See the question B<When
386	I log-in to another system it tells me about missing terminfo data?> on	941	I log-in to another system it tells me about missing terminfo data?> on
387	how to do this).	942	how to do this).
388		943
389	=item My numerical keypad acts weird and generates differing output?
390		944
391	Some Debian GNUL/Linux users seem to have this problem, although no	945	=head2 Encoding / Locale / Input Method Issues
392	specific details were reported so far. It is possible that this is caused
393	by the wrong C<TERM> setting, although the details of wether and how
394	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
395	keymap. See the answer to the previous question, and please report if that
396	helped.
397		946
398	=item Rxvt-unicode does not seem to understand the selected encoding?	947	=head3 Rxvt-unicode does not seem to understand the selected encoding?
399		948
		949	See next entry.
		950
400	=item Unicode does not seem to work?	951	=head3 Unicode does not seem to work?
401		952
402	If you encounter strange problems like typing an accented character but	953	If you encounter strange problems like typing an accented character but
403	getting two unrelated other characters or similar, or if program output is	954	getting two unrelated other characters or similar, or if program output is
404	subtly garbled, then you should check your locale settings.	955	subtly garbled, then you should check your locale settings.
405		956
…		…
425		976
426	If nothing works and you are sure that everything is set correctly then	977	If nothing works and you are sure that everything is set correctly then
427	you will need to remember a little known fact: Some programs just don't	978	you will need to remember a little known fact: Some programs just don't
428	support locales :(	979	support locales :(
429		980
430	=item Why do some characters look so much different than others?	981	=head3 How does rxvt-unicode determine the encoding to use?
431		982
432	=item How does rxvt-unicode choose fonts?	983	See next entry.
433		984
434	Most fonts do not contain the full range of Unicode, which is	985	=head3 Is there an option to switch encodings?
435	fine. Chances are that the font you (or the admin/package maintainer of
436	your system/os) have specified does not cover all the characters you want
437	to display.
438		986
439	B<rxvt-unicode> makes a best-effort try at finding a replacement	987	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
440	font. Often the result is fine, but sometimes the chosen font looks	988	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
441	bad/ugly/wrong. Some fonts have totally strange characters that don't	989	UTF-8 or any other encodings with respect to terminal I/O.
442	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
443	intelligence to detect that a specific glyph is wrong: it has to believe
444	the font that the characters it claims to contain indeed look correct.
445		990
446	In that case, select a font of your taste and add it to the font list,	991	The reasons is that there exists a perfectly fine mechanism for selecting
447	e.g.:	992	the encoding, doing I/O and (most important) communicating this to all
448		993	applications so everybody agrees on character properties such as width
449	@@RXVT_NAME@@ -fn basefont,font2,font3...	994	and code number. This mechanism is the I<locale>. Applications not using
450		995	that info will have problems (for example, C<xterm> gets the width of
451	When rxvt-unicode sees a character, it will first look at the base	996	characters wrong as it uses it's own, locale-independent table under all
452	font. If the base font does not contain the character, it will go to the
453	next font, and so on. Specifying your own fonts will also speed up this
454	search and use less resources within rxvt-unicode and the X-server.
455
456	The only limitation is that none of the fonts may be larger than the base
457	font, as the base font defines the terminal character cell size, which
458	must be the same due to the way terminals work.
459
460	=item Why do some chinese characters look so different than others?
461
462	This is because there is a difference between script and language --
463	rxvt-unicode does not know which language the text that is output is,
464	as it only knows the unicode character codes. If rxvt-unicode first
465	sees a japanese/chinese character, it might choose a japanese font for
466	display. Subsequent japanese characters will use that font. Now, many
467	chinese characters aren't represented in japanese fonts, so when the first
468	non-japanese character comes up, rxvt-unicode will look for a chinese font
469	-- unfortunately at this point, it will still use the japanese font for
470	chinese characters that are also in the japanese font.
471
472	The workaround is easy: just tag a chinese font at the end of your font
473	list (see the previous question). The key is to view the font list as
474	a preference list: If you expect more japanese, list a japanese font
475	first. If you expect more chinese, put a chinese font first.
476
477	In the future it might be possible to switch language preferences at
478	runtime (the internal data structure has no problem with using different
479	fonts for the same character at the same time, but no interface for this
480	has been designed yet).
481
482	Until then, you might get away with switching fonts at runtime (see L<Can
483	I switch the fonts at runtime?> later in this document).
484
485	=item Why does rxvt-unicode sometimes leave pixel droppings?
486
487	Most fonts were not designed for terminal use, which means that character
488	size varies a lot. A font that is otherwise fine for terminal use might
489	contain some characters that are simply too wide. Rxvt-unicode will avoid
490	these characters. For characters that are just "a bit" too wide a special
491	"careful" rendering mode is used that redraws adjacent characters.
492
493	All of this requires that fonts do not lie about character sizes,
494	however: Xft fonts often draw glyphs larger than their acclaimed bounding
495	box, and rxvt-unicode has no way of detecting this (the correct way is to
496	ask for the character bounding box, which unfortunately is wrong in these
497	cases).	997	locales).
498		998
499	It's not clear (to me at least), wether this is a bug in Xft, freetype,	999	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
500	or the respective font. If you encounter this problem you might try using	1000	programs doing the same (that is, most) will automatically agree in the
501	the C<-lsp> option to give the font more height. If that doesn't work, you	1001	interpretation of characters.
502	might be forced to use a different font.
503		1002
504	All of this is not a problem when using X11 core fonts, as their bounding	1003	Unfortunately, there is no system-independent way to select locales, nor
505	box data is correct.	1004	is there a standard on how locale specifiers will look like.
506		1005
		1006	On most systems, the content of the C<LC_CTYPE> environment variable
		1007	contains an arbitrary string which corresponds to an already-installed
		1008	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1009	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1010	(i.e. C<de> or C<german>) are also common.
		1011
		1012	Rxvt-unicode ignores all other locale categories, and except for
		1013	the encoding, ignores country or language-specific settings,
		1014	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		1015	rxvt-unicode.
		1016
		1017	If you want to use a specific encoding you have to make sure you start
		1018	rxvt-unicode with the correct C<LC_CTYPE> category.
		1019
		1020	=head3 Can I switch locales at runtime?
		1021
		1022	Yes, using an escape sequence. Try something like this, which sets
		1023	rxvt-unicode's idea of C<LC_CTYPE>.
		1024
		1025	printf '\e]701;%s\007' ja_JP.SJIS
		1026
		1027	See also the previous answer.
		1028
		1029	Sometimes this capability is rather handy when you want to work in
		1030	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		1031	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		1032	first switches to a locale supported by xjdic and back later:
		1033
		1034	printf '\e]701;%s\007' ja_JP.SJIS
		1035	xjdic -js
		1036	printf '\e]701;%s\007' de_DE.UTF-8
		1037
		1038	You can also use xterm's C<luit> program, which usually works fine, except
		1039	for some locales where character width differs between program- and
		1040	rxvt-unicode-locales.
		1041
		1042	=head3 I have problems getting my input method working.
		1043
		1044	Try a search engine, as this is slightly different for every input method server.
		1045
		1046	Here is a checklist:
		1047
		1048	=over 4
		1049
		1050	=item - Make sure your locale I<and> the imLocale are supported on your OS.
		1051
		1052	Try C<locale -a> or check the documentation for your OS.
		1053
		1054	=item - Make sure your locale or imLocale matches a locale supported by your XIM.
		1055
		1056	For example, B<kinput2> does not support UTF-8 locales, you should use
		1057	C<ja_JP.EUC-JP> or equivalent.
		1058
		1059	=item - Make sure your XIM server is actually running.
		1060
		1061	=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
		1062
		1063	When you want to use e.g. B<kinput2>, it must be set to
		1064	C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input
		1065	method servers are running with this command:
		1066
		1067	xprop -root XIM_SERVERS
		1068
		1069	=item
		1070
		1071	=back
		1072
		1073	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		1074
		1075	You can specify separate locales for the input method and the rest of the
		1076	terminal, using the resource C<imlocale>:
		1077
		1078	URxvt.imlocale: ja_JP.EUC-JP
		1079
		1080	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1081	use your input method. Please note, however, that, depending on your Xlib
		1082	version, you may not be able to input characters outside C<EUC-JP> in a
		1083	normal way then, as your input method limits you.
		1084
		1085	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		1086
		1087	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1088	design. Applications can avoid some crashes at the expense of memory
		1089	leaks, and Input Methods can avoid some crashes by careful ordering at
		1090	exit time. B<kinput2> (and derived input methods) generally succeeds,
		1091	while B<SCIM> (or similar input methods) fails. In the end, however,
		1092	crashes cannot be completely avoided even if both sides cooperate.
		1093
		1094	So the only workaround is not to kill your Input Method Servers.
		1095
		1096
		1097	=head2 Operating Systems / Package Maintaining
		1098
		1099	=head3 I am using Debian GNU/Linux and have a problem...
		1100
		1101	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1102	patches that considerably change the behaviour of rxvt-unicode (but
		1103	unfortunately this notice has been removed). Before reporting a bug to
		1104	the original rxvt-unicode author please download and install the genuine
		1105	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1106	the problem. If you cannot, chances are that the problems are specific to
		1107	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		1108	Tracking System (use C<reportbug> to report the bug).
		1109
		1110	For other problems that also affect the Debian package, you can and
		1111	probably should use the Debian BTS, too, because, after all, it's also a
		1112	bug in the Debian version and it serves as a reminder for other users that
		1113	might encounter the same issue.
		1114
		1115	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1116
		1117	You should build one binary with the default options. F<configure>
		1118	now enables most useful options, and the trend goes to making them
		1119	runtime-switchable, too, so there is usually no drawback to enbaling them,
		1120	except higher disk and possibly memory usage. The perl interpreter should
		1121	be enabled, as important functionality (menus, selection, likely more in
		1122	the future) depends on it.
		1123
		1124	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		1125	system-wide (except maybe with C<defaults>). This will result in useful
		1126	behaviour. If your distribution aims at low memory, add an empty
		1127	C<perl-ext-common> resource to the app-defaults file. This will keep the
		1128	perl interpreter disabled until the user enables it.
		1129
		1130	If you can/want build more binaries, I recommend building a minimal
		1131	one with C<--disable-everything> (very useful) and a maximal one with
		1132	C<--enable-everything> (less useful, it will be very big due to a lot of
		1133	encodings built-in that increase download times and are rarely used).
		1134
		1135	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1136
		1137	It should be, starting with release 7.1. You are encouraged to properly
		1138	install urxvt with privileges necessary for your OS now.
		1139
		1140	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1141	into a helper process for privileged operations (pty handling on some
		1142	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1143	immediately. This is much safer than most other terminals that keep
		1144	privileges while running (but is more relevant to urxvt, as it contains
		1145	things as perl interpreters, which might be "helpful" to attackers).
		1146
		1147	This forking is done as the very first within main(), which is very early
		1148	and reduces possible bugs to initialisation code run before main(), or
		1149	things like the dynamic loader of your system, which should result in very
		1150	little risk.
		1151
507	=item On Solaris 9, many line-drawing characters are too wide.	1152	=head3 On Solaris 9, many line-drawing characters are too wide.
508		1153
509	Seems to be a known bug, read	1154	Seems to be a known bug, read
510	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	1155	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
511	following ugly workaround to get non-double-wide-characters working:	1156	following ugly workaround to get non-double-wide-characters working:
512		1157
513	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	1158	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
514		1159
515	=item My Compose (Multi_key) key is no longer working.
516
517	The most common causes for this are that either your locale is not set
518	correctly, or you specified a B<preeditStyle> that is not supported by
519	your input method. For example, if you specified B<OverTheSpot> and
520	your input method (e.g. the default input method handling Compose keys)
521	does not support this (for instance because it is not visual), then
522	rxvt-unicode will continue without an input method.
523
524	In this case either do not specify a B<preeditStyle> or specify more than
525	one pre-edit style, such as B<OverTheSpot,Root,None>.
526
527	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
528
529	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
530	international keyboards) or simply use ISO 14755 support to your
531	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
532	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
533	character and so on.
534
535	=item How can I keep rxvt-unicode from using reverse video so much?
536
537	First of all, make sure you are running with the right terminal settings
538	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
539	make sure you have specified colours for italic and bold, as otherwise
540	rxvt-unicode might use reverse video to simulate the effect:
541
542	URxvt.colorBD: white
543	URxvt.colorIT: green
544
545	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
546
547	For some unexplainable reason, some rare programs assume a very weird
548	colour palette when confronted with a terminal with more than the standard
549	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
550	these programs not to assume non-ISO colours without very good reasons.
551
552	In the meantime, you can either edit your C<rxvt-unicode> terminfo
553	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
554	fix colours but keep you from using other rxvt-unicode features.
555
556	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	1160	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
557		1161
558	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	1162	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
559	in your compile environment, or an implementation that implements it,	1163	in your compile environment, or an implementation that implements it,
560	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	1164	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
561	B<wchar_t> is represented as unicode.	1165	B<wchar_t> is represented as unicode.
…		…
583		1187
584	The rxvt-unicode author insists that the right way to fix this is in the	1188	The rxvt-unicode author insists that the right way to fix this is in the
585	system libraries once and for all, instead of forcing every app to carry	1189	system libraries once and for all, instead of forcing every app to carry
586	complete replacements for them :)	1190	complete replacements for them :)
587		1191
588	=item I use Solaris 9 and it doesn't compile/work/etc.	1192	=head3 I use Solaris 9 and it doesn't compile/work/etc.
589		1193
590	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	1194	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
591	problems with C<wcwidth> and a compile problem.	1195	problems with C<wcwidth> and a compile problem.
592		1196
593	=item How can I use rxvt-unicode under cygwin?	1197	=head3 How can I use rxvt-unicode under cygwin?
594		1198
595	rxvt-unicode should compile and run out of the box on cygwin, using	1199	rxvt-unicode should compile and run out of the box on cygwin, using
596	the X11 libraries that come with cygwin. libW11 emulation is no	1200	the X11 libraries that come with cygwin. libW11 emulation is no
597	longer supported (and makes no sense, either, as it only supported a	1201	longer supported (and makes no sense, either, as it only supported a
598	single font). I recommend starting the X-server in C<-multiwindow> or	1202	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
601		1205
602	At the time of this writing, cygwin didn't seem to support any multi-byte	1206	At the time of this writing, cygwin didn't seem to support any multi-byte
603	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1207	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
604	to 8-bit encodings.	1208	to 8-bit encodings.
605		1209
606	=item How does rxvt-unicode determine the encoding to use?
607
608	=item Is there an option to switch encodings?
609
610	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
611	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
612	UTF-8 or any other encodings with respect to terminal I/O.
613
614	The reasons is that there exists a perfectly fine mechanism for selecting
615	the encoding, doing I/O and (most important) communicating this to all
616	applications so everybody agrees on character properties such as width
617	and code number. This mechanism is the I<locale>. Applications not using
618	that info will have problems (for example, C<xterm> gets the width of
619	characters wrong as it uses it's own, locale-independent table under all
620	locales).
621
622	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
623	programs doing the same (that is, most) will automatically agree in the
624	interpretation of characters.
625
626	Unfortunately, there is no system-independent way to select locales, nor
627	is there a standard on how locale specifiers will look like.
628
629	On most systems, the content of the C<LC_CTYPE> environment variable
630	contains an arbitrary string which corresponds to an already-installed
631	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
632	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
633	(i.e. C<de> or C<german>) are also common.
634
635	Rxvt-unicode ignores all other locale categories, and except for
636	the encoding, ignores country or language-specific settings,
637	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
638	rxvt-unicode.
639
640	If you want to use a specific encoding you have to make sure you start
641	rxvt-unicode with the correct C<LC_CTYPE> category.
642
643	=item Can I switch locales at runtime?
644
645	Yes, using an escape sequence. Try something like this, which sets
646	rxvt-unicode's idea of C<LC_CTYPE>.
647
648	printf '\e]701;%s\007' ja_JP.SJIS
649
650	See also the previous answer.
651
652	Sometimes this capability is rather handy when you want to work in
653	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
654	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
655	first switches to a locale supported by xjdic and back later:
656
657	printf '\e]701;%s\007' ja_JP.SJIS
658	xjdic -js
659	printf '\e]701;%s\007' de_DE.UTF-8
660
661	You can also use xterm's C<luit> program, which usually works fine, except
662	for some locales where character width differs between program- and
663	rxvt-unicode-locales.
664
665	=item Can I switch the fonts at runtime?
666
667	Yes, using an escape sequence. Try something like this, which has the same
668	effect as using the C<-fn> switch, and takes effect immediately:
669
670	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
671
672	This is useful if you e.g. work primarily with japanese (and prefer a
673	japanese font), but you have to switch to chinese temporarily, where
674	japanese fonts would only be in your way.
675
676	You can think of this as a kind of manual ISO-2022 switching.
677
678	=item Why do italic characters look as if clipped?
679
680	Many fonts have difficulties with italic characters and hinting. For
681	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
682	Mono> completely fails in it's italic face. A workaround might be to
683	enable freetype autohinting, i.e. like this:
684
685	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
686	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
687
688	=item My input method wants <some encoding> but I want UTF-8, what can I do?
689
690	You can specify separate locales for the input method and the rest of the
691	terminal, using the resource C<imlocale>:
692
693	URxvt.imlocale: ja_JP.EUC-JP
694
695	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
696	use your input method. Please note, however, that you will not be able to
697	input characters outside C<EUC-JP> in a normal way then, as your input
698	method limits you.
699
700	=item Rxvt-unicode crashes when the X Input Method changes or exits.
701
702	Unfortunately, this is unavoidable, as the XIM protocol is racy by
703	design. Applications can avoid some crashes at the expense of memory
704	leaks, and Input Methods can avoid some crashes by careful ordering at
705	exit time. B<kinput2> (and derived input methods) generally succeeds,
706	while B<SCIM> (or similar input methods) fails. In the end, however,
707	crashes cannot be completely avoided even if both sides cooperate.
708
709	So the only workaround is not to kill your Input Method Servers.
710
711	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
712
713	Rxvt-unicode tries to obey the rule of not charging you for something you
714	don't use. One thing you should try is to configure out all settings that
715	you don't need, for example, Xft support is a resource hog by design,
716	when used. Compiling it out ensures that no Xft font will be loaded
717	accidentally when rxvt-unicode tries to find a font for your characters.
718
719	Also, many people (me included) like large windows and even larger
720	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
721	6 bytes per screen cell. For a 160x?? window this amounts to almost a
722	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
723	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
724	rxvt-unicode then uses 8 bytes per screen cell.
725
726	=item Can I speed up Xft rendering somehow?
727
728	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
729	it is simply slow. If you still want Xft fonts you might try to disable
730	antialiasing (by appending C<:antialias=false>), which saves lots of
731	memory and also speeds up rendering considerably.
732
733	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
734
735	Rxvt-unicode will use whatever you specify as a font. If it needs to
736	fall back to it's default font search list it will prefer X11 core
737	fonts, because they are small and fast, and then use Xft fonts. It has
738	antialiasing disabled for most of them, because the author thinks they
739	look best that way.
740
741	If you want antialiasing, you have to specify the fonts manually.
742
743	=item Mouse cut/paste suddenly no longer works.
744
745	Make sure that mouse reporting is actually turned off since killing
746	some editors prematurely may leave the mouse in mouse report mode. I've
747	heard that tcsh may use mouse reporting unless it otherwise specified. A
748	quick check is to see if cut/paste works when the Alt or Shift keys are
749	depressed.
750
751	=item What's with this bold/blink stuff?
752
753	If no bold colour is set via C<colorBD:>, bold will invert text using the
754	standard foreground colour.
755
756	For the standard background colour, blinking will actually make the
757	text blink when compiled with C<--enable-blinking>. with standard
758	colours. Without C<--enable-blinking>, the blink attribute will be
759	ignored.
760
761	On ANSI colours, bold/blink attributes are used to set high-intensity
762	foreground/background colors.
763
764	color0-7 are the low-intensity colors.
765
766	color8-15 are the corresponding high-intensity colors.
767
768	=item I don't like the screen colors. How do I change them?
769
770	You can change the screen colors at run-time using F<~/.Xdefaults>
771	resources (or as long-options).
772
773	Here are values that are supposed to resemble a VGA screen,
774	including the murky brown that passes for low-intensity yellow:
775
776	URxvt.color0: #000000
777	URxvt.color1: #A80000
778	URxvt.color2: #00A800
779	URxvt.color3: #A8A800
780	URxvt.color4: #0000A8
781	URxvt.color5: #A800A8
782	URxvt.color6: #00A8A8
783	URxvt.color7: #A8A8A8
784
785	URxvt.color8: #000054
786	URxvt.color9: #FF0054
787	URxvt.color10: #00FF54
788	URxvt.color11: #FFFF54
789	URxvt.color12: #0000FF
790	URxvt.color13: #FF00FF
791	URxvt.color14: #00FFFF
792	URxvt.color15: #FFFFFF
793
794	And here is a more complete set of non-standard colors described (not by
795	me) as "pretty girly".
796
797	URxvt.cursorColor: #dc74d1
798	URxvt.pointerColor: #dc74d1
799	URxvt.background: #0e0e0e
800	URxvt.foreground: #4ad5e1
801	URxvt.color0: #000000
802	URxvt.color8: #8b8f93
803	URxvt.color1: #dc74d1
804	URxvt.color9: #dc74d1
805	URxvt.color2: #0eb8c7
806	URxvt.color10: #0eb8c7
807	URxvt.color3: #dfe37e
808	URxvt.color11: #dfe37e
809	URxvt.color5: #9e88f0
810	URxvt.color13: #9e88f0
811	URxvt.color6: #73f7ff
812	URxvt.color14: #73f7ff
813	URxvt.color7: #e1dddd
814	URxvt.color15: #e1dddd
815
816	=item How can I start @@RXVT_NAME@@d in a race-free way?
817
818	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
819	display, create the listening socket and then fork.
820
821	=item What's with the strange Backspace/Delete key behaviour?
822
823	Assuming that the physical Backspace key corresponds to the
824	BackSpace keysym (not likely for Linux ... see the following
825	question) there are two standard values that can be used for
826	Backspace: C<^H> and C<^?>.
827
828	Historically, either value is correct, but rxvt-unicode adopts the debian
829	policy of using C<^?> when unsure, because it's the one only only correct
830	choice :).
831
832	Rxvt-unicode tries to inherit the current stty settings and uses the value
833	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
834	started from a terminal (say, from a menu or by remote shell), then the
835	system value of `erase', which corresponds to CERASE in <termios.h>, will
836	be used (which may not be the same as your stty setting).
837
838	For starting a new rxvt-unicode:
839
840	# use Backspace = ^H
841	$ stty erase ^H
842	$ @@RXVT_NAME@@
843
844	# use Backspace = ^?
845	$ stty erase ^?
846	$ @@RXVT_NAME@@
847
848	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
849
850	For an existing rxvt-unicode:
851
852	# use Backspace = ^H
853	$ stty erase ^H
854	$ echo -n "^[[36h"
855
856	# use Backspace = ^?
857	$ stty erase ^?
858	$ echo -n "^[[36l"
859
860	This helps satisfy some of the Backspace discrepancies that occur, but
861	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
862	properly reflects that.
863
864	The Delete key is a another casualty of the ill-defined Backspace problem.
865	To avoid confusion between the Backspace and Delete keys, the Delete
866	key has been assigned an escape sequence to match the vt100 for Execute
867	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
868
869	Some other Backspace problems:
870
871	some editors use termcap/terminfo,
872	some editors (vim I'm told) expect Backspace = ^H,
873	GNU Emacs (and Emacs-like editors) use ^H for help.
874
875	Perhaps someday this will all be resolved in a consistent manner.
876
877	=item I don't like the key-bindings. How do I change them?
878
879	There are some compile-time selections available via configure. Unless
880	you have run "configure" with the C<--disable-resources> option you can
881	use the `keysym' resource to alter the keystrings associated with keysyms.
882
883	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
884
885	URxvt.keysym.Home: \033[1~
886	URxvt.keysym.End: \033[4~
887	URxvt.keysym.C-apostrophe: \033<C-'>
888	URxvt.keysym.C-slash: \033<C-/>
889	URxvt.keysym.C-semicolon: \033<C-;>
890	URxvt.keysym.C-grave: \033<C-`>
891	URxvt.keysym.C-comma: \033<C-,>
892	URxvt.keysym.C-period: \033<C-.>
893	URxvt.keysym.C-0x60: \033<C-`>
894	URxvt.keysym.C-Tab: \033<C-Tab>
895	URxvt.keysym.C-Return: \033<C-Return>
896	URxvt.keysym.S-Return: \033<S-Return>
897	URxvt.keysym.S-space: \033<S-Space>
898	URxvt.keysym.M-Up: \033<M-Up>
899	URxvt.keysym.M-Down: \033<M-Down>
900	URxvt.keysym.M-Left: \033<M-Left>
901	URxvt.keysym.M-Right: \033<M-Right>
902	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
903	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
904	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
905
906	See some more examples in the documentation for the B<keysym> resource.
907
908	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
909	How do I make use of them? For example, the Sun Keyboard type 4
910	has the following mappings that rxvt-unicode doesn't recognize.
911
912	KP_Insert == Insert
913	F22 == Print
914	F27 == Home
915	F29 == Prior
916	F33 == End
917	F35 == Next
918
919	Rather than have rxvt-unicode try to accommodate all the various possible
920	keyboard mappings, it is better to use `xmodmap' to remap the keys as
921	required for your particular machine.
922
923	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
924	I need this to decide about setting colors etc.
925
926	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
927	check and see if that is set. Note that several programs, JED, slrn,
928	Midnight Commander automatically check this variable to decide whether or
929	not to use color.
930
931	=item How do I set the correct, full IP address for the DISPLAY variable?
932
933	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
934	insecure mode then it is possible to use the following shell script
935	snippets to correctly set the display. If your version of rxvt-unicode
936	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
937	the COLORTERM variable can be used to distinguish rxvt-unicode from a
938	regular xterm.
939
940	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
941	snippets:
942
943	# Bourne/Korn/POSIX family of shells:
944	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
945	if [ ${TERM:-foo} = xterm ]; then
946	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
947	echo -n '^[Z'
948	read term_id
949	stty icanon echo
950	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
951	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
952	read DISPLAY # set it in our local shell
953	fi
954	fi
955
956	=item How do I compile the manual pages for myself?
957
958	You need to have a recent version of perl installed as F</usr/bin/perl>,
959	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
960	the doc subdirectory and enter C<make alldoc>.
961
962	=item My question isn't answered here, can I ask a human?
963
964	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
965	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
966	interested in learning about new and exciting problems (but not FAQs :).
967
968	=back
969
970	=head1 RXVT TECHNICAL REFERENCE	1210	=head1 RXVT-UNICODE TECHNICAL REFERENCE
971
972	=head1 DESCRIPTION
973		1211
974	The rest of this document describes various technical aspects of	1212	The rest of this document describes various technical aspects of
975	B<rxvt-unicode>. First the description of supported command sequences,	1213	B<rxvt-unicode>. First the description of supported command sequences,
976	followed by pixmap support and last by a description of all features	1214	followed by pixmap support and last by a description of all features
977	selectable at C<configure> time.	1215	selectable at C<configure> time.
978		1216
979	=head1 Definitions	1217	=head2 Definitions
980		1218
981	=over 4	1219	=over 4
982		1220
983	=item B<< C<c> >>	1221	=item B<< C<c> >>
984		1222
…		…
1002		1240
1003	A text parameter composed of printable characters.	1241	A text parameter composed of printable characters.
1004		1242
1005	=back	1243	=back
1006		1244
1007	=head1 Values	1245	=head2 Values
1008		1246
1009	=over 4	1247	=over 4
1010		1248
1011	=item B<< C<ENQ> >>	1249	=item B<< C<ENQ> >>
1012		1250
…		…
1055		1293
1056	Space Character	1294	Space Character
1057		1295
1058	=back	1296	=back
1059		1297
1060	=head1 Escape Sequences	1298	=head2 Escape Sequences
1061		1299
1062	=over 4	1300	=over 4
1063		1301
1064	=item B<< C<ESC # 8> >>	1302	=item B<< C<ESC # 8> >>
1065		1303
…		…
1163		1401
1164	=back	1402	=back
1165		1403
1166	X<CSI>	1404	X<CSI>
1167		1405
1168	=head1 CSI (Command Sequence Introducer) Sequences	1406	=head2 CSI (Command Sequence Introducer) Sequences
1169		1407
1170	=over 4	1408	=over 4
1171		1409
1172	=item B<< C<ESC [ Ps @> >>	1410	=item B<< C<ESC [ Ps @> >>
1173		1411
…		…
1443		1681
1444	=back	1682	=back
1445		1683
1446	X<PrivateModes>	1684	X<PrivateModes>
1447		1685
1448	=head1 DEC Private Modes	1686	=head2 DEC Private Modes
1449		1687
1450	=over 4	1688	=over 4
1451		1689
1452	=item B<< C<ESC [ ? Pm h> >>	1690	=item B<< C<ESC [ ? Pm h> >>
1453		1691
…		…
1717		1955
1718	=back	1956	=back
1719		1957
1720	X<XTerm>	1958	X<XTerm>
1721		1959
1722	=head1 XTerm Operating System Commands	1960	=head2 XTerm Operating System Commands
1723		1961
1724	=over 4	1962	=over 4
1725		1963
1726	=item B<< C<ESC ] Ps;Pt ST> >>	1964	=item B<< C<ESC ] Ps;Pt ST> >>
1727		1965
…		…
1765		2003
1766	=end table	2004	=end table
1767		2005
1768	=back	2006	=back
1769		2007
1770	X<XPM>
1771
1772	=head1 XPM	2008	=head1 XPM
1773		2009
1774	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	2010	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1775	of B<< C<Pt> >> can be the name of the background pixmap followed by a	2011	of B<< C<Pt> >> can be the name of the background pixmap followed by a
1776	sequence of scaling/positioning commands separated by semi-colons. The	2012	sequence of scaling/positioning commands separated by semi-colons. The
…		…
1873	=begin table	2109	=begin table
1874		2110
1875	4 Shift	2111	4 Shift
1876	8 Meta	2112	8 Meta
1877	16 Control	2113	16 Control
1878	32 Double Click I<(Rxvt extension)>	2114	32 Double Click I<(rxvt extension)>
1879		2115
1880	=end table	2116	=end table
1881		2117
1882	Col = B<< C<< <x> - SPACE >> >>	2118	Col = B<< C<< <x> - SPACE >> >>
1883		2119
…		…
2211	Remove support for mouse selection style like that of xterm.	2447	Remove support for mouse selection style like that of xterm.
2212		2448
2213	=item --enable-dmalloc (default: off)	2449	=item --enable-dmalloc (default: off)
2214		2450
2215	Use Gray Watson's malloc - which is good for debugging See	2451	Use Gray Watson's malloc - which is good for debugging See
2216	http://www.letters.com/dmalloc/ for details If you use either this or the	2452	L<http://www.letters.com/dmalloc/> for details If you use either this or the
2217	next option, you may need to edit src/Makefile after compiling to point	2453	next option, you may need to edit src/Makefile after compiling to point
2218	DINCLUDE and DLIB to the right places.	2454	DINCLUDE and DLIB to the right places.
2219		2455
2220	You can only use either this option and the following (should	2456	You can only use either this option and the following (should
2221	you use either) .	2457	you use either) .

Diff Legend

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