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.75 by root, Wed Jan 11 05:29:40 2006 UTC vs.
Revision 1.105 by root, Tue Jan 31 21:00:26 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
		27	=head2 Meta, Features & Commandline Issues
		28
		29	=head3 My question isn't answered here, can I ask a human?
		30
		31	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
		32	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
		33	interested in learning about new and exciting problems (but not FAQs :).
		34
		35	=head3 Does it support tabs, can I have a tabbed rxvt-unicode?
		36
		37	Beginning with version 7.3, there is a perl extension that implements a
		38	simple tabbed terminal. It is installed by default, so any of these should
		39	give you tabs:
		40
		41	@@URXVT_NAME@@ -pe tabbed
		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
29	=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?
30		117
31	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
32	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
33	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
34	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
…		…
66	(21152k + extra 4204k in separate processes) or konsole (22200k + extra	153	(21152k + extra 4204k in separate processes) or konsole (22200k + extra
67	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
68	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
69	extremely well *g*.	156	extremely well *g*.
70		157
71	=item Why C++, isn't that unportable/bloated/uncool?	158	=head3 Why C++, isn't that unportable/bloated/uncool?
72		159
73	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
74	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
75	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
76	shorter: It simply wouldn't exist without C++.	163	shorter: It simply wouldn't exist without C++.
…		…
100	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)	187	/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
101		188
102	No large bloated libraries (of course, none were linked in statically),	189	No large bloated libraries (of course, none were linked in statically),
103	except maybe libX11 :)	190	except maybe libX11 :)
104		191
105	=item Does it support tabs, can I have a tabbed rxvt-unicode?
106		192
107	rxvt-unicode does not directly support tabs. It will work fine with	193	=head2 Rendering, Font & Look and Feel Issues
108	tabbing functionality of many window managers or similar tabbing programs,
109	and its embedding-features allow it to be embedded into other programs,
110	as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
111	module, which features a tabbed urxvt (murxvt) terminal as an example
112	embedding application.
113		194
114	=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?
115		196
116	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
117	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
118	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
119	daemon.	200	of passage: ... and you failed.
120		201
121	=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!
122		204
123	The Debian GNU/Linux package of rxvt-unicode in sarge contains large	205	1. Use inheritPixmap:
124	patches that considerably change the behaviour of rxvt-unicode. Before
125	reporting a bug to the original rxvt-unicode author please download and
126	install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
127	and try to reproduce the problem. If you cannot, chances are that the
128	problems are specific to Debian GNU/Linux, in which case it should be
129	reported via the Debian Bug Tracking System (use C<reportbug> to report
130	the bug).
131		206
132	For other problems that also affect the Debian package, you can and	207	Esetroot wallpaper.jpg
133	probably should use the Debian BTS, too, because, after all, it's also a	208	@@URXVT_NAME@@ -ip -tint red -sh 40
134	bug in the Debian version and it serves as a reminder for other users that
135	might encounter the same issue.
136		209
137	=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.
138		212
139	You should build one binary with the default options. F<configure>	213	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
140	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
141	runtime-switchable, too, so there is usually no drawback to enbaling them,	215	your picture with gimp or any other tool:
142	except higher disk and possibly memory usage. The perl interpreter should
143	be enabled, as important functionality (menus, selection, likely more in
144	the future) depends on it.
145		216
146	You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources	217	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
147	system-wide (except maybe with C<defaults>). This will result in useful	218	@@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
148	behaviour. If your distribution aims at low memory, add an empty
149	C<perl-ext-common> resource to the app-defaults file. This will keep the
150	perl interpreter disabled until the user enables it.
151		219
152	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
153	one with C<--disable-everything> (very useful) and a maximal one with	221	are unable to read.
154	C<--enable-everything> (less useful, it will be very big due to a lot of
155	encodings built-in that increase download times and are rarely used).
156		222
157	=item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?	223	3. Use an ARGB visual:
158		224
159	Likely not. While I honestly try to make it secure, and am probably	225	@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
160	not bad at it, I think it is simply unreasonable to expect all of
161	freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to all be
162	secure. Also, rxvt-unicode disables some options when it detects that it
163	runs setuid or setgid, which is not nice.
164		226
165	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
166	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
167	ptys, but some need it for utmp support). If rxvt-unicode doesn't support	229	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
168	the library/setuid helper that your OS needs I'll be happy to assist you	230	bugfixes and workarounds for Xft and Xlib to make it work, but that
169	in implementing support for it.	231	doesn't mean that your WM has the required kludges in place.
170		232
171	So, while setuid/setgid operation is supported and not a problem on your	233	4. Use xcompmgr and let it do the job:
172	typical single-user-no-other-logins unix desktop, always remember that
173	its an awful lot of code, most of which isn't checked for security issues
174	regularly.
175		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
176	=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?
177		667
178	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
179	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).
180		670
181	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
…		…
197	resource to set it:	687	resource to set it:
198		688
199	URxvt.termName: rxvt	689	URxvt.termName: rxvt
200		690
201	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
202	the rxvt terminfo file with the rxvt-unicode one.	692	the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
203		693
204	=item C<tic> outputs some error when compiling the terminfo entry.	694	=head3 C<tic> outputs some error when compiling the terminfo entry.
205		695
206	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
207	C<enacs=\E[0@> and try again.	697	C<enacs=\E[0@> and try again.
208		698
209	=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@@.
210		700
		701	See next entry.
		702
211	=item I need a termcap file entry.	703	=head3 I need a termcap file entry.
212		704
213	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
214	systems still compile some programs using the long-obsoleted termcap	706	systems still compile some programs using the long-obsoleted termcap
215	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
216	for C<rxvt-unicode>.	708	for C<rxvt-unicode>.
…		…
242	: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:\
243	: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:\
244	: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:\
245	:vs=\E[?25h:	737	:vs=\E[?25h:
246		738
247	=item Why does C<ls> no longer have coloured output?	739	=head3 Why does C<ls> no longer have coloured output?
248		740
249	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
250	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
251	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
252	with most other terminals supporting colour). Either add:	744	with most other terminals supporting colour). Either add:
…		…
257		749
258	alias ls='ls --color=auto'	750	alias ls='ls --color=auto'
259		751
260	to your C<.profile> or C<.bashrc>.	752	to your C<.profile> or C<.bashrc>.
261		753
262	=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?
263		755
		756	See next entry.
		757
264	=item Why doesn't vim/emacs etc. make use of italic?	758	=head3 Why doesn't vim/emacs etc. make use of italic?
265		759
		760	See next entry.
		761
266	=item Why are the secondary screen-related options not working properly?	762	=head3 Why are the secondary screen-related options not working properly?
267		763
268	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
269	distributions (most notably Debian GNU/Linux) break rxvt-unicode	765	distributions (most notably Debian GNU/Linux) break rxvt-unicode
270	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
271	features. Unfortunately, some of these (most notably, again, Debian	767	features. Unfortunately, some of these (most notably, again, Debian
272	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
273	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
274	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
275	how to do this).	771	how to do this).
276		772
277	=item My numerical keypad acts weird and generates differing output?
278		773
279	Some Debian GNUL/Linux users seem to have this problem, although no	774	=head2 Encoding / Locale / Input Method Issues
280	specific details were reported so far. It is possible that this is caused
281	by the wrong C<TERM> setting, although the details of wether and how
282	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
283	keymap. See the answer to the previous question, and please report if that
284	helped.
285		775
286	=item Rxvt-unicode does not seem to understand the selected encoding?	776	=head3 Rxvt-unicode does not seem to understand the selected encoding?
287		777
		778	See next entry.
		779
288	=item Unicode does not seem to work?	780	=head3 Unicode does not seem to work?
289		781
290	If you encounter strange problems like typing an accented character but	782	If you encounter strange problems like typing an accented character but
291	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
292	subtly garbled, then you should check your locale settings.	784	subtly garbled, then you should check your locale settings.
293		785
…		…
313		805
314	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
315	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
316	support locales :(	808	support locales :(
317		809
318	=item Why do some characters look so much different than others?	810	=head3 How does rxvt-unicode determine the encoding to use?
319		811
320	=item How does rxvt-unicode choose fonts?	812	See next entry.
321		813
322	Most fonts do not contain the full range of Unicode, which is	814	=head3 Is there an option to switch encodings?
323	fine. Chances are that the font you (or the admin/package maintainer of
324	your system/os) have specified does not cover all the characters you want
325	to display.
326		815
327	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
328	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
329	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.
330	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
331	intelligence to detect that a specific glyph is wrong: it has to believe
332	the font that the characters it claims to contain indeed look correct.
333		819
334	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
335	e.g.:	821	the encoding, doing I/O and (most important) communicating this to all
336		822	applications so everybody agrees on character properties such as width
337	@@RXVT_NAME@@ -fn basefont,font2,font3...	823	and code number. This mechanism is the I<locale>. Applications not using
338		824	that info will have problems (for example, C<xterm> gets the width of
339	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
340	font. If the base font does not contain the character, it will go to the
341	next font, and so on. Specifying your own fonts will also speed up this
342	search and use less resources within rxvt-unicode and the X-server.
343
344	The only limitation is that none of the fonts may be larger than the base
345	font, as the base font defines the terminal character cell size, which
346	must be the same due to the way terminals work.
347
348	=item Why do some chinese characters look so different than others?
349
350	This is because there is a difference between script and language --
351	rxvt-unicode does not know which language the text that is output is,
352	as it only knows the unicode character codes. If rxvt-unicode first
353	sees a japanese/chinese character, it might choose a japanese font for
354	display. Subsequent japanese characters will use that font. Now, many
355	chinese characters aren't represented in japanese fonts, so when the first
356	non-japanese character comes up, rxvt-unicode will look for a chinese font
357	-- unfortunately at this point, it will still use the japanese font for
358	chinese characters that are also in the japanese font.
359
360	The workaround is easy: just tag a chinese font at the end of your font
361	list (see the previous question). The key is to view the font list as
362	a preference list: If you expect more japanese, list a japanese font
363	first. If you expect more chinese, put a chinese font first.
364
365	In the future it might be possible to switch language preferences at
366	runtime (the internal data structure has no problem with using different
367	fonts for the same character at the same time, but no interface for this
368	has been designed yet).
369
370	Until then, you might get away with switching fonts at runtime (see L<Can
371	I switch the fonts at runtime?> later in this document).
372
373	=item Why does rxvt-unicode sometimes leave pixel droppings?
374
375	Most fonts were not designed for terminal use, which means that character
376	size varies a lot. A font that is otherwise fine for terminal use might
377	contain some characters that are simply too wide. Rxvt-unicode will avoid
378	these characters. For characters that are just "a bit" too wide a special
379	"careful" rendering mode is used that redraws adjacent characters.
380
381	All of this requires that fonts do not lie about character sizes,
382	however: Xft fonts often draw glyphs larger than their acclaimed bounding
383	box, and rxvt-unicode has no way of detecting this (the correct way is to
384	ask for the character bounding box, which unfortunately is wrong in these
385	cases).	826	locales).
386		827
387	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
388	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
389	the C<-lsp> option to give the font more height. If that doesn't work, you	830	interpretation of characters.
390	might be forced to use a different font.
391		831
392	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
393	box data is correct.	833	is there a standard on how locale specifiers will look like.
394		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
395	=item On Solaris 9, many line-drawing characters are too wide.	950	=head3 On Solaris 9, many line-drawing characters are too wide.
396		951
397	Seems to be a known bug, read	952	Seems to be a known bug, read
398	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
399	following ugly workaround to get non-double-wide-characters working:	954	following ugly workaround to get non-double-wide-characters working:
400		955
401	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	956	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
402		957
403	=item My Compose (Multi_key) key is no longer working.
404
405	The most common causes for this are that either your locale is not set
406	correctly, or you specified a B<preeditStyle> that is not supported by
407	your input method. For example, if you specified B<OverTheSpot> and
408	your input method (e.g. the default input method handling Compose keys)
409	does not support this (for instance because it is not visual), then
410	rxvt-unicode will continue without an input method.
411
412	In this case either do not specify a B<preeditStyle> or specify more than
413	one pre-edit style, such as B<OverTheSpot,Root,None>.
414
415	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
416
417	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
418	international keyboards) or simply use ISO 14755 support to your
419	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
420	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
421	character and so on.
422
423	=item How can I keep rxvt-unicode from using reverse video so much?
424
425	First of all, make sure you are running with the right terminal settings
426	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
427	make sure you have specified colours for italic and bold, as otherwise
428	rxvt-unicode might use reverse video to simulate the effect:
429
430	URxvt.colorBD: white
431	URxvt.colorIT: green
432
433	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
434
435	For some unexplainable reason, some rare programs assume a very weird
436	colour palette when confronted with a terminal with more than the standard
437	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
438	these programs not to assume non-ISO colours without very good reasons.
439
440	In the meantime, you can either edit your C<rxvt-unicode> terminfo
441	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
442	fix colours but keep you from using other rxvt-unicode features.
443
444	=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.
445		959
446	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
447	in your compile environment, or an implementation that implements it,	961	in your compile environment, or an implementation that implements it,
448	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
449	B<wchar_t> is represented as unicode.	963	B<wchar_t> is represented as unicode.
…		…
471		985
472	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
473	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
474	complete replacements for them :)	988	complete replacements for them :)
475		989
476	=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.
477		991
478	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
479	problems with C<wcwidth> and a compile problem.	993	problems with C<wcwidth> and a compile problem.
480		994
481	=item How can I use rxvt-unicode under cygwin?	995	=head3 How can I use rxvt-unicode under cygwin?
482		996
483	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
484	the X11 libraries that come with cygwin. libW11 emulation is no	998	the X11 libraries that come with cygwin. libW11 emulation is no
485	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
486	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
…		…
489		1003
490	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
491	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
492	to 8-bit encodings.	1006	to 8-bit encodings.
493		1007
494	=item How does rxvt-unicode determine the encoding to use?
495
496	=item Is there an option to switch encodings?
497
498	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
499	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
500	UTF-8 or any other encodings with respect to terminal I/O.
501
502	The reasons is that there exists a perfectly fine mechanism for selecting
503	the encoding, doing I/O and (most important) communicating this to all
504	applications so everybody agrees on character properties such as width
505	and code number. This mechanism is the I<locale>. Applications not using
506	that info will have problems (for example, C<xterm> gets the width of
507	characters wrong as it uses it's own, locale-independent table under all
508	locales).
509
510	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
511	programs doing the same (that is, most) will automatically agree in the
512	interpretation of characters.
513
514	Unfortunately, there is no system-independent way to select locales, nor
515	is there a standard on how locale specifiers will look like.
516
517	On most systems, the content of the C<LC_CTYPE> environment variable
518	contains an arbitrary string which corresponds to an already-installed
519	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
520	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
521	(i.e. C<de> or C<german>) are also common.
522
523	Rxvt-unicode ignores all other locale categories, and except for
524	the encoding, ignores country or language-specific settings,
525	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
526	rxvt-unicode.
527
528	If you want to use a specific encoding you have to make sure you start
529	rxvt-unicode with the correct C<LC_CTYPE> category.
530
531	=item Can I switch locales at runtime?
532
533	Yes, using an escape sequence. Try something like this, which sets
534	rxvt-unicode's idea of C<LC_CTYPE>.
535
536	printf '\e]701;%s\007' ja_JP.SJIS
537
538	See also the previous answer.
539
540	Sometimes this capability is rather handy when you want to work in
541	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
542	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
543	first switches to a locale supported by xjdic and back later:
544
545	printf '\e]701;%s\007' ja_JP.SJIS
546	xjdic -js
547	printf '\e]701;%s\007' de_DE.UTF-8
548
549	You can also use xterm's C<luit> program, which usually works fine, except
550	for some locales where character width differs between program- and
551	rxvt-unicode-locales.
552
553	=item Can I switch the fonts at runtime?
554
555	Yes, using an escape sequence. Try something like this, which has the same
556	effect as using the C<-fn> switch, and takes effect immediately:
557
558	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
559
560	This is useful if you e.g. work primarily with japanese (and prefer a
561	japanese font), but you have to switch to chinese temporarily, where
562	japanese fonts would only be in your way.
563
564	You can think of this as a kind of manual ISO-2022 switching.
565
566	=item Why do italic characters look as if clipped?
567
568	Many fonts have difficulties with italic characters and hinting. For
569	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
570	Mono> completely fails in it's italic face. A workaround might be to
571	enable freetype autohinting, i.e. like this:
572
573	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
574	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
575
576	=item My input method wants <some encoding> but I want UTF-8, what can I do?
577
578	You can specify separate locales for the input method and the rest of the
579	terminal, using the resource C<imlocale>:
580
581	URxvt*imlocale: ja_JP.EUC-JP
582
583	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
584	use your input method. Please note, however, that you will not be able to
585	input characters outside C<EUC-JP> in a normal way then, as your input
586	method limits you.
587
588	=item Rxvt-unicode crashes when the X Input Method changes or exits.
589
590	Unfortunately, this is unavoidable, as the XIM protocol is racy by
591	design. Applications can avoid some crashes at the expense of memory
592	leaks, and Input Methods can avoid some crashes by careful ordering at
593	exit time. B<kinput2> (and derived input methods) generally succeeds,
594	while B<SCIM> (or similar input methods) fails. In the end, however,
595	crashes cannot be completely avoided even if both sides cooperate.
596
597	So the only workaround is not to kill your Input Method Servers.
598
599	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
600
601	Rxvt-unicode tries to obey the rule of not charging you for something you
602	don't use. One thing you should try is to configure out all settings that
603	you don't need, for example, Xft support is a resource hog by design,
604	when used. Compiling it out ensures that no Xft font will be loaded
605	accidentally when rxvt-unicode tries to find a font for your characters.
606
607	Also, many people (me included) like large windows and even larger
608	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
609	6 bytes per screen cell. For a 160x?? window this amounts to almost a
610	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
611	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
612	rxvt-unicode then uses 8 bytes per screen cell.
613
614	=item Can I speed up Xft rendering somehow?
615
616	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
617	it is simply slow. If you still want Xft fonts you might try to disable
618	antialiasing (by appending C<:antialias=false>), which saves lots of
619	memory and also speeds up rendering considerably.
620
621	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
622
623	Rxvt-unicode will use whatever you specify as a font. If it needs to
624	fall back to it's default font search list it will prefer X11 core
625	fonts, because they are small and fast, and then use Xft fonts. It has
626	antialiasing disabled for most of them, because the author thinks they
627	look best that way.
628
629	If you want antialiasing, you have to specify the fonts manually.
630
631	=item Mouse cut/paste suddenly no longer works.
632
633	Make sure that mouse reporting is actually turned off since killing
634	some editors prematurely may leave the mouse in mouse report mode. I've
635	heard that tcsh may use mouse reporting unless it otherwise specified. A
636	quick check is to see if cut/paste works when the Alt or Shift keys are
637	depressed. See @@RXVT_NAME@@(7)
638
639	=item What's with this bold/blink stuff?
640
641	If no bold colour is set via C<colorBD:>, bold will invert text using the
642	standard foreground colour.
643
644	For the standard background colour, blinking will actually make the
645	text blink when compiled with C<--enable-blinking>. with standard
646	colours. Without C<--enable-blinking>, the blink attribute will be
647	ignored.
648
649	On ANSI colours, bold/blink attributes are used to set high-intensity
650	foreground/background colors.
651
652	color0-7 are the low-intensity colors.
653
654	color8-15 are the corresponding high-intensity colors.
655
656	=item I don't like the screen colors. How do I change them?
657
658	You can change the screen colors at run-time using F<~/.Xdefaults>
659	resources (or as long-options).
660
661	Here are values that are supposed to resemble a VGA screen,
662	including the murky brown that passes for low-intensity yellow:
663
664	URxvt.color0: #000000
665	URxvt.color1: #A80000
666	URxvt.color2: #00A800
667	URxvt.color3: #A8A800
668	URxvt.color4: #0000A8
669	URxvt.color5: #A800A8
670	URxvt.color6: #00A8A8
671	URxvt.color7: #A8A8A8
672
673	URxvt.color8: #000054
674	URxvt.color9: #FF0054
675	URxvt.color10: #00FF54
676	URxvt.color11: #FFFF54
677	URxvt.color12: #0000FF
678	URxvt.color13: #FF00FF
679	URxvt.color14: #00FFFF
680	URxvt.color15: #FFFFFF
681
682	And here is a more complete set of non-standard colors described (not by
683	me) as "pretty girly".
684
685	URxvt.cursorColor: #dc74d1
686	URxvt.pointerColor: #dc74d1
687	URxvt.background: #0e0e0e
688	URxvt.foreground: #4ad5e1
689	URxvt.color0: #000000
690	URxvt.color8: #8b8f93
691	URxvt.color1: #dc74d1
692	URxvt.color9: #dc74d1
693	URxvt.color2: #0eb8c7
694	URxvt.color10: #0eb8c7
695	URxvt.color3: #dfe37e
696	URxvt.color11: #dfe37e
697	URxvt.color5: #9e88f0
698	URxvt.color13: #9e88f0
699	URxvt.color6: #73f7ff
700	URxvt.color14: #73f7ff
701	URxvt.color7: #e1dddd
702	URxvt.color15: #e1dddd
703
704	=item How can I start @@RXVT_NAME@@d in a race-free way?
705
706	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
707	display, create the listening socket and then fork.
708
709	=item What's with the strange Backspace/Delete key behaviour?
710
711	Assuming that the physical Backspace key corresponds to the
712	BackSpace keysym (not likely for Linux ... see the following
713	question) there are two standard values that can be used for
714	Backspace: C<^H> and C<^?>.
715
716	Historically, either value is correct, but rxvt-unicode adopts the debian
717	policy of using C<^?> when unsure, because it's the one only only correct
718	choice :).
719
720	Rxvt-unicode tries to inherit the current stty settings and uses the value
721	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
722	started from a terminal (say, from a menu or by remote shell), then the
723	system value of `erase', which corresponds to CERASE in <termios.h>, will
724	be used (which may not be the same as your stty setting).
725
726	For starting a new rxvt-unicode:
727
728	# use Backspace = ^H
729	$ stty erase ^H
730	$ @@RXVT_NAME@@
731
732	# use Backspace = ^?
733	$ stty erase ^?
734	$ @@RXVT_NAME@@
735
736	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
737
738	For an existing rxvt-unicode:
739
740	# use Backspace = ^H
741	$ stty erase ^H
742	$ echo -n "^[[36h"
743
744	# use Backspace = ^?
745	$ stty erase ^?
746	$ echo -n "^[[36l"
747
748	This helps satisfy some of the Backspace discrepancies that occur, but
749	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
750	properly reflects that.
751
752	The Delete key is a another casualty of the ill-defined Backspace problem.
753	To avoid confusion between the Backspace and Delete keys, the Delete
754	key has been assigned an escape sequence to match the vt100 for Execute
755	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
756
757	Some other Backspace problems:
758
759	some editors use termcap/terminfo,
760	some editors (vim I'm told) expect Backspace = ^H,
761	GNU Emacs (and Emacs-like editors) use ^H for help.
762
763	Perhaps someday this will all be resolved in a consistent manner.
764
765	=item I don't like the key-bindings. How do I change them?
766
767	There are some compile-time selections available via configure. Unless
768	you have run "configure" with the C<--disable-resources> option you can
769	use the `keysym' resource to alter the keystrings associated with keysyms.
770
771	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
772
773	URxvt.keysym.Home: \033[1~
774	URxvt.keysym.End: \033[4~
775	URxvt.keysym.C-apostrophe: \033<C-'>
776	URxvt.keysym.C-slash: \033<C-/>
777	URxvt.keysym.C-semicolon: \033<C-;>
778	URxvt.keysym.C-grave: \033<C-`>
779	URxvt.keysym.C-comma: \033<C-,>
780	URxvt.keysym.C-period: \033<C-.>
781	URxvt.keysym.C-0x60: \033<C-`>
782	URxvt.keysym.C-Tab: \033<C-Tab>
783	URxvt.keysym.C-Return: \033<C-Return>
784	URxvt.keysym.S-Return: \033<S-Return>
785	URxvt.keysym.S-space: \033<S-Space>
786	URxvt.keysym.M-Up: \033<M-Up>
787	URxvt.keysym.M-Down: \033<M-Down>
788	URxvt.keysym.M-Left: \033<M-Left>
789	URxvt.keysym.M-Right: \033<M-Right>
790	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
791	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
792	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
793
794	See some more examples in the documentation for the B<keysym> resource.
795
796	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
797	How do I make use of them? For example, the Sun Keyboard type 4
798	has the following mappings that rxvt-unicode doesn't recognize.
799
800	KP_Insert == Insert
801	F22 == Print
802	F27 == Home
803	F29 == Prior
804	F33 == End
805	F35 == Next
806
807	Rather than have rxvt-unicode try to accommodate all the various possible
808	keyboard mappings, it is better to use `xmodmap' to remap the keys as
809	required for your particular machine.
810
811	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
812	I need this to decide about setting colors etc.
813
814	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
815	check and see if that is set. Note that several programs, JED, slrn,
816	Midnight Commander automatically check this variable to decide whether or
817	not to use color.
818
819	=item How do I set the correct, full IP address for the DISPLAY variable?
820
821	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
822	insecure mode then it is possible to use the following shell script
823	snippets to correctly set the display. If your version of rxvt-unicode
824	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
825	the COLORTERM variable can be used to distinguish rxvt-unicode from a
826	regular xterm.
827
828	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
829	snippets:
830
831	# Bourne/Korn/POSIX family of shells:
832	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
833	if [ ${TERM:-foo} = xterm ]; then
834	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
835	echo -n '^[Z'
836	read term_id
837	stty icanon echo
838	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
839	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
840	read DISPLAY # set it in our local shell
841	fi
842	fi
843
844	=item How do I compile the manual pages for myself?
845
846	You need to have a recent version of perl installed as F</usr/bin/perl>,
847	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
848	the doc subdirectory and enter C<make alldoc>.
849
850	=item My question isn't answered here, can I ask a human?
851
852	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
853	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
854	interested in learning about new and exciting problems (but not FAQs :).
855
856	=back
857
858	=head1 RXVT TECHNICAL REFERENCE	1008	=head1 RXVT-UNICODE TECHNICAL REFERENCE
859		1009
860	=head1 DESCRIPTION	1010	=head1 DESCRIPTION
861		1011
862	The rest of this document describes various technical aspects of	1012	The rest of this document describes various technical aspects of
863	B<rxvt-unicode>. First the description of supported command sequences,	1013	B<rxvt-unicode>. First the description of supported command sequences,
864	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
865	features selectable at C<configure> time.	1015	selectable at C<configure> time.
866		1016
867	=head1 Definitions	1017	=head1 Definitions
868		1018
869	=over 4	1019	=over 4
870		1020
…		…
1438	B<< C<h> >> Send Mouse X & Y on button press.	1588	B<< C<h> >> Send Mouse X & Y on button press.
1439	B<< C<l> >> No mouse reporting.	1589	B<< C<l> >> No mouse reporting.
1440		1590
1441	=end table	1591	=end table
1442		1592
1443	=item B<< C<Ps = 10> >> (B<rxvt>)
1444
1445	=begin table
1446
1447	B<< C<h> >> menuBar visible
1448	B<< C<l> >> menuBar invisible
1449
1450	=end table
1451
1452	=item B<< C<Ps = 25> >>	1593	=item B<< C<Ps = 25> >>
1453		1594
1454	=begin table	1595	=begin table
1455		1596
1456	B<< C<h> >> Visible cursor {cnorm/cvvis}	1597	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
1638	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> >>
1639	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> >>
1640	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> >>
1641	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]
1642	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]
1643	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).
1644	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> >>.
1645	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>
1646	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> >>.
1647	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> >>
1648	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> >>
1649	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).
1650	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>.
1651	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> >>
1652	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).
1653	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> >>
1654	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> >>
1655	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>.
…		…
1662		1803
1663	=end table	1804	=end table
1664		1805
1665	=back	1806	=back
1666		1807
1667	X<menuBar>
1668
1669	=head1 menuBar
1670
1671	B<< The exact syntax used is I<almost> solidified. >>
1672	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1673	menuBar.
1674
1675	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1676	omitted: use B<./> to specify a menu relative to the current menu.
1677
1678	=head2 Overview of menuBar operation
1679
1680	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1681	of C<Pt> can be used for a variety of tasks:
1682
1683	At the top level is the current menuBar which is a member of a circular
1684	linked-list of other such menuBars.
1685
1686	The menuBar acts as a parent for the various drop-down menus, which in
1687	turn, may have labels, separator lines, menuItems and subMenus.
1688
1689	The menuItems are the useful bits: you can use them to mimic keyboard
1690	input or even to send text or escape sequences back to rxvt.
1691
1692	The menuBar syntax is intended to provide a simple yet robust method of
1693	constructing and manipulating menus and navigating through the
1694	menuBars.
1695
1696	The first step is to use the tag B<< [menu:I<name>] >> which creates
1697	the menuBar called I<name> and allows access. You may now or menus,
1698	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1699	menuBar access as B<readonly> to prevent accidental corruption of the
1700	menus. To re-access the current menuBar for alterations, use the tag
1701	B<[menu]>, make the alterations and then use B<[done]>
1702
1703	X<menuBarCommands>
1704
1705	=head2 Commands
1706
1707	=over 4
1708
1709	=item B<< [menu:+I<name>] >>
1710
1711	access the named menuBar for creation or alteration. If a new menuBar
1712	is created, it is called I<name> (max of 15 chars) and the current
1713	menuBar is pushed onto the stack
1714
1715	=item B<[menu]>
1716
1717	access the current menuBar for alteration
1718
1719	=item B<< [title:+I<string>] >>
1720
1721	set the current menuBar's title to I<string>, which may contain the
1722	following format specifiers:
1723
1724	B<%n> rxvt name (as per the B<-name> command-line option)
1725	B<%v> rxvt version
1726	B<%%> literal B<%> character
1727
1728	=item B<[done]>
1729
1730	set menuBar access as B<readonly>.
1731	End-of-file tag for B<< [read:+I<file>] >> operations.
1732
1733	=item B<< [read:+I<file>] >>
1734
1735	read menu commands directly from I<file> (extension ".menu" will be
1736	appended if required.) Start reading at a line with B<[menu]> or B<<
1737	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1738
1739	Blank and comment lines (starting with B<#>) are ignored. Actually,
1740	since any invalid menu commands are also ignored, almost anything could
1741	be construed as a comment line, but this may be tightened up in the
1742	future ... so don't count on it!.
1743
1744	=item B<< [read:+I<file>;+I<name>] >>
1745
1746	The same as B<< [read:+I<file>] >>, but start reading at a line with
1747	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1748	B<[done]> is encountered.
1749
1750	=item B<[dump]>
1751
1752	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1753	later rereading.
1754
1755	=item B<[rm:name]>
1756
1757	remove the named menuBar
1758
1759	=item B<[rm] [rm:]>
1760
1761	remove the current menuBar
1762
1763	=item B<[rm*] [rm:*]>
1764
1765	remove all menuBars
1766
1767	=item B<[swap]>
1768
1769	swap the top two menuBars
1770
1771	=item B<[prev]>
1772
1773	access the previous menuBar
1774
1775	=item B<[next]>
1776
1777	access the next menuBar
1778
1779	=item B<[show]>
1780
1781	Enable display of the menuBar
1782
1783	=item B<[hide]>
1784
1785	Disable display of the menuBar
1786
1787	=item B<< [pixmap:+I<name>] >>
1788
1789	=item B<< [pixmap:+I<name>;I<scaling>] >>
1790
1791	(set the background pixmap globally
1792
1793	B<< A Future implementation I<may> make this local to the menubar >>)
1794
1795	=item B<< [:+I<command>:] >>
1796
1797	ignore the menu readonly status and issue a I<command> to or a menu or
1798	menuitem or change the ; a useful shortcut for setting the quick arrows
1799	from a menuBar.
1800
1801	=back
1802
1803	X<menuBarAdd>
1804
1805	=head2 Adding and accessing menus
1806
1807	The following commands may also be B<+> prefixed.
1808
1809	=over 4
1810
1811	=item B</+>
1812
1813	access menuBar top level
1814
1815	=item B<./+>
1816
1817	access current menu level
1818
1819	=item B<../+>
1820
1821	access parent menu (1 level up)
1822
1823	=item B<../../>
1824
1825	access parent menu (multiple levels up)
1826
1827	=item B<< I</path/>menu >>
1828
1829	add/access menu
1830
1831	=item B<< I</path/>menu/* >>
1832
1833	add/access menu and clear it if it exists
1834
1835	=item B<< I</path/>{-} >>
1836
1837	add separator
1838
1839	=item B<< I</path/>{item} >>
1840
1841	add B<item> as a label
1842
1843	=item B<< I</path/>{item} action >>
1844
1845	add/alter I<menuitem> with an associated I<action>
1846
1847	=item B<< I</path/>{item}{right-text} >>
1848
1849	add/alter I<menuitem> with B<right-text> as the right-justified text
1850	and as the associated I<action>
1851
1852	=item B<< I</path/>{item}{rtext} action >>
1853
1854	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1855	the right-justified text.
1856
1857	=back
1858
1859	=over 4
1860
1861	=item Special characters in I<action> must be backslash-escaped:
1862
1863	B<\a \b \E \e \n \r \t \octal>
1864
1865	=item or in control-character notation:
1866
1867	B<^@, ^A .. ^Z .. ^_, ^?>
1868
1869	=back
1870
1871	To send a string starting with a B<NUL> (B<^@>) character to the
1872	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1873	the first of which will be stripped off and the balance directed to the
1874	program. Otherwise if I<action> begins with B<NUL> followed by
1875	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1876	balance is sent back to rxvt.
1877
1878	As a convenience for the many Emacs-type editors, I<action> may start
1879	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1880	appended if missed from B<M-x> commands.
1881
1882	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1883	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1884
1885	=over 4
1886
1887	=item For example,
1888
1889	B<M-xapropos> is equivalent to B<\Exapropos\r>
1890
1891	=item and
1892
1893	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1894
1895	=back
1896
1897	The option B<< {I<right-rtext>} >> will be right-justified. In the
1898	absence of a specified action, this text will be used as the I<action>
1899	as well.
1900
1901	=over 4
1902
1903	=item For example,
1904
1905	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1906
1907	=back
1908
1909	The left label I<is> necessary, since it's used for matching, but
1910	implicitly hiding the left label (by using same name for both left and
1911	right labels), or explicitly hiding the left label (by preceeding it
1912	with a dot), makes it possible to have right-justified text only.
1913
1914	=over 4
1915
1916	=item For example,
1917
1918	B</File/{Open}{Open} Open-File-Action>
1919
1920	=item or hiding it
1921
1922	B</File/{.anylabel}{Open} Open-File-Action>
1923
1924	=back
1925
1926	X<menuBarRemove>
1927
1928	=head2 Removing menus
1929
1930	=over 4
1931
1932	=item B<< -/*+ >>
1933
1934	remove all menus from the menuBar, the same as B<[clear]>
1935
1936	=item B<< -+I</path>menu+ >>
1937
1938	remove menu
1939
1940	=item B<< -+I</path>{item}+ >>
1941
1942	remove item
1943
1944	=item B<< -+I</path>{-} >>
1945
1946	remove separator)
1947
1948	=item B<-/path/menu/*>
1949
1950	remove all items, separators and submenus from menu
1951
1952	=back
1953
1954	X<menuBarArrows>
1955
1956	=head2 Quick Arrows
1957
1958	The menus also provide a hook for I<quick arrows> to provide easier
1959	user access. If nothing has been explicitly set, the default is to
1960	emulate the curror keys. The syntax permits each arrow to be altered
1961	individually or all four at once without re-entering their common
1962	beginning/end text. For example, to explicitly associate cursor actions
1963	with the arrows, any of the following forms could be used:
1964
1965	=over 4
1966
1967	=item B<< <r>+I<Right> >>
1968
1969	=item B<< <l>+I<Left> >>
1970
1971	=item B<< <u>+I<Up> >>
1972
1973	=item B<< <d>+I<Down> >>
1974
1975	Define actions for the respective arrow buttons
1976
1977	=item B<< <b>+I<Begin> >>
1978
1979	=item B<< <e>+I<End> >>
1980
1981	Define common beginning/end parts for I<quick arrows> which used in
1982	conjunction with the above <r> <l> <u> <d> constructs
1983
1984	=back
1985
1986	=over 4
1987
1988	=item For example, define arrows individually,
1989
1990	<u>\E[A
1991
1992	<d>\E[B
1993
1994	<r>\E[C
1995
1996	<l>\E[D
1997
1998	=item or all at once
1999
2000	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
2001
2002	=item or more compactly (factoring out common parts)
2003
2004	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
2005
2006	=back
2007
2008	X<menuBarSummary>
2009
2010	=head2 Command Summary
2011
2012	A short summary of the most I<common> commands:
2013
2014	=over 4
2015
2016	=item [menu:name]
2017
2018	use an existing named menuBar or start a new one
2019
2020	=item [menu]
2021
2022	use the current menuBar
2023
2024	=item [title:string]
2025
2026	set menuBar title
2027
2028	=item [done]
2029
2030	set menu access to readonly and, if reading from a file, signal EOF
2031
2032	=item [done:name]
2033
2034	if reading from a file using [read:file;name] signal EOF
2035
2036	=item [rm:name]
2037
2038	remove named menuBar(s)
2039
2040	=item [rm] [rm:]
2041
2042	remove current menuBar
2043
2044	=item [rm*] [rm:*]
2045
2046	remove all menuBar(s)
2047
2048	=item [swap]
2049
2050	swap top two menuBars
2051
2052	=item [prev]
2053
2054	access the previous menuBar
2055
2056	=item [next]
2057
2058	access the next menuBar
2059
2060	=item [show]
2061
2062	map menuBar
2063
2064	=item [hide]
2065
2066	unmap menuBar
2067
2068	=item [pixmap;file]
2069
2070	=item [pixmap;file;scaling]
2071
2072	set a background pixmap
2073
2074	=item [read:file]
2075
2076	=item [read:file;name]
2077
2078	read in a menu from a file
2079
2080	=item [dump]
2081
2082	dump out all menuBars to /tmp/rxvt-PID
2083
2084	=item /
2085
2086	access menuBar top level
2087
2088	=item ./
2089
2090	=item ../
2091
2092	=item ../../
2093
2094	access current or parent menu level
2095
2096	=item /path/menu
2097
2098	add/access menu
2099
2100	=item /path/{-}
2101
2102	add separator
2103
2104	=item /path/{item}{rtext} action
2105
2106	add/alter menu item
2107
2108	=item -/*
2109
2110	remove all menus from the menuBar
2111
2112	=item -/path/menu
2113
2114	remove menu items, separators and submenus from menu
2115
2116	=item -/path/menu
2117
2118	remove menu
2119
2120	=item -/path/{item}
2121
2122	remove item
2123
2124	=item -/path/{-}
2125
2126	remove separator
2127
2128	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
2129
2130	menu quick arrows
2131
2132	=back
2133	X<XPM>	1808	X<XPM>
2134		1809
2135	=head1 XPM	1810	=head1 XPM
2136		1811
2137	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
…		…
2236	=begin table	1911	=begin table
2237		1912
2238	4 Shift	1913	4 Shift
2239	8 Meta	1914	8 Meta
2240	16 Control	1915	16 Control
2241	32 Double Click I<(Rxvt extension)>	1916	32 Double Click I<(rxvt extension)>
2242		1917
2243	=end table	1918	=end table
2244		1919
2245	Col = B<< C<< <x> - SPACE >> >>	1920	Col = B<< C<< <x> - SPACE >> >>
2246		1921
…		…
2384	alternative input methods (e.g. kinput2) and will also correctly	2059	alternative input methods (e.g. kinput2) and will also correctly
2385	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.
2386		2061
2387	=item --enable-unicode3 (default: off)	2062	=item --enable-unicode3 (default: off)
2388		2063
		2064	Recommended to stay off unless you really need non-BMP characters.
		2065
2389	Enable direct support for displaying unicode codepoints above	2066	Enable direct support for displaying unicode codepoints above
2390	65535 (the basic multilingual page). This increases storage	2067	65535 (the basic multilingual page). This increases storage
2391	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
2392	support these extra characters, but Xft does.	2069	support these extra characters, but Xft does.
2393		2070
…		…
2403	composite characters. This is required for proper viewing of text	2080	composite characters. This is required for proper viewing of text
2404	where accents are encoded as seperate unicode characters. This is	2081	where accents are encoded as seperate unicode characters. This is
2405	done by using precomposited characters when available or creating	2082	done by using precomposited characters when available or creating
2406	new pseudo-characters when no precomposed form exists.	2083	new pseudo-characters when no precomposed form exists.
2407		2084
2408	Without --enable-unicode3, the number of additional precomposed characters	2085	Without --enable-unicode3, the number of additional precomposed
2409	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
2410	private use area, extending the number of combinations to 8448). With
2411	--enable-unicode3, no practical limit exists.	2087	(ab-)used). With --enable-unicode3, no practical limit exists.
2412		2088
2413	This option will also enable storage (but not display) of characters	2089	This option will also enable storage (but not display) of characters
2414	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2090	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2415		2091
2416	The combining table also contains entries for arabic presentation forms,	2092	The combining table also contains entries for arabic presentation forms,
2417	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
2418	tell me how these are to be used...).	2094	tell me how these are to be used...).
2419		2095
2420	=item --enable-fallback(=CLASS) (default: Rxvt)	2096	=item --enable-fallback(=CLASS) (default: Rxvt)
2421		2097
2422	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.
2423		2100
2424	=item --with-res-name=NAME (default: urxvt)	2101	=item --with-res-name=NAME (default: urxvt)
2425		2102
2426	Use the given name as default application name when	2103	Use the given name as default application name when
2427	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2104	reading resources. Specify --with-res-name=rxvt to replace rxvt.
…		…
2464		2141
2465	=item --enable-tinting (default: on)	2142	=item --enable-tinting (default: on)
2466		2143
2467	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).	2144	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2468		2145
2469	=item --enable-menubar (default: off) [DEPRECATED]
2470
2471	Add support for our menu bar system (this interacts badly with dynamic
2472	locale switching currently). This option is DEPRECATED and will be removed
2473	in the future.
2474
2475	=item --enable-rxvt-scroll (default: on)	2146	=item --enable-rxvt-scroll (default: on)
2476		2147
2477	Add support for the original rxvt scrollbar.	2148	Add support for the original rxvt scrollbar.
2478		2149
2479	=item --enable-next-scroll (default: on)	2150	=item --enable-next-scroll (default: on)
…		…
2488		2159
2489	Add support for a very unobtrusive, plain-looking scrollbar that	2160	Add support for a very unobtrusive, plain-looking scrollbar that
2490	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
2491	many years.	2162	many years.
2492		2163
2493	=item --enable-half-shadow (default: off)
2494
2495	Make shadows on the scrollbar only half the normal width & height.
2496	only applicable to rxvt scrollbars.
2497
2498	=item --enable-ttygid (default: off)	2164	=item --enable-ttygid (default: off)
2499		2165
2500	Change tty device setting to group "tty" - only use this if	2166	Change tty device setting to group "tty" - only use this if
2501	your system uses this type of security.	2167	your system uses this type of security.
2502		2168
…		…
2510	do it.	2176	do it.
2511		2177
2512	=item --disable-resources	2178	=item --disable-resources
2513		2179
2514	Removes any support for resource checking.	2180	Removes any support for resource checking.
2515
2516	=item --enable-xgetdefault
2517
2518	Make resources checking via XGetDefault() instead of our small
2519	version which only checks ~/.Xdefaults, or if that doesn't exist then
2520	~/.Xresources.
2521
2522	Please note that nowadays, things like XIM will automatically pull in and
2523	use the full X resource manager, so the overhead of using it might be very
2524	small, if nonexistant.
2525
2526	=item --enable-strings (default: off)
2527
2528	Add support for our possibly faster memset() function and other
2529	various routines, overriding your system's versions which may
2530	have been hand-crafted in assembly or may require extra libraries
2531	to link in. (this breaks ANSI-C rules and has problems on many
2532	GNU/Linux systems).
2533		2181
2534	=item --disable-swapscreen	2182	=item --disable-swapscreen
2535		2183
2536	Remove support for secondary/swap screen.	2184	Remove support for secondary/swap screen.
2537		2185
…		…
2546		2194
2547	MWM-hints	2195	MWM-hints
2548	EWMH-hints (pid, utf8 names) and protocols (ping)	2196	EWMH-hints (pid, utf8 names) and protocols (ping)
2549	seperate underline colour (-underlineColor)	2197	seperate underline colour (-underlineColor)
2550	settable border widths and borderless switch (-w, -b, -bl)	2198	settable border widths and borderless switch (-w, -b, -bl)
		2199	visual depth selection (-depth)
2551	settable extra linespacing /-lsp)	2200	settable extra linespacing /-lsp)
2552	iso-14755-2 and -3, and visual feedback	2201	iso-14755-2 and -3, and visual feedback
2553	backindex and forwardindex escape sequence
2554	window op and some xterm/OSC escape sequences
2555	tripleclickwords (-tcw)	2202	tripleclickwords (-tcw)
2556	settable insecure mode (-insecure)	2203	settable insecure mode (-insecure)
2557	keysym remapping support	2204	keysym remapping support
2558	cursor blinking and underline cursor (-cb, -uc)	2205	cursor blinking and underline cursor (-cb, -uc)
2559	XEmbed support (-embed)	2206	XEmbed support (-embed)
2560	user-pty (-pty-fd)	2207	user-pty (-pty-fd)
2561	hold on exit (-hold)	2208	hold on exit (-hold)
2562	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
2563	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
2564		2224
2565	=item --enable-iso14755 (default: on)	2225	=item --enable-iso14755 (default: on)
2566		2226
2567	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2227	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2568	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
…		…
2611		2271
2612	=item --enable-pointer-blank (default: on)	2272	=item --enable-pointer-blank (default: on)
2613		2273
2614	Add support to have the pointer disappear when typing or inactive.	2274	Add support to have the pointer disappear when typing or inactive.
2615		2275
2616	=item --enable-perl (default: off)	2276	=item --enable-perl (default: on)
2617		2277
2618	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)>
2619	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
2620	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
2621	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