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.50 by root, Sat Oct 27 12:09:02 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 pod2xhtml (from Pod::Xhtml).
		96	Then go to the doc 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, please address all transparency related issues to Sasha
196	should give you tabs:	175	Vasko at sasha@aftercode.net and do not bug the author about it. Also,
		176	if you can't get it working consider it a rite of passage: ... and you
		177	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.jpg
		195	urxvt -pixmap background.jpg -pe automove-background
		196
		197	That works. If you think it doesn't, you lack AfterImage and Perl
		198	support, or 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	How can I make mplayer display video correctly?
		415	We are working on it, in the meantime, as a workaround, use something
		416	like:
		417
		418	urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		419
		420	Keyboard, Mouse & User Interaction
		421	The new selection selects pieces that are too big, how can I select single words?
		422	If you want to select e.g. alphanumeric words, you can use the following
		423	setting:
		424
		425	URxvt.selection.pattern-0: ([[:word:]]+)
		426
		427	If you click more than twice, the selection will be extended more and
		428	more.
		429
		430	To get a selection that is very similar to the old code, try this
		431	pattern:
		432
		433	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		434
		435	Please also note that the *LeftClick Shift-LeftClik* combination also
		436	selects words like the old code.
		437
		438	I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		439	You can disable the perl extension completely by setting the
		440	perl-ext-common resource to the empty string, which also keeps
		441	rxvt-unicode from initialising perl, saving memory.
		442
		443	If you only want to disable specific features, you first have to
		444	identify which perl extension is responsible. For this, read the section
		445	PREPACKAGED EXTENSIONS in the urxvtperl(3) manpage. For example, to
		446	disable the selection-popup and option-popup, specify this
		447	perl-ext-common resource:
		448
		449	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		450
		451	This will keep the default extensions, but disable the two popup
		452	extensions. Some extensions can also be configured, for example,
		453	scrollback search mode is triggered by M-s. You can move it to any other
		454	combination either by setting the searchable-scrollback resource:
		455
		456	URxvt.searchable-scrollback: CM-s
		457
		458	The cursor moves when selecting text in the current input line, how do I switch this off?
		459	See next entry.
		460
		461	During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		462	These are caused by the "readline" perl extension. Under normal
		463	circumstances, it will move your cursor around when you click into the
		464	line that contains it. It tries hard not to do this at the wrong moment,
		465	but when running a program that doesn't parse cursor movements or in
		466	some cases during rlogin sessions, it fails to detect this properly.
		467
		468	You can permanently switch this feature off by disabling the "readline"
		469	extension:
		470
200	URxvt.perl-ext-common: default,tabbed	471	URxvt.perl-ext-common: default,-readline
201		472
202	It will also work fine with tabbing functionality of many window	473	My numerical keypad acts weird and generates differing output?
203	managers or similar tabbing programs, and its embedding-features allow	474	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	475	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	476	caused by the wrong "TERM" setting, although the details of whether and
206	(murxvt) terminal as an example embedding application.	477	how this can happen are unknown, as "TERM=rxvt" should offer a
		478	compatible keymap. See the answer to the previous question, and please
		479	report if that helped.
207		480
208	How do I know which rxvt-unicode version I'm using?	481	My Compose (Multi_key) key is no longer working.
209	The version number is displayed with the usage (-h). Also the escape	482	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	483	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.	484	input method. For example, if you specified OverTheSpot and your input
		485	method (e.g. the default input method handling Compose keys) does not
		486	support this (for instance because it is not visual), then rxvt-unicode
		487	will continue without an input method.
212		488
213	I am using Debian GNU/Linux and have a problem...	489	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	490	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		491
223	For other problems that also affect the Debian package, you can and	492	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	493	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	494	international keyboards) or simply use ISO 14755 support to your
226	that might encounter the same issue.	495	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for
		496	other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
		497	escape character and so on.
