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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.29 by root, Wed Dec 29 19:17:18 2004 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 How can I configure rxvt-unicode so that it looks similar to the original rxvt?	121	=item Why does C<ls> no longer have coloured output?
72		122
73	Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode	123	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
74	behave similar to the original rxvt:	124	decide wether a terminal has colour, but uses it's own configuration
		125	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
		126	with most other terminals supporting colour). Either add:
75		127
76	URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1	128	TERM rxvt-unicode
77	URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1	129
		130	to C</etc/DIR_COLORS> or simply add:
		131
		132	alias ls='ls --color=auto'
		133
		134	to your C<.profile> or C<.bashrc>.
		135
		136	=item Why doesn't vim/emacs etc. use the 88 colour mode?
		137
		138	=item Why doesn't vim/emacs etc. make use of italic?
		139
		140	=item Why are the secondary screen-related options not working properly?
		141
		142	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
		143	distributions (most notably Debian GNU/Linux) break rxvt-unicode
		144	by setting C<TERM> to C<rxvt>, which doesn't have these extra
		145	features. Unfortunately, some of these (most notably, again, Debian
		146	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
		147	file, so you will need to install it on your own (See the question B<When
		148	I log-in to another system it tells me about missing terminfo data?> on
		149	how to do this).
		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.
78		159
79	=item Rxvt-unicode does not seem to understand the selected encoding?	160	=item Rxvt-unicode does not seem to understand the selected encoding?
80		161
81	=item Unicode does not seem to work?	162	=item Unicode does not seem to work?
82		163
…		…
85	subtly garbled, then you should check your locale settings.	166	subtly garbled, then you should check your locale settings.
86		167
87	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
88	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
89	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
90	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.
91		172
92	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
93	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.
94		175
95	printf '\e]701;%s\007' "$LC_CTYPE"	176	printf '\e]701;%s\007' "$LC_CTYPE"
96		177
97	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
98	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
99	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:
100		183
101	locale: Cannot set LC_CTYPE to default locale: ...	184	locale: Cannot set LC_CTYPE to default locale: ...
102		185
103	Then the locale you specified is not supported on your system.	186	Then the locale you specified is not supported on your system.
104		187
…		…
115	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
116	to display.	199	to display.
117		200
118	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
119	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
120	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
121	correct glyph at all, and rxvt-unicode lacks the artificial intelligence	204	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
122	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
123	the characters it contains indeed look correct.	206	the font that the characters it claims to contain indeed look correct.
124		207
125	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,
126	e.g.:	209	e.g.:
127		210
128	@@RXVT_NAME@@ -fn basefont,font2,font3...	211	@@RXVT_NAME@@ -fn basefont,font2,font3...
…		…
130	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
131	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
132	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
133	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.
134		217
135	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
136	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
137	same due to the way terminals work.	220	must be the same due to the way terminals work.
138		221
139	=item Why do some chinese characters look so different than others?	222	=item Why do some chinese characters look so different than others?
140		223
141	This is because there is a difference between script and language --	224	This is because there is a difference between script and language --
142	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,
143	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
144	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
145	it. Subsequent japanese characters will take that font. Now, many chinese	228	display. Subsequent japanese characters will use that font. Now, many
146	characters aren't represented in japanese fonts, so when the first	229	chinese characters aren't represented in japanese fonts, so when the first
147	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
148	-- 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
149	japanese characters that are also chinese.	232	chinese characters that are also in the japanese font.
150		233
151	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
152	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
153	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
154	first. If you expect more chinese, put a chinese font first.	237	first. If you expect more chinese, put a chinese font first.
155		238
156	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
157	internal data structure has no problem with using different fonts for	240	runtime (the internal data structure has no problem with using different
158	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
159	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).
160		246
161	=item Why does rxvt-unicode sometimes leave pixel droppings?	247	=item Why does rxvt-unicode sometimes leave pixel droppings?
162		248
163	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
164	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
…		…
170	however: Xft fonts often draw glyphs larger than their acclaimed bounding	256	however: Xft fonts often draw glyphs larger than their acclaimed bounding
171	box, and rxvt-unicode has no way of detecting this (the correct way is to	257	box, and rxvt-unicode has no way of detecting this (the correct way is to
172	ask for the character bounding box, which unfortunately is wrong in these	258	ask for the character bounding box, which unfortunately is wrong in these
173	cases).	259	cases).
174		260
175	It's not clear (to me at least), wether this is a bug in Xft, freetype, or	261	It's not clear (to me at least), wether this is a bug in Xft, freetype,
176	the respective font. If you encounter this problem there is no way to work	262	or the respective font. If you encounter this problem you might try using
177	around this except by using a different font.	263	the C<-lsp> option to give the font more height. If that doesn't work, you
		264	might be forced to use a different font.
178		265
179	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
180	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)
181		276
182	=item My Compose (Multi_key) key is no longer working.	277	=item My Compose (Multi_key) key is no longer working.
183		278
184	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
185	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
…		…
199	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
200	character and so on.	295	character and so on.
201		296
202	=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?
203		298
204	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
205	(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
206	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
207	might use reverse video to simulate the effect:	302	rxvt-unicode might use reverse video to simulate the effect:
208		303
209	URxvt*colorBD: white	304	URxvt.colorBD: white
210	URxvt*colorIT: green	305	URxvt.colorIT: green
211		306
212	=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?
213		308
214	For some unexplainable reason, some programs (i.e. irssi) assume a very	309	For some unexplainable reason, some rare programs assume a very weird
215	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
216	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
217	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.
218	good reasons.
219		313
220	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
221	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
222	but keep you from using other rxvt-unicode features.	316	fix colours but keep you from using other rxvt-unicode features.
223		317
224	=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.
225		319
226	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
227	in your compile environment, or an implementation that implements it,	321	in your compile environment, or an implementation that implements it,
228	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
229	B<wchar_t> is represented as unicode.	323	B<wchar_t> is represented as unicode.
230		324
231	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
232	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
233	B<wchar_t>. This is, of course, completely legal.	327	B<wchar_t>. This is, of course, completely fine with respect to standards.
234		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
235	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
236	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)
237	non-standardized) representation of B<wchar_t> makes it impossible to	334	representation of B<wchar_t> makes it impossible to convert between
238	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
239	other encoding without implementing OS-specific-wrappers for each and	336	without implementing OS-specific-wrappers for each and every locale. There
240	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
241	except the current locale encoding.	338	locale encoding.
242		339
243	Some applications (such as the formidable B<mlterm>) work around this	340	Some applications (such as the formidable B<mlterm>) work around this
244	by carrying their own replacement functions for character set handling	341	by carrying their own replacement functions for character set handling
245	with them, and either implementing OS-dependent hacks or doing multiple	342	with them, and either implementing OS-dependent hacks or doing multiple
246	conversions (which is slow and unreliable in case the OS implements	343	conversions (which is slow and unreliable in case the OS implements
247	encodings slightly different than the terminal emulator).	344	encodings slightly different than the terminal emulator).
248		345
249	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
250	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
251	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.
252		367
253	=item How does rxvt-unicode determine the encoding to use?	368	=item How does rxvt-unicode determine the encoding to use?
254		369
255	=item Is there an option to switch encodings?	370	=item Is there an option to switch encodings?
256		371
…		…
258	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
259	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.
260		375
261	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
262	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
263	applications so everybody agrees on character properties such as width and	378	applications so everybody agrees on character properties such as width
264	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).
265		383
266	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
267	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
268	interpretation of characters.	386	interpretation of characters.
269		387
…		…
276	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
277	(i.e. C<de> or C<german>) are also common.	395	(i.e. C<de> or C<german>) are also common.
278		396
279	Rxvt-unicode ignores all other locale categories, and except for	397	Rxvt-unicode ignores all other locale categories, and except for
280	the encoding, ignores country or language-specific settings,	398	the encoding, ignores country or language-specific settings,
281	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.
282		401
283	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
284	rxvt-unicode with the correct C<LC_CTYPE> category.	403	rxvt-unicode with the correct C<LC_CTYPE> category.
285		404
286	=item Can I switch locales at runtime?	405	=item Can I switch locales at runtime?
287		406
288	Yes, using an escape sequence. Try sth. like this, which sets	407	Yes, using an escape sequence. Try something like this, which sets
289	rxvt-unicode's idea of C<LC_CTYPE>.	408	rxvt-unicode's idea of C<LC_CTYPE>.
290		409
291	printf '\e]701;%s\007' ja_JP.SJIS	410	printf '\e]701;%s\007' ja_JP.SJIS
292		411
293	See also the previous question.	412	See also the previous answer.
294		413
295	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
296	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
297	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
298	locale supported by xjdic and back later:	417	first switches to a locale supported by xjdic and back later:
299		418
300	printf '\e]701;%s\007' ja_JP.SJIS	419	printf '\e]701;%s\007' ja_JP.SJIS
301	xjdic -js	420	xjdic -js
302	printf '\e]701;%s\007' de_DE.UTF-8	421	printf '\e]701;%s\007' de_DE.UTF-8
303		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
304	=item Can I switch the fonts at runtime?	427	=item Can I switch the fonts at runtime?
305		428
306	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
307	effect as using the C<-fn> switch, and takes effect immediately:	430	effect as using the C<-fn> switch, and takes effect immediately:
308		431
309	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"	432	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
310		433
311	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
…		…
316		439
317	=item Why do italic characters look as if clipped?	440	=item Why do italic characters look as if clipped?
318		441
319	Many fonts have difficulties with italic characters and hinting. For	442	Many fonts have difficulties with italic characters and hinting. For
320	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
321	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
322	freetype autohinting, i.e. like this:	445	enable freetype autohinting, i.e. like this:
323		446
324	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true	447	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
325	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true	448	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
326		449
327	=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?
328		451
329	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
330	terminal, using the resource C<imlocale>:	453	terminal, using the resource C<imlocale>:
…		…
334	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
335	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
336	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
337	method limits you.	460	method limits you.
338		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
339	=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?
340		474
341	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
342	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
343	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,
344	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
345	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.
346		480
…		…
353		487
354	=item Can I speed up Xft rendering somehow?	488	=item Can I speed up Xft rendering somehow?
355		489
356	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
357	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
358	antialiasing (by appending C<:antialiasing=false>), which saves lots of	492	antialiasing (by appending C<:antialias=false>), which saves lots of
359	memory and also speeds up rendering considerably.	493	memory and also speeds up rendering considerably.
360		494
361	=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?
362		496
363	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
…		…
399	resources (or as long-options).	533	resources (or as long-options).
400		534
401	Here are values that are supposed to resemble a VGA screen,	535	Here are values that are supposed to resemble a VGA screen,
402	including the murky brown that passes for low-intensity yellow:	536	including the murky brown that passes for low-intensity yellow:
403		537
404	URxvt*color0: #000000	538	URxvt.color0: #000000
405	URxvt*color1: #A80000	539	URxvt.color1: #A80000
406	URxvt*color2: #00A800	540	URxvt.color2: #00A800
407	URxvt*color3: #A8A800	541	URxvt.color3: #A8A800
408	URxvt*color4: #0000A8	542	URxvt.color4: #0000A8
409	URxvt*color5: #A800A8	543	URxvt.color5: #A800A8
410	URxvt*color6: #00A8A8	544	URxvt.color6: #00A8A8
411	URxvt*color7: #A8A8A8	545	URxvt.color7: #A8A8A8
412		546
413	URxvt*color8: #000054	547	URxvt.color8: #000054
414	URxvt*color9: #FF0054	548	URxvt.color9: #FF0054
415	URxvt*color10: #00FF54	549	URxvt.color10: #00FF54
416	URxvt*color11: #FFFF54	550	URxvt.color11: #FFFF54
417	URxvt*color12: #0000FF	551	URxvt.color12: #0000FF
418	URxvt*color13: #FF00FF	552	URxvt.color13: #FF00FF
419	URxvt*color14: #00FFFF	553	URxvt.color14: #00FFFF
420	URxvt*color15: #FFFFFF	554	URxvt.color15: #FFFFFF
421		555
422	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
423	"pretty girly":	557	me) as "pretty girly".
424		558
425	URxvt.cursorColor: #dc74d1	559	URxvt.cursorColor: #dc74d1
426	URxvt.pointerColor: #dc74d1	560	URxvt.pointerColor: #dc74d1
427	URxvt.background: #0e0e0e	561	URxvt.background: #0e0e0e
428	URxvt.foreground: #4ad5e1	562	URxvt.foreground: #4ad5e1
…		…
439	URxvt.color6: #73f7ff	573	URxvt.color6: #73f7ff
440	URxvt.color14: #73f7ff	574	URxvt.color14: #73f7ff
441	URxvt.color7: #e1dddd	575	URxvt.color7: #e1dddd
442	URxvt.color15: #e1dddd	576	URxvt.color15: #e1dddd
443		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
444	=item What's with the strange Backspace/Delete key behaviour?	583	=item What's with the strange Backspace/Delete key behaviour?
445		584
446	Assuming that the physical Backspace key corresponds to the	585	Assuming that the physical Backspace key corresponds to the
447	BackSpace keysym (not likely for Linux ... see the following	586	BackSpace keysym (not likely for Linux ... see the following
448	question) there are two standard values that can be used for	587	question) there are two standard values that can be used for
…		…
466		605
467	# use Backspace = ^?	606	# use Backspace = ^?
468	$ stty erase ^?	607	$ stty erase ^?
469	$ @@RXVT_NAME@@	608	$ @@RXVT_NAME@@
470		609
471	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).
472		611
473	For an existing rxvt-unicode:	612	For an existing rxvt-unicode:
474		613
475	# use Backspace = ^H	614	# use Backspace = ^H
476	$ stty erase ^H	615	$ stty erase ^H
…		…
485	properly reflects that.	624	properly reflects that.
486		625
487	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.
488	To avoid confusion between the Backspace and Delete keys, the Delete	627	To avoid confusion between the Backspace and Delete keys, the Delete
489	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
490	(ESC[3~) and is in the supplied termcap/terminfo.	629	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
491		630
492	Some other Backspace problems:	631	Some other Backspace problems:
493		632
494	some editors use termcap/terminfo,	633	some editors use termcap/terminfo,
495	some editors (vim I'm told) expect Backspace = ^H,	634	some editors (vim I'm told) expect Backspace = ^H,
…		…
499		638
500	=item I don't like the key-bindings. How do I change them?	639	=item I don't like the key-bindings. How do I change them?
501		640
502	There are some compile-time selections available via configure. Unless	641	There are some compile-time selections available via configure. Unless
503	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
504	use the `keysym' resource to alter the keystrings associated with keysym	643	use the `keysym' resource to alter the keystrings associated with keysyms.
505	0xFF00 - 0xFFFF (function, cursor keys, etc).
506		644
507	Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270'	645	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
508		646
509	!# ----- special uses ------:	647	URxvt.keysym.Home: \033[1~
510	! tn3270 login, remap function and arrow keys.	648	URxvt.keysym.End: \033[4~
511	tn3270font: clean-bold----15-*	649	URxvt.keysym.C-apostrophe: \033<C-'>
		650	URxvt.keysym.C-slash: \033<C-/>
		651	URxvt.keysym.C-semicolon: \033<C-;>
		652	URxvt.keysym.C-grave: \033<C-`>
		653	URxvt.keysym.C-comma: \033<C-,>
		654	URxvt.keysym.C-period: \033<C-.>
		655	URxvt.keysym.C-0x60: \033<C-`>
		656	URxvt.keysym.C-Tab: \033<C-Tab>
		657	URxvt.keysym.C-Return: \033<C-Return>
		658	URxvt.keysym.S-Return: \033<S-Return>
		659	URxvt.keysym.S-space: \033<S-Space>
		660	URxvt.keysym.M-Up: \033<M-Up>
		661	URxvt.keysym.M-Down: \033<M-Down>
		662	URxvt.keysym.M-Left: \033<M-Left>
		663	URxvt.keysym.M-Right: \033<M-Right>
		664	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		665	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		666	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
512		667
513	! keysym - used by rxvt only	668	See some more examples in the documentation for the B<keysym> resource.
514	! Delete - ^D
515	tn3270*keysym.0xFFFF: \004
516
517	! Home - ^A
518	tn3270*keysym.0xFF50: \001
519	! Left - ^B
520	tn3270*keysym.0xFF51: \002
521	! Up - ^P
522	tn3270*keysym.0xFF52: \020
523	! Right - ^F
524	tn3270*keysym.0xFF53: \006
525	! Down - ^N
526	tn3270*keysym.0xFF54: \016
527	! End - ^E
528	tn3270*keysym.0xFF57: \005
529
530	! F1 - F12
531	tn3270*keysym.0xFFBE: \e1
532	tn3270*keysym.0xFFBF: \e2
533	tn3270*keysym.0xFFC0: \e3
534	tn3270*keysym.0xFFC1: \e4
535	tn3270*keysym.0xFFC2: \e5
536	tn3270*keysym.0xFFC3: \e6
537	tn3270*keysym.0xFFC4: \e7
538	tn3270*keysym.0xFFC5: \e8
539	tn3270*keysym.0xFFC6: \e9
540	tn3270*keysym.0xFFC7: \e0
541	tn3270*keysym.0xFFC8: \e-
542	tn3270*keysym.0xFFC9: \e=
543
544	! map Prior/Next to F7/F8
545	tn3270*keysym.0xFF55: \e7
546	tn3270*keysym.0xFF56: \e8
547		669
548	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.	670	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
549	How do I make use of them? For example, the Sun Keyboard type 4	671	How do I make use of them? For example, the Sun Keyboard type 4
550	has the following mappings that rxvt-unicode doesn't recognize.	672	has the following mappings that rxvt-unicode doesn't recognize.
551		673
…		…
554	F27 == Home	676	F27 == Home
555	F29 == Prior	677	F29 == Prior
556	F33 == End	678	F33 == End
557	F35 == Next	679	F35 == Next
558		680
559	Rather than have rxvt-unicode try to accommodate all the various possible keyboard	681	Rather than have rxvt-unicode try to accommodate all the various possible
560	mappings, it is better to use `xmodmap' to remap the keys as required for	682	keyboard mappings, it is better to use `xmodmap' to remap the keys as
561	your particular machine.	683	required for your particular machine.
562		684
563	=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?
564	I need this to decide about setting colors etc.	686	I need this to decide about setting colors etc.
565		687
566	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
567	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,
568	Midnight Commander automatically check this variable to decide whether or	690	Midnight Commander automatically check this variable to decide whether or
…		…
605	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
606	interested in learning about new and exciting problems (but not FAQs :).	728	interested in learning about new and exciting problems (but not FAQs :).
607		729
608	=back	730	=back
609		731
610	=head1 SYNOPSIS	732	=head1 RXVT TECHNICAL REFERENCE
611
612	# set a new font set
613	printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
614
615	# change the locale and tell rxvt-unicode about it
616	export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
617
618	# set window title
619	printf '\33]2;%s\007' "new window title"
620		733
621	=head1 DESCRIPTION	734	=head1 DESCRIPTION
622		735
623	The rest of this document describes various technical aspects of	736	The rest of this document describes various technical aspects of
624	B<rxvt-unicode>. First the description of supported command sequences,	737	B<rxvt-unicode>. First the description of supported command sequences,
625	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
626	features selectable at C<configure> time.	739	features selectable at C<configure> time.
627		740
628	=head1 RXVT TECHNICAL REFERENCE
629
630	=head1 Definitions	741	=head1 Definitions
631		742
632	=over 4	743	=over 4
633		744
634	=item B<< C<c> >>	745	=item B<< C<c> >>
…		…
762	Single Shift Select of G3 Character Set (SS3): affects next character	873	Single Shift Select of G3 Character Set (SS3): affects next character
763	only I<unimplemented>	874	only I<unimplemented>
764		875
765	=item B<< C<ESC Z> >>	876	=item B<< C<ESC Z> >>
766		877
767	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>
768		879
769	=item B<< C<ESC c> >>	880	=item B<< C<ESC c> >>
770		881
771	Full reset (RIS)	882	Full reset (RIS)
772		883
…		…
776		887
777	=item B<< C<ESC o> >>	888	=item B<< C<ESC o> >>
778		889
779	Invoke the G3 Character Set (LS3)	890	Invoke the G3 Character Set (LS3)
780		891
781	=item B<< C<ESC> ( C> >>	892	=item B<< C<ESC ( C> >>
782		893
783	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>.
784		895
785	=item B<< C<ESC> ) C> >>	896	=item B<< C<ESC ) C> >>
786		897
787	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>.
788		899
789	=item B<< C<ESC * C> >>	900	=item B<< C<ESC * C> >>
790		901
…		…
931		1042
932	=item B<< C<ESC [ Ps c> >>	1043	=item B<< C<ESC [ Ps c> >>
933		1044
934	Send Device Attributes (DA)	1045	Send Device Attributes (DA)
935	B<< C<Ps = 0> >> (or omitted): request attributes from terminal	1046	B<< C<Ps = 0> >> (or omitted): request attributes from terminal
936	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
937	Option'')	1048	Option'')
938		1049
939	=item B<< C<ESC [ Ps d> >>	1050	=item B<< C<ESC [ Ps d> >>
940		1051
941	Cursor to Line B<< C<Ps> >> (VPA)	1052	Cursor to Line B<< C<Ps> >> (VPA)
…		…
1057		1168
1058	=item B<< C<ESC [ s> >>	1169	=item B<< C<ESC [ s> >>
1059		1170
1060	Save Cursor (SC)	1171	Save Cursor (SC)
1061		1172
		1173	=item B<< C<ESC [ Ps;Pt t> >>
		1174
		1175	Window Operations
		1176
		1177	=begin table
		1178
		1179	B<< C<Ps = 1> >> Deiconify (map) window
		1180	B<< C<Ps = 2> >> Iconify window
		1181	B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X\|Y)
		1182	B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels
		1183	B<< C<Ps = 5> >> Raise window
		1184	B<< C<Ps = 6> >> Lower window
		1185	B<< C<Ps = 7> >> Refresh screen once
		1186	B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns
		1187	B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>)
		1188	B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>)
		1189	B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>)
		1190	B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>)
		1191	B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9>
		1192	B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>)
		1193	B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>)
		1194	B<< C<Ps = 24..> >> Set window height to C<Ps> rows
		1195
		1196	=end table
		1197
		1198	=item B<< C<ESC [ u> >>
		1199
		1200	Restore Cursor
		1201
1062	=item B<< C<ESC [ Ps x> >>	1202	=item B<< C<ESC [ Ps x> >>
1063		1203
1064	Request Terminal Parameters (DECREQTPARM)	1204	Request Terminal Parameters (DECREQTPARM)
1065
1066	=item B<< C<ESC [ u> >>
1067
1068	Restore Cursor
1069		1205
1070	=back	1206	=back
1071		1207
1072	X<PrivateModes>	1208	X<PrivateModes>
1073		1209
…		…
1368	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> >>
1369	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> >>
1370	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> >>
1371	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> >>
1372	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1508	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>
1373	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> >>.
1374	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>
1375	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> >>.
1376	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> >>
1377	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> >>
1378	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).
1379	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).
1380	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> >>
1381	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).
1382	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>.
1383	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).
1384	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).
1385	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).
1386		1524
1387	=end table	1525	=end table
1388		1526
1389	=back	1527	=back
1390		1528
…		…
1442		1580
1443	=item B<< [title:+I<string>] >>	1581	=item B<< [title:+I<string>] >>
1444		1582
1445	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
1446	following format specifiers:	1584	following format specifiers:
1447	B<%%> : literal B<%> character	1585
1448	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)
1449	B<%v> : rxvt version	1587	B<%v> rxvt version
		1588	B<%%> literal B<%> character
