ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.pod
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.74 by root, Mon Jan 9 07:24:43 2006 UTC vs.
Revision 1.101 by root, Tue Jan 31 01:02:19 2006 UTC

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

Diff Legend

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