227		498
228	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?	499	Mouse cut/paste suddenly no longer works.
229	You should build one binary with the default options. configure now	500	Make sure that mouse reporting is actually turned off since killing some
230	enables most useful options, and the trend goes to making them	501	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	502	that tcsh may use mouse reporting unless it otherwise specified. A quick
232	them, except higher disk and possibly memory usage. The perl interpreter	503	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	504	depressed.
234	more in the future) depends on it.
235		505
236	You should not overwrite the "perl-ext-common" snd "perl-ext" resources	506	What's with the strange Backspace/Delete key behaviour?
237	system-wide (except maybe with "defaults"). This will result in useful	507	Assuming that the physical Backspace key corresponds to the Backspace
238	behaviour. If your distribution aims at low memory, add an empty	508	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	509	two standard values that can be used for Backspace: "^H" and "^?".
240	perl interpreter disabled until the user enables it.
241		510
242	If you can/want build more binaries, I recommend building a minimal one	511	Historically, either value is correct, but rxvt-unicode adopts the
243	with "--disable-everything" (very useful) and a maximal one with	512	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	513	correct choice :).
245	encodings built-in that increase download times and are rarely used).
246		514
247	I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	515	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	516	value of `erase' to guess the value for backspace. If rxvt-unicode
249	install urxvt with privileges necessary for your OS now.	517	wasn't started from a terminal (say, from a menu or by remote shell),
		518	then the system value of `erase', which corresponds to CERASE in
		519	<termios.h>, will be used (which may not be the same as your stty
		520	setting).
