[ViewVC] Diff of: cvs/rxvt-unicode/README.FAQ

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.39 by root, Tue Jan 31 20:52:19 2006 UTC vs.
Revision 1.59 by sf-exg, Sat Jul 24 14:20:48 2010 UTC

…		…
1	FREQUENTLY ASKED QUESTIONS	1	RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
2	Meta, Features & Commandline Issues	2	Meta, Features & Commandline Issues
3	My question isn't answered here, can I ask a human?	3	My question isn't answered here, can I ask a human?
4	Before sending me mail, you could go to IRC: "irc.freenode.net", channel	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	5	"#rxvt-unicode" has some rxvt-unicode enthusiasts that might be
6	interested in learning about new and exciting problems (but not FAQs :).	6	interested in learning about new and exciting problems (but not FAQs :).
7		7
		8	I use Gentoo, and I have a problem...
		9	There are three big problems with Gentoo Linux: first of all, most if
		10	not all Gentoo systems are completely broken (missing or mismatched
		11	header files, broken compiler etc. are just the tip of the iceberg);
		12	secondly, the Gentoo maintainer thinks it is a good idea to add broken
		13	patches to the code; and lastly, it should be called Gentoo GNU/Linux.
		14
		15	For these reasons, it is impossible to support rxvt-unicode on Gentoo.
		16	Problems appearing on Gentoo systems will usually simply be ignored
		17	unless they can be reproduced on non-Gentoo systems.
		18
8	Does it support tabs, can I have a tabbed rxvt-unicode?	19	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	20	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	21	simple tabbed terminal. It is installed by default, so any of these
11	should give you tabs:	22	should give you tabs:
12		23
13	rxvt -pe tabbed	24	urxvt -pe tabbed
14		25
15	URxvt.perl-ext-common: default,tabbed	26	URxvt.perl-ext-common: default,tabbed
16		27
17	It will also work fine with tabbing functionality of many window	28	It will also work fine with tabbing functionality of many window
18	managers or similar tabbing programs, and its embedding-features allow	29	managers or similar tabbing programs, and its embedding-features allow
21	(murxvt) terminal as an example embedding application.	32	(murxvt) terminal as an example embedding application.
22		33
23	How do I know which rxvt-unicode version I'm using?	34	How do I know which rxvt-unicode version I'm using?
24	The version number is displayed with the usage (-h). Also the escape	35	The version number is displayed with the usage (-h). Also the escape
25	sequence "ESC [ 8 n" sets the window title to the version number. When	36	sequence "ESC [ 8 n" sets the window title to the version number. When
26	using the rxvtc client, the version displayed is that of the daemon.	37	using the urxvtc client, the version displayed is that of the daemon.
27		38
28	Rxvt-unicode uses gobs of memory, how can I reduce that?	39	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	40	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	41	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	42	that you don't need, for example, Xft support is a resource hog by
…		…
38	bytes per screen cell. For a 160x?? window this amounts to almost a	49	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	50	kilobyte per line. A scrollback buffer of 10000 lines will then (if
40	full) use 10 Megabytes of memory. With "--enable-unicode3" it gets	51	full) use 10 Megabytes of memory. With "--enable-unicode3" it gets
41	worse, as rxvt-unicode then uses 8 bytes per screen cell.	52	worse, as rxvt-unicode then uses 8 bytes per screen cell.
42		53
43	How can I start rxvtd in a race-free way?	54	How can I start urxvtd in a race-free way?
44	Try "rxvtd -f -o", which tells rxvtd to open the display, create the	55	Try "urxvtd -f -o", which tells urxvtd to open the display, create the
45	listening socket and then fork.	56	listening socket and then fork.
46		57
47	How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.	58	How can I start urxvtd automatically when I run urxvtc?
48	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can	59	If you want to start urxvtd automatically whenever you run urxvtc and
49	check and see if that is set. Note that several programs, JED, slrn,	60	the daemon isn't running yet, use this script:
50	Midnight Commander automatically check this variable to decide whether	61
51	or not to use color.	62	#!/bin/sh
		63	urxvtc "$@"
		64	if [ $? -eq 2 ]; then
		65	urxvtd -q -o -f
		66	urxvtc "$@"
		67	fi
		68
		69	This tries to create a new terminal, and if fails with exit status 2,
		70	meaning it couldn't connect to the daemon, it will start the daemon and
		71	re-run the command. Subsequent invocations of the script will re-use the
		72	existing daemon.
		73
		74	How do I distinguish whether I'm running rxvt-unicode or a regular
		75	xterm? I need this to decide about setting colours etc.
		76	The original rxvt and rxvt-unicode always export the variable
		77	"COLORTERM", so you can check and see if that is set. Note that several
		78	programs, JED, slrn, Midnight Commander automatically check this
		79	variable to decide whether or not to use colour.
