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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.33 by root, Sun Jan 16 18:48:04 2005 UTC vs.
Revision 1.56 by root, Wed Jul 13 01:01:41 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 contains large patches that
		37	considerably change the behaviour of rxvt-unicode. Before reporting a
		38	bug to the original rxvt-unicode author please download and install the
		39	genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to
		40	reproduce the problem. If you cannot, chances are that the problems are
		41	specific to Debian GNU/Linux, in which case it should be reported via the
		42	Debian Bug Tracking System (use C<reportbug> to report the bug).
		43
		44	For other problems that also affect the Debian package, you can and
		45	probably should use the Debian BTS, too, because, after all, it's also a
		46	bug in the Debian version and it serves as a reminder for other users that
		47	might encounter the same issue.
13		48
14	=item When I log-in to another system it tells me about missing terminfo data?	49	=item When I log-in to another system it tells me about missing terminfo data?
15		50
16	The terminal description used by rxvt-unicode is not as widely available	51	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).	52	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	63	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	64	problems arising, which includes wrong keymapping, less and different
30	colours and some refresh errors in fullscreen applications. It's a nice	65	colours and some refresh errors in fullscreen applications. It's a nice
31	quick-and-dirty workaround for rare cases, though.	66	quick-and-dirty workaround for rare cases, though.
32		67
33	If you always want to do this you can either recompile rxvt-unicode with	68	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:	69	can either recompile rxvt-unicode with the desired TERM value or use a
		70	resource to set it:
35		71
36	URxvt.termName: rxvt	72	URxvt.termName: rxvt
37		73
38	If you don't plan to use B<rxvt> (quite common...) you could also replace	74	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.	75	the rxvt terminfo file with the rxvt-unicode one.
40		76
		77	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
		78
41	=item I need a termcap file entry.	79	=item I need a termcap file entry.
		80
		81	One reason you might want this is that some distributions or operating
		82	systems still compile some programs using the long-obsoleted termcap
		83	library (Fedora Core's bash is one example) and rely on a termcap entry
		84	for C<rxvt-unicode>.
42		85
43	You could use rxvt's termcap entry with resonable results in many cases.	86	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	87	You can also create a termcap entry by using terminfo's infocmp program
45	like this:	88	like this:
46		89
47	infocmp -C rxvt-unicode	90	infocmp -C rxvt-unicode
48		91
49	OR you could this termcap entry:	92	Or you could use this termcap entry, generated by the command above:
50		93
51	rxvt-unicode\|rxvt-unicode terminal (X Window System):\	94	rxvt-unicode\|rxvt-unicode terminal (X Window System):\
52	:am:bw:eo:km:mi:ms:xn:xo:\	95	:am:bw:eo:km:mi:ms:xn:xo:\
53	:co#80:it#8:li#24:\	96	:co#80:it#8:li#24:lm#0:\
54	:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\	97	: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:\	98	: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:\	99	: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:\	100	: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:\	101	: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[@:\	102	:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
		103	: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:\	104	: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~:\	105	: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~:\	106	: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:\	107	: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=:\	108	: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:\	109	: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:\	110	: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:\	111	: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:\	112	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
69	:vs=\E[?25h:	113	:vs=\E[?25h:
70		114
71	=item Why does C<ls> no longer have coloured output?	115	=item Why does C<ls> no longer have coloured output?
72		116
73	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	117	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	140	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	141	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	142	I log-in to another system it tells me about missing terminfo data?> on
99	how to do this).	143	how to do this).
100		144
		145	=item My numerical keypad acts weird and generates differing output?
		146
		147	Some Debian GNUL/Linux users seem to have this problem, although no
		148	specific details were reported so far. It is possible that this is caused
		149	by the wrong C<TERM> setting, although the details of wether and how
		150	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		151	keymap. See the answer to the previous question, and please report if that
		152	helped.
		153
101	=item Rxvt-unicode does not seem to understand the selected encoding?	154	=item Rxvt-unicode does not seem to understand the selected encoding?
102		155
103	=item Unicode does not seem to work?	156	=item Unicode does not seem to work?
104		157
105	If you encounter strange problems like typing an accented character but	158	If you encounter strange problems like typing an accented character but
…		…
107	subtly garbled, then you should check your locale settings.	160	subtly garbled, then you should check your locale settings.
108		161
109	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the	162	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	163	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	164	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.	165	something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
113		166
114	The best thing is to fix your startup environment, as you will likely run	167	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.	168	into other problems. If nothing works you can try this in your .profile.
116		169
117	printf '\e]701;%s\007' "$LC_CTYPE"	170	printf '\e]701;%s\007' "$LC_CTYPE"
118		171
119	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not	172	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	173	supported on your systems. Some systems have a C<locale> command which
121	displays this. If it displays sth. like:	174	displays this (also, C<perl -e0> can be used to check locale settings, as
		175	it will complain loudly if it cannot set the locale). If it displays something
		176	like:
122		177
123	locale: Cannot set LC_CTYPE to default locale: ...	178	locale: Cannot set LC_CTYPE to default locale: ...
124		179
125	Then the locale you specified is not supported on your system.	180	Then the locale you specified is not supported on your system.
126		181
…		…
137	your system/os) have specified does not cover all the characters you want	192	your system/os) have specified does not cover all the characters you want
138	to display.	193	to display.
139		194
140	B<rxvt-unicode> makes a best-effort try at finding a replacement	195	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	196	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	197	bad/ugly/wrong. Some fonts have totally strange characters that don't
143	correct glyph at all, and rxvt-unicode lacks the artificial intelligence	198	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	199	intelligence to detect that a specific glyph is wrong: it has to believe
145	the characters it contains indeed look correct.	200	the font that the characters it claims to contain indeed look correct.
146		201
147	In that case, select a font of your taste and add it to the font list,	202	In that case, select a font of your taste and add it to the font list,
148	e.g.:	203	e.g.:
149		204
150	@@RXVT_NAME@@ -fn basefont,font2,font3...	205	@@RXVT_NAME@@ -fn basefont,font2,font3...
…		…
152	When rxvt-unicode sees a character, it will first look at the base	207	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	208	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	209	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.	210	search and use less resources within rxvt-unicode and the X-server.
156		211
157	The only limitation is that all the fonts must not be larger than the base	212	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	213	font, as the base font defines the terminal character cell size, which
159	same due to the way terminals work.	214	must be the same due to the way terminals work.
160		215
161	=item Why do some chinese characters look so different than others?	216	=item Why do some chinese characters look so different than others?
162		217
163	This is because there is a difference between script and language --	218	This is because there is a difference between script and language --
164	rxvt-unicode does not know which language the text that is output	219	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	220	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	221	sees a japanese/chinese character, it might choose a japanese font for
167	it. Subsequent japanese characters will take that font. Now, many chinese	222	display. Subsequent japanese characters will use that font. Now, many
168	characters aren't represented in japanese fonts, so when the first	223	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	224	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	225	-- unfortunately at this point, it will still use the japanese font for
171	japanese characters that are also chinese.	226	chinese characters that are also in the japanese font.
172		227
173	The workaround is easy: just tag a chinese font at the end of your font	228	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	229	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	230	a preference list: If you expect more japanese, list a japanese font
176	first. If you expect more chinese, put a chinese font first.	231	first. If you expect more chinese, put a chinese font first.
177		232
178	In the future it might be possible to switch preferences at runtime (the	233	In the future it might be possible to switch language preferences at
179	internal data structure has no problem with using different fonts for	234	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	235	fonts for the same character at the same time, but no interface for this
181	designed yet).	236	has been designed yet).
		237
		238	Until then, you might get away with switching fonts at runtime (see L<Can
		239	I switch the fonts at runtime?> later in this document).