250		521
251	When rxvt-unicode detects that it runs setuid or setgid, it will fork	522	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		523
258	This forking is done as the very first within main(), which is very	524	# use Backspace = ^H
259	early and reduces possible bugs to initialisation code run before	525	$ stty erase ^H
260	main(), or things like the dynamic loader of your system, which should	526	$ urxvt
261	result in very little risk.
262		527
		528	# use Backspace = ^?
		529	$ stty erase ^?
		530	$ urxvt
		531
		532	Toggle with "ESC [ 36 h" / "ESC [ 36 l".
		533
		534	For an existing rxvt-unicode:
		535
		536	# use Backspace = ^H
		537	$ stty erase ^H
		538	$ echo -n "^[[36h"
		539
		540	# use Backspace = ^?
		541	$ stty erase ^?
		542	$ echo -n "^[[36l"
		543
		544	This helps satisfy some of the Backspace discrepancies that occur, but
		545	if you use Backspace = "^H", make sure that the termcap/terminfo value
		546	properly reflects that.
		547
		548	The Delete key is a another casualty of the ill-defined Backspace
		549	problem. To avoid confusion between the Backspace and Delete keys, the
		550	Delete key has been assigned an escape sequence to match the vt100 for
		551	Execute ("ESC [ 3 ~") and is in the supplied termcap/terminfo.
		552
		553	Some other Backspace problems:
		554
		555	some editors use termcap/terminfo, some editors (vim I'm told) expect
		556	Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for help.
		557
		558	Perhaps someday this will all be resolved in a consistent manner.
		559
		560	I don't like the key-bindings. How do I change them?
		561	There are some compile-time selections available via configure. Unless
		562	you have run "configure" with the "--disable-resources" option you can
		563	use the `keysym' resource to alter the keystrings associated with
		564	keysyms.
		565
		566	Here's an example for a URxvt session started using "urxvt -name URxvt"
		567
		568	URxvt.keysym.Home: \033[1~
		569	URxvt.keysym.End: \033[4~
		570	URxvt.keysym.C-apostrophe: \033<C-'>
		571	URxvt.keysym.C-slash: \033<C-/>
		572	URxvt.keysym.C-semicolon: \033<C-;>
		573	URxvt.keysym.C-grave: \033<C-`>
		574	URxvt.keysym.C-comma: \033<C-,>
		575	URxvt.keysym.C-period: \033<C-.>
		576	URxvt.keysym.C-0x60: \033<C-`>
		577	URxvt.keysym.C-Tab: \033<C-Tab>
		578	URxvt.keysym.C-Return: \033<C-Return>
		579	URxvt.keysym.S-Return: \033<S-Return>
		580	URxvt.keysym.S-space: \033<S-Space>
		581	URxvt.keysym.M-Up: \033<M-Up>
		582	URxvt.keysym.M-Down: \033<M-Down>
		583	URxvt.keysym.M-Left: \033<M-Left>
		584	URxvt.keysym.M-Right: \033<M-Right>
		585	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		586	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		587	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		588
		589	See some more examples in the documentation for the keysym resource.
		590
		591	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
		592	KP_Insert == Insert
		593	F22 == Print
		594	F27 == Home
		595	F29 == Prior
		596	F33 == End
		597	F35 == Next
		598
		599	Rather than have rxvt-unicode try to accommodate all the various
		600	possible keyboard mappings, it is better to use `xmodmap' to remap the
		601	keys as required for your particular machine.
		602
		603	Terminal Configuration
		604	Can I see a typical configuration?
		605	The default configuration tries to be xterm-like, which I don't like
		606	that much, but it's least surprise to regular users.
		607
		608	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		609	time into customising your terminal. To get you started, here is the
		610	author's .Xdefaults entries, with comments on what they do. It's
		611	certainly not *typical*, but what's typical...
		612
		613	URxvt.cutchars: "()*,<>[]{}|'
		614	URxvt.print-pipe: cat >/tmp/xxx
		615
		616	These are just for testing stuff.
		617
		618	URxvt.imLocale: ja_JP.UTF-8
		619	URxvt.preeditType: OnTheSpot,None
		620
		621	This tells rxvt-unicode to use a special locale when communicating with
		622	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		623	type, which requires the "xim-onthespot" perl extension but rewards me
		624	with correct-looking fonts.
		625
		626	URxvt.perl-lib: /root/lib/urxvt
		627	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		628	URxvt.selection.pattern-0: ( at .*? line \\d+)
		629	URxvt.selection.pattern-1: ^(/[^:]+):\
		630	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		631	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		632
		633	This is my perl configuration. The first two set the perl library
		634	directory and also tells urxvt to use a large number of extensions. I
		635	develop for myself mostly, so I actually use most of the extensions I
		636	write.
		637
		638	The selection stuff mainly makes the selection perl-error-message aware
		639	and tells it to convert perl error messages into vi-commands to load the
		640	relevant file and go tot he error line number.
		641
		642	URxvt.scrollstyle: plain
		643	URxvt.secondaryScroll: true
		644
		645	As the documentation says: plain is the preferred scrollbar for the
		646	author. The "secondaryScroll" configures urxvt to scroll in full-screen
		647	apps, like screen, so lines scrolled out of screen end up in urxvt's
		648	scrollback buffer.
		649
		650	URxvt.background: #000000
		651	URxvt.foreground: gray90
		652	URxvt.color7: gray90
		653	URxvt.colorBD: #ffffff
		654	URxvt.cursorColor: #e0e080
		655	URxvt.throughColor: #8080f0
		656	URxvt.highlightColor: #f0f0f0
		657
		658	Some colours. Not sure which ones are being used or even non-defaults,
		659	but these are in my .Xdefaults. Most notably, they set
		660	foreground/background to light gray/black, and also make sure that the
		661	colour 7 matches the default foreground colour.
		662
		663	URxvt.underlineColor: yellow
		664
		665	Another colour, makes underline lines look different. Sometimes hurts,
		666	but is mostly a nice effect.
		667
		668	URxvt.geometry: 154x36
		669	URxvt.loginShell: false
		670	URxvt.meta: ignore
		671	URxvt.utmpInhibit: true
		672
		673	Uh, well, should be mostly self-explanatory. By specifying some defaults
		674	manually, I can quickly switch them for testing.
		675
		676	URxvt.saveLines: 8192
		677
		678	A large scrollback buffer is essential. Really.
		679
		680	URxvt.mapAlert: true
		681
		682	The only case I use it is for my IRC window, which I like to keep
		683	iconified till people msg me (which beeps).
		684
		685	URxvt.visualBell: true
		686
		687	The audible bell is often annoying, especially when in a crowd.
		688
		689	URxvt.insecure: true
		690
		691	Please don't hack my mutt! Ooops...
		692
		693	URxvt.pastableTabs: false
		694
		695	I once thought this is a great idea.
		696
		697	urxvt.font: 9x15bold,\
		698	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		699	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		700	[codeset=JISX0208]xft:Kochi Gothic, \
		701	xft:Bitstream Vera Sans Mono:autohint=true, \
		702	xft:Code2000:antialias=false
		703	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		704	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		705	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		706
		707	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		708	overwhelmed. A special note: the "9x15bold" mentioned above is actually
		709	the version from XFree-3.3, as XFree-4 replaced it by a totally
		710	different font (different glyphs for ";" and many other harmless
		711	characters), while the second font is actually the "9x15bold" from
		712	XFree4/XOrg. The bold version has less chars than the medium version, so
		713	I use it for rare characters, too. When editing sources with vim, I use
		714	italic for comments and other stuff, which looks quite good with
		715	Bitstream Vera anti-aliased.
		716
		717	Terminus is a quite bad font (many very wrong glyphs), but for most of
		718	my purposes, it works, and gives a different look, as my normal
		719	(Non-bold) font is already bold, and I want to see a difference between
		720	bold and normal fonts.
		721
		722	Please note that I used the "urxvt" instance name and not the "URxvt"
		723	class name. Thats because I use different configs for different
		724	purposes, for example, my IRC window is started with "-name IRC", and
		725	uses these defaults:
		726
		727	IRC*title: IRC
		728	IRC*geometry: 87x12+535+542
		729	IRC*saveLines: 0
		730	IRC*mapAlert: true
		731	IRC*font: suxuseuro
		732	IRC*boldFont: suxuseuro
		733	IRC*colorBD: white
		734	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		735	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		736
		737	"Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes.
		738	"suxuseuro" allows me to keep an eye (and actually read) stuff while
		739	keeping a very small window. If somebody pastes something complicated
		740	(e.g. japanese), I temporarily switch to a larger font.
		741
		742	The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
		743	"xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
		744	file for different hosts, for example, on ym main desktop, I use:
		745
		746	URxvt.keysym.C-M-q: command:\033[3;5;5t
		747	URxvt.keysym.C-M-y: command:\033[3;5;606t
		748	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		749	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		750	URxvt.keysym.C-M-p: perl:test
		751
		752	The first for keysym definitions allow me to quickly bring some windows
		753	in the layout I like most. Ion users might start laughing but will stop
		754	immediately when I tell them that I use my own Fvwm2 module for much the
		755	same effect as Ion provides, and I only very rarely use the above key
		756	combinations :->
		757
		758	Why doesn't rxvt-unicode read my resources?
		759	Well, why, indeed? It does, in a way very similar to other X
		760	applications. Most importantly, this means that if you or your OS loads
		761	resources into the X display (the right way to do it), rxvt-unicode will
		762	ignore any resource files in your home directory. It will only read
		763	$HOME/.Xdefaults when no resources are attached to the display.
		764
		765	If you have or use an $HOME/.Xresources file, chances are that resources
		766	are loaded into your X-server. In this case, you have to re-login after
		767	every change (or run xrdb -merge $HOME/.Xresources).
		768
		769	Also consider the form resources have to use:
		770
		771	URxvt.resource: value
		772
		773	If you want to use another form (there are lots of different ways of
		774	specifying resources), make sure you understand whether and why it
		775	works. If unsure, use the form above.
		776
263	When I log-in to another system it tells me about missing terminfo data?	777	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	778	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	779	as that for xterm, or even rxvt (for which the same problem often
266	arises).	780	arises).
267		781
268	The correct solution for this problem is to install the terminfo, this	782	The correct solution for this problem is to install the terminfo, this
269	can be done like this (with ncurses' infocmp):	783	can be done like this (with ncurses' infocmp and works as user and
		784	admin):
270		785
271	REMOTE=remotesystem.domain	786	REMOTE=remotesystem.domain
272	infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	787	infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
273		788
274	... or by installing rxvt-unicode normally on the remote system,	789	... or by installing rxvt-unicode normally on the remote system,
		790
		791	One some systems you might need to set $TERMINFO to the full path of
		792	$HOME/.terminfo for this to work.
275		793
276	If you cannot or do not want to do this, then you can simply set	794	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	795	"TERM=rxvt" or even "TERM=xterm", and live with the small number of
278	problems arising, which includes wrong keymapping, less and different	796	problems arising, which includes wrong keymapping, less and different
279	colours and some refresh errors in fullscreen applications. It's a nice	797	colours and some refresh errors in fullscreen applications. It's a nice
…		…
284	resource to set it:	802	resource to set it:
285		803
286	URxvt.termName: rxvt	804	URxvt.termName: rxvt
287		805
288	If you don't plan to use rxvt (quite common...) you could also replace	806	If you don't plan to use rxvt (quite common...) you could also replace
289	the rxvt terminfo file with the rxvt-unicode one.	807	the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
290		808
291	"tic" outputs some error when compiling the terminfo entry.	809	"tic" outputs some error when compiling the terminfo entry.
292	Most likely it's the empty definition for "enacs=". Just replace it by	810	Most likely it's the empty definition for "enacs=". Just replace it by
293	"enacs=\E[0@" and try again.	811	"enacs=\E[0@" and try again.
294		812
295	"bash"'s readline does not work correctly under rxvt.	813	"bash"'s readline does not work correctly under urxvt.
296	See next entry.	814	See next entry.
297		815
298	I need a termcap file entry.	816	I need a termcap file entry.
299	One reason you might want this is that some distributions or operating	817	One reason you might want this is that some distributions or operating
300	systems still compile some programs using the long-obsoleted termcap	818	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	819	library (Fedora Core's bash is one example) and rely on a termcap entry
302	for "rxvt-unicode".	820	for "rxvt-unicode".
303		821
304	You could use rxvt's termcap entry with resonable results in many cases.	822	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	823	cases. You can also create a termcap entry by using terminfo's infocmp
306	like this:	824	program like this:
307		825
308	infocmp -C rxvt-unicode	826	infocmp -C rxvt-unicode
309		827
310	Or you could use this termcap entry, generated by the command above:	828	Or you could use this termcap entry, generated by the command above:
311		829
…		…
328	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	846	: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:\	847	: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:\	848	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
331	:vs=\E[?25h:	849	:vs=\E[?25h:
332		850
333	Why does "ls" no longer have coloured output?	851	Why does "ls" no longer have coloured output?
334	The "ls" in the GNU coreutils unfortunately doesn't use terminfo to	852	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	853	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	854	file. Needless to say, "rxvt-unicode" is not in its default file (among
337	with most other terminals supporting colour). Either add:	855	with most other terminals supporting colour). Either add:
338		856
339	TERM rxvt-unicode	857	TERM rxvt-unicode
340		858
341	to "/etc/DIR_COLORS" or simply add:	859	to "/etc/DIR_COLORS" or simply add:
342		860
343	alias ls='ls --color=auto'	861	alias ls='ls --color=auto'
344		862
345	to your ".profile" or ".bashrc".	863	to your ".profile" or ".bashrc".
346		864
347	Why doesn't vim/emacs etc. use the 88 colour mode?	865	Why doesn't vim/emacs etc. use the 88 colour mode?
348	See next entry.	866	See next entry.
349		867
350	Why doesn't vim/emacs etc. make use of italic?	868	Why doesn't vim/emacs etc. make use of italic?
351	See next entry.	869	See next entry.
352		870
353	Why are the secondary screen-related options not working properly?	871	Why are the secondary screen-related options not working properly?
354	Make sure you are using "TERM=rxvt-unicode". Some pre-packaged	872	Make sure you are using "TERM=rxvt-unicode". Some pre-packaged
355	distributions (most notably Debian GNU/Linux) break rxvt-unicode by	873	distributions (most notably Debian GNU/Linux) break rxvt-unicode by
356	setting "TERM" to "rxvt", which doesn't have these extra features.	874	setting "TERM" to "rxvt", which doesn't have these extra features.
357	Unfortunately, some of these (most notably, again, Debian GNU/Linux)	875	Unfortunately, some of these (most notably, again, Debian GNU/Linux)
358	furthermore fail to even install the "rxvt-unicode" terminfo file, so	876	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	877	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	878	to another system it tells me about missing terminfo data? on how to do
361	this).	879	this).
362		880
363	My numerical keypad acts weird and generates differing output?	881	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?	882	Rxvt-unicode does not seem to understand the selected encoding?
372	See next entry.	883	See next entry.
373		884
374	Unicode does not seem to work?	885	Unicode does not seem to work?
375	If you encounter strange problems like typing an accented character but	886	If you encounter strange problems like typing an accented character but
376	getting two unrelated other characters or similar, or if program output	887	getting two unrelated other characters or similar, or if program output
377	is subtly garbled, then you should check your locale settings.	888	is subtly garbled, then you should check your locale settings.
378		889
379	Rxvt-unicode must be started with the same "LC_CTYPE" setting as the	890	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	891	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	892	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	893	the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
383	going to work.	894	is not going to work, and is the most common cause for problems.
384		895
385	The best thing is to fix your startup environment, as you will likely	896	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	897	run into other problems. If nothing works you can try this in your
387	.profile.	898	.profile.
388		899
389	printf '\e]701;%s\007' "$LC_CTYPE"	900	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
390		901
391	If this doesn't work, then maybe you use a "LC_CTYPE" specification not	902	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	903	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	904	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	905	it will complain loudly if it cannot set the locale). If it displays
…		…
400		911
401	If nothing works and you are sure that everything is set correctly then	912	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	913	you will need to remember a little known fact: Some programs just don't
403	support locales :(	914	support locales :(
404		915
405	Why do some characters look so much different than others?	916	How does rxvt-unicode determine the encoding to use?
406	See next entry.	917	See next entry.
407		918
408	How does rxvt-unicode choose fonts?	919	Is there an option to switch encodings?
409	Most fonts do not contain the full range of Unicode, which is fine.	920	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	921	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	922	about UTF-8 or any other encodings with respect to terminal I/O.
412	display.
413		923
414	rxvt-unicode makes a best-effort try at finding a replacement font.	924	The reasons is that there exists a perfectly fine mechanism for
415	Often the result is fine, but sometimes the chosen font looks	925	selecting the encoding, doing I/O and (most important) communicating
416	bad/ugly/wrong. Some fonts have totally strange characters that don't	926	this to all applications so everybody agrees on character properties
417	resemble the correct glyph at all, and rxvt-unicode lacks the artificial	927	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	928	Applications not using that info will have problems (for example,
419	the font that the characters it claims to contain indeed look correct.	929	"xterm" gets the width of characters wrong as it uses its own,
		930	locale-independent table under all locales).
420		931
421	In that case, select a font of your taste and add it to the font list,	932	Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All
422	e.g.:	933	programs doing the same (that is, most) will automatically agree in the
		934	interpretation of characters.
423		935
424	rxvt -fn basefont,font2,font3...	936	Unfortunately, there is no system-independent way to select locales, nor
		937	is there a standard on how locale specifiers will look like.
425		938
426	When rxvt-unicode sees a character, it will first look at the base font.	939	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	940	contains an arbitrary string which corresponds to an already-installed
428	font, and so on. Specifying your own fonts will also speed up this	941	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.	942	"ja_JP.EUC-JP", i.e. "language_country.encoding", but other forms (i.e.
		943	"de" or "german") are also common.
430		944
431	The only limitation is that none of the fonts may be larger than the	945	Rxvt-unicode ignores all other locale categories, and except for the
432	base font, as the base font defines the terminal character cell size,	946	encoding, ignores country or language-specific settings, i.e.
433	which must be the same due to the way terminals work.	947	"de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to rxvt-unicode.
434		948
435	Why do some chinese characters look so different than others?	949	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 --	950	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		951
446	The workaround is easy: just tag a chinese font at the end of your font	952	Can I switch locales at runtime?
447	list (see the previous question). The key is to view the font list as a	953	Yes, using an escape sequence. Try something like this, which sets
448	preference list: If you expect more japanese, list a japanese font	954	rxvt-unicode's idea of "LC_CTYPE".
449	first. If you expect more chinese, put a chinese font first.
450		955
451	In the future it might be possible to switch language preferences at	956	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		957
456	Until then, you might get away with switching fonts at runtime (see "Can	958	See also the previous answer.
457	I switch the fonts at runtime?" later in this document).
458		959
459	Why does rxvt-unicode sometimes leave pixel droppings?	960	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	961	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	962	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	963	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		964
467	All of this requires that fonts do not lie about character sizes,	965	printf '\33]701;%s\007' ja_JP.SJIS
468	however: Xft fonts often draw glyphs larger than their acclaimed	966	xjdic -js
469	bounding box, and rxvt-unicode has no way of detecting this (the correct	967	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		968
473	It's not clear (to me at least), wether this is a bug in Xft, freetype,	969	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	970	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	971	and rxvt-unicode-locales.
476	work, you might be forced to use a different font.
477		972
478	All of this is not a problem when using X11 core fonts, as their	973	I have problems getting my input method working.
479	bounding box data is correct.	974	Try a search engine, as this is slightly different for every input
		975	method server.
480		976
481	On Solaris 9, many line-drawing characters are too wide.	977	Here is a checklist:
482	Seems to be a known bug, read
483	<http://nixdoc.net/files/forum/about34198.html>. Some people use the
484	following ugly workaround to get non-double-wide-characters working:
485		978
486	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	979	- Make sure your locale *and* the imLocale are supported on your OS.
		980	Try "locale -a" or check the documentation for your OS.
487		981
488	My Compose (Multi_key) key is no longer working.	982	- Make sure your locale or imLocale matches a locale supported by your
489	The most common causes for this are that either your locale is not set	983	XIM.
490	correctly, or you specified a preeditStyle that is not supported by your	984	For example, kinput2 does not support UTF-8 locales, you should use
491	input method. For example, if you specified OverTheSpot and your input	985	"ja_JP.EUC-JP" or equivalent.
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		986
496	In this case either do not specify a preeditStyle or specify more than	987	- Make sure your XIM server is actually running.
497	one pre-edit style, such as OverTheSpot,Root,None.	988	- Make sure the "XMODIFIERS" environment variable is set correctly when
		989	*starting* rxvt-unicode.
		990	When you want to use e.g. kinput2, it must be set to "@im=kinput2".
		991	For scim, use "@im=SCIM". You can see what input method servers are
		992	running with this command:
498		993
499	I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755	994	xprop -root XIM_SERVERS
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		995
506	How can I keep rxvt-unicode from using reverse video so much?	996	*
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		997
512	URxvt.colorBD: white	998	My input method wants <some encoding> but I want UTF-8, what can I do?
513	URxvt.colorIT: green	999	You can specify separate locales for the input method and the rest of
		1000	the terminal, using the resource "imlocale":
514		1001
515	Some programs assume totally weird colours (red instead of blue), how can I fix that?	1002	URxvt.imlocale: ja_JP.EUC-JP
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		1003
522	In the meantime, you can either edit your "rxvt-unicode" terminfo	1004	Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still
523	definition to only claim 8 colour support or use "TERM=rxvt", which will	1005	use your input method. Please note, however, that, depending on your
524	fix colours but keep you from using other rxvt-unicode features.	1006	Xlib version, you may not be able to input characters outside "EUC-JP"
		1007	in a normal way then, as your input method limits you.
525		1008
		1009	Rxvt-unicode crashes when the X Input Method changes or exits.
		1010	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		1011	design. Applications can avoid some crashes at the expense of memory
		1012	leaks, and Input Methods can avoid some crashes by careful ordering at
		1013	exit time. kinput2 (and derived input methods) generally succeeds, while
		1014	SCIM (or similar input methods) fails. In the end, however, crashes
		1015	cannot be completely avoided even if both sides cooperate.
		1016
		1017	So the only workaround is not to kill your Input Method Servers.
		1018
		1019	Operating Systems / Package Maintaining
		1020	I am using Debian GNU/Linux and have a problem...
		1021	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		1022	patches that considerably change the behaviour of rxvt-unicode (but
		1023	unfortunately this notice has been removed). Before reporting a bug to
		1024	the original rxvt-unicode author please download and install the genuine
		1025	version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		1026	the problem. If you cannot, chances are that the problems are specific
		1027	to Debian GNU/Linux, in which case it should be reported via the Debian
		1028	Bug Tracking System (use "reportbug" to report the bug).
		1029
		1030	For other problems that also affect the Debian package, you can and
		1031	probably should use the Debian BTS, too, because, after all, it's also a
		1032	bug in the Debian version and it serves as a reminder for other users
		1033	that might encounter the same issue.
		1034
		1035	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		1036	You should build one binary with the default options. configure now
		1037	enables most useful options, and the trend goes to making them
		1038	runtime-switchable, too, so there is usually no drawback to enabling
		1039	them, except higher disk and possibly memory usage. The perl interpreter
		1040	should be enabled, as important functionality (menus, selection, likely
		1041	more in the future) depends on it.
		1042
		1043	You should not overwrite the "perl-ext-common" snd "perl-ext" resources
		1044	system-wide (except maybe with "defaults"). This will result in useful
		1045	behaviour. If your distribution aims at low memory, add an empty
		1046	"perl-ext-common" resource to the app-defaults file. This will keep the
		1047	perl interpreter disabled until the user enables it.
		1048
		1049	If you can/want build more binaries, I recommend building a minimal one
		1050	with "--disable-everything" (very useful) and a maximal one with
		1051	"--enable-everything" (less useful, it will be very big due to a lot of
		1052	encodings built-in that increase download times and are rarely used).
		1053
		1054	I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		1055	It should be, starting with release 7.1. You are encouraged to properly
		1056	install urxvt with privileges necessary for your OS now.
		1057
		1058	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		1059	into a helper process for privileged operations (pty handling on some
		1060	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		1061	immediately. This is much safer than most other terminals that keep
		1062	privileges while running (but is more relevant to urxvt, as it contains
		1063	things as perl interpreters, which might be "helpful" to attackers).
		1064
		1065	This forking is done as the very first within main(), which is very
		1066	early and reduces possible bugs to initialisation code run before
		1067	main(), or things like the dynamic loader of your system, which should
		1068	result in very little risk.
		1069
526	I am on FreeBSD and rxvt-unicode does not seem to work at all.	1070	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	1071	Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
528	your compile environment, or an implementation that implements it,	1072	your compile environment, or an implementation that implements it,
529	wether it defines the symbol or not. "__STDC_ISO_10646__" requires that	1073	whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
530	wchar_t is represented as unicode.	1074	wchar_t is represented as unicode.
531		1075
532	As you might have guessed, FreeBSD does neither define this symobl nor	1076	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	1077	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.	1078	wchar_t. This is, of course, completely fine with respect to standards.
535		1079
536	However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and	1080	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.	1081	"UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
538		1082
…		…
552		1096
553	The rxvt-unicode author insists that the right way to fix this is in the	1097	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	1098	system libraries once and for all, instead of forcing every app to carry
555	complete replacements for them :)	1099	complete replacements for them :)
556		1100
557	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
559	problems with "wcwidth" and a compile problem.
560
561	How can I use rxvt-unicode under cygwin?	1101	How can I use rxvt-unicode under cygwin?
562	rxvt-unicode should compile and run out of the box on cygwin, using the	1102	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	1103	X11 libraries that come with cygwin. libW11 emulation is no longer
564	supported (and makes no sense, either, as it only supported a single	1104	supported (and makes no sense, either, as it only supported a single
565	font). I recommend starting the X-server in "-multiwindow" or	1105	font). I recommend starting the X-server in "-multiwindow" or
566	"-rootless" mode instead, which will result in similar look&feel as the	1106	"-rootless" mode instead, which will result in similar look&feel as the
…		…
568		1108
569	At the time of this writing, cygwin didn't seem to support any	1109	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	1110	multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
571	likely limited to 8-bit encodings.	1111	likely limited to 8-bit encodings.
572		1112
573	How does rxvt-unicode determine the encoding to use?	1113	Character widths are not correct.
574	See next entry.	1114	urxvt uses the system wcwidth function to know the information about the
		1115	width of characters, so on systems with incorrect locale data you will
		1116	likely get bad results. Two notorious examples are Solaris 9, where
		1117	single-width characters like U+2514 are reported as double-width, and
		1118	Darwin 8, where combining chars are reported having width 1.
575		1119
576	Is there an option to switch encodings?	1120	The solution is to upgrade your system or switch to a better one. A
577	Unlike some other terminals, rxvt-unicode has no encoding switch, and no	1121	possibly working workaround is to use a wcwidth implementation like
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		1122
581	The reasons is that there exists a perfectly fine mechanism for	1123	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
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		1124
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