[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.34 by root, Thu Feb 3 10:24:10 2005 UTC vs.
Revision 1.60 by root, Fri Jul 29 03:12:10 2005 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	RXVT REFERENCE - FAQ, command sequences and other background information	3	RXVT REFERENCE - FAQ, command sequences and other background information
4		4
		5	=head1 SYNOPSIS
		6
		7	# set a new font set
		8	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
		9
		10	# change the locale and tell rxvt-unicode about it
		11	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
		12
		13	# set window title
		14	printf '\33]2;%s\007' "new window title"
		15
		16	=head1 DESCRIPTION
		17
		18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
		19	all escape sequences, and other background information.
		20
		21	The newest version of this document is
		22	also available on the World Wide Web at
		23	L<http://cvs.schmorp.de/browse/checkout/rxvt-unicode/doc/rxvt.7.html>.
		24
5	=head1 FREQUENTLY ASKED QUESTIONS	25	=head1 FREQUENTLY ASKED QUESTIONS
6		26
7	=over 4	27	=over 4
8		28
9	=item How do I know which rxvt-unicode version I'm using?	29	=item How do I know which rxvt-unicode version I'm using?
10		30
11	The version number is displayed with the usage (-h). Also the escape	31	The version number is displayed with the usage (-h). Also the escape
12	sequence C<ESC[8n> sets the window title to the version number.	32	sequence C<ESC [ 8 n> sets the window title to the version number.
		33
		34	=item I am using Debian GNU/Linux and have a problem...
		35
		36	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		37	patches that considerably change the behaviour of rxvt-unicode. Before
		38	reporting a bug to the original rxvt-unicode author please download and
		39	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
		40	and try to reproduce the problem. If you cannot, chances are that the
		41	problems are specific to Debian GNU/Linux, in which case it should be
		42	reported via the Debian Bug Tracking System (use C<reportbug> to report
		43	the bug).
		44
		45	For other problems that also affect the Debian package, you can and
		46	probably should use the Debian BTS, too, because, after all, it's also a
		47	bug in the Debian version and it serves as a reminder for other users that
		48	might encounter the same issue.
13		49
14	=item When I log-in to another system it tells me about missing terminfo data?	50	=item When I log-in to another system it tells me about missing terminfo data?
15		51
16	The terminal description used by rxvt-unicode is not as widely available	52	The terminal description used by rxvt-unicode is not as widely available
17	as that for xterm, or even rxvt (for which the same problem often arises).	53	as that for xterm, or even rxvt (for which the same problem often arises).
28	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of	64	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
29	problems arising, which includes wrong keymapping, less and different	65	problems arising, which includes wrong keymapping, less and different
30	colours and some refresh errors in fullscreen applications. It's a nice	66	colours and some refresh errors in fullscreen applications. It's a nice
31	quick-and-dirty workaround for rare cases, though.	67	quick-and-dirty workaround for rare cases, though.
32		68
33	If you always want to do this you can either recompile rxvt-unicode with	69	If you always want to do this (and are fine with the consequences) you
34	the desired TERM value or use a resource to set it:	70	can either recompile rxvt-unicode with the desired TERM value or use a
		71	resource to set it:
35		72
36	URxvt.termName: rxvt	73	URxvt.termName: rxvt
37		74
38	If you don't plan to use B<rxvt> (quite common...) you could also replace	75	If you don't plan to use B<rxvt> (quite common...) you could also replace
39	the rxvt terminfo file with the rxvt-unicode one.	76	the rxvt terminfo file with the rxvt-unicode one.
40		77
		78	=item C<tic> outputs some error when compiling the terminfo entry.
		79
		80	Most likely it's the empty definition for C<enacs=>. Just replace it by
		81	C<enacs=\E[0@> and try again.
		82
		83	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
		84
41	=item I need a termcap file entry.	85	=item I need a termcap file entry.
		86
		87	One reason you might want this is that some distributions or operating
		88	systems still compile some programs using the long-obsoleted termcap
		89	library (Fedora Core's bash is one example) and rely on a termcap entry
		90	for C<rxvt-unicode>.
42		91
43	You could use rxvt's termcap entry with resonable results in many cases.	92	You could use rxvt's termcap entry with resonable results in many cases.
44	You can also create a termcap entry by using terminfo's infocmp program	93	You can also create a termcap entry by using terminfo's infocmp program
45	like this:	94	like this:
46		95
47	infocmp -C rxvt-unicode	96	infocmp -C rxvt-unicode
48		97
49	OR you could this termcap entry:	98	Or you could use this termcap entry, generated by the command above:
50		99
51	rxvt-unicode\|rxvt-unicode terminal (X Window System):\	100	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
52	:am:bw:eo:km:mi:ms:xn:xo:\	101	:am:bw:eo:km:mi:ms:xn:xo:\
53	:co#80:it#8:li#24:\	102	:co#80:it#8:li#24:lm#0:\
54	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	103	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
55	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\	104	:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
56	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\	105	:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
57	:as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\	106	:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
58	:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\	107	:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
59	:ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\	108	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
		109	:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
60	:im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\	110	:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
61	:k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\	111	:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
62	:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\	112	:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
63	:kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\	113	:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
64	:ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\	114	:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
65	:ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\	115	:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
66	:nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\	116	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
67	:st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\	117	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
68	:up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	118	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
69	:vs=\E[?25h:	119	:vs=\E[?25h:
70		120
71	=item Why does C<ls> no longer have coloured output?	121	=item Why does C<ls> no longer have coloured output?
72		122
73	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	123	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
…		…
96	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	146	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
97	file, so you will need to install it on your own (See the question B<When	147	file, so you will need to install it on your own (See the question B<When
98	I log-in to another system it tells me about missing terminfo data?> on	148	I log-in to another system it tells me about missing terminfo data?> on
99	how to do this).	149	how to do this).
100		150
		151	=item My numerical keypad acts weird and generates differing output?
		152
		153	Some Debian GNUL/Linux users seem to have this problem, although no
		154	specific details were reported so far. It is possible that this is caused
		155	by the wrong C<TERM> setting, although the details of wether and how
		156	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		157	keymap. See the answer to the previous question, and please report if that
		158	helped.
		159
101	=item Rxvt-unicode does not seem to understand the selected encoding?	160	=item Rxvt-unicode does not seem to understand the selected encoding?
102		161
103	=item Unicode does not seem to work?	162	=item Unicode does not seem to work?
104		163
105	If you encounter strange problems like typing an accented character but	164	If you encounter strange problems like typing an accented character but
…		…
107	subtly garbled, then you should check your locale settings.	166	subtly garbled, then you should check your locale settings.
108		167
109	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	168	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
110	programs. Often rxvt-unicode is started in the C<C> locale, while the	169	programs. Often rxvt-unicode is started in the C<C> locale, while the
111	login script running within the rxvt-unicode window changes the locale to	170	login script running within the rxvt-unicode window changes the locale to
112	sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work.	171	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
113		172
114	The best thing is to fix your startup environment, as you will likely run	173	The best thing is to fix your startup environment, as you will likely run
115	into other problems. If nothing works you can try this in your .profile.	174	into other problems. If nothing works you can try this in your .profile.
116		175
117	printf '\e]701;%s\007' "$LC_CTYPE"	176	printf '\e]701;%s\007' "$LC_CTYPE"
118		177
119	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	178	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
120	supported on your systems. Some systems have a C<locale> command which	179	supported on your systems. Some systems have a C<locale> command which
121	displays this. If it displays sth. like:	180	displays this (also, C<perl -e0> can be used to check locale settings, as
		181	it will complain loudly if it cannot set the locale). If it displays something
		182	like:
122		183
123	locale: Cannot set LC_CTYPE to default locale: ...	184	locale: Cannot set LC_CTYPE to default locale: ...
124		185
125	Then the locale you specified is not supported on your system.	186	Then the locale you specified is not supported on your system.
126		187
…		…
137	your system/os) have specified does not cover all the characters you want	198	your system/os) have specified does not cover all the characters you want
138	to display.	199	to display.
139		200
140	B<rxvt-unicode> makes a best-effort try at finding a replacement	201	B<rxvt-unicode> makes a best-effort try at finding a replacement
141	font. Often the result is fine, but sometimes the chosen font looks	202	font. Often the result is fine, but sometimes the chosen font looks
142	bad. Many fonts have totally strange characters that don't resemble the	203	bad/ugly/wrong. Some fonts have totally strange characters that don't
143	correct glyph at all, and rxvt-unicode lacks the artificial intelligence	204	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
144	to detect that a specific glyph is wrong: it has to believe the font that	205	intelligence to detect that a specific glyph is wrong: it has to believe
145	the characters it contains indeed look correct.	206	the font that the characters it claims to contain indeed look correct.
146		207
147	In that case, select a font of your taste and add it to the font list,	208	In that case, select a font of your taste and add it to the font list,
148	e.g.:	209	e.g.:
149		210
150	@@RXVT_NAME@@ -fn basefont,font2,font3...	211	@@RXVT_NAME@@ -fn basefont,font2,font3...
…		…
152	When rxvt-unicode sees a character, it will first look at the base	213	When rxvt-unicode sees a character, it will first look at the base
153	font. If the base font does not contain the character, it will go to the	214	font. If the base font does not contain the character, it will go to the
154	next font, and so on. Specifying your own fonts will also speed up this	215	next font, and so on. Specifying your own fonts will also speed up this
155	search and use less resources within rxvt-unicode and the X-server.	216	search and use less resources within rxvt-unicode and the X-server.
156		217
157	The only limitation is that all the fonts must not be larger than the base	218	The only limitation is that none of the fonts may be larger than the base
158	font, as the base font defines the principal cell size, which must be the	219	font, as the base font defines the terminal character cell size, which
159	same due to the way terminals work.	220	must be the same due to the way terminals work.
160		221
161	=item Why do some chinese characters look so different than others?	222	=item Why do some chinese characters look so different than others?
162		223
163	This is because there is a difference between script and language --	224	This is because there is a difference between script and language --
164	rxvt-unicode does not know which language the text that is output	225	rxvt-unicode does not know which language the text that is output is,
165	is, as it only knows the unicode character codes. If rxvt-unicode	226	as it only knows the unicode character codes. If rxvt-unicode first
166	first sees a japanese character, it might choose a japanese font for	227	sees a japanese/chinese character, it might choose a japanese font for
167	it. Subsequent japanese characters will take that font. Now, many chinese	228	display. Subsequent japanese characters will use that font. Now, many
168	characters aren't represented in japanese fonts, so when the first	229	chinese characters aren't represented in japanese fonts, so when the first
169	non-japanese character comes up, rxvt-unicode will look for a chinese font	230	non-japanese character comes up, rxvt-unicode will look for a chinese font
170	-- unfortunately at this point, it will still use the japanese font for	231	-- unfortunately at this point, it will still use the japanese font for
171	japanese characters that are also chinese.	232	chinese characters that are also in the japanese font.
172		233
173	The workaround is easy: just tag a chinese font at the end of your font	234	The workaround is easy: just tag a chinese font at the end of your font
174	list (see the previous question). The key is to view the font list as	235	list (see the previous question). The key is to view the font list as
175	a preference list: If you expect more japanese, list a japanese font	236	a preference list: If you expect more japanese, list a japanese font
176	first. If you expect more chinese, put a chinese font first.	237	first. If you expect more chinese, put a chinese font first.
177		238
178	In the future it might be possible to switch preferences at runtime (the	239	In the future it might be possible to switch language preferences at
179	internal data structure has no problem with using different fonts for	240	runtime (the internal data structure has no problem with using different
180	the same character at the same time, but no interface for this has been	241	fonts for the same character at the same time, but no interface for this
181	designed yet).	242	has been designed yet).
		243
		244	Until then, you might get away with switching fonts at runtime (see L<Can
		245	I switch the fonts at runtime?> later in this document).
182		246
183	=item Why does rxvt-unicode sometimes leave pixel droppings?	247	=item Why does rxvt-unicode sometimes leave pixel droppings?
184		248
185	Most fonts were not designed for terminal use, which means that character	249	Most fonts were not designed for terminal use, which means that character
186	size varies a lot. A font that is otherwise fine for terminal use might	250	size varies a lot. A font that is otherwise fine for terminal use might
…		…
199	the C<-lsp> option to give the font more height. If that doesn't work, you	263	the C<-lsp> option to give the font more height. If that doesn't work, you
200	might be forced to use a different font.	264	might be forced to use a different font.
201		265
202	All of this is not a problem when using X11 core fonts, as their bounding	266	All of this is not a problem when using X11 core fonts, as their bounding
203	box data is correct.	267	box data is correct.
		268
		269	=item On Solaris 9, many line-drawing characters are too wide.
		270
		271	Seems to be a known bug, read
		272	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
		273	following ugly workaround to get non-double-wide-characters working:
		274
		275	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
204		276
205	=item My Compose (Multi_key) key is no longer working.	277	=item My Compose (Multi_key) key is no longer working.
206		278
207	The most common causes for this are that either your locale is not set	279	The most common causes for this are that either your locale is not set
208	correctly, or you specified a B<preeditStyle> that is not supported by	280	correctly, or you specified a B<preeditStyle> that is not supported by
…		…
222	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape	294	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
223	character and so on.	295	character and so on.
224		296
225	=item How can I keep rxvt-unicode from using reverse video so much?	297	=item How can I keep rxvt-unicode from using reverse video so much?
226		298
227	First of all, make sure you are running with the right terminfo	299	First of all, make sure you are running with the right terminal settings
228	(C<urxvt>), which will get rid of most of these effects. Then make sure	300	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
229	you have specified colours for italic and bold, as otherwise rxvt-unicode	301	make sure you have specified colours for italic and bold, as otherwise
230	might use reverse video to simulate the effect:	302	rxvt-unicode might use reverse video to simulate the effect:
231		303
232	URxvt*colorBD: white	304	URxvt.colorBD: white
233	URxvt*colorIT: green	305	URxvt.colorIT: green
234		306
235	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?	307	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
236		308
237	For some unexplainable reason, some programs (i.e. irssi) assume a very	309	For some unexplainable reason, some rare programs assume a very weird
238	weird colour palette when confronted with a terminal with more than the	310	colour palette when confronted with a terminal with more than the standard
239	standard 8 colours (rxvt-unicode supports 88). The right fix is, of	311	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
240	course, to fix these programs not to assume non-ISO colours without very	312	these programs not to assume non-ISO colours without very good reasons.
241	good reasons.
242		313
243	In the meantime, you can either edit your C<urxvt> terminfo definition to	314	In the meantime, you can either edit your C<rxvt-unicode> terminfo
244	only claim 8 colour support or use C<TERM=rxvt>, which will fix colours	315	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
245	but keep you from using other rxvt-unicode features.	316	fix colours but keep you from using other rxvt-unicode features.
246		317
247	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	318	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
248		319
249	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	320	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
250	in your compile environment, or an implementation that implements it,	321	in your compile environment, or an implementation that implements it,
251	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	322	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
252	B<wchar_t> is represented as unicode.	323	B<wchar_t> is represented as unicode.
253		324
254	As you might have guessed, FreeBSD does neither define this symobl nor	325	As you might have guessed, FreeBSD does neither define this symobl nor
255	does it support it. Instead, it uses it's own internal representation of	326	does it support it. Instead, it uses it's own internal representation of
256	B<wchar_t>. This is, of course, completely legal.	327	B<wchar_t>. This is, of course, completely fine with respect to standards.
257		328
		329	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
		330	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
		331
258	However, C<__STDC_ISO_10646__> is the only sane way to support	332	C<__STDC_ISO_10646__> is the only sane way to support multi-language
259	multi-language apps in an OS, as using a locale-dependent (and	333	apps in an OS, as using a locale-dependent (and non-standardized)
260	non-standardized) representation of B<wchar_t> makes it impossible to	334	representation of B<wchar_t> makes it impossible to convert between
261	convert between B<wchar_t> (as used by X11 and your applications) and any	335	B<wchar_t> (as used by X11 and your applications) and any other encoding
262	other encoding without implementing OS-specific-wrappers for each and	336	without implementing OS-specific-wrappers for each and every locale. There
263	every locale. There simply are no APIs to convert B<wchar_t> into anything	337	simply are no APIs to convert B<wchar_t> into anything except the current
264	except the current locale encoding.	338	locale encoding.
265		339
266	Some applications (such as the formidable B<mlterm>) work around this	340	Some applications (such as the formidable B<mlterm>) work around this
267	by carrying their own replacement functions for character set handling	341	by carrying their own replacement functions for character set handling
268	with them, and either implementing OS-dependent hacks or doing multiple	342	with them, and either implementing OS-dependent hacks or doing multiple
269	conversions (which is slow and unreliable in case the OS implements	343	conversions (which is slow and unreliable in case the OS implements
270	encodings slightly different than the terminal emulator).	344	encodings slightly different than the terminal emulator).
271		345
272	The rxvt-unicode author insists that the right way to fix this is in the	346	The rxvt-unicode author insists that the right way to fix this is in the
273	system libraries once and for all, instead of forcing every app to carry	347	system libraries once and for all, instead of forcing every app to carry
274	complete replacements.	348	complete replacements for them :)
		349
		350	=item I use Solaris 9 and it doesn't compile/work/etc.
		351
		352	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
		353	problems with C<wcwidth> and a compile problem.
		354
		355	=item How can I use rxvt-unicode under cygwin?
		356
		357	rxvt-unicode should compile and run out of the box on cygwin, using
		358	the X11 libraries that come with cygwin. libW11 emulation is no
		359	longer supported (and makes no sense, either, as it only supported a
		360	single font). I recommend starting the X-server in C<-multiwindow> or
		361	C<-rootless> mode instead, which will result in similar look&feel as the
		362	old libW11 emulation.
		363
		364	At the time of this writing, cygwin didn't seem to support any multi-byte
		365	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
		366	to 8-bit encodings.
275		367
276	=item How does rxvt-unicode determine the encoding to use?	368	=item How does rxvt-unicode determine the encoding to use?
277		369
278	=item Is there an option to switch encodings?	370	=item Is there an option to switch encodings?
279		371
…		…
281	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about	373	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
282	UTF-8 or any other encodings with respect to terminal I/O.	374	UTF-8 or any other encodings with respect to terminal I/O.
283		375
284	The reasons is that there exists a perfectly fine mechanism for selecting	376	The reasons is that there exists a perfectly fine mechanism for selecting
285	the encoding, doing I/O and (most important) communicating this to all	377	the encoding, doing I/O and (most important) communicating this to all
286	applications so everybody agrees on character properties such as width and	378	applications so everybody agrees on character properties such as width
287	code number. This mechanism is the I<locale>.	379	and code number. This mechanism is the I<locale>. Applications not using
		380	that info will have problems (for example, C<xterm> gets the width of
		381	characters wrong as it uses it's own, locale-independent table under all
		382	locales).
288		383
289	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All	384	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
290	programs doing the same (that is, most) will automatically agree in the	385	programs doing the same (that is, most) will automatically agree in the
291	interpretation of characters.	386	interpretation of characters.
292		387
…		…
299	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms	394	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
300	(i.e. C<de> or C<german>) are also common.	395	(i.e. C<de> or C<german>) are also common.
301		396
302	Rxvt-unicode ignores all other locale categories, and except for	397	Rxvt-unicode ignores all other locale categories, and except for
303	the encoding, ignores country or language-specific settings,	398	the encoding, ignores country or language-specific settings,
304	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode.	399	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		400	rxvt-unicode.
305		401
306	If you want to use a specific encoding you have to make sure you start	402	If you want to use a specific encoding you have to make sure you start
307	rxvt-unicode with the correct C<LC_CTYPE> category.	403	rxvt-unicode with the correct C<LC_CTYPE> category.
308		404
309	=item Can I switch locales at runtime?	405	=item Can I switch locales at runtime?
310		406
311	Yes, using an escape sequence. Try sth. like this, which sets	407	Yes, using an escape sequence. Try something like this, which sets
312	rxvt-unicode's idea of C<LC_CTYPE>.	408	rxvt-unicode's idea of C<LC_CTYPE>.
313		409
314	printf '\e]701;%s\007' ja_JP.SJIS	410	printf '\e]701;%s\007' ja_JP.SJIS
315		411
316	See also the previous question.	412	See also the previous answer.
317		413
318	Sometimes this capability is rather handy when you want to work in one	414	Sometimes this capability is rather handy when you want to work in
319	locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For	415	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
320	example, I use this script to start C<xjdic>, which first switches to a	416	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
321	locale supported by xjdic and back later:	417	first switches to a locale supported by xjdic and back later:
322		418
323	printf '\e]701;%s\007' ja_JP.SJIS	419	printf '\e]701;%s\007' ja_JP.SJIS
324	xjdic -js	420	xjdic -js
325	printf '\e]701;%s\007' de_DE.UTF-8	421	printf '\e]701;%s\007' de_DE.UTF-8
326		422
		423	You can also use xterm's C<luit> program, which usually works fine, except
		424	for some locales where character width differs between program- and
		425	rxvt-unicode-locales.
		426
327	=item Can I switch the fonts at runtime?	427	=item Can I switch the fonts at runtime?
328		428
329	Yes, using an escape sequence. Try sth. like this, which has the same	429	Yes, using an escape sequence. Try something like this, which has the same
330	effect as using the C<-fn> switch, and takes effect immediately:	430	effect as using the C<-fn> switch, and takes effect immediately:
331		431
332	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	432	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
333		433
334	This is useful if you e.g. work primarily with japanese (and prefer a	434	This is useful if you e.g. work primarily with japanese (and prefer a
…		…
339		439
340	=item Why do italic characters look as if clipped?	440	=item Why do italic characters look as if clipped?
341		441
342	Many fonts have difficulties with italic characters and hinting. For	442	Many fonts have difficulties with italic characters and hinting. For
343	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans	443	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
344	Mono> completely fails in it's italic face. A workaround is to enable	444	Mono> completely fails in it's italic face. A workaround might be to
345	freetype autohinting, i.e. like this:	445	enable freetype autohinting, i.e. like this:
346		446
347	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	447	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
348	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	448	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
349		449
350	=item My input method wants <some encoding> but I want UTF-8, what can I do?	450	=item My input method wants <some encoding> but I want UTF-8, what can I do?
351		451
352	You can specify separate locales for the input method and the rest of the	452	You can specify separate locales for the input method and the rest of the
353	terminal, using the resource C<imlocale>:	453	terminal, using the resource C<imlocale>:
…		…
357	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still	457	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
358	use your input method. Please note, however, that you will not be able to	458	use your input method. Please note, however, that you will not be able to
359	input characters outside C<EUC-JP> in a normal way then, as your input	459	input characters outside C<EUC-JP> in a normal way then, as your input
360	method limits you.	460	method limits you.
361		461
		462	=item Rxvt-unicode crashes when the X Input Method changes or exits.
		463
		464	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		465	design. Applications can avoid some crashes at the expense of memory
		466	leaks, and Input Methods can avoid some crashes by careful ordering at
		467	exit time. B<kinput2> (and derived input methods) generally succeeds,
		468	while B<SCIM> (or similar input methods) fails. In the end, however,
		469	crashes cannot be completely avoided even if both sides cooperate.
		470
		471	So the only workaround is not to kill your Input Method Servers.
		472
362	=item Rxvt-unicode uses gobs of memory, how can I reduce that?	473	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
363		474
364	Rxvt-unicode tries to obey the rule of not charging you for sth. you	475	Rxvt-unicode tries to obey the rule of not charging you for something you
365	don't use. One thing you should try is to configure out all settings that	476	don't use. One thing you should try is to configure out all settings that
366	you don't need, for example, Xft support is a resource hog by design,	477	you don't need, for example, Xft support is a resource hog by design,
367	when used. Compiling it out ensures that no Xft font will be loaded	478	when used. Compiling it out ensures that no Xft font will be loaded
368	accidentally when rxvt-unicode tries to find a font for your characters.	479	accidentally when rxvt-unicode tries to find a font for your characters.
369		480
…		…
376		487
377	=item Can I speed up Xft rendering somehow?	488	=item Can I speed up Xft rendering somehow?
378		489
379	Yes, the most obvious way to speed it up is to avoid Xft entirely, as	490	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
380	it is simply slow. If you still want Xft fonts you might try to disable	491	it is simply slow. If you still want Xft fonts you might try to disable
381	antialiasing (by appending C<:antialiasing=false>), which saves lots of	492	antialiasing (by appending C<:antialias=false>), which saves lots of
382	memory and also speeds up rendering considerably.	493	memory and also speeds up rendering considerably.
383		494
384	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?	495	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
385		496
386	Rxvt-unicode will use whatever you specify as a font. If it needs to	497	Rxvt-unicode will use whatever you specify as a font. If it needs to
…		…
422	resources (or as long-options).	533	resources (or as long-options).
423		534
424	Here are values that are supposed to resemble a VGA screen,	535	Here are values that are supposed to resemble a VGA screen,
425	including the murky brown that passes for low-intensity yellow:	536	including the murky brown that passes for low-intensity yellow:
426		537
427	URxvt*color0: #000000	538	URxvt.color0: #000000
428	URxvt*color1: #A80000	539	URxvt.color1: #A80000
429	URxvt*color2: #00A800	540	URxvt.color2: #00A800
430	URxvt*color3: #A8A800	541	URxvt.color3: #A8A800
431	URxvt*color4: #0000A8	542	URxvt.color4: #0000A8
432	URxvt*color5: #A800A8	543	URxvt.color5: #A800A8
433	URxvt*color6: #00A8A8	544	URxvt.color6: #00A8A8
434	URxvt*color7: #A8A8A8	545	URxvt.color7: #A8A8A8
435		546
436	URxvt*color8: #000054	547	URxvt.color8: #000054
437	URxvt*color9: #FF0054	548	URxvt.color9: #FF0054
438	URxvt*color10: #00FF54	549	URxvt.color10: #00FF54
439	URxvt*color11: #FFFF54	550	URxvt.color11: #FFFF54
440	URxvt*color12: #0000FF	551	URxvt.color12: #0000FF
441	URxvt*color13: #FF00FF	552	URxvt.color13: #FF00FF
442	URxvt*color14: #00FFFF	553	URxvt.color14: #00FFFF
443	URxvt*color15: #FFFFFF	554	URxvt.color15: #FFFFFF
444		555
445	And here is a more complete set of non-standard colors described as	556	And here is a more complete set of non-standard colors described (not by
446	"pretty girly":	557	me) as "pretty girly".
447		558
448	URxvt.cursorColor: #dc74d1	559	URxvt.cursorColor: #dc74d1
449	URxvt.pointerColor: #dc74d1	560	URxvt.pointerColor: #dc74d1
450	URxvt.background: #0e0e0e	561	URxvt.background: #0e0e0e
451	URxvt.foreground: #4ad5e1	562	URxvt.foreground: #4ad5e1
…		…
462	URxvt.color6: #73f7ff	573	URxvt.color6: #73f7ff
463	URxvt.color14: #73f7ff	574	URxvt.color14: #73f7ff
464	URxvt.color7: #e1dddd	575	URxvt.color7: #e1dddd
465	URxvt.color15: #e1dddd	576	URxvt.color15: #e1dddd
466		577
		578	=item How can I start @@RXVT_NAME@@d in a race-free way?
		579
		580	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
		581	display, create the listening socket and then fork.
		582
467	=item What's with the strange Backspace/Delete key behaviour?	583	=item What's with the strange Backspace/Delete key behaviour?
468		584
469	Assuming that the physical Backspace key corresponds to the	585	Assuming that the physical Backspace key corresponds to the
470	BackSpace keysym (not likely for Linux ... see the following	586	BackSpace keysym (not likely for Linux ... see the following
471	question) there are two standard values that can be used for	587	question) there are two standard values that can be used for
…		…
489		605
490	# use Backspace = ^?	606	# use Backspace = ^?
491	$ stty erase ^?	607	$ stty erase ^?
492	$ @@RXVT_NAME@@	608	$ @@RXVT_NAME@@
493		609
494	Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).	610	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
495		611
496	For an existing rxvt-unicode:	612	For an existing rxvt-unicode:
497		613
498	# use Backspace = ^H	614	# use Backspace = ^H
499	$ stty erase ^H	615	$ stty erase ^H
…		…
508	properly reflects that.	624	properly reflects that.
509		625
510	The Delete key is a another casualty of the ill-defined Backspace problem.	626	The Delete key is a another casualty of the ill-defined Backspace problem.
511	To avoid confusion between the Backspace and Delete keys, the Delete	627	To avoid confusion between the Backspace and Delete keys, the Delete
512	key has been assigned an escape sequence to match the vt100 for Execute	628	key has been assigned an escape sequence to match the vt100 for Execute
513	(ESC[3~) and is in the supplied termcap/terminfo.	629	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
514		630
515	Some other Backspace problems:	631	Some other Backspace problems:
516		632
517	some editors use termcap/terminfo,	633	some editors use termcap/terminfo,
518	some editors (vim I'm told) expect Backspace = ^H,	634	some editors (vim I'm told) expect Backspace = ^H,
…		…
524		640
525	There are some compile-time selections available via configure. Unless	641	There are some compile-time selections available via configure. Unless
526	you have run "configure" with the C<--disable-resources> option you can	642	you have run "configure" with the C<--disable-resources> option you can
527	use the `keysym' resource to alter the keystrings associated with keysyms.	643	use the `keysym' resource to alter the keystrings associated with keysyms.
528		644
529	Here's an example for a URxvt session started using `@@RXVT_NAME@@ -name URxvt'	645	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
530		646
531	URxvt.keysym.Home: \033[1~	647	URxvt.keysym.Home: \033[1~
532	URxvt.keysym.End: \033[4~	648	URxvt.keysym.End: \033[4~
533	URxvt.keysym.C-apostrophe: \033<C-'>	649	URxvt.keysym.C-apostrophe: \033<C-'>
534	URxvt.keysym.C-slash: \033<C-/>	650	URxvt.keysym.C-slash: \033<C-/>
…		…
564		680
565	Rather than have rxvt-unicode try to accommodate all the various possible	681	Rather than have rxvt-unicode try to accommodate all the various possible
566	keyboard mappings, it is better to use `xmodmap' to remap the keys as	682	keyboard mappings, it is better to use `xmodmap' to remap the keys as
567	required for your particular machine.	683	required for your particular machine.
568		684
569	=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?	685	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
570	I need this to decide about setting colors etc.	686	I need this to decide about setting colors etc.
571		687
572	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can	688	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
573	check and see if that is set. Note that several programs, JED, slrn,	689	check and see if that is set. Note that several programs, JED, slrn,
574	Midnight Commander automatically check this variable to decide whether or	690	Midnight Commander automatically check this variable to decide whether or
…		…
611	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be	727	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
612	interested in learning about new and exciting problems (but not FAQs :).	728	interested in learning about new and exciting problems (but not FAQs :).
613		729
614	=back	730	=back
615		731
616	=head1 SYNOPSIS	732	=head1 RXVT TECHNICAL REFERENCE
617
618	# set a new font set
619	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
620
621	# change the locale and tell rxvt-unicode about it
622	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
623
624	# set window title
625	printf '\33]2;%s\007' "new window title"
626		733
627	=head1 DESCRIPTION	734	=head1 DESCRIPTION
628		735
629	The rest of this document describes various technical aspects of	736	The rest of this document describes various technical aspects of
630	B<rxvt-unicode>. First the description of supported command sequences,	737	B<rxvt-unicode>. First the description of supported command sequences,
631	followed by menu and pixmap support and last by a description of all	738	followed by menu and pixmap support and last by a description of all
632	features selectable at C<configure> time.	739	features selectable at C<configure> time.
633		740
634	=head1 RXVT TECHNICAL REFERENCE
635
636	=head1 Definitions	741	=head1 Definitions
637		742
638	=over 4	743	=over 4
639		744
640	=item B<< C<c> >>	745	=item B<< C<c> >>
…		…
768	Single Shift Select of G3 Character Set (SS3): affects next character	873	Single Shift Select of G3 Character Set (SS3): affects next character
769	only I<unimplemented>	874	only I<unimplemented>
770		875
771	=item B<< C<ESC Z> >>	876	=item B<< C<ESC Z> >>
772		877
773	Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option>	878	Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option>
774		879
775	=item B<< C<ESC c> >>	880	=item B<< C<ESC c> >>
776		881
777	Full reset (RIS)	882	Full reset (RIS)
778		883
…		…
782		887
783	=item B<< C<ESC o> >>	888	=item B<< C<ESC o> >>
784		889
785	Invoke the G3 Character Set (LS3)	890	Invoke the G3 Character Set (LS3)
786		891
787	=item B<< C<ESC> ( C> >>	892	=item B<< C<ESC ( C> >>
788		893
789	Designate G0 Character Set (ISO 2022), see below for values of C<C>.	894	Designate G0 Character Set (ISO 2022), see below for values of C<C>.
790		895
791	=item B<< C<ESC> ) C> >>	896	=item B<< C<ESC ) C> >>
792		897
793	Designate G1 Character Set (ISO 2022), see below for values of C<C>.	898	Designate G1 Character Set (ISO 2022), see below for values of C<C>.
794		899
795	=item B<< C<ESC * C> >>	900	=item B<< C<ESC * C> >>
796		901
…		…
937		1042
938	=item B<< C<ESC [ Ps c> >>	1043	=item B<< C<ESC [ Ps c> >>
939		1044
940	Send Device Attributes (DA)	1045	Send Device Attributes (DA)
941	B<< C<Ps = 0> >> (or omitted): request attributes from terminal	1046	B<< C<Ps = 0> >> (or omitted): request attributes from terminal
942	returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video	1047	returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video
943	Option'')	1048	Option'')
944		1049
945	=item B<< C<ESC [ Ps d> >>	1050	=item B<< C<ESC [ Ps d> >>
946		1051
947	Cursor to Line B<< C<Ps> >> (VPA)	1052	Cursor to Line B<< C<Ps> >> (VPA)
…		…
1077	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels	1182	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
1078	B<< C<Ps = 5> >> Raise window	1183	B<< C<Ps = 5> >> Raise window
1079	B<< C<Ps = 6> >> Lower window	1184	B<< C<Ps = 6> >> Lower window
1080	B<< C<Ps = 7> >> Refresh screen once	1185	B<< C<Ps = 7> >> Refresh screen once
1081	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns	1186	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
1082	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>	1187	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
1083	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)	1188	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
1084	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)	1189	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
1085	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)	1190	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
1086	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>	1191	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
1087	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)	1192	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
…		…
1399	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1504	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1400	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1505	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1401	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1506	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>
1402	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1507	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>
1403	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1508	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
1404	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option>	1509	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1405	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1510	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1406	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>	1511	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1407	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>	1512	B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>
1408	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1513	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1409	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (@@RXVT_NAME@@ extension)	1514	B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).
1410	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)	1515	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).
1411	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1516	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1412	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>	1517	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1413	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1518	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1414	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1519	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1415	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1520	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1416	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1521	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1522	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1523	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1417		1524
1418	=end table	1525	=end table
1419		1526
1420	=back	1527	=back
1421		1528
…		…
1473		1580
1474	=item B<< [title:+I<string>] >>	1581	=item B<< [title:+I<string>] >>
1475		1582
1476	set the current menuBar's title to I<string>, which may contain the	1583	set the current menuBar's title to I<string>, which may contain the
1477	following format specifiers:	1584	following format specifiers:
1478	B<%%> : literal B<%> character	1585
1479	B<%n> : rxvt name (as per the B<-name> command-line option)	1586	B<%n> rxvt name (as per the B<-name> command-line option)
1480	B<%v> : rxvt version	1587	B<%v> rxvt version
		1588	B<%%> literal B<%> character
1481		1589
1482	=item B<[done]>	1590	=item B<[done]>
1483		1591
1484	set menuBar access as B<readonly>.	1592	set menuBar access as B<readonly>.
1485	End-of-file tag for B<< [read:+I<file>] >> operations.	1593	End-of-file tag for B<< [read:+I<file>] >> operations.
…		…
1631		1739
1632	As a convenience for the many Emacs-type editors, I<action> may start	1740	As a convenience for the many Emacs-type editors, I<action> may start
1633	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be	1741	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1634	appended if missed from B<M-x> commands.	1742	appended if missed from B<M-x> commands.
1635		1743
1636	As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or	1744	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1637	quick arrow), a B<BEL> (B<^G>) will be appended if needed.	1745	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1638		1746
1639	=over 4	1747	=over 4
1640		1748
1641	=item For example,	1749	=item For example,
…		…
2105	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2213	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2106	styles. The fonts can be set manually or automatically.	2214	styles. The fonts can be set manually or automatically.
2107		2215
2108	=item --with-codesets=NAME,...	2216	=item --with-codesets=NAME,...
2109		2217
2110	Compile in support for additional codeset (encoding) groups (eu, vn are	2218	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2111	always compiled in, which includes most 8-bit character sets). These	2219	are always compiled in, which includes most 8-bit character sets). These
2112	codeset tables are currently only used for driving X11 core fonts, they	2220	codeset tables are used for driving X11 core fonts, they are not required
2113	are not required for Xft fonts. Compiling them in will make your binary	2221	for Xft fonts, although having them compiled in lets rxvt-unicode choose
2114	bigger (together about 700kB), but it doesn't increase memory usage unless	2222	replacement fonts more intelligently. Compiling them in will make your
		2223	binary bigger (all of together cost about 700kB), but it doesn't increase
2115	you use an X11 font requiring one of these encodings.	2224	memory usage unless you use a font requiring one of these encodings.
2116		2225
2117	=begin table	2226	=begin table
2118		2227
2119	all all available codeset groups	2228	all all available codeset groups
2120	zh common chinese encodings	2229	zh common chinese encodings
…		…
2150	composite characters. This is required for proper viewing of text	2259	composite characters. This is required for proper viewing of text
2151	where accents are encoded as seperate unicode characters. This is	2260	where accents are encoded as seperate unicode characters. This is
2152	done by using precomposited characters when available or creating	2261	done by using precomposited characters when available or creating
2153	new pseudo-characters when no precomposed form exists.	2262	new pseudo-characters when no precomposed form exists.
2154		2263
2155	Without --enable-unicode3, the number of additional precomposed	2264	Without --enable-unicode3, the number of additional precomposed characters
2156	characters is rather limited (2048, if this is full, rxvt will use the	2265	is rather limited (2048, if this is full, rxvt-unicode will use the
2157	private use area, extending the number of combinations to 8448). With	2266	private use area, extending the number of combinations to 8448). With
2158	--enable-unicode3, no practical limit exists. This will also enable	2267	--enable-unicode3, no practical limit exists.
2159	storage of characters >65535.	2268
		2269	This option will also enable storage (but not display) of characters
		2270	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2160		2271
2161	The combining table also contains entries for arabic presentation forms,	2272	The combining table also contains entries for arabic presentation forms,
2162	but these are not currently used. Bug me if you want these to be used.	2273	but these are not currently used. Bug me if you want these to be used (and
		2274	tell me how these are to be used...).
2163		2275
2164	=item --enable-fallback(=CLASS)	2276	=item --enable-fallback(=CLASS)
2165		2277
2166	When reading resource settings, also read settings for class CLASS	2278	When reading resource settings, also read settings for class CLASS
2167	(default: Rxvt). To disable resource fallback use --disable-fallback.	2279	(default: Rxvt). To disable resource fallback use --disable-fallback.
…		…
2259	Remove all resources checking.	2371	Remove all resources checking.
2260		2372
2261	=item --enable-xgetdefault	2373	=item --enable-xgetdefault
2262		2374
2263	Make resources checking via XGetDefault() instead of our small	2375	Make resources checking via XGetDefault() instead of our small
2264	version which only checks ~/.Xdefaults, or if that doesn't exist	2376	version which only checks ~/.Xdefaults, or if that doesn't exist then
2265	then ~/.Xresources.	2377	~/.Xresources.
		2378
		2379	Please note that nowadays, things like XIM will automatically pull in and
		2380	use the full X resource manager, so the overhead of using it might be very
		2381	small, if nonexistant.
2266		2382
2267	=item --enable-strings	2383	=item --enable-strings
2268		2384
2269	Add support for our possibly faster memset() function and other	2385	Add support for our possibly faster memset() function and other
2270	various routines, overriding your system's versions which may	2386	various routines, overriding your system's versions which may
…		…
2284		2400
2285	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2401	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2286	in combination with other switches) is:	2402	in combination with other switches) is:
2287		2403
2288	MWM-hints	2404	MWM-hints
		2405	EWMH-hints (pid, utf8 names) and protocols (ping)
2289	seperate underline colour	2406	seperate underline colour
2290	settable border widths and borderless switch	2407	settable border widths and borderless switch
2291	settable extra linespacing	2408	settable extra linespacing
2292	extra window properties (e.g. UTF-8 window names and PID)
2293	iso-14755-2 and -3, and visual feedback	2409	iso-14755-2 and -3, and visual feedback
2294	backindex and forwardindex escape sequence	2410	backindex and forwardindex escape sequence
2295	window op and locale change escape sequences	2411	window op and some xterm/OSC escape sequences
2296	tripleclickwords	2412	tripleclickwords
2297	settable insecure mode	2413	settable insecure mode
		2414	keysym remapping support
		2415	cursor blinking and underline cursor
		2416	-embed and -pty-fd options
2298		2417
2299	=item --enable-iso14755	2418	=item --enable-iso14755
2300		2419
2301	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2420	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2302	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2421	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2341		2460
2342	Add smart growth/shrink behaviour when changing font size via from hot	2461	Add smart growth/shrink behaviour when changing font size via from hot
2343	keys. This should keep in a fixed position the rxvt corner which is	2462	keys. This should keep in a fixed position the rxvt corner which is
2344	closest to a corner of the screen.	2463	closest to a corner of the screen.
2345		2464
2346	=item --enable-cursor-blink
2347
2348	Add support for a blinking cursor.
2349
2350	=item --enable-pointer-blank	2465	=item --enable-pointer-blank
2351		2466
2352	Add support to have the pointer disappear when typing or inactive.	2467	Add support to have the pointer disappear when typing or inactive.
2353		2468
2354	=item --with-name=NAME	2469	=item --with-name=NAME

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.34 by root, Thu Feb 3 10:24:10 2005 UTC vs. Revision 1.60 by root, Fri Jul 29 03:12:10 2005 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.34 by root, Thu Feb 3 10:24:10 2005 UTC vs.
Revision 1.60 by root, Fri Jul 29 03:12:10 2005 UTC