1450		1589
1451	=item B<[done]>	1590	=item B<[done]>
1452		1591
1453	set menuBar access as B<readonly>.	1592	set menuBar access as B<readonly>.
1454	End-of-file tag for B<< [read:+I<file>] >> operations.	1593	End-of-file tag for B<< [read:+I<file>] >> operations.
…		…
1600		1739
1601	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
1602	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
1603	appended if missed from B<M-x> commands.	1742	appended if missed from B<M-x> commands.
1604		1743
1605	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
1606	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.
1607		1746
1608	=over 4	1747	=over 4
1609		1748
1610	=item For example,	1749	=item For example,
…		…
2074	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
2075	styles. The fonts can be set manually or automatically.	2214	styles. The fonts can be set manually or automatically.
2076		2215
2077	=item --with-codesets=NAME,...	2216	=item --with-codesets=NAME,...
2078		2217
2079	Compile in support for additional codeset (encoding) groups (eu, vn are	2218	Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2080	always compiled in, which includes most 8-bit character sets). These	2219	are always compiled in, which includes most 8-bit character sets). These
2081	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
2082	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
2083	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
2084	you use an X11 font requiring one of these encodings.	2224	memory usage unless you use a font requiring one of these encodings.
2085		2225
2086	=begin table	2226	=begin table
2087		2227
2088	all all available codeset groups	2228	all all available codeset groups
2089	zh common chinese encodings	2229	zh common chinese encodings
…		…
2119	composite characters. This is required for proper viewing of text	2259	composite characters. This is required for proper viewing of text
2120	where accents are encoded as seperate unicode characters. This is	2260	where accents are encoded as seperate unicode characters. This is
2121	done by using precomposited characters when available or creating	2261	done by using precomposited characters when available or creating
2122	new pseudo-characters when no precomposed form exists.	2262	new pseudo-characters when no precomposed form exists.
2123		2263
2124	Without --enable-unicode3, the number of additional precomposed	2264	Without --enable-unicode3, the number of additional precomposed characters
2125	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
2126	private use area, extending the number of combinations to 8448). With	2266	private use area, extending the number of combinations to 8448). With
2127	--enable-unicode3, no practical limit exists. This will also enable	2267	--enable-unicode3, no practical limit exists.
2128	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.
2129		2271
2130	The combining table also contains entries for arabic presentation forms,	2272	The combining table also contains entries for arabic presentation forms,
2131	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...).
2132		2275
2133	=item --enable-fallback(=CLASS)	2276	=item --enable-fallback(=CLASS)
2134		2277
2135	When reading resource settings, also read settings for class CLASS	2278	When reading resource settings, also read settings for class CLASS
2136	(default: Rxvt). To disable resource fallback use --disable-fallback.	2279	(default: Rxvt). To disable resource fallback use --disable-fallback.
…		…
2228	Remove all resources checking.	2371	Remove all resources checking.
2229		2372
2230	=item --enable-xgetdefault	2373	=item --enable-xgetdefault
2231		2374
2232	Make resources checking via XGetDefault() instead of our small	2375	Make resources checking via XGetDefault() instead of our small
2233	version which only checks ~/.Xdefaults, or if that doesn't exist	2376	version which only checks ~/.Xdefaults, or if that doesn't exist then
2234	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.
2235		2382
2236	=item --enable-strings	2383	=item --enable-strings
2237		2384
2238	Add support for our possibly faster memset() function and other	2385	Add support for our possibly faster memset() function and other
2239	various routines, overriding your system's versions which may	2386	various routines, overriding your system's versions which may
…		…
2249		2396
2250	Add support for many small features that are not essential but nice to	2397	Add support for many small features that are not essential but nice to
2251	have. Normally you want this, but for very small binaries you may want to	2398	have. Normally you want this, but for very small binaries you may want to
2252	disable this.	2399	disable this.
2253		2400
		2401	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
		2402	in combination with other switches) is:
		2403
		2404	MWM-hints
		2405	EWMH-hints (pid, utf8 names) and protocols (ping)
		2406	seperate underline colour
		2407	settable border widths and borderless switch
		2408	settable extra linespacing
		2409	iso-14755-2 and -3, and visual feedback
		2410	backindex and forwardindex escape sequence
		2411	window op and some xterm/OSC escape sequences
		2412	tripleclickwords
		2413	settable insecure mode
		2414	keysym remapping support
		2415	cursor blinking and underline cursor
		2416	-embed and -pty-fd options
		2417
