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.67 by root, Mon Jan 2 19:36:07 2006 UTC vs.
Revision 1.102 by root, Tue Jan 31 20:50:48 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 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	@@RXVT_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 @@RXVT_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 @@RXVT_NAME@@d in a race-free way?
		74
		75	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_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	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
		81	check and see if that is set. Note that several programs, JED, slrn,
		82	Midnight Commander automatically check this variable to decide whether or
		83	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
…		…
62	memory.	149	memory.
63		150
64	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this	151	Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
65	still fares rather well. And compared to some monsters like gnome-terminal	152	still fares rather well. And compared to some monsters like gnome-terminal
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 aminute 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	@@RXVT_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
		210	That works. If you think it doesn't, you lack transparency and tinting
		211	support, or you are unable to read.
		212
		213	2. Use a simple pixmap and emulate pseudo-transparency. This enables you
		214	to use effects other than tinting and shading: Just shade/tint/whatever
		215	your picture with gimp or any other tool:
		216
		217	convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
		218	@@RXVT_NAME@@ -pixmap background.xpm -pe automove-background
		219
		220	That works. If you think it doesn't, you lack XPM and Perl support, or you
		221	are unable to read.
		222
		223	3. Use an ARGB visual:
		224
		225	@@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
		226
		227	This requires XFT support, and the support of your X-server. If that
		228	doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
		229	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
		230	bugfixes and workarounds for Xft and Xlib to make it work, but that
		231	doesn't mean that your WM has the required kludges in place.
		232
		233	4. Use xcompmgr and let it do the job:
		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	@@RXVT_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 @@RXVT_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	$ @@RXVT_NAME@@
		564
		565	# use Backspace = ^?
		566	$ stty erase ^?
		567	$ @@RXVT_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<@@RXVT_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
