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

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.40 by root, Tue Jan 31 20:57:29 2006 UTC vs.
Revision 1.56 by root, Tue Nov 4 23:00:43 2008 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
		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.
7		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:
42		53
43	How can I start urxvtd in a race-free way?	54	How can I start urxvtd in a race-free way?
44	Try "urxvtd -f -o", which tells urxvtd 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
		58	How can I start urxvtd automatically when I run urxvtc?
		59	If you want to start urxvtd automatically whenever you run urxvtc and
		60	the daemon isn't running yet, use this script:
		61
		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
47	How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.	74	How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
48	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can	75	The original rxvt and rxvt-unicode always export the variable
49	check and see if that is set. Note that several programs, JED, slrn,	76	"COLORTERM", so you can check and see if that is set. Note that several
50	Midnight Commander automatically check this variable to decide whether	77	programs, JED, slrn, Midnight Commander automatically check this
51	or not to use color.	78	variable to decide whether or not to use color.
52		79
53	How do I set the correct, full IP address for the DISPLAY variable?	80	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	81	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	82	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	83	snippets to correctly set the display. If your version of rxvt-unicode
…		…
74	fi	101	fi
75	fi	102	fi
76		103
77	How do I compile the manual pages on my own?	104	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,	105	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	106	one that comes with pod2man, pod2text and pod2xhtml (from Pod::Xhtml).
80	subdirectory and enter "make alldoc".	107	Then go to the doc subdirectory and enter "make alldoc".
81		108
82	Isn't rxvt-unicode supposed to be small? Don't all those features bloat?	109	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	110	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	111	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	112	that the urxvt binary is larger (due to some encoding tables always
…		…
90		117
91	text data bss drs rss filename	118	text data bss drs rss filename
92	98398 1664 24 15695 1824 rxvt --disable-everything	119	98398 1664 24 15695 1824 rxvt --disable-everything
93	188985 9048 66616 18222 1788 urxvt --disable-everything	120	188985 9048 66616 18222 1788 urxvt --disable-everything
94		121
95	When you "--enable-everything" (which _is_ unfair, as this involves xft	122	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	123	and full locale/XIM support which are quite bloaty inside libX11 and my
97	libc), the two diverge, but not unreasnobaly so.	124	libc), the two diverge, but not unreasonably so.
98		125
99	text data bss drs rss filename	126	text data bss drs rss filename
100	163431 2152 24 20123 2060 rxvt --enable-everything	127	163431 2152 24 20123 2060 rxvt --enable-everything
101	1035683 49680 66648 29096 3680 urxvt --enable-everything	128	1035683 49680 66648 29096 3680 urxvt --enable-everything
102		129
…		…
144		171
145	And here is rxvt-unicode:	172	And here is rxvt-unicode:
146		173
147	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	174	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
148	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)	175	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
149	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)	176	libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
150	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)	177	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
151	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	178	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
152		179
153	No large bloated libraries (of course, none were linked in statically),	180	No large bloated libraries (of course, none were linked in statically),
154	except maybe libX11 :)	181	except maybe libX11 :)
155		182
156	Rendering, Font & Look and Feel Issues	183	Rendering, Font & Look and Feel Issues
157	I can't get transparency working, what am I doing wrong?	184	I can't get transparency working, what am I doing wrong?
158	First of all, transparency isn't officially supported in rxvt-unicode,	185	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	186	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	187	if you can't get it working consider it a rite of passage: ... and you
161	rite of passage: ... and you failed.	188	failed.
162		189
163	Here are four ways to get transparency. Do read the manpage and option	190	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!	191	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
165		192
166	1. Use inheritPixmap:	193	1. Use transparent mode:
167		194
168	Esetroot wallpaper.jpg	195	Esetroot wallpaper.jpg
169	urxvt -ip -tint red -sh 40	196	urxvt -tr -tint red -sh 40
170		197
171	That works. If you think it doesn't, you lack transparency and tinting	198	That works. If you think it doesn't, you lack transparency and tinting
172	support, or you are unable to read.	199	support, or you are unable to read.
173		200
174	2. Use a simple pixmap and emulate pseudo-transparency. This enables you	201	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	202	to use effects other than tinting and shading: Just shade/tint/whatever
176	your picture with gimp or any other tool:	203	your picture with gimp or any other tool:
177		204
178	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	205	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
179	urxvt -pixmap background.xpm -pe automove-background	206	urxvt -pixmap "background.jpg;:root"
180		207
181	That works. If you think it doesn't, you lack XPM and Perl support, or	208	That works. If you think it doesn't, you lack AfterImage support, or you
182	you are unable to read.	209	are unable to read.
183		210
184	3. Use an ARGB visual:	211	3. Use an ARGB visual:
185		212
186	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc	213	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
187		214
188	This requires XFT support, and the support of your X-server. If that	215	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	216	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	217	there yet, no matter what they claim. Rxvt-Unicode contains the
191	neccessary bugfixes and workarounds for Xft and Xlib to make it work,	218	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.	219	that doesn't mean that your WM has the required kludges in place.
193		220
194	4. Use xcompmgr and let it do the job:	221	4. Use xcompmgr and let it do the job:
195		222
196	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \	223	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
197	-set _NET_WM_WINDOW_OPACITY 0xc0000000	224	-set _NET_WM_WINDOW_OPACITY 0xc0000000
198		225
199	Then click on a window you want to make transparent. Replace 0xc0000000	226	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	227	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.	228	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		229
227	Why does rxvt-unicode sometimes leave pixel droppings?	230	Why does rxvt-unicode sometimes leave pixel droppings?
228	Most fonts were not designed for terminal use, which means that	231	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	232	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	233	use might contain some characters that are simply too wide. Rxvt-unicode
…		…
236	however: Xft fonts often draw glyphs larger than their acclaimed	239	however: Xft fonts often draw glyphs larger than their acclaimed
237	bounding box, and rxvt-unicode has no way of detecting this (the correct	240	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	241	way is to ask for the character bounding box, which unfortunately is
239	wrong in these cases).	242	wrong in these cases).
240		243
241	It's not clear (to me at least), wether this is a bug in Xft, freetype,	244	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	245	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	246	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.	247	work, you might be forced to use a different font.
245		248
246	All of this is not a problem when using X11 core fonts, as their	249	All of this is not a problem when using X11 core fonts, as their
…		…
268		271
269	Can I switch the fonts at runtime?	272	Can I switch the fonts at runtime?
270	Yes, using an escape sequence. Try something like this, which has the	273	Yes, using an escape sequence. Try something like this, which has the
271	same effect as using the "-fn" switch, and takes effect immediately:	274	same effect as using the "-fn" switch, and takes effect immediately:
272		275
273	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	276	printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
274		277
275	This is useful if you e.g. work primarily with japanese (and prefer a	278	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	279	japanese font), but you have to switch to chinese temporarily, where
277	japanese fonts would only be in your way.	280	japanese fonts would only be in your way.
278		281
279	You can think of this as a kind of manual ISO-2022 switching.	282	You can think of this as a kind of manual ISO-2022 switching.
280		283
281	Why do italic characters look as if clipped?	284	Why do italic characters look as if clipped?
282	Many fonts have difficulties with italic characters and hinting. For	285	Many fonts have difficulties with italic characters and hinting. For
283	example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans	286	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	287	Mono" completely fails in its italic face. A workaround might be to
285	enable freetype autohinting, i.e. like this:	288	enable freetype autohinting, i.e. like this:
286		289
287	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	290	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
288	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	291	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
289		292
…		…
293	antialiasing (by appending ":antialias=false"), which saves lots of	296	antialiasing (by appending ":antialias=false"), which saves lots of
294	memory and also speeds up rendering considerably.	297	memory and also speeds up rendering considerably.
295		298
296	Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	299	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	300	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	301	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	302	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	303	antialiasing disabled for most of them, because the author thinks they
301	look best that way.	304	look best that way.
302		305
303	If you want antialiasing, you have to specify the fonts manually.	306	If you want antialiasing, you have to specify the fonts manually.
304		307
305	What's with this bold/blink stuff?	308	What's with this bold/blink stuff?
306	If no bold colour is set via "colorBD:", bold will invert text using the	309	If no bold colour is set via "colorBD:", bold will invert text using the
307	standard foreground colour.	310	standard foreground colour.
308		311
309	For the standard background colour, blinking will actually make the text	312	For the standard background colour, blinking will actually make the text
310	blink when compiled with "--enable-blinking". with standard colours.	313	blink when compiled with "--enable-text-blink". Without
311	Without "--enable-blinking", the blink attribute will be ignored.	314	"--enable-text-blink", the blink attribute will be ignored.
312		315
313	On ANSI colours, bold/blink attributes are used to set high-intensity	316	On ANSI colours, bold/blink attributes are used to set high-intensity
314	foreground/background colors.	317	foreground/background colors.
315		318
316	color0-7 are the low-intensity colors.	319	color0-7 are the low-intensity colors.
…		…
340	URxvt.color12: #0000FF	343	URxvt.color12: #0000FF
341	URxvt.color13: #FF00FF	344	URxvt.color13: #FF00FF
342	URxvt.color14: #00FFFF	345	URxvt.color14: #00FFFF
343	URxvt.color15: #FFFFFF	346	URxvt.color15: #FFFFFF
344		347
345	And here is a more complete set of non-standard colors described (not by	348	And here is a more complete set of non-standard colors.
346	me) as "pretty girly".
347		349
348	URxvt.cursorColor: #dc74d1	350	URxvt.cursorColor: #dc74d1
349	URxvt.pointerColor: #dc74d1	351	URxvt.pointerColor: #dc74d1
350	URxvt.background: #0e0e0e	352	URxvt.background: #0e0e0e
351	URxvt.foreground: #4ad5e1	353	URxvt.foreground: #4ad5e1
…		…
362	URxvt.color6: #73f7ff	364	URxvt.color6: #73f7ff
363	URxvt.color14: #73f7ff	365	URxvt.color14: #73f7ff
364	URxvt.color7: #e1dddd	366	URxvt.color7: #e1dddd
365	URxvt.color15: #e1dddd	367	URxvt.color15: #e1dddd
366		368
		369	They have been described (not by me) as "pretty girly".
		370
