ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/rxvt-unicode/doc/rxvt.7.pod

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.78 by root, Thu Jan 12 05:37:34 2006 UTC vs.
Revision 1.106 by root, Tue Jan 31 21:01:36 2006 UTC

…		…
16	=head1 DESCRIPTION	16	=head1 DESCRIPTION
17		17
18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting	18	This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
19	all escape sequences, and other background information.	19	all escape sequences, and other background information.
20		20
21	The newest version of this document is	21	The newest version of this document is also available on the World Wide Web at
22	also available on the World Wide Web at
23	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.	22	L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
24		23
25	=head1 FREQUENTLY ASKED QUESTIONS	24	=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
26		25
27	=over 4
28		26
29	=item I don't like the new selection/popups/hotkeys/perl, how do I	27	=head2 Meta, Features & Commandline Issues
30	change/disable it?
31		28
32	You can disable the perl extension completely by setting the	29	=head3 My question isn't answered here, can I ask a human?
33	B<perl-ext-common> resource to the empty string, which also keeps
34	rxvt-unicode from initialising perl, saving memory.
35		30
36	If you only want to disable specific features, you first have to	31	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
37	identify which perl extension is responsible. For this, read the section	32	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
38	B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For	33	interested in learning about new and exciting problems (but not FAQs :).
39	example, to disable the B<selection-popup> and B<option-popup>, specify
40	this B<perl-ext-common> resource:
41		34
42	URxvt.perl-ext-common: default,-selection-popup,-option-popup	35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
43		36
44	This will keep the default extensions, but disable the two popup	37	Beginning with version 7.3, there is a perl extension that implements a
45	extensions. Some extensions can also be configured, for example,	38	simple tabbed terminal. It is installed by default, so any of these should
46	scrollback search mode is triggered by B<M-s>. You can move it to any	39	give you tabs:
47	other combination either by setting the B<searchable-scrollback> resource:
48		40
49	URxvt.searchable-scrollback: CM-s	41	@@URXVT_NAME@@ -pe tabbed
50		42
		43	URxvt.perl-ext-common: default,tabbed
		44
		45	It will also work fine with tabbing functionality of many window managers
		46	or similar tabbing programs, and its embedding-features allow it to be
		47	embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or
		48	the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt
		49	(murxvt) terminal as an example embedding application.
		50
		51	=head3 How do I know which rxvt-unicode version I'm using?
		52
		53	The version number is displayed with the usage (-h). Also the escape
		54	sequence C<ESC [ 8 n> sets the window title to the version number. When
		55	using the @@URXVT_NAME@@c client, the version displayed is that of the
		56	daemon.
		57
		58	=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
		59
		60	Rxvt-unicode tries to obey the rule of not charging you for something you
		61	don't use. One thing you should try is to configure out all settings that
		62	you don't need, for example, Xft support is a resource hog by design,
		63	when used. Compiling it out ensures that no Xft font will be loaded
		64	accidentally when rxvt-unicode tries to find a font for your characters.
		65
		66	Also, many people (me included) like large windows and even larger
		67	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		68	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		69	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
		70	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		71	rxvt-unicode then uses 8 bytes per screen cell.
		72
		73	=head3 How can I start @@URXVT_NAME@@d in a race-free way?
		74
		75	Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
		76	display, create the listening socket and then fork.
		77
		78	=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
		79
		80	The original rxvt and rxvt-unicode always export the variable "COLORTERM",
		81	so you can check and see if that is set. Note that several programs, JED,
		82	slrn, Midnight Commander automatically check this variable to decide
		83	whether or not to use color.
		84
		85	=head3 How do I set the correct, full IP address for the DISPLAY variable?
		86
		87	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
		88	insecure mode then it is possible to use the following shell script
		89	snippets to correctly set the display. If your version of rxvt-unicode
		90	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
		91	the COLORTERM variable can be used to distinguish rxvt-unicode from a
		92	regular xterm.
		93
		94	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
		95	snippets:
		96
		97	# Bourne/Korn/POSIX family of shells:
		98	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
		99	if [ ${TERM:-foo} = xterm ]; then
		100	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
		101	echo -n '^[Z'
		102	read term_id
		103	stty icanon echo
		104	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
		105	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
		106	read DISPLAY # set it in our local shell
		107	fi
		108	fi
		109
		110	=head3 How do I compile the manual pages on my own?
		111
		112	You need to have a recent version of perl installed as F</usr/bin/perl>,
		113	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
		114	the doc subdirectory and enter C<make alldoc>.
		115
51	=item Isn't rxvt supposed to be small? Don't all those features bloat?	116	=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
52		117
53	I often get asked about this, and I think, no, they didn't cause extra	118	I often get asked about this, and I think, no, they didn't cause extra
54	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see	119	bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
55	that the urxvt binary is larger (due to some encoding tables always being	120	that the urxvt binary is larger (due to some encoding tables always being
56	compiled in), but it actually uses less memory (RSS) after startup. Even	121	compiled in), but it actually uses less memory (RSS) after startup. Even
…		…
60		125
61	text data bss drs rss filename	126	text data bss drs rss filename
62	98398 1664 24 15695 1824 rxvt --disable-everything	127	98398 1664 24 15695 1824 rxvt --disable-everything
63	188985 9048 66616 18222 1788 urxvt --disable-everything	128	188985 9048 66616 18222 1788 urxvt --disable-everything
64		129
65	When you C<--enable-everything> (which _is_ unfair, as this involves xft	130	When you C<--enable-everything> (which I<is> unfair, as this involves xft
66	and full locale/XIM support which are quite bloaty inside libX11 and my	131	and full locale/XIM support which are quite bloaty inside libX11 and my
67	libc), the two diverge, but not unreasnobaly so.	132	libc), the two diverge, but not unreasnobaly so.
68		133
69	text data bss drs rss filename	134	text data bss drs rss filename
70	163431 2152 24 20123 2060 rxvt --enable-everything	135	163431 2152 24 20123 2060 rxvt --enable-everything
…		…
88	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	153	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
89	43180k in daemons that stay around after exit, plus half a minute of	154	43180k in daemons that stay around after exit, plus half a minute of
90	startup time, including the hundreds of warnings it spits out), it fares	155	startup time, including the hundreds of warnings it spits out), it fares
91	extremely well *g*.	156	extremely well *g*.
92		157
93	=item Why C++, isn't that unportable/bloated/uncool?	158	=head3 Why C++, isn't that unportable/bloated/uncool?
94		159
95	Is this a question? :) It comes up very often. The simple answer is: I had	160	Is this a question? :) It comes up very often. The simple answer is: I had
96	to write it, and C++ allowed me to write and maintain it in a fraction	161	to write it, and C++ allowed me to write and maintain it in a fraction
97	of the time and effort (which is a scarce resource for me). Put even	162	of the time and effort (which is a scarce resource for me). Put even
98	shorter: It simply wouldn't exist without C++.	163	shorter: It simply wouldn't exist without C++.
…		…
122	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	187	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
123		188
124	No large bloated libraries (of course, none were linked in statically),	189	No large bloated libraries (of course, none were linked in statically),
125	except maybe libX11 :)	190	except maybe libX11 :)
126		191
127	=item Does it support tabs, can I have a tabbed rxvt-unicode?
128		192
129	rxvt-unicode does not directly support tabs. It will work fine with	193	=head2 Rendering, Font & Look and Feel Issues
130	tabbing functionality of many window managers or similar tabbing programs,
131	and its embedding-features allow it to be embedded into other programs,
132	as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
133	module, which features a tabbed urxvt (murxvt) terminal as an example
134	embedding application.
135		194
136	=item How do I know which rxvt-unicode version I'm using?	195	=head3 I can't get transparency working, what am I doing wrong?
137		196
138	The version number is displayed with the usage (-h). Also the escape	197	First of all, transparency isn't officially supported in rxvt-unicode, so
139	sequence C<ESC [ 8 n> sets the window title to the version number. When	198	you are mostly on your own. Do not bug the author about it (but you may
140	using the @@RXVT_NAME@@c client, the version displayed is that of the	199	bug everybody else). Also, if you can't get it working consider it a rite
141	daemon.	200	of passage: ... and you failed.
142		201
143	=item I am using Debian GNU/Linux and have a problem...	202	Here are four ways to get transparency. B<Do> read the manpage and option
		203	descriptions for the programs mentioned and rxvt-unicode. Really, do it!
144		204
145	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	205	1. Use inheritPixmap:
146	patches that considerably change the behaviour of rxvt-unicode. Before
147	reporting a bug to the original rxvt-unicode author please download and
148	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
149	and try to reproduce the problem. If you cannot, chances are that the
150	problems are specific to Debian GNU/Linux, in which case it should be
151	reported via the Debian Bug Tracking System (use C<reportbug> to report
152	the bug).
153		206
154	For other problems that also affect the Debian package, you can and	207	Esetroot wallpaper.jpg
155	probably should use the Debian BTS, too, because, after all, it's also a	208	@@URXVT_NAME@@ -ip -tint red -sh 40
156	bug in the Debian version and it serves as a reminder for other users that
157	might encounter the same issue.
158		209
159	=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?	210	That works. If you think it doesn't, you lack transparency and tinting
		211	support, or you are unable to read.
160		212
161	You should build one binary with the default options. F<configure>	213	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
162	now enables most useful options, and the trend goes to making them	214	to use effects other than tinting and shading: Just shade/tint/whatever
163	runtime-switchable, too, so there is usually no drawback to enbaling them,	215	your picture with gimp or any other tool:
164	except higher disk and possibly memory usage. The perl interpreter should
165	be enabled, as important functionality (menus, selection, likely more in
166	the future) depends on it.
167		216
168	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	217	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
169	system-wide (except maybe with C<defaults>). This will result in useful	218	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
170	behaviour. If your distribution aims at low memory, add an empty
171	C<perl-ext-common> resource to the app-defaults file. This will keep the
172	perl interpreter disabled until the user enables it.
173		219
174	If you can/want build more binaries, I recommend building a minimal	220	That works. If you think it doesn't, you lack XPM and Perl support, or you
175	one with C<--disable-everything> (very useful) and a maximal one with	221	are unable to read.
176	C<--enable-everything> (less useful, it will be very big due to a lot of
177	encodings built-in that increase download times and are rarely used).
178		222
179	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	223	3. Use an ARGB visual:
180		224
181	Likely not. While I honestly try to make it secure, and am probably not	225	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
182	bad at it, I think it is simply unreasonable to expect all of freetype
183	+ fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be
184	secure. Also, rxvt-unicode disables some options when it detects that it
185	runs setuid or setgid, which is not nice. Besides, with the embedded perl
186	interpreter the possibility for security problems easily multiplies.
187		226
188	Elevated privileges are only required for utmp and pty operations on some	227	This requires XFT support, and the support of your X-server. If that
189	systems (for example, GNU/Linux doesn't need any extra privileges for	228	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
190	ptys, but some need it for utmp support). It is planned to mvoe this into	229	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
191	a forked handler process, but this is not yet done.	230	bugfixes and workarounds for Xft and Xlib to make it work, but that
		231	doesn't mean that your WM has the required kludges in place.
192		232
193	So, while setuid/setgid operation is supported and not a problem on your	233	4. Use xcompmgr and let it do the job:
194	typical single-user-no-other-logins unix desktop, always remember that
195	its an awful lot of code, most of which isn't checked for security issues
196	regularly.
197		234
		235	xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
		236	-set _NET_WM_WINDOW_OPACITY 0xc0000000
		237
		238	Then click on a window you want to make transparent. Replace C<0xc0000000>
		239	by other values to change the degree of opacity. If it doesn't work and
		240	your server crashes, you got to keep the pieces.
		241
		242	=head3 Why do some chinese characters look so different than others?
		243
		244	This is because there is a difference between script and language --
		245	rxvt-unicode does not know which language the text that is output is,
		246	as it only knows the unicode character codes. If rxvt-unicode first
		247	sees a japanese/chinese character, it might choose a japanese font for
		248	display. Subsequent japanese characters will use that font. Now, many
		249	chinese characters aren't represented in japanese fonts, so when the first
		250	non-japanese character comes up, rxvt-unicode will look for a chinese font
		251	-- unfortunately at this point, it will still use the japanese font for
		252	chinese characters that are also in the japanese font.
		253
		254	The workaround is easy: just tag a chinese font at the end of your font
		255	list (see the previous question). The key is to view the font list as
		256	a preference list: If you expect more japanese, list a japanese font
		257	first. If you expect more chinese, put a chinese font first.
		258
		259	In the future it might be possible to switch language preferences at
		260	runtime (the internal data structure has no problem with using different
		261	fonts for the same character at the same time, but no interface for this
		262	has been designed yet).
		263
		264	Until then, you might get away with switching fonts at runtime (see L<Can
		265	I switch the fonts at runtime?> later in this document).
		266
		267	=head3 Why does rxvt-unicode sometimes leave pixel droppings?
		268
		269	Most fonts were not designed for terminal use, which means that character
		270	size varies a lot. A font that is otherwise fine for terminal use might
		271	contain some characters that are simply too wide. Rxvt-unicode will avoid
		272	these characters. For characters that are just "a bit" too wide a special
		273	"careful" rendering mode is used that redraws adjacent characters.
		274
		275	All of this requires that fonts do not lie about character sizes,
		276	however: Xft fonts often draw glyphs larger than their acclaimed bounding
		277	box, and rxvt-unicode has no way of detecting this (the correct way is to
		278	ask for the character bounding box, which unfortunately is wrong in these
		279	cases).
		280
		281	It's not clear (to me at least), wether this is a bug in Xft, freetype,
		282	or the respective font. If you encounter this problem you might try using
		283	the C<-lsp> option to give the font more height. If that doesn't work, you
		284	might be forced to use a different font.
		285
		286	All of this is not a problem when using X11 core fonts, as their bounding
		287	box data is correct.
		288
		289	=head3 How can I keep rxvt-unicode from using reverse video so much?
		290
		291	First of all, make sure you are running with the right terminal settings
		292	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
		293	make sure you have specified colours for italic and bold, as otherwise
		294	rxvt-unicode might use reverse video to simulate the effect:
		295
		296	URxvt.colorBD: white
		297	URxvt.colorIT: green
		298
		299	=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that?
		300
		301	For some unexplainable reason, some rare programs assume a very weird
		302	colour palette when confronted with a terminal with more than the standard
		303	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
		304	these programs not to assume non-ISO colours without very good reasons.
		305
		306	In the meantime, you can either edit your C<rxvt-unicode> terminfo
		307	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
		308	fix colours but keep you from using other rxvt-unicode features.
		309
		310	=head3 Can I switch the fonts at runtime?
		311
		312	Yes, using an escape sequence. Try something like this, which has the same
		313	effect as using the C<-fn> switch, and takes effect immediately:
		314
		315	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		316
		317	This is useful if you e.g. work primarily with japanese (and prefer a
		318	japanese font), but you have to switch to chinese temporarily, where
		319	japanese fonts would only be in your way.
		320
		321	You can think of this as a kind of manual ISO-2022 switching.
		322
		323	=head3 Why do italic characters look as if clipped?
		324
		325	Many fonts have difficulties with italic characters and hinting. For
		326	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		327	Mono> completely fails in it's italic face. A workaround might be to
		328	enable freetype autohinting, i.e. like this:
		329
		330	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		331	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		332
		333	=head3 Can I speed up Xft rendering somehow?
		334
		335	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		336	it is simply slow. If you still want Xft fonts you might try to disable
		337	antialiasing (by appending C<:antialias=false>), which saves lots of
		338	memory and also speeds up rendering considerably.
		339
		340	=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		341
		342	Rxvt-unicode will use whatever you specify as a font. If it needs to
		343	fall back to it's default font search list it will prefer X11 core
		344	fonts, because they are small and fast, and then use Xft fonts. It has
		345	antialiasing disabled for most of them, because the author thinks they
		346	look best that way.
		347
		348	If you want antialiasing, you have to specify the fonts manually.
		349
		350	=head3 What's with this bold/blink stuff?
		351
		352	If no bold colour is set via C<colorBD:>, bold will invert text using the
		353	standard foreground colour.
		354
		355	For the standard background colour, blinking will actually make the
		356	text blink when compiled with C<--enable-blinking>. with standard
		357	colours. Without C<--enable-blinking>, the blink attribute will be
		358	ignored.
		359
		360	On ANSI colours, bold/blink attributes are used to set high-intensity
		361	foreground/background colors.
		362
		363	color0-7 are the low-intensity colors.
		364
		365	color8-15 are the corresponding high-intensity colors.
		366
		367	=head3 I don't like the screen colors. How do I change them?
		368
		369	You can change the screen colors at run-time using F<~/.Xdefaults>
		370	resources (or as long-options).
		371
		372	Here are values that are supposed to resemble a VGA screen,
		373	including the murky brown that passes for low-intensity yellow:
		374
		375	URxvt.color0: #000000
		376	URxvt.color1: #A80000
		377	URxvt.color2: #00A800
		378	URxvt.color3: #A8A800
		379	URxvt.color4: #0000A8
		380	URxvt.color5: #A800A8
		381	URxvt.color6: #00A8A8
		382	URxvt.color7: #A8A8A8
		383
		384	URxvt.color8: #000054
		385	URxvt.color9: #FF0054
		386	URxvt.color10: #00FF54
		387	URxvt.color11: #FFFF54
		388	URxvt.color12: #0000FF
		389	URxvt.color13: #FF00FF
		390	URxvt.color14: #00FFFF
		391	URxvt.color15: #FFFFFF
		392
		393	And here is a more complete set of non-standard colors described (not by
		394	me) as "pretty girly".
		395
		396	URxvt.cursorColor: #dc74d1
		397	URxvt.pointerColor: #dc74d1
		398	URxvt.background: #0e0e0e
		399	URxvt.foreground: #4ad5e1
		400	URxvt.color0: #000000
		401	URxvt.color8: #8b8f93
		402	URxvt.color1: #dc74d1
		403	URxvt.color9: #dc74d1
		404	URxvt.color2: #0eb8c7
		405	URxvt.color10: #0eb8c7
		406	URxvt.color3: #dfe37e
		407	URxvt.color11: #dfe37e
		408	URxvt.color5: #9e88f0
		409	URxvt.color13: #9e88f0
		410	URxvt.color6: #73f7ff
		411	URxvt.color14: #73f7ff
		412	URxvt.color7: #e1dddd
		413	URxvt.color15: #e1dddd
		414
		415	=head3 Why do some characters look so much different than others?
		416
		417	See next entry.
		418
		419	=head3 How does rxvt-unicode choose fonts?
		420
		421	Most fonts do not contain the full range of Unicode, which is
		422	fine. Chances are that the font you (or the admin/package maintainer of
		423	your system/os) have specified does not cover all the characters you want
		424	to display.
		425
		426	B<rxvt-unicode> makes a best-effort try at finding a replacement
		427	font. Often the result is fine, but sometimes the chosen font looks
		428	bad/ugly/wrong. Some fonts have totally strange characters that don't
		429	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
		430	intelligence to detect that a specific glyph is wrong: it has to believe
		431	the font that the characters it claims to contain indeed look correct.
		432
		433	In that case, select a font of your taste and add it to the font list,
		434	e.g.:
		435
		436	@@URXVT_NAME@@ -fn basefont,font2,font3...
		437
		438	When rxvt-unicode sees a character, it will first look at the base
		439	font. If the base font does not contain the character, it will go to the
		440	next font, and so on. Specifying your own fonts will also speed up this
		441	search and use less resources within rxvt-unicode and the X-server.
		442
		443	The only limitation is that none of the fonts may be larger than the base
		444	font, as the base font defines the terminal character cell size, which
		445	must be the same due to the way terminals work.
		446
		447
		448	=head2 Keyboard, Mouse & User Interaction
		449
		450	=head3 The new selection selects pieces that are too big, how can I select single words?
		451
		452	If you want to select e.g. alphanumeric words, you can use the following
		453	setting:
		454
		455	URxvt.selection.pattern-0: ([[:word:]]+)
		456
		457	If you click more than twice, the selection will be extended
		458	more and more.
		459
		460	To get a selection that is very similar to the old code, try this pattern:
		461
		462	URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
		463
		464	Please also note that the I<LeftClick Shift-LeftClik> combination also
		465	selects words like the old code.
		466
		467	=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
		468
		469	You can disable the perl extension completely by setting the
		470	B<perl-ext-common> resource to the empty string, which also keeps
		471	rxvt-unicode from initialising perl, saving memory.
		472
		473	If you only want to disable specific features, you first have to
		474	identify which perl extension is responsible. For this, read the section
		475	B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
		476	example, to disable the B<selection-popup> and B<option-popup>, specify
		477	this B<perl-ext-common> resource:
		478
		479	URxvt.perl-ext-common: default,-selection-popup,-option-popup
		480
		481	This will keep the default extensions, but disable the two popup
		482	extensions. Some extensions can also be configured, for example,
		483	scrollback search mode is triggered by B<M-s>. You can move it to any
		484	other combination either by setting the B<searchable-scrollback> resource:
		485
		486	URxvt.searchable-scrollback: CM-s
		487
		488	=head3 The cursor moves when selecting text in the current input line, how do I switch this off?
		489
		490	See next entry.
		491
		492	=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
		493
		494	These are caused by the C<readline> perl extension. Under normal
		495	circumstances, it will move your cursor around when you click into the
		496	line that contains it. It tries hard not to do this at the wrong moment,
		497	but when running a program that doesn't parse cursor movements or in some
		498	cases during rlogin sessions, it fails to detect this properly.
		499
		500	You can permamently switch this feature off by disabling the C<readline>
		501	extension:
		502
		503	URxvt.perl-ext-common: default,-readline
		504
		505	=head3 My numerical keypad acts weird and generates differing output?
		506
		507	Some Debian GNUL/Linux users seem to have this problem, although no
		508	specific details were reported so far. It is possible that this is caused
		509	by the wrong C<TERM> setting, although the details of wether and how
		510	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
		511	keymap. See the answer to the previous question, and please report if that
		512	helped.
		513
		514	=head3 My Compose (Multi_key) key is no longer working.
		515
		516	The most common causes for this are that either your locale is not set
		517	correctly, or you specified a B<preeditStyle> that is not supported by
		518	your input method. For example, if you specified B<OverTheSpot> and
		519	your input method (e.g. the default input method handling Compose keys)
		520	does not support this (for instance because it is not visual), then
		521	rxvt-unicode will continue without an input method.
		522
		523	In this case either do not specify a B<preeditStyle> or specify more than
		524	one pre-edit style, such as B<OverTheSpot,Root,None>.
		525
		526	=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
		527
		528	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
		529	international keyboards) or simply use ISO 14755 support to your
		530	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
		531	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
		532	character and so on.
		533
		534	=head3 Mouse cut/paste suddenly no longer works.
		535
		536	Make sure that mouse reporting is actually turned off since killing
		537	some editors prematurely may leave the mouse in mouse report mode. I've
		538	heard that tcsh may use mouse reporting unless it otherwise specified. A
		539	quick check is to see if cut/paste works when the Alt or Shift keys are
		540	depressed.
		541
		542	=head3 What's with the strange Backspace/Delete key behaviour?
		543
		544	Assuming that the physical Backspace key corresponds to the
		545	BackSpace keysym (not likely for Linux ... see the following
		546	question) there are two standard values that can be used for
		547	Backspace: C<^H> and C<^?>.
		548
		549	Historically, either value is correct, but rxvt-unicode adopts the debian
		550	policy of using C<^?> when unsure, because it's the one only only correct
		551	choice :).
		552
		553	Rxvt-unicode tries to inherit the current stty settings and uses the value
		554	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
		555	started from a terminal (say, from a menu or by remote shell), then the
		556	system value of `erase', which corresponds to CERASE in <termios.h>, will
		557	be used (which may not be the same as your stty setting).
		558
		559	For starting a new rxvt-unicode:
		560
		561	# use Backspace = ^H
		562	$ stty erase ^H
		563	$ @@URXVT_NAME@@
		564
		565	# use Backspace = ^?
		566	$ stty erase ^?
		567	$ @@URXVT_NAME@@
		568
		569	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
		570
		571	For an existing rxvt-unicode:
		572
		573	# use Backspace = ^H
		574	$ stty erase ^H
		575	$ echo -n "^[[36h"
		576
		577	# use Backspace = ^?
		578	$ stty erase ^?
		579	$ echo -n "^[[36l"
		580
		581	This helps satisfy some of the Backspace discrepancies that occur, but
		582	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
		583	properly reflects that.
		584
		585	The Delete key is a another casualty of the ill-defined Backspace problem.
		586	To avoid confusion between the Backspace and Delete keys, the Delete
		587	key has been assigned an escape sequence to match the vt100 for Execute
		588	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
		589
		590	Some other Backspace problems:
		591
		592	some editors use termcap/terminfo,
		593	some editors (vim I'm told) expect Backspace = ^H,
		594	GNU Emacs (and Emacs-like editors) use ^H for help.
		595
		596	Perhaps someday this will all be resolved in a consistent manner.
		597
		598	=head3 I don't like the key-bindings. How do I change them?
		599
		600	There are some compile-time selections available via configure. Unless
		601	you have run "configure" with the C<--disable-resources> option you can
		602	use the `keysym' resource to alter the keystrings associated with keysyms.
		603
		604	Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
		605
		606	URxvt.keysym.Home: \033[1~
		607	URxvt.keysym.End: \033[4~
		608	URxvt.keysym.C-apostrophe: \033<C-'>
		609	URxvt.keysym.C-slash: \033<C-/>
		610	URxvt.keysym.C-semicolon: \033<C-;>
		611	URxvt.keysym.C-grave: \033<C-`>
		612	URxvt.keysym.C-comma: \033<C-,>
		613	URxvt.keysym.C-period: \033<C-.>
		614	URxvt.keysym.C-0x60: \033<C-`>
		615	URxvt.keysym.C-Tab: \033<C-Tab>
		616	URxvt.keysym.C-Return: \033<C-Return>
		617	URxvt.keysym.S-Return: \033<S-Return>
		618	URxvt.keysym.S-space: \033<S-Space>
		619	URxvt.keysym.M-Up: \033<M-Up>
		620	URxvt.keysym.M-Down: \033<M-Down>
		621	URxvt.keysym.M-Left: \033<M-Left>
		622	URxvt.keysym.M-Right: \033<M-Right>
		623	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
		624	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
		625	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
		626
		627	See some more examples in the documentation for the B<keysym> resource.
		628
		629	=head3 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map
		630
		631	KP_Insert == Insert
		632	F22 == Print
		633	F27 == Home
		634	F29 == Prior
		635	F33 == End
		636	F35 == Next
		637
		638	Rather than have rxvt-unicode try to accommodate all the various possible
		639	keyboard mappings, it is better to use `xmodmap' to remap the keys as
		640	required for your particular machine.
		641
		642
		643
		644	=head2 Terminal Configuration
		645
		646	=head3 Why doesn't rxvt-unicode read my resources?
		647
		648	Well, why, indeed? It does, in a way very similar to other X
		649	applications. Most importantly, this means that if you or your OS loads
		650	resources into the X display (the right way to do it), rxvt-unicode will
		651	ignore any resource files in your home directory. It will only read
		652	F<$HOME/.Xdefaults> when no resources are attached to the display.
		653
		654	If you have or use an F<$HOME/.Xresources> file, chances are that
		655	resources are loaded into your X-server. In this case, you have to
		656	re-login after every change (or run F<xrdb -merge $HOME/.Xresources>).
		657
		658	Also consider the form resources have to use:
		659
		660	URxvt.resource: value
		661
		662	If you want to use another form (there are lots of different ways of
		663	specifying resources), make sure you understand wether and why it
		664	works. If unsure, use the form above.
		665
198	=item When I log-in to another system it tells me about missing terminfo data?	666	=head3 When I log-in to another system it tells me about missing terminfo data?
199		667
200	The terminal description used by rxvt-unicode is not as widely available	668	The terminal description used by rxvt-unicode is not as widely available
201	as that for xterm, or even rxvt (for which the same problem often arises).	669	as that for xterm, or even rxvt (for which the same problem often arises).
202		670
203	The correct solution for this problem is to install the terminfo, this can	671	The correct solution for this problem is to install the terminfo, this can
…		…
219	resource to set it:	687	resource to set it:
220		688
221	URxvt.termName: rxvt	689	URxvt.termName: rxvt
222		690
223	If you don't plan to use B<rxvt> (quite common...) you could also replace	691	If you don't plan to use B<rxvt> (quite common...) you could also replace
224	the rxvt terminfo file with the rxvt-unicode one.	692	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
225		693
226	=item C<tic> outputs some error when compiling the terminfo entry.	694	=head3 C<tic> outputs some error when compiling the terminfo entry.
227		695
228	Most likely it's the empty definition for C<enacs=>. Just replace it by	696	Most likely it's the empty definition for C<enacs=>. Just replace it by
229	C<enacs=\E[0@> and try again.	697	C<enacs=\E[0@> and try again.
230		698
231	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	699	=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
232		700
		701	See next entry.
		702
233	=item I need a termcap file entry.	703	=head3 I need a termcap file entry.
234		704
235	One reason you might want this is that some distributions or operating	705	One reason you might want this is that some distributions or operating
236	systems still compile some programs using the long-obsoleted termcap	706	systems still compile some programs using the long-obsoleted termcap
237	library (Fedora Core's bash is one example) and rely on a termcap entry	707	library (Fedora Core's bash is one example) and rely on a termcap entry
238	for C<rxvt-unicode>.	708	for C<rxvt-unicode>.
…		…
264	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\	734	:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
265	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\	735	:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
266	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\	736	:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
267	:vs=\E[?25h:	737	:vs=\E[?25h:
268		738
269	=item Why does C<ls> no longer have coloured output?	739	=head3 Why does C<ls> no longer have coloured output?
270		740
271	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to	741	The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
272	decide wether a terminal has colour, but uses it's own configuration	742	decide wether a terminal has colour, but uses it's own configuration
273	file. Needless to say, C<rxvt-unicode> is not in it's default file (among	743	file. Needless to say, C<rxvt-unicode> is not in it's default file (among
274	with most other terminals supporting colour). Either add:	744	with most other terminals supporting colour). Either add:
…		…
279		749
280	alias ls='ls --color=auto'	750	alias ls='ls --color=auto'
281		751
282	to your C<.profile> or C<.bashrc>.	752	to your C<.profile> or C<.bashrc>.
283		753
284	=item Why doesn't vim/emacs etc. use the 88 colour mode?	754	=head3 Why doesn't vim/emacs etc. use the 88 colour mode?
285		755
		756	See next entry.
		757
286	=item Why doesn't vim/emacs etc. make use of italic?	758	=head3 Why doesn't vim/emacs etc. make use of italic?
287		759
		760	See next entry.
		761
288	=item Why are the secondary screen-related options not working properly?	762	=head3 Why are the secondary screen-related options not working properly?
289		763
290	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged	764	Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged
291	distributions (most notably Debian GNU/Linux) break rxvt-unicode	765	distributions (most notably Debian GNU/Linux) break rxvt-unicode
292	by setting C<TERM> to C<rxvt>, which doesn't have these extra	766	by setting C<TERM> to C<rxvt>, which doesn't have these extra
293	features. Unfortunately, some of these (most notably, again, Debian	767	features. Unfortunately, some of these (most notably, again, Debian
294	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo	768	GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo
295	file, so you will need to install it on your own (See the question B<When	769	file, so you will need to install it on your own (See the question B<When
296	I log-in to another system it tells me about missing terminfo data?> on	770	I log-in to another system it tells me about missing terminfo data?> on
297	how to do this).	771	how to do this).
298		772
299	=item My numerical keypad acts weird and generates differing output?
300		773
301	Some Debian GNUL/Linux users seem to have this problem, although no	774	=head2 Encoding / Locale / Input Method Issues
302	specific details were reported so far. It is possible that this is caused
303	by the wrong C<TERM> setting, although the details of wether and how
304	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
305	keymap. See the answer to the previous question, and please report if that
306	helped.
307		775
308	=item Rxvt-unicode does not seem to understand the selected encoding?	776	=head3 Rxvt-unicode does not seem to understand the selected encoding?
309		777
		778	See next entry.
		779
310	=item Unicode does not seem to work?	780	=head3 Unicode does not seem to work?
311		781
312	If you encounter strange problems like typing an accented character but	782	If you encounter strange problems like typing an accented character but
313	getting two unrelated other characters or similar, or if program output is	783	getting two unrelated other characters or similar, or if program output is
314	subtly garbled, then you should check your locale settings.	784	subtly garbled, then you should check your locale settings.
315		785
…		…
335		805
336	If nothing works and you are sure that everything is set correctly then	806	If nothing works and you are sure that everything is set correctly then
337	you will need to remember a little known fact: Some programs just don't	807	you will need to remember a little known fact: Some programs just don't
338	support locales :(	808	support locales :(
339		809
340	=item Why do some characters look so much different than others?	810	=head3 How does rxvt-unicode determine the encoding to use?
341		811
342	=item How does rxvt-unicode choose fonts?	812	See next entry.
343		813
344	Most fonts do not contain the full range of Unicode, which is	814	=head3 Is there an option to switch encodings?
345	fine. Chances are that the font you (or the admin/package maintainer of
346	your system/os) have specified does not cover all the characters you want
347	to display.
348		815
349	B<rxvt-unicode> makes a best-effort try at finding a replacement	816	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
350	font. Often the result is fine, but sometimes the chosen font looks	817	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
351	bad/ugly/wrong. Some fonts have totally strange characters that don't	818	UTF-8 or any other encodings with respect to terminal I/O.
352	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
353	intelligence to detect that a specific glyph is wrong: it has to believe
354	the font that the characters it claims to contain indeed look correct.
355		819
356	In that case, select a font of your taste and add it to the font list,	820	The reasons is that there exists a perfectly fine mechanism for selecting
357	e.g.:	821	the encoding, doing I/O and (most important) communicating this to all
358		822	applications so everybody agrees on character properties such as width
359	@@RXVT_NAME@@ -fn basefont,font2,font3...	823	and code number. This mechanism is the I<locale>. Applications not using
360		824	that info will have problems (for example, C<xterm> gets the width of
361	When rxvt-unicode sees a character, it will first look at the base	825	characters wrong as it uses it's own, locale-independent table under all
362	font. If the base font does not contain the character, it will go to the
363	next font, and so on. Specifying your own fonts will also speed up this
364	search and use less resources within rxvt-unicode and the X-server.
365
366	The only limitation is that none of the fonts may be larger than the base
367	font, as the base font defines the terminal character cell size, which
368	must be the same due to the way terminals work.
369
370	=item Why do some chinese characters look so different than others?
371
372	This is because there is a difference between script and language --
373	rxvt-unicode does not know which language the text that is output is,
374	as it only knows the unicode character codes. If rxvt-unicode first
375	sees a japanese/chinese character, it might choose a japanese font for
376	display. Subsequent japanese characters will use that font. Now, many
377	chinese characters aren't represented in japanese fonts, so when the first
378	non-japanese character comes up, rxvt-unicode will look for a chinese font
379	-- unfortunately at this point, it will still use the japanese font for
380	chinese characters that are also in the japanese font.
381
382	The workaround is easy: just tag a chinese font at the end of your font
383	list (see the previous question). The key is to view the font list as
384	a preference list: If you expect more japanese, list a japanese font
385	first. If you expect more chinese, put a chinese font first.
386
387	In the future it might be possible to switch language preferences at
388	runtime (the internal data structure has no problem with using different
389	fonts for the same character at the same time, but no interface for this
390	has been designed yet).
391
392	Until then, you might get away with switching fonts at runtime (see L<Can
393	I switch the fonts at runtime?> later in this document).
394
395	=item Why does rxvt-unicode sometimes leave pixel droppings?
396
397	Most fonts were not designed for terminal use, which means that character
398	size varies a lot. A font that is otherwise fine for terminal use might
399	contain some characters that are simply too wide. Rxvt-unicode will avoid
400	these characters. For characters that are just "a bit" too wide a special
401	"careful" rendering mode is used that redraws adjacent characters.
402
403	All of this requires that fonts do not lie about character sizes,
404	however: Xft fonts often draw glyphs larger than their acclaimed bounding
405	box, and rxvt-unicode has no way of detecting this (the correct way is to
406	ask for the character bounding box, which unfortunately is wrong in these
407	cases).	826	locales).
408		827
409	It's not clear (to me at least), wether this is a bug in Xft, freetype,	828	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
410	or the respective font. If you encounter this problem you might try using	829	programs doing the same (that is, most) will automatically agree in the
411	the C<-lsp> option to give the font more height. If that doesn't work, you	830	interpretation of characters.
412	might be forced to use a different font.
413		831
414	All of this is not a problem when using X11 core fonts, as their bounding	832	Unfortunately, there is no system-independent way to select locales, nor
415	box data is correct.	833	is there a standard on how locale specifiers will look like.
416		834
		835	On most systems, the content of the C<LC_CTYPE> environment variable
		836	contains an arbitrary string which corresponds to an already-installed
		837	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		838	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		839	(i.e. C<de> or C<german>) are also common.
		840
		841	Rxvt-unicode ignores all other locale categories, and except for
		842	the encoding, ignores country or language-specific settings,
		843	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
		844	rxvt-unicode.
		845
		846	If you want to use a specific encoding you have to make sure you start
		847	rxvt-unicode with the correct C<LC_CTYPE> category.
		848
		849	=head3 Can I switch locales at runtime?
		850
		851	Yes, using an escape sequence. Try something like this, which sets
		852	rxvt-unicode's idea of C<LC_CTYPE>.
		853
		854	printf '\e]701;%s\007' ja_JP.SJIS
		855
		856	See also the previous answer.
		857
		858	Sometimes this capability is rather handy when you want to work in
		859	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
		860	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
		861	first switches to a locale supported by xjdic and back later:
		862
		863	printf '\e]701;%s\007' ja_JP.SJIS
		864	xjdic -js
		865	printf '\e]701;%s\007' de_DE.UTF-8
		866
		867	You can also use xterm's C<luit> program, which usually works fine, except
		868	for some locales where character width differs between program- and
		869	rxvt-unicode-locales.
		870
		871	=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
		872
		873	You can specify separate locales for the input method and the rest of the
		874	terminal, using the resource C<imlocale>:
		875
		876	URxvt.imlocale: ja_JP.EUC-JP
		877
		878	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		879	use your input method. Please note, however, that you will not be able to
		880	input characters outside C<EUC-JP> in a normal way then, as your input
		881	method limits you.
		882
		883	=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
		884
		885	Unfortunately, this is unavoidable, as the XIM protocol is racy by
		886	design. Applications can avoid some crashes at the expense of memory
		887	leaks, and Input Methods can avoid some crashes by careful ordering at
		888	exit time. B<kinput2> (and derived input methods) generally succeeds,
		889	while B<SCIM> (or similar input methods) fails. In the end, however,
		890	crashes cannot be completely avoided even if both sides cooperate.
		891
		892	So the only workaround is not to kill your Input Method Servers.
		893
		894
		895	=head2 Operating Systems / Package Maintaining
		896
		897	=head3 I am using Debian GNU/Linux and have a problem...
		898
		899	The Debian GNU/Linux package of rxvt-unicode in sarge contains large
		900	patches that considerably change the behaviour of rxvt-unicode (but
		901	unfortunately this notice has been removed). Before reporting a bug to
		902	the original rxvt-unicode author please download and install the genuine
		903	version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
		904	the problem. If you cannot, chances are that the problems are specific to
		905	Debian GNU/Linux, in which case it should be reported via the Debian Bug
		906	Tracking System (use C<reportbug> to report the bug).
		907
		908	For other problems that also affect the Debian package, you can and
		909	probably should use the Debian BTS, too, because, after all, it's also a
		910	bug in the Debian version and it serves as a reminder for other users that
		911	might encounter the same issue.
		912
		913	=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
		914
		915	You should build one binary with the default options. F<configure>
		916	now enables most useful options, and the trend goes to making them
		917	runtime-switchable, too, so there is usually no drawback to enbaling them,
		918	except higher disk and possibly memory usage. The perl interpreter should
		919	be enabled, as important functionality (menus, selection, likely more in
		920	the future) depends on it.
		921
		922	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
		923	system-wide (except maybe with C<defaults>). This will result in useful
		924	behaviour. If your distribution aims at low memory, add an empty
		925	C<perl-ext-common> resource to the app-defaults file. This will keep the
		926	perl interpreter disabled until the user enables it.
		927
		928	If you can/want build more binaries, I recommend building a minimal
		929	one with C<--disable-everything> (very useful) and a maximal one with
		930	C<--enable-everything> (less useful, it will be very big due to a lot of
		931	encodings built-in that increase download times and are rarely used).
		932
		933	=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
		934
		935	It should be, starting with release 7.1. You are encouraged to properly
		936	install urxvt with privileges necessary for your OS now.
		937
		938	When rxvt-unicode detects that it runs setuid or setgid, it will fork
		939	into a helper process for privileged operations (pty handling on some
		940	systems, utmp/wtmp/lastlog handling on others) and drop privileges
		941	immediately. This is much safer than most other terminals that keep
		942	privileges while running (but is more relevant to urxvt, as it contains
		943	things as perl interpreters, which might be "helpful" to attackers).
		944
		945	This forking is done as the very first within main(), which is very early
		946	and reduces possible bugs to initialisation code run before main(), or
		947	things like the dynamic loader of your system, which should result in very
		948	little risk.
		949
417	=item On Solaris 9, many line-drawing characters are too wide.	950	=head3 On Solaris 9, many line-drawing characters are too wide.
418		951
419	Seems to be a known bug, read	952	Seems to be a known bug, read
420	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the	953	L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
421	following ugly workaround to get non-double-wide-characters working:	954	following ugly workaround to get non-double-wide-characters working:
422		955
423	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	956	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
424		957
425	=item My Compose (Multi_key) key is no longer working.
426
427	The most common causes for this are that either your locale is not set
428	correctly, or you specified a B<preeditStyle> that is not supported by
429	your input method. For example, if you specified B<OverTheSpot> and
430	your input method (e.g. the default input method handling Compose keys)
431	does not support this (for instance because it is not visual), then
432	rxvt-unicode will continue without an input method.
433
434	In this case either do not specify a B<preeditStyle> or specify more than
435	one pre-edit style, such as B<OverTheSpot,Root,None>.
436
437	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
438
439	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
440	international keyboards) or simply use ISO 14755 support to your
441	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
442	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
443	character and so on.
444
445	=item How can I keep rxvt-unicode from using reverse video so much?
446
447	First of all, make sure you are running with the right terminal settings
448	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
449	make sure you have specified colours for italic and bold, as otherwise
450	rxvt-unicode might use reverse video to simulate the effect:
451
452	URxvt.colorBD: white
453	URxvt.colorIT: green
454
455	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
456
457	For some unexplainable reason, some rare programs assume a very weird
458	colour palette when confronted with a terminal with more than the standard
459	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
460	these programs not to assume non-ISO colours without very good reasons.
461
462	In the meantime, you can either edit your C<rxvt-unicode> terminfo
463	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
464	fix colours but keep you from using other rxvt-unicode features.
465
466	=item I am on FreeBSD and rxvt-unicode does not seem to work at all.	958	=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
467		959
468	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined	960	Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
469	in your compile environment, or an implementation that implements it,	961	in your compile environment, or an implementation that implements it,
470	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that	962	wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
471	B<wchar_t> is represented as unicode.	963	B<wchar_t> is represented as unicode.
…		…
493		985
494	The rxvt-unicode author insists that the right way to fix this is in the	986	The rxvt-unicode author insists that the right way to fix this is in the
495	system libraries once and for all, instead of forcing every app to carry	987	system libraries once and for all, instead of forcing every app to carry
496	complete replacements for them :)	988	complete replacements for them :)
497		989
498	=item I use Solaris 9 and it doesn't compile/work/etc.	990	=head3 I use Solaris 9 and it doesn't compile/work/etc.
499		991
500	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst	992	Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
501	problems with C<wcwidth> and a compile problem.	993	problems with C<wcwidth> and a compile problem.
502		994
503	=item How can I use rxvt-unicode under cygwin?	995	=head3 How can I use rxvt-unicode under cygwin?
504		996
505	rxvt-unicode should compile and run out of the box on cygwin, using	997	rxvt-unicode should compile and run out of the box on cygwin, using
506	the X11 libraries that come with cygwin. libW11 emulation is no	998	the X11 libraries that come with cygwin. libW11 emulation is no
507	longer supported (and makes no sense, either, as it only supported a	999	longer supported (and makes no sense, either, as it only supported a
508	single font). I recommend starting the X-server in C<-multiwindow> or	1000	single font). I recommend starting the X-server in C<-multiwindow> or
…		…
511		1003
512	At the time of this writing, cygwin didn't seem to support any multi-byte	1004	At the time of this writing, cygwin didn't seem to support any multi-byte
513	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited	1005	encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
514	to 8-bit encodings.	1006	to 8-bit encodings.
515		1007
516	=item How does rxvt-unicode determine the encoding to use?
517
518	=item Is there an option to switch encodings?
519
520	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
521	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
522	UTF-8 or any other encodings with respect to terminal I/O.
523
524	The reasons is that there exists a perfectly fine mechanism for selecting
525	the encoding, doing I/O and (most important) communicating this to all
526	applications so everybody agrees on character properties such as width
527	and code number. This mechanism is the I<locale>. Applications not using
528	that info will have problems (for example, C<xterm> gets the width of
529	characters wrong as it uses it's own, locale-independent table under all
530	locales).
531
532	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
533	programs doing the same (that is, most) will automatically agree in the
534	interpretation of characters.
535
536	Unfortunately, there is no system-independent way to select locales, nor
537	is there a standard on how locale specifiers will look like.
538
539	On most systems, the content of the C<LC_CTYPE> environment variable
540	contains an arbitrary string which corresponds to an already-installed
541	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
542	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
543	(i.e. C<de> or C<german>) are also common.
544
545	Rxvt-unicode ignores all other locale categories, and except for
546	the encoding, ignores country or language-specific settings,
547	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
548	rxvt-unicode.
549
550	If you want to use a specific encoding you have to make sure you start
551	rxvt-unicode with the correct C<LC_CTYPE> category.
552
553	=item Can I switch locales at runtime?
554
555	Yes, using an escape sequence. Try something like this, which sets
556	rxvt-unicode's idea of C<LC_CTYPE>.
557
558	printf '\e]701;%s\007' ja_JP.SJIS
559
560	See also the previous answer.
561
562	Sometimes this capability is rather handy when you want to work in
563	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
564	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
565	first switches to a locale supported by xjdic and back later:
566
567	printf '\e]701;%s\007' ja_JP.SJIS
568	xjdic -js
569	printf '\e]701;%s\007' de_DE.UTF-8
570
571	You can also use xterm's C<luit> program, which usually works fine, except
572	for some locales where character width differs between program- and
573	rxvt-unicode-locales.
574
575	=item Can I switch the fonts at runtime?
576
577	Yes, using an escape sequence. Try something like this, which has the same
578	effect as using the C<-fn> switch, and takes effect immediately:
579
580	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
581
582	This is useful if you e.g. work primarily with japanese (and prefer a
583	japanese font), but you have to switch to chinese temporarily, where
584	japanese fonts would only be in your way.
585
586	You can think of this as a kind of manual ISO-2022 switching.
587
588	=item Why do italic characters look as if clipped?
589
590	Many fonts have difficulties with italic characters and hinting. For
591	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
592	Mono> completely fails in it's italic face. A workaround might be to
593	enable freetype autohinting, i.e. like this:
594
595	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
596	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
597
598	=item My input method wants <some encoding> but I want UTF-8, what can I do?
599
600	You can specify separate locales for the input method and the rest of the
601	terminal, using the resource C<imlocale>:
602
603	URxvt*imlocale: ja_JP.EUC-JP
604
605	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
606	use your input method. Please note, however, that you will not be able to
607	input characters outside C<EUC-JP> in a normal way then, as your input
608	method limits you.
609
610	=item Rxvt-unicode crashes when the X Input Method changes or exits.
611
612	Unfortunately, this is unavoidable, as the XIM protocol is racy by
613	design. Applications can avoid some crashes at the expense of memory
614	leaks, and Input Methods can avoid some crashes by careful ordering at
615	exit time. B<kinput2> (and derived input methods) generally succeeds,
616	while B<SCIM> (or similar input methods) fails. In the end, however,
617	crashes cannot be completely avoided even if both sides cooperate.
618
619	So the only workaround is not to kill your Input Method Servers.
620
621	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
622
623	Rxvt-unicode tries to obey the rule of not charging you for something you
624	don't use. One thing you should try is to configure out all settings that
625	you don't need, for example, Xft support is a resource hog by design,
626	when used. Compiling it out ensures that no Xft font will be loaded
627	accidentally when rxvt-unicode tries to find a font for your characters.
628
629	Also, many people (me included) like large windows and even larger
630	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
631	6 bytes per screen cell. For a 160x?? window this amounts to almost a
632	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
633	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
634	rxvt-unicode then uses 8 bytes per screen cell.
635
636	=item Can I speed up Xft rendering somehow?
637
638	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
639	it is simply slow. If you still want Xft fonts you might try to disable
640	antialiasing (by appending C<:antialias=false>), which saves lots of
641	memory and also speeds up rendering considerably.
642
643	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
644
645	Rxvt-unicode will use whatever you specify as a font. If it needs to
646	fall back to it's default font search list it will prefer X11 core
647	fonts, because they are small and fast, and then use Xft fonts. It has
648	antialiasing disabled for most of them, because the author thinks they
649	look best that way.
650
651	If you want antialiasing, you have to specify the fonts manually.
652
653	=item Mouse cut/paste suddenly no longer works.
654
655	Make sure that mouse reporting is actually turned off since killing
656	some editors prematurely may leave the mouse in mouse report mode. I've
657	heard that tcsh may use mouse reporting unless it otherwise specified. A
658	quick check is to see if cut/paste works when the Alt or Shift keys are
659	depressed. See @@RXVT_NAME@@(7)
660
661	=item What's with this bold/blink stuff?
662
663	If no bold colour is set via C<colorBD:>, bold will invert text using the
664	standard foreground colour.
665
666	For the standard background colour, blinking will actually make the
667	text blink when compiled with C<--enable-blinking>. with standard
668	colours. Without C<--enable-blinking>, the blink attribute will be
669	ignored.
670
671	On ANSI colours, bold/blink attributes are used to set high-intensity
672	foreground/background colors.
673
674	color0-7 are the low-intensity colors.
675
676	color8-15 are the corresponding high-intensity colors.
677
678	=item I don't like the screen colors. How do I change them?
679
680	You can change the screen colors at run-time using F<~/.Xdefaults>
681	resources (or as long-options).
682
683	Here are values that are supposed to resemble a VGA screen,
684	including the murky brown that passes for low-intensity yellow:
685
686	URxvt.color0: #000000
687	URxvt.color1: #A80000
688	URxvt.color2: #00A800
689	URxvt.color3: #A8A800
690	URxvt.color4: #0000A8
691	URxvt.color5: #A800A8
692	URxvt.color6: #00A8A8
693	URxvt.color7: #A8A8A8
694
695	URxvt.color8: #000054
696	URxvt.color9: #FF0054
697	URxvt.color10: #00FF54
698	URxvt.color11: #FFFF54
699	URxvt.color12: #0000FF
700	URxvt.color13: #FF00FF
701	URxvt.color14: #00FFFF
702	URxvt.color15: #FFFFFF
703
704	And here is a more complete set of non-standard colors described (not by
705	me) as "pretty girly".
706
707	URxvt.cursorColor: #dc74d1
708	URxvt.pointerColor: #dc74d1
709	URxvt.background: #0e0e0e
710	URxvt.foreground: #4ad5e1
711	URxvt.color0: #000000
712	URxvt.color8: #8b8f93
713	URxvt.color1: #dc74d1
714	URxvt.color9: #dc74d1
715	URxvt.color2: #0eb8c7
716	URxvt.color10: #0eb8c7
717	URxvt.color3: #dfe37e
718	URxvt.color11: #dfe37e
719	URxvt.color5: #9e88f0
720	URxvt.color13: #9e88f0
721	URxvt.color6: #73f7ff
722	URxvt.color14: #73f7ff
723	URxvt.color7: #e1dddd
724	URxvt.color15: #e1dddd
725
726	=item How can I start @@RXVT_NAME@@d in a race-free way?
727
728	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
729	display, create the listening socket and then fork.
730
731	=item What's with the strange Backspace/Delete key behaviour?
732
733	Assuming that the physical Backspace key corresponds to the
734	BackSpace keysym (not likely for Linux ... see the following
735	question) there are two standard values that can be used for
736	Backspace: C<^H> and C<^?>.
737
738	Historically, either value is correct, but rxvt-unicode adopts the debian
739	policy of using C<^?> when unsure, because it's the one only only correct
740	choice :).
741
742	Rxvt-unicode tries to inherit the current stty settings and uses the value
743	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
744	started from a terminal (say, from a menu or by remote shell), then the
745	system value of `erase', which corresponds to CERASE in <termios.h>, will
746	be used (which may not be the same as your stty setting).
747
748	For starting a new rxvt-unicode:
749
750	# use Backspace = ^H
751	$ stty erase ^H
752	$ @@RXVT_NAME@@
753
754	# use Backspace = ^?
755	$ stty erase ^?
756	$ @@RXVT_NAME@@
757
758	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
759
760	For an existing rxvt-unicode:
761
762	# use Backspace = ^H
763	$ stty erase ^H
764	$ echo -n "^[[36h"
765
766	# use Backspace = ^?
767	$ stty erase ^?
768	$ echo -n "^[[36l"
769
770	This helps satisfy some of the Backspace discrepancies that occur, but
771	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
772	properly reflects that.
773
774	The Delete key is a another casualty of the ill-defined Backspace problem.
775	To avoid confusion between the Backspace and Delete keys, the Delete
776	key has been assigned an escape sequence to match the vt100 for Execute
777	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
778
779	Some other Backspace problems:
780
781	some editors use termcap/terminfo,
782	some editors (vim I'm told) expect Backspace = ^H,
783	GNU Emacs (and Emacs-like editors) use ^H for help.
784
785	Perhaps someday this will all be resolved in a consistent manner.
786
787	=item I don't like the key-bindings. How do I change them?
788
789	There are some compile-time selections available via configure. Unless
790	you have run "configure" with the C<--disable-resources> option you can
791	use the `keysym' resource to alter the keystrings associated with keysyms.
792
793	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
794
795	URxvt.keysym.Home: \033[1~
796	URxvt.keysym.End: \033[4~
797	URxvt.keysym.C-apostrophe: \033<C-'>
798	URxvt.keysym.C-slash: \033<C-/>
799	URxvt.keysym.C-semicolon: \033<C-;>
800	URxvt.keysym.C-grave: \033<C-`>
801	URxvt.keysym.C-comma: \033<C-,>
802	URxvt.keysym.C-period: \033<C-.>
803	URxvt.keysym.C-0x60: \033<C-`>
804	URxvt.keysym.C-Tab: \033<C-Tab>
805	URxvt.keysym.C-Return: \033<C-Return>
806	URxvt.keysym.S-Return: \033<S-Return>
807	URxvt.keysym.S-space: \033<S-Space>
808	URxvt.keysym.M-Up: \033<M-Up>
809	URxvt.keysym.M-Down: \033<M-Down>
810	URxvt.keysym.M-Left: \033<M-Left>
811	URxvt.keysym.M-Right: \033<M-Right>
812	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
813	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
814	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
815
816	See some more examples in the documentation for the B<keysym> resource.
817
818	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
819	How do I make use of them? For example, the Sun Keyboard type 4
820	has the following mappings that rxvt-unicode doesn't recognize.
821
822	KP_Insert == Insert
823	F22 == Print
824	F27 == Home
825	F29 == Prior
826	F33 == End
827	F35 == Next
828
829	Rather than have rxvt-unicode try to accommodate all the various possible
830	keyboard mappings, it is better to use `xmodmap' to remap the keys as
831	required for your particular machine.
832
833	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
834	I need this to decide about setting colors etc.
835
836	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
837	check and see if that is set. Note that several programs, JED, slrn,
838	Midnight Commander automatically check this variable to decide whether or
839	not to use color.
840
841	=item How do I set the correct, full IP address for the DISPLAY variable?
842
843	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
844	insecure mode then it is possible to use the following shell script
845	snippets to correctly set the display. If your version of rxvt-unicode
846	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
847	the COLORTERM variable can be used to distinguish rxvt-unicode from a
848	regular xterm.
849
850	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
851	snippets:
852
853	# Bourne/Korn/POSIX family of shells:
854	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
855	if [ ${TERM:-foo} = xterm ]; then
856	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
857	echo -n '^[Z'
858	read term_id
859	stty icanon echo
860	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
861	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
862	read DISPLAY # set it in our local shell
863	fi
864	fi
865
866	=item How do I compile the manual pages for myself?
867
868	You need to have a recent version of perl installed as F</usr/bin/perl>,
869	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
870	the doc subdirectory and enter C<make alldoc>.
871
872	=item My question isn't answered here, can I ask a human?
873
874	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
875	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
876	interested in learning about new and exciting problems (but not FAQs :).
877
878	=back
879
880	=head1 RXVT TECHNICAL REFERENCE	1008	=head1 RXVT-UNICODE TECHNICAL REFERENCE
881		1009
882	=head1 DESCRIPTION	1010	=head1 DESCRIPTION
883		1011
884	The rest of this document describes various technical aspects of	1012	The rest of this document describes various technical aspects of
885	B<rxvt-unicode>. First the description of supported command sequences,	1013	B<rxvt-unicode>. First the description of supported command sequences,
886	followed by menu and pixmap support and last by a description of all	1014	followed by pixmap support and last by a description of all features
887	features selectable at C<configure> time.	1015	selectable at C<configure> time.
888		1016
889	=head1 Definitions	1017	=head1 Definitions
890		1018
891	=over 4	1019	=over 4
892		1020
…		…
1460	B<< C<h> >> Send Mouse X & Y on button press.	1588	B<< C<h> >> Send Mouse X & Y on button press.
1461	B<< C<l> >> No mouse reporting.	1589	B<< C<l> >> No mouse reporting.
1462		1590
1463	=end table	1591	=end table
1464		1592
1465	=item B<< C<Ps = 10> >> (B<rxvt>)
1466
1467	=begin table
1468
1469	B<< C<h> >> menuBar visible
1470	B<< C<l> >> menuBar invisible
1471
1472	=end table
1473
1474	=item B<< C<Ps = 25> >>	1593	=item B<< C<Ps = 25> >>
1475		1594
1476	=begin table	1595	=begin table
1477		1596
1478	B<< C<h> >> Visible cursor {cnorm/cvvis}	1597	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
1660	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>	1779	B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >>
1661	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>	1780	B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >>
1662	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>	1781	B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >>
1663	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]	1782	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1664	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]	1783	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1665	B<< C<Ps = 20> >> Change default background to B<< C<Pt> >>	1784	B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM).
1666	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.	1785	B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>.
1667	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>	1786	B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented>
1668	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.	1787	B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>.
1669	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> >>	1788	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> >>
1670	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>	1789	B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >>
1671	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).	1790	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).
1672	B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar).	1791	B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>.
1673	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>	1792	B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >>
1674	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).	1793	B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
1675	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>	1794	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
1676	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>	1795	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1677	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.	1796	B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
…		…
1684		1803
1685	=end table	1804	=end table
1686		1805
1687	=back	1806	=back
1688		1807
1689	X<menuBar>
1690
1691	=head1 menuBar
1692
1693	B<< The exact syntax used is I<almost> solidified. >>
1694	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1695	menuBar.
1696
1697	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1698	omitted: use B<./> to specify a menu relative to the current menu.
1699
1700	=head2 Overview of menuBar operation
1701
1702	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1703	of C<Pt> can be used for a variety of tasks:
1704
1705	At the top level is the current menuBar which is a member of a circular
1706	linked-list of other such menuBars.
1707
1708	The menuBar acts as a parent for the various drop-down menus, which in
1709	turn, may have labels, separator lines, menuItems and subMenus.
1710
1711	The menuItems are the useful bits: you can use them to mimic keyboard
1712	input or even to send text or escape sequences back to rxvt.
1713
1714	The menuBar syntax is intended to provide a simple yet robust method of
1715	constructing and manipulating menus and navigating through the
1716	menuBars.
1717
1718	The first step is to use the tag B<< [menu:I<name>] >> which creates
1719	the menuBar called I<name> and allows access. You may now or menus,
1720	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1721	menuBar access as B<readonly> to prevent accidental corruption of the
1722	menus. To re-access the current menuBar for alterations, use the tag
1723	B<[menu]>, make the alterations and then use B<[done]>
1724
1725	X<menuBarCommands>
1726
1727	=head2 Commands
1728
1729	=over 4
1730
1731	=item B<< [menu:+I<name>] >>
1732
1733	access the named menuBar for creation or alteration. If a new menuBar
1734	is created, it is called I<name> (max of 15 chars) and the current
1735	menuBar is pushed onto the stack
1736
1737	=item B<[menu]>
1738
1739	access the current menuBar for alteration
1740
1741	=item B<< [title:+I<string>] >>
1742
1743	set the current menuBar's title to I<string>, which may contain the
1744	following format specifiers:
1745
1746	B<%n> rxvt name (as per the B<-name> command-line option)
1747	B<%v> rxvt version
1748	B<%%> literal B<%> character
1749
1750	=item B<[done]>
1751
1752	set menuBar access as B<readonly>.
1753	End-of-file tag for B<< [read:+I<file>] >> operations.
1754
1755	=item B<< [read:+I<file>] >>
1756
1757	read menu commands directly from I<file> (extension ".menu" will be
1758	appended if required.) Start reading at a line with B<[menu]> or B<<
1759	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1760
1761	Blank and comment lines (starting with B<#>) are ignored. Actually,
1762	since any invalid menu commands are also ignored, almost anything could
1763	be construed as a comment line, but this may be tightened up in the
1764	future ... so don't count on it!.
1765
1766	=item B<< [read:+I<file>;+I<name>] >>
1767
1768	The same as B<< [read:+I<file>] >>, but start reading at a line with
1769	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1770	B<[done]> is encountered.
1771
1772	=item B<[dump]>
1773
1774	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1775	later rereading.
1776
1777	=item B<[rm:name]>
1778
1779	remove the named menuBar
1780
1781	=item B<[rm] [rm:]>
1782
1783	remove the current menuBar
1784
1785	=item B<[rm*] [rm:*]>
1786
1787	remove all menuBars
1788
1789	=item B<[swap]>
1790
1791	swap the top two menuBars
1792
1793	=item B<[prev]>
1794
1795	access the previous menuBar
1796
1797	=item B<[next]>
1798
1799	access the next menuBar
1800
1801	=item B<[show]>
1802
1803	Enable display of the menuBar
1804
1805	=item B<[hide]>
1806
1807	Disable display of the menuBar
1808
1809	=item B<< [pixmap:+I<name>] >>
1810
1811	=item B<< [pixmap:+I<name>;I<scaling>] >>
1812
1813	(set the background pixmap globally
1814
1815	B<< A Future implementation I<may> make this local to the menubar >>)
1816
1817	=item B<< [:+I<command>:] >>
1818
1819	ignore the menu readonly status and issue a I<command> to or a menu or
1820	menuitem or change the ; a useful shortcut for setting the quick arrows
1821	from a menuBar.
1822
1823	=back
1824
1825	X<menuBarAdd>
1826
1827	=head2 Adding and accessing menus
1828
1829	The following commands may also be B<+> prefixed.
1830
1831	=over 4
1832
1833	=item B</+>
1834
1835	access menuBar top level
1836
1837	=item B<./+>
1838
1839	access current menu level
1840
1841	=item B<../+>
1842
1843	access parent menu (1 level up)
1844
1845	=item B<../../>
1846
1847	access parent menu (multiple levels up)
1848
1849	=item B<< I</path/>menu >>
1850
1851	add/access menu
1852
1853	=item B<< I</path/>menu/* >>
1854
1855	add/access menu and clear it if it exists
1856
1857	=item B<< I</path/>{-} >>
1858
1859	add separator
1860
1861	=item B<< I</path/>{item} >>
1862
1863	add B<item> as a label
1864
1865	=item B<< I</path/>{item} action >>
1866
1867	add/alter I<menuitem> with an associated I<action>
1868
1869	=item B<< I</path/>{item}{right-text} >>
1870
1871	add/alter I<menuitem> with B<right-text> as the right-justified text
1872	and as the associated I<action>
1873
1874	=item B<< I</path/>{item}{rtext} action >>
1875
1876	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1877	the right-justified text.
1878
1879	=back
1880
1881	=over 4
1882
1883	=item Special characters in I<action> must be backslash-escaped:
1884
1885	B<\a \b \E \e \n \r \t \octal>
1886
1887	=item or in control-character notation:
1888
1889	B<^@, ^A .. ^Z .. ^_, ^?>
1890
1891	=back
1892
1893	To send a string starting with a B<NUL> (B<^@>) character to the
1894	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1895	the first of which will be stripped off and the balance directed to the
1896	program. Otherwise if I<action> begins with B<NUL> followed by
1897	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1898	balance is sent back to rxvt.
1899
1900	As a convenience for the many Emacs-type editors, I<action> may start
1901	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1902	appended if missed from B<M-x> commands.
1903
1904	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1905	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1906
1907	=over 4
1908
1909	=item For example,
1910
1911	B<M-xapropos> is equivalent to B<\Exapropos\r>
1912
1913	=item and
1914
1915	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1916
1917	=back
1918
1919	The option B<< {I<right-rtext>} >> will be right-justified. In the
1920	absence of a specified action, this text will be used as the I<action>
1921	as well.
1922
1923	=over 4
1924
1925	=item For example,
1926
1927	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1928
1929	=back
1930
1931	The left label I<is> necessary, since it's used for matching, but
1932	implicitly hiding the left label (by using same name for both left and
1933	right labels), or explicitly hiding the left label (by preceeding it
1934	with a dot), makes it possible to have right-justified text only.
1935
1936	=over 4
1937
1938	=item For example,
1939
1940	B</File/{Open}{Open} Open-File-Action>
1941
1942	=item or hiding it
1943
1944	B</File/{.anylabel}{Open} Open-File-Action>
1945
1946	=back
1947
1948	X<menuBarRemove>
1949
1950	=head2 Removing menus
1951
1952	=over 4
1953
1954	=item B<< -/*+ >>
1955
1956	remove all menus from the menuBar, the same as B<[clear]>
1957
1958	=item B<< -+I</path>menu+ >>
1959
1960	remove menu
1961
1962	=item B<< -+I</path>{item}+ >>
1963
1964	remove item
1965
1966	=item B<< -+I</path>{-} >>
1967
1968	remove separator)
1969
1970	=item B<-/path/menu/*>
1971
1972	remove all items, separators and submenus from menu
1973
1974	=back
1975
1976	X<menuBarArrows>
1977
1978	=head2 Quick Arrows
1979
1980	The menus also provide a hook for I<quick arrows> to provide easier
1981	user access. If nothing has been explicitly set, the default is to
1982	emulate the curror keys. The syntax permits each arrow to be altered
1983	individually or all four at once without re-entering their common
1984	beginning/end text. For example, to explicitly associate cursor actions
1985	with the arrows, any of the following forms could be used:
1986
1987	=over 4
1988
1989	=item B<< <r>+I<Right> >>
1990
1991	=item B<< <l>+I<Left> >>
1992
1993	=item B<< <u>+I<Up> >>
1994
1995	=item B<< <d>+I<Down> >>
1996
1997	Define actions for the respective arrow buttons
1998
1999	=item B<< <b>+I<Begin> >>
2000
2001	=item B<< <e>+I<End> >>
2002
2003	Define common beginning/end parts for I<quick arrows> which used in
2004	conjunction with the above <r> <l> <u> <d> constructs
2005
2006	=back
2007
2008	=over 4
2009
2010	=item For example, define arrows individually,
2011
2012	<u>\E[A
2013
2014	<d>\E[B
2015
2016	<r>\E[C
2017
2018	<l>\E[D
2019
2020	=item or all at once
2021
2022	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
2023
2024	=item or more compactly (factoring out common parts)
2025
2026	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
2027
2028	=back
2029
2030	X<menuBarSummary>
2031
2032	=head2 Command Summary
2033
2034	A short summary of the most I<common> commands:
2035
2036	=over 4
2037
2038	=item [menu:name]
2039
2040	use an existing named menuBar or start a new one
2041
2042	=item [menu]
2043
2044	use the current menuBar
2045
2046	=item [title:string]
2047
2048	set menuBar title
2049
2050	=item [done]
2051
2052	set menu access to readonly and, if reading from a file, signal EOF
2053
2054	=item [done:name]
2055
2056	if reading from a file using [read:file;name] signal EOF
2057
2058	=item [rm:name]
2059
2060	remove named menuBar(s)
2061
2062	=item [rm] [rm:]
2063
2064	remove current menuBar
2065
2066	=item [rm*] [rm:*]
2067
2068	remove all menuBar(s)
2069
2070	=item [swap]
2071
2072	swap top two menuBars
2073
2074	=item [prev]
2075
2076	access the previous menuBar
2077
2078	=item [next]
2079
2080	access the next menuBar
2081
2082	=item [show]
2083
2084	map menuBar
2085
2086	=item [hide]
2087
2088	unmap menuBar
2089
2090	=item [pixmap;file]
2091
2092	=item [pixmap;file;scaling]
2093
2094	set a background pixmap
2095
2096	=item [read:file]
2097
2098	=item [read:file;name]
2099
2100	read in a menu from a file
2101
2102	=item [dump]
2103
2104	dump out all menuBars to /tmp/rxvt-PID
2105
2106	=item /
2107
2108	access menuBar top level
2109
2110	=item ./
2111
2112	=item ../
2113
2114	=item ../../
2115
2116	access current or parent menu level
2117
2118	=item /path/menu
2119
2120	add/access menu
2121
2122	=item /path/{-}
2123
2124	add separator
2125
2126	=item /path/{item}{rtext} action
2127
2128	add/alter menu item
2129
2130	=item -/*
2131
2132	remove all menus from the menuBar
2133
2134	=item -/path/menu
2135
2136	remove menu items, separators and submenus from menu
2137
2138	=item -/path/menu
2139
2140	remove menu
2141
2142	=item -/path/{item}
2143
2144	remove item
2145
2146	=item -/path/{-}
2147
2148	remove separator
2149
2150	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
2151
2152	menu quick arrows
2153
2154	=back
2155	X<XPM>	1808	X<XPM>
2156		1809
2157	=head1 XPM	1810	=head1 XPM
2158		1811
2159	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value	1812	For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
…		…
2258	=begin table	1911	=begin table
2259		1912
2260	4 Shift	1913	4 Shift
2261	8 Meta	1914	8 Meta
2262	16 Control	1915	16 Control
2263	32 Double Click I<(Rxvt extension)>	1916	32 Double Click I<(rxvt extension)>
2264		1917
2265	=end table	1918	=end table
2266		1919
2267	Col = B<< C<< <x> - SPACE >> >>	1920	Col = B<< C<< <x> - SPACE >> >>
2268		1921
…		…
2406	alternative input methods (e.g. kinput2) and will also correctly	2059	alternative input methods (e.g. kinput2) and will also correctly
2407	set up the input for people using dead keys or compose keys.	2060	set up the input for people using dead keys or compose keys.
2408		2061
2409	=item --enable-unicode3 (default: off)	2062	=item --enable-unicode3 (default: off)
2410		2063
		2064	Recommended to stay off unless you really need non-BMP characters.
		2065
2411	Enable direct support for displaying unicode codepoints above	2066	Enable direct support for displaying unicode codepoints above
2412	65535 (the basic multilingual page). This increases storage	2067	65535 (the basic multilingual page). This increases storage
2413	requirements per character from 2 to 4 bytes. X11 fonts do not yet	2068	requirements per character from 2 to 4 bytes. X11 fonts do not yet
2414	support these extra characters, but Xft does.	2069	support these extra characters, but Xft does.
2415		2070
…		…
2425	composite characters. This is required for proper viewing of text	2080	composite characters. This is required for proper viewing of text
2426	where accents are encoded as seperate unicode characters. This is	2081	where accents are encoded as seperate unicode characters. This is
2427	done by using precomposited characters when available or creating	2082	done by using precomposited characters when available or creating
2428	new pseudo-characters when no precomposed form exists.	2083	new pseudo-characters when no precomposed form exists.
2429		2084
2430	Without --enable-unicode3, the number of additional precomposed characters	2085	Without --enable-unicode3, the number of additional precomposed
2431	is rather limited (2048, if this is full, rxvt-unicode will use the	2086	characters is somewhat limited (the 6400 private use characters will be
2432	private use area, extending the number of combinations to 8448). With
2433	--enable-unicode3, no practical limit exists.	2087	(ab-)used). With --enable-unicode3, no practical limit exists.
2434		2088
2435	This option will also enable storage (but not display) of characters	2089	This option will also enable storage (but not display) of characters
2436	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2090	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2437		2091
2438	The combining table also contains entries for arabic presentation forms,	2092	The combining table also contains entries for arabic presentation forms,
2439	but these are not currently used. Bug me if you want these to be used (and	2093	but these are not currently used. Bug me if you want these to be used (and
2440	tell me how these are to be used...).	2094	tell me how these are to be used...).
2441		2095
2442	=item --enable-fallback(=CLASS) (default: Rxvt)	2096	=item --enable-fallback(=CLASS) (default: Rxvt)
2443		2097
2444	When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.	2098	When reading resource settings, also read settings for class CLASS. To
		2099	disable resource fallback use --disable-fallback.
2445		2100
2446	=item --with-res-name=NAME (default: urxvt)	2101	=item --with-res-name=NAME (default: urxvt)
2447		2102
2448	Use the given name as default application name when	2103	Use the given name as default application name when
2449	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2104	reading resources. Specify --with-res-name=rxvt to replace rxvt.
…		…
2486		2141
2487	=item --enable-tinting (default: on)	2142	=item --enable-tinting (default: on)
2488		2143
2489	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).	2144	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2490		2145
2491	=item --enable-menubar (default: off) [DEPRECATED]
2492
2493	Add support for our menu bar system (this interacts badly with dynamic
2494	locale switching currently). This option is DEPRECATED and will be removed
2495	in the future.
2496
2497	=item --enable-rxvt-scroll (default: on)	2146	=item --enable-rxvt-scroll (default: on)
2498		2147
2499	Add support for the original rxvt scrollbar.	2148	Add support for the original rxvt scrollbar.
2500		2149
2501	=item --enable-next-scroll (default: on)	2150	=item --enable-next-scroll (default: on)
…		…
2510		2159
2511	Add support for a very unobtrusive, plain-looking scrollbar that	2160	Add support for a very unobtrusive, plain-looking scrollbar that
2512	is the favourite of the rxvt-unicode author, having used it for	2161	is the favourite of the rxvt-unicode author, having used it for
2513	many years.	2162	many years.
2514		2163
2515	=item --enable-half-shadow (default: off)
2516
2517	Make shadows on the scrollbar only half the normal width & height.
2518	only applicable to rxvt scrollbars.
2519
2520	=item --enable-ttygid (default: off)	2164	=item --enable-ttygid (default: off)
2521		2165
2522	Change tty device setting to group "tty" - only use this if	2166	Change tty device setting to group "tty" - only use this if
2523	your system uses this type of security.	2167	your system uses this type of security.
2524		2168
…		…
2532	do it.	2176	do it.
2533		2177
2534	=item --disable-resources	2178	=item --disable-resources
2535		2179
2536	Removes any support for resource checking.	2180	Removes any support for resource checking.
2537
2538	=item --enable-strings (default: off)
2539
2540	Add support for our possibly faster memset() function and other
2541	various routines, overriding your system's versions which may
2542	have been hand-crafted in assembly or may require extra libraries
2543	to link in. (this breaks ANSI-C rules and has problems on many
2544	GNU/Linux systems).
2545		2181
2546	=item --disable-swapscreen	2182	=item --disable-swapscreen
2547		2183
2548	Remove support for secondary/swap screen.	2184	Remove support for secondary/swap screen.
2549		2185
…		…
2558		2194
2559	MWM-hints	2195	MWM-hints
2560	EWMH-hints (pid, utf8 names) and protocols (ping)	2196	EWMH-hints (pid, utf8 names) and protocols (ping)
2561	seperate underline colour (-underlineColor)	2197	seperate underline colour (-underlineColor)
2562	settable border widths and borderless switch (-w, -b, -bl)	2198	settable border widths and borderless switch (-w, -b, -bl)
		2199	visual depth selection (-depth)
2563	settable extra linespacing /-lsp)	2200	settable extra linespacing /-lsp)
2564	iso-14755-2 and -3, and visual feedback	2201	iso-14755-2 and -3, and visual feedback
2565	backindex and forwardindex escape sequence
2566	window op and some xterm/OSC escape sequences
2567	tripleclickwords (-tcw)	2202	tripleclickwords (-tcw)
2568	settable insecure mode (-insecure)	2203	settable insecure mode (-insecure)
2569	keysym remapping support	2204	keysym remapping support
2570	cursor blinking and underline cursor (-cb, -uc)	2205	cursor blinking and underline cursor (-cb, -uc)
2571	XEmbed support (-embed)	2206	XEmbed support (-embed)
2572	user-pty (-pty-fd)	2207	user-pty (-pty-fd)
2573	hold on exit (-hold)	2208	hold on exit (-hold)
2574	skip builtin block graphics (-sbg)	2209	skip builtin block graphics (-sbg)
		2210
		2211	It also enabled some non-essential features otherwise disabled, such as:
		2212
		2213	some round-trip time optimisations
		2214	nearest color allocation on pseudocolor screens
		2215	UTF8_STRING supporr for selection
2575	sgr modes 90..97 and 100..107	2216	sgr modes 90..97 and 100..107
		2217	backindex and forwardindex escape sequences
		2218	view change/zero scorllback esacpe sequences
		2219	locale switching escape sequence
		2220	window op and some xterm/OSC escape sequences
		2221	rectangular selections
		2222	trailing space removal for selections
		2223	verbose X error handling
2576		2224
2577	=item --enable-iso14755 (default: on)	2225	=item --enable-iso14755 (default: on)
2578		2226
2579	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2227	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2580	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by	2228	F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
…		…
2623		2271
2624	=item --enable-pointer-blank (default: on)	2272	=item --enable-pointer-blank (default: on)
2625		2273
2626	Add support to have the pointer disappear when typing or inactive.	2274	Add support to have the pointer disappear when typing or inactive.
2627		2275
2628	=item --enable-perl (default: off)	2276	=item --enable-perl (default: on)
2629		2277
2630	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>	2278	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2631	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files	2279	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
2632	in F<src/perl-ext/> for the extensions that are installed by default. The	2280	in F<src/perl-ext/> for the extensions that are installed by default. The
2633	perl interpreter that is used can be specified via the C<PERL> environment	2281	perl interpreter that is used can be specified via the C<PERL> environment

Diff Legend

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