[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.62 by root, Thu Dec 9 10:36:51 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
		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
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
…		…
130	the case of rxvt-unicode this hardly matters, as its portability limits	158	the case of rxvt-unicode this hardly matters, as its portability limits
131	are defined by things like X11, pseudo terminals, locale support and	159	are defined by things like X11, pseudo terminals, locale support and
132	unix domain sockets, which are all less portable than C++ itself.	160	unix domain sockets, which are all less portable than C++ itself.
133		161
134	Regarding the bloat, see the above question: It's easy to write programs	162	Regarding the bloat, see the above question: It's easy to write programs
135	in C that use gobs of memory, an certainly possible to write programs in	163	in C that use gobs of memory, and certainly possible to write programs
136	C++ that don't. C++ also often comes with large libraries, but this is	164	in C++ that don't. C++ also often comes with large libraries, but this
137	not necessarily the case with GCC. Here is what rxvt links against on my	165	is not necessarily the case with GCC. Here is what rxvt links against on
138	system with a minimal config:	166	my system with a minimal config:
139		167
140	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)	168	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
141	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)	169	libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
142	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)	170	libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
143	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	171	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
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
…		…
161	rite of passage: ... and you failed.	189	rite of passage: ... and you 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	urxvt -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. This method requires that the
		201	background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID
		202	property. Compatible programs are Esetroot, hsetroot and feh.