182		240
183	=item Why does rxvt-unicode sometimes leave pixel droppings?	241	=item Why does rxvt-unicode sometimes leave pixel droppings?
184		242
185	Most fonts were not designed for terminal use, which means that character	243	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	244	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	257	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.	258	might be forced to use a different font.
201		259
202	All of this is not a problem when using X11 core fonts, as their bounding	260	All of this is not a problem when using X11 core fonts, as their bounding
203	box data is correct.	261	box data is correct.
		262
		263	=item On Solaris 9, many line-drawing characters are too wide.
		264
		265	Seems to be a known bug, read
		266	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
		267	following ugly workaround to get non-double-wide-characters working:
		268
		269	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
204		270
205	=item My Compose (Multi_key) key is no longer working.	271	=item My Compose (Multi_key) key is no longer working.
206		272
207	The most common causes for this are that either your locale is not set	273	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	274	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	288	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
223	character and so on.	289	character and so on.
224		290
225	=item How can I keep rxvt-unicode from using reverse video so much?	291	=item How can I keep rxvt-unicode from using reverse video so much?
226		292
227	First of all, make sure you are running with the right terminfo	293	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	294	(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	295	make sure you have specified colours for italic and bold, as otherwise
230	might use reverse video to simulate the effect:	296	rxvt-unicode might use reverse video to simulate the effect:
231		297
232	URxvt*colorBD: white	298	URxvt.colorBD: white
233	URxvt*colorIT: green	299	URxvt.colorIT: green
234		300
235	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?	301	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
236		302
237	For some unexplainable reason, some programs (i.e. irssi) assume a very	303	For some unexplainable reason, some rare programs assume a very weird
238	weird colour palette when confronted with a terminal with more than the	304	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	305	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	306	these programs not to assume non-ISO colours without very good reasons.
241	good reasons.
242		307
243	In the meantime, you can either edit your C<urxvt> terminfo definition to	308	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	309	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
245	but keep you from using other rxvt-unicode features.	310	fix colours but keep you from using other rxvt-unicode features.
246		311
247	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	312	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.
248		313
249	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	314	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
250	in your compile environment, or an implementation that implements it,	315	in your compile environment, or an implementation that implements it,
251	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	316	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
252	B<wchar_t> is represented as unicode.	317	B<wchar_t> is represented as unicode.
253		318
254	As you might have guessed, FreeBSD does neither define this symobl nor	319	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	320	does it support it. Instead, it uses it's own internal representation of
256	B<wchar_t>. This is, of course, completely legal.	321	B<wchar_t>. This is, of course, completely fine with respect to standards.
257		322
		323	However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
		324	C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
		325
258	However, C<__STDC_ISO_10646__> is the only sane way to support	326	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	327	apps in an OS, as using a locale-dependent (and non-standardized)
260	non-standardized) representation of B<wchar_t> makes it impossible to	328	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	329	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	330	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	331	simply are no APIs to convert B<wchar_t> into anything except the current
264	except the current locale encoding.	332	locale encoding.
265		333
266	Some applications (such as the formidable B<mlterm>) work around this	334	Some applications (such as the formidable B<mlterm>) work around this
267	by carrying their own replacement functions for character set handling	335	by carrying their own replacement functions for character set handling
268	with them, and either implementing OS-dependent hacks or doing multiple	336	with them, and either implementing OS-dependent hacks or doing multiple
269	conversions (which is slow and unreliable in case the OS implements	337	conversions (which is slow and unreliable in case the OS implements
270	encodings slightly different than the terminal emulator).	338	encodings slightly different than the terminal emulator).
271		339
272	The rxvt-unicode author insists that the right way to fix this is in the	340	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	341	system libraries once and for all, instead of forcing every app to carry
274	complete replacements.	342	complete replacements for them :)
		343
		344	=item I use Solaris 9 and it doesn't compile/work/etc.
		345
		346	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
		347	problems with C<wcwidth> and a compile problem.
		348
		349	=item How can I use rxvt-unicode under cygwin?
		350
		351	rxvt-unicode should compile and run out of the box on cygwin, using
		352	the X11 libraries that come with cygwin. libW11 emulation is no
		353	longer supported (and makes no sense, either, as it only supported a
		354	single font). I recommend starting the X-server in C<-multiwindow> or
		355	C<-rootless> mode instead, which will result in similar look&feel as the
		356	old libW11 emulation.
		357
		358	At the time of this writing, cygwin didn't seem to support any multi-byte
		359	encodings, so you are likely limited to 8-bit encodings.