137	=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?
138		667
139	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
140	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).
141		670
142	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
…		…
160	URxvt.termName: rxvt	689	URxvt.termName: rxvt
161		690
162	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
163	the rxvt terminfo file with the rxvt-unicode one.	692	the rxvt terminfo file with the rxvt-unicode one.
164		693
165	=item C<tic> outputs some error when compiling the terminfo entry.	694	=head3 C<tic> outputs some error when compiling the terminfo entry.
166		695
167	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
168	C<enacs=\E[0@> and try again.	697	C<enacs=\E[0@> and try again.
169		698
170	=item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.	699	=head3 C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
171		700
		701	See next entry.
		702
172	=item I need a termcap file entry.	703	=head3 I need a termcap file entry.
173		704
174	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
175	systems still compile some programs using the long-obsoleted termcap	706	systems still compile some programs using the long-obsoleted termcap
176	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
177	for C<rxvt-unicode>.	708	for C<rxvt-unicode>.
…		…
203	: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:\
204	: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:\
205	: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:\
206	:vs=\E[?25h:	737	:vs=\E[?25h:
207		738
208	=item Why does C<ls> no longer have coloured output?	739	=head3 Why does C<ls> no longer have coloured output?
209		740
210	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
211	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
212	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
213	with most other terminals supporting colour). Either add:	744	with most other terminals supporting colour). Either add:
…		…
218		749
219	alias ls='ls --color=auto'	750	alias ls='ls --color=auto'
220		751
221	to your C<.profile> or C<.bashrc>.	752	to your C<.profile> or C<.bashrc>.
222		753
223	=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?
224		755
		756	See next entry.
		757
225	=item Why doesn't vim/emacs etc. make use of italic?	758	=head3 Why doesn't vim/emacs etc. make use of italic?
226		759
		760	See next entry.
		761
227	=item Why are the secondary screen-related options not working properly?	762	=head3 Why are the secondary screen-related options not working properly?
228		763
229	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
230	distributions (most notably Debian GNU/Linux) break rxvt-unicode	765	distributions (most notably Debian GNU/Linux) break rxvt-unicode
231	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
232	features. Unfortunately, some of these (most notably, again, Debian	767	features. Unfortunately, some of these (most notably, again, Debian
233	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
234	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
235	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
236	how to do this).	771	how to do this).
237		772
238	=item My numerical keypad acts weird and generates differing output?
239		773
240	Some Debian GNUL/Linux users seem to have this problem, although no	774	=head2 Encoding / Locale / Input Method Issues
241	specific details were reported so far. It is possible that this is caused
242	by the wrong C<TERM> setting, although the details of wether and how
243	this can happen are unknown, as C<TERM=rxvt> should offer a compatible
244	keymap. See the answer to the previous question, and please report if that
245	helped.
246		775
247	=item Rxvt-unicode does not seem to understand the selected encoding?	776	=head3 Rxvt-unicode does not seem to understand the selected encoding?
248		777
		778	See next entry.
		779
249	=item Unicode does not seem to work?	780	=head3 Unicode does not seem to work?
250		781
251	If you encounter strange problems like typing an accented character but	782	If you encounter strange problems like typing an accented character but
252	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
253	subtly garbled, then you should check your locale settings.	784	subtly garbled, then you should check your locale settings.
254		785
…		…
274		805
275	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
276	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
277	support locales :(	808	support locales :(
278		809
279	=item Why do some characters look so much different than others?	810	=head3 How does rxvt-unicode determine the encoding to use?
280		811
281	=item How does rxvt-unicode choose fonts?	812	See next entry.
282		813
283	Most fonts do not contain the full range of Unicode, which is	814	=head3 Is there an option to switch encodings?
284	fine. Chances are that the font you (or the admin/package maintainer of
285	your system/os) have specified does not cover all the characters you want
286	to display.
287		815
288	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
289	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
290	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.
291	resemble the correct glyph at all, and rxvt-unicode lacks the artificial
292	intelligence to detect that a specific glyph is wrong: it has to believe
293	the font that the characters it claims to contain indeed look correct.
294		819
295	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
296	e.g.:	821	the encoding, doing I/O and (most important) communicating this to all
297		822	applications so everybody agrees on character properties such as width
298	@@RXVT_NAME@@ -fn basefont,font2,font3...	823	and code number. This mechanism is the I<locale>. Applications not using
299		824	that info will have problems (for example, C<xterm> gets the width of
300	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
301	font. If the base font does not contain the character, it will go to the
302	next font, and so on. Specifying your own fonts will also speed up this
303	search and use less resources within rxvt-unicode and the X-server.
304
305	The only limitation is that none of the fonts may be larger than the base
306	font, as the base font defines the terminal character cell size, which
307	must be the same due to the way terminals work.
308
309	=item Why do some chinese characters look so different than others?
310
311	This is because there is a difference between script and language --
312	rxvt-unicode does not know which language the text that is output is,
313	as it only knows the unicode character codes. If rxvt-unicode first
314	sees a japanese/chinese character, it might choose a japanese font for
315	display. Subsequent japanese characters will use that font. Now, many
316	chinese characters aren't represented in japanese fonts, so when the first
317	non-japanese character comes up, rxvt-unicode will look for a chinese font
318	-- unfortunately at this point, it will still use the japanese font for
319	chinese characters that are also in the japanese font.
320
321	The workaround is easy: just tag a chinese font at the end of your font
322	list (see the previous question). The key is to view the font list as
323	a preference list: If you expect more japanese, list a japanese font
324	first. If you expect more chinese, put a chinese font first.
325
326	In the future it might be possible to switch language preferences at
327	runtime (the internal data structure has no problem with using different
328	fonts for the same character at the same time, but no interface for this
329	has been designed yet).
330
331	Until then, you might get away with switching fonts at runtime (see L<Can
332	I switch the fonts at runtime?> later in this document).
333
334	=item Why does rxvt-unicode sometimes leave pixel droppings?
335
336	Most fonts were not designed for terminal use, which means that character
337	size varies a lot. A font that is otherwise fine for terminal use might
338	contain some characters that are simply too wide. Rxvt-unicode will avoid
339	these characters. For characters that are just "a bit" too wide a special
340	"careful" rendering mode is used that redraws adjacent characters.
341
342	All of this requires that fonts do not lie about character sizes,
343	however: Xft fonts often draw glyphs larger than their acclaimed bounding
344	box, and rxvt-unicode has no way of detecting this (the correct way is to
345	ask for the character bounding box, which unfortunately is wrong in these
346	cases).	826	locales).
347		827
348	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
349	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
350	the C<-lsp> option to give the font more height. If that doesn't work, you	830	interpretation of characters.
351	might be forced to use a different font.
352		831
353	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
354	box data is correct.	833	is there a standard on how locale specifiers will look like.
355		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
356	=item On Solaris 9, many line-drawing characters are too wide.	950	=head3 On Solaris 9, many line-drawing characters are too wide.
357		951
358	Seems to be a known bug, read	952	Seems to be a known bug, read
359	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
360	following ugly workaround to get non-double-wide-characters working:	954	following ugly workaround to get non-double-wide-characters working:
361		955
362	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)	956	#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
363		957
364	=item My Compose (Multi_key) key is no longer working.
365
366	The most common causes for this are that either your locale is not set
367	correctly, or you specified a B<preeditStyle> that is not supported by
368	your input method. For example, if you specified B<OverTheSpot> and
369	your input method (e.g. the default input method handling Compose keys)
370	does not support this (for instance because it is not visual), then
371	rxvt-unicode will continue without an input method.
372
373	In this case either do not specify a B<preeditStyle> or specify more than
374	one pre-edit style, such as B<OverTheSpot,Root,None>.
375
376	=item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755
377
378	Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on
379	international keyboards) or simply use ISO 14755 support to your
380	advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
381	codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape
382	character and so on.
383
384	=item How can I keep rxvt-unicode from using reverse video so much?
385
386	First of all, make sure you are running with the right terminal settings
387	(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then
388	make sure you have specified colours for italic and bold, as otherwise
389	rxvt-unicode might use reverse video to simulate the effect:
390
391	URxvt.colorBD: white
392	URxvt.colorIT: green
393
394	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
395
396	For some unexplainable reason, some rare programs assume a very weird
397	colour palette when confronted with a terminal with more than the standard
398	8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
399	these programs not to assume non-ISO colours without very good reasons.
400
401	In the meantime, you can either edit your C<rxvt-unicode> terminfo
402	definition to only claim 8 colour support or use C<TERM=rxvt>, which will
403	fix colours but keep you from using other rxvt-unicode features.
404
405	=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.
406		959
407	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
408	in your compile environment, or an implementation that implements it,	961	in your compile environment, or an implementation that implements it,
409	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
410	B<wchar_t> is represented as unicode.	963	B<wchar_t> is represented as unicode.
…		…
432		985
433	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
434	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
435	complete replacements for them :)	988	complete replacements for them :)
436		989
437	=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.
438		991
439	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
440	problems with C<wcwidth> and a compile problem.	993	problems with C<wcwidth> and a compile problem.
441		994
442	=item How can I use rxvt-unicode under cygwin?	995	=head3 How can I use rxvt-unicode under cygwin?
443		996
444	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
445	the X11 libraries that come with cygwin. libW11 emulation is no	998	the X11 libraries that come with cygwin. libW11 emulation is no
446	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
447	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
…		…
450		1003
451	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
452	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
453	to 8-bit encodings.	1006	to 8-bit encodings.
454		1007
455	=item How does rxvt-unicode determine the encoding to use?
456
457	=item Is there an option to switch encodings?
458
459	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
460	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
461	UTF-8 or any other encodings with respect to terminal I/O.
462
463	The reasons is that there exists a perfectly fine mechanism for selecting
464	the encoding, doing I/O and (most important) communicating this to all
465	applications so everybody agrees on character properties such as width
466	and code number. This mechanism is the I<locale>. Applications not using
467	that info will have problems (for example, C<xterm> gets the width of
468	characters wrong as it uses it's own, locale-independent table under all
469	locales).
470
471	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
472	programs doing the same (that is, most) will automatically agree in the
473	interpretation of characters.
474
475	Unfortunately, there is no system-independent way to select locales, nor
476	is there a standard on how locale specifiers will look like.
477
478	On most systems, the content of the C<LC_CTYPE> environment variable
479	contains an arbitrary string which corresponds to an already-installed
480	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
481	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
482	(i.e. C<de> or C<german>) are also common.
483
484	Rxvt-unicode ignores all other locale categories, and except for
485	the encoding, ignores country or language-specific settings,
486	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to
487	rxvt-unicode.
488
489	If you want to use a specific encoding you have to make sure you start
490	rxvt-unicode with the correct C<LC_CTYPE> category.
491
492	=item Can I switch locales at runtime?
493
494	Yes, using an escape sequence. Try something like this, which sets
495	rxvt-unicode's idea of C<LC_CTYPE>.
496
497	printf '\e]701;%s\007' ja_JP.SJIS
498
499	See also the previous answer.
500
501	Sometimes this capability is rather handy when you want to work in
502	one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
503	(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
504	first switches to a locale supported by xjdic and back later:
505
506	printf '\e]701;%s\007' ja_JP.SJIS
507	xjdic -js
508	printf '\e]701;%s\007' de_DE.UTF-8
509
510	You can also use xterm's C<luit> program, which usually works fine, except
511	for some locales where character width differs between program- and
512	rxvt-unicode-locales.
513
514	=item Can I switch the fonts at runtime?
515
516	Yes, using an escape sequence. Try something like this, which has the same
517	effect as using the C<-fn> switch, and takes effect immediately:
518
519	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
520
521	This is useful if you e.g. work primarily with japanese (and prefer a
522	japanese font), but you have to switch to chinese temporarily, where
523	japanese fonts would only be in your way.
524
525	You can think of this as a kind of manual ISO-2022 switching.
526
527	=item Why do italic characters look as if clipped?
528
529	Many fonts have difficulties with italic characters and hinting. For
530	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
531	Mono> completely fails in it's italic face. A workaround might be to
532	enable freetype autohinting, i.e. like this:
533
534	URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
535	URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
536
537	=item My input method wants <some encoding> but I want UTF-8, what can I do?
538
539	You can specify separate locales for the input method and the rest of the
540	terminal, using the resource C<imlocale>:
541
542	URxvt*imlocale: ja_JP.EUC-JP
543
544	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
545	use your input method. Please note, however, that you will not be able to
546	input characters outside C<EUC-JP> in a normal way then, as your input
547	method limits you.
548
549	=item Rxvt-unicode crashes when the X Input Method changes or exits.
550
551	Unfortunately, this is unavoidable, as the XIM protocol is racy by
552	design. Applications can avoid some crashes at the expense of memory
553	leaks, and Input Methods can avoid some crashes by careful ordering at
554	exit time. B<kinput2> (and derived input methods) generally succeeds,
555	while B<SCIM> (or similar input methods) fails. In the end, however,
556	crashes cannot be completely avoided even if both sides cooperate.
557
558	So the only workaround is not to kill your Input Method Servers.
559
560	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
561
562	Rxvt-unicode tries to obey the rule of not charging you for something you
563	don't use. One thing you should try is to configure out all settings that
564	you don't need, for example, Xft support is a resource hog by design,
565	when used. Compiling it out ensures that no Xft font will be loaded
566	accidentally when rxvt-unicode tries to find a font for your characters.
567
568	Also, many people (me included) like large windows and even larger
569	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
570	6 bytes per screen cell. For a 160x?? window this amounts to almost a
571	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
572	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
573	rxvt-unicode then uses 8 bytes per screen cell.
574
575	=item Can I speed up Xft rendering somehow?
576
577	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
578	it is simply slow. If you still want Xft fonts you might try to disable
579	antialiasing (by appending C<:antialias=false>), which saves lots of
580	memory and also speeds up rendering considerably.
581
582	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
583
584	Rxvt-unicode will use whatever you specify as a font. If it needs to
585	fall back to it's default font search list it will prefer X11 core
586	fonts, because they are small and fast, and then use Xft fonts. It has
587	antialiasing disabled for most of them, because the author thinks they
588	look best that way.
589
590	If you want antialiasing, you have to specify the fonts manually.
591
592	=item Mouse cut/paste suddenly no longer works.
593
594	Make sure that mouse reporting is actually turned off since killing
595	some editors prematurely may leave the mouse in mouse report mode. I've
596	heard that tcsh may use mouse reporting unless it otherwise specified. A
597	quick check is to see if cut/paste works when the Alt or Shift keys are
598	depressed. See @@RXVT_NAME@@(7)
599
600	=item What's with this bold/blink stuff?
601
602	If no bold colour is set via C<colorBD:>, bold will invert text using the
603	standard foreground colour.
604
605	For the standard background colour, blinking will actually make the
606	text blink when compiled with C<--enable-blinking>. with standard
607	colours. Without C<--enable-blinking>, the blink attribute will be
608	ignored.
609
610	On ANSI colours, bold/blink attributes are used to set high-intensity
611	foreground/background colors.
612
613	color0-7 are the low-intensity colors.
614
615	color8-15 are the corresponding high-intensity colors.
616
617	=item I don't like the screen colors. How do I change them?
618
619	You can change the screen colors at run-time using F<~/.Xdefaults>
620	resources (or as long-options).
621
622	Here are values that are supposed to resemble a VGA screen,
623	including the murky brown that passes for low-intensity yellow:
624
625	URxvt.color0: #000000
626	URxvt.color1: #A80000
627	URxvt.color2: #00A800
628	URxvt.color3: #A8A800
629	URxvt.color4: #0000A8
630	URxvt.color5: #A800A8
631	URxvt.color6: #00A8A8
632	URxvt.color7: #A8A8A8
633
634	URxvt.color8: #000054
635	URxvt.color9: #FF0054
636	URxvt.color10: #00FF54
637	URxvt.color11: #FFFF54
638	URxvt.color12: #0000FF
639	URxvt.color13: #FF00FF
640	URxvt.color14: #00FFFF
641	URxvt.color15: #FFFFFF
642
643	And here is a more complete set of non-standard colors described (not by
644	me) as "pretty girly".
645
646	URxvt.cursorColor: #dc74d1
647	URxvt.pointerColor: #dc74d1
648	URxvt.background: #0e0e0e
649	URxvt.foreground: #4ad5e1
650	URxvt.color0: #000000
651	URxvt.color8: #8b8f93
652	URxvt.color1: #dc74d1
653	URxvt.color9: #dc74d1
654	URxvt.color2: #0eb8c7
655	URxvt.color10: #0eb8c7
656	URxvt.color3: #dfe37e
657	URxvt.color11: #dfe37e
658	URxvt.color5: #9e88f0
659	URxvt.color13: #9e88f0
660	URxvt.color6: #73f7ff
661	URxvt.color14: #73f7ff
662	URxvt.color7: #e1dddd
663	URxvt.color15: #e1dddd
664
665	=item How can I start @@RXVT_NAME@@d in a race-free way?
666
667	Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
668	display, create the listening socket and then fork.
669
670	=item What's with the strange Backspace/Delete key behaviour?
671
672	Assuming that the physical Backspace key corresponds to the
673	BackSpace keysym (not likely for Linux ... see the following
674	question) there are two standard values that can be used for
675	Backspace: C<^H> and C<^?>.
676
677	Historically, either value is correct, but rxvt-unicode adopts the debian
678	policy of using C<^?> when unsure, because it's the one only only correct
679	choice :).
680
681	Rxvt-unicode tries to inherit the current stty settings and uses the value
682	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
683	started from a terminal (say, from a menu or by remote shell), then the
684	system value of `erase', which corresponds to CERASE in <termios.h>, will
685	be used (which may not be the same as your stty setting).
686
687	For starting a new rxvt-unicode:
688
689	# use Backspace = ^H
690	$ stty erase ^H
691	$ @@RXVT_NAME@@
692
693	# use Backspace = ^?
694	$ stty erase ^?
695	$ @@RXVT_NAME@@
696
697	Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
698
699	For an existing rxvt-unicode:
700
701	# use Backspace = ^H
702	$ stty erase ^H
703	$ echo -n "^[[36h"
704
705	# use Backspace = ^?
706	$ stty erase ^?
707	$ echo -n "^[[36l"
708
709	This helps satisfy some of the Backspace discrepancies that occur, but
710	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
711	properly reflects that.
712
713	The Delete key is a another casualty of the ill-defined Backspace problem.
714	To avoid confusion between the Backspace and Delete keys, the Delete
715	key has been assigned an escape sequence to match the vt100 for Execute
716	(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo.
717
718	Some other Backspace problems:
719
720	some editors use termcap/terminfo,
721	some editors (vim I'm told) expect Backspace = ^H,
722	GNU Emacs (and Emacs-like editors) use ^H for help.
723
724	Perhaps someday this will all be resolved in a consistent manner.
725
726	=item I don't like the key-bindings. How do I change them?
727
728	There are some compile-time selections available via configure. Unless
729	you have run "configure" with the C<--disable-resources> option you can
730	use the `keysym' resource to alter the keystrings associated with keysyms.
731
732	Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt>
733
734	URxvt.keysym.Home: \033[1~
735	URxvt.keysym.End: \033[4~
736	URxvt.keysym.C-apostrophe: \033<C-'>
737	URxvt.keysym.C-slash: \033<C-/>
738	URxvt.keysym.C-semicolon: \033<C-;>
739	URxvt.keysym.C-grave: \033<C-`>
740	URxvt.keysym.C-comma: \033<C-,>
741	URxvt.keysym.C-period: \033<C-.>
742	URxvt.keysym.C-0x60: \033<C-`>
743	URxvt.keysym.C-Tab: \033<C-Tab>
744	URxvt.keysym.C-Return: \033<C-Return>
745	URxvt.keysym.S-Return: \033<S-Return>
746	URxvt.keysym.S-space: \033<S-Space>
747	URxvt.keysym.M-Up: \033<M-Up>
748	URxvt.keysym.M-Down: \033<M-Down>
749	URxvt.keysym.M-Left: \033<M-Left>
750	URxvt.keysym.M-Right: \033<M-Right>
751	URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
752	URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
753	URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
754
755	See some more examples in the documentation for the B<keysym> resource.
756
757	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
758	How do I make use of them? For example, the Sun Keyboard type 4
759	has the following mappings that rxvt-unicode doesn't recognize.
760
761	KP_Insert == Insert
762	F22 == Print
763	F27 == Home
764	F29 == Prior
765	F33 == End
766	F35 == Next
767
768	Rather than have rxvt-unicode try to accommodate all the various possible
769	keyboard mappings, it is better to use `xmodmap' to remap the keys as
770	required for your particular machine.
771
772	=item How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
773	I need this to decide about setting colors etc.
774
775	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
776	check and see if that is set. Note that several programs, JED, slrn,
777	Midnight Commander automatically check this variable to decide whether or
778	not to use color.
779
780	=item How do I set the correct, full IP address for the DISPLAY variable?
781
782	If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
783	insecure mode then it is possible to use the following shell script
784	snippets to correctly set the display. If your version of rxvt-unicode
785	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
786	the COLORTERM variable can be used to distinguish rxvt-unicode from a
787	regular xterm.
788
789	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
790	snippets:
791
792	# Bourne/Korn/POSIX family of shells:
793	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
794	if [ ${TERM:-foo} = xterm ]; then
795	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
796	echo -n '^[Z'
797	read term_id
798	stty icanon echo
799	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
800	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
801	read DISPLAY # set it in our local shell
802	fi
803	fi
804
805	=item How do I compile the manual pages for myself?
806
807	You need to have a recent version of perl installed as F</usr/bin/perl>,
808	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
809	the doc subdirectory and enter C<make alldoc>.
810
811	=item My question isn't answered here, can I ask a human?
812
813	Before sending me mail, you could go to IRC: C<irc.freenode.net>,
814	channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be
815	interested in learning about new and exciting problems (but not FAQs :).
816
817	=back
818
819	=head1 RXVT TECHNICAL REFERENCE	1008	=head1 RXVT TECHNICAL REFERENCE
820		1009
821	=head1 DESCRIPTION	1010	=head1 DESCRIPTION
822		1011
823	The rest of this document describes various technical aspects of	1012	The rest of this document describes various technical aspects of
824	B<rxvt-unicode>. First the description of supported command sequences,	1013	B<rxvt-unicode>. First the description of supported command sequences,
825	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
826	features selectable at C<configure> time.	1015	selectable at C<configure> time.
827		1016
828	=head1 Definitions	1017	=head1 Definitions
829		1018
830	=over 4	1019	=over 4
831		1020
…		…
1399	B<< C<h> >> Send Mouse X & Y on button press.	1588	B<< C<h> >> Send Mouse X & Y on button press.
1400	B<< C<l> >> No mouse reporting.	1589	B<< C<l> >> No mouse reporting.
1401		1590
1402	=end table	1591	=end table
1403		1592
1404	=item B<< C<Ps = 10> >> (B<rxvt>)
1405
1406	=begin table
1407
1408	B<< C<h> >> menuBar visible
1409	B<< C<l> >> menuBar invisible
1410
1411	=end table
1412
1413	=item B<< C<Ps = 25> >>	1593	=item B<< C<Ps = 25> >>
1414		1594
1415	=begin table	1595	=begin table
1416		1596
1417	B<< C<h> >> Visible cursor {cnorm/cvvis}	1597	B<< C<h> >> Visible cursor {cnorm/cvvis}
…		…
1597	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>	1777	B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> B<(NB: may change in future)>
1598	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>	1778	B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> B<(NB: may change in future)>
1599	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> >>
1600	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> >>
1601	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> >>
1602	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >>	1782	B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706]
1603	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >>	1783	B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707]
1604	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).
1605	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> >>.
1606	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>
1607	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> >>.
1608	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> >>
1609	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> >>
1610	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).
1611	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>.
1612	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> >>
1613	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).
		1794	B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >>
		1795	B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >>
1614	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>.
1615	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	1797	B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1616	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	1798	B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1617	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).	1799	B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
1618	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).	1800	B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
1619	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).	1801	B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
		1802	B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1620		1803
1621	=end table	1804	=end table
1622		1805
1623	=back	1806	=back
1624		1807
1625	X<menuBar>
1626
1627	=head1 menuBar
1628
1629	B<< The exact syntax used is I<almost> solidified. >>
1630	In the menus, B<DON'T> try to use menuBar commands that add or remove a
1631	menuBar.
1632
1633	Note that in all of the commands, the B<< I</path/> >> I<cannot> be
1634	omitted: use B<./> to specify a menu relative to the current menu.
1635
1636	=head2 Overview of menuBar operation
1637
1638	For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax
1639	of C<Pt> can be used for a variety of tasks:
1640
1641	At the top level is the current menuBar which is a member of a circular
1642	linked-list of other such menuBars.
1643
1644	The menuBar acts as a parent for the various drop-down menus, which in
1645	turn, may have labels, separator lines, menuItems and subMenus.
1646
1647	The menuItems are the useful bits: you can use them to mimic keyboard
1648	input or even to send text or escape sequences back to rxvt.
1649
1650	The menuBar syntax is intended to provide a simple yet robust method of
1651	constructing and manipulating menus and navigating through the
1652	menuBars.
1653
1654	The first step is to use the tag B<< [menu:I<name>] >> which creates
1655	the menuBar called I<name> and allows access. You may now or menus,
1656	subMenus, and menuItems. Finally, use the tag B<[done]> to set the
1657	menuBar access as B<readonly> to prevent accidental corruption of the
1658	menus. To re-access the current menuBar for alterations, use the tag
1659	B<[menu]>, make the alterations and then use B<[done]>
1660
1661	X<menuBarCommands>
1662
1663	=head2 Commands
1664
1665	=over 4
1666
1667	=item B<< [menu:+I<name>] >>
1668
1669	access the named menuBar for creation or alteration. If a new menuBar
1670	is created, it is called I<name> (max of 15 chars) and the current
1671	menuBar is pushed onto the stack
1672
1673	=item B<[menu]>
1674
1675	access the current menuBar for alteration
1676
1677	=item B<< [title:+I<string>] >>
1678
1679	set the current menuBar's title to I<string>, which may contain the
1680	following format specifiers:
1681
1682	B<%n> rxvt name (as per the B<-name> command-line option)
1683	B<%v> rxvt version
1684	B<%%> literal B<%> character
1685
1686	=item B<[done]>
1687
1688	set menuBar access as B<readonly>.
1689	End-of-file tag for B<< [read:+I<file>] >> operations.
1690
1691	=item B<< [read:+I<file>] >>
1692
1693	read menu commands directly from I<file> (extension ".menu" will be
1694	appended if required.) Start reading at a line with B<[menu]> or B<<
1695	[menu:+I<name> >> and continuing until B<[done]> is encountered.
1696
1697	Blank and comment lines (starting with B<#>) are ignored. Actually,
1698	since any invalid menu commands are also ignored, almost anything could
1699	be construed as a comment line, but this may be tightened up in the
1700	future ... so don't count on it!.
1701
1702	=item B<< [read:+I<file>;+I<name>] >>
1703
1704	The same as B<< [read:+I<file>] >>, but start reading at a line with
1705	B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or
1706	B<[done]> is encountered.
1707
1708	=item B<[dump]>
1709
1710	dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for
1711	later rereading.
1712
1713	=item B<[rm:name]>
1714
1715	remove the named menuBar
1716
1717	=item B<[rm] [rm:]>
1718
1719	remove the current menuBar
1720
1721	=item B<[rm*] [rm:*]>
1722
1723	remove all menuBars
1724
1725	=item B<[swap]>
1726
1727	swap the top two menuBars
1728
1729	=item B<[prev]>
1730
1731	access the previous menuBar
1732
1733	=item B<[next]>
1734
1735	access the next menuBar
1736
1737	=item B<[show]>
1738
1739	Enable display of the menuBar
1740
1741	=item B<[hide]>
1742
1743	Disable display of the menuBar
1744
1745	=item B<< [pixmap:+I<name>] >>
1746
1747	=item B<< [pixmap:+I<name>;I<scaling>] >>
1748
1749	(set the background pixmap globally
1750
1751	B<< A Future implementation I<may> make this local to the menubar >>)
1752
1753	=item B<< [:+I<command>:] >>
1754
1755	ignore the menu readonly status and issue a I<command> to or a menu or
1756	menuitem or change the ; a useful shortcut for setting the quick arrows
1757	from a menuBar.
1758
1759	=back
1760
1761	X<menuBarAdd>
1762
1763	=head2 Adding and accessing menus
1764
1765	The following commands may also be B<+> prefixed.
1766
1767	=over 4
1768
1769	=item B</+>
1770
1771	access menuBar top level
1772
1773	=item B<./+>
1774
1775	access current menu level
1776
1777	=item B<../+>
1778
1779	access parent menu (1 level up)
1780
1781	=item B<../../>
1782
1783	access parent menu (multiple levels up)
1784
1785	=item B<< I</path/>menu >>
1786
1787	add/access menu
1788
1789	=item B<< I</path/>menu/* >>
1790
1791	add/access menu and clear it if it exists
1792
1793	=item B<< I</path/>{-} >>
1794
1795	add separator
1796
1797	=item B<< I</path/>{item} >>
1798
1799	add B<item> as a label
1800
1801	=item B<< I</path/>{item} action >>
1802
1803	add/alter I<menuitem> with an associated I<action>
1804
1805	=item B<< I</path/>{item}{right-text} >>
1806
1807	add/alter I<menuitem> with B<right-text> as the right-justified text
1808	and as the associated I<action>
1809
1810	=item B<< I</path/>{item}{rtext} action >>
1811
1812	add/alter I<menuitem> with an associated I<action> and with B<rtext> as
1813	the right-justified text.
1814
1815	=back
1816
1817	=over 4
1818
1819	=item Special characters in I<action> must be backslash-escaped:
1820
1821	B<\a \b \E \e \n \r \t \octal>
1822
1823	=item or in control-character notation:
1824
1825	B<^@, ^A .. ^Z .. ^_, ^?>
1826
1827	=back
1828
1829	To send a string starting with a B<NUL> (B<^@>) character to the
1830	program, start I<action> with a pair of B<NUL> characters (B<^@^@>),
1831	the first of which will be stripped off and the balance directed to the
1832	program. Otherwise if I<action> begins with B<NUL> followed by
1833	non-+B<NUL> characters, the leading B<NUL> is stripped off and the
1834	balance is sent back to rxvt.
1835
1836	As a convenience for the many Emacs-type editors, I<action> may start
1837	with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be
1838	appended if missed from B<M-x> commands.
1839
1840	As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or
1841	quick arrow), a B<BEL> (B<^G>) will be appended if needed.
1842
1843	=over 4
1844
1845	=item For example,
1846
1847	B<M-xapropos> is equivalent to B<\Exapropos\r>
1848
1849	=item and
1850
1851	B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a>
1852
1853	=back
1854
1855	The option B<< {I<right-rtext>} >> will be right-justified. In the
1856	absence of a specified action, this text will be used as the I<action>
1857	as well.
1858
1859	=over 4
1860
1861	=item For example,
1862
1863	B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F>
1864
1865	=back
1866
1867	The left label I<is> necessary, since it's used for matching, but
1868	implicitly hiding the left label (by using same name for both left and
1869	right labels), or explicitly hiding the left label (by preceeding it
1870	with a dot), makes it possible to have right-justified text only.
1871
1872	=over 4
1873
1874	=item For example,
1875
1876	B</File/{Open}{Open} Open-File-Action>
1877
1878	=item or hiding it
1879
1880	B</File/{.anylabel}{Open} Open-File-Action>
1881
1882	=back
1883
1884	X<menuBarRemove>
1885
1886	=head2 Removing menus
1887
1888	=over 4
1889
1890	=item B<< -/*+ >>
1891
1892	remove all menus from the menuBar, the same as B<[clear]>
1893
1894	=item B<< -+I</path>menu+ >>
1895
1896	remove menu
1897
1898	=item B<< -+I</path>{item}+ >>
1899
1900	remove item
1901
1902	=item B<< -+I</path>{-} >>
1903
1904	remove separator)
1905
1906	=item B<-/path/menu/*>
1907
1908	remove all items, separators and submenus from menu
1909
1910	=back
1911
1912	X<menuBarArrows>
1913
1914	=head2 Quick Arrows
1915
1916	The menus also provide a hook for I<quick arrows> to provide easier
1917	user access. If nothing has been explicitly set, the default is to
1918	emulate the curror keys. The syntax permits each arrow to be altered
1919	individually or all four at once without re-entering their common
1920	beginning/end text. For example, to explicitly associate cursor actions
1921	with the arrows, any of the following forms could be used:
1922
1923	=over 4
1924
1925	=item B<< <r>+I<Right> >>
1926
1927	=item B<< <l>+I<Left> >>
1928
1929	=item B<< <u>+I<Up> >>
1930
1931	=item B<< <d>+I<Down> >>
1932
1933	Define actions for the respective arrow buttons
1934
1935	=item B<< <b>+I<Begin> >>
1936
1937	=item B<< <e>+I<End> >>
1938
1939	Define common beginning/end parts for I<quick arrows> which used in
1940	conjunction with the above <r> <l> <u> <d> constructs
1941
1942	=back
1943
1944	=over 4
1945
1946	=item For example, define arrows individually,
1947
1948	<u>\E[A
1949
1950	<d>\E[B
1951
1952	<r>\E[C
1953
1954	<l>\E[D
1955
1956	=item or all at once
1957
1958	<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
1959
1960	=item or more compactly (factoring out common parts)
1961
1962	<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
1963
1964	=back
1965
1966	X<menuBarSummary>
1967
1968	=head2 Command Summary
1969
1970	A short summary of the most I<common> commands:
1971
1972	=over 4
1973
1974	=item [menu:name]
1975
1976	use an existing named menuBar or start a new one
1977
1978	=item [menu]
1979
1980	use the current menuBar
1981
1982	=item [title:string]
1983
1984	set menuBar title
1985
1986	=item [done]
1987
1988	set menu access to readonly and, if reading from a file, signal EOF
1989
1990	=item [done:name]
1991
1992	if reading from a file using [read:file;name] signal EOF
1993
1994	=item [rm:name]
1995
1996	remove named menuBar(s)
1997
1998	=item [rm] [rm:]
1999
2000	remove current menuBar
2001
2002	=item [rm*] [rm:*]
2003
2004	remove all menuBar(s)
2005
2006	=item [swap]
2007
2008	swap top two menuBars
2009
2010	=item [prev]
2011
2012	access the previous menuBar
2013
2014	=item [next]
2015
2016	access the next menuBar
2017
2018	=item [show]
2019
2020	map menuBar
2021
2022	=item [hide]
2023
2024	unmap menuBar
2025
2026	=item [pixmap;file]
2027
2028	=item [pixmap;file;scaling]
2029
2030	set a background pixmap
2031
2032	=item [read:file]
2033
2034	=item [read:file;name]
2035
2036	read in a menu from a file
2037
2038	=item [dump]
2039
2040	dump out all menuBars to /tmp/rxvt-PID
2041
2042	=item /
2043
2044	access menuBar top level
2045
2046	=item ./
2047
2048	=item ../
2049
2050	=item ../../
2051
2052	access current or parent menu level
2053
2054	=item /path/menu
2055
2056	add/access menu
2057
2058	=item /path/{-}
2059
2060	add separator
2061
2062	=item /path/{item}{rtext} action
2063
2064	add/alter menu item
2065
2066	=item -/*
2067
2068	remove all menus from the menuBar
2069
2070	=item -/path/menu
2071
2072	remove menu items, separators and submenus from menu
2073
2074	=item -/path/menu
2075
2076	remove menu
2077
2078	=item -/path/{item}
2079
2080	remove item
2081
2082	=item -/path/{-}
2083
2084	remove separator
2085
2086	=item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
2087
2088	menu quick arrows
2089
2090	=back
2091	X<XPM>	1808	X<XPM>
2092		1809
2093	=head1 XPM	1810	=head1 XPM
2094		1811
2095	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
…		…
2342	alternative input methods (e.g. kinput2) and will also correctly	2059	alternative input methods (e.g. kinput2) and will also correctly
2343	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.
2344		2061
2345	=item --enable-unicode3 (default: off)	2062	=item --enable-unicode3 (default: off)
2346		2063
		2064	Recommended to stay off unless you really need non-BMP characters.
		2065
2347	Enable direct support for displaying unicode codepoints above	2066	Enable direct support for displaying unicode codepoints above
2348	65535 (the basic multilingual page). This increases storage	2067	65535 (the basic multilingual page). This increases storage
2349	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
2350	support these extra characters, but Xft does.	2069	support these extra characters, but Xft does.
2351		2070
…		…
2361	composite characters. This is required for proper viewing of text	2080	composite characters. This is required for proper viewing of text
2362	where accents are encoded as seperate unicode characters. This is	2081	where accents are encoded as seperate unicode characters. This is
2363	done by using precomposited characters when available or creating	2082	done by using precomposited characters when available or creating
2364	new pseudo-characters when no precomposed form exists.	2083	new pseudo-characters when no precomposed form exists.
2365		2084
2366	Without --enable-unicode3, the number of additional precomposed characters	2085	Without --enable-unicode3, the number of additional precomposed
2367	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
2368	private use area, extending the number of combinations to 8448). With
2369	--enable-unicode3, no practical limit exists.	2087	(ab-)used). With --enable-unicode3, no practical limit exists.
2370		2088
2371	This option will also enable storage (but not display) of characters	2089	This option will also enable storage (but not display) of characters
2372	beyond plane 0 (>65535) when --enable-unicode3 was not specified.	2090	beyond plane 0 (>65535) when --enable-unicode3 was not specified.
2373		2091
2374	The combining table also contains entries for arabic presentation forms,	2092	The combining table also contains entries for arabic presentation forms,
2375	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
2376	tell me how these are to be used...).	2094	tell me how these are to be used...).
2377		2095
2378	=item --enable-fallback(=CLASS) (default: Rxvt)	2096	=item --enable-fallback(=CLASS) (default: Rxvt)
2379		2097
2380	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.
2381		2100
2382	=item --with-res-name=NAME (default: urxvt)	2101	=item --with-res-name=NAME (default: urxvt)
2383		2102
2384	Use the given name as default application name when	2103	Use the given name as default application name when
2385	reading resources. Specify --with-res-name=rxvt to replace rxvt.	2104	reading resources. Specify --with-res-name=rxvt to replace rxvt.
…		…
2405		2124
2406	Write user and tty to lastlog file (used by programs like	2125	Write user and tty to lastlog file (used by programs like
2407	F<lastlogin>) at start of rxvt execution. This option requires	2126	F<lastlogin>) at start of rxvt execution. This option requires
2408	--enable-utmp to also be specified.	2127	--enable-utmp to also be specified.
2409		2128
2410	=item --enable-xpm-background (default: off)	2129	=item --enable-xpm-background (default: on)
2411		2130
2412	Add support for XPM background pixmaps.	2131	Add support for XPM background pixmaps.
2413		2132
2414	=item --enable-transparency (default: off)	2133	=item --enable-transparency (default: on)
2415		2134
2416	Add support for inheriting parent backgrounds thus giving a fake	2135	Add support for inheriting parent backgrounds thus giving a fake
2417	transparency to the term.	2136	transparency to the term.
2418		2137
2419	=item --enable-fading (default: on)	2138	=item --enable-fading (default: on)
…		…
2421	Add support for fading the text when focus is lost (requires C<--enable-transparency>).	2140	Add support for fading the text when focus is lost (requires C<--enable-transparency>).
2422		2141
2423	=item --enable-tinting (default: on)	2142	=item --enable-tinting (default: on)
2424		2143
2425	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).	2144	Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
2426
2427	=item --enable-menubar (default: off)
2428
2429	Add support for our menu bar system (this interacts badly with
2430	dynamic locale switching currently).
2431		2145
2432	=item --enable-rxvt-scroll (default: on)	2146	=item --enable-rxvt-scroll (default: on)
2433		2147
2434	Add support for the original rxvt scrollbar.	2148	Add support for the original rxvt scrollbar.
2435		2149
…		…
2445		2159
2446	Add support for a very unobtrusive, plain-looking scrollbar that	2160	Add support for a very unobtrusive, plain-looking scrollbar that
2447	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
2448	many years.	2162	many years.
2449		2163
2450	=item --enable-half-shadow (default: off)
2451
2452	Make shadows on the scrollbar only half the normal width & height.
2453	only applicable to rxvt scrollbars.
2454
2455	=item --enable-ttygid (default: off)	2164	=item --enable-ttygid (default: off)
2456		2165
2457	Change tty device setting to group "tty" - only use this if	2166	Change tty device setting to group "tty" - only use this if
2458	your system uses this type of security.	2167	your system uses this type of security.
2459		2168
…		…
2467	do it.	2176	do it.
2468		2177
2469	=item --disable-resources	2178	=item --disable-resources
2470		2179
2471	Removes any support for resource checking.	2180	Removes any support for resource checking.
2472
2473	=item --enable-xgetdefault
2474
2475	Make resources checking via XGetDefault() instead of our small
2476	version which only checks ~/.Xdefaults, or if that doesn't exist then
2477	~/.Xresources.
2478
2479	Please note that nowadays, things like XIM will automatically pull in and
2480	use the full X resource manager, so the overhead of using it might be very
2481	small, if nonexistant.
2482
2483	=item --enable-strings (default: off)
2484
2485	Add support for our possibly faster memset() function and other
2486	various routines, overriding your system's versions which may
2487	have been hand-crafted in assembly or may require extra libraries
2488	to link in. (this breaks ANSI-C rules and has problems on many
2489	GNU/Linux systems).
2490		2181
2491	=item --disable-swapscreen	2182	=item --disable-swapscreen
2492		2183
2493	Remove support for secondary/swap screen.	2184	Remove support for secondary/swap screen.
2494		2185
…		…
2501	A non-exhaustive list of features enabled by C<--enable-frills> (possibly	2192	A non-exhaustive list of features enabled by C<--enable-frills> (possibly
2502	in combination with other switches) is:	2193	in combination with other switches) is:
2503		2194
2504	MWM-hints	2195	MWM-hints
2505	EWMH-hints (pid, utf8 names) and protocols (ping)	2196	EWMH-hints (pid, utf8 names) and protocols (ping)
2506	seperate underline colour	2197	seperate underline colour (-underlineColor)
2507	settable border widths and borderless switch	2198	settable border widths and borderless switch (-w, -b, -bl)
		2199	visual depth selection (-depth)
2508	settable extra linespacing	2200	settable extra linespacing /-lsp)
2509	iso-14755-2 and -3, and visual feedback	2201	iso-14755-2 and -3, and visual feedback
		2202	tripleclickwords (-tcw)
		2203	settable insecure mode (-insecure)
		2204	keysym remapping support
		2205	cursor blinking and underline cursor (-cb, -uc)
		2206	XEmbed support (-embed)
		2207	user-pty (-pty-fd)
		2208	hold on exit (-hold)
		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
		2216	sgr modes 90..97 and 100..107
2510	backindex and forwardindex escape sequence	2217	backindex and forwardindex escape sequences
		2218	view change/zero scorllback esacpe sequences
		2219	locale switching escape sequence
2511	window op and some xterm/OSC escape sequences	2220	window op and some xterm/OSC escape sequences
2512	tripleclickwords	2221	rectangular selections
2513	settable insecure mode	2222	trailing space removal for selections
2514	keysym remapping support	2223	verbose X error handling
2515	cursor blinking and underline cursor
2516	-embed, -pty-fd and -hold options
2517		2224
2518	=item --enable-iso14755 (default: on)	2225	=item --enable-iso14755 (default: on)
2519		2226
2520	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or	2227	Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
2521	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
…		…
2564		2271
2565	=item --enable-pointer-blank (default: on)	2272	=item --enable-pointer-blank (default: on)
2566		2273
2567	Add support to have the pointer disappear when typing or inactive.	2274	Add support to have the pointer disappear when typing or inactive.
2568		2275
2569	=item --enable-perl (default: off)	2276	=item --enable-perl (default: on)
2570		2277
2571	Enable an embedded perl interpreter. See the B<rxvtperl(3)> manpage	2278	Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
2572	(F<doc/rxvtperl.txt>) for more info on this feature, or the files in	2279	manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
2573	F<src/perl-ext/> for the extensions that are installed by default.	2280	in F<src/perl-ext/> for the extensions that are installed by default. The
		2281	perl interpreter that is used can be specified via the C<PERL> environment
		2282	variable when running configure.
2574		2283
2575	=item --with-name=NAME (default: urxvt)	2284	=item --with-name=NAME (default: urxvt)
2576		2285
2577	Set the basename for the installed binaries, resulting	2286	Set the basename for the installed binaries, resulting
2578	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with	2287	in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with

Diff Legend

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