2254	=item --enable-iso14755	2418	=item --enable-iso14755
2255		2419
2256	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2420	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2257	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
2258	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with	2422	C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
2259	this switch.	2423	this switch.
2260		2424
2261	=item --enable-linespace
2262
2263	Add support to provide user specified line spacing between text rows.
2264
2265	=item --enable-keepscrolling	2425	=item --enable-keepscrolling
2266		2426
2267	Add support for continual scrolling of the display when you hold	2427	Add support for continual scrolling of the display when you hold
2268	the mouse button down on a scrollbar arrow.	2428	the mouse button down on a scrollbar arrow.
2269		2429
…		…
2300		2460
2301	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
2302	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
2303	closest to a corner of the screen.	2463	closest to a corner of the screen.
2304		2464
2305	=item --enable-cursor-blink
2306
2307	Add support for a blinking cursor.
2308
2309	=item --enable-pointer-blank	2465	=item --enable-pointer-blank
2310		2466
2311	Add support to have the pointer disappear when typing or inactive.	2467	Add support to have the pointer disappear when typing or inactive.
2312		2468
2313	=item --with-name=NAME	2469	=item --with-name=NAME
2314		2470
2315	Set the basename for the installed binaries (default: urxvt, resulting in	2471	Set the basename for the installed binaries (default: C<urxvt>, resulting
2316	urxvt, urxvtd etc.). Specify --with-name=rxvt to replace rxvt.	2472	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
		2473	C<rxvt>.
2317		2474
2318	=item --with-term=NAME	2475	=item --with-term=NAME
2319		2476
2320	Change the environmental variable for the terminal to NAME (default	2477	Change the environmental variable for the terminal to NAME (default
2321	"rxvt")	2478	C<rxvt-unicode>)
2322		2479
2323	=item --with-terminfo=PATH	2480	=item --with-terminfo=PATH
2324		2481
2325	Change the environmental variable for the path to the terminfo tree to	2482	Change the environmental variable for the path to the terminfo tree to
2326	PATH.	2483	PATH.

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.29 by root, Wed Dec 29 19:17:18 2004 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.29 by root, Wed Dec 29 19:17:18 2004 UTC vs.
Revision 1.60 by root, Fri Jul 29 03:12:10 2005 UTC