52		80
53	How do I set the correct, full IP address for the DISPLAY variable?	81	How do I set the correct, full IP address for the DISPLAY variable?
54	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled	82	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
55	insecure mode then it is possible to use the following shell script	83	insecure mode then it is possible to use the following shell script
56	snippets to correctly set the display. If your version of rxvt-unicode	84	snippets to correctly set the display. If your version of rxvt-unicode
…		…
74	fi	102	fi
75	fi	103	fi
76		104
77	How do I compile the manual pages on my own?	105	How do I compile the manual pages on my own?
78	You need to have a recent version of perl installed as /usr/bin/perl,	106	You need to have a recent version of perl installed as /usr/bin/perl,
79	one that comes with pod2man, pod2text and pod2html. Then go to the doc	107	one that comes with pod2man, pod2text and pod2xhtml (from Pod::Xhtml).
80	subdirectory and enter "make alldoc".	108	Then go to the doc subdirectory and enter "make alldoc".
81		109
82	Isn't rxvt-unicode supposed to be small? Don't all those features bloat?	110	Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
83	I often get asked about this, and I think, no, they didn't cause extra	111	I often get asked about this, and I think, no, they didn't cause extra
84	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see	112	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
85	that the urxvt binary is larger (due to some encoding tables always	113	that the urxvt binary is larger (due to some encoding tables always
…		…
90		118
91	text data bss drs rss filename	119	text data bss drs rss filename
92	98398 1664 24 15695 1824 rxvt --disable-everything	120	98398 1664 24 15695 1824 rxvt --disable-everything
93	188985 9048 66616 18222 1788 urxvt --disable-everything	121	188985 9048 66616 18222 1788 urxvt --disable-everything
94		122
95	When you "--enable-everything" (which _is_ unfair, as this involves xft	123	When you "--enable-everything" (which is unfair, as this involves xft
96	and full locale/XIM support which are quite bloaty inside libX11 and my	124	and full locale/XIM support which are quite bloaty inside libX11 and my
97	libc), the two diverge, but not unreasnobaly so.	125	libc), the two diverge, but not unreasonably so.
98		126
99	text data bss drs rss filename	127	text data bss drs rss filename
100	163431 2152 24 20123 2060 rxvt --enable-everything	128	163431 2152 24 20123 2060 rxvt --enable-everything
101	1035683 49680 66648 29096 3680 urxvt --enable-everything	129	1035683 49680 66648 29096 3680 urxvt --enable-everything
102		130
…		…
144		172
145	And here is rxvt-unicode:	173	And here is rxvt-unicode:
146		174
147	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	175	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
148	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)	176	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
149	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)	177	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
150	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)	178	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
151	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	179	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
152		180
153	No large bloated libraries (of course, none were linked in statically),	181	No large bloated libraries (of course, none were linked in statically),
154	except maybe libX11 :)	182	except maybe libX11 :)
155		183
156	Rendering, Font & Look and Feel Issues	184	Rendering, Font & Look and Feel Issues
157	I can't get transparency working, what am I doing wrong?	185	I can't get transparency working, what am I doing wrong?
158	First of all, transparency isn't officially supported in rxvt-unicode,	186	First of all, please address all transparency related issues to Sasha
159	so you are mostly on your own. Do not bug the author about it (but you	187	Vasko at sasha@aftercode.net and do not bug the author about it. Also,
160	may bug everybody else). Also, if you can't get it working consider it a	188	if you can't get it working consider it a rite of passage: ... and you
161	rite of passage: ... and you failed.	189	failed.
162		190
163	Here are four ways to get transparency. Do read the manpage and option	191	Here are four ways to get transparency. Do read the manpage and option
164	descriptions for the programs mentioned and rxvt-unicode. Really, do it!	192	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
165		193
166	1. Use inheritPixmap:	194	1. Use transparent mode:
167		195
168	Esetroot wallpaper.jpg	196	Esetroot wallpaper.jpg
169	rxvt -ip -tint red -sh 40	197	urxvt -tr -tint red -sh 40
170		198
171	That works. If you think it doesn't, you lack transparency and tinting	199	That works. If you think it doesn't, you lack transparency and tinting
172	support, or you are unable to read.	200	support, or you are unable to read.
173		201
174	2. Use a simple pixmap and emulate pseudo-transparency. This enables you	202	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
175	to use effects other than tinting and shading: Just shade/tint/whatever	203	to use effects other than tinting and shading: Just shade/tint/whatever
176	your picture with gimp or any other tool:	204	your picture with gimp or any other tool:
177		205
178	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	206	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
179	rxvt -pixmap background.xpm -pe automove-background	207	urxvt -pixmap "background.jpg;:root"
180		208
181	That works. If you think it doesn't, you lack XPM and Perl support, or	209	That works. If you think it doesn't, you lack AfterImage support, or you
182	you are unable to read.	210	are unable to read.
183		211
184	3. Use an ARGB visual:	212	3. Use an ARGB visual:
185		213
186	rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc	214	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
187		215
188	This requires XFT support, and the support of your X-server. If that	216	This requires XFT support, and the support of your X-server. If that
189	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't	217	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
190	there yet, no matter what they claim. Rxvt-Unicode contains the	218	there yet, no matter what they claim. Rxvt-Unicode contains the
191	neccessary bugfixes and workarounds for Xft and Xlib to make it work,	219	necessary bugfixes and workarounds for Xft and Xlib to make it work, but
192	but that doesn't mean that your WM has the required kludges in place.	220	that doesn't mean that your WM has the required kludges in place.
193		221
194	4. Use xcompmgr and let it do the job:	222	4. Use xcompmgr and let it do the job:
195		223
196	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \	224	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
197	-set _NET_WM_WINDOW_OPACITY 0xc0000000	225	-set _NET_WM_WINDOW_OPACITY 0xc0000000
198		226
199	Then click on a window you want to make transparent. Replace 0xc0000000	227	Then click on a window you want to make transparent. Replace 0xc0000000
200	by other values to change the degree of opacity. If it doesn't work and	228	by other values to change the degree of opacity. If it doesn't work and
201	your server crashes, you got to keep the pieces.	229	your server crashes, you got to keep the pieces.
202
203	Why do some chinese characters look so different than others?
204	This is because there is a difference between script and language --
205	rxvt-unicode does not know which language the text that is output is, as
206	it only knows the unicode character codes. If rxvt-unicode first sees a
207	japanese/chinese character, it might choose a japanese font for display.
208	Subsequent japanese characters will use that font. Now, many chinese
209	characters aren't represented in japanese fonts, so when the first
210	non-japanese character comes up, rxvt-unicode will look for a chinese
211	font -- unfortunately at this point, it will still use the japanese font
212	for chinese characters that are also in the japanese font.
213
214	The workaround is easy: just tag a chinese font at the end of your font
215	list (see the previous question). The key is to view the font list as a
216	preference list: If you expect more japanese, list a japanese font
217	first. If you expect more chinese, put a chinese font first.
218
219	In the future it might be possible to switch language preferences at
220	runtime (the internal data structure has no problem with using different
221	fonts for the same character at the same time, but no interface for this
222	has been designed yet).
223
224	Until then, you might get away with switching fonts at runtime (see "Can
225	I switch the fonts at runtime?" later in this document).
226		230
227	Why does rxvt-unicode sometimes leave pixel droppings?	231	Why does rxvt-unicode sometimes leave pixel droppings?
228	Most fonts were not designed for terminal use, which means that	232	Most fonts were not designed for terminal use, which means that
229	character size varies a lot. A font that is otherwise fine for terminal	233	character size varies a lot. A font that is otherwise fine for terminal
230	use might contain some characters that are simply too wide. Rxvt-unicode	234	use might contain some characters that are simply too wide. Rxvt-unicode
…		…
236	however: Xft fonts often draw glyphs larger than their acclaimed	240	however: Xft fonts often draw glyphs larger than their acclaimed
237	bounding box, and rxvt-unicode has no way of detecting this (the correct	241	bounding box, and rxvt-unicode has no way of detecting this (the correct
238	way is to ask for the character bounding box, which unfortunately is	242	way is to ask for the character bounding box, which unfortunately is
239	wrong in these cases).	243	wrong in these cases).
240		244
241	It's not clear (to me at least), wether this is a bug in Xft, freetype,	245	It's not clear (to me at least), whether this is a bug in Xft, freetype,
242	or the respective font. If you encounter this problem you might try	246	or the respective font. If you encounter this problem you might try
243	using the "-lsp" option to give the font more height. If that doesn't	247	using the "-lsp" option to give the font more height. If that doesn't
244	work, you might be forced to use a different font.	248	work, you might be forced to use a different font.
245		249
246	All of this is not a problem when using X11 core fonts, as their	250	All of this is not a problem when using X11 core fonts, as their
…		…
268		272
269	Can I switch the fonts at runtime?	273	Can I switch the fonts at runtime?
270	Yes, using an escape sequence. Try something like this, which has the	274	Yes, using an escape sequence. Try something like this, which has the
271	same effect as using the "-fn" switch, and takes effect immediately:	275	same effect as using the "-fn" switch, and takes effect immediately:
272		276
273	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	277	printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
274		278
275	This is useful if you e.g. work primarily with japanese (and prefer a	279	This is useful if you e.g. work primarily with japanese (and prefer a
276	japanese font), but you have to switch to chinese temporarily, where	280	japanese font), but you have to switch to chinese temporarily, where
277	japanese fonts would only be in your way.	281	japanese fonts would only be in your way.
278		282
279	You can think of this as a kind of manual ISO-2022 switching.	283	You can think of this as a kind of manual ISO-2022 switching.
280		284
281	Why do italic characters look as if clipped?	285	Why do italic characters look as if clipped?
282	Many fonts have difficulties with italic characters and hinting. For	286	Many fonts have difficulties with italic characters and hinting. For
283	example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans	287	example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans
284	Mono" completely fails in it's italic face. A workaround might be to	288	Mono" completely fails in its italic face. A workaround might be to
285	enable freetype autohinting, i.e. like this:	289	enable freetype autohinting, i.e. like this:
286		290
287	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	291	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
288	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	292	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
289		293
…		…
293	antialiasing (by appending ":antialias=false"), which saves lots of	297	antialiasing (by appending ":antialias=false"), which saves lots of
294	memory and also speeds up rendering considerably.	298	memory and also speeds up rendering considerably.
295		299
296	Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	300	Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
297	Rxvt-unicode will use whatever you specify as a font. If it needs to	301	Rxvt-unicode will use whatever you specify as a font. If it needs to
298	fall back to it's default font search list it will prefer X11 core	302	fall back to its default font search list it will prefer X11 core fonts,
299	fonts, because they are small and fast, and then use Xft fonts. It has	303	because they are small and fast, and then use Xft fonts. It has
300	antialiasing disabled for most of them, because the author thinks they	304	antialiasing disabled for most of them, because the author thinks they
301	look best that way.	305	look best that way.
302		306
303	If you want antialiasing, you have to specify the fonts manually.	307	If you want antialiasing, you have to specify the fonts manually.
304		308
305	What's with this bold/blink stuff?	309	What's with this bold/blink stuff?
306	If no bold colour is set via "colorBD:", bold will invert text using the	310	If no bold colour is set via "colorBD:", bold will invert text using the
307	standard foreground colour.	311	standard foreground colour.
308		312
309	For the standard background colour, blinking will actually make the text	313	For the standard background colour, blinking will actually make the text
310	blink when compiled with "--enable-blinking". with standard colours.	314	blink when compiled with "--enable-text-blink". Without
311	Without "--enable-blinking", the blink attribute will be ignored.	315	"--enable-text-blink", the blink attribute will be ignored.
312		316
313	On ANSI colours, bold/blink attributes are used to set high-intensity	317	On ANSI colours, bold/blink attributes are used to set high-intensity
314	foreground/background colors.	318	foreground/background colours.
315		319
316	color0-7 are the low-intensity colors.	320	color0-7 are the low-intensity colours.
317		321
318	color8-15 are the corresponding high-intensity colors.	322	color8-15 are the corresponding high-intensity colours.
319		323
320	I don't like the screen colors. How do I change them?	324	I don't like the screen colours. How do I change them?
321	You can change the screen colors at run-time using ~/.Xdefaults	325	You can change the screen colours at run-time using ~/.Xdefaults
322	resources (or as long-options).	326	resources (or as long-options).
323		327
324	Here are values that are supposed to resemble a VGA screen, including	328	Here are values that are supposed to resemble a VGA screen, including
325	the murky brown that passes for low-intensity yellow:	329	the murky brown that passes for low-intensity yellow:
326		330
…		…
340	URxvt.color12: #0000FF	344	URxvt.color12: #0000FF
341	URxvt.color13: #FF00FF	345	URxvt.color13: #FF00FF
342	URxvt.color14: #00FFFF	346	URxvt.color14: #00FFFF
343	URxvt.color15: #FFFFFF	347	URxvt.color15: #FFFFFF
344		348
345	And here is a more complete set of non-standard colors described (not by	349	And here is a more complete set of non-standard colours.
346	me) as "pretty girly".
347		350
348	URxvt.cursorColor: #dc74d1	351	URxvt.cursorColor: #dc74d1
349	URxvt.pointerColor: #dc74d1	352	URxvt.pointerColor: #dc74d1
350	URxvt.background: #0e0e0e	353	URxvt.background: #0e0e0e
351	URxvt.foreground: #4ad5e1	354	URxvt.foreground: #4ad5e1
…		…
362	URxvt.color6: #73f7ff	365	URxvt.color6: #73f7ff
363	URxvt.color14: #73f7ff	366	URxvt.color14: #73f7ff
364	URxvt.color7: #e1dddd	367	URxvt.color7: #e1dddd
365	URxvt.color15: #e1dddd	368	URxvt.color15: #e1dddd
366		369
		370	They have been described (not by me) as "pretty girly".
		371
367	Why do some characters look so much different than others?	372	Why do some characters look so much different than others?
368	See next entry.	373	See next entry.
369		374
370	How does rxvt-unicode choose fonts?	375	How does rxvt-unicode choose fonts?
371	Most fonts do not contain the full range of Unicode, which is fine.	376	Most fonts do not contain the full range of Unicode, which is fine.
…		…
381	the font that the characters it claims to contain indeed look correct.	386	the font that the characters it claims to contain indeed look correct.
382		387
383	In that case, select a font of your taste and add it to the font list,	388	In that case, select a font of your taste and add it to the font list,
384	e.g.:	389	e.g.:
385		390
386	rxvt -fn basefont,font2,font3...	391	urxvt -fn basefont,font2,font3...
387		392
388	When rxvt-unicode sees a character, it will first look at the base font.	393	When rxvt-unicode sees a character, it will first look at the base font.
389	If the base font does not contain the character, it will go to the next	394	If the base font does not contain the character, it will go to the next
390	font, and so on. Specifying your own fonts will also speed up this	395	font, and so on. Specifying your own fonts will also speed up this
391	search and use less resources within rxvt-unicode and the X-server.	396	search and use less resources within rxvt-unicode and the X-server.
392		397
393	The only limitation is that none of the fonts may be larger than the	398	The only limitation is that none of the fonts may be larger than the
394	base font, as the base font defines the terminal character cell size,	399	base font, as the base font defines the terminal character cell size,
395	which must be the same due to the way terminals work.	400	which must be the same due to the way terminals work.
396		401
		402	Why do some chinese characters look so different than others?
		403	This is because there is a difference between script and language --
		404	rxvt-unicode does not know which language the text that is output is, as
		405	it only knows the unicode character codes. If rxvt-unicode first sees a
		406	japanese/chinese character, it might choose a japanese font for display.
		407	Subsequent japanese characters will use that font. Now, many chinese
		408	characters aren't represented in japanese fonts, so when the first
		409	non-japanese character comes up, rxvt-unicode will look for a chinese
		410	font -- unfortunately at this point, it will still use the japanese font
		411	for chinese characters that are also in the japanese font.
		412
		413	The workaround is easy: just tag a chinese font at the end of your font
		414	list (see the previous question). The key is to view the font list as a
		415	preference list: If you expect more japanese, list a japanese font
		416	first. If you expect more chinese, put a chinese font first.
		417
		418	In the future it might be possible to switch language preferences at
		419	runtime (the internal data structure has no problem with using different
		420	fonts for the same character at the same time, but no interface for this
		421	has been designed yet).
		422
		423	Until then, you might get away with switching fonts at runtime (see "Can
		424	I switch the fonts at runtime?" later in this document).
		425
		426	How can I make mplayer display video correctly?
		427	We are working on it, in the meantime, as a workaround, use something
		428	like:
		429
		430	urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		431
397	Keyboard, Mouse & User Interaction	432	Keyboard, Mouse & User Interaction
398	The new selection selects pieces that are too big, how can I select single words?	433	The new selection selects pieces that are too big, how can I select single words?
399	If you want to select e.g. alphanumeric words, you can use the following	434	If you want to select e.g. alphanumeric words, you can use the following
400	setting:	435	setting:
401		436
…		…
407	To get a selection that is very similar to the old code, try this	442	To get a selection that is very similar to the old code, try this
408	pattern:	443	pattern:
409		444
410	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{\|})]+)	445	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{\|})]+)
411		446
412	Please also note that the LeftClick Shift-LeftClik combination also	447	Please also note that the LeftClick Shift-LeftClick combination also
413	selects words like the old code.	448	selects words like the old code.
414		449
415	I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?	450	I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
416	You can disable the perl extension completely by setting the	451	You can disable the perl extension completely by setting the
417	perl-ext-common resource to the empty string, which also keeps	452	perl-ext-common resource to the empty string, which also keeps
418	rxvt-unicode from initialising perl, saving memory.	453	rxvt-unicode from initialising perl, saving memory.
419		454
420	If you only want to disable specific features, you first have to	455	If you only want to disable specific features, you first have to
421	identify which perl extension is responsible. For this, read the section	456	identify which perl extension is responsible. For this, read the section
422	PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For example, to	457	PREPACKAGED EXTENSIONS in the urxvtperl(3) manpage. For example, to
423	disable the selection-popup and option-popup, specify this	458	disable the selection-popup and option-popup, specify this
424	perl-ext-common resource:	459	perl-ext-common resource:
425		460
426	URxvt.perl-ext-common: default,-selection-popup,-option-popup	461	URxvt.perl-ext-common: default,-selection-popup,-option-popup
427		462
…		…
440	circumstances, it will move your cursor around when you click into the	475	circumstances, it will move your cursor around when you click into the
441	line that contains it. It tries hard not to do this at the wrong moment,	476	line that contains it. It tries hard not to do this at the wrong moment,
442	but when running a program that doesn't parse cursor movements or in	477	but when running a program that doesn't parse cursor movements or in
443	some cases during rlogin sessions, it fails to detect this properly.	478	some cases during rlogin sessions, it fails to detect this properly.
444		479
445	You can permamently switch this feature off by disabling the "readline"	480	You can permanently switch this feature off by disabling the "readline"
446	extension:	481	extension:
447		482
448	URxvt.perl-ext-common: default,-readline	483	URxvt.perl-ext-common: default,-readline
449		484
450	My numerical keypad acts weird and generates differing output?	485	My numerical keypad acts weird and generates differing output?
451	Some Debian GNUL/Linux users seem to have this problem, although no	486	Some Debian GNUL/Linux users seem to have this problem, although no
452	specific details were reported so far. It is possible that this is	487	specific details were reported so far. It is possible that this is
453	caused by the wrong "TERM" setting, although the details of wether and	488	caused by the wrong "TERM" setting, although the details of whether and
454	how this can happen are unknown, as "TERM=rxvt" should offer a	489	how this can happen are unknown, as "TERM=rxvt" should offer a
455	compatible keymap. See the answer to the previous question, and please	490	compatible keymap. See the answer to the previous question, and please
456	report if that helped.	491	report if that helped.
457		492
458	My Compose (Multi_key) key is no longer working.	493	My Compose (Multi_key) key is no longer working.
…		…
464	will continue without an input method.	499	will continue without an input method.
465		500
466	In this case either do not specify a preeditStyle or specify more than	501	In this case either do not specify a preeditStyle or specify more than
467	one pre-edit style, such as OverTheSpot,Root,None.	502	one pre-edit style, such as OverTheSpot,Root,None.
468		503
		504	If it still doesn't work, then maybe your input method doesn't support
		505	compose sequences - to fall back to the built-in one, make sure you
		506	don't specify an input method via "-im" or "XMODIFIERS".
		507