173		203
174	2. Use a simple pixmap and emulate pseudo-transparency. This enables you	204	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	205	to use effects other than tinting and shading: Just shade/tint/whatever
176	your picture with gimp or any other tool:	206	your picture with gimp or any other tool:
177		207
178	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	208	convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
179	urxvt -pixmap background.xpm -pe automove-background	209	urxvt -pixmap "background.jpg;:root"
180		210
181	That works. If you think it doesn't, you lack XPM and Perl support, or	211	That works. If you think it doesn't, you lack libAfterImage or
182	you are unable to read.	212	GDK-PixBuf support, or you are unable to read.
183		213
184	3. Use an ARGB visual:	214	3. Use an ARGB visual:
185		215
186	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc	216	urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
187		217
188	This requires XFT support, and the support of your X-server. If that	218	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	219	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	220	there yet, no matter what they claim. Rxvt-Unicode contains the
191	neccessary bugfixes and workarounds for Xft and Xlib to make it work,	221	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.	222	that doesn't mean that your WM has the required kludges in place.
193		223
194	4. Use xcompmgr and let it do the job:	224	4. Use xcompmgr and let it do the job:
195		225
196	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \	226	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
197	-set _NET_WM_WINDOW_OPACITY 0xc0000000	227	-set _NET_WM_WINDOW_OPACITY 0xc0000000
198		228
199	Then click on a window you want to make transparent. Replace 0xc0000000	229	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	230	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.	231	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		232
227	Why does rxvt-unicode sometimes leave pixel droppings?	233	Why does rxvt-unicode sometimes leave pixel droppings?
228	Most fonts were not designed for terminal use, which means that	234	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	235	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	236	use might contain some characters that are simply too wide. Rxvt-unicode
…		…
236	however: Xft fonts often draw glyphs larger than their acclaimed	242	however: Xft fonts often draw glyphs larger than their acclaimed
237	bounding box, and rxvt-unicode has no way of detecting this (the correct	243	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	244	way is to ask for the character bounding box, which unfortunately is
239	wrong in these cases).	245	wrong in these cases).
240		246
241	It's not clear (to me at least), wether this is a bug in Xft, freetype,	247	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	248	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	249	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.	250	work, you might be forced to use a different font.
245		251
246	All of this is not a problem when using X11 core fonts, as their	252	All of this is not a problem when using X11 core fonts, as their
…		…
268		274
269	Can I switch the fonts at runtime?	275	Can I switch the fonts at runtime?
270	Yes, using an escape sequence. Try something like this, which has the	276	Yes, using an escape sequence. Try something like this, which has the
271	same effect as using the "-fn" switch, and takes effect immediately:	277	same effect as using the "-fn" switch, and takes effect immediately:
272		278
273	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	279	printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
274		280
275	This is useful if you e.g. work primarily with japanese (and prefer a	281	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	282	japanese font), but you have to switch to chinese temporarily, where
277	japanese fonts would only be in your way.	283	japanese fonts would only be in your way.
278		284
279	You can think of this as a kind of manual ISO-2022 switching.	285	You can think of this as a kind of manual ISO-2022 switching.
280		286
281	Why do italic characters look as if clipped?	287	Why do italic characters look as if clipped?
282	Many fonts have difficulties with italic characters and hinting. For	288	Many fonts have difficulties with italic characters and hinting. For
283	example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans	289	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	290	Mono" completely fails in its italic face. A workaround might be to
285	enable freetype autohinting, i.e. like this:	291	enable freetype autohinting, i.e. like this:
286		292
287	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	293	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
288	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	294	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
289		295
…		…
293	antialiasing (by appending ":antialias=false"), which saves lots of	299	antialiasing (by appending ":antialias=false"), which saves lots of
294	memory and also speeds up rendering considerably.	300	memory and also speeds up rendering considerably.
295		301
296	Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	302	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	303	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	304	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	305	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	306	antialiasing disabled for most of them, because the author thinks they
301	look best that way.	307	look best that way.
302		308
303	If you want antialiasing, you have to specify the fonts manually.	309	If you want antialiasing, you have to specify the fonts manually.
304		310
305	What's with this bold/blink stuff?	311	What's with this bold/blink stuff?
306	If no bold colour is set via "colorBD:", bold will invert text using the	312	If no bold colour is set via "colorBD:", bold will invert text using the
307	standard foreground colour.	313	standard foreground colour.
308		314
309	For the standard background colour, blinking will actually make the text	315	For the standard background colour, blinking will actually make the text
310	blink when compiled with "--enable-blinking". with standard colours.	316	blink when compiled with "--enable-text-blink". Without
311	Without "--enable-blinking", the blink attribute will be ignored.	317	"--enable-text-blink", the blink attribute will be ignored.
312		318
313	On ANSI colours, bold/blink attributes are used to set high-intensity	319	On ANSI colours, bold/blink attributes are used to set high-intensity
314	foreground/background colors.	320	foreground/background colours.
315		321
316	color0-7 are the low-intensity colors.	322	color0-7 are the low-intensity colours.
317		323
318	color8-15 are the corresponding high-intensity colors.	324	color8-15 are the corresponding high-intensity colours.
319		325
320	I don't like the screen colors. How do I change them?	326	I don't like the screen colours. How do I change them?
321	You can change the screen colors at run-time using ~/.Xdefaults	327	You can change the screen colours at run-time using ~/.Xdefaults
322	resources (or as long-options).	328	resources (or as long-options).
323		329
324	Here are values that are supposed to resemble a VGA screen, including	330	Here are values that are supposed to resemble a VGA screen, including
325	the murky brown that passes for low-intensity yellow:	331	the murky brown that passes for low-intensity yellow:
326		332
…		…
340	URxvt.color12: #0000FF	346	URxvt.color12: #0000FF
341	URxvt.color13: #FF00FF	347	URxvt.color13: #FF00FF
342	URxvt.color14: #00FFFF	348	URxvt.color14: #00FFFF
343	URxvt.color15: #FFFFFF	349	URxvt.color15: #FFFFFF
344		350
345	And here is a more complete set of non-standard colors described (not by	351	And here is a more complete set of non-standard colours.
346	me) as "pretty girly".
347		352
348	URxvt.cursorColor: #dc74d1	353	URxvt.cursorColor: #dc74d1
349	URxvt.pointerColor: #dc74d1	354	URxvt.pointerColor: #dc74d1
350	URxvt.background: #0e0e0e	355	URxvt.background: #0e0e0e
351	URxvt.foreground: #4ad5e1	356	URxvt.foreground: #4ad5e1
…		…
362	URxvt.color6: #73f7ff	367	URxvt.color6: #73f7ff
363	URxvt.color14: #73f7ff	368	URxvt.color14: #73f7ff
364	URxvt.color7: #e1dddd	369	URxvt.color7: #e1dddd
365	URxvt.color15: #e1dddd	370	URxvt.color15: #e1dddd
366		371
		372	They have been described (not by me) as "pretty girly".
		373