275		360
276	=item How does rxvt-unicode determine the encoding to use?	361	=item How does rxvt-unicode determine the encoding to use?
277		362
278	=item Is there an option to switch encodings?	363	=item Is there an option to switch encodings?
279		364
…		…
281	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about	366	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.	367	UTF-8 or any other encodings with respect to terminal I/O.
283		368
284	The reasons is that there exists a perfectly fine mechanism for selecting	369	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	370	the encoding, doing I/O and (most important) communicating this to all
286	applications so everybody agrees on character properties such as width and	371	applications so everybody agrees on character properties such as width
287	code number. This mechanism is the I<locale>.	372	and code number. This mechanism is the I<locale>. Applications not using
		373	that info will have problems (for example, C<xterm> gets the width of
		374	characters wrong as it uses it's own, locale-independent table under all
		375	locales).
288		376
289	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All	377	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	378	programs doing the same (that is, most) will automatically agree in the
291	interpretation of characters.	379	interpretation of characters.
292		380
…		…
299	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms	387	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.	388	(i.e. C<de> or C<german>) are also common.
301		389
302	Rxvt-unicode ignores all other locale categories, and except for	390	Rxvt-unicode ignores all other locale categories, and except for
303	the encoding, ignores country or language-specific settings,	391	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.	392	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		393	rxvt-unicode.
305		394
306	If you want to use a specific encoding you have to make sure you start	395	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.	396	rxvt-unicode with the correct C<LC_CTYPE> category.
308		397
309	=item Can I switch locales at runtime?	398	=item Can I switch locales at runtime?
310		399
311	Yes, using an escape sequence. Try sth. like this, which sets	400	Yes, using an escape sequence. Try something like this, which sets
312	rxvt-unicode's idea of C<LC_CTYPE>.	401	rxvt-unicode's idea of C<LC_CTYPE>.
313		402
314	printf '\e]701;%s\007' ja_JP.SJIS	403	printf '\e]701;%s\007' ja_JP.SJIS
315		404
316	See also the previous question.	405	See also the previous answer.
317		406
318	Sometimes this capability is rather handy when you want to work in one	407	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	408	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	409	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
321	locale supported by xjdic and back later:	410	first switches to a locale supported by xjdic and back later:
322		411
323	printf '\e]701;%s\007' ja_JP.SJIS	412	printf '\e]701;%s\007' ja_JP.SJIS
324	xjdic -js	413	xjdic -js
325	printf '\e]701;%s\007' de_DE.UTF-8	414	printf '\e]701;%s\007' de_DE.UTF-8
326		415
		416	You can also use xterm's C<luit> program, which usually works fine, except
		417	for some locales where character width differs between program- and
		418	rxvt-unicode-locales.
		419