367	Why do some characters look so much different than others?	371	Why do some characters look so much different than others?
368	See next entry.	372	See next entry.
369		373
370	How does rxvt-unicode choose fonts?	374	How does rxvt-unicode choose fonts?
371	Most fonts do not contain the full range of Unicode, which is fine.	375	Most fonts do not contain the full range of Unicode, which is fine.
…		…
382		386
383	In that case, select a font of your taste and add it to the font list,	387	In that case, select a font of your taste and add it to the font list,
384	e.g.:	388	e.g.:
385		389
386	urxvt -fn basefont,font2,font3...	390	urxvt -fn basefont,font2,font3...
387		391
388	When rxvt-unicode sees a character, it will first look at the base font.	392	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	393	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	394	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.	395	search and use less resources within rxvt-unicode and the X-server.
392		396
393	The only limitation is that none of the fonts may be larger than the	397	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,	398	base font, as the base font defines the terminal character cell size,
395	which must be the same due to the way terminals work.	399	which must be the same due to the way terminals work.
396		400
		401	Why do some chinese characters look so different than others?
		402	This is because there is a difference between script and language --
		403	rxvt-unicode does not know which language the text that is output is, as
		404	it only knows the unicode character codes. If rxvt-unicode first sees a
		405	japanese/chinese character, it might choose a japanese font for display.
		406	Subsequent japanese characters will use that font. Now, many chinese
		407	characters aren't represented in japanese fonts, so when the first
		408	non-japanese character comes up, rxvt-unicode will look for a chinese
		409	font -- unfortunately at this point, it will still use the japanese font
		410	for chinese characters that are also in the japanese font.
		411
		412	The workaround is easy: just tag a chinese font at the end of your font
		413	list (see the previous question). The key is to view the font list as a
		414	preference list: If you expect more japanese, list a japanese font
		415	first. If you expect more chinese, put a chinese font first.
		416
		417	In the future it might be possible to switch language preferences at
		418	runtime (the internal data structure has no problem with using different
		419	fonts for the same character at the same time, but no interface for this
		420	has been designed yet).
		421
		422	Until then, you might get away with switching fonts at runtime (see "Can
		423	I switch the fonts at runtime?" later in this document).
		424
		425	How can I make mplayer display video correctly?
		426	We are working on it, in the meantime, as a workaround, use something
		427	like:
		428
		429	urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		430
397	Keyboard, Mouse & User Interaction	431	Keyboard, Mouse & User Interaction
398	The new selection selects pieces that are too big, how can I select single words?	432	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	433	If you want to select e.g. alphanumeric words, you can use the following
400	setting:	434	setting:
401		435
…		…
407	To get a selection that is very similar to the old code, try this	441	To get a selection that is very similar to the old code, try this
408	pattern:	442	pattern:
409		443
410	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{\|})]+)	444	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{\|})]+)
411		445
412	Please also note that the LeftClick Shift-LeftClik combination also	446	Please also note that the LeftClick Shift-LeftClick combination also
413	selects words like the old code.	447	selects words like the old code.
414		448
415	I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?	449	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	450	You can disable the perl extension completely by setting the
417	perl-ext-common resource to the empty string, which also keeps	451	perl-ext-common resource to the empty string, which also keeps
…		…
440	circumstances, it will move your cursor around when you click into the	474	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,	475	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	476	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.	477	some cases during rlogin sessions, it fails to detect this properly.
444		478
445	You can permamently switch this feature off by disabling the "readline"	479	You can permanently switch this feature off by disabling the "readline"
446	extension:	480	extension:
447		481
448	URxvt.perl-ext-common: default,-readline	482	URxvt.perl-ext-common: default,-readline
449		483
450	My numerical keypad acts weird and generates differing output?	484	My numerical keypad acts weird and generates differing output?
451	Some Debian GNUL/Linux users seem to have this problem, although no	485	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	486	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	487	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	488	how this can happen are unknown, as "TERM=rxvt" should offer a
455	compatible keymap. See the answer to the previous question, and please	489	compatible keymap. See the answer to the previous question, and please
456	report if that helped.	490	report if that helped.
457		491
458	My Compose (Multi_key) key is no longer working.	492	My Compose (Multi_key) key is no longer working.
…		…
479	that tcsh may use mouse reporting unless it otherwise specified. A quick	513	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	514	check is to see if cut/paste works when the Alt or Shift keys are
481	depressed.	515	depressed.
482		516
483	What's with the strange Backspace/Delete key behaviour?	517	What's with the strange Backspace/Delete key behaviour?
484	Assuming that the physical Backspace key corresponds to the BackSpace	518	Assuming that the physical Backspace key corresponds to the Backspace
485	keysym (not likely for Linux ... see the following question) there are	519	keysym (not likely for Linux ... see the following question) there are
486	two standard values that can be used for Backspace: "^H" and "^?".	520	two standard values that can be used for Backspace: "^H" and "^?".
487		521
488	Historically, either value is correct, but rxvt-unicode adopts the	522	Historically, either value is correct, but rxvt-unicode adopts the
489	debian policy of using "^?" when unsure, because it's the one only only	523	debian policy of using "^?" when unsure, because it's the one and only
490	correct choice :).	524	correct choice :).
491		525
492	Rxvt-unicode tries to inherit the current stty settings and uses the	526	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	527	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),	528	wasn't started from a terminal (say, from a menu or by remote shell),
…		…
576	Rather than have rxvt-unicode try to accommodate all the various	610	Rather than have rxvt-unicode try to accommodate all the various
577	possible keyboard mappings, it is better to use `xmodmap' to remap the	611	possible keyboard mappings, it is better to use `xmodmap' to remap the
578	keys as required for your particular machine.	612	keys as required for your particular machine.
579		613
580	Terminal Configuration	614	Terminal Configuration
		615	Can I see a typical configuration?
		616	The default configuration tries to be xterm-like, which I don't like
		617	that much, but it's least surprise to regular users.
		618
		619	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		620	time into customising your terminal. To get you started, here is the
		621	author's .Xdefaults entries, with comments on what they do. It's
		622	certainly not typical, but what's typical...
		623
		624	URxvt.cutchars: "()*,<>[]{}\|'
		625	URxvt.print-pipe: cat >/tmp/xxx
		626
		627	These are just for testing stuff.
		628
		629	URxvt.imLocale: ja_JP.UTF-8
		630	URxvt.preeditType: OnTheSpot,None
		631
		632	This tells rxvt-unicode to use a special locale when communicating with
		633	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		634	type, which requires the "xim-onthespot" perl extension but rewards me
		635	with correct-looking fonts.
		636
		637	URxvt.perl-lib: /root/lib/urxvt
		638	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		639	URxvt.selection.pattern-0: ( at .*? line \\d+)
		640	URxvt.selection.pattern-1: ^(/[^:]+):\
		641	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		642	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		643
		644	This is my perl configuration. The first two set the perl library
		645	directory and also tells urxvt to use a large number of extensions. I
		646	develop for myself mostly, so I actually use most of the extensions I
		647	write.
		648
		649	The selection stuff mainly makes the selection perl-error-message aware
		650	and tells it to convert perl error messages into vi-commands to load the
		651	relevant file and go tot he error line number.
		652
		653	URxvt.scrollstyle: plain
		654	URxvt.secondaryScroll: true
		655
		656	As the documentation says: plain is the preferred scrollbar for the
		657	author. The "secondaryScroll" configures urxvt to scroll in full-screen
		658	apps, like screen, so lines scrolled out of screen end up in urxvt's
		659	scrollback buffer.
		660
		661	URxvt.background: #000000
		662	URxvt.foreground: gray90
		663	URxvt.color7: gray90
		664	URxvt.colorBD: #ffffff
		665	URxvt.cursorColor: #e0e080
		666	URxvt.throughColor: #8080f0
		667	URxvt.highlightColor: #f0f0f0
		668
		669	Some colours. Not sure which ones are being used or even non-defaults,
		670	but these are in my .Xdefaults. Most notably, they set
		671	foreground/background to light gray/black, and also make sure that the
		672	colour 7 matches the default foreground colour.
		673
		674	URxvt.underlineColor: yellow
		675
		676	Another colour, makes underline lines look different. Sometimes hurts,
		677	but is mostly a nice effect.
		678
		679	URxvt.geometry: 154x36
		680	URxvt.loginShell: false
		681	URxvt.meta: ignore
		682	URxvt.utmpInhibit: true
		683
		684	Uh, well, should be mostly self-explanatory. By specifying some defaults
		685	manually, I can quickly switch them for testing.
		686
		687	URxvt.saveLines: 8192
		688
		689	A large scrollback buffer is essential. Really.
		690
		691	URxvt.mapAlert: true
		692
		693	The only case I use it is for my IRC window, which I like to keep
		694	iconified till people msg me (which beeps).
		695
		696	URxvt.visualBell: true
		697
		698	The audible bell is often annoying, especially when in a crowd.
		699
		700	URxvt.insecure: true
		701
		702	Please don't hack my mutt! Ooops...
		703
		704	URxvt.pastableTabs: false
		705
		706	I once thought this is a great idea.
		707
		708	urxvt.font: 9x15bold,\
		709	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		710	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		711	[codeset=JISX0208]xft:Kochi Gothic, \
		712	xft:Bitstream Vera Sans Mono:autohint=true, \
		713	xft:Code2000:antialias=false
		714	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		715	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		716	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		717
		718	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		719	overwhelmed. A special note: the "9x15bold" mentioned above is actually
		720	the version from XFree-3.3, as XFree-4 replaced it by a totally
		721	different font (different glyphs for ";" and many other harmless
		722	characters), while the second font is actually the "9x15bold" from
		723	XFree4/XOrg. The bold version has less chars than the medium version, so
		724	I use it for rare characters, too. When editing sources with vim, I use
		725	italic for comments and other stuff, which looks quite good with
		726	Bitstream Vera anti-aliased.
		727
		728	Terminus is a quite bad font (many very wrong glyphs), but for most of
		729	my purposes, it works, and gives a different look, as my normal
		730	(Non-bold) font is already bold, and I want to see a difference between
		731	bold and normal fonts.
		732
		733	Please note that I used the "urxvt" instance name and not the "URxvt"
		734	class name. Thats because I use different configs for different
		735	purposes, for example, my IRC window is started with "-name IRC", and
		736	uses these defaults:
		737
		738	IRC*title: IRC
		739	IRC*geometry: 87x12+535+542
		740	IRC*saveLines: 0
		741	IRC*mapAlert: true
		742	IRC*font: suxuseuro
		743	IRC*boldFont: suxuseuro
		744	IRC*colorBD: white
		745	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		746	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		747
		748	"Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes.
		749	"suxuseuro" allows me to keep an eye (and actually read) stuff while
		750	keeping a very small window. If somebody pastes something complicated
		751	(e.g. japanese), I temporarily switch to a larger font.
		752
		753	The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
		754	"xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
		755	file for different hosts, for example, on ym main desktop, I use:
		756
		757	URxvt.keysym.C-M-q: command:\033[3;5;5t
		758	URxvt.keysym.C-M-y: command:\033[3;5;606t
		759	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		760	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		761	URxvt.keysym.C-M-p: perl:test
		762
		763	The first for keysym definitions allow me to quickly bring some windows
		764	in the layout I like most. Ion users might start laughing but will stop
		765	immediately when I tell them that I use my own Fvwm2 module for much the
		766	same effect as Ion provides, and I only very rarely use the above key
		767	combinations :->
		768
581	Why doesn't rxvt-unicode read my resources?	769	Why doesn't rxvt-unicode read my resources?
582	Well, why, indeed? It does, in a way very similar to other X	770	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	771	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	772	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	773	ignore any resource files in your home directory. It will only read
…		…
592	Also consider the form resources have to use:	780	Also consider the form resources have to use:
593		781
594	URxvt.resource: value	782	URxvt.resource: value
595		783
596	If you want to use another form (there are lots of different ways of	784	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.	785	specifying resources), make sure you understand whether and why it
598	If unsure, use the form above.	786	works. If unsure, use the form above.
599		787
600	When I log-in to another system it tells me about missing terminfo data?	788	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	789	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	790	as that for xterm, or even rxvt (for which the same problem often
603	arises).	791	arises).
604		792
605	The correct solution for this problem is to install the terminfo, this	793	The correct solution for this problem is to install the terminfo, this
606	can be done like this (with ncurses' infocmp):	794	can be done like this (with ncurses' infocmp and works as user and
		795	admin):
607		796
608	REMOTE=remotesystem.domain	797	REMOTE=remotesystem.domain
609	infocmp rxvt-unicode \| ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	798	infocmp rxvt-unicode \| ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
610		799
611	... or by installing rxvt-unicode normally on the remote system,	800	... or by installing rxvt-unicode normally on the remote system,
		801
		802	One some systems you might need to set $TERMINFO to the full path of
		803	$HOME/.terminfo for this to work.
612		804
613	If you cannot or do not want to do this, then you can simply set	805	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	806	"TERM=rxvt" or even "TERM=xterm", and live with the small number of
615	problems arising, which includes wrong keymapping, less and different	807	problems arising, which includes wrong keymapping, less and different
616	colours and some refresh errors in fullscreen applications. It's a nice	808	colours and some refresh errors in fullscreen applications. It's a nice
…		…
621	resource to set it:	813	resource to set it:
622		814
623	URxvt.termName: rxvt	815	URxvt.termName: rxvt
624		816
625	If you don't plan to use rxvt (quite common...) you could also replace	817	If you don't plan to use rxvt (quite common...) you could also replace
626	the rxvt terminfo file with the rxvt-unicode one.	818	the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
627		819
628	"tic" outputs some error when compiling the terminfo entry.	820	"tic" outputs some error when compiling the terminfo entry.
629	Most likely it's the empty definition for "enacs=". Just replace it by	821	Most likely it's the empty definition for "enacs=". Just replace it by
630	"enacs=\E[0@" and try again.	822	"enacs=\E[0@" and try again.
631		823
…		…
636	One reason you might want this is that some distributions or operating	828	One reason you might want this is that some distributions or operating
637	systems still compile some programs using the long-obsoleted termcap	829	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	830	library (Fedora Core's bash is one example) and rely on a termcap entry
639	for "rxvt-unicode".	831	for "rxvt-unicode".
640		832
641	You could use rxvt's termcap entry with resonable results in many cases.	833	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	834	cases. You can also create a termcap entry by using terminfo's infocmp
643	like this:	835	program like this:
644		836
645	infocmp -C rxvt-unicode	837	infocmp -C rxvt-unicode
646		838
647	Or you could use this termcap entry, generated by the command above:	839	Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap,
648		840	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		841
670	Why does "ls" no longer have coloured output?	842	Why does "ls" no longer have coloured output?
671	The "ls" in the GNU coreutils unfortunately doesn't use terminfo to	843	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	844	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	845	file. Needless to say, "rxvt-unicode" is not in its default file (among
674	with most other terminals supporting colour). Either add:	846	with most other terminals supporting colour). Either add:
675		847
676	TERM rxvt-unicode	848	TERM rxvt-unicode
677		849
678	to "/etc/DIR_COLORS" or simply add:	850	to "/etc/DIR_COLORS" or simply add:
…		…
705	If you encounter strange problems like typing an accented character but	877	If you encounter strange problems like typing an accented character but
706	getting two unrelated other characters or similar, or if program output	878	getting two unrelated other characters or similar, or if program output
707	is subtly garbled, then you should check your locale settings.	879	is subtly garbled, then you should check your locale settings.
708		880
709	Rxvt-unicode must be started with the same "LC_CTYPE" setting as the	881	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	882	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	883	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	884	the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
713	going to work.	885	is not going to work, and is the most common cause for problems.
714		886
715	The best thing is to fix your startup environment, as you will likely	887	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	888	run into other problems. If nothing works you can try this in your
717	.profile.	889	.profile.
718		890
719	printf '\e]701;%s\007' "$LC_CTYPE"	891	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
720		892
721	If this doesn't work, then maybe you use a "LC_CTYPE" specification not	893	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	894	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	895	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	896	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	915	The reasons is that there exists a perfectly fine mechanism for
744	selecting the encoding, doing I/O and (most important) communicating	916	selecting the encoding, doing I/O and (most important) communicating
745	this to all applications so everybody agrees on character properties	917	this to all applications so everybody agrees on character properties
746	such as width and code number. This mechanism is the locale.	918	such as width and code number. This mechanism is the locale.
747	Applications not using that info will have problems (for example,	919	Applications not using that info will have problems (for example,
748	"xterm" gets the width of characters wrong as it uses it's own,	920	"xterm" gets the width of characters wrong as it uses its own,
749	locale-independent table under all locales).	921	locale-independent table under all locales).
750		922
751	Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All	923	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	924	programs doing the same (that is, most) will automatically agree in the
753	interpretation of characters.	925	interpretation of characters.
…		…
770		942
771	Can I switch locales at runtime?	943	Can I switch locales at runtime?
772	Yes, using an escape sequence. Try something like this, which sets	944	Yes, using an escape sequence. Try something like this, which sets
773	rxvt-unicode's idea of "LC_CTYPE".	945	rxvt-unicode's idea of "LC_CTYPE".
774		946
775	printf '\e]701;%s\007' ja_JP.SJIS	947	printf '\33]701;%s\007' ja_JP.SJIS
776		948
777	See also the previous answer.	949	See also the previous answer.
778		950
779	Sometimes this capability is rather handy when you want to work in one	951	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.	952	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	953	UTF-8). For example, I use this script to start "xjdic", which first
782	switches to a locale supported by xjdic and back later:	954	switches to a locale supported by xjdic and back later:
783		955
784	printf '\e]701;%s\007' ja_JP.SJIS	956	printf '\33]701;%s\007' ja_JP.SJIS
785	xjdic -js	957	xjdic -js
786	printf '\e]701;%s\007' de_DE.UTF-8	958	printf '\33]701;%s\007' de_DE.UTF-8
787		959
788	You can also use xterm's "luit" program, which usually works fine,	960	You can also use xterm's "luit" program, which usually works fine,
789	except for some locales where character width differs between program-	961	except for some locales where character width differs between program-
790	and rxvt-unicode-locales.	962	and rxvt-unicode-locales.
791		963
		964	I have problems getting my input method working.
		965	Try a search engine, as this is slightly different for every input
		966	method server.
		967
		968	Here is a checklist:
		969
		970	- Make sure your locale and the imLocale are supported on your OS.
		971	Try "locale -a" or check the documentation for your OS.
		972
		973	- Make sure your locale or imLocale matches a locale supported by your
		974	XIM.
		975	For example, kinput2 does not support UTF-8 locales, you should use
		976	"ja_JP.EUC-JP" or equivalent.
		977
		978	- Make sure your XIM server is actually running.
		979	- Make sure the "XMODIFIERS" environment variable is set correctly when
		980	starting rxvt-unicode.
		981	When you want to use e.g. kinput2, it must be set to "@im=kinput2".
		982	For scim, use "@im=SCIM". You can see what input method servers are
		983	running with this command:
		984
		985	xprop -root XIM_SERVERS
		986
		987
		988