367	Why do some characters look so much different than others?	374	Why do some characters look so much different than others?
368	See next entry.	375	See next entry.
369		376
370	How does rxvt-unicode choose fonts?	377	How does rxvt-unicode choose fonts?
371	Most fonts do not contain the full range of Unicode, which is fine.	378	Most fonts do not contain the full range of Unicode, which is fine.
…		…
382		389
383	In that case, select a font of your taste and add it to the font list,	390	In that case, select a font of your taste and add it to the font list,
384	e.g.:	391	e.g.:
385		392
386	urxvt -fn basefont,font2,font3...	393	urxvt -fn basefont,font2,font3...
387		394
388	When rxvt-unicode sees a character, it will first look at the base font.	395	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	396	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	397	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.	398	search and use less resources within rxvt-unicode and the X-server.
392		399
393	The only limitation is that none of the fonts may be larger than the	400	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,	401	base font, as the base font defines the terminal character cell size,
395	which must be the same due to the way terminals work.	402	which must be the same due to the way terminals work.
396		403
		404	Why do some chinese characters look so different than others?
		405	This is because there is a difference between script and language --
		406	rxvt-unicode does not know which language the text that is output is, as
		407	it only knows the unicode character codes. If rxvt-unicode first sees a
		408	japanese/chinese character, it might choose a japanese font for display.
		409	Subsequent japanese characters will use that font. Now, many chinese
		410	characters aren't represented in japanese fonts, so when the first
		411	non-japanese character comes up, rxvt-unicode will look for a chinese
		412	font -- unfortunately at this point, it will still use the japanese font
		413	for chinese characters that are also in the japanese font.
		414
		415	The workaround is easy: just tag a chinese font at the end of your font
		416	list (see the previous question). The key is to view the font list as a
		417	preference list: If you expect more japanese, list a japanese font
		418	first. If you expect more chinese, put a chinese font first.
		419
		420	In the future it might be possible to switch language preferences at
		421	runtime (the internal data structure has no problem with using different
		422	fonts for the same character at the same time, but no interface for this
		423	has been designed yet).
		424
		425	Until then, you might get away with switching fonts at runtime (see "Can
		426	I switch the fonts at runtime?" later in this document).
		427
		428	How can I make mplayer display video correctly?
		429	We are working on it, in the meantime, as a workaround, use something
		430	like:
		431
		432	urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
		433
397	Keyboard, Mouse & User Interaction	434	Keyboard, Mouse & User Interaction
398	The new selection selects pieces that are too big, how can I select single words?	435	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	436	If you want to select e.g. alphanumeric words, you can use the following
400	setting:	437	setting:
401		438
…		…
407	To get a selection that is very similar to the old code, try this	444	To get a selection that is very similar to the old code, try this
408	pattern:	445	pattern:
409		446
410	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{\|})]+)	447	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{\|})]+)
411		448
412	Please also note that the LeftClick Shift-LeftClik combination also	449	Please also note that the LeftClick Shift-LeftClick combination also
413	selects words like the old code.	450	selects words like the old code.
414		451
415	I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?	452	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	453	You can disable the perl extension completely by setting the
417	perl-ext-common resource to the empty string, which also keeps	454	perl-ext-common resource to the empty string, which also keeps
…		…
440	circumstances, it will move your cursor around when you click into the	477	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,	478	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	479	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.	480	some cases during rlogin sessions, it fails to detect this properly.
444		481
445	You can permamently switch this feature off by disabling the "readline"	482	You can permanently switch this feature off by disabling the "readline"
446	extension:	483	extension:
447		484
448	URxvt.perl-ext-common: default,-readline	485	URxvt.perl-ext-common: default,-readline
449		486
450	My numerical keypad acts weird and generates differing output?	487	My numerical keypad acts weird and generates differing output?
451	Some Debian GNUL/Linux users seem to have this problem, although no	488	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	489	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	490	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	491	how this can happen are unknown, as "TERM=rxvt" should offer a
455	compatible keymap. See the answer to the previous question, and please	492	compatible keymap. See the answer to the previous question, and please
456	report if that helped.	493	report if that helped.
457		494
458	My Compose (Multi_key) key is no longer working.	495	My Compose (Multi_key) key is no longer working.
…		…
464	will continue without an input method.	501	will continue without an input method.
465		502
466	In this case either do not specify a preeditStyle or specify more than	503	In this case either do not specify a preeditStyle or specify more than
467	one pre-edit style, such as OverTheSpot,Root,None.	504	one pre-edit style, such as OverTheSpot,Root,None.
468		505
		506	If it still doesn't work, then maybe your input method doesn't support
		507	compose sequences - to fall back to the built-in one, make sure you
		508	don't specify an input method via "-im" or "XMODIFIERS".
		509