327	=item Can I switch the fonts at runtime?	420	=item Can I switch the fonts at runtime?
328		421
329	Yes, using an escape sequence. Try sth. like this, which has the same	422	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:	423	effect as using the C<-fn> switch, and takes effect immediately:
331		424
332	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	425	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
333		426
334	This is useful if you e.g. work primarily with japanese (and prefer a	427	This is useful if you e.g. work primarily with japanese (and prefer a
…		…
339		432
340	=item Why do italic characters look as if clipped?	433	=item Why do italic characters look as if clipped?
341		434
342	Many fonts have difficulties with italic characters and hinting. For	435	Many fonts have difficulties with italic characters and hinting. For
343	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans	436	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	437	Mono> completely fails in it's italic face. A workaround might be to
345	freetype autohinting, i.e. like this:	438	enable freetype autohinting, i.e. like this:
346		439
347	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	440	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
348	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	441	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
349		442
350	=item My input method wants <some encoding> but I want UTF-8, what can I do?	443	=item My input method wants <some encoding> but I want UTF-8, what can I do?
351		444
352	You can specify separate locales for the input method and the rest of the	445	You can specify separate locales for the input method and the rest of the
353	terminal, using the resource C<imlocale>:	446	terminal, using the resource C<imlocale>:
…		…
357	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still	450	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	451	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	452	input characters outside C<EUC-JP> in a normal way then, as your input
360	method limits you.	453	method limits you.
361		454
		455	=item Rxvt-unicode crashes when the X Input Method changes or exits.
		456
		457	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		458	design. Applications can avoid some crashes at the expense of memory
		459	leaks, and Input Methods can avoid some crashes by careful ordering at
		460	exit time. B<kinput2> (and derived input methods) generally succeeds,
		461	while B<SCIM> (or similar input methods) fails. In the end, however,
		462	crashes cannot be completely avoided even if both sides cooperate.
		463
		464	So the only workaround is not to kill your Input Method Servers.
		465
362	=item Rxvt-unicode uses gobs of memory, how can I reduce that?	466	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
363		467
364	Rxvt-unicode tries to obey the rule of not charging you for sth. you	468	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	469	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,	470	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	471	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.	472	accidentally when rxvt-unicode tries to find a font for your characters.
369		473
…		…
422	resources (or as long-options).	526	resources (or as long-options).
423		527
424	Here are values that are supposed to resemble a VGA screen,	528	Here are values that are supposed to resemble a VGA screen,
425	including the murky brown that passes for low-intensity yellow:	529	including the murky brown that passes for low-intensity yellow:
426		530
427	URxvt*color0: #000000	531	URxvt.color0: #000000
428	URxvt*color1: #A80000	532	URxvt.color1: #A80000
429	URxvt*color2: #00A800	533	URxvt.color2: #00A800
430	URxvt*color3: #A8A800	534	URxvt.color3: #A8A800
431	URxvt*color4: #0000A8	535	URxvt.color4: #0000A8
432	URxvt*color5: #A800A8	536	URxvt.color5: #A800A8
433	URxvt*color6: #00A8A8	537	URxvt.color6: #00A8A8
434	URxvt*color7: #A8A8A8	538	URxvt.color7: #A8A8A8
435		539
436	URxvt*color8: #000054	540	URxvt.color8: #000054
437	URxvt*color9: #FF0054	541	URxvt.color9: #FF0054
438	URxvt*color10: #00FF54	542	URxvt.color10: #00FF54
439	URxvt*color11: #FFFF54	543	URxvt.color11: #FFFF54
440	URxvt*color12: #0000FF	544	URxvt.color12: #0000FF
441	URxvt*color13: #FF00FF	545	URxvt.color13: #FF00FF
442	URxvt*color14: #00FFFF	546	URxvt.color14: #00FFFF
443	URxvt*color15: #FFFFFF	547	URxvt.color15: #FFFFFF
444		548
445	And here is a more complete set of non-standard colors described as	549	And here is a more complete set of non-standard colors described (not by
446	"pretty girly":	550	me) as "pretty girly".
447		551
448	URxvt.cursorColor: #dc74d1	552	URxvt.cursorColor: #dc74d1
449	URxvt.pointerColor: #dc74d1	553	URxvt.pointerColor: #dc74d1
450	URxvt.background: #0e0e0e	554	URxvt.background: #0e0e0e
451	URxvt.foreground: #4ad5e1	555	URxvt.foreground: #4ad5e1
…		…
462	URxvt.color6: #73f7ff	566	URxvt.color6: #73f7ff
463	URxvt.color14: #73f7ff	567	URxvt.color14: #73f7ff
464	URxvt.color7: #e1dddd	568	URxvt.color7: #e1dddd
465	URxvt.color15: #e1dddd	569	URxvt.color15: #e1dddd
466		570
		571	=item How can I start @@RXVT_NAME@@d in a race-free way?
		572
		573	Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a
		574	server that answers @@RXVT_NAME@@c's requests, so it doesn't background
		575	itself.
		576
		577	To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
		578	following method to wait for the startup message before continuing:
		579
		580	{ @@RXVT_NAME@@d & } \| read
		581
467	=item What's with the strange Backspace/Delete key behaviour?	582	=item What's with the strange Backspace/Delete key behaviour?
468		583
469	Assuming that the physical Backspace key corresponds to the	584	Assuming that the physical Backspace key corresponds to the
470	BackSpace keysym (not likely for Linux ... see the following	585	BackSpace keysym (not likely for Linux ... see the following
471	question) there are two standard values that can be used for	586	question) there are two standard values that can be used for
…		…
489		604
490	# use Backspace = ^?	605	# use Backspace = ^?
491	$ stty erase ^?	606	$ stty erase ^?
492	$ @@RXVT_NAME@@	607	$ @@RXVT_NAME@@
493		608
494	Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).	609	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
495		610
496	For an existing rxvt-unicode:	611	For an existing rxvt-unicode:
497		612
498	# use Backspace = ^H	613	# use Backspace = ^H
499	$ stty erase ^H	614	$ stty erase ^H
…		…
508	properly reflects that.	623	properly reflects that.
509		624
510	The Delete key is a another casualty of the ill-defined Backspace problem.	625	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	626	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	627	key has been assigned an escape sequence to match the vt100 for Execute
513	(ESC[3~) and is in the supplied termcap/terminfo.	628	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
514		629
515	Some other Backspace problems:	630	Some other Backspace problems:
516		631
517	some editors use termcap/terminfo,	632	some editors use termcap/terminfo,
518	some editors (vim I'm told) expect Backspace = ^H,	633	some editors (vim I'm told) expect Backspace = ^H,
…		…
524		639
525	There are some compile-time selections available via configure. Unless	640	There are some compile-time selections available via configure. Unless
526	you have run "configure" with the C<--disable-resources> option you can	641	you have run "configure" with the C<--disable-resources> option you can
527	use the `keysym' resource to alter the keystrings associated with keysyms.	642	use the `keysym' resource to alter the keystrings associated with keysyms.
528		643
529	Here's an example for a URxvt session started using `@@RXVT_NAME@@ -name URxvt'	644	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
530		645
531	URxvt*keysym.Home: \e[1~	646	URxvt.keysym.Home: \033[1~
532	URxvt*keysym.End: \e[4~	647	URxvt.keysym.End: \033[4~
533	URxvt*keysym.C-apostrophe: \e<C-'>	648	URxvt.keysym.C-apostrophe: \033<C-'>
534	URxvt*keysym.C-slash: \e<C-/>	649	URxvt.keysym.C-slash: \033<C-/>
535	URxvt*keysym.C-semicolon: \e<C-;>	650	URxvt.keysym.C-semicolon: \033<C-;>
536	URxvt*keysym.C-grave: \e<C-`>	651	URxvt.keysym.C-grave: \033<C-`>
537	URxvt*keysym.C-comma: \e<C-,>	652	URxvt.keysym.C-comma: \033<C-,>
538	URxvt*keysym.C-period: \e<C-.>	653	URxvt.keysym.C-period: \033<C-.>
539	URxvt*keysym.C-0x60: \e<C-`>	654	URxvt.keysym.C-0x60: \033<C-`>
540	URxvt*keysym.C-Tab: \e<C-Tab>	655	URxvt.keysym.C-Tab: \033<C-Tab>
541	URxvt*keysym.C-Return: \e<C-Return>	656	URxvt.keysym.C-Return: \033<C-Return>
542	URxvt*keysym.S-Return: \e<S-Return>	657	URxvt.keysym.S-Return: \033<S-Return>
543	URxvt*keysym.S-space: \e<S-Space>	658	URxvt.keysym.S-space: \033<S-Space>
544	URxvt*keysym.M-Up: \e<M-Up>	659	URxvt.keysym.M-Up: \033<M-Up>
545	URxvt*keysym.M-Down: \e<M-Down>	660	URxvt.keysym.M-Down: \033<M-Down>
546	URxvt*keysym.M-Left: \e<M-Left>	661	URxvt.keysym.M-Left: \033<M-Left>
547	URxvt*keysym.M-Right: \e<M-Right>	662	URxvt.keysym.M-Right: \033<M-Right>
548	URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.>	663	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
549	URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.>	664	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
550	URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007	665	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		666
		667	See some more examples in the documentation for the B<keysym> resource.
551		668
552	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.	669	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
553	How do I make use of them? For example, the Sun Keyboard type 4	670	How do I make use of them? For example, the Sun Keyboard type 4
554	has the following mappings that rxvt-unicode doesn't recognize.	671	has the following mappings that rxvt-unicode doesn't recognize.
555		672
…		…
558	F27 == Home	675	F27 == Home
559	F29 == Prior	676	F29 == Prior
560	F33 == End	677	F33 == End
561	F35 == Next	678	F35 == Next
562		679
563	Rather than have rxvt-unicode try to accommodate all the various possible keyboard	680	Rather than have rxvt-unicode try to accommodate all the various possible
564	mappings, it is better to use `xmodmap' to remap the keys as required for	681	keyboard mappings, it is better to use `xmodmap' to remap the keys as
565	your particular machine.	682	required for your particular machine.
566		683
567	=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?	684	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
568	I need this to decide about setting colors etc.	685	I need this to decide about setting colors etc.
569		686
570	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can	687	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
571	check and see if that is set. Note that several programs, JED, slrn,	688	check and see if that is set. Note that several programs, JED, slrn,
572	Midnight Commander automatically check this variable to decide whether or	689	Midnight Commander automatically check this variable to decide whether or
…		…
609	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be	726	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
610	interested in learning about new and exciting problems (but not FAQs :).	727	interested in learning about new and exciting problems (but not FAQs :).
611		728
612	=back	729	=back
613		730
614	=head1 SYNOPSIS	731	=head1 RXVT TECHNICAL REFERENCE
615
616	# set a new font set
617	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
618
619	# change the locale and tell rxvt-unicode about it
620	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
621
622	# set window title
623	printf '\33]2;%s\007' "new window title"
624		732
625	=head1 DESCRIPTION	733	=head1 DESCRIPTION
626		734
627	The rest of this document describes various technical aspects of	735	The rest of this document describes various technical aspects of
628	B<rxvt-unicode>. First the description of supported command sequences,	736	B<rxvt-unicode>. First the description of supported command sequences,
629	followed by menu and pixmap support and last by a description of all	737	followed by menu and pixmap support and last by a description of all
630	features selectable at C<configure> time.	738	features selectable at C<configure> time.
631		739
632	=head1 RXVT TECHNICAL REFERENCE
633
634	=head1 Definitions	740	=head1 Definitions
635		741
636	=over 4	742	=over 4
637		743
638	=item B<< C<c> >>	744	=item B<< C<c> >>
…		…
766	Single Shift Select of G3 Character Set (SS3): affects next character	872	Single Shift Select of G3 Character Set (SS3): affects next character
767	only I<unimplemented>	873	only I<unimplemented>
768		874
769	=item B<< C<ESC Z> >>	875	=item B<< C<ESC Z> >>
770		876
771	Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option>	877	Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option>
772		878
773	=item B<< C<ESC c> >>	879	=item B<< C<ESC c> >>
774		880
775	Full reset (RIS)	881	Full reset (RIS)
776		882
…		…
780		886
781	=item B<< C<ESC o> >>	887	=item B<< C<ESC o> >>
782		888
783	Invoke the G3 Character Set (LS3)	889	Invoke the G3 Character Set (LS3)
784		890
785	=item B<< C<ESC> ( C> >>	891	=item B<< C<ESC ( C> >>
786		892
787	Designate G0 Character Set (ISO 2022), see below for values of C<C>.	893	Designate G0 Character Set (ISO 2022), see below for values of C<C>.
788		894
789	=item B<< C<ESC> ) C> >>	895	=item B<< C<ESC ) C> >>
790		896
791	Designate G1 Character Set (ISO 2022), see below for values of C<C>.	897	Designate G1 Character Set (ISO 2022), see below for values of C<C>.
792		898
793	=item B<< C<ESC * C> >>	899	=item B<< C<ESC * C> >>
794		900
…		…
935		1041
936	=item B<< C<ESC [ Ps c> >>	1042	=item B<< C<ESC [ Ps c> >>
937		1043
938	Send Device Attributes (DA)	1044	Send Device Attributes (DA)
939	B<< C<Ps = 0> >> (or omitted): request attributes from terminal	1045	B<< C<Ps = 0> >> (or omitted): request attributes from terminal
940	returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video	1046	returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video
941	Option'')	1047	Option'')
942		1048
943	=item B<< C<ESC [ Ps d> >>	1049	=item B<< C<ESC [ Ps d> >>
944		1050
945	Cursor to Line B<< C<Ps> >> (VPA)	1051	Cursor to Line B<< C<Ps> >> (VPA)
…		…
1061		1167
1062	=item B<< C<ESC [ s> >>	1168	=item B<< C<ESC [ s> >>
1063		1169
1064	Save Cursor (SC)	1170	Save Cursor (SC)
1065		1171
		1172	=item B<< C<ESC [ Ps;Pt t> >>
		1173
		1174	Window Operations
		1175
		1176	=begin table
		1177
		1178	B<< C<Ps = 1> >> Deiconify (map) window
		1179	B<< C<Ps = 2> >> Iconify window
		1180	B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X\|Y)
		1181	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
		1182	B<< C<Ps = 5> >> Raise window
		1183	B<< C<Ps = 6> >> Lower window
		1184	B<< C<Ps = 7> >> Refresh screen once
		1185	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
		1186	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
		1187	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
		1188	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
		1189	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
		1190	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
		1191	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
		1192	B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>)
		1193	B<< C<Ps = 24..> >> Set window height to C<Ps> rows
		1194
		1195	=end table
		1196
		1197	=item B<< C<ESC [ u> >>
		1198
		1199	Restore Cursor
		1200
1066	=item B<< C<ESC [ Ps x> >>	1201	=item B<< C<ESC [ Ps x> >>
1067		1202
1068	Request Terminal Parameters (DECREQTPARM)	1203	Request Terminal Parameters (DECREQTPARM)
1069
1070	=item B<< C<ESC [ u> >>
1071
1072	Restore Cursor
1073		1204
1074	=back	1205	=back
1075		1206
1076	X<PrivateModes>	1207	X<PrivateModes>
1077		1208
…		…
1372	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1503	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1373	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1504	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1374	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1505	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>
1375	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1506	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>
1376	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1507	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
1377	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option>	1508	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1378	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1509	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1379	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>	1510	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1380	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> >>	1511	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> >>
1381	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1512	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1382	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)	1513	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).
1383	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)	1514	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).
1384	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1515	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1385	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >>	1516	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1386	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1517	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
1387	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1518	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1388	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1519	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1389	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.	1520	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
		1521	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1522	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1390		1523
1391	=end table	1524	=end table
1392		1525
1393	=back	1526	=back
1394		1527
…		…
1446		1579
1447	=item B<< [title:+I<string>] >>	1580	=item B<< [title:+I<string>] >>
1448		1581
1449	set the current menuBar's title to I<string>, which may contain the	1582	set the current menuBar's title to I<string>, which may contain the
1450	following format specifiers:	1583	following format specifiers:
1451	B<%%> : literal B<%> character	1584
1452	B<%n> : rxvt name (as per the B<-name> command-line option)	1585	B<%n> rxvt name (as per the B<-name> command-line option)
1453	B<%v> : rxvt version	1586	B<%v> rxvt version
		1587	B<%%> literal B<%> character
1454		1588
1455	=item B<[done]>	1589	=item B<[done]>
1456		1590
1457	set menuBar access as B<readonly>.	1591	set menuBar access as B<readonly>.
1458	End-of-file tag for B<< [read:+I<file>] >> operations.	1592	End-of-file tag for B<< [read:+I<file>] >> operations.
…		…
1604		1738
1605	As a convenience for the many Emacs-type editors, I<action> may start	1739	As a convenience for the many Emacs-type editors, I<action> may start
1606	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be	1740	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1607	appended if missed from B<M-x> commands.	1741	appended if missed from B<M-x> commands.
1608		1742
1609	As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or	1743	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1610	quick arrow), a B<BEL> (B<^G>) will be appended if needed.	1744	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1611		1745
1612	=over 4	1746	=over 4
1613		1747
1614	=item For example,	1748	=item For example,
…		…
2078	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font	2212	Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2079	styles. The fonts can be set manually or automatically.	2213	styles. The fonts can be set manually or automatically.
2080		2214
2081	=item --with-codesets=NAME,...	2215	=item --with-codesets=NAME,...
2082		2216
2083	Compile in support for additional codeset (encoding) groups (eu, vn are	2217	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2084	always compiled in, which includes most 8-bit character sets). These	2218	are always compiled in, which includes most 8-bit character sets). These
2085	codeset tables are currently only used for driving X11 core fonts, they	2219	codeset tables are used for driving X11 core fonts, they are not required
2086	are not required for Xft fonts. Compiling them in will make your binary	2220	for Xft fonts, although having them compiled in lets rxvt-unicode choose
2087	bigger (together about 700kB), but it doesn't increase memory usage unless	2221	replacement fonts more intelligently. Compiling them in will make your
		2222	binary bigger (all of together cost about 700kB), but it doesn't increase
2088	you use an X11 font requiring one of these encodings.	2223	memory usage unless you use a font requiring one of these encodings.
2089		2224
2090	=begin table	2225	=begin table
2091		2226
2092	all all available codeset groups	2227	all all available codeset groups
2093	zh common chinese encodings	2228	zh common chinese encodings
…		…
2123	composite characters. This is required for proper viewing of text	2258	composite characters. This is required for proper viewing of text
2124	where accents are encoded as seperate unicode characters. This is	2259	where accents are encoded as seperate unicode characters. This is
2125	done by using precomposited characters when available or creating	2260	done by using precomposited characters when available or creating
2126	new pseudo-characters when no precomposed form exists.	2261	new pseudo-characters when no precomposed form exists.
2127		2262
2128	Without --enable-unicode3, the number of additional precomposed	2263	Without --enable-unicode3, the number of additional precomposed characters
2129	characters is rather limited (2048, if this is full, rxvt will use the	2264	is rather limited (2048, if this is full, rxvt-unicode will use the
2130	private use area, extending the number of combinations to 8448). With	2265	private use area, extending the number of combinations to 8448). With
2131	--enable-unicode3, no practical limit exists. This will also enable	2266	--enable-unicode3, no practical limit exists.
2132	storage of characters >65535.	2267
		2268	This option will also enable storage (but not display) of characters
		2269	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2133		2270
2134	The combining table also contains entries for arabic presentation forms,	2271	The combining table also contains entries for arabic presentation forms,
2135	but these are not currently used. Bug me if you want these to be used.	2272	but these are not currently used. Bug me if you want these to be used (and
		2273	tell me how these are to be used...).
2136		2274
2137	=item --enable-fallback(=CLASS)	2275	=item --enable-fallback(=CLASS)
2138		2276
2139	When reading resource settings, also read settings for class CLASS	2277	When reading resource settings, also read settings for class CLASS
2140	(default: Rxvt). To disable resource fallback use --disable-fallback.	2278	(default: Rxvt). To disable resource fallback use --disable-fallback.
…		…
2232	Remove all resources checking.	2370	Remove all resources checking.
2233		2371
2234	=item --enable-xgetdefault	2372	=item --enable-xgetdefault
2235		2373
2236	Make resources checking via XGetDefault() instead of our small	2374	Make resources checking via XGetDefault() instead of our small
2237	version which only checks ~/.Xdefaults, or if that doesn't exist	2375	version which only checks ~/.Xdefaults, or if that doesn't exist then
2238	then ~/.Xresources.	2376	~/.Xresources.
		2377
		2378	Please note that nowadays, things like XIM will automatically pull in and
		2379	use the full X resource manager, so the overhead of using it might be very
		2380	small, if nonexistant.
2239		2381
2240	=item --enable-strings	2382	=item --enable-strings
2241		2383
2242	Add support for our possibly faster memset() function and other	2384	Add support for our possibly faster memset() function and other
2243	various routines, overriding your system's versions which may	2385	various routines, overriding your system's versions which may
…		…
2257		2399
2258	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2400	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2259	in combination with other switches) is:	2401	in combination with other switches) is:
2260		2402
2261	MWM-hints	2403	MWM-hints
		2404	EWMH-hints (pid, utf8 names) and protocols (ping)
2262	seperate underline colour	2405	seperate underline colour
2263	settable border widths and borderless switch	2406	settable border widths and borderless switch
2264	settable extra linespacing	2407	settable extra linespacing
2265	extra window properties (e.g. UTF-8 window names and PID)
2266	iso-14755-2 and -3, and visual feedback	2408	iso-14755-2 and -3, and visual feedback
2267	backindex and forwardindex escape sequence	2409	backindex and forwardindex escape sequence
2268	window op and locale change escape sequences	2410	window op and some xterm/OSC escape sequences
2269	tripleclickwords	2411	tripleclickwords
2270	settable insecure mode	2412	settable insecure mode
		2413	keysym remapping support
		2414	cursor blinking and underline cursor
		2415	-embed and -pty-fd options
2271		2416
2272	=item --enable-iso14755	2417	=item --enable-iso14755
2273		2418
2274	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2419	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2275	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2420	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2314		2459
2315	Add smart growth/shrink behaviour when changing font size via from hot	2460	Add smart growth/shrink behaviour when changing font size via from hot
2316	keys. This should keep in a fixed position the rxvt corner which is	2461	keys. This should keep in a fixed position the rxvt corner which is
2317	closest to a corner of the screen.	2462	closest to a corner of the screen.
2318		2463
2319	=item --enable-cursor-blink
2320
2321	Add support for a blinking cursor.
2322
2323	=item --enable-pointer-blank	2464	=item --enable-pointer-blank
2324		2465
2325	Add support to have the pointer disappear when typing or inactive.	2466	Add support to have the pointer disappear when typing or inactive.
2326		2467
2327	=item --with-name=NAME	2468	=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.33 by root, Sun Jan 16 18:48:04 2005 UTC vs. Revision 1.56 by root, Wed Jul 13 01:01:41 2005 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.33 by root, Sun Jan 16 18:48:04 2005 UTC vs.
Revision 1.56 by root, Wed Jul 13 01:01:41 2005 UTC