1 |
=head1 NAME |
2 |
|
3 |
RXVT REFERENCE - FAQ, command sequences and other background information |
4 |
|
5 |
=head1 SYNOPSIS |
6 |
|
7 |
# set a new font set |
8 |
printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho" |
9 |
|
10 |
# change the locale and tell rxvt-unicode about it |
11 |
export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007" |
12 |
|
13 |
# set window title |
14 |
printf '\33]2;%s\007' "new window title" |
15 |
|
16 |
=head1 DESCRIPTION |
17 |
|
18 |
This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
19 |
all escape sequences, and other background information. |
20 |
|
21 |
The newest version of this document is also available on the World Wide Web at |
22 |
L<http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod>. |
23 |
|
24 |
The main manual page for @@RXVT_NAME@@ itself is available at |
25 |
L<http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.1.pod>. |
26 |
|
27 |
=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS |
28 |
|
29 |
|
30 |
=head2 Meta, Features & Commandline Issues |
31 |
|
32 |
=head3 My question isn't answered here, can I ask a human? |
33 |
|
34 |
Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
35 |
channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
36 |
interested in learning about new and exciting problems (but not FAQs :). |
37 |
|
38 |
=head3 I use Gentoo, and I have a problem... |
39 |
|
40 |
There are three big problems with Gentoo Linux: first of all, most if not |
41 |
all Gentoo systems are completely broken (missing or mismatched header |
42 |
files, broken compiler etc. are just the tip of the iceberg); secondly, |
43 |
the Gentoo maintainer thinks it is a good idea to add broken patches to |
44 |
the code; and lastly, it should be called Gentoo GNU/Linux. |
45 |
|
46 |
For these reasons, it is impossible to support rxvt-unicode on |
47 |
Gentoo. Problems appearing on Gentoo systems will usually simply be |
48 |
ignored unless they can be reproduced on non-Gentoo systems. |
49 |
|
50 |
=head3 Does it support tabs, can I have a tabbed rxvt-unicode? |
51 |
|
52 |
Beginning with version 7.3, there is a perl extension that implements a |
53 |
simple tabbed terminal. It is installed by default, so any of these should |
54 |
give you tabs: |
55 |
|
56 |
@@URXVT_NAME@@ -pe tabbed |
57 |
|
58 |
URxvt.perl-ext-common: default,tabbed |
59 |
|
60 |
It will also work fine with tabbing functionality of many window managers |
61 |
or similar tabbing programs, and its embedding-features allow it to be |
62 |
embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
63 |
the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
64 |
(murxvt) terminal as an example embedding application. |
65 |
|
66 |
=head3 How do I know which rxvt-unicode version I'm using? |
67 |
|
68 |
The version number is displayed with the usage (-h). Also the escape |
69 |
sequence C<ESC [ 8 n> sets the window title to the version number. When |
70 |
using the @@URXVT_NAME@@c client, the version displayed is that of the |
71 |
daemon. |
72 |
|
73 |
=head3 Rxvt-unicode uses gobs of memory, how can I reduce that? |
74 |
|
75 |
Rxvt-unicode tries to obey the rule of not charging you for something you |
76 |
don't use. One thing you should try is to configure out all settings that |
77 |
you don't need, for example, Xft support is a resource hog by design, |
78 |
when used. Compiling it out ensures that no Xft font will be loaded |
79 |
accidentally when rxvt-unicode tries to find a font for your characters. |
80 |
|
81 |
Also, many people (me included) like large windows and even larger |
82 |
scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
83 |
6 bytes per screen cell. For a 160x?? window this amounts to almost a |
84 |
kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
85 |
use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
86 |
rxvt-unicode then uses 8 bytes per screen cell. |
87 |
|
88 |
=head3 How can I start @@URXVT_NAME@@d in a race-free way? |
89 |
|
90 |
Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the |
91 |
display, create the listening socket and then fork. |
92 |
|
93 |
=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c? |
94 |
|
95 |
If you want to start @@URXVT_NAME@@d automatically whenever you run |
96 |
@@URXVT_NAME@@c and the daemon isn't running yet, use this script: |
97 |
|
98 |
#!/bin/sh |
99 |
@@URXVT_NAME@@c "$@" |
100 |
if [ $? -eq 2 ]; then |
101 |
@@URXVT_NAME@@d -q -o -f |
102 |
@@URXVT_NAME@@c "$@" |
103 |
fi |
104 |
|
105 |
This tries to create a new terminal, and if fails with exit status 2, |
106 |
meaning it couldn't connect to the daemon, it will start the daemon and |
107 |
re-run the command. Subsequent invocations of the script will re-use the |
108 |
existing daemon. |
109 |
|
110 |
=head3 How do I distinguish whether I'm running rxvt-unicode or a regular |
111 |
xterm? I need this to decide about setting colours etc. |
112 |
|
113 |
The original rxvt and rxvt-unicode always export the variable "COLORTERM", |
114 |
so you can check and see if that is set. Note that several programs, JED, |
115 |
slrn, Midnight Commander automatically check this variable to decide |
116 |
whether or not to use colour. |
117 |
|
118 |
=head3 How do I set the correct, full IP address for the DISPLAY variable? |
119 |
|
120 |
If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
121 |
insecure mode then it is possible to use the following shell script |
122 |
snippets to correctly set the display. If your version of rxvt-unicode |
123 |
wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
124 |
the COLORTERM variable can be used to distinguish rxvt-unicode from a |
125 |
regular xterm. |
126 |
|
127 |
Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
128 |
snippets: |
129 |
|
130 |
# Bourne/Korn/POSIX family of shells: |
131 |
[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
132 |
if [ ${TERM:-foo} = xterm ]; then |
133 |
stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
134 |
echo -n '^[Z' |
135 |
read term_id |
136 |
stty icanon echo |
137 |
if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
138 |
echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
139 |
read DISPLAY # set it in our local shell |
140 |
fi |
141 |
fi |
142 |
|
143 |
=head3 How do I compile the manual pages on my own? |
144 |
|
145 |
You need to have a recent version of perl installed as F</usr/bin/perl>, |
146 |
one that comes with F<pod2man>, F<pod2text> and F<pod2xhtml> (from |
147 |
F<Pod::Xhtml>). Then go to the doc subdirectory and enter C<make alldoc>. |
148 |
|
149 |
=head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
150 |
|
151 |
I often get asked about this, and I think, no, they didn't cause extra |
152 |
bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
153 |
that the urxvt binary is larger (due to some encoding tables always being |
154 |
compiled in), but it actually uses less memory (RSS) after startup. Even |
155 |
with C<--disable-everything>, this comparison is a bit unfair, as many |
156 |
features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
157 |
already in use in this mode. |
158 |
|
159 |
text data bss drs rss filename |
160 |
98398 1664 24 15695 1824 rxvt --disable-everything |
161 |
188985 9048 66616 18222 1788 urxvt --disable-everything |
162 |
|
163 |
When you C<--enable-everything> (which I<is> unfair, as this involves xft |
164 |
and full locale/XIM support which are quite bloaty inside libX11 and my |
165 |
libc), the two diverge, but not unreasonably so. |
166 |
|
167 |
text data bss drs rss filename |
168 |
163431 2152 24 20123 2060 rxvt --enable-everything |
169 |
1035683 49680 66648 29096 3680 urxvt --enable-everything |
170 |
|
171 |
The very large size of the text section is explained by the east-asian |
172 |
encoding tables, which, if unused, take up disk space but nothing else |
173 |
and can be compiled out unless you rely on X11 core fonts that use those |
174 |
encodings. The BSS size comes from the 64k emergency buffer that my c++ |
175 |
compiler allocates (but of course doesn't use unless you are out of |
176 |
memory). Also, using an xft font instead of a core font immediately adds a |
177 |
few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when |
178 |
not used. |
179 |
|
180 |
Of course, due to every character using two or four bytes instead of one, |
181 |
a large scrollback buffer will ultimately make rxvt-unicode use more |
182 |
memory. |
183 |
|
184 |
Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
185 |
still fares rather well. And compared to some monsters like gnome-terminal |
186 |
(21152k + extra 4204k in separate processes) or konsole (22200k + extra |
187 |
43180k in daemons that stay around after exit, plus half a minute of |
188 |
startup time, including the hundreds of warnings it spits out), it fares |
189 |
extremely well *g*. |
190 |
|
191 |
=head3 Why C++, isn't that unportable/bloated/uncool? |
192 |
|
193 |
Is this a question? :) It comes up very often. The simple answer is: I had |
194 |
to write it, and C++ allowed me to write and maintain it in a fraction |
195 |
of the time and effort (which is a scarce resource for me). Put even |
196 |
shorter: It simply wouldn't exist without C++. |
197 |
|
198 |
My personal stance on this is that C++ is less portable than C, but in |
199 |
the case of rxvt-unicode this hardly matters, as its portability limits |
200 |
are defined by things like X11, pseudo terminals, locale support and unix |
201 |
domain sockets, which are all less portable than C++ itself. |
202 |
|
203 |
Regarding the bloat, see the above question: It's easy to write programs |
204 |
in C that use gobs of memory, an certainly possible to write programs in |
205 |
C++ that don't. C++ also often comes with large libraries, but this is |
206 |
not necessarily the case with GCC. Here is what rxvt links against on my |
207 |
system with a minimal config: |
208 |
|
209 |
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
210 |
libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
211 |
libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
212 |
/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
213 |
|
214 |
And here is rxvt-unicode: |
215 |
|
216 |
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
217 |
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
218 |
libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
219 |
libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
220 |
/lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
221 |
|
222 |
No large bloated libraries (of course, none were linked in statically), |
223 |
except maybe libX11 :) |
224 |
|
225 |
|
226 |
=head2 Rendering, Font & Look and Feel Issues |
227 |
|
228 |
=head3 I can't get transparency working, what am I doing wrong? |
229 |
|
230 |
First of all, please address all transparency related issues to Sasha Vasko at |
231 |
sasha@aftercode.net and do not bug the author about it. Also, if you can't |
232 |
get it working consider it a rite of passage: ... and you failed. |
233 |
|
234 |
Here are four ways to get transparency. B<Do> read the manpage and option |
235 |
descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
236 |
|
237 |
1. Use transparent mode: |
238 |
|
239 |
Esetroot wallpaper.jpg |
240 |
@@URXVT_NAME@@ -tr -tint red -sh 40 |
241 |
|
242 |
That works. If you think it doesn't, you lack transparency and tinting |
243 |
support, or you are unable to read. |
244 |
|
245 |
2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
246 |
to use effects other than tinting and shading: Just shade/tint/whatever |
247 |
your picture with gimp or any other tool: |
248 |
|
249 |
convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
250 |
@@URXVT_NAME@@ -pixmap "background.jpg;:root" |
251 |
|
252 |
That works. If you think it doesn't, you lack AfterImage support, or you |
253 |
are unable to read. |
254 |
|
255 |
3. Use an ARGB visual: |
256 |
|
257 |
@@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
258 |
|
259 |
This requires XFT support, and the support of your X-server. If that |
260 |
doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
261 |
there yet, no matter what they claim. Rxvt-Unicode contains the necessary |
262 |
bugfixes and workarounds for Xft and Xlib to make it work, but that |
263 |
doesn't mean that your WM has the required kludges in place. |
264 |
|
265 |
4. Use xcompmgr and let it do the job: |
266 |
|
267 |
xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
268 |
-set _NET_WM_WINDOW_OPACITY 0xc0000000 |
269 |
|
270 |
Then click on a window you want to make transparent. Replace C<0xc0000000> |
271 |
by other values to change the degree of opacity. If it doesn't work and |
272 |
your server crashes, you got to keep the pieces. |
273 |
|
274 |
=head3 Why does rxvt-unicode sometimes leave pixel droppings? |
275 |
|
276 |
Most fonts were not designed for terminal use, which means that character |
277 |
size varies a lot. A font that is otherwise fine for terminal use might |
278 |
contain some characters that are simply too wide. Rxvt-unicode will avoid |
279 |
these characters. For characters that are just "a bit" too wide a special |
280 |
"careful" rendering mode is used that redraws adjacent characters. |
281 |
|
282 |
All of this requires that fonts do not lie about character sizes, |
283 |
however: Xft fonts often draw glyphs larger than their acclaimed bounding |
284 |
box, and rxvt-unicode has no way of detecting this (the correct way is to |
285 |
ask for the character bounding box, which unfortunately is wrong in these |
286 |
cases). |
287 |
|
288 |
It's not clear (to me at least), whether this is a bug in Xft, freetype, |
289 |
or the respective font. If you encounter this problem you might try using |
290 |
the C<-lsp> option to give the font more height. If that doesn't work, you |
291 |
might be forced to use a different font. |
292 |
|
293 |
All of this is not a problem when using X11 core fonts, as their bounding |
294 |
box data is correct. |
295 |
|
296 |
=head3 How can I keep rxvt-unicode from using reverse video so much? |
297 |
|
298 |
First of all, make sure you are running with the right terminal settings |
299 |
(C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
300 |
make sure you have specified colours for italic and bold, as otherwise |
301 |
rxvt-unicode might use reverse video to simulate the effect: |
302 |
|
303 |
URxvt.colorBD: white |
304 |
URxvt.colorIT: green |
305 |
|
306 |
=head3 Some programs assume totally weird colours (red instead of blue), how can I fix that? |
307 |
|
308 |
For some unexplainable reason, some rare programs assume a very weird |
309 |
colour palette when confronted with a terminal with more than the standard |
310 |
8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
311 |
these programs not to assume non-ISO colours without very good reasons. |
312 |
|
313 |
In the meantime, you can either edit your C<rxvt-unicode> terminfo |
314 |
definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
315 |
fix colours but keep you from using other rxvt-unicode features. |
316 |
|
317 |
=head3 Can I switch the fonts at runtime? |
318 |
|
319 |
Yes, using an escape sequence. Try something like this, which has the same |
320 |
effect as using the C<-fn> switch, and takes effect immediately: |
321 |
|
322 |
printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic" |
323 |
|
324 |
This is useful if you e.g. work primarily with japanese (and prefer a |
325 |
japanese font), but you have to switch to chinese temporarily, where |
326 |
japanese fonts would only be in your way. |
327 |
|
328 |
You can think of this as a kind of manual ISO-2022 switching. |
329 |
|
330 |
=head3 Why do italic characters look as if clipped? |
331 |
|
332 |
Many fonts have difficulties with italic characters and hinting. For |
333 |
example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
334 |
Mono> completely fails in its italic face. A workaround might be to |
335 |
enable freetype autohinting, i.e. like this: |
336 |
|
337 |
URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
338 |
URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
339 |
|
340 |
=head3 Can I speed up Xft rendering somehow? |
341 |
|
342 |
Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
343 |
it is simply slow. If you still want Xft fonts you might try to disable |
344 |
antialiasing (by appending C<:antialias=false>), which saves lots of |
345 |
memory and also speeds up rendering considerably. |
346 |
|
347 |
=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
348 |
|
349 |
Rxvt-unicode will use whatever you specify as a font. If it needs to |
350 |
fall back to its default font search list it will prefer X11 core |
351 |
fonts, because they are small and fast, and then use Xft fonts. It has |
352 |
antialiasing disabled for most of them, because the author thinks they |
353 |
look best that way. |
354 |
|
355 |
If you want antialiasing, you have to specify the fonts manually. |
356 |
|
357 |
=head3 What's with this bold/blink stuff? |
358 |
|
359 |
If no bold colour is set via C<colorBD:>, bold will invert text using the |
360 |
standard foreground colour. |
361 |
|
362 |
For the standard background colour, blinking will actually make |
363 |
the text blink when compiled with C<--enable-text-blink>. Without |
364 |
C<--enable-text-blink>, the blink attribute will be ignored. |
365 |
|
366 |
On ANSI colours, bold/blink attributes are used to set high-intensity |
367 |
foreground/background colours. |
368 |
|
369 |
color0-7 are the low-intensity colours. |
370 |
|
371 |
color8-15 are the corresponding high-intensity colours. |
372 |
|
373 |
=head3 I don't like the screen colours. How do I change them? |
374 |
|
375 |
You can change the screen colours at run-time using F<~/.Xdefaults> |
376 |
resources (or as long-options). |
377 |
|
378 |
Here are values that are supposed to resemble a VGA screen, |
379 |
including the murky brown that passes for low-intensity yellow: |
380 |
|
381 |
URxvt.color0: #000000 |
382 |
URxvt.color1: #A80000 |
383 |
URxvt.color2: #00A800 |
384 |
URxvt.color3: #A8A800 |
385 |
URxvt.color4: #0000A8 |
386 |
URxvt.color5: #A800A8 |
387 |
URxvt.color6: #00A8A8 |
388 |
URxvt.color7: #A8A8A8 |
389 |
|
390 |
URxvt.color8: #000054 |
391 |
URxvt.color9: #FF0054 |
392 |
URxvt.color10: #00FF54 |
393 |
URxvt.color11: #FFFF54 |
394 |
URxvt.color12: #0000FF |
395 |
URxvt.color13: #FF00FF |
396 |
URxvt.color14: #00FFFF |
397 |
URxvt.color15: #FFFFFF |
398 |
|
399 |
And here is a more complete set of non-standard colours. |
400 |
|
401 |
URxvt.cursorColor: #dc74d1 |
402 |
URxvt.pointerColor: #dc74d1 |
403 |
URxvt.background: #0e0e0e |
404 |
URxvt.foreground: #4ad5e1 |
405 |
URxvt.color0: #000000 |
406 |
URxvt.color8: #8b8f93 |
407 |
URxvt.color1: #dc74d1 |
408 |
URxvt.color9: #dc74d1 |
409 |
URxvt.color2: #0eb8c7 |
410 |
URxvt.color10: #0eb8c7 |
411 |
URxvt.color3: #dfe37e |
412 |
URxvt.color11: #dfe37e |
413 |
URxvt.color5: #9e88f0 |
414 |
URxvt.color13: #9e88f0 |
415 |
URxvt.color6: #73f7ff |
416 |
URxvt.color14: #73f7ff |
417 |
URxvt.color7: #e1dddd |
418 |
URxvt.color15: #e1dddd |
419 |
|
420 |
They have been described (not by me) as "pretty girly". |
421 |
|
422 |
=head3 Why do some characters look so much different than others? |
423 |
|
424 |
See next entry. |
425 |
|
426 |
=head3 How does rxvt-unicode choose fonts? |
427 |
|
428 |
Most fonts do not contain the full range of Unicode, which is |
429 |
fine. Chances are that the font you (or the admin/package maintainer of |
430 |
your system/os) have specified does not cover all the characters you want |
431 |
to display. |
432 |
|
433 |
B<rxvt-unicode> makes a best-effort try at finding a replacement |
434 |
font. Often the result is fine, but sometimes the chosen font looks |
435 |
bad/ugly/wrong. Some fonts have totally strange characters that don't |
436 |
resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
437 |
intelligence to detect that a specific glyph is wrong: it has to believe |
438 |
the font that the characters it claims to contain indeed look correct. |
439 |
|
440 |
In that case, select a font of your taste and add it to the font list, |
441 |
e.g.: |
442 |
|
443 |
@@URXVT_NAME@@ -fn basefont,font2,font3... |
444 |
|
445 |
When rxvt-unicode sees a character, it will first look at the base |
446 |
font. If the base font does not contain the character, it will go to the |
447 |
next font, and so on. Specifying your own fonts will also speed up this |
448 |
search and use less resources within rxvt-unicode and the X-server. |
449 |
|
450 |
The only limitation is that none of the fonts may be larger than the base |
451 |
font, as the base font defines the terminal character cell size, which |
452 |
must be the same due to the way terminals work. |
453 |
|
454 |
=head3 Why do some chinese characters look so different than others? |
455 |
|
456 |
This is because there is a difference between script and language -- |
457 |
rxvt-unicode does not know which language the text that is output is, |
458 |
as it only knows the unicode character codes. If rxvt-unicode first |
459 |
sees a japanese/chinese character, it might choose a japanese font for |
460 |
display. Subsequent japanese characters will use that font. Now, many |
461 |
chinese characters aren't represented in japanese fonts, so when the first |
462 |
non-japanese character comes up, rxvt-unicode will look for a chinese font |
463 |
-- unfortunately at this point, it will still use the japanese font for |
464 |
chinese characters that are also in the japanese font. |
465 |
|
466 |
The workaround is easy: just tag a chinese font at the end of your font |
467 |
list (see the previous question). The key is to view the font list as |
468 |
a preference list: If you expect more japanese, list a japanese font |
469 |
first. If you expect more chinese, put a chinese font first. |
470 |
|
471 |
In the future it might be possible to switch language preferences at |
472 |
runtime (the internal data structure has no problem with using different |
473 |
fonts for the same character at the same time, but no interface for this |
474 |
has been designed yet). |
475 |
|
476 |
Until then, you might get away with switching fonts at runtime (see L<Can |
477 |
I switch the fonts at runtime?> later in this document). |
478 |
|
479 |
=head3 How can I make mplayer display video correctly? |
480 |
|
481 |
We are working on it, in the meantime, as a workaround, use something like: |
482 |
|
483 |
@@URXVT_NAME@@ -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
484 |
|
485 |
|
486 |
=head2 Keyboard, Mouse & User Interaction |
487 |
|
488 |
=head3 The new selection selects pieces that are too big, how can I select single words? |
489 |
|
490 |
If you want to select e.g. alphanumeric words, you can use the following |
491 |
setting: |
492 |
|
493 |
URxvt.selection.pattern-0: ([[:word:]]+) |
494 |
|
495 |
If you click more than twice, the selection will be extended |
496 |
more and more. |
497 |
|
498 |
To get a selection that is very similar to the old code, try this pattern: |
499 |
|
500 |
URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
501 |
|
502 |
Please also note that the I<LeftClick Shift-LeftClick> combination also |
503 |
selects words like the old code. |
504 |
|
505 |
=head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
506 |
|
507 |
You can disable the perl extension completely by setting the |
508 |
B<perl-ext-common> resource to the empty string, which also keeps |
509 |
rxvt-unicode from initialising perl, saving memory. |
510 |
|
511 |
If you only want to disable specific features, you first have to |
512 |
identify which perl extension is responsible. For this, read the section |
513 |
B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For |
514 |
example, to disable the B<selection-popup> and B<option-popup>, specify |
515 |
this B<perl-ext-common> resource: |
516 |
|
517 |
URxvt.perl-ext-common: default,-selection-popup,-option-popup |
518 |
|
519 |
This will keep the default extensions, but disable the two popup |
520 |
extensions. Some extensions can also be configured, for example, |
521 |
scrollback search mode is triggered by B<M-s>. You can move it to any |
522 |
other combination either by setting the B<searchable-scrollback> resource: |
523 |
|
524 |
URxvt.searchable-scrollback: CM-s |
525 |
|
526 |
=head3 The cursor moves when selecting text in the current input line, how do I switch this off? |
527 |
|
528 |
See next entry. |
529 |
|
530 |
=head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
531 |
|
532 |
These are caused by the C<readline> perl extension. Under normal |
533 |
circumstances, it will move your cursor around when you click into the |
534 |
line that contains it. It tries hard not to do this at the wrong moment, |
535 |
but when running a program that doesn't parse cursor movements or in some |
536 |
cases during rlogin sessions, it fails to detect this properly. |
537 |
|
538 |
You can permanently switch this feature off by disabling the C<readline> |
539 |
extension: |
540 |
|
541 |
URxvt.perl-ext-common: default,-readline |
542 |
|
543 |
=head3 My numerical keypad acts weird and generates differing output? |
544 |
|
545 |
Some Debian GNUL/Linux users seem to have this problem, although no |
546 |
specific details were reported so far. It is possible that this is caused |
547 |
by the wrong C<TERM> setting, although the details of whether and how |
548 |
this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
549 |
keymap. See the answer to the previous question, and please report if that |
550 |
helped. |
551 |
|
552 |
=head3 My Compose (Multi_key) key is no longer working. |
553 |
|
554 |
The most common causes for this are that either your locale is not set |
555 |
correctly, or you specified a B<preeditStyle> that is not supported by |
556 |
your input method. For example, if you specified B<OverTheSpot> and |
557 |
your input method (e.g. the default input method handling Compose keys) |
558 |
does not support this (for instance because it is not visual), then |
559 |
rxvt-unicode will continue without an input method. |
560 |
|
561 |
In this case either do not specify a B<preeditStyle> or specify more than |
562 |
one pre-edit style, such as B<OverTheSpot,Root,None>. |
563 |
|
564 |
If it still doesn't work, then maybe your input method doesn't support |
565 |
compose sequences - to fall back to the built-in one, make sure you don't |
566 |
specify an input method via C<-im> or C<XMODIFIERS>. |
567 |
|
568 |
=head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
569 |
|
570 |
Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
571 |
international keyboards) or simply use ISO 14755 support to your |
572 |
advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
573 |
codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
574 |
character and so on. |
575 |
|
576 |
=head3 Mouse cut/paste suddenly no longer works. |
577 |
|
578 |
Make sure that mouse reporting is actually turned off since killing |
579 |
some editors prematurely may leave the mouse in mouse report mode. I've |
580 |
heard that tcsh may use mouse reporting unless it otherwise specified. A |
581 |
quick check is to see if cut/paste works when the Alt or Shift keys are |
582 |
depressed. |
583 |
|
584 |
=head3 What's with the strange Backspace/Delete key behaviour? |
585 |
|
586 |
Assuming that the physical Backspace key corresponds to the |
587 |
Backspace keysym (not likely for Linux ... see the following |
588 |
question) there are two standard values that can be used for |
589 |
Backspace: C<^H> and C<^?>. |
590 |
|
591 |
Historically, either value is correct, but rxvt-unicode adopts the debian |
592 |
policy of using C<^?> when unsure, because it's the one and only correct |
593 |
choice :). |
594 |
|
595 |
Rxvt-unicode tries to inherit the current stty settings and uses the value |
596 |
of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
597 |
started from a terminal (say, from a menu or by remote shell), then the |
598 |
system value of `erase', which corresponds to CERASE in <termios.h>, will |
599 |
be used (which may not be the same as your stty setting). |
600 |
|
601 |
For starting a new rxvt-unicode: |
602 |
|
603 |
# use Backspace = ^H |
604 |
$ stty erase ^H |
605 |
$ @@URXVT_NAME@@ |
606 |
|
607 |
# use Backspace = ^? |
608 |
$ stty erase ^? |
609 |
$ @@URXVT_NAME@@ |
610 |
|
611 |
Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. |
612 |
|
613 |
For an existing rxvt-unicode: |
614 |
|
615 |
# use Backspace = ^H |
616 |
$ stty erase ^H |
617 |
$ echo -n "^[[36h" |
618 |
|
619 |
# use Backspace = ^? |
620 |
$ stty erase ^? |
621 |
$ echo -n "^[[36l" |
622 |
|
623 |
This helps satisfy some of the Backspace discrepancies that occur, but |
624 |
if you use Backspace = C<^H>, make sure that the termcap/terminfo value |
625 |
properly reflects that. |
626 |
|
627 |
The Delete key is a another casualty of the ill-defined Backspace problem. |
628 |
To avoid confusion between the Backspace and Delete keys, the Delete |
629 |
key has been assigned an escape sequence to match the vt100 for Execute |
630 |
(C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
631 |
|
632 |
Some other Backspace problems: |
633 |
|
634 |
some editors use termcap/terminfo, |
635 |
some editors (vim I'm told) expect Backspace = ^H, |
636 |
GNU Emacs (and Emacs-like editors) use ^H for help. |
637 |
|
638 |
Perhaps someday this will all be resolved in a consistent manner. |
639 |
|
640 |
=head3 I don't like the key-bindings. How do I change them? |
641 |
|
642 |
There are some compile-time selections available via configure. Unless |
643 |
you have run "configure" with the C<--disable-resources> option you can |
644 |
use the `keysym' resource to alter the keystrings associated with keysyms. |
645 |
|
646 |
Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt> |
647 |
|
648 |
URxvt.keysym.Home: \033[1~ |
649 |
URxvt.keysym.End: \033[4~ |
650 |
URxvt.keysym.C-apostrophe: \033<C-'> |
651 |
URxvt.keysym.C-slash: \033<C-/> |
652 |
URxvt.keysym.C-semicolon: \033<C-;> |
653 |
URxvt.keysym.C-grave: \033<C-`> |
654 |
URxvt.keysym.C-comma: \033<C-,> |
655 |
URxvt.keysym.C-period: \033<C-.> |
656 |
URxvt.keysym.C-0x60: \033<C-`> |
657 |
URxvt.keysym.C-Tab: \033<C-Tab> |
658 |
URxvt.keysym.C-Return: \033<C-Return> |
659 |
URxvt.keysym.S-Return: \033<S-Return> |
660 |
URxvt.keysym.S-space: \033<S-Space> |
661 |
URxvt.keysym.M-Up: \033<M-Up> |
662 |
URxvt.keysym.M-Down: \033<M-Down> |
663 |
URxvt.keysym.M-Left: \033<M-Left> |
664 |
URxvt.keysym.M-Right: \033<M-Right> |
665 |
URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
666 |
URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
667 |
URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
668 |
|
669 |
See some more examples in the documentation for the B<keysym> resource. |
670 |
|
671 |
=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 |
672 |
|
673 |
KP_Insert == Insert |
674 |
F22 == Print |
675 |
F27 == Home |
676 |
F29 == Prior |
677 |
F33 == End |
678 |
F35 == Next |
679 |
|
680 |
Rather than have rxvt-unicode try to accommodate all the various possible |
681 |
keyboard mappings, it is better to use `xmodmap' to remap the keys as |
682 |
required for your particular machine. |
683 |
|
684 |
|
685 |
=head2 Terminal Configuration |
686 |
|
687 |
=head3 Can I see a typical configuration? |
688 |
|
689 |
The default configuration tries to be xterm-like, which I don't like that |
690 |
much, but it's least surprise to regular users. |
691 |
|
692 |
As a rxvt or rxvt-unicode user, you are practically supposed to invest |
693 |
time into customising your terminal. To get you started, here is the |
694 |
author's .Xdefaults entries, with comments on what they do. It's certainly |
695 |
not I<typical>, but what's typical... |
696 |
|
697 |
URxvt.cutchars: "()*,<>[]{}|' |
698 |
URxvt.print-pipe: cat >/tmp/xxx |
699 |
|
700 |
These are just for testing stuff. |
701 |
|
702 |
URxvt.imLocale: ja_JP.UTF-8 |
703 |
URxvt.preeditType: OnTheSpot,None |
704 |
|
705 |
This tells rxvt-unicode to use a special locale when communicating with |
706 |
the X Input Method, and also tells it to only use the OnTheSpot pre-edit |
707 |
type, which requires the C<xim-onthespot> perl extension but rewards me |
708 |
with correct-looking fonts. |
709 |
|
710 |
URxvt.perl-lib: /root/lib/urxvt |
711 |
URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard |
712 |
URxvt.selection.pattern-0: ( at .*? line \\d+) |
713 |
URxvt.selection.pattern-1: ^(/[^:]+):\ |
714 |
URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
715 |
URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
716 |
|
717 |
This is my perl configuration. The first two set the perl library |
718 |
directory and also tells urxvt to use a large number of extensions. I |
719 |
develop for myself mostly, so I actually use most of the extensions I |
720 |
write. |
721 |
|
722 |
The selection stuff mainly makes the selection perl-error-message aware |
723 |
and tells it to convert perl error messages into vi-commands to load the |
724 |
relevant file and go to the error line number. |
725 |
|
726 |
URxvt.scrollstyle: plain |
727 |
URxvt.secondaryScroll: true |
728 |
|
729 |
As the documentation says: plain is the preferred scrollbar for the |
730 |
author. The C<secondaryScroll> configures urxvt to scroll in full-screen |
731 |
apps, like screen, so lines scrolled out of screen end up in urxvt's |
732 |
scrollback buffer. |
733 |
|
734 |
URxvt.background: #000000 |
735 |
URxvt.foreground: gray90 |
736 |
URxvt.color7: gray90 |
737 |
URxvt.colorBD: #ffffff |
738 |
URxvt.cursorColor: #e0e080 |
739 |
URxvt.throughColor: #8080f0 |
740 |
URxvt.highlightColor: #f0f0f0 |
741 |
|
742 |
Some colours. Not sure which ones are being used or even non-defaults, but |
743 |
these are in my .Xdefaults. Most notably, they set foreground/background |
744 |
to light gray/black, and also make sure that the colour 7 matches the |
745 |
default foreground colour. |
746 |
|
747 |
URxvt.underlineColor: yellow |
748 |
|
749 |
Another colour, makes underline lines look different. Sometimes hurts, but |
750 |
is mostly a nice effect. |
751 |
|
752 |
URxvt.geometry: 154x36 |
753 |
URxvt.loginShell: false |
754 |
URxvt.meta: ignore |
755 |
URxvt.utmpInhibit: true |
756 |
|
757 |
Uh, well, should be mostly self-explanatory. By specifying some defaults |
758 |
manually, I can quickly switch them for testing. |
759 |
|
760 |
URxvt.saveLines: 8192 |
761 |
|
762 |
A large scrollback buffer is essential. Really. |
763 |
|
764 |
URxvt.mapAlert: true |
765 |
|
766 |
The only case I use it is for my IRC window, which I like to keep |
767 |
iconified till people msg me (which beeps). |
768 |
|
769 |
URxvt.visualBell: true |
770 |
|
771 |
The audible bell is often annoying, especially when in a crowd. |
772 |
|
773 |
URxvt.insecure: true |
774 |
|
775 |
Please don't hack my mutt! Ooops... |
776 |
|
777 |
URxvt.pastableTabs: false |
778 |
|
779 |
I once thought this is a great idea. |
780 |
|
781 |
urxvt.font: 9x15bold,\ |
782 |
-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
783 |
-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
784 |
[codeset=JISX0208]xft:Kochi Gothic, \ |
785 |
xft:Bitstream Vera Sans Mono:autohint=true, \ |
786 |
xft:Code2000:antialias=false |
787 |
urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
788 |
urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
789 |
urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
790 |
|
791 |
I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
792 |
overwhelmed. A special note: the C<9x15bold> mentioned above is actually |
793 |
the version from XFree-3.3, as XFree-4 replaced it by a totally different |
794 |
font (different glyphs for C<;> and many other harmless characters), |
795 |
while the second font is actually the C<9x15bold> from XFree4/XOrg. The |
796 |
bold version has less chars than the medium version, so I use it for rare |
797 |
characters, too. When editing sources with vim, I use italic for comments |
798 |
and other stuff, which looks quite good with Bitstream Vera anti-aliased. |
799 |
|
800 |
Terminus is a quite bad font (many very wrong glyphs), but for most of my |
801 |
purposes, it works, and gives a different look, as my normal (Non-bold) |
802 |
font is already bold, and I want to see a difference between bold and |
803 |
normal fonts. |
804 |
|
805 |
Please note that I used the C<urxvt> instance name and not the C<URxvt> |
806 |
class name. That is because I use different configs for different purposes, |
807 |
for example, my IRC window is started with C<-name IRC>, and uses these |
808 |
defaults: |
809 |
|
810 |
IRC*title: IRC |
811 |
IRC*geometry: 87x12+535+542 |
812 |
IRC*saveLines: 0 |
813 |
IRC*mapAlert: true |
814 |
IRC*font: suxuseuro |
815 |
IRC*boldFont: suxuseuro |
816 |
IRC*colorBD: white |
817 |
IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
818 |
IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
819 |
|
820 |
C<Alt-Ctrl-1> and C<Alt-Ctrl-2> switch between two different font |
821 |
sizes. C<suxuseuro> allows me to keep an eye (and actually read) |
822 |
stuff while keeping a very small window. If somebody pastes something |
823 |
complicated (e.g. japanese), I temporarily switch to a larger font. |
824 |
|
825 |
The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor |
826 |
C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname> |
827 |
file for different hosts, for example, on ym main desktop, I use: |
828 |
|
829 |
URxvt.keysym.C-M-q: command:\033[3;5;5t |
830 |
URxvt.keysym.C-M-y: command:\033[3;5;606t |
831 |
URxvt.keysym.C-M-e: command:\033[3;1605;5t |
832 |
URxvt.keysym.C-M-c: command:\033[3;1605;606t |
833 |
URxvt.keysym.C-M-p: perl:test |
834 |
|
835 |
The first for keysym definitions allow me to quickly bring some windows |
836 |
in the layout I like most. Ion users might start laughing but will stop |
837 |
immediately when I tell them that I use my own Fvwm2 module for much the |
838 |
same effect as Ion provides, and I only very rarely use the above key |
839 |
combinations :-> |
840 |
|
841 |
=head3 Why doesn't rxvt-unicode read my resources? |
842 |
|
843 |
Well, why, indeed? It does, in a way very similar to other X |
844 |
applications. Most importantly, this means that if you or your OS loads |
845 |
resources into the X display (the right way to do it), rxvt-unicode will |
846 |
ignore any resource files in your home directory. It will only read |
847 |
F<$HOME/.Xdefaults> when no resources are attached to the display. |
848 |
|
849 |
If you have or use an F<$HOME/.Xresources> file, chances are that |
850 |
resources are loaded into your X-server. In this case, you have to |
851 |
re-login after every change (or run F<xrdb -merge $HOME/.Xresources>). |
852 |
|
853 |
Also consider the form resources have to use: |
854 |
|
855 |
URxvt.resource: value |
856 |
|
857 |
If you want to use another form (there are lots of different ways of |
858 |
specifying resources), make sure you understand whether and why it |
859 |
works. If unsure, use the form above. |
860 |
|
861 |
=head3 When I log-in to another system it tells me about missing terminfo data? |
862 |
|
863 |
The terminal description used by rxvt-unicode is not as widely available |
864 |
as that for xterm, or even rxvt (for which the same problem often arises). |
865 |
|
866 |
The correct solution for this problem is to install the terminfo, this can |
867 |
be done by simply installing rxvt-unicode on the remote system as well |
868 |
(in case you have a nice package manager ready), or you can install the |
869 |
terminfo database manually like this (with ncurses infocmp. works as |
870 |
user and root): |
871 |
|
872 |
REMOTE=remotesystem.domain |
873 |
infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
874 |
|
875 |
One some systems you might need to set C<$TERMINFO> to the full path of |
876 |
F<$HOME/.terminfo> for this to work. |
877 |
|
878 |
If you cannot or do not want to do this, then you can simply set |
879 |
C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
880 |
problems arising, which includes wrong keymapping, less and different |
881 |
colours and some refresh errors in fullscreen applications. It's a nice |
882 |
quick-and-dirty workaround for rare cases, though. |
883 |
|
884 |
If you always want to do this (and are fine with the consequences) you |
885 |
can either recompile rxvt-unicode with the desired TERM value or use a |
886 |
resource to set it: |
887 |
|
888 |
URxvt.termName: rxvt |
889 |
|
890 |
If you don't plan to use B<rxvt> (quite common...) you could also replace |
891 |
the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>. |
892 |
|
893 |
=head3 nano fails with "Error opening terminal: rxvt-unicode" |
894 |
|
895 |
This exceptionally confusing and useless error message is printed by nano |
896 |
when it can't find the terminfo database. Nothing is wrong with your |
897 |
terminal, read the previous answer for a solution. |
898 |
|
899 |
=head3 C<tic> outputs some error when compiling the terminfo entry. |
900 |
|
901 |
Most likely it's the empty definition for C<enacs=>. Just replace it by |
902 |
C<enacs=\E[0@> and try again. |
903 |
|
904 |
=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@. |
905 |
|
906 |
See next entry. |
907 |
|
908 |
=head3 I need a termcap file entry. |
909 |
|
910 |
One reason you might want this is that some distributions or operating |
911 |
systems still compile some programs using the long-obsoleted termcap |
912 |
library (Fedora Core's bash is one example) and rely on a termcap entry |
913 |
for C<rxvt-unicode>. |
914 |
|
915 |
You could use rxvt's termcap entry with reasonable results in many cases. |
916 |
You can also create a termcap entry by using terminfo's infocmp program |
917 |
like this: |
918 |
|
919 |
infocmp -C rxvt-unicode |
920 |
|
921 |
Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap, |
922 |
generated by the command above. |
923 |
|
924 |
=head3 Why does C<ls> no longer have coloured output? |
925 |
|
926 |
The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
927 |
decide whether a terminal has colour, but uses its own configuration |
928 |
file. Needless to say, C<rxvt-unicode> is not in its default file (among |
929 |
with most other terminals supporting colour). Either add: |
930 |
|
931 |
TERM rxvt-unicode |
932 |
|
933 |
to C</etc/DIR_COLORS> or simply add: |
934 |
|
935 |
alias ls='ls --color=auto' |
936 |
|
937 |
to your C<.profile> or C<.bashrc>. |
938 |
|
939 |
=head3 Why doesn't vim/emacs etc. use the 88 colour mode? |
940 |
|
941 |
See next entry. |
942 |
|
943 |
=head3 Why doesn't vim/emacs etc. make use of italic? |
944 |
|
945 |
See next entry. |
946 |
|
947 |
=head3 Why are the secondary screen-related options not working properly? |
948 |
|
949 |
Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
950 |
distributions (most notably Debian GNU/Linux) break rxvt-unicode |
951 |
by setting C<TERM> to C<rxvt>, which doesn't have these extra |
952 |
features. Unfortunately, some of these (most notably, again, Debian |
953 |
GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
954 |
file, so you will need to install it on your own (See the question B<When |
955 |
I log-in to another system it tells me about missing terminfo data?> on |
956 |
how to do this). |
957 |
|
958 |
|
959 |
=head2 Encoding / Locale / Input Method Issues |
960 |
|
961 |
=head3 Rxvt-unicode does not seem to understand the selected encoding? |
962 |
|
963 |
See next entry. |
964 |
|
965 |
=head3 Unicode does not seem to work? |
966 |
|
967 |
If you encounter strange problems like typing an accented character but |
968 |
getting two unrelated other characters or similar, or if program output is |
969 |
subtly garbled, then you should check your locale settings. |
970 |
|
971 |
Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
972 |
programs running in it. Often rxvt-unicode is started in the C<C> locale, |
973 |
while the login script running within the rxvt-unicode window changes the |
974 |
locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is |
975 |
not going to work, and is the most common cause for problems. |
976 |
|
977 |
The best thing is to fix your startup environment, as you will likely run |
978 |
into other problems. If nothing works you can try this in your .profile. |
979 |
|
980 |
printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too |
981 |
|
982 |
If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
983 |
supported on your systems. Some systems have a C<locale> command which |
984 |
displays this (also, C<perl -e0> can be used to check locale settings, as |
985 |
it will complain loudly if it cannot set the locale). If it displays something |
986 |
like: |
987 |
|
988 |
locale: Cannot set LC_CTYPE to default locale: ... |
989 |
|
990 |
Then the locale you specified is not supported on your system. |
991 |
|
992 |
If nothing works and you are sure that everything is set correctly then |
993 |
you will need to remember a little known fact: Some programs just don't |
994 |
support locales :( |
995 |
|
996 |
=head3 How does rxvt-unicode determine the encoding to use? |
997 |
|
998 |
See next entry. |
999 |
|
1000 |
=head3 Is there an option to switch encodings? |
1001 |
|
1002 |
Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
1003 |
specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
1004 |
UTF-8 or any other encodings with respect to terminal I/O. |
1005 |
|
1006 |
The reasons is that there exists a perfectly fine mechanism for selecting |
1007 |
the encoding, doing I/O and (most important) communicating this to all |
1008 |
applications so everybody agrees on character properties such as width |
1009 |
and code number. This mechanism is the I<locale>. Applications not using |
1010 |
that info will have problems (for example, C<xterm> gets the width of |
1011 |
characters wrong as it uses its own, locale-independent table under all |
1012 |
locales). |
1013 |
|
1014 |
Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
1015 |
programs doing the same (that is, most) will automatically agree in the |
1016 |
interpretation of characters. |
1017 |
|
1018 |
Unfortunately, there is no system-independent way to select locales, nor |
1019 |
is there a standard on how locale specifiers will look like. |
1020 |
|
1021 |
On most systems, the content of the C<LC_CTYPE> environment variable |
1022 |
contains an arbitrary string which corresponds to an already-installed |
1023 |
locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>, |
1024 |
C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
1025 |
(i.e. C<de> or C<german>) are also common. |
1026 |
|
1027 |
Rxvt-unicode ignores all other locale categories, and except for |
1028 |
the encoding, ignores country or language-specific settings, |
1029 |
i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
1030 |
rxvt-unicode. |
1031 |
|
1032 |
If you want to use a specific encoding you have to make sure you start |
1033 |
rxvt-unicode with the correct C<LC_CTYPE> category. |
1034 |
|
1035 |
=head3 Can I switch locales at runtime? |
1036 |
|
1037 |
Yes, using an escape sequence. Try something like this, which sets |
1038 |
rxvt-unicode's idea of C<LC_CTYPE>. |
1039 |
|
1040 |
printf '\33]701;%s\007' ja_JP.SJIS |
1041 |
|
1042 |
See also the previous answer. |
1043 |
|
1044 |
Sometimes this capability is rather handy when you want to work in |
1045 |
one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it |
1046 |
(e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
1047 |
first switches to a locale supported by xjdic and back later: |
1048 |
|
1049 |
printf '\33]701;%s\007' ja_JP.SJIS |
1050 |
xjdic -js |
1051 |
printf '\33]701;%s\007' de_DE.UTF-8 |
1052 |
|
1053 |
You can also use xterm's C<luit> program, which usually works fine, except |
1054 |
for some locales where character width differs between program- and |
1055 |
rxvt-unicode-locales. |
1056 |
|
1057 |
=head3 I have problems getting my input method working. |
1058 |
|
1059 |
Try a search engine, as this is slightly different for every input method server. |
1060 |
|
1061 |
Here is a checklist: |
1062 |
|
1063 |
=over 4 |
1064 |
|
1065 |
=item - Make sure your locale I<and> the imLocale are supported on your OS. |
1066 |
|
1067 |
Try C<locale -a> or check the documentation for your OS. |
1068 |
|
1069 |
=item - Make sure your locale or imLocale matches a locale supported by your XIM. |
1070 |
|
1071 |
For example, B<kinput2> does not support UTF-8 locales, you should use |
1072 |
C<ja_JP.EUC-JP> or equivalent. |
1073 |
|
1074 |
=item - Make sure your XIM server is actually running. |
1075 |
|
1076 |
=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode. |
1077 |
|
1078 |
When you want to use e.g. B<kinput2>, it must be set to |
1079 |
C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input |
1080 |
method servers are running with this command: |
1081 |
|
1082 |
xprop -root XIM_SERVERS |
1083 |
|
1084 |
=item |
1085 |
|
1086 |
=back |
1087 |
|
1088 |
=head3 My input method wants <some encoding> but I want UTF-8, what can I do? |
1089 |
|
1090 |
You can specify separate locales for the input method and the rest of the |
1091 |
terminal, using the resource C<imlocale>: |
1092 |
|
1093 |
URxvt.imlocale: ja_JP.EUC-JP |
1094 |
|
1095 |
Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
1096 |
use your input method. Please note, however, that, depending on your Xlib |
1097 |
version, you may not be able to input characters outside C<EUC-JP> in a |
1098 |
normal way then, as your input method limits you. |
1099 |
|
1100 |
=head3 Rxvt-unicode crashes when the X Input Method changes or exits. |
1101 |
|
1102 |
Unfortunately, this is unavoidable, as the XIM protocol is racy by |
1103 |
design. Applications can avoid some crashes at the expense of memory |
1104 |
leaks, and Input Methods can avoid some crashes by careful ordering at |
1105 |
exit time. B<kinput2> (and derived input methods) generally succeeds, |
1106 |
while B<SCIM> (or similar input methods) fails. In the end, however, |
1107 |
crashes cannot be completely avoided even if both sides cooperate. |
1108 |
|
1109 |
So the only workaround is not to kill your Input Method Servers. |
1110 |
|
1111 |
|
1112 |
=head2 Operating Systems / Package Maintaining |
1113 |
|
1114 |
=head3 I am using Debian GNU/Linux and have a problem... |
1115 |
|
1116 |
The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
1117 |
patches that considerably change the behaviour of rxvt-unicode (but |
1118 |
unfortunately this notice has been removed). Before reporting a bug to |
1119 |
the original rxvt-unicode author please download and install the genuine |
1120 |
version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
1121 |
the problem. If you cannot, chances are that the problems are specific to |
1122 |
Debian GNU/Linux, in which case it should be reported via the Debian Bug |
1123 |
Tracking System (use C<reportbug> to report the bug). |
1124 |
|
1125 |
For other problems that also affect the Debian package, you can and |
1126 |
probably should use the Debian BTS, too, because, after all, it's also a |
1127 |
bug in the Debian version and it serves as a reminder for other users that |
1128 |
might encounter the same issue. |
1129 |
|
1130 |
=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1131 |
|
1132 |
You should build one binary with the default options. F<configure> |
1133 |
now enables most useful options, and the trend goes to making them |
1134 |
runtime-switchable, too, so there is usually no drawback to enabling them, |
1135 |
except higher disk and possibly memory usage. The perl interpreter should |
1136 |
be enabled, as important functionality (menus, selection, likely more in |
1137 |
the future) depends on it. |
1138 |
|
1139 |
You should not overwrite the C<perl-ext-common> and C<perl-ext> resources |
1140 |
system-wide (except maybe with C<defaults>). This will result in useful |
1141 |
behaviour. If your distribution aims at low memory, add an empty |
1142 |
C<perl-ext-common> resource to the app-defaults file. This will keep the |
1143 |
perl interpreter disabled until the user enables it. |
1144 |
|
1145 |
If you can/want build more binaries, I recommend building a minimal |
1146 |
one with C<--disable-everything> (very useful) and a maximal one with |
1147 |
C<--enable-everything> (less useful, it will be very big due to a lot of |
1148 |
encodings built-in that increase download times and are rarely used). |
1149 |
|
1150 |
=head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
1151 |
|
1152 |
It should be, starting with release 7.1. You are encouraged to properly |
1153 |
install urxvt with privileges necessary for your OS now. |
1154 |
|
1155 |
When rxvt-unicode detects that it runs setuid or setgid, it will fork |
1156 |
into a helper process for privileged operations (pty handling on some |
1157 |
systems, utmp/wtmp/lastlog handling on others) and drop privileges |
1158 |
immediately. This is much safer than most other terminals that keep |
1159 |
privileges while running (but is more relevant to urxvt, as it contains |
1160 |
things as perl interpreters, which might be "helpful" to attackers). |
1161 |
|
1162 |
This forking is done as the very first within main(), which is very early |
1163 |
and reduces possible bugs to initialisation code run before main(), or |
1164 |
things like the dynamic loader of your system, which should result in very |
1165 |
little risk. |
1166 |
|
1167 |
=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1168 |
|
1169 |
Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
1170 |
in your compile environment, or an implementation that implements it, |
1171 |
whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
1172 |
B<wchar_t> is represented as unicode. |
1173 |
|
1174 |
As you might have guessed, FreeBSD does neither define this symbol nor |
1175 |
does it support it. Instead, it uses its own internal representation of |
1176 |
B<wchar_t>. This is, of course, completely fine with respect to standards. |
1177 |
|
1178 |
However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
1179 |
C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>). |
1180 |
|
1181 |
C<__STDC_ISO_10646__> is the only sane way to support multi-language |
1182 |
apps in an OS, as using a locale-dependent (and non-standardized) |
1183 |
representation of B<wchar_t> makes it impossible to convert between |
1184 |
B<wchar_t> (as used by X11 and your applications) and any other encoding |
1185 |
without implementing OS-specific-wrappers for each and every locale. There |
1186 |
simply are no APIs to convert B<wchar_t> into anything except the current |
1187 |
locale encoding. |
1188 |
|
1189 |
Some applications (such as the formidable B<mlterm>) work around this |
1190 |
by carrying their own replacement functions for character set handling |
1191 |
with them, and either implementing OS-dependent hacks or doing multiple |
1192 |
conversions (which is slow and unreliable in case the OS implements |
1193 |
encodings slightly different than the terminal emulator). |
1194 |
|
1195 |
The rxvt-unicode author insists that the right way to fix this is in the |
1196 |
system libraries once and for all, instead of forcing every app to carry |
1197 |
complete replacements for them :) |
1198 |
|
1199 |
=head3 How can I use rxvt-unicode under cygwin? |
1200 |
|
1201 |
rxvt-unicode should compile and run out of the box on cygwin, using |
1202 |
the X11 libraries that come with cygwin. libW11 emulation is no |
1203 |
longer supported (and makes no sense, either, as it only supported a |
1204 |
single font). I recommend starting the X-server in C<-multiwindow> or |
1205 |
C<-rootless> mode instead, which will result in similar look&feel as the |
1206 |
old libW11 emulation. |
1207 |
|
1208 |
At the time of this writing, cygwin didn't seem to support any multi-byte |
1209 |
encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
1210 |
to 8-bit encodings. |
1211 |
|
1212 |
=head3 Character widths are not correct. |
1213 |
|
1214 |
urxvt uses the system wcwidth function to know the information about |
1215 |
the width of characters, so on systems with incorrect locale data you |
1216 |
will likely get bad results. Two notorious examples are Solaris 9, |
1217 |
where single-width characters like U+2514 are reported as double-width, |
1218 |
and Darwin 8, where combining chars are reported having width 1. |
1219 |
|
1220 |
The solution is to upgrade your system or switch to a better one. A |
1221 |
possibly working workaround is to use a wcwidth implementation like |
1222 |
|
1223 |
http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
1224 |
|
1225 |
=head1 RXVT-UNICODE TECHNICAL REFERENCE |
1226 |
|
1227 |
The rest of this document describes various technical aspects of |
1228 |
B<rxvt-unicode>. First the description of supported command sequences, |
1229 |
followed by pixmap support and last by a description of all features |
1230 |
selectable at C<configure> time. |
1231 |
|
1232 |
=head2 Definitions |
1233 |
|
1234 |
=over 4 |
1235 |
|
1236 |
=item B<< C<c> >> |
1237 |
|
1238 |
The literal character c. |
1239 |
|
1240 |
=item B<< C<C> >> |
1241 |
|
1242 |
A single (required) character. |
1243 |
|
1244 |
=item B<< C<Ps> >> |
1245 |
|
1246 |
A single (usually optional) numeric parameter, composed of one or more |
1247 |
digits. |
1248 |
|
1249 |
=item B<< C<Pm> >> |
1250 |
|
1251 |
A multiple numeric parameter composed of any number of single numeric |
1252 |
parameters, separated by C<;> character(s). |
1253 |
|
1254 |
=item B<< C<Pt> >> |
1255 |
|
1256 |
A text parameter composed of printable characters. |
1257 |
|
1258 |
=back |
1259 |
|
1260 |
=head2 Values |
1261 |
|
1262 |
=over 4 |
1263 |
|
1264 |
=item B<< C<ENQ> >> |
1265 |
|
1266 |
Enquiry (Ctrl-E) = Send Device Attributes (DA) |
1267 |
request attributes from terminal. See B<< C<ESC [ Ps c> >>. |
1268 |
|
1269 |
=item B<< C<BEL> >> |
1270 |
|
1271 |
Bell (Ctrl-G) |
1272 |
|
1273 |
=item B<< C<BS> >> |
1274 |
|
1275 |
Backspace (Ctrl-H) |
1276 |
|
1277 |
=item B<< C<TAB> >> |
1278 |
|
1279 |
Horizontal Tab (HT) (Ctrl-I) |
1280 |
|
1281 |
=item B<< C<LF> >> |
1282 |
|
1283 |
Line Feed or New Line (NL) (Ctrl-J) |
1284 |
|
1285 |
=item B<< C<VT> >> |
1286 |
|
1287 |
Vertical Tab (Ctrl-K) same as B<< C<LF> >> |
1288 |
|
1289 |
=item B<< C<FF> >> |
1290 |
|
1291 |
Form Feed or New Page (NP) (Ctrl-L) same as B<< C<LF> >> |
1292 |
|
1293 |
=item B<< C<CR> >> |
1294 |
|
1295 |
Carriage Return (Ctrl-M) |
1296 |
|
1297 |
=item B<< C<SO> >> |
1298 |
|
1299 |
Shift Out (Ctrl-N), invokes the G1 character set. |
1300 |
Switch to Alternate Character Set |
1301 |
|
1302 |
=item B<< C<SI> >> |
1303 |
|
1304 |
Shift In (Ctrl-O), invokes the G0 character set (the default). |
1305 |
Switch to Standard Character Set |
1306 |
|
1307 |
=item B<< C<SPC> >> |
1308 |
|
1309 |
Space Character |
1310 |
|
1311 |
=back |
1312 |
|
1313 |
=head2 Escape Sequences |
1314 |
|
1315 |
=over 4 |
1316 |
|
1317 |
=item B<< C<ESC # 8> >> |
1318 |
|
1319 |
DEC Screen Alignment Test (DECALN) |
1320 |
|
1321 |
=item B<< C<ESC 7> >> |
1322 |
|
1323 |
Save Cursor (SC) |
1324 |
|
1325 |
=item B<< C<ESC 8> >> |
1326 |
|
1327 |
Restore Cursor |
1328 |
|
1329 |
=item B<< C<ESC => >> |
1330 |
|
1331 |
Application Keypad (SMKX). See also next sequence. |
1332 |
|
1333 |
=item B<<< C<< ESC > >> >>> |
1334 |
|
1335 |
Normal Keypad (RMKX) |
1336 |
|
1337 |
B<Note:> If the numeric keypad is activated, eg, B<Num_Lock> has been |
1338 |
pressed, numbers or control functions are generated by the numeric keypad |
1339 |
(see Key Codes). |
1340 |
|
1341 |
=item B<< C<ESC D> >> |
1342 |
|
1343 |
Index (IND) |
1344 |
|
1345 |
=item B<< C<ESC E> >> |
1346 |
|
1347 |
Next Line (NEL) |
1348 |
|
1349 |
=item B<< C<ESC H> >> |
1350 |
|
1351 |
Tab Set (HTS) |
1352 |
|
1353 |
=item B<< C<ESC M> >> |
1354 |
|
1355 |
Reverse Index (RI) |
1356 |
|
1357 |
=item B<< C<ESC N> >> |
1358 |
|
1359 |
Single Shift Select of G2 Character Set (SS2): affects next character |
1360 |
only I<unimplemented> |
1361 |
|
1362 |
=item B<< C<ESC O> >> |
1363 |
|
1364 |
Single Shift Select of G3 Character Set (SS3): affects next character |
1365 |
only I<unimplemented> |
1366 |
|
1367 |
=item B<< C<ESC Z> >> |
1368 |
|
1369 |
Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option> |
1370 |
|
1371 |
=item B<< C<ESC c> >> |
1372 |
|
1373 |
Full reset (RIS) |
1374 |
|
1375 |
=item B<< C<ESC n> >> |
1376 |
|
1377 |
Invoke the G2 Character Set (LS2) |
1378 |
|
1379 |
=item B<< C<ESC o> >> |
1380 |
|
1381 |
Invoke the G3 Character Set (LS3) |
1382 |
|
1383 |
=item B<< C<ESC ( C> >> |
1384 |
|
1385 |
Designate G0 Character Set (ISO 2022), see below for values of C<C>. |
1386 |
|
1387 |
=item B<< C<ESC ) C> >> |
1388 |
|
1389 |
Designate G1 Character Set (ISO 2022), see below for values of C<C>. |
1390 |
|
1391 |
=item B<< C<ESC * C> >> |
1392 |
|
1393 |
Designate G2 Character Set (ISO 2022), see below for values of C<C>. |
1394 |
|
1395 |
=item B<< C<ESC + C> >> |
1396 |
|
1397 |
Designate G3 Character Set (ISO 2022), see below for values of C<C>. |
1398 |
|
1399 |
=item B<< C<ESC $ C> >> |
1400 |
|
1401 |
Designate Kanji Character Set |
1402 |
|
1403 |
Where B<< C<C> >> is one of: |
1404 |
|
1405 |
=begin table |
1406 |
|
1407 |
C = C<0> DEC Special Character and Line Drawing Set |
1408 |
C = C<A> United Kingdom (UK) |
1409 |
C = C<B> United States (USASCII) |
1410 |
C = C<< < >> Multinational character set I<unimplemented> |
1411 |
C = C<5> Finnish character set I<unimplemented> |
1412 |
C = C<C> Finnish character set I<unimplemented> |
1413 |
C = C<K> German character set I<unimplemented> |
1414 |
|
1415 |
=end table |
1416 |
|
1417 |
=back |
1418 |
|
1419 |
X<CSI> |
1420 |
|
1421 |
=head2 CSI (Command Sequence Introducer) Sequences |
1422 |
|
1423 |
=over 4 |
1424 |
|
1425 |
=item B<< C<ESC [ Ps @> >> |
1426 |
|
1427 |
Insert B<< C<Ps> >> (Blank) Character(s) [default: 1] (ICH)X<ESCOBPsA> |
1428 |
|
1429 |
=item B<< C<ESC [ Ps A> >> |
1430 |
|
1431 |
Cursor Up B<< C<Ps> >> Times [default: 1] (CUU) |
1432 |
|
1433 |
=item B<< C<ESC [ Ps B> >> |
1434 |
|
1435 |
Cursor Down B<< C<Ps> >> Times [default: 1] (CUD)X<ESCOBPsC> |
1436 |
|
1437 |
=item B<< C<ESC [ Ps C> >> |
1438 |
|
1439 |
Cursor Forward B<< C<Ps> >> Times [default: 1] (CUF) |
1440 |
|
1441 |
=item B<< C<ESC [ Ps D> >> |
1442 |
|
1443 |
Cursor Backward B<< C<Ps> >> Times [default: 1] (CUB) |
1444 |
|
1445 |
=item B<< C<ESC [ Ps E> >> |
1446 |
|
1447 |
Cursor Down B<< C<Ps> >> Times [default: 1] and to first column |
1448 |
|
1449 |
=item B<< C<ESC [ Ps F> >> |
1450 |
|
1451 |
Cursor Up B<< C<Ps> >> Times [default: 1] and to first columnX<ESCOBPsG> |
1452 |
|
1453 |
=item B<< C<ESC [ Ps G> >> |
1454 |
|
1455 |
Cursor to Column B<< C<Ps> >> (HPA) |
1456 |
|
1457 |
=item B<< C<ESC [ Ps;Ps H> >> |
1458 |
|
1459 |
Cursor Position [row;column] [default: 1;1] (CUP) |
1460 |
|
1461 |
=item B<< C<ESC [ Ps I> >> |
1462 |
|
1463 |
Move forward B<< C<Ps> >> tab stops [default: 1] |
1464 |
|
1465 |
=item B<< C<ESC [ Ps J> >> |
1466 |
|
1467 |
Erase in Display (ED) |
1468 |
|
1469 |
=begin table |
1470 |
|
1471 |
B<< C<Ps = 0> >> Clear Below (default) |
1472 |
B<< C<Ps = 1> >> Clear Above |
1473 |
B<< C<Ps = 2> >> Clear All |
1474 |
|
1475 |
=end table |
1476 |
|
1477 |
=item B<< C<ESC [ Ps K> >> |
1478 |
|
1479 |
Erase in Line (EL) |
1480 |
|
1481 |
=begin table |
1482 |
|
1483 |
B<< C<Ps = 0> >> Clear to Right (default) |
1484 |
B<< C<Ps = 1> >> Clear to Left |
1485 |
B<< C<Ps = 2> >> Clear All |
1486 |
B<< C<Ps = 3> >> Like Ps = 0, but is ignored when wrapped |
1487 |
(@@RXVT_NAME@@ extension) |
1488 |
|
1489 |
=end table |
1490 |
|
1491 |
=item B<< C<ESC [ Ps L> >> |
1492 |
|
1493 |
Insert B<< C<Ps> >> Line(s) [default: 1] (IL) |
1494 |
|
1495 |
=item B<< C<ESC [ Ps M> >> |
1496 |
|
1497 |
Delete B<< C<Ps> >> Line(s) [default: 1] (DL) |
1498 |
|
1499 |
=item B<< C<ESC [ Ps P> >> |
1500 |
|
1501 |
Delete B<< C<Ps> >> Character(s) [default: 1] (DCH) |
1502 |
|
1503 |
=item B<< C<ESC [ Ps;Ps;Ps;Ps;Ps T> >> |
1504 |
|
1505 |
Initiate . I<unimplemented> Parameters are |
1506 |
[func;startx;starty;firstrow;lastrow]. |
1507 |
|
1508 |
=item B<< C<ESC [ Ps W> >> |
1509 |
|
1510 |
Tabulator functions |
1511 |
|
1512 |
=begin table |
1513 |
|
1514 |
B<< C<Ps = 0> >> Tab Set (HTS) |
1515 |
B<< C<Ps = 2> >> Tab Clear (TBC), Clear Current Column (default) |
1516 |
B<< C<Ps = 5> >> Tab Clear (TBC), Clear All |
1517 |
|
1518 |
=end table |
1519 |
|
1520 |
=item B<< C<ESC [ Ps X> >> |
1521 |
|
1522 |
Erase B<< C<Ps> >> Character(s) [default: 1] (ECH) |
1523 |
|
1524 |
=item B<< C<ESC [ Ps Z> >> |
1525 |
|
1526 |
Move backward B<< C<Ps> >> [default: 1] tab stops |
1527 |
|
1528 |
=item B<< C<ESC [ Ps '> >> |
1529 |
|
1530 |
See B<< C<ESC [ Ps G> >> |
1531 |
|
1532 |
=item B<< C<ESC [ Ps a> >> |
1533 |
|
1534 |
See B<< C<ESC [ Ps C> >> |
1535 |
|
1536 |
=item B<< C<ESC [ Ps c> >> |
1537 |
|
1538 |
Send Device Attributes (DA) |
1539 |
B<< C<Ps = 0> >> (or omitted): request attributes from terminal |
1540 |
returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video |
1541 |
Option'') |
1542 |
|
1543 |
=item B<< C<ESC [ Ps d> >> |
1544 |
|
1545 |
Cursor to Line B<< C<Ps> >> (VPA) |
1546 |
|
1547 |
=item B<< C<ESC [ Ps e> >> |
1548 |
|
1549 |
See B<< C<ESC [ Ps A> >> |
1550 |
|
1551 |
=item B<< C<ESC [ Ps;Ps f> >> |
1552 |
|
1553 |
Horizontal and Vertical Position [row;column] (HVP) [default: 1;1] |
1554 |
|
1555 |
=item B<< C<ESC [ Ps g> >> |
1556 |
|
1557 |
Tab Clear (TBC) |
1558 |
|
1559 |
=begin table |
1560 |
|
1561 |
B<< C<Ps = 0> >> Clear Current Column (default) |
1562 |
B<< C<Ps = 3> >> Clear All (TBC) |
1563 |
|
1564 |
=end table |
1565 |
|
1566 |
=item B<< C<ESC [ Pm h> >> |
1567 |
|
1568 |
Set Mode (SM). See B<< C<ESC [ Pm l> >> sequence for description of C<Pm>. |
1569 |
|
1570 |
=item B<< C<ESC [ Ps i> >> |
1571 |
|
1572 |
Printing. See also the C<print-pipe> resource. |
1573 |
|
1574 |
=begin table |
1575 |
|
1576 |
B<< C<Ps = 0> >> print screen (MC0) |
1577 |
B<< C<Ps = 4> >> disable transparent print mode (MC4) |
1578 |
B<< C<Ps = 5> >> enable transparent print mode (MC5) |
1579 |
|
1580 |
=end table |
1581 |
|
1582 |
=item B<< C<ESC [ Pm l> >> |
1583 |
|
1584 |
Reset Mode (RM) |
1585 |
|
1586 |
=over 4 |
1587 |
|
1588 |
=item B<< C<Ps = 4> >> |
1589 |
|
1590 |
=begin table |
1591 |
|
1592 |
B<< C<h> >> Insert Mode (SMIR) |
1593 |
B<< C<l> >> Replace Mode (RMIR) |
1594 |
|
1595 |
=end table |
1596 |
|
1597 |
=item B<< C<Ps = 20> >> (partially implemented) |
1598 |
|
1599 |
=begin table |
1600 |
|
1601 |
B<< C<h> >> Automatic Newline (LNM) |
1602 |
B<< C<l> >> Normal Linefeed (LNM) |
1603 |
|
1604 |
=end table |
1605 |
|
1606 |
=back |
1607 |
|
1608 |
=item B<< C<ESC [ Pm m> >> |
1609 |
|
1610 |
Character Attributes (SGR) |
1611 |
|
1612 |
=begin table |
1613 |
|
1614 |
B<< C<Ps = 0> >> Normal (default) |
1615 |
B<< C<Ps = 1 / 21> >> On / Off Bold (bright fg) |
1616 |
B<< C<Ps = 3 / 23> >> On / Off Italic |
1617 |
B<< C<Ps = 4 / 24> >> On / Off Underline |
1618 |
B<< C<Ps = 5 / 25> >> On / Off Slow Blink (bright bg) |
1619 |
B<< C<Ps = 6 / 26> >> On / Off Rapid Blink (bright bg) |
1620 |
B<< C<Ps = 7 / 27> >> On / Off Inverse |
1621 |
B<< C<Ps = 8 / 27> >> On / Off Invisible (NYI) |
1622 |
B<< C<Ps = 30 / 40> >> fg/bg Black |
1623 |
B<< C<Ps = 31 / 41> >> fg/bg Red |
1624 |
B<< C<Ps = 32 / 42> >> fg/bg Green |
1625 |
B<< C<Ps = 33 / 43> >> fg/bg Yellow |
1626 |
B<< C<Ps = 34 / 44> >> fg/bg Blue |
1627 |
B<< C<Ps = 35 / 45> >> fg/bg Magenta |
1628 |
B<< C<Ps = 36 / 46> >> fg/bg Cyan |
1629 |
B<< C<Ps = 38;5 / 48;5> >> set fg/bg to colour #m (ISO 8613-6) |
1630 |
B<< C<Ps = 37 / 47> >> fg/bg White |
1631 |
B<< C<Ps = 39 / 49> >> fg/bg Default |
1632 |
B<< C<Ps = 90 / 100> >> fg/bg Bright Black |
1633 |
B<< C<Ps = 91 / 101> >> fg/bg Bright Red |
1634 |
B<< C<Ps = 92 / 102> >> fg/bg Bright Green |
1635 |
B<< C<Ps = 93 / 103> >> fg/bg Bright Yellow |
1636 |
B<< C<Ps = 94 / 104> >> fg/bg Bright Blue |
1637 |
B<< C<Ps = 95 / 105> >> fg/bg Bright Magenta |
1638 |
B<< C<Ps = 96 / 106> >> fg/bg Bright Cyan |
1639 |
B<< C<Ps = 97 / 107> >> fg/bg Bright White |
1640 |
B<< C<Ps = 99 / 109> >> fg/bg Bright Default |
1641 |
|
1642 |
=end table |
1643 |
|
1644 |
=item B<< C<ESC [ Ps n> >> |
1645 |
|
1646 |
Device Status Report (DSR) |
1647 |
|
1648 |
=begin table |
1649 |
|
1650 |
B<< C<Ps = 5> >> Status Report B<< C<ESC [ 0 n> >> (``OK'') |
1651 |
B<< C<Ps = 6> >> Report Cursor Position (CPR) [row;column] as B<< C<ESC [ r ; c R> >> |
1652 |
B<< C<Ps = 7> >> Request Display Name |
1653 |
B<< C<Ps = 8> >> Request Version Number (place in window title) |
1654 |
|
1655 |
=end table |
1656 |
|
1657 |
=item B<< C<ESC [ Ps;Ps r> >> |
1658 |
|
1659 |
Set Scrolling Region [top;bottom] |
1660 |
[default: full size of window] (CSR) |
1661 |
|
1662 |
=item B<< C<ESC [ s> >> |
1663 |
|
1664 |
Save Cursor (SC) |
1665 |
|
1666 |
=item B<< C<ESC [ Ps;Pt t> >> |
1667 |
|
1668 |
Window Operations |
1669 |
|
1670 |
=begin table |
1671 |
|
1672 |
B<< C<Ps = 1> >> Deiconify (map) window |
1673 |
B<< C<Ps = 2> >> Iconify window |
1674 |
B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X|Y) |
1675 |
B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels |
1676 |
B<< C<Ps = 5> >> Raise window |
1677 |
B<< C<Ps = 6> >> Lower window |
1678 |
B<< C<Ps = 7> >> Refresh screen once |
1679 |
B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns |
1680 |
B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>) |
1681 |
B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>) |
1682 |
B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>) |
1683 |
B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>) |
1684 |
B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9> |
1685 |
B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>) |
1686 |
B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>) |
1687 |
B<< C<Ps = 24..> >> Set window height to C<Ps> rows |
1688 |
|
1689 |
=end table |
1690 |
|
1691 |
=item B<< C<ESC [ u> >> |
1692 |
|
1693 |
Restore Cursor |
1694 |
|
1695 |
=item B<< C<ESC [ Ps x> >> |
1696 |
|
1697 |
Request Terminal Parameters (DECREQTPARM) |
1698 |
|
1699 |
=back |
1700 |
|
1701 |
X<PrivateModes> |
1702 |
|
1703 |
=head2 DEC Private Modes |
1704 |
|
1705 |
=over 4 |
1706 |
|
1707 |
=item B<< C<ESC [ ? Pm h> >> |
1708 |
|
1709 |
DEC Private Mode Set (DECSET) |
1710 |
|
1711 |
=item B<< C<ESC [ ? Pm l> >> |
1712 |
|
1713 |
DEC Private Mode Reset (DECRST) |
1714 |
|
1715 |
=item B<< C<ESC [ ? Pm r> >> |
1716 |
|
1717 |
Restore previously saved DEC Private Mode Values. |
1718 |
|
1719 |
=item B<< C<ESC [ ? Pm s> >> |
1720 |
|
1721 |
Save DEC Private Mode Values. |
1722 |
|
1723 |
=item B<< C<ESC [ ? Pm t> >> |
1724 |
|
1725 |
Toggle DEC Private Mode Values (rxvt extension). I<where> |
1726 |
|
1727 |
=over 4 |
1728 |
|
1729 |
=item B<< C<Pm = 1> >> (DECCKM) |
1730 |
|
1731 |
=begin table |
1732 |
|
1733 |
B<< C<h> >> Application Cursor Keys |
1734 |
B<< C<l> >> Normal Cursor Keys |
1735 |
|
1736 |
=end table |
1737 |
|
1738 |
=item B<< C<Pm = 2> >> (ANSI/VT52 mode) |
1739 |
|
1740 |
=begin table |
1741 |
|
1742 |
B<< C<h> >> Enter VT52 mode |
1743 |
B<< C<l> >> Enter VT52 mode |
1744 |
|
1745 |
=end table |
1746 |
|
1747 |
=item B<< C<Pm = 3> >> |
1748 |
|
1749 |
=begin table |
1750 |
|
1751 |
B<< C<h> >> 132 Column Mode (DECCOLM) |
1752 |
B<< C<l> >> 80 Column Mode (DECCOLM) |
1753 |
|
1754 |
=end table |
1755 |
|
1756 |
=item B<< C<Pm = 4> >> |
1757 |
|
1758 |
=begin table |
1759 |
|
1760 |
B<< C<h> >> Smooth (Slow) Scroll (DECSCLM) |
1761 |
B<< C<l> >> Jump (Fast) Scroll (DECSCLM) |
1762 |
|
1763 |
=end table |
1764 |
|
1765 |
=item B<< C<Pm = 5> >> |
1766 |
|
1767 |
=begin table |
1768 |
|
1769 |
B<< C<h> >> Reverse Video (DECSCNM) |
1770 |
B<< C<l> >> Normal Video (DECSCNM) |
1771 |
|
1772 |
=end table |
1773 |
|
1774 |
=item B<< C<Pm = 6> >> |
1775 |
|
1776 |
=begin table |
1777 |
|
1778 |
B<< C<h> >> Origin Mode (DECOM) |
1779 |
B<< C<l> >> Normal Cursor Mode (DECOM) |
1780 |
|
1781 |
=end table |
1782 |
|
1783 |
=item B<< C<Pm = 7> >> |
1784 |
|
1785 |
=begin table |
1786 |
|
1787 |
B<< C<h> >> Wraparound Mode (DECAWM) |
1788 |
B<< C<l> >> No Wraparound Mode (DECAWM) |
1789 |
|
1790 |
=end table |
1791 |
|
1792 |
=item B<< C<Pm = 8> >> I<unimplemented> |
1793 |
|
1794 |
=begin table |
1795 |
|
1796 |
B<< C<h> >> Auto-repeat Keys (DECARM) |
1797 |
B<< C<l> >> No Auto-repeat Keys (DECARM) |
1798 |
|
1799 |
=end table |
1800 |
|
1801 |
=item B<< C<Pm = 9> >> X10 XTerm |
1802 |
|
1803 |
=begin table |
1804 |
|
1805 |
B<< C<h> >> Send Mouse X & Y on button press. |
1806 |
B<< C<l> >> No mouse reporting. |
1807 |
|
1808 |
=end table |
1809 |
|
1810 |
=item B<< C<Pm = 25> >> |
1811 |
|
1812 |
=begin table |
1813 |
|
1814 |
B<< C<h> >> Visible cursor {cnorm/cvvis} |
1815 |
B<< C<l> >> Invisible cursor {civis} |
1816 |
|
1817 |
=end table |
1818 |
|
1819 |
=item B<< C<Pm = 30> >> |
1820 |
|
1821 |
=begin table |
1822 |
|
1823 |
B<< C<h> >> scrollBar visible |
1824 |
B<< C<l> >> scrollBar invisible |
1825 |
|
1826 |
=end table |
1827 |
|
1828 |
=item B<< C<Pm = 35> >> (B<rxvt>) |
1829 |
|
1830 |
=begin table |
1831 |
|
1832 |
B<< C<h> >> Allow XTerm Shift+key sequences |
1833 |
B<< C<l> >> Disallow XTerm Shift+key sequences |
1834 |
|
1835 |
=end table |
1836 |
|
1837 |
=item B<< C<Pm = 38> >> I<unimplemented> |
1838 |
|
1839 |
Enter Tektronix Mode (DECTEK) |
1840 |
|
1841 |
=item B<< C<Pm = 40> >> |
1842 |
|
1843 |
=begin table |
1844 |
|
1845 |
B<< C<h> >> Allow 80/132 Mode |
1846 |
B<< C<l> >> Disallow 80/132 Mode |
1847 |
|
1848 |
=end table |
1849 |
|
1850 |
=item B<< C<Pm = 44> >> I<unimplemented> |
1851 |
|
1852 |
=begin table |
1853 |
|
1854 |
B<< C<h> >> Turn On Margin Bell |
1855 |
B<< C<l> >> Turn Off Margin Bell |
1856 |
|
1857 |
=end table |
1858 |
|
1859 |
=item B<< C<Pm = 45> >> I<unimplemented> |
1860 |
|
1861 |
=begin table |
1862 |
|
1863 |
B<< C<h> >> Reverse-wraparound Mode |
1864 |
B<< C<l> >> No Reverse-wraparound Mode |
1865 |
|
1866 |
=end table |
1867 |
|
1868 |
=item B<< C<Pm = 46> >> I<unimplemented> |
1869 |
|
1870 |
=item B<< C<Pm = 47> >> |
1871 |
|
1872 |
=begin table |
1873 |
|
1874 |
B<< C<h> >> Use Alternate Screen Buffer |
1875 |
B<< C<l> >> Use Normal Screen Buffer |
1876 |
|
1877 |
=end table |
1878 |
|
1879 |
X<Priv66> |
1880 |
|
1881 |
=item B<< C<Pm = 66> >> |
1882 |
|
1883 |
=begin table |
1884 |
|
1885 |
B<< C<h> >> Application Keypad (DECKPAM/DECPAM) == C<ESC => |
1886 |
B<< C<l> >> Normal Keypad (DECKPNM/DECPNM) == C<< ESC > >> |
1887 |
|
1888 |
=end table |
1889 |
|
1890 |
=item B<< C<Pm = 67> >> |
1891 |
|
1892 |
=begin table |
1893 |
|
1894 |
B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >> |
1895 |
B<< C<l> >> Backspace key sends B<< C<DEL> >> |
1896 |
|
1897 |
=end table |
1898 |
|
1899 |
=item B<< C<Pm = 1000> >> (X11 XTerm) |
1900 |
|
1901 |
=begin table |
1902 |
|
1903 |
B<< C<h> >> Send Mouse X & Y on button press and release. |
1904 |
B<< C<l> >> No mouse reporting. |
1905 |
|
1906 |
=end table |
1907 |
|
1908 |
=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented> |
1909 |
|
1910 |
=begin table |
1911 |
|
1912 |
B<< C<h> >> Use Hilite Mouse Tracking. |
1913 |
B<< C<l> >> No mouse reporting. |
1914 |
|
1915 |
=end table |
1916 |
|
1917 |
=item B<< C<Pm = 1002> >> (X11 XTerm) |
1918 |
|
1919 |
=begin table |
1920 |
|
1921 |
B<< C<h> >> Send Mouse X & Y on button press and release, and motion with a button pressed. |
1922 |
B<< C<l> >> No mouse reporting. |
1923 |
|
1924 |
=end table |
1925 |
|
1926 |
=item B<< C<Pm = 1003> >> (X11 XTerm) |
1927 |
|
1928 |
=begin table |
1929 |
|
1930 |
B<< C<h> >> Send Mouse X & Y on button press and release, and motion. |
1931 |
B<< C<l> >> No mouse reporting. |
1932 |
|
1933 |
=end table |
1934 |
|
1935 |
=item B<< C<Pm = 1010> >> (B<rxvt>) |
1936 |
|
1937 |
=begin table |
1938 |
|
1939 |
B<< C<h> >> Don't scroll to bottom on TTY output |
1940 |
B<< C<l> >> Scroll to bottom on TTY output |
1941 |
|
1942 |
=end table |
1943 |
|
1944 |
=item B<< C<Pm = 1011> >> (B<rxvt>) |
1945 |
|
1946 |
=begin table |
1947 |
|
1948 |
B<< C<h> >> Scroll to bottom when a key is pressed |
1949 |
B<< C<l> >> Don't scroll to bottom when a key is pressed |
1950 |
|
1951 |
=end table |
1952 |
|
1953 |
=item B<< C<Pm = 1021> >> (B<rxvt>) |
1954 |
|
1955 |
=begin table |
1956 |
|
1957 |
B<< C<h> >> Bold/italic implies high intensity (see option B<-is>) |
1958 |
B<< C<l> >> Font styles have no effect on intensity (Compile styles) |
1959 |
|
1960 |
=end table |
1961 |
|
1962 |
=item B<< C<Pm = 1047> >> |
1963 |
|
1964 |
=begin table |
1965 |
|
1966 |
B<< C<h> >> Use Alternate Screen Buffer |
1967 |
B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it |
1968 |
|
1969 |
=end table |
1970 |
|
1971 |
=item B<< C<Pm = 1048> >> |
1972 |
|
1973 |
=begin table |
1974 |
|
1975 |
B<< C<h> >> Save cursor position |
1976 |
B<< C<l> >> Restore cursor position |
1977 |
|
1978 |
=end table |
1979 |
|
1980 |
=item B<< C<Pm = 1049> >> |
1981 |
|
1982 |
=begin table |
1983 |
|
1984 |
B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it |
1985 |
B<< C<l> >> Use Normal Screen Buffer |
1986 |
|
1987 |
=end table |
1988 |
|
1989 |
=item B<< C<Pm = 2004> >> |
1990 |
|
1991 |
=begin table |
1992 |
|
1993 |
B<< C<h> >> Enable bracketed paste mode - prepend / append to the pasted text the control sequences C<ESC [ 200 ~> / C<ESC [ 201 ~> |
1994 |
B<< C<l> >> Disable bracketed paste mode |
1995 |
|
1996 |
=end table |
1997 |
|
1998 |
=back |
1999 |
|
2000 |
=back |
2001 |
|
2002 |
X<XTerm> |
2003 |
|
2004 |
=head2 XTerm Operating System Commands |
2005 |
|
2006 |
=over 4 |
2007 |
|
2008 |
=item B<< C<ESC ] Ps;Pt ST> >> |
2009 |
|
2010 |
Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b, |
2011 |
0x5c), backwards compatible terminator BEL (0x07) is also accepted. any |
2012 |
B<octet> can be escaped by prefixing it with SYN (0x16, ^V). |
2013 |
|
2014 |
=begin table |
2015 |
|
2016 |
B<< C<Ps = 0> >> Change Icon Name and Window Title to B<< C<Pt> >> |
2017 |
B<< C<Ps = 1> >> Change Icon Name to B<< C<Pt> >> |
2018 |
B<< C<Ps = 2> >> Change Window Title to B<< C<Pt> >> |
2019 |
B<< C<Ps = 3> >> If B<< C<Pt> >> starts with a B<< C<?> >>, query the (STRING) property of the window and return it. If B<< C<Pt> >> contains a B<< C<=> >>, set the named property to the given value, else delete the specified property. |
2020 |
B<< C<Ps = 4> >> B<< C<Pt> >> is a semi-colon separated sequence of one or more semi-colon separated B<number>/B<name> pairs, where B<number> is an index to a colour and B<name> is the name of a colour. Each pair causes the B<number>ed colour to be changed to B<name>. Numbers 0-7 corresponds to low-intensity (normal) colours and 8-15 corresponds to high-intensity colours. 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white |
2021 |
B<< C<Ps = 10> >> Change colour of text foreground to B<< C<Pt> >> |
2022 |
B<< C<Ps = 11> >> Change colour of text background to B<< C<Pt> >> |
2023 |
B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >> |
2024 |
B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> |
2025 |
B<< C<Ps = 17> >> Change background colour of highlight characters to B<< C<Pt> >> |
2026 |
B<< C<Ps = 19> >> Change foreground colour of highlight characters to B<< C<Pt> >> |
2027 |
B<< C<Ps = 20> >> Change background pixmap parameters (see section BACKGROUND IMAGE) (Compile AfterImage). |
2028 |
B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. [deprecated, use 10] |
2029 |
B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> |
2030 |
B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>. [deprecated, use 11] |
2031 |
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> >> |
2032 |
B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> [disabled] |
2033 |
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). |
2034 |
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>. |
2035 |
B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >> |
2036 |
B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency). |
2037 |
B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >> |
2038 |
B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >> |
2039 |
B<< C<Ps = 708> >> Change colour of the border to B<< C<Pt> >> |
2040 |
B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
2041 |
B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles). |
2042 |
B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles). |
2043 |
B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles). |
2044 |
B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills). |
2045 |
B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills). |
2046 |
B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl). |
2047 |
|
2048 |
=end table |
2049 |
|
2050 |
=back |
2051 |
|
2052 |
=head1 BACKGROUND IMAGE |
2053 |
|
2054 |
For the BACKGROUND IMAGE XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> the value |
2055 |
of B<< C<Pt> >> can be the name of the background image file followed by a |
2056 |
sequence of scaling/positioning commands separated by semi-colons. The |
2057 |
scaling/positioning commands are as follows: |
2058 |
|
2059 |
=over 4 |
2060 |
|
2061 |
=item query scale/position |
2062 |
|
2063 |
B<?> |
2064 |
|
2065 |
=item change scale and position |
2066 |
|
2067 |
B<WxH+X+Y> |
2068 |
|
2069 |
B<WxH+X> (== B<WxH+X+X>) |
2070 |
|
2071 |
B<WxH> (same as B<WxH+50+50>) |
2072 |
|
2073 |
B<W+X+Y> (same as B<WxW+X+Y>) |
2074 |
|
2075 |
B<W+X> (same as B<WxW+X+X>) |
2076 |
|
2077 |
B<W> (same as B<WxW+50+50>) |
2078 |
|
2079 |
=item change position (absolute) |
2080 |
|
2081 |
B<=+X+Y> |
2082 |
|
2083 |
B<=+X> (same as B<=+X+Y>) |
2084 |
|
2085 |
=item change position (relative) |
2086 |
|
2087 |
B<+X+Y> |
2088 |
|
2089 |
B<+X> (same as B<+X+Y>) |
2090 |
|
2091 |
=item rescale (relative) |
2092 |
|
2093 |
B<Wx0> -> B<W *= (W/100)> |
2094 |
|
2095 |
B<0xH> -> B<H *= (H/100)> |
2096 |
|
2097 |
=back |
2098 |
|
2099 |
For example: |
2100 |
|
2101 |
=over 4 |
2102 |
|
2103 |
=item B<\E]20;funky.jpg\a> |
2104 |
|
2105 |
load B<funky.jpg> as a tiled image |
2106 |
|
2107 |
=item B<\E]20;mona.jpg;100\a> |
2108 |
|
2109 |
load B<mona.jpg> with a scaling of 100% |
2110 |
|
2111 |
=item B<\E]20;;200;?\a> |
2112 |
|
2113 |
rescale the current pixmap to 200% and display the image geometry in |
2114 |
the title |
2115 |
|
2116 |
=back |
2117 |
|
2118 |
X<Mouse> |
2119 |
|
2120 |
=head1 Mouse Reporting |
2121 |
|
2122 |
=over 4 |
2123 |
|
2124 |
=item B<< C<< ESC [ M <b> <x> <y> >> >> |
2125 |
|
2126 |
report mouse position |
2127 |
|
2128 |
=back |
2129 |
|
2130 |
The lower 2 bits of B<< C<< <b> >> >> indicate the button: |
2131 |
|
2132 |
=over 4 |
2133 |
|
2134 |
=item Button = B<< C<< (<b> - SPACE) & 3 >> >> |
2135 |
|
2136 |
=begin table |
2137 |
|
2138 |
0 Button1 pressed |
2139 |
1 Button2 pressed |
2140 |
2 Button3 pressed |
2141 |
3 button released (X11 mouse report) |
2142 |
|
2143 |
=end table |
2144 |
|
2145 |
=back |
2146 |
|
2147 |
The upper bits of B<< C<< <b> >> >> indicate the modifiers when the |
2148 |
button was pressed and are added together (X11 mouse report only): |
2149 |
|
2150 |
=over 4 |
2151 |
|
2152 |
=item State = B<< C<< (<b> - SPACE) & 60 >> >> |
2153 |
|
2154 |
=begin table |
2155 |
|
2156 |
4 Shift |
2157 |
8 Meta |
2158 |
16 Control |
2159 |
32 Double Click I<(rxvt extension)> |
2160 |
|
2161 |
=end table |
2162 |
|
2163 |
Col = B<< C<< <x> - SPACE >> >> |
2164 |
|
2165 |
Row = B<< C<< <y> - SPACE >> >> |
2166 |
|
2167 |
=back |
2168 |
|
2169 |
=head1 Key Codes |
2170 |
|
2171 |
X<KeyCodes> |
2172 |
|
2173 |
Note: B<Shift> + B<F1>-B<F10> generates B<F11>-B<F20> |
2174 |
|
2175 |
For the keypad, use B<Shift> to temporarily override Application-Keypad |
2176 |
setting use B<Num_Lock> to toggle Application-Keypad setting if |
2177 |
B<Num_Lock> is off, toggle Application-Keypad setting. Also note that |
2178 |
values of B<Home>, B<End>, B<Delete> may have been compiled differently on |
2179 |
your system. |
2180 |
|
2181 |
=begin table |
2182 |
|
2183 |
B<Normal> B<Shift> B<Control> B<Ctrl+Shift> |
2184 |
Tab ^I ESC [ Z ^I ESC [ Z |
2185 |
BackSpace ^H ^? ^? ^? |
2186 |
Find ESC [ 1 ~ ESC [ 1 $ ESC [ 1 ^ ESC [ 1 @ |
2187 |
Insert ESC [ 2 ~ I<paste> ESC [ 2 ^ ESC [ 2 @ |
2188 |
Execute ESC [ 3 ~ ESC [ 3 $ ESC [ 3 ^ ESC [ 3 @ |
2189 |
Select ESC [ 4 ~ ESC [ 4 $ ESC [ 4 ^ ESC [ 4 @ |
2190 |
Prior ESC [ 5 ~ I<scroll-up> ESC [ 5 ^ ESC [ 5 @ |
2191 |
Next ESC [ 6 ~ I<scroll-down> ESC [ 6 ^ ESC [ 6 @ |
2192 |
Home ESC [ 7 ~ ESC [ 7 $ ESC [ 7 ^ ESC [ 7 @ |
2193 |
End ESC [ 8 ~ ESC [ 8 $ ESC [ 8 ^ ESC [ 8 @ |
2194 |
Delete ESC [ 3 ~ ESC [ 3 $ ESC [ 3 ^ ESC [ 3 @ |
2195 |
F1 ESC [ 11 ~ ESC [ 23 ~ ESC [ 11 ^ ESC [ 23 ^ |
2196 |
F2 ESC [ 12 ~ ESC [ 24 ~ ESC [ 12 ^ ESC [ 24 ^ |
2197 |
F3 ESC [ 13 ~ ESC [ 25 ~ ESC [ 13 ^ ESC [ 25 ^ |
2198 |
F4 ESC [ 14 ~ ESC [ 26 ~ ESC [ 14 ^ ESC [ 26 ^ |
2199 |
F5 ESC [ 15 ~ ESC [ 28 ~ ESC [ 15 ^ ESC [ 28 ^ |
2200 |
F6 ESC [ 17 ~ ESC [ 29 ~ ESC [ 17 ^ ESC [ 29 ^ |
2201 |
F7 ESC [ 18 ~ ESC [ 31 ~ ESC [ 18 ^ ESC [ 31 ^ |
2202 |
F8 ESC [ 19 ~ ESC [ 32 ~ ESC [ 19 ^ ESC [ 32 ^ |
2203 |
F9 ESC [ 20 ~ ESC [ 33 ~ ESC [ 20 ^ ESC [ 33 ^ |
2204 |
F10 ESC [ 21 ~ ESC [ 34 ~ ESC [ 21 ^ ESC [ 34 ^ |
2205 |
F11 ESC [ 23 ~ ESC [ 23 $ ESC [ 23 ^ ESC [ 23 @ |
2206 |
F12 ESC [ 24 ~ ESC [ 24 $ ESC [ 24 ^ ESC [ 24 @ |
2207 |
F13 ESC [ 25 ~ ESC [ 25 $ ESC [ 25 ^ ESC [ 25 @ |
2208 |
F14 ESC [ 26 ~ ESC [ 26 $ ESC [ 26 ^ ESC [ 26 @ |
2209 |
F15 (Help) ESC [ 28 ~ ESC [ 28 $ ESC [ 28 ^ ESC [ 28 @ |
2210 |
F16 (Menu) ESC [ 29 ~ ESC [ 29 $ ESC [ 29 ^ ESC [ 29 @ |
2211 |
F17 ESC [ 31 ~ ESC [ 31 $ ESC [ 31 ^ ESC [ 31 @ |
2212 |
F18 ESC [ 32 ~ ESC [ 32 $ ESC [ 32 ^ ESC [ 32 @ |
2213 |
F19 ESC [ 33 ~ ESC [ 33 $ ESC [ 33 ^ ESC [ 33 @ |
2214 |
F20 ESC [ 34 ~ ESC [ 34 $ ESC [ 34 ^ ESC [ 34 @ |
2215 |
B<Application> |
2216 |
Up ESC [ A ESC [ a ESC O a ESC O A |
2217 |
Down ESC [ B ESC [ b ESC O b ESC O B |
2218 |
Right ESC [ C ESC [ c ESC O c ESC O C |
2219 |
Left ESC [ D ESC [ d ESC O d ESC O D |
2220 |
KP_Enter ^M ESC O M |
2221 |
KP_F1 ESC O P ESC O P |
2222 |
KP_F2 ESC O Q ESC O Q |
2223 |
KP_F3 ESC O R ESC O R |
2224 |
KP_F4 ESC O S ESC O S |
2225 |
XK_KP_Multiply * ESC O j |
2226 |
XK_KP_Add + ESC O k |
2227 |
XK_KP_Separator , ESC O l |
2228 |
XK_KP_Subtract - ESC O m |
2229 |
XK_KP_Decimal . ESC O n |
2230 |
XK_KP_Divide / ESC O o |
2231 |
XK_KP_0 0 ESC O p |
2232 |
XK_KP_1 1 ESC O q |
2233 |
XK_KP_2 2 ESC O r |
2234 |
XK_KP_3 3 ESC O s |
2235 |
XK_KP_4 4 ESC O t |
2236 |
XK_KP_5 5 ESC O u |
2237 |
XK_KP_6 6 ESC O v |
2238 |
XK_KP_7 7 ESC O w |
2239 |
XK_KP_8 8 ESC O x |
2240 |
XK_KP_9 9 ESC O y |
2241 |
|
2242 |
=end table |
2243 |
|
2244 |
=head1 CONFIGURE OPTIONS |
2245 |
|
2246 |
General hint: if you get compile errors, then likely your configuration |
2247 |
hasn't been tested well. Either try with C<--enable-everything> or use |
2248 |
the default configuration (i.e. no C<--enable-xxx> or C<--disable-xxx> |
2249 |
switches). Of course, you should always report when a combination doesn't |
2250 |
work, so it can be fixed. Marc Lehmann <rxvt@schmorp.de>. |
2251 |
|
2252 |
All |
2253 |
|
2254 |
=over 4 |
2255 |
|
2256 |
=item --enable-everything |
2257 |
|
2258 |
Add (or remove) support for all non-multichoice options listed |
2259 |
in C<./configure --help>, except for C<--enable-assert> and |
2260 |
C<--enable-256-color>. |
2261 |
|
2262 |
You can specify this and then disable options you do not like by |
2263 |
I<following> this with the appropriate C<--disable-...> arguments, |
2264 |
or you can start with a minimal configuration by specifying |
2265 |
C<--disable-everything> and than adding just the C<--enable-...> arguments |
2266 |
you want. |
2267 |
|
2268 |
=item --enable-xft (default: enabled) |
2269 |
|
2270 |
Add support for Xft (anti-aliases, among others) fonts. Xft fonts are |
2271 |
slower and require lots of memory, but as long as you don't use them, you |
2272 |
don't pay for them. |
2273 |
|
2274 |
=item --enable-font-styles (default: on) |
2275 |
|
2276 |
Add support for B<bold>, I<italic> and B<< I<bold italic> >> font |
2277 |
styles. The fonts can be set manually or automatically. |
2278 |
|
2279 |
=item --with-codesets=NAME,... (default: all) |
2280 |
|
2281 |
Compile in support for additional codeset (encoding) groups (C<eu>, C<vn> |
2282 |
are always compiled in, which includes most 8-bit character sets). These |
2283 |
codeset tables are used for driving X11 core fonts, they are not required |
2284 |
for Xft fonts, although having them compiled in lets rxvt-unicode choose |
2285 |
replacement fonts more intelligently. Compiling them in will make your |
2286 |
binary bigger (all of together cost about 700kB), but it doesn't increase |
2287 |
memory usage unless you use a font requiring one of these encodings. |
2288 |
|
2289 |
=begin table |
2290 |
|
2291 |
all all available codeset groups |
2292 |
zh common chinese encodings |
2293 |
zh_ext rarely used but very big chinese encodings |
2294 |
jp common japanese encodings |
2295 |
jp_ext rarely used but big japanese encodings |
2296 |
kr korean encodings |
2297 |
|
2298 |
=end table |
2299 |
|
2300 |
=item --enable-xim (default: on) |
2301 |
|
2302 |
Add support for XIM (X Input Method) protocol. This allows using |
2303 |
alternative input methods (e.g. kinput2) and will also correctly |
2304 |
set up the input for people using dead keys or compose keys. |
2305 |
|
2306 |
=item --enable-unicode3 (default: off) |
2307 |
|
2308 |
Recommended to stay off unless you really need non-BMP characters. |
2309 |
|
2310 |
Enable direct support for displaying unicode codepoints above |
2311 |
65535 (the basic multilingual page). This increases storage |
2312 |
requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2313 |
support these extra characters, but Xft does. |
2314 |
|
2315 |
Please note that rxvt-unicode can store unicode code points >65535 |
2316 |
even without this flag, but the number of such characters is |
2317 |
limited to a few thousand (shared with combining characters, |
2318 |
see next switch), and right now rxvt-unicode cannot display them |
2319 |
(input/output and cut&paste still work, though). |
2320 |
|
2321 |
=item --enable-combining (default: on) |
2322 |
|
2323 |
Enable automatic composition of combining characters into |
2324 |
composite characters. This is required for proper viewing of text |
2325 |
where accents are encoded as separate unicode characters. This is |
2326 |
done by using precomposited characters when available or creating |
2327 |
new pseudo-characters when no precomposed form exists. |
2328 |
|
2329 |
Without --enable-unicode3, the number of additional precomposed |
2330 |
characters is somewhat limited (the 6400 private use characters will be |
2331 |
(ab-)used). With --enable-unicode3, no practical limit exists. |
2332 |
|
2333 |
This option will also enable storage (but not display) of characters |
2334 |
beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2335 |
|
2336 |
The combining table also contains entries for arabic presentation forms, |
2337 |
but these are not currently used. Bug me if you want these to be used (and |
2338 |
tell me how these are to be used...). |
2339 |
|
2340 |
=item --enable-fallback(=CLASS) (default: Rxvt) |
2341 |
|
2342 |
When reading resource settings, also read settings for class CLASS. To |
2343 |
disable resource fallback use --disable-fallback. |
2344 |
|
2345 |
=item --with-res-name=NAME (default: urxvt) |
2346 |
|
2347 |
Use the given name as default application name when |
2348 |
reading resources. Specify --with-res-name=rxvt to replace rxvt. |
2349 |
|
2350 |
=item --with-res-class=CLASS (default: URxvt) |
2351 |
|
2352 |
Use the given class as default application class |
2353 |
when reading resources. Specify --with-res-class=Rxvt to replace |
2354 |
rxvt. |
2355 |
|
2356 |
=item --enable-utmp (default: on) |
2357 |
|
2358 |
Write user and tty to utmp file (used by programs like F<w>) at |
2359 |
start of rxvt execution and delete information when rxvt exits. |
2360 |
|
2361 |
=item --enable-wtmp (default: on) |
2362 |
|
2363 |
Write user and tty to wtmp file (used by programs like F<last>) at |
2364 |
start of rxvt execution and write logout when rxvt exits. This |
2365 |
option requires --enable-utmp to also be specified. |
2366 |
|
2367 |
=item --enable-lastlog (default: on) |
2368 |
|
2369 |
Write user and tty to lastlog file (used by programs like |
2370 |
F<lastlogin>) at start of rxvt execution. This option requires |
2371 |
--enable-utmp to also be specified. |
2372 |
|
2373 |
=item --enable-afterimage (default: on) |
2374 |
|
2375 |
Add support for libAfterImage to be used for transparency and background |
2376 |
images. It adds support for many file formats including JPG, PNG, |
2377 |
SVG, TIFF, GIF, XPM, BMP, ICO, XCF, TGA and AfterStep image XML |
2378 |
(L<http://www.afterstep.org/visualdoc.php?show=asimagexml>). |
2379 |
|
2380 |
This option also adds such eye candy as blending an image over the root |
2381 |
background, as well as dynamic scaling and bluring of background images. |
2382 |
|
2383 |
Note that with this option enabled, @@RXVT_NAME@@'s memory footprint might |
2384 |
increase by a few megabytes even if no extra features are used (mostly due |
2385 |
to third-party libraries used by libAI). Memory footprint may somewhat be |
2386 |
lowered if libAfterImage is configured without support for SVG. |
2387 |
|
2388 |
=item --enable-transparency (default: on) |
2389 |
|
2390 |
Add support for backgrounds, creating illusion of transparency in the term. |
2391 |
|
2392 |
=item --enable-fading (default: on) |
2393 |
|
2394 |
Add support for fading the text when focus is lost. |
2395 |
|
2396 |
=item --enable-rxvt-scroll (default: on) |
2397 |
|
2398 |
Add support for the original rxvt scrollbar. |
2399 |
|
2400 |
=item --enable-next-scroll (default: on) |
2401 |
|
2402 |
Add support for a NeXT-like scrollbar. |
2403 |
|
2404 |
=item --enable-xterm-scroll (default: on) |
2405 |
|
2406 |
Add support for an Xterm-like scrollbar. |
2407 |
|
2408 |
=item --disable-backspace-key |
2409 |
|
2410 |
Removes any handling of the backspace key by us - let the X server do it. |
2411 |
|
2412 |
=item --disable-delete-key |
2413 |
|
2414 |
Removes any handling of the delete key by us - let the X server |
2415 |
do it. |
2416 |
|
2417 |
=item --disable-resources |
2418 |
|
2419 |
Removes any support for resource checking. |
2420 |
|
2421 |
=item --disable-swapscreen |
2422 |
|
2423 |
Remove support for secondary/swap screen. |
2424 |
|
2425 |
=item --enable-frills (default: on) |
2426 |
|
2427 |
Add support for many small features that are not essential but nice to |
2428 |
have. Normally you want this, but for very small binaries you may want to |
2429 |
disable this. |
2430 |
|
2431 |
A non-exhaustive list of features enabled by C<--enable-frills> (possibly |
2432 |
in combination with other switches) is: |
2433 |
|
2434 |
MWM-hints |
2435 |
EWMH-hints (pid, utf8 names) and protocols (ping) |
2436 |
urgency hint |
2437 |
separate underline colour (-underlineColor) |
2438 |
settable border widths and borderless switch (-w, -b, -bl) |
2439 |
visual depth selection (-depth) |
2440 |
settable extra linespacing (-lsp) |
2441 |
iso-14755 5.1 (basic) support |
2442 |
tripleclickwords (-tcw) |
2443 |
settable insecure mode (-insecure) |
2444 |
keysym remapping support |
2445 |
cursor blinking and underline cursor (-bc, -uc) |
2446 |
XEmbed support (-embed) |
2447 |
user-pty (-pty-fd) |
2448 |
hold on exit (-hold) |
2449 |
compile in built-in block graphics |
2450 |
skip builtin block graphics (-sbg) |
2451 |
separate highlight colour (-highlightColor, -highlightTextColor) |
2452 |
|
2453 |
It also enables some non-essential features otherwise disabled, such as: |
2454 |
|
2455 |
some round-trip time optimisations |
2456 |
nearest colour allocation on pseudocolor screens |
2457 |
UTF8_STRING support for selection |
2458 |
sgr modes 90..97 and 100..107 |
2459 |
backindex and forwardindex escape sequences |
2460 |
view change/zero scrollback escape sequences |
2461 |
locale switching escape sequence |
2462 |
window op and some xterm/OSC escape sequences |
2463 |
rectangular selections |
2464 |
trailing space removal for selections |
2465 |
verbose X error handling |
2466 |
|
2467 |
=item --enable-iso14755 (default: on) |
2468 |
|
2469 |
Enable extended ISO 14755 support (see @@RXVT_NAME@@(1)). |
2470 |
Basic support (section 5.1) is enabled by C<--enable-frills>, while |
2471 |
support for 5.2, 5.3 and 5.4 is enabled with this switch. |
2472 |
|
2473 |
=item --enable-keepscrolling (default: on) |
2474 |
|
2475 |
Add support for continual scrolling of the display when you hold |
2476 |
the mouse button down on a scrollbar arrow. |
2477 |
|
2478 |
=item --enable-selectionscrolling (default: on) |
2479 |
|
2480 |
Add support for scrolling when the selection moves to the top or |
2481 |
bottom of the screen. |
2482 |
|
2483 |
=item --enable-mousewheel (default: on) |
2484 |
|
2485 |
Add support for scrolling via mouse wheel or buttons 4 & 5. |
2486 |
|
2487 |
=item --enable-slipwheeling (default: on) |
2488 |
|
2489 |
Add support for continual scrolling (using the mouse wheel as an |
2490 |
accelerator) while the control key is held down. This option |
2491 |
requires --enable-mousewheel to also be specified. |
2492 |
|
2493 |
=item --enable-smart-resize (default: off) |
2494 |
|
2495 |
Add smart growth/shrink behaviour when resizing. |
2496 |
This should keep the window corner which is closest to a corner of |
2497 |
the screen in a fixed position. |
2498 |
|
2499 |
=item --enable-text-blink (default: on) |
2500 |
|
2501 |
Add support for blinking text. |
2502 |
|
2503 |
=item --enable-pointer-blank (default: on) |
2504 |
|
2505 |
Add support to have the pointer disappear when typing or inactive. |
2506 |
|
2507 |
=item --enable-perl (default: on) |
2508 |
|
2509 |
Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)> |
2510 |
manpage for more info on this feature, or the files in F<src/perl/> |
2511 |
for the extensions that are installed by default. |
2512 |
The perl interpreter that is used can be specified via the C<PERL> |
2513 |
environment variable when running configure. Even when compiled in, |
2514 |
perl will I<not> be initialised when all extensions have been disabled |
2515 |
C<-pe "" --perl-ext-common "">, so it should be safe to enable from a |
2516 |
resource standpoint. |
2517 |
|
2518 |
=item --enable-assert (default: off) |
2519 |
|
2520 |
Enables the assertions in the code, normally disabled. This switch is only |
2521 |
useful when developing rxvt-unicode. |
2522 |
|
2523 |
=item --enable-256-color (default: off) |
2524 |
|
2525 |
Force use of so-called 256 colour mode, to work around buggy applications |
2526 |
that do not support termcap/terminfo, or simply improve support for |
2527 |
applications hardcoding the xterm 256 colour table. |
2528 |
|
2529 |
This switch breaks termcap/terminfo compatibility to C<TERM=rxvt-unicode>, |
2530 |
and consequently sets C<TERM> to C<rxvt-unicode-256color> by default |
2531 |
(F<doc/etc/> contains termcap/terminfo definitions for both). |
2532 |
|
2533 |
It also results in higher memory usage and can slow down @@RXVT_NAME@@ |
2534 |
dramatically when more than six fonts are in use by a terminal instance. |
2535 |
|
2536 |
=item --with-afterimage-config=DIR |
2537 |
|
2538 |
Look for the libAfterImage config script in DIR. |
2539 |
|
2540 |
=item --with-name=NAME (default: urxvt) |
2541 |
|
2542 |
Set the basename for the installed binaries, resulting |
2543 |
in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with |
2544 |
C<rxvt>. |
2545 |
|
2546 |
=item --with-term=NAME (default: rxvt-unicode) |
2547 |
|
2548 |
Change the environmental variable for the terminal to NAME. |
2549 |
|
2550 |
=item --with-terminfo=PATH |
2551 |
|
2552 |
Change the environmental variable for the path to the terminfo tree to |
2553 |
PATH. |
2554 |
|
2555 |
=item --with-x |
2556 |
|
2557 |
Use the X Window System (pretty much default, eh?). |
2558 |
|
2559 |
=back |
2560 |
|
2561 |
=head1 AUTHORS |
2562 |
|
2563 |
Marc Lehmann <rxvt@schmorp.de> converted this document to pod and |
2564 |
reworked it from the original Rxvt documentation, which was done by Geoff |
2565 |
Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other |
2566 |
sources. |
2567 |
|