792	My input method wants <some encoding> but I want UTF-8, what can I do?	989	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	990	You can specify separate locales for the input method and the rest of
794	the terminal, using the resource "imlocale":	991	the terminal, using the resource "imlocale":
795		992
796	URxvt.imlocale: ja_JP.EUC-JP	993	URxvt.imlocale: ja_JP.EUC-JP
797		994
798	Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still	995	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	996	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	997	Xlib version, you may not be able to input characters outside "EUC-JP"
801	method limits you.	998	in a normal way then, as your input method limits you.
802		999
803	Rxvt-unicode crashes when the X Input Method changes or exits.	1000	Rxvt-unicode crashes when the X Input Method changes or exits.
804	Unfortunately, this is unavoidable, as the XIM protocol is racy by	1001	Unfortunately, this is unavoidable, as the XIM protocol is racy by
805	design. Applications can avoid some crashes at the expense of memory	1002	design. Applications can avoid some crashes at the expense of memory
806	leaks, and Input Methods can avoid some crashes by careful ordering at	1003	leaks, and Input Methods can avoid some crashes by careful ordering at
…		…
827	that might encounter the same issue.	1024	that might encounter the same issue.
828		1025
829	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?	1026	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
830	You should build one binary with the default options. configure now	1027	You should build one binary with the default options. configure now
831	enables most useful options, and the trend goes to making them	1028	enables most useful options, and the trend goes to making them
832	runtime-switchable, too, so there is usually no drawback to enbaling	1029	runtime-switchable, too, so there is usually no drawback to enabling
833	them, except higher disk and possibly memory usage. The perl interpreter	1030	them, except higher disk and possibly memory usage. The perl interpreter
834	should be enabled, as important functionality (menus, selection, likely	1031	should be enabled, as important functionality (menus, selection, likely
835	more in the future) depends on it.	1032	more in the future) depends on it.
836		1033
837	You should not overwrite the "perl-ext-common" snd "perl-ext" resources	1034	You should not overwrite the "perl-ext-common" snd "perl-ext" resources
…		…
859	This forking is done as the very first within main(), which is very	1056	This forking is done as the very first within main(), which is very
860	early and reduces possible bugs to initialisation code run before	1057	early and reduces possible bugs to initialisation code run before
861	main(), or things like the dynamic loader of your system, which should	1058	main(), or things like the dynamic loader of your system, which should
862	result in very little risk.	1059	result in very little risk.
863		1060
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.	1061	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	1062	Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
873	your compile environment, or an implementation that implements it,	1063	your compile environment, or an implementation that implements it,
874	wether it defines the symbol or not. "__STDC_ISO_10646__" requires that	1064	whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
875	wchar_t is represented as unicode.	1065	wchar_t is represented as unicode.
876		1066
877	As you might have guessed, FreeBSD does neither define this symobl nor	1067	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	1068	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.	1069	wchar_t. This is, of course, completely fine with respect to standards.
880		1070
881	However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and	1071	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.	1072	"UTF-8" locales under FreeBSD (which all use Unicode as wchar_t).
883		1073
884	"__STDC_ISO_10646__" is the only sane way to support multi-language apps	1074	"__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)	1075	in an OS, as using a locale-dependent (and non-standardized)
886	representation of wchar_t makes it impossible to convert between wchar_t	1076	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	1077	(as used by X11 and your applications) and any other encoding without
…		…
897		1087
898	The rxvt-unicode author insists that the right way to fix this is in the	1088	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	1089	system libraries once and for all, instead of forcing every app to carry
900	complete replacements for them :)	1090	complete replacements for them :)
901		1091
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?	1092	How can I use rxvt-unicode under cygwin?
907	rxvt-unicode should compile and run out of the box on cygwin, using the	1093	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	1094	X11 libraries that come with cygwin. libW11 emulation is no longer
909	supported (and makes no sense, either, as it only supported a single	1095	supported (and makes no sense, either, as it only supported a single
910	font). I recommend starting the X-server in "-multiwindow" or	1096	font). I recommend starting the X-server in "-multiwindow" or
…		…
913		1099
914	At the time of this writing, cygwin didn't seem to support any	1100	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	1101	multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
916	likely limited to 8-bit encodings.	1102	likely limited to 8-bit encodings.
917		1103
		1104	Character widths are not correct.
		1105	urxvt uses the system wcwidth function to know the information about the
		1106	width of characters, so on systems with incorrect locale data you will
		1107	likely get bad results. Two notorious examples are Solaris 9, where
		1108	single-width characters like U+2514 are reported as double-width, and
		1109	Darwin 8, where combining chars are reported having width 1.
		1110
		1111	The solution is to upgrade your system or switch to a better one. A
		1112	possibly working workaround is to use a wcwidth implementation like
		1113
		1114	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
		1115

Diff Legend

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

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.40 by root, Tue Jan 31 20:57:29 2006 UTC vs. Revision 1.56 by root, Tue Nov 4 23:00:43 2008 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.40 by root, Tue Jan 31 20:57:29 2006 UTC vs.
Revision 1.56 by root, Tue Nov 4 23:00:43 2008 UTC