469	I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755	508	I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755
470	Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on	509	Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on
471	international keyboards) or simply use ISO 14755 support to your	510	international keyboards) or simply use ISO 14755 support to your
472	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for	511	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for
473	other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet	512	other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
…		…
479	that tcsh may use mouse reporting unless it otherwise specified. A quick	518	that tcsh may use mouse reporting unless it otherwise specified. A quick
480	check is to see if cut/paste works when the Alt or Shift keys are	519	check is to see if cut/paste works when the Alt or Shift keys are
481	depressed.	520	depressed.
482		521
483	What's with the strange Backspace/Delete key behaviour?	522	What's with the strange Backspace/Delete key behaviour?
484	Assuming that the physical Backspace key corresponds to the BackSpace	523	Assuming that the physical Backspace key corresponds to the Backspace
485	keysym (not likely for Linux ... see the following question) there are	524	keysym (not likely for Linux ... see the following question) there are
486	two standard values that can be used for Backspace: "^H" and "^?".	525	two standard values that can be used for Backspace: "^H" and "^?".
487		526
488	Historically, either value is correct, but rxvt-unicode adopts the	527	Historically, either value is correct, but rxvt-unicode adopts the
489	debian policy of using "^?" when unsure, because it's the one only only	528	debian policy of using "^?" when unsure, because it's the one and only
490	correct choice :).	529	correct choice :).
491		530
492	Rxvt-unicode tries to inherit the current stty settings and uses the	531	Rxvt-unicode tries to inherit the current stty settings and uses the
493	value of `erase' to guess the value for backspace. If rxvt-unicode	532	value of `erase' to guess the value for backspace. If rxvt-unicode
494	wasn't started from a terminal (say, from a menu or by remote shell),	533	wasn't started from a terminal (say, from a menu or by remote shell),
…		…
498		537
499	For starting a new rxvt-unicode:	538	For starting a new rxvt-unicode:
500		539
501	# use Backspace = ^H	540	# use Backspace = ^H
502	$ stty erase ^H	541	$ stty erase ^H
503	$ rxvt	542	$ urxvt
504		543
505	# use Backspace = ^?	544	# use Backspace = ^?
506	$ stty erase ^?	545	$ stty erase ^?
507	$ rxvt	546	$ urxvt
508		547
509	Toggle with "ESC [ 36 h" / "ESC [ 36 l".	548	Toggle with "ESC [ 36 h" / "ESC [ 36 l".
510		549
511	For an existing rxvt-unicode:	550	For an existing rxvt-unicode:
512		551
…		…
538	There are some compile-time selections available via configure. Unless	577	There are some compile-time selections available via configure. Unless
539	you have run "configure" with the "--disable-resources" option you can	578	you have run "configure" with the "--disable-resources" option you can
540	use the `keysym' resource to alter the keystrings associated with	579	use the `keysym' resource to alter the keystrings associated with
541	keysyms.	580	keysyms.
542		581
543	Here's an example for a URxvt session started using "rxvt -name URxvt"	582	Here's an example for a URxvt session started using "urxvt -name URxvt"
544		583
545	URxvt.keysym.Home: \033[1~	584	URxvt.keysym.Home: \033[1~
546	URxvt.keysym.End: \033[4~	585	URxvt.keysym.End: \033[4~
547	URxvt.keysym.C-apostrophe: \033<C-'>	586	URxvt.keysym.C-apostrophe: \033<C-'>
548	URxvt.keysym.C-slash: \033<C-/>	587	URxvt.keysym.C-slash: \033<C-/>
…		…
576	Rather than have rxvt-unicode try to accommodate all the various	615	Rather than have rxvt-unicode try to accommodate all the various
577	possible keyboard mappings, it is better to use `xmodmap' to remap the	616	possible keyboard mappings, it is better to use `xmodmap' to remap the
578	keys as required for your particular machine.	617	keys as required for your particular machine.
579		618
580	Terminal Configuration	619	Terminal Configuration
		620	Can I see a typical configuration?
		621	The default configuration tries to be xterm-like, which I don't like
		622	that much, but it's least surprise to regular users.
		623
		624	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		625	time into customising your terminal. To get you started, here is the
		626	author's .Xdefaults entries, with comments on what they do. It's
		627	certainly not typical, but what's typical...
		628
		629	URxvt.cutchars: "()*,<>[]{}\|'
		630	URxvt.print-pipe: cat >/tmp/xxx
		631
		632	These are just for testing stuff.
		633
		634	URxvt.imLocale: ja_JP.UTF-8
		635	URxvt.preeditType: OnTheSpot,None
		636
		637	This tells rxvt-unicode to use a special locale when communicating with
		638	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		639	type, which requires the "xim-onthespot" perl extension but rewards me
		640	with correct-looking fonts.
		641
		642	URxvt.perl-lib: /root/lib/urxvt
		643	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		644	URxvt.selection.pattern-0: ( at .*? line \\d+)
		645	URxvt.selection.pattern-1: ^(/[^:]+):\
		646	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		647	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		648
		649	This is my perl configuration. The first two set the perl library
		650	directory and also tells urxvt to use a large number of extensions. I
		651	develop for myself mostly, so I actually use most of the extensions I
		652	write.
		653
		654	The selection stuff mainly makes the selection perl-error-message aware
		655	and tells it to convert perl error messages into vi-commands to load the
		656	relevant file and go to the error line number.
		657
		658	URxvt.scrollstyle: plain
		659	URxvt.secondaryScroll: true
		660
		661	As the documentation says: plain is the preferred scrollbar for the
		662	author. The "secondaryScroll" configures urxvt to scroll in full-screen
		663	apps, like screen, so lines scrolled out of screen end up in urxvt's
		664	scrollback buffer.
		665
		666	URxvt.background: #000000
		667	URxvt.foreground: gray90
		668	URxvt.color7: gray90
		669	URxvt.colorBD: #ffffff
		670	URxvt.cursorColor: #e0e080
		671	URxvt.throughColor: #8080f0
		672	URxvt.highlightColor: #f0f0f0
		673
		674	Some colours. Not sure which ones are being used or even non-defaults,
		675	but these are in my .Xdefaults. Most notably, they set
		676	foreground/background to light gray/black, and also make sure that the
		677	colour 7 matches the default foreground colour.
		678
		679	URxvt.underlineColor: yellow
		680
		681	Another colour, makes underline lines look different. Sometimes hurts,
		682	but is mostly a nice effect.
		683
		684	URxvt.geometry: 154x36
		685	URxvt.loginShell: false
		686	URxvt.meta: ignore
		687	URxvt.utmpInhibit: true
		688
		689	Uh, well, should be mostly self-explanatory. By specifying some defaults
		690	manually, I can quickly switch them for testing.
		691
		692	URxvt.saveLines: 8192
		693
		694	A large scrollback buffer is essential. Really.
		695
		696	URxvt.mapAlert: true
		697
		698	The only case I use it is for my IRC window, which I like to keep
		699	iconified till people msg me (which beeps).
		700
		701	URxvt.visualBell: true
		702
		703	The audible bell is often annoying, especially when in a crowd.
		704
		705	URxvt.insecure: true
		706
		707	Please don't hack my mutt! Ooops...
		708
		709	URxvt.pastableTabs: false
		710
		711	I once thought this is a great idea.
		712
		713	urxvt.font: 9x15bold,\
		714	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		715	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		716	[codeset=JISX0208]xft:Kochi Gothic, \
		717	xft:Bitstream Vera Sans Mono:autohint=true, \
		718	xft:Code2000:antialias=false
		719	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		720	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		721	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		722
		723	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		724	overwhelmed. A special note: the "9x15bold" mentioned above is actually
		725	the version from XFree-3.3, as XFree-4 replaced it by a totally
		726	different font (different glyphs for ";" and many other harmless
		727	characters), while the second font is actually the "9x15bold" from
		728	XFree4/XOrg. The bold version has less chars than the medium version, so
		729	I use it for rare characters, too. When editing sources with vim, I use
		730	italic for comments and other stuff, which looks quite good with
		731	Bitstream Vera anti-aliased.
		732
		733	Terminus is a quite bad font (many very wrong glyphs), but for most of
		734	my purposes, it works, and gives a different look, as my normal
		735	(Non-bold) font is already bold, and I want to see a difference between
		736	bold and normal fonts.
		737
		738	Please note that I used the "urxvt" instance name and not the "URxvt"
		739	class name. That is because I use different configs for different
		740	purposes, for example, my IRC window is started with "-name IRC", and
		741	uses these defaults:
		742
		743	IRC*title: IRC
		744	IRC*geometry: 87x12+535+542
		745	IRC*saveLines: 0
		746	IRC*mapAlert: true
		747	IRC*font: suxuseuro
		748	IRC*boldFont: suxuseuro
		749	IRC*colorBD: white
		750	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		751	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		752
		753	"Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes.
		754	"suxuseuro" allows me to keep an eye (and actually read) stuff while
		755	keeping a very small window. If somebody pastes something complicated
		756	(e.g. japanese), I temporarily switch to a larger font.
		757
		758	The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
		759	"xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
		760	file for different hosts, for example, on ym main desktop, I use:
		761
		762	URxvt.keysym.C-M-q: command:\033[3;5;5t
		763	URxvt.keysym.C-M-y: command:\033[3;5;606t
		764	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		765	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		766	URxvt.keysym.C-M-p: perl:test
		767
		768	The first for keysym definitions allow me to quickly bring some windows
		769	in the layout I like most. Ion users might start laughing but will stop
		770	immediately when I tell them that I use my own Fvwm2 module for much the
		771	same effect as Ion provides, and I only very rarely use the above key
		772	combinations :->
		773
581	Why doesn't rxvt-unicode read my resources?	774	Why doesn't rxvt-unicode read my resources?
582	Well, why, indeed? It does, in a way very similar to other X	775	Well, why, indeed? It does, in a way very similar to other X
583	applications. Most importantly, this means that if you or your OS loads	776	applications. Most importantly, this means that if you or your OS loads
584	resources into the X display (the right way to do it), rxvt-unicode will	777	resources into the X display (the right way to do it), rxvt-unicode will
585	ignore any resource files in your home directory. It will only read	778	ignore any resource files in your home directory. It will only read
…		…
592	Also consider the form resources have to use:	785	Also consider the form resources have to use:
593		786
594	URxvt.resource: value	787	URxvt.resource: value
595		788
596	If you want to use another form (there are lots of different ways of	789	If you want to use another form (there are lots of different ways of
597	specifying resources), make sure you understand wether and why it works.	790	specifying resources), make sure you understand whether and why it
598	If unsure, use the form above.	791	works. If unsure, use the form above.
599		792
600	When I log-in to another system it tells me about missing terminfo data?	793	When I log-in to another system it tells me about missing terminfo data?
601	The terminal description used by rxvt-unicode is not as widely available	794	The terminal description used by rxvt-unicode is not as widely available
602	as that for xterm, or even rxvt (for which the same problem often	795	as that for xterm, or even rxvt (for which the same problem often
603	arises).	796	arises).
604		797
605	The correct solution for this problem is to install the terminfo, this	798	The correct solution for this problem is to install the terminfo, this
606	can be done like this (with ncurses' infocmp):	799	can be done by simply installing rxvt-unicode on the remote system as
		800	well (in case you have a nice package manager ready), or you can install
		801	the terminfo database manually like this (with ncurses infocmp. works as
		802	user and root):
607		803
608	REMOTE=remotesystem.domain	804	REMOTE=remotesystem.domain
609	infocmp rxvt-unicode \| ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	805	infocmp rxvt-unicode \| ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
610		806
611	... or by installing rxvt-unicode normally on the remote system,	807	One some systems you might need to set $TERMINFO to the full path of
		808	$HOME/.terminfo for this to work.
612		809
613	If you cannot or do not want to do this, then you can simply set	810	If you cannot or do not want to do this, then you can simply set
614	"TERM=rxvt" or even "TERM=xterm", and live with the small number of	811	"TERM=rxvt" or even "TERM=xterm", and live with the small number of
615	problems arising, which includes wrong keymapping, less and different	812	problems arising, which includes wrong keymapping, less and different
616	colours and some refresh errors in fullscreen applications. It's a nice	813	colours and some refresh errors in fullscreen applications. It's a nice
…		…
621	resource to set it:	818	resource to set it:
622		819
623	URxvt.termName: rxvt	820	URxvt.termName: rxvt
624		821
625	If you don't plan to use rxvt (quite common...) you could also replace	822	If you don't plan to use rxvt (quite common...) you could also replace
626	the rxvt terminfo file with the rxvt-unicode one.	823	the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
		824
		825	nano fails with "Error opening terminal: rxvt-unicode"
		826	This exceptionally confusing and useless error message is printed by
		827	nano when it can't find the terminfo database. Nothing is wrong with
		828	your terminal, read the previous answer for a solution.
627		829
628	"tic" outputs some error when compiling the terminfo entry.	830	"tic" outputs some error when compiling the terminfo entry.
629	Most likely it's the empty definition for "enacs=". Just replace it by	831	Most likely it's the empty definition for "enacs=". Just replace it by
630	"enacs=\E[0@" and try again.	832	"enacs=\E[0@" and try again.
631		833
632	"bash"'s readline does not work correctly under rxvt.	834	"bash"'s readline does not work correctly under urxvt.
633	See next entry.	835	See next entry.
634		836
635	I need a termcap file entry.	837	I need a termcap file entry.
636	One reason you might want this is that some distributions or operating	838	One reason you might want this is that some distributions or operating
637	systems still compile some programs using the long-obsoleted termcap	839	systems still compile some programs using the long-obsoleted termcap
638	library (Fedora Core's bash is one example) and rely on a termcap entry	840	library (Fedora Core's bash is one example) and rely on a termcap entry
639	for "rxvt-unicode".	841	for "rxvt-unicode".
640		842
641	You could use rxvt's termcap entry with resonable results in many cases.	843	You could use rxvt's termcap entry with reasonable results in many
642	You can also create a termcap entry by using terminfo's infocmp program	844	cases. You can also create a termcap entry by using terminfo's infocmp
643	like this:	845	program like this:
644		846
645	infocmp -C rxvt-unicode	847	infocmp -C rxvt-unicode
646		848
647	Or you could use this termcap entry, generated by the command above:	849	Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap,
648		850	generated by the command above.
649	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
650	:am:bw:eo:km:mi:ms:xn:xo:\
651	:co#80:it#8:li#24:lm#0:\
652	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
653	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
654	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
655	:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
656	:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
657	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
658	:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
659	:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
660	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
661	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
662	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
663	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
664	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
665	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
666	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
667	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
668	:vs=\E[?25h:
669		851
670	Why does "ls" no longer have coloured output?	852	Why does "ls" no longer have coloured output?
671	The "ls" in the GNU coreutils unfortunately doesn't use terminfo to	853	The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
672	decide wether a terminal has colour, but uses it's own configuration	854	decide whether a terminal has colour, but uses its own configuration
673	file. Needless to say, "rxvt-unicode" is not in it's default file (among	855	file. Needless to say, "rxvt-unicode" is not in its default file (among
674	with most other terminals supporting colour). Either add:	856	with most other terminals supporting colour). Either add:
675		857
676	TERM rxvt-unicode	858	TERM rxvt-unicode
677		859
678	to "/etc/DIR_COLORS" or simply add:	860	to "/etc/DIR_COLORS" or simply add:
…		…
705	If you encounter strange problems like typing an accented character but	887	If you encounter strange problems like typing an accented character but
706	getting two unrelated other characters or similar, or if program output	888	getting two unrelated other characters or similar, or if program output
707	is subtly garbled, then you should check your locale settings.	889	is subtly garbled, then you should check your locale settings.
708		890
709	Rxvt-unicode must be started with the same "LC_CTYPE" setting as the	891	Rxvt-unicode must be started with the same "LC_CTYPE" setting as the
710	programs. Often rxvt-unicode is started in the "C" locale, while the	892	programs running in it. Often rxvt-unicode is started in the "C" locale,
711	login script running within the rxvt-unicode window changes the locale	893	while the login script running within the rxvt-unicode window changes
712	to something else, e.g. "en_GB.UTF-8". Needless to say, this is not	894	the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
713	going to work.	895	is not going to work, and is the most common cause for problems.
714		896
715	The best thing is to fix your startup environment, as you will likely	897	The best thing is to fix your startup environment, as you will likely
716	run into other problems. If nothing works you can try this in your	898	run into other problems. If nothing works you can try this in your
717	.profile.	899	.profile.
718		900
719	printf '\e]701;%s\007' "$LC_CTYPE"	901	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
720		902
721	If this doesn't work, then maybe you use a "LC_CTYPE" specification not	903	If this doesn't work, then maybe you use a "LC_CTYPE" specification not
722	supported on your systems. Some systems have a "locale" command which	904	supported on your systems. Some systems have a "locale" command which
723	displays this (also, "perl -e0" can be used to check locale settings, as	905	displays this (also, "perl -e0" can be used to check locale settings, as
724	it will complain loudly if it cannot set the locale). If it displays	906	it will complain loudly if it cannot set the locale). If it displays
…		…
743	The reasons is that there exists a perfectly fine mechanism for	925	The reasons is that there exists a perfectly fine mechanism for
744	selecting the encoding, doing I/O and (most important) communicating	926	selecting the encoding, doing I/O and (most important) communicating
745	this to all applications so everybody agrees on character properties	927	this to all applications so everybody agrees on character properties
746	such as width and code number. This mechanism is the locale.	928	such as width and code number. This mechanism is the locale.
747	Applications not using that info will have problems (for example,	929	Applications not using that info will have problems (for example,
748	"xterm" gets the width of characters wrong as it uses it's own,	930	"xterm" gets the width of characters wrong as it uses its own,
749	locale-independent table under all locales).	931	locale-independent table under all locales).
750		932
751	Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All	933	Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All
752	programs doing the same (that is, most) will automatically agree in the	934	programs doing the same (that is, most) will automatically agree in the
753	interpretation of characters.	935	interpretation of characters.
…		…
770		952
771	Can I switch locales at runtime?	953	Can I switch locales at runtime?
772	Yes, using an escape sequence. Try something like this, which sets	954	Yes, using an escape sequence. Try something like this, which sets
773	rxvt-unicode's idea of "LC_CTYPE".	955	rxvt-unicode's idea of "LC_CTYPE".
774		956
775	printf '\e]701;%s\007' ja_JP.SJIS	957	printf '\33]701;%s\007' ja_JP.SJIS
776		958
777	See also the previous answer.	959	See also the previous answer.
778		960
779	Sometimes this capability is rather handy when you want to work in one	961	Sometimes this capability is rather handy when you want to work in one
780	locale (e.g. "de_DE.UTF-8") but some programs don't support it (e.g.	962	locale (e.g. "de_DE.UTF-8") but some programs don't support it (e.g.
781	UTF-8). For example, I use this script to start "xjdic", which first	963	UTF-8). For example, I use this script to start "xjdic", which first
782	switches to a locale supported by xjdic and back later:	964	switches to a locale supported by xjdic and back later:
783		965
784	printf '\e]701;%s\007' ja_JP.SJIS	966	printf '\33]701;%s\007' ja_JP.SJIS
785	xjdic -js	967	xjdic -js
786	printf '\e]701;%s\007' de_DE.UTF-8	968	printf '\33]701;%s\007' de_DE.UTF-8
787		969
788	You can also use xterm's "luit" program, which usually works fine,	970	You can also use xterm's "luit" program, which usually works fine,
789	except for some locales where character width differs between program-	971	except for some locales where character width differs between program-
790	and rxvt-unicode-locales.	972	and rxvt-unicode-locales.
791		973
		974	I have problems getting my input method working.
		975	Try a search engine, as this is slightly different for every input
		976	method server.
		977
		978	Here is a checklist:
		979
		980	- Make sure your locale and the imLocale are supported on your OS.
		981	Try "locale -a" or check the documentation for your OS.
		982
		983	- Make sure your locale or imLocale matches a locale supported by your
		984	XIM.
		985	For example, kinput2 does not support UTF-8 locales, you should use
		986	"ja_JP.EUC-JP" or equivalent.
		987
		988	- Make sure your XIM server is actually running.
		989	- Make sure the "XMODIFIERS" environment variable is set correctly when
		990	starting rxvt-unicode.
		991	When you want to use e.g. kinput2, it must be set to "@im=kinput2".
		992	For scim, use "@im=SCIM". You can see what input method servers are
		993	running with this command:
		994
		995	xprop -root XIM_SERVERS
		996
		997
		998
792	My input method wants <some encoding> but I want UTF-8, what can I do?	999	My input method wants <some encoding> but I want UTF-8, what can I do?
793	You can specify separate locales for the input method and the rest of	1000	You can specify separate locales for the input method and the rest of
794	the terminal, using the resource "imlocale":	1001	the terminal, using the resource "imlocale":
795		1002
796	URxvt.imlocale: ja_JP.EUC-JP	1003	URxvt.imlocale: ja_JP.EUC-JP
797		1004
798	Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still	1005	Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still
799	use your input method. Please note, however, that you will not be able	1006	use your input method. Please note, however, that, depending on your
800	to input characters outside "EUC-JP" in a normal way then, as your input	1007	Xlib version, you may not be able to input characters outside "EUC-JP"
801	method limits you.	1008	in a normal way then, as your input method limits you.
802		1009
803	Rxvt-unicode crashes when the X Input Method changes or exits.	1010	Rxvt-unicode crashes when the X Input Method changes or exits.
804	Unfortunately, this is unavoidable, as the XIM protocol is racy by	1011	Unfortunately, this is unavoidable, as the XIM protocol is racy by
805	design. Applications can avoid some crashes at the expense of memory	1012	design. Applications can avoid some crashes at the expense of memory
806	leaks, and Input Methods can avoid some crashes by careful ordering at	1013	leaks, and Input Methods can avoid some crashes by careful ordering at
…		…
827	that might encounter the same issue.	1034	that might encounter the same issue.
828		1035
829	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?	1036	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
830	You should build one binary with the default options. configure now	1037	You should build one binary with the default options. configure now
831	enables most useful options, and the trend goes to making them	1038	enables most useful options, and the trend goes to making them
832	runtime-switchable, too, so there is usually no drawback to enbaling	1039	runtime-switchable, too, so there is usually no drawback to enabling
833	them, except higher disk and possibly memory usage. The perl interpreter	1040	them, except higher disk and possibly memory usage. The perl interpreter
834	should be enabled, as important functionality (menus, selection, likely	1041	should be enabled, as important functionality (menus, selection, likely
835	more in the future) depends on it.	1042	more in the future) depends on it.
836		1043
837	You should not overwrite the "perl-ext-common" snd "perl-ext" resources	1044	You should not overwrite the "perl-ext-common" and "perl-ext" resources
838	system-wide (except maybe with "defaults"). This will result in useful	1045	system-wide (except maybe with "defaults"). This will result in useful
839	behaviour. If your distribution aims at low memory, add an empty	1046	behaviour. If your distribution aims at low memory, add an empty
840	"perl-ext-common" resource to the app-defaults file. This will keep the	1047	"perl-ext-common" resource to the app-defaults file. This will keep the
841	perl interpreter disabled until the user enables it.	1048	perl interpreter disabled until the user enables it.
842		1049
…		…
859	This forking is done as the very first within main(), which is very	1066	This forking is done as the very first within main(), which is very
860	early and reduces possible bugs to initialisation code run before	1067	early and reduces possible bugs to initialisation code run before
861	main(), or things like the dynamic loader of your system, which should	1068	main(), or things like the dynamic loader of your system, which should
862	result in very little risk.	1069	result in very little risk.
863		1070
864	On Solaris 9, many line-drawing characters are too wide.
865	Seems to be a known bug, read
866	<http://nixdoc.net/files/forum/about34198.html>. Some people use the
867	following ugly workaround to get non-double-wide-characters working:
868
869	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
870
871	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.
872	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
873	your compile environment, or an implementation that implements it,	1073	your compile environment, or an implementation that implements it,
874	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
875	wchar_t is represented as unicode.	1075	wchar_t is represented as unicode.
876		1076
877	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
878	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
879	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.
880		1080
881	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
882	"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).
883		1083
884	"__STDC_ISO_10646__" is the only sane way to support multi-language apps	1084	"__STDC_ISO_10646__" is the only sane way to support multi-language apps
885	in an OS, as using a locale-dependent (and non-standardized)	1085	in an OS, as using a locale-dependent (and non-standardized)
886	representation of wchar_t makes it impossible to convert between wchar_t	1086	representation of wchar_t makes it impossible to convert between wchar_t
887	(as used by X11 and your applications) and any other encoding without	1087	(as used by X11 and your applications) and any other encoding without
…		…
897		1097
898	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
899	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
900	complete replacements for them :)	1100	complete replacements for them :)
901		1101
902	I use Solaris 9 and it doesn't compile/work/etc.
903	Try the diff in doc/solaris9.patch as a base. It fixes the worst
904	problems with "wcwidth" and a compile problem.
905
906	How can I use rxvt-unicode under cygwin?	1102	How can I use rxvt-unicode under cygwin?
907	rxvt-unicode should compile and run out of the box on cygwin, using the	1103	rxvt-unicode should compile and run out of the box on cygwin, using the
908	X11 libraries that come with cygwin. libW11 emulation is no longer	1104	X11 libraries that come with cygwin. libW11 emulation is no longer
909	supported (and makes no sense, either, as it only supported a single	1105	supported (and makes no sense, either, as it only supported a single
910	font). I recommend starting the X-server in "-multiwindow" or	1106	font). I recommend starting the X-server in "-multiwindow" or
…		…
913		1109
914	At the time of this writing, cygwin didn't seem to support any	1110	At the time of this writing, cygwin didn't seem to support any
915	multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are	1111	multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
916	likely limited to 8-bit encodings.	1112	likely limited to 8-bit encodings.
917		1113
		1114	Character widths are not correct.
		1115	urxvt uses the system wcwidth function to know the information about the
		1116	width of characters, so on systems with incorrect locale data you will
		1117	likely get bad results. Two notorious examples are Solaris 9, where
		1118	single-width characters like U+2514 are reported as double-width, and
		1119	Darwin 8, where combining chars are reported having width 1.
		1120
		1121	The solution is to upgrade your system or switch to a better one. A
		1122	possibly working workaround is to use a wcwidth implementation like
		1123
		1124	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
		1125

Diff Legend

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

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.39 by root, Tue Jan 31 20:52:19 2006 UTC vs. Revision 1.59 by sf-exg, Sat Jul 24 14:20:48 2010 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.39 by root, Tue Jan 31 20:52:19 2006 UTC vs.
Revision 1.59 by sf-exg, Sat Jul 24 14:20:48 2010 UTC