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

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.20 by root, Sun Apr 17 22:36:13 2005 UTC vs.
Revision 1.76 by root, Thu Jul 6 18:56:10 2006 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines