ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/rxvt-unicode/README.FAQ

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.38 by root, Tue Jan 31 01:42:21 2006 UTC vs.
Revision 1.47 by root, Sat Jun 2 05:07:11 2007 UTC

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

Diff Legend

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