469	I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755	510	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	511	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	512	international keyboards) or simply use ISO 14755 support to your
472	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for	513	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	514	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	520	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	521	check is to see if cut/paste works when the Alt or Shift keys are
481	depressed.	522	depressed.
482		523
483	What's with the strange Backspace/Delete key behaviour?	524	What's with the strange Backspace/Delete key behaviour?
484	Assuming that the physical Backspace key corresponds to the BackSpace	525	Assuming that the physical Backspace key corresponds to the Backspace
485	keysym (not likely for Linux ... see the following question) there are	526	keysym (not likely for Linux ... see the following question) there are
486	two standard values that can be used for Backspace: "^H" and "^?".	527	two standard values that can be used for Backspace: "^H" and "^?".
487		528
488	Historically, either value is correct, but rxvt-unicode adopts the	529	Historically, either value is correct, but rxvt-unicode adopts the
489	debian policy of using "^?" when unsure, because it's the one only only	530	debian policy of using "^?" when unsure, because it's the one and only
490	correct choice :).	531	correct choice :).
491		532
492	Rxvt-unicode tries to inherit the current stty settings and uses the	533	It is possible to toggle between "^H" and "^?" with the DECBKM private
493	value of `erase' to guess the value for backspace. If rxvt-unicode	534	mode:
494	wasn't started from a terminal (say, from a menu or by remote shell),
495	then the system value of `erase', which corresponds to CERASE in
496	<termios.h>, will be used (which may not be the same as your stty
497	setting).
498
499	For starting a new rxvt-unicode:
500		535
501	# use Backspace = ^H	536	# use Backspace = ^H
502	$ stty erase ^H	537	$ stty erase ^H
503	$ urxvt	538	$ echo -n "^[[?67h"
504		539
505	# use Backspace = ^?	540	# use Backspace = ^?
506	$ stty erase ^?	541	$ stty erase ^?
507	$ urxvt
508
509	Toggle with "ESC [ 36 h" / "ESC [ 36 l".
510
511	For an existing rxvt-unicode:
512
513	# use Backspace = ^H
514	$ stty erase ^H
515	$ echo -n "^[[36h"
516
517	# use Backspace = ^?
518	$ stty erase ^?
519	$ echo -n "^[[36l"	542	$ echo -n "^[[?67l"
520		543
521	This helps satisfy some of the Backspace discrepancies that occur, but	544	This helps satisfy some of the Backspace discrepancies that occur, but
522	if you use Backspace = "^H", make sure that the termcap/terminfo value	545	if you use Backspace = "^H", make sure that the termcap/terminfo value
523	properly reflects that.	546	properly reflects that.
524		547
…		…
576	Rather than have rxvt-unicode try to accommodate all the various	599	Rather than have rxvt-unicode try to accommodate all the various
577	possible keyboard mappings, it is better to use `xmodmap' to remap the	600	possible keyboard mappings, it is better to use `xmodmap' to remap the
578	keys as required for your particular machine.	601	keys as required for your particular machine.
579		602
580	Terminal Configuration	603	Terminal Configuration
		604	Can I see a typical configuration?
		605	The default configuration tries to be xterm-like, which I don't like
		606	that much, but it's least surprise to regular users.
		607
		608	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		609	time into customising your terminal. To get you started, here is the
		610	author's .Xdefaults entries, with comments on what they do. It's
		611	certainly not typical, but what's typical...
		612
		613	URxvt.cutchars: "()*,<>[]{}\|'
		614	URxvt.print-pipe: cat >/tmp/xxx
		615
		616	These are just for testing stuff.
		617
		618	URxvt.imLocale: ja_JP.UTF-8
		619	URxvt.preeditType: OnTheSpot,None
		620
		621	This tells rxvt-unicode to use a special locale when communicating with
		622	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		623	type, which requires the "xim-onthespot" perl extension but rewards me
		624	with correct-looking fonts.
		625
		626	URxvt.perl-lib: /root/lib/urxvt
		627	URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		628	URxvt.selection.pattern-0: ( at .*? line \\d+)
		629	URxvt.selection.pattern-1: ^(/[^:]+):\
		630	URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
		631	URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
		632
		633	This is my perl configuration. The first two set the perl library
		634	directory and also tells urxvt to use a large number of extensions. I
		635	develop for myself mostly, so I actually use most of the extensions I
		636	write.
		637
		638	The selection stuff mainly makes the selection perl-error-message aware
		639	and tells it to convert perl error messages into vi-commands to load the
		640	relevant file and go to the error line number.
		641
		642	URxvt.scrollstyle: plain
		643	URxvt.secondaryScroll: true
		644
		645	As the documentation says: plain is the preferred scrollbar for the
		646	author. The "secondaryScroll" configures urxvt to scroll in full-screen
		647	apps, like screen, so lines scrolled out of screen end up in urxvt's
		648	scrollback buffer.
		649
		650	URxvt.background: #000000
		651	URxvt.foreground: gray90
		652	URxvt.color7: gray90
		653	URxvt.colorBD: #ffffff
		654	URxvt.cursorColor: #e0e080
		655	URxvt.throughColor: #8080f0
		656	URxvt.highlightColor: #f0f0f0
		657
		658	Some colours. Not sure which ones are being used or even non-defaults,
		659	but these are in my .Xdefaults. Most notably, they set
		660	foreground/background to light gray/black, and also make sure that the
		661	colour 7 matches the default foreground colour.
		662
		663	URxvt.underlineColor: yellow
		664
		665	Another colour, makes underline lines look different. Sometimes hurts,
		666	but is mostly a nice effect.
		667
		668	URxvt.geometry: 154x36
		669	URxvt.loginShell: false
		670	URxvt.meta: ignore
		671	URxvt.utmpInhibit: true
		672
		673	Uh, well, should be mostly self-explanatory. By specifying some defaults
		674	manually, I can quickly switch them for testing.
		675
		676	URxvt.saveLines: 8192
		677
		678	A large scrollback buffer is essential. Really.
		679
		680	URxvt.mapAlert: true
		681
		682	The only case I use it is for my IRC window, which I like to keep
		683	iconified till people msg me (which beeps).
		684
		685	URxvt.visualBell: true
		686
		687	The audible bell is often annoying, especially when in a crowd.
		688
		689	URxvt.insecure: true
		690
		691	Please don't hack my mutt! Ooops...
		692
		693	URxvt.pastableTabs: false
		694
		695	I once thought this is a great idea.
		696
		697	urxvt.font: 9x15bold,\
		698	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		699	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		700	[codeset=JISX0208]xft:Kochi Gothic, \
		701	xft:Bitstream Vera Sans Mono:autohint=true, \
		702	xft:Code2000:antialias=false
		703	urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		704	urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		705	urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		706
		707	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		708	overwhelmed. A special note: the "9x15bold" mentioned above is actually
		709	the version from XFree-3.3, as XFree-4 replaced it by a totally
		710	different font (different glyphs for ";" and many other harmless
		711	characters), while the second font is actually the "9x15bold" from
		712	XFree4/XOrg. The bold version has less chars than the medium version, so
		713	I use it for rare characters, too. When editing sources with vim, I use
		714	italic for comments and other stuff, which looks quite good with
		715	Bitstream Vera anti-aliased.
		716
		717	Terminus is a quite bad font (many very wrong glyphs), but for most of
		718	my purposes, it works, and gives a different look, as my normal
		719	(Non-bold) font is already bold, and I want to see a difference between
		720	bold and normal fonts.
		721
		722	Please note that I used the "urxvt" instance name and not the "URxvt"
		723	class name. That is because I use different configs for different
		724	purposes, for example, my IRC window is started with "-name IRC", and
		725	uses these defaults:
		726
		727	IRC*title: IRC
		728	IRC*geometry: 87x12+535+542
		729	IRC*saveLines: 0
		730	IRC*mapAlert: true
		731	IRC*font: suxuseuro
		732	IRC*boldFont: suxuseuro
		733	IRC*colorBD: white
		734	IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
		735	IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
		736
		737	"Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes.
		738	"suxuseuro" allows me to keep an eye (and actually read) stuff while
		739	keeping a very small window. If somebody pastes something complicated
		740	(e.g. japanese), I temporarily switch to a larger font.
		741
		742	The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
		743	"xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
		744	file for different hosts, for example, on my main desktop, I use:
		745
		746	URxvt.keysym.C-M-q: command:\033[3;5;5t
		747	URxvt.keysym.C-M-y: command:\033[3;5;606t
		748	URxvt.keysym.C-M-e: command:\033[3;1605;5t
		749	URxvt.keysym.C-M-c: command:\033[3;1605;606t
		750	URxvt.keysym.C-M-p: perl:test
		751
		752	The first for keysym definitions allow me to quickly bring some windows
		753	in the layout I like most. Ion users might start laughing but will stop
		754	immediately when I tell them that I use my own Fvwm2 module for much the
		755	same effect as Ion provides, and I only very rarely use the above key
		756	combinations :->
		757
581	Why doesn't rxvt-unicode read my resources?	758	Why doesn't rxvt-unicode read my resources?
582	Well, why, indeed? It does, in a way very similar to other X	759	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	760	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	761	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	762	ignore any resource files in your home directory. It will only read
…		…
592	Also consider the form resources have to use:	769	Also consider the form resources have to use:
593		770
594	URxvt.resource: value	771	URxvt.resource: value
595		772
596	If you want to use another form (there are lots of different ways of	773	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.	774	specifying resources), make sure you understand whether and why it
598	If unsure, use the form above.	775	works. If unsure, use the form above.
599		776
600	When I log-in to another system it tells me about missing terminfo data?	777	When I log-in to another system it tells me about missing terminfo data?
601	The terminal description used by rxvt-unicode is not as widely available	778	The terminal description used by rxvt-unicode is not as widely available
602	as that for xterm, or even rxvt (for which the same problem often	779	as that for xterm, or even rxvt (for which the same problem often
603	arises).	780	arises).
604		781
605	The correct solution for this problem is to install the terminfo, this	782	The correct solution for this problem is to install the terminfo, this
606	can be done like this (with ncurses' infocmp):	783	can be done by simply installing rxvt-unicode on the remote system as
		784	well (in case you have a nice package manager ready), or you can install
		785	the terminfo database manually like this (with ncurses infocmp. works as
		786	user and root):
607		787
608	REMOTE=remotesystem.domain	788	REMOTE=remotesystem.domain
609	infocmp rxvt-unicode \| ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"	789	infocmp rxvt-unicode \| ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
610		790
611	... or by installing rxvt-unicode normally on the remote system,	791	One some systems you might need to set $TERMINFO to the full path of
		792	$HOME/.terminfo for this to work.
612		793
613	If you cannot or do not want to do this, then you can simply set	794	If you cannot or do not want to do this, then you can simply set
614	"TERM=rxvt" or even "TERM=xterm", and live with the small number of	795	"TERM=rxvt" or even "TERM=xterm", and live with the small number of
615	problems arising, which includes wrong keymapping, less and different	796	problems arising, which includes wrong keymapping, less and different
616	colours and some refresh errors in fullscreen applications. It's a nice	797	colours and some refresh errors in fullscreen applications. It's a nice
…		…
621	resource to set it:	802	resource to set it:
622		803
623	URxvt.termName: rxvt	804	URxvt.termName: rxvt
624		805
625	If you don't plan to use rxvt (quite common...) you could also replace	806	If you don't plan to use rxvt (quite common...) you could also replace
626	the rxvt terminfo file with the rxvt-unicode one.	807	the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
		808
		809	nano fails with "Error opening terminal: rxvt-unicode"
		810	This exceptionally confusing and useless error message is printed by
		811	nano when it can't find the terminfo database. Nothing is wrong with
		812	your terminal, read the previous answer for a solution.
627		813
628	"tic" outputs some error when compiling the terminfo entry.	814	"tic" outputs some error when compiling the terminfo entry.
629	Most likely it's the empty definition for "enacs=". Just replace it by	815	Most likely it's the empty definition for "enacs=". Just replace it by
630	"enacs=\E[0@" and try again.	816	"enacs=\E[0@" and try again.
631		817
…		…
636	One reason you might want this is that some distributions or operating	822	One reason you might want this is that some distributions or operating
637	systems still compile some programs using the long-obsoleted termcap	823	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	824	library (Fedora Core's bash is one example) and rely on a termcap entry
639	for "rxvt-unicode".	825	for "rxvt-unicode".
640		826
641	You could use rxvt's termcap entry with resonable results in many cases.	827	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	828	cases. You can also create a termcap entry by using terminfo's infocmp
643	like this:	829	program like this:
644		830
645	infocmp -C rxvt-unicode	831	infocmp -C rxvt-unicode
646		832
647	Or you could use this termcap entry, generated by the command above:	833	Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap,
648		834	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		835
670	Why does "ls" no longer have coloured output?	836	Why does "ls" no longer have coloured output?
671	The "ls" in the GNU coreutils unfortunately doesn't use terminfo to	837	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	838	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	839	file. Needless to say, "rxvt-unicode" is not in its default file (among
674	with most other terminals supporting colour). Either add:	840	with most other terminals supporting colour). Either add:
675		841
676	TERM rxvt-unicode	842	TERM rxvt-unicode
677		843
678	to "/etc/DIR_COLORS" or simply add:	844	to "/etc/DIR_COLORS" or simply add:
…		…
705	If you encounter strange problems like typing an accented character but	871	If you encounter strange problems like typing an accented character but
706	getting two unrelated other characters or similar, or if program output	872	getting two unrelated other characters or similar, or if program output
707	is subtly garbled, then you should check your locale settings.	873	is subtly garbled, then you should check your locale settings.
708		874
709	Rxvt-unicode must be started with the same "LC_CTYPE" setting as the	875	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	876	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	877	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	878	the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
713	going to work.	879	is not going to work, and is the most common cause for problems.
714		880
715	The best thing is to fix your startup environment, as you will likely	881	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	882	run into other problems. If nothing works you can try this in your
717	.profile.	883	.profile.
718		884
719	printf '\e]701;%s\007' "$LC_CTYPE"	885	printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
720		886
721	If this doesn't work, then maybe you use a "LC_CTYPE" specification not	887	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	888	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	889	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	890	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	909	The reasons is that there exists a perfectly fine mechanism for
744	selecting the encoding, doing I/O and (most important) communicating	910	selecting the encoding, doing I/O and (most important) communicating
745	this to all applications so everybody agrees on character properties	911	this to all applications so everybody agrees on character properties
746	such as width and code number. This mechanism is the locale.	912	such as width and code number. This mechanism is the locale.
747	Applications not using that info will have problems (for example,	913	Applications not using that info will have problems (for example,
748	"xterm" gets the width of characters wrong as it uses it's own,	914	"xterm" gets the width of characters wrong as it uses its own,
749	locale-independent table under all locales).	915	locale-independent table under all locales).
750		916
751	Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All	917	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	918	programs doing the same (that is, most) will automatically agree in the
753	interpretation of characters.	919	interpretation of characters.
…		…
770		936
771	Can I switch locales at runtime?	937	Can I switch locales at runtime?
772	Yes, using an escape sequence. Try something like this, which sets	938	Yes, using an escape sequence. Try something like this, which sets
773	rxvt-unicode's idea of "LC_CTYPE".	939	rxvt-unicode's idea of "LC_CTYPE".
774		940
775	printf '\e]701;%s\007' ja_JP.SJIS	941	printf '\33]701;%s\007' ja_JP.SJIS
776		942
777	See also the previous answer.	943	See also the previous answer.
778		944
779	Sometimes this capability is rather handy when you want to work in one	945	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.	946	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	947	UTF-8). For example, I use this script to start "xjdic", which first
782	switches to a locale supported by xjdic and back later:	948	switches to a locale supported by xjdic and back later:
783		949
784	printf '\e]701;%s\007' ja_JP.SJIS	950	printf '\33]701;%s\007' ja_JP.SJIS
785	xjdic -js	951	xjdic -js
786	printf '\e]701;%s\007' de_DE.UTF-8	952	printf '\33]701;%s\007' de_DE.UTF-8
787		953
788	You can also use xterm's "luit" program, which usually works fine,	954	You can also use xterm's "luit" program, which usually works fine,
789	except for some locales where character width differs between program-	955	except for some locales where character width differs between program-
790	and rxvt-unicode-locales.	956	and rxvt-unicode-locales.
791		957
		958	I have problems getting my input method working.
		959	Try a search engine, as this is slightly different for every input
		960	method server.
		961
		962	Here is a checklist:
		963
		964	- Make sure your locale and the imLocale are supported on your OS.
		965	Try "locale -a" or check the documentation for your OS.
		966
		967	- Make sure your locale or imLocale matches a locale supported by your
		968	XIM.
		969	For example, kinput2 does not support UTF-8 locales, you should use
		970	"ja_JP.EUC-JP" or equivalent.
		971
		972	- Make sure your XIM server is actually running.
		973	- Make sure the "XMODIFIERS" environment variable is set correctly when
		974	starting rxvt-unicode.
		975	When you want to use e.g. kinput2, it must be set to "@im=kinput2".
		976	For scim, use "@im=SCIM". You can see what input method servers are
		977	running with this command:
		978
		979	xprop -root XIM_SERVERS
		980
		981
		982
792	My input method wants <some encoding> but I want UTF-8, what can I do?	983	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	984	You can specify separate locales for the input method and the rest of
794	the terminal, using the resource "imlocale":	985	the terminal, using the resource "imlocale":
795		986
796	URxvt.imlocale: ja_JP.EUC-JP	987	URxvt.imlocale: ja_JP.EUC-JP
797		988
798	Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still	989	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	990	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	991	Xlib version, you may not be able to input characters outside "EUC-JP"
801	method limits you.	992	in a normal way then, as your input method limits you.
802		993
803	Rxvt-unicode crashes when the X Input Method changes or exits.	994	Rxvt-unicode crashes when the X Input Method changes or exits.
804	Unfortunately, this is unavoidable, as the XIM protocol is racy by	995	Unfortunately, this is unavoidable, as the XIM protocol is racy by
805	design. Applications can avoid some crashes at the expense of memory	996	design. Applications can avoid some crashes at the expense of memory
806	leaks, and Input Methods can avoid some crashes by careful ordering at	997	leaks, and Input Methods can avoid some crashes by careful ordering at
…		…
827	that might encounter the same issue.	1018	that might encounter the same issue.
828		1019
829	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?	1020	I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
830	You should build one binary with the default options. configure now	1021	You should build one binary with the default options. configure now
831	enables most useful options, and the trend goes to making them	1022	enables most useful options, and the trend goes to making them
832	runtime-switchable, too, so there is usually no drawback to enbaling	1023	runtime-switchable, too, so there is usually no drawback to enabling
833	them, except higher disk and possibly memory usage. The perl interpreter	1024	them, except higher disk and possibly memory usage. The perl interpreter
834	should be enabled, as important functionality (menus, selection, likely	1025	should be enabled, as important functionality (menus, selection, likely
835	more in the future) depends on it.	1026	more in the future) depends on it.
836		1027
837	You should not overwrite the "perl-ext-common" snd "perl-ext" resources	1028	You should not overwrite the "perl-ext-common" and "perl-ext" resources
838	system-wide (except maybe with "defaults"). This will result in useful	1029	system-wide (except maybe with "defaults"). This will result in useful
839	behaviour. If your distribution aims at low memory, add an empty	1030	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	1031	"perl-ext-common" resource to the app-defaults file. This will keep the
841	perl interpreter disabled until the user enables it.	1032	perl interpreter disabled until the user enables it.
842		1033
…		…
859	This forking is done as the very first within main(), which is very	1050	This forking is done as the very first within main(), which is very
860	early and reduces possible bugs to initialisation code run before	1051	early and reduces possible bugs to initialisation code run before
861	main(), or things like the dynamic loader of your system, which should	1052	main(), or things like the dynamic loader of your system, which should
862	result in very little risk.	1053	result in very little risk.
863		1054
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.	1055	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	1056	Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
873	your compile environment, or an implementation that implements it,	1057	your compile environment, or an implementation that implements it,
874	wether it defines the symbol or not. "__STDC_ISO_10646__" requires that	1058	whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
875	wchar_t is represented as unicode.	1059	wchar_t is represented as unicode.
876		1060
877	As you might have guessed, FreeBSD does neither define this symobl nor	1061	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	1062	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.	1063	wchar_t. This is, of course, completely fine with respect to standards.
880		1064
881	However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and	1065	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.	1066	"UTF-8" locales under FreeBSD (which all use Unicode as wchar_t).
883		1067
884	"__STDC_ISO_10646__" is the only sane way to support multi-language apps	1068	"__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)	1069	in an OS, as using a locale-dependent (and non-standardized)
886	representation of wchar_t makes it impossible to convert between wchar_t	1070	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	1071	(as used by X11 and your applications) and any other encoding without
…		…
897		1081
898	The rxvt-unicode author insists that the right way to fix this is in the	1082	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	1083	system libraries once and for all, instead of forcing every app to carry
900	complete replacements for them :)	1084	complete replacements for them :)
901		1085
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?	1086	How can I use rxvt-unicode under cygwin?
907	rxvt-unicode should compile and run out of the box on cygwin, using the	1087	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	1088	X11 libraries that come with cygwin. libW11 emulation is no longer
909	supported (and makes no sense, either, as it only supported a single	1089	supported (and makes no sense, either, as it only supported a single
910	font). I recommend starting the X-server in "-multiwindow" or	1090	font). I recommend starting the X-server in "-multiwindow" or
…		…
913		1093
914	At the time of this writing, cygwin didn't seem to support any	1094	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	1095	multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
916	likely limited to 8-bit encodings.	1096	likely limited to 8-bit encodings.
917		1097
		1098	Character widths are not correct.
		1099	urxvt uses the system wcwidth function to know the information about the
		1100	width of characters, so on systems with incorrect locale data you will
		1101	likely get bad results. Two notorious examples are Solaris 9, where
		1102	single-width characters like U+2514 are reported as double-width, and
		1103	Darwin 8, where combining chars are reported having width 1.
		1104
		1105	The solution is to upgrade your system or switch to a better one. A
		1106	possibly working workaround is to use a wcwidth implementation like
		1107
		1108	http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
		1109

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.62 by root, Thu Dec 9 10:36:51 2010 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.62 by root, Thu Dec 9 10:36:51 2010 UTC