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.12 by root, Fri Feb 11 18:06:44 2005 UTC vs.
Revision 1.78 by root, Mon Jul 17 19:20:29 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
… …
126. ds Ae AE 126. ds Ae AE
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_NAME@@ 7"
132.TH rxvt 7 "2005-02-11" "5.0" "RXVT-UNICODE" 132.TH @@RXVT_NAME@@ 7 "2006-07-17" "7.8" "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
169bug to the original rxvt-unicode author please download and install the
170genuine version (<http://software.schmorp.de#rxvt\-unicode>) and try to
171reproduce the problem. If you cannot, chances are that the problems are
172specific to Debian GNU/Linux, in which case it should be reported via the
173Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
174.Sp
175For other problems that also affect the Debian package, you can and
176probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a
177bug in the Debian version and it serves as a reminder for other users that
178might encounter the same issue.
179.IP "When I log-in to another system it tells me about missing terminfo data?" 4
180.IX Item "When I log-in to another system it tells me about missing terminfo data?"
181The 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).
183.Sp
184The correct solution for this problem is to install the terminfo, this can
185be done like this (with ncurses' infocmp):
186.Sp
187.Vb 2
188\& REMOTE=remotesystem.domain
189\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
190.Ve
191.Sp
192\&... or by installing rxvt-unicode normally on the remote system,
193.Sp
194If 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
196problems arising, which includes wrong keymapping, less and different
197colours and some refresh errors in fullscreen applications. It's a nice
198quick-and-dirty workaround for rare cases, though.
199.Sp
200If 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
202resource to set it:
203.Sp
204.Vb 1
205\& URxvt.termName: rxvt
206.Ve
207.Sp
208If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
209the rxvt terminfo file with the rxvt-unicode one.
210.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4
211.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4
212.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@."
213.PD 0
214.IP "I need a termcap file entry." 4
215.IX Item "I need a termcap file entry."
216.PD
217One reason you might want this is that some distributions or operating
218systems still compile some programs using the long-obsoleted termcap
219(Fedora Core's bash is one example) and rely on a termcap entry for
220\&\f(CW\*(C`rxvt\-unicode\*(C'\fR.
221.Sp
222You 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
224like this:
225.Sp
226.Vb 1
227\& infocmp -C rxvt-unicode
228.Ve
229.Sp
230Or you could use this termcap entry, generated by the command above:
231.Sp
232.Vb 19
233\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e
234\& :am:bw:eo:km:mi:ms:xn:xo:\e
235\& :co#80:it#8:li#24:\e
236\& :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
238\& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=^O:al=\eE[L:\e
239\& :as=^N:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:cm=\eE[%i%d;%dH:\e
240\& :cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:dl=\eE[M:do=^J:\e
241\& :ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:\e
242\& :im=\eE[4h:is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e
243\& :k0=\eE[21~:k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:\e
244\& :k5=\eE[15~:k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:\e
245\& :kD=\eE[3~:kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:\e
246\& :ke=\eE[?1l\eE>:kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:\e
247\& :ku=\eEOA:le=^H:mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:\e
248\& :nd=\eE[C:rc=\eE8:sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:\e
249\& :st=\eEH:ta=^I:te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:\e
250\& :up=\eE[A:us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e
251\& :vs=\eE[?25h:
252.Ve
253.ie n .IP "Why does ""ls"" no longer have coloured output?" 4
254.el .IP "Why does \f(CWls\fR no longer have coloured output?" 4
255.IX Item "Why does ls no longer have coloured output?"
256The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
257decide wether a terminal has colour, but uses it's own configuration
258file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among
259with most other terminals supporting colour). Either add:
260.Sp
261.Vb 1
262\& TERM rxvt-unicode
263.Ve
264.Sp
265to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
266.Sp
267.Vb 1
268\& alias ls='ls --color=auto'
269.Ve
270.Sp
271to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
272.IP "Why doesn't vim/emacs etc. use the 88 colour mode?" 4
273.IX Item "Why doesn't vim/emacs etc. use the 88 colour mode?"
274.PD 0
275.IP "Why doesn't vim/emacs etc. make use of italic?" 4
276.IX Item "Why doesn't vim/emacs etc. make use of italic?"
277.IP "Why are the secondary screen-related options not working properly?" 4
278.IX Item "Why are the secondary screen-related options not working properly?"
279.PD
280Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged
281distributions (most notably Debian GNU/Linux) break rxvt-unicode
282by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra
283features. Unfortunately, some of these (most notably, again, Debian
284GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
285file, so you will need to install it on your own (See the question \fBWhen
286I log-in to another system it tells me about missing terminfo data?\fR on
287how to do this).
288.IP "My numerical keypad acts weird and generates differing output?" 4
289.IX Item "My numerical keypad acts weird and generates differing output?"
290Some Debian GNUL/Linux users seem to have this problem, although no
291specific details were reported so far. It is possible that this is caused
292by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
293this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
294keymap. See the answer to the previous question, and please report if that
295helped.
296.IP "Rxvt-unicode does not seem to understand the selected encoding?" 4
297.IX Item "Rxvt-unicode does not seem to understand the selected encoding?"
298.PD 0
299.IP "Unicode does not seem to work?" 4
300.IX Item "Unicode does not seem to work?"
301.PD
302If you encounter strange problems like typing an accented character but
303getting two unrelated other characters or similar, or if program output is
304subtly garbled, then you should check your locale settings.
305.Sp
306Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the
307programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the
308login script running within the rxvt-unicode window changes the locale to
309something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work.
310.Sp
311The best thing is to fix your startup environment, as you will likely run
312into other problems. If nothing works you can try this in your .profile.
313.Sp
314.Vb 1
315\& printf '\ee]701;%s\e007' "$LC_CTYPE"
316.Ve
317.Sp
318If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not
319supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which
320displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as
321it will complain loudly if it cannot set the locale). If it displays something
322like:
323.Sp
324.Vb 1
325\& locale: Cannot set LC_CTYPE to default locale: ...
326.Ve
327.Sp
328Then the locale you specified is not supported on your system.
329.Sp
330If nothing works and you are sure that everything is set correctly then
331you will need to remember a little known fact: Some programs just don't
332support locales :(
333.IP "Why do some characters look so much different than others?" 4
334.IX Item "Why do some characters look so much different than others?"
335.PD 0
336.IP "How does rxvt-unicode choose fonts?" 4
337.IX Item "How does rxvt-unicode choose fonts?"
338.PD
339Most fonts do not contain the full range of Unicode, which is
340fine. Chances are that the font you (or the admin/package maintainer of
341your system/os) have specified does not cover all the characters you want
342to display.
343.Sp
344\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement
345font. Often the result is fine, but sometimes the chosen font looks
346bad/ugly/wrong. Some fonts have totally strange characters that don't
347resemble the correct glyph at all, and rxvt-unicode lacks the artificial
348intelligence to detect that a specific glyph is wrong: it has to believe
349the font that the characters it claims to contain indeed look correct.
350.Sp
351In that case, select a font of your taste and add it to the font list,
352e.g.:
353.Sp
354.Vb 1
355\& @@RXVT_NAME@@ -fn basefont,font2,font3...
356.Ve
357.Sp
358When rxvt-unicode sees a character, it will first look at the base
359font. If the base font does not contain the character, it will go to the
360next font, and so on. Specifying your own fonts will also speed up this
361search and use less resources within rxvt-unicode and the X\-server.
362.Sp
363The only limitation is that none of the fonts may be larger than the base
364font, as the base font defines the terminal character cell size, which
365must be the same due to the way terminals work.
366.IP "Why do some chinese characters look so different than others?" 4
367.IX Item "Why do some chinese characters look so different than others?"
368This is because there is a difference between script and language \*(--
369rxvt-unicode does not know which language the text that is output is,
370as it only knows the unicode character codes. If rxvt-unicode first
371sees a japanese/chinese character, it might choose a japanese font for
372display. Subsequent japanese characters will use that font. Now, many
373chinese characters aren't represented in japanese fonts, so when the first
374non-japanese character comes up, rxvt-unicode will look for a chinese font
375\&\*(-- unfortunately at this point, it will still use the japanese font for
376chinese characters that are also in the japanese font.
377.Sp
378The workaround is easy: just tag a chinese font at the end of your font
379list (see the previous question). The key is to view the font list as
380a preference list: If you expect more japanese, list a japanese font
381first. If you expect more chinese, put a chinese font first.
382.Sp
383In the future it might be possible to switch language preferences at
384runtime (the internal data structure has no problem with using different
385fonts for the same character at the same time, but no interface for this
386has been designed yet).
387.Sp
388Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
389.IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4
390.IX Item "Why does rxvt-unicode sometimes leave pixel droppings?"
391Most fonts were not designed for terminal use, which means that character
392size varies a lot. A font that is otherwise fine for terminal use might
393contain some characters that are simply too wide. Rxvt-unicode will avoid
394these characters. For characters that are just \*(L"a bit\*(R" too wide a special
395\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
396.Sp
397All of this requires that fonts do not lie about character sizes,
398however: Xft fonts often draw glyphs larger than their acclaimed bounding
399box, and rxvt-unicode has no way of detecting this (the correct way is to
400ask for the character bounding box, which unfortunately is wrong in these
401cases).
402.Sp
403It's not clear (to me at least), wether this is a bug in Xft, freetype,
404or the respective font. If you encounter this problem you might try using
405the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
406might be forced to use a different font.
407.Sp
408All of this is not a problem when using X11 core fonts, as their bounding
409box data is correct.
410.IP "My Compose (Multi_key) key is no longer working." 4
411.IX Item "My Compose (Multi_key) key is no longer working."
412The most common causes for this are that either your locale is not set
413correctly, or you specified a \fBpreeditStyle\fR that is not supported by
414your input method. For example, if you specified \fBOverTheSpot\fR and
415your input method (e.g. the default input method handling Compose keys)
416does not support this (for instance because it is not visual), then
417rxvt-unicode will continue without an input method.
418.Sp
419In this case either do not specify a \fBpreeditStyle\fR or specify more than
420one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
421.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
422.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
423.IX Item "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
424Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
425international keyboards) or simply use \s-1ISO\s0 14755 support to your
426advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
427codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
428character and so on.
429.IP "How can I keep rxvt-unicode from using reverse video so much?" 4
430.IX Item "How can I keep rxvt-unicode from using reverse video so much?"
431First of all, make sure you are running with the right terminal settings
432(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
433make sure you have specified colours for italic and bold, as otherwise
434rxvt-unicode might use reverse video to simulate the effect:
435.Sp
436.Vb 2
437\& URxvt.colorBD: white
438\& URxvt.colorIT: green
439.Ve
440.IP "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 4
441.IX Item "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
442For some unexplainable reason, some rare programs assume a very weird
443colour palette when confronted with a terminal with more than the standard
4448 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
445these programs not to assume non-ISO colours without very good reasons.
446.Sp
447In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
448definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
449fix colours but keep you from using other rxvt-unicode features.
450.IP "I am on FreeBSD and rxvt-unicode does not seem to work at all." 4
451.IX Item "I am on FreeBSD and rxvt-unicode does not seem to work at all."
452Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
453in your compile environment, or an implementation that implements it,
454wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
455\&\fBwchar_t\fR is represented as unicode.
456.Sp
457As you might have guessed, FreeBSD does neither define this symobl nor
458does it support it. Instead, it uses it's own internal representation of
459\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
460.Sp
461However, \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support
462multi-language apps in an \s-1OS\s0, as using a locale-dependent (and
463non\-standardized) representation of \fBwchar_t\fR makes it impossible to
464convert between \fBwchar_t\fR (as used by X11 and your applications) and any
465other encoding without implementing OS-specific-wrappers for each and
466every locale. There simply are no APIs to convert \fBwchar_t\fR into anything
467except the current locale encoding.
468.Sp
469Some applications (such as the formidable \fBmlterm\fR) work around this
470by carrying their own replacement functions for character set handling
471with them, and either implementing OS-dependent hacks or doing multiple
472conversions (which is slow and unreliable in case the \s-1OS\s0 implements
473encodings slightly different than the terminal emulator).
474.Sp
475The rxvt-unicode author insists that the right way to fix this is in the
476system libraries once and for all, instead of forcing every app to carry
477complete replacements for them :)
478.IP "How does rxvt-unicode determine the encoding to use?" 4
479.IX Item "How does rxvt-unicode determine the encoding to use?"
480.PD 0
481.IP "Is there an option to switch encodings?" 4
482.IX Item "Is there an option to switch encodings?"
483.PD
484Unlike some other terminals, rxvt-unicode has no encoding switch, and no
485specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
486\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
487.Sp
488The reasons is that there exists a perfectly fine mechanism for selecting
489the encoding, doing I/O and (most important) communicating this to all
490applications so everybody agrees on character properties such as width
491and code number. This mechanism is the \fIlocale\fR. Applications not using
492that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
493characters wrong as it uses it's own, locale-independent table under all
494locales).
495.Sp
496Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
497programs doing the same (that is, most) will automatically agree in the
498interpretation of characters.
499.Sp
500Unfortunately, there is no system-independent way to select locales, nor
501is there a standard on how locale specifiers will look like.
502.Sp
503On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
504contains an arbitrary string which corresponds to an already-installed
505locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
506\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
507(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
508.Sp
509Rxvt-unicode ignores all other locale categories, and except for
510the encoding, ignores country or language-specific settings,
511i.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
512rxvt\-unicode.
513.Sp
514If you want to use a specific encoding you have to make sure you start
515rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
516.IP "Can I switch locales at runtime?" 4
517.IX Item "Can I switch locales at runtime?"
518Yes, using an escape sequence. Try something like this, which sets
519rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
520.Sp
521.Vb 1
522\& printf '\ee]701;%s\e007' ja_JP.SJIS
523.Ve
524.Sp
525See also the previous answer.
526.Sp
527Sometimes this capability is rather handy when you want to work in
528one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
529(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
530first switches to a locale supported by xjdic and back later:
531.Sp
532.Vb 3
533\& printf '\ee]701;%s\e007' ja_JP.SJIS
534\& xjdic -js
535\& printf '\ee]701;%s\e007' de_DE.UTF-8
536.Ve
537.Sp
538You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
539for some locales where character width differs between program\- and
540rxvt\-unicode\-locales.
541.IP "Can I switch the fonts at runtime?" 4
542.IX Item "Can I switch the fonts at runtime?"
543Yes, using an escape sequence. Try something like this, which has the same
544effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
545.Sp
546.Vb 1
547\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
548.Ve
549.Sp
550This is useful if you e.g. work primarily with japanese (and prefer a
551japanese font), but you have to switch to chinese temporarily, where
552japanese fonts would only be in your way.
553.Sp
554You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
555.IP "Why do italic characters look as if clipped?" 4
556.IX Item "Why do italic characters look as if clipped?"
557Many fonts have difficulties with italic characters and hinting. For
558example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
559Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
560enable freetype autohinting, i.e. like this:
561.Sp
562.Vb 2
563\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
564\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
565.Ve
566.IP "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" 4
567.IX Item "My input method wants <some encoding> but I want UTF-8, what can I do?"
568You can specify separate locales for the input method and the rest of the
569terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
570.Sp
571.Vb 1
572\& URxvt*imlocale: ja_JP.EUC-JP
573.Ve
574.Sp
575Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
576use your input method. Please note, however, that you will not be able to
577input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
578method limits you.
579.IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4 192\fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR
580.IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?" 193.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
194.PP
581Rxvt-unicode tries to obey the rule of not charging you for something you 195Rxvt-unicode tries to obey the rule of not charging you for something you
582don't use. One thing you should try is to configure out all settings that 196don't use. One thing you should try is to configure out all settings that
583you don't need, for example, Xft support is a resource hog by design, 197you don't need, for example, Xft support is a resource hog by design,
584when used. Compiling it out ensures that no Xft font will be loaded 198when used. Compiling it out ensures that no Xft font will be loaded
585accidentally when rxvt-unicode tries to find a font for your characters. 199accidentally when rxvt-unicode tries to find a font for your characters.
586.Sp 200.PP
587Also, many people (me included) like large windows and even larger 201Also, many people (me included) like large windows and even larger
588scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use 202scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
5896 bytes per screen cell. For a 160x?? window this amounts to almost a 2036 bytes per screen cell. For a 160x?? window this amounts to almost a
590kilobyte per line. A scrollback buffer of 10000 lines will then (if full) 204kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
591use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as 205use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
592rxvt-unicode then uses 8 bytes per screen cell. 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 its 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
593.IP "Can I speed up Xft rendering somehow?" 4 497\fICan I speed up Xft rendering somehow?\fR
594.IX Item "Can I speed up Xft rendering somehow?" 498.IX Subsection "Can I speed up Xft rendering somehow?"
499.PP
595Yes, the most obvious way to speed it up is to avoid Xft entirely, as 500Yes, the most obvious way to speed it up is to avoid Xft entirely, as
596it is simply slow. If you still want Xft fonts you might try to disable 501it is simply slow. If you still want Xft fonts you might try to disable
597antialiasing (by appending \f(CW\*(C`:antialiasing=false\*(C'\fR), which saves lots of 502antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
598memory and also speeds up rendering considerably. 503memory and also speeds up rendering considerably.
504.PP
599.IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 505\fIRxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?\fR
600.IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 506.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
507.PP
601Rxvt-unicode will use whatever you specify as a font. If it needs to 508Rxvt-unicode will use whatever you specify as a font. If it needs to
602fall back to it's default font search list it will prefer X11 core 509fall back to its default font search list it will prefer X11 core
603fonts, because they are small and fast, and then use Xft fonts. It has 510fonts, because they are small and fast, and then use Xft fonts. It has
604antialiasing disabled for most of them, because the author thinks they 511antialiasing disabled for most of them, because the author thinks they
605look best that way. 512look best that way.
606.Sp 513.PP
607If you want antialiasing, you have to specify the fonts manually. 514If you want antialiasing, you have to specify the fonts manually.
608.IP "Mouse cut/paste suddenly no longer works." 4 515.PP
609.IX Item "Mouse cut/paste suddenly no longer works."
610Make sure that mouse reporting is actually turned off since killing
611some editors prematurely may leave the mouse in mouse report mode. I've
612heard that tcsh may use mouse reporting unless it otherwise specified. A
613quick check is to see if cut/paste works when the Alt or Shift keys are
614depressed. See @@RXVT_NAME@@(7)
615.IP "What's with this bold/blink stuff?" 4 516\fIWhat's with this bold/blink stuff?\fR
616.IX Item "What's with this bold/blink stuff?" 517.IX Subsection "What's with this bold/blink stuff?"
518.PP
617If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the 519If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
618standard foreground colour. 520standard foreground colour.
619.Sp 521.PP
620For the standard background colour, blinking will actually make the 522For the standard background colour, blinking will actually make the
621text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard 523text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
622colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be 524colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
623ignored. 525ignored.
624.Sp 526.PP
625On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity 527On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
626foreground/background colors. 528foreground/background colors.
627.Sp 529.PP
628color0\-7 are the low-intensity colors. 530color0\-7 are the low-intensity colors.
629.Sp 531.PP
630color8\-15 are the corresponding high-intensity colors. 532color8\-15 are the corresponding high-intensity colors.
533.PP
631.IP "I don't like the screen colors. How do I change them?" 4 534\fII don't like the screen colors. How do I change them?\fR
632.IX Item "I don't like the screen colors. How do I change them?" 535.IX Subsection "I don't like the screen colors. How do I change them?"
536.PP
633You can change the screen colors at run-time using \fI~/.Xdefaults\fR 537You can change the screen colors at run-time using \fI~/.Xdefaults\fR
634resources (or as long\-options). 538resources (or as long\-options).
635.Sp 539.PP
636Here are values that are supposed to resemble a \s-1VGA\s0 screen, 540Here are values that are supposed to resemble a \s-1VGA\s0 screen,
637including the murky brown that passes for low-intensity yellow: 541including the murky brown that passes for low-intensity yellow:
638.Sp 542.PP
639.Vb 8 543.Vb 8
640\& URxvt.color0: #000000 544\& URxvt.color0: #000000
641\& URxvt.color1: #A80000 545\& URxvt.color1: #A80000
642\& URxvt.color2: #00A800 546\& URxvt.color2: #00A800
643\& URxvt.color3: #A8A800 547\& URxvt.color3: #A8A800
644\& URxvt.color4: #0000A8 548\& URxvt.color4: #0000A8
645\& URxvt.color5: #A800A8 549\& URxvt.color5: #A800A8
646\& URxvt.color6: #00A8A8 550\& URxvt.color6: #00A8A8
647\& URxvt.color7: #A8A8A8 551\& URxvt.color7: #A8A8A8
648.Ve 552\&
649.Sp
650.Vb 8
651\& URxvt.color8: #000054 553\& URxvt.color8: #000054
652\& URxvt.color9: #FF0054 554\& URxvt.color9: #FF0054
653\& URxvt.color10: #00FF54 555\& URxvt.color10: #00FF54
654\& URxvt.color11: #FFFF54 556\& URxvt.color11: #FFFF54
655\& URxvt.color12: #0000FF 557\& URxvt.color12: #0000FF
656\& URxvt.color13: #FF00FF 558\& URxvt.color13: #FF00FF
657\& URxvt.color14: #00FFFF 559\& URxvt.color14: #00FFFF
658\& URxvt.color15: #FFFFFF 560\& URxvt.color15: #FFFFFF
659.Ve 561.Ve
660.Sp 562.PP
661And here is a more complete set of non-standard colors described (not by 563And here is a more complete set of non-standard colors.
662me) as \*(L"pretty girly\*(R". 564.PP
663.Sp
664.Vb 18 565.Vb 10
665\& URxvt.cursorColor: #dc74d1 566\& URxvt.cursorColor: #dc74d1
666\& URxvt.pointerColor: #dc74d1 567\& URxvt.pointerColor: #dc74d1
667\& URxvt.background: #0e0e0e 568\& URxvt.background: #0e0e0e
668\& URxvt.foreground: #4ad5e1 569\& URxvt.foreground: #4ad5e1
669\& URxvt.color0: #000000 570\& URxvt.color0: #000000
… …
679\& URxvt.color6: #73f7ff 580\& URxvt.color6: #73f7ff
680\& URxvt.color14: #73f7ff 581\& URxvt.color14: #73f7ff
681\& URxvt.color7: #e1dddd 582\& URxvt.color7: #e1dddd
682\& URxvt.color15: #e1dddd 583\& URxvt.color15: #e1dddd
683.Ve 584.Ve
684.IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 585.PP
685.IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" 586They have been described (not by me) as \*(L"pretty girly\*(R".
686Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a 587.PP
687server that answers @@RXVT_NAME@@c's requests, so it doesn't background 588\fIWhy do some characters look so much different than others?\fR
688itself. 589.IX Subsection "Why do some characters look so much different than others?"
689.Sp 590.PP
690To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the 591See next entry.
691following method to wait for the startup message before continuing: 592.PP
692.Sp 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
693.Vb 1 611.Vb 1
694\& { @@RXVT_NAME@@d & } | read 612\& @@URXVT_NAME@@ \-fn basefont,font2,font3...
695.Ve 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
696.IP "What's with the strange Backspace/Delete key behaviour?" 4 761\fIWhat's with the strange Backspace/Delete key behaviour?\fR
697.IX Item "What's with the strange Backspace/Delete key behaviour?" 762.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
763.PP
698Assuming that the physical Backspace key corresponds to the 764Assuming that the physical Backspace key corresponds to the
699BackSpace keysym (not likely for Linux ... see the following 765BackSpace keysym (not likely for Linux ... see the following
700question) there are two standard values that can be used for 766question) there are two standard values that can be used for
701Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. 767Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
702.Sp 768.PP
703Historically, either value is correct, but rxvt-unicode adopts the debian 769Historically, either value is correct, but rxvt-unicode adopts the debian
704policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct 770policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
705choice :). 771choice :).
706.Sp 772.PP
707Rxvt-unicode tries to inherit the current stty settings and uses the value 773Rxvt-unicode tries to inherit the current stty settings and uses the value
708of `erase' to guess the value for backspace. If rxvt-unicode wasn't 774of `erase' to guess the value for backspace. If rxvt-unicode wasn't
709started from a terminal (say, from a menu or by remote shell), then the 775started from a terminal (say, from a menu or by remote shell), then the
710system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will 776system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
711be used (which may not be the same as your stty setting). 777be used (which may not be the same as your stty setting).
712.Sp 778.PP
713For starting a new rxvt\-unicode: 779For starting a new rxvt\-unicode:
714.Sp 780.PP
715.Vb 3 781.Vb 3
716\& # use Backspace = ^H 782\& # use Backspace = ^H
717\& $ stty erase ^H 783\& $ stty erase ^H
718\& $ @@RXVT_NAME@@ 784\& $ @@URXVT_NAME@@
719.Ve 785\&
720.Sp
721.Vb 3
722\& # use Backspace = ^? 786\& # use Backspace = ^?
723\& $ stty erase ^? 787\& $ stty erase ^?
724\& $ @@RXVT_NAME@@ 788\& $ @@URXVT_NAME@@
725.Ve 789.Ve
726.Sp 790.PP
727Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR as documented in @@RXVT_NAME@@(7). 791Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
728.Sp 792.PP
729For an existing rxvt\-unicode: 793For an existing rxvt\-unicode:
730.Sp 794.PP
731.Vb 3 795.Vb 3
732\& # use Backspace = ^H 796\& # use Backspace = ^H
733\& $ stty erase ^H 797\& $ stty erase ^H
734\& $ echo -n "^[[36h" 798\& $ echo \-n "^[[36h"
735.Ve 799\&
736.Sp
737.Vb 3
738\& # use Backspace = ^? 800\& # use Backspace = ^?
739\& $ stty erase ^? 801\& $ stty erase ^?
740\& $ echo -n "^[[36l" 802\& $ echo \-n "^[[36l"
741.Ve 803.Ve
742.Sp 804.PP
743This helps satisfy some of the Backspace discrepancies that occur, but 805This helps satisfy some of the Backspace discrepancies that occur, but
744if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value 806if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
745properly reflects that. 807properly reflects that.
746.Sp 808.PP
747The Delete key is a another casualty of the ill-defined Backspace problem. 809The Delete key is a another casualty of the ill-defined Backspace problem.
748To avoid confusion between the Backspace and Delete keys, the Delete 810To avoid confusion between the Backspace and Delete keys, the Delete
749key has been assigned an escape sequence to match the vt100 for Execute 811key has been assigned an escape sequence to match the vt100 for Execute
750(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. 812(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
751.Sp 813.PP
752Some other Backspace problems: 814Some other Backspace problems:
753.Sp 815.PP
754some editors use termcap/terminfo, 816some editors use termcap/terminfo,
755some editors (vim I'm told) expect Backspace = ^H, 817some editors (vim I'm told) expect Backspace = ^H,
756\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. 818\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
757.Sp 819.PP
758Perhaps someday this will all be resolved in a consistent manner. 820Perhaps someday this will all be resolved in a consistent manner.
821.PP
759.IP "I don't like the key\-bindings. How do I change them?" 4 822\fII don't like the key\-bindings. How do I change them?\fR
760.IX Item "I don't like the key-bindings. How do I change them?" 823.IX Subsection "I don't like the key-bindings. How do I change them?"
824.PP
761There are some compile-time selections available via configure. Unless 825There are some compile-time selections available via configure. Unless
762you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can 826you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
763use the `keysym' resource to alter the keystrings associated with keysyms. 827use the `keysym' resource to alter the keystrings associated with keysyms.
764.Sp 828.PP
765Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR 829Here's an example for a URxvt session started using \f(CW\*(C`@@URXVT_NAME@@ \-name URxvt\*(C'\fR
766.Sp 830.PP
767.Vb 20 831.Vb 10
768\& URxvt.keysym.Home: \e033[1~ 832\& URxvt.keysym.Home: \e033[1~
769\& URxvt.keysym.End: \e033[4~ 833\& URxvt.keysym.End: \e033[4~
770\& URxvt.keysym.C-apostrophe: \e033<C-'> 834\& URxvt.keysym.C\-apostrophe: \e033<C\-'>
771\& URxvt.keysym.C-slash: \e033<C-/> 835\& URxvt.keysym.C\-slash: \e033<C\-/>
772\& URxvt.keysym.C-semicolon: \e033<C-;> 836\& URxvt.keysym.C\-semicolon: \e033<C\-;>
773\& URxvt.keysym.C-grave: \e033<C-`> 837\& URxvt.keysym.C\-grave: \e033<C\-`>
774\& URxvt.keysym.C-comma: \e033<C-,> 838\& URxvt.keysym.C\-comma: \e033<C\-,>
775\& URxvt.keysym.C-period: \e033<C-.> 839\& URxvt.keysym.C\-period: \e033<C\-.>
776\& URxvt.keysym.C-0x60: \e033<C-`> 840\& URxvt.keysym.C\-0x60: \e033<C\-`>
777\& URxvt.keysym.C-Tab: \e033<C-Tab> 841\& URxvt.keysym.C\-Tab: \e033<C\-Tab>
778\& URxvt.keysym.C-Return: \e033<C-Return> 842\& URxvt.keysym.C\-Return: \e033<C\-Return>
779\& URxvt.keysym.S-Return: \e033<S-Return> 843\& URxvt.keysym.S\-Return: \e033<S\-Return>
780\& URxvt.keysym.S-space: \e033<S-Space> 844\& URxvt.keysym.S\-space: \e033<S\-Space>
781\& URxvt.keysym.M-Up: \e033<M-Up> 845\& URxvt.keysym.M\-Up: \e033<M\-Up>
782\& URxvt.keysym.M-Down: \e033<M-Down> 846\& URxvt.keysym.M\-Down: \e033<M\-Down>
783\& URxvt.keysym.M-Left: \e033<M-Left> 847\& URxvt.keysym.M\-Left: \e033<M\-Left>
784\& URxvt.keysym.M-Right: \e033<M-Right> 848\& URxvt.keysym.M\-Right: \e033<M\-Right>
785\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > 849\& URxvt.keysym.M\-C\-0: list \e033<M\-C\- 0123456789 >
786\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > 850\& URxvt.keysym.M\-C\-a: list \e033<M\-C\- abcdefghijklmnopqrstuvwxyz >
787\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 851\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
788.Ve 852.Ve
789.Sp 853.PP
790See some more examples in the documentation for the \fBkeysym\fR resource. 854See some more examples in the documentation for the \fBkeysym\fR resource.
855.PP
791.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 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
792.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." 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
793.Vb 6 859.Vb 6
794\& KP_Insert == Insert 860\& KP_Insert == Insert
795\& F22 == Print 861\& F22 == Print
796\& F27 == Home 862\& F27 == Home
797\& F29 == Prior 863\& F29 == Prior
798\& F33 == End 864\& F33 == End
799\& F35 == Next 865\& F35 == Next
800.Ve 866.Ve
801.Sp 867.PP
802Rather than have rxvt-unicode try to accommodate all the various possible 868Rather than have rxvt-unicode try to accommodate all the various possible
803keyboard mappings, it is better to use `xmodmap' to remap the keys as 869keyboard mappings, it is better to use `xmodmap' to remap the keys as
804required for your particular machine. 870required for your particular machine.
805.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 871.Sh "Terminal Configuration"
806.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." 872.IX Subsection "Terminal Configuration"
807rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can 873\fICan I see a typical configuration?\fR
808check and see if that is set. Note that several programs, \s-1JED\s0, slrn, 874.IX Subsection "Can I see a typical configuration?"
809Midnight Commander automatically check this variable to decide whether or 875.PP
810not to use color. 876The default configuration tries to be xterm\-like, which I don't like that
811.IP "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" 4 877much, but it's least surprise to regular users.
812.IX Item "How do I set the correct, full IP address for the DISPLAY variable?" 878.PP
813If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled 879As a rxvt or rxvt-unicode user, you are practically supposed to invest
814insecure mode then it is possible to use the following shell script 880time into customising your terminal. To get you started, here is the
815snippets to correctly set the display. If your version of rxvt-unicode 881author's .Xdefaults entries, with comments on what they do. It's certainly
816wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then 882not \fItypical\fR, but what's typical...
817the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a 883.PP
818regular xterm. 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
1081\fIWhen I log-in to another system it tells me about missing terminfo data?\fR
1082.IX Subsection "When I log-in to another system it tells me about missing terminfo data?"
1083.PP
1084The terminal description used by rxvt-unicode is not as widely available
1085as that for xterm, or even rxvt (for which the same problem often arises).
1086.PP
1087The correct solution for this problem is to install the terminfo, this can
1088be done like this (with ncurses' infocmp):
1089.PP
1090.Vb 2
1091\& REMOTE=remotesystem.domain
1092\& infocmp rxvt\-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
1093.Ve
1094.PP
1095\&... or by installing rxvt-unicode normally on the remote system,
1096.PP
1097If you cannot or do not want to do this, then you can simply set
1098\&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of
1099problems arising, which includes wrong keymapping, less and different
1100colours and some refresh errors in fullscreen applications. It's a nice
1101quick-and-dirty workaround for rare cases, though.
1102.PP
1103If you always want to do this (and are fine with the consequences) you
1104can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a
1105resource to set it:
1106.PP
1107.Vb 1
1108\& URxvt.termName: rxvt
1109.Ve
1110.PP
1111If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
1112the rxvt terminfo file with the rxvt-unicode one and use \f(CW\*(C`TERM=rxvt\*(C'\fR.
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
1120\fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR
1121.IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@."
1122.PP
1123See next entry.
1124.PP
1125\fII need a termcap file entry.\fR
1126.IX Subsection "I need a termcap file entry."
1127.PP
1128One reason you might want this is that some distributions or operating
1129systems still compile some programs using the long-obsoleted termcap
1130library (Fedora Core's bash is one example) and rely on a termcap entry
1131for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
1132.PP
1133You could use rxvt's termcap entry with resonable results in many cases.
1134You can also create a termcap entry by using terminfo's infocmp program
1135like this:
1136.PP
1137.Vb 1
1138\& infocmp \-C rxvt\-unicode
1139.Ve
1140.PP
1141Or you could use this termcap entry, generated by the command above:
1142.PP
1143.Vb 10
1144\& rxvt\-unicode|rxvt\-unicode terminal (X Window System):\e
1145\& :am:bw:eo:km:mi:ms:xn:xo:\e
1146\& :co#80:it#8:li#24:lm#0:\e
1147\& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e
1148\& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e
1149\& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=\eE(B:al=\eE[L:\e
1150\& :as=\eE(0:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:\e
1151\& :cm=\eE[%i%d;%dH:cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:\e
1152\& :dl=\eE[M:do=^J:ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:\e
1153\& :i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:im=\eE[4h:\e
1154\& :is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e
1155\& :k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:k5=\eE[15~:\e
1156\& :k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:kD=\eE[3~:\e
1157\& :kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:ke=\eE[?1l\eE>:\e
1158\& :kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:ku=\eEOA:le=^H:\e
1159\& :mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:nd=\eE[C:rc=\eE8:\e
1160\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e
1161\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e
1162\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e
1163\& :vs=\eE[?25h:
1164.Ve
1165.PP
1166\fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR
1167.IX Subsection "Why does ls no longer have coloured output?"
1168.PP
1169The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
1170decide wether a terminal has colour, but uses its own configuration
1171file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in its default file (among
1172with most other terminals supporting colour). Either add:
1173.PP
1174.Vb 1
1175\& TERM rxvt\-unicode
1176.Ve
1177.PP
1178to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
1179.PP
1180.Vb 1
1181\& alias ls='ls \-\-color=auto'
1182.Ve
1183.PP
1184to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
1185.PP
1186\fIWhy doesn't vim/emacs etc. use the 88 colour mode?\fR
1187.IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?"
1188.PP
1189See next entry.
1190.PP
1191\fIWhy doesn't vim/emacs etc. make use of italic?\fR
1192.IX Subsection "Why doesn't vim/emacs etc. make use of italic?"
1193.PP
1194See next entry.
1195.PP
1196\fIWhy are the secondary screen-related options not working properly?\fR
1197.IX Subsection "Why are the secondary screen-related options not working properly?"
1198.PP
1199Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged
1200distributions (most notably Debian GNU/Linux) break rxvt-unicode
1201by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra
1202features. Unfortunately, some of these (most notably, again, Debian
1203GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
1204file, so you will need to install it on your own (See the question \fBWhen
1205I log-in to another system it tells me about missing terminfo data?\fR on
1206how to do this).
1207.Sh "Encoding / Locale / Input Method Issues"
1208.IX Subsection "Encoding / Locale / Input Method Issues"
1209\fIRxvt-unicode does not seem to understand the selected encoding?\fR
1210.IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?"
1211.PP
1212See next entry.
1213.PP
1214\fIUnicode does not seem to work?\fR
1215.IX Subsection "Unicode does not seem to work?"
1216.PP
1217If you encounter strange problems like typing an accented character but
1218getting two unrelated other characters or similar, or if program output is
1219subtly garbled, then you should check your locale settings.
1220.PP
1221Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the
1222programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the
1223login script running within the rxvt-unicode window changes the locale to
1224something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work.
1225.PP
1226The best thing is to fix your startup environment, as you will likely run
1227into other problems. If nothing works you can try this in your .profile.
1228.PP
1229.Vb 1
1230\& printf '\e33]701;%s\e007' "$LC_CTYPE"
1231.Ve
1232.PP
1233If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not
1234supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which
1235displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as
1236it will complain loudly if it cannot set the locale). If it displays something
1237like:
1238.PP
1239.Vb 1
1240\& locale: Cannot set LC_CTYPE to default locale: ...
1241.Ve
1242.PP
1243Then the locale you specified is not supported on your system.
1244.PP
1245If nothing works and you are sure that everything is set correctly then
1246you will need to remember a little known fact: Some programs just don't
1247support locales :(
1248.PP
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 its 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."
1332.PD 0
1333.ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4
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."
1336.PD
1337When you want to use e.g. \fBkinput2\fR, it must be set to
1338\&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input
1339method servers are running with this command:
819.Sp 1340.Sp
820Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
821snippets:
822.Sp
823.Vb 12 1341.Vb 1
824\& # Bourne/Korn/POSIX family of shells: 1342\& xprop \-root XIM_SERVERS
825\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
826\& if [ ${TERM:-foo} = xterm ]; then
827\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
828\& echo -n '^[Z'
829\& read term_id
830\& stty icanon echo
831\& if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
832\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
833\& read DISPLAY # set it in our local shell
834\& fi
835\& fi
836.Ve 1343.Ve
837.IP "How do I compile the manual pages for myself?" 4 1344.IP "" 4
838.IX Item "How do I compile the manual pages for myself?" 1345.PP
839You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, 1346\fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR
840one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to 1347.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
841the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. 1348.PP
842.IP "My question isn't answered here, can I ask a human?" 4 1349You can specify separate locales for the input method and the rest of the
843.IX Item "My question isn't answered here, can I ask a human?" 1350terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
844Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, 1351.PP
845channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be 1352.Vb 1
846interested in learning about new and exciting problems (but not FAQs :). 1353\& URxvt.imlocale: ja_JP.EUC\-JP
1354.Ve
1355.PP
1356Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
1357use your input method. Please note, however, that, depending on your Xlib
1358version, you may not be able to input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a
1359normal way then, as your input method limits you.
1360.PP
1361\fIRxvt-unicode crashes when the X Input Method changes or exits.\fR
1362.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
1363.PP
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
1441\fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR
1442.IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all."
1443.PP
1444Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
1445in your compile environment, or an implementation that implements it,
1446wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
1447\&\fBwchar_t\fR is represented as unicode.
1448.PP
1449As you might have guessed, FreeBSD does neither define this symobl nor
1450does it support it. Instead, it uses its own internal representation of
1451\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
1452.PP
1453However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and
1454\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.
1455.PP
1456\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language
1457apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized)
1458representation of \fBwchar_t\fR makes it impossible to convert between
1459\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding
1460without implementing OS-specific-wrappers for each and every locale. There
1461simply are no APIs to convert \fBwchar_t\fR into anything except the current
1462locale encoding.
1463.PP
1464Some applications (such as the formidable \fBmlterm\fR) work around this
1465by carrying their own replacement functions for character set handling
1466with them, and either implementing OS-dependent hacks or doing multiple
1467conversions (which is slow and unreliable in case the \s-1OS\s0 implements
1468encodings slightly different than the terminal emulator).
1469.PP
1470The rxvt-unicode author insists that the right way to fix this is in the
1471system libraries once and for all, instead of forcing every app to carry
1472complete replacements for them :)
1473.PP
1474\fII use Solaris 9 and it doesn't compile/work/etc.\fR
1475.IX Subsection "I use Solaris 9 and it doesn't compile/work/etc."
1476.PP
1477Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
1478problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
1479.PP
1480\fIHow can I use rxvt-unicode under cygwin?\fR
1481.IX Subsection "How can I use rxvt-unicode under cygwin?"
1482.PP
1483rxvt-unicode should compile and run out of the box on cygwin, using
1484the X11 libraries that come with cygwin. libW11 emulation is no
1485longer supported (and makes no sense, either, as it only supported a
1486single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
1487\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
1488old libW11 emulation.
1489.PP
1490At the time of this writing, cygwin didn't seem to support any multi-byte
1491encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
1492to 8\-bit encodings.
847.SH "RXVT TECHNICAL REFERENCE" 1493.SH "RXVT-UNICODE TECHNICAL REFERENCE"
848.IX Header "RXVT TECHNICAL REFERENCE" 1494.IX Header "RXVT-UNICODE TECHNICAL REFERENCE"
849.SH "DESCRIPTION"
850.IX Header "DESCRIPTION"
851The rest of this document describes various technical aspects of 1495The rest of this document describes various technical aspects of
852\&\fBrxvt-unicode\fR. First the description of supported command sequences, 1496\&\fBrxvt-unicode\fR. First the description of supported command sequences,
853followed by menu and pixmap support and last by a description of all 1497followed by pixmap support and last by a description of all features
854features selectable at \f(CW\*(C`configure\*(C'\fR time. 1498selectable at \f(CW\*(C`configure\*(C'\fR time.
855.SH "Definitions" 1499.Sh "Definitions"
856.IX Header "Definitions" 1500.IX Subsection "Definitions"
857.ie n .IP "\fB\fB""c""\fB\fR" 4 1501.ie n .IP "\fB\fB""c""\fB\fR" 4
858.el .IP "\fB\f(CBc\fB\fR" 4 1502.el .IP "\fB\f(CBc\fB\fR" 4
859.IX Item "c" 1503.IX Item "c"
860The literal character c. 1504The literal character c.
861.ie n .IP "\fB\fB""C""\fB\fR" 4 1505.ie n .IP "\fB\fB""C""\fB\fR" 4
… …
874parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). 1518parameters, separated by \f(CW\*(C`;\*(C'\fR character(s).
875.ie n .IP "\fB\fB""Pt""\fB\fR" 4 1519.ie n .IP "\fB\fB""Pt""\fB\fR" 4
876.el .IP "\fB\f(CBPt\fB\fR" 4 1520.el .IP "\fB\f(CBPt\fB\fR" 4
877.IX Item "Pt" 1521.IX Item "Pt"
878A text parameter composed of printable characters. 1522A text parameter composed of printable characters.
879.SH "Values" 1523.Sh "Values"
880.IX Header "Values" 1524.IX Subsection "Values"
881.ie n .IP "\fB\fB""ENQ""\fB\fR" 4 1525.ie n .IP "\fB\fB""ENQ""\fB\fR" 4
882.el .IP "\fB\f(CBENQ\fB\fR" 4 1526.el .IP "\fB\f(CBENQ\fB\fR" 4
883.IX Item "ENQ" 1527.IX Item "ENQ"
884Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) 1528Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0)
885request 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.
… …
923Switch to Standard Character Set 1567Switch to Standard Character Set
924.ie n .IP "\fB\fB""SPC""\fB\fR" 4 1568.ie n .IP "\fB\fB""SPC""\fB\fR" 4
925.el .IP "\fB\f(CBSPC\fB\fR" 4 1569.el .IP "\fB\f(CBSPC\fB\fR" 4
926.IX Item "SPC" 1570.IX Item "SPC"
927Space Character 1571Space Character
928.SH "Escape Sequences" 1572.Sh "Escape Sequences"
929.IX Header "Escape Sequences" 1573.IX Subsection "Escape Sequences"
930.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 1574.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4
931.el .IP "\fB\f(CBESC # 8\fB\fR" 4 1575.el .IP "\fB\f(CBESC # 8\fB\fR" 4
932.IX Item "ESC # 8" 1576.IX Item "ESC # 8"
933\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) 1577\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0)
934.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 1578.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4
… …
1023C = < Multinational character set unimplemented 1667C = < Multinational character set unimplemented
1024C = 5 Finnish character set unimplemented 1668C = 5 Finnish character set unimplemented
1025C = C Finnish character set unimplemented 1669C = C Finnish character set unimplemented
1026C = K German character set unimplemented 1670C = K German character set unimplemented
1027.TE 1671.TE
1028
1029.PP 1672.PP
1030 1673
1031.IX Xref "CSI" 1674.IX Xref "CSI"
1032.SH "CSI (Command Sequence Introducer) Sequences" 1675.Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences"
1033.IX Header "CSI (Command Sequence Introducer) Sequences" 1676.IX Subsection "CSI (Command Sequence Introducer) Sequences"
1034.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 1677.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4
1035.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 1678.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4
1036.IX Item "ESC [ Ps @" 1679.IX Item "ESC [ Ps @"
1037Insert \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)
1038.IX Xref "ESCOBPsA" 1681.IX Xref "ESCOBPsA"
… …
1082l l . 1725l l .
1083Ps = 0 Clear Below (default) 1726Ps = 0 Clear Below (default)
1084Ps = 1 Clear Above 1727Ps = 1 Clear Above
1085Ps = 2 Clear All 1728Ps = 2 Clear All
1086.TE 1729.TE
1087
1088.ie n .IP "\fB\fB""ESC [ Ps K""\fB\fR" 4 1730.ie n .IP "\fB\fB""ESC [ Ps K""\fB\fR" 4
1089.el .IP "\fB\f(CBESC [ Ps K\fB\fR" 4 1731.el .IP "\fB\f(CBESC [ Ps K\fB\fR" 4
1090.IX Item "ESC [ Ps K" 1732.IX Item "ESC [ Ps K"
1091Erase in Line (\s-1EL\s0) 1733Erase in Line (\s-1EL\s0)
1092.TS 1734.TS
1093l l . 1735l l .
1094Ps = 0 Clear to Right (default) 1736Ps = 0 Clear to Right (default)
1095Ps = 1 Clear to Left 1737Ps = 1 Clear to Left
1096Ps = 2 Clear All 1738Ps = 2 Clear All
1097.TE 1739.TE
1098
1099.ie n .IP "\fB\fB""ESC [ Ps L""\fB\fR" 4 1740.ie n .IP "\fB\fB""ESC [ Ps L""\fB\fR" 4
1100.el .IP "\fB\f(CBESC [ Ps L\fB\fR" 4 1741.el .IP "\fB\f(CBESC [ Ps L\fB\fR" 4
1101.IX Item "ESC [ Ps L" 1742.IX Item "ESC [ Ps L"
1102Insert \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)
1103.ie n .IP "\fB\fB""ESC [ Ps M""\fB\fR" 4 1744.ie n .IP "\fB\fB""ESC [ Ps M""\fB\fR" 4
… …
1121l l . 1762l l .
1122Ps = 0 Tab Set (HTS) 1763Ps = 0 Tab Set (HTS)
1123Ps = 2 Tab Clear (TBC), Clear Current Column (default) 1764Ps = 2 Tab Clear (TBC), Clear Current Column (default)
1124Ps = 5 Tab Clear (TBC), Clear All 1765Ps = 5 Tab Clear (TBC), Clear All
1125.TE 1766.TE
1126
1127.ie n .IP "\fB\fB""ESC [ Ps X""\fB\fR" 4 1767.ie n .IP "\fB\fB""ESC [ Ps X""\fB\fR" 4
1128.el .IP "\fB\f(CBESC [ Ps X\fB\fR" 4 1768.el .IP "\fB\f(CBESC [ Ps X\fB\fR" 4
1129.IX Item "ESC [ Ps X" 1769.IX Item "ESC [ Ps X"
1130Erase \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)
1131.ie n .IP "\fB\fB""ESC [ Ps Z""\fB\fR" 4 1771.ie n .IP "\fB\fB""ESC [ Ps Z""\fB\fR" 4
… …
1166.TS 1806.TS
1167l l . 1807l l .
1168Ps = 0 Clear Current Column (default) 1808Ps = 0 Clear Current Column (default)
1169Ps = 3 Clear All (TBC) 1809Ps = 3 Clear All (TBC)
1170.TE 1810.TE
1171
1172.ie n .IP "\fB\fB""ESC [ Pm h""\fB\fR" 4 1811.ie n .IP "\fB\fB""ESC [ Pm h""\fB\fR" 4
1173.el .IP "\fB\f(CBESC [ Pm h\fB\fR" 4 1812.el .IP "\fB\f(CBESC [ Pm h\fB\fR" 4
1174.IX Item "ESC [ Pm h" 1813.IX Item "ESC [ Pm h"
1175Set 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.
1176.ie n .IP "\fB\fB""ESC [ Ps i""\fB\fR" 4 1815.ie n .IP "\fB\fB""ESC [ Ps i""\fB\fR" 4
… …
1181l l . 1820l l .
1182Ps = 0 print screen (MC0) 1821Ps = 0 print screen (MC0)
1183Ps = 4 disable transparent print mode (MC4) 1822Ps = 4 disable transparent print mode (MC4)
1184Ps = 5 enable transparent print mode (MC5) 1823Ps = 5 enable transparent print mode (MC5)
1185.TE 1824.TE
1186
1187.ie n .IP "\fB\fB""ESC [ Pm l""\fB\fR" 4 1825.ie n .IP "\fB\fB""ESC [ Pm l""\fB\fR" 4
1188.el .IP "\fB\f(CBESC [ Pm l\fB\fR" 4 1826.el .IP "\fB\f(CBESC [ Pm l\fB\fR" 4
1189.IX Item "ESC [ Pm l" 1827.IX Item "ESC [ Pm l"
1190Reset Mode (\s-1RM\s0) 1828Reset Mode (\s-1RM\s0)
1191.RS 4 1829.RS 4
… …
1195.TS 1833.TS
1196l l . 1834l l .
1197h Insert Mode (SMIR) 1835h Insert Mode (SMIR)
1198l Replace Mode (RMIR) 1836l Replace Mode (RMIR)
1199.TE 1837.TE
1200
1201.PD 0 1838.PD 0
1202.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
1203.el .IP "\fB\f(CBPs = 20\fB\fR (partially implemented)" 4 1840.el .IP "\fB\f(CBPs = 20\fB\fR (partially implemented)" 4
1204.IX Item "Ps = 20 (partially implemented)" 1841.IX Item "Ps = 20 (partially implemented)"
1205.TS 1842.TS
1206l l . 1843l l .
1207h Automatic Newline (LNM) 1844h Automatic Newline (LNM)
1208l Normal Linefeed (LNM) 1845l Normal Linefeed (LNM)
1209.TE 1846.TE
1210
1211.RE 1847.RE
1212.RS 4 1848.RS 4
1213.RE 1849.RE
1214.ie n .IP "\fB\fB""ESC [ Pm m""\fB\fR" 4 1850.ie n .IP "\fB\fB""ESC [ Pm m""\fB\fR" 4
1215.el .IP "\fB\f(CBESC [ Pm m\fB\fR" 4 1851.el .IP "\fB\f(CBESC [ Pm m\fB\fR" 4
… …
1244Ps = 95 / 105 fg/bg Bright Magenta 1880Ps = 95 / 105 fg/bg Bright Magenta
1245Ps = 96 / 106 fg/bg Bright Cyan 1881Ps = 96 / 106 fg/bg Bright Cyan
1246Ps = 97 / 107 fg/bg Bright White 1882Ps = 97 / 107 fg/bg Bright White
1247Ps = 99 / 109 fg/bg Bright Default 1883Ps = 99 / 109 fg/bg Bright Default
1248.TE 1884.TE
1249
1250.ie n .IP "\fB\fB""ESC [ Ps n""\fB\fR" 4 1885.ie n .IP "\fB\fB""ESC [ Ps n""\fB\fR" 4
1251.el .IP "\fB\f(CBESC [ Ps n\fB\fR" 4 1886.el .IP "\fB\f(CBESC [ Ps n\fB\fR" 4
1252.IX Item "ESC [ Ps n" 1887.IX Item "ESC [ Ps n"
1253Device Status Report (\s-1DSR\s0) 1888Device Status Report (\s-1DSR\s0)
1254.TS 1889.TS
… …
1256Ps = 5 Status Report ESC [ 0 n (``OK'') 1891Ps = 5 Status Report ESC [ 0 n (``OK'')
1257Ps = 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
1258Ps = 7 Request Display Name 1893Ps = 7 Request Display Name
1259Ps = 8 Request Version Number (place in window title) 1894Ps = 8 Request Version Number (place in window title)
1260.TE 1895.TE
1261
1262.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
1263.el .IP "\fB\f(CBESC [ Ps;Ps r\fB\fR" 4 1897.el .IP "\fB\f(CBESC [ Ps;Ps r\fB\fR" 4
1264.IX Item "ESC [ Ps;Ps r" 1898.IX Item "ESC [ Ps;Ps r"
1265Set Scrolling Region [top;bottom] 1899Set Scrolling Region [top;bottom]
1266[default: full size of window] (\s-1CSR\s0) 1900[default: full size of window] (\s-1CSR\s0)
… …
1289Ps = 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
1290Ps = 20 Reports icon label (ESC ] L NAME \234) 1924Ps = 20 Reports icon label (ESC ] L NAME \234)
1291Ps = 21 Reports window title (ESC ] l NAME \234) 1925Ps = 21 Reports window title (ESC ] l NAME \234)
1292Ps = 24.. Set window height to Ps rows 1926Ps = 24.. Set window height to Ps rows
1293.TE 1927.TE
1294
1295.ie n .IP "\fB\fB""ESC [ u""\fB\fR" 4 1928.ie n .IP "\fB\fB""ESC [ u""\fB\fR" 4
1296.el .IP "\fB\f(CBESC [ u\fB\fR" 4 1929.el .IP "\fB\f(CBESC [ u\fB\fR" 4
1297.IX Item "ESC [ u" 1930.IX Item "ESC [ u"
1298Restore Cursor 1931Restore Cursor
1299.ie n .IP "\fB\fB""ESC [ Ps x""\fB\fR" 4 1932.ie n .IP "\fB\fB""ESC [ Ps x""\fB\fR" 4
… …
1301.IX Item "ESC [ Ps x" 1934.IX Item "ESC [ Ps x"
1302Request Terminal Parameters (\s-1DECREQTPARM\s0) 1935Request Terminal Parameters (\s-1DECREQTPARM\s0)
1303.PP 1936.PP
1304 1937
1305.IX Xref "PrivateModes" 1938.IX Xref "PrivateModes"
1306.SH "DEC Private Modes" 1939.Sh "\s-1DEC\s0 Private Modes"
1307.IX Header "DEC Private Modes" 1940.IX Subsection "DEC Private Modes"
1308.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 1941.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4
1309.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 1942.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4
1310.IX Item "ESC [ ? Pm h" 1943.IX Item "ESC [ ? Pm h"
1311\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) 1944\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0)
1312.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 1945.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4
… …
1324.ie n .IP "\fB\fB""ESC [ ? Pm t""\fB\fR" 4 1957.ie n .IP "\fB\fB""ESC [ ? Pm t""\fB\fR" 4
1325.el .IP "\fB\f(CBESC [ ? Pm t\fB\fR" 4 1958.el .IP "\fB\f(CBESC [ ? Pm t\fB\fR" 4
1326.IX Item "ESC [ ? Pm t" 1959.IX Item "ESC [ ? Pm t"
1327Toggle \s-1DEC\s0 Private Mode Values (rxvt extension). \fIwhere\fR 1960Toggle \s-1DEC\s0 Private Mode Values (rxvt extension). \fIwhere\fR
1328.RS 4 1961.RS 4
1329.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
1330.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
1331.IX Item "Ps = 1 (DECCKM)" 1964.IX Item "Pm = 1 (DECCKM)"
1332.TS 1965.TS
1333l l . 1966l l .
1334h Application Cursor Keys 1967h Application Cursor Keys
1335l Normal Cursor Keys 1968l Normal Cursor Keys
1336.TE 1969.TE
1337
1338.PD 0 1970.PD 0
1339.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
1340.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
1341.IX Item "Ps = 2 (ANSI/VT52 mode)" 1973.IX Item "Pm = 2 (ANSI/VT52 mode)"
1342.TS 1974.TS
1343l l . 1975l l .
1344h Enter VT52 mode 1976h Enter VT52 mode
1345l Enter VT52 mode 1977l Enter VT52 mode
1346.TE 1978.TE
1347
1348.ie n .IP "\fB\fB""Ps = 3""\fB\fR" 4 1979.ie n .IP "\fB\fB""Pm = 3""\fB\fR" 4
1349.el .IP "\fB\f(CBPs = 3\fB\fR" 4 1980.el .IP "\fB\f(CBPm = 3\fB\fR" 4
1350.IX Item "Ps = 3" 1981.IX Item "Pm = 3"
1351.TS 1982.TS
1352l l . 1983l l .
1353h 132 Column Mode (DECCOLM) 1984h 132 Column Mode (DECCOLM)
1354l 80 Column Mode (DECCOLM) 1985l 80 Column Mode (DECCOLM)
1355.TE 1986.TE
1356
1357.ie n .IP "\fB\fB""Ps = 4""\fB\fR" 4 1987.ie n .IP "\fB\fB""Pm = 4""\fB\fR" 4
1358.el .IP "\fB\f(CBPs = 4\fB\fR" 4 1988.el .IP "\fB\f(CBPm = 4\fB\fR" 4
1359.IX Item "Ps = 4" 1989.IX Item "Pm = 4"
1360.TS 1990.TS
1361l l . 1991l l .
1362h Smooth (Slow) Scroll (DECSCLM) 1992h Smooth (Slow) Scroll (DECSCLM)
1363l Jump (Fast) Scroll (DECSCLM) 1993l Jump (Fast) Scroll (DECSCLM)
1364.TE 1994.TE
1365
1366.ie n .IP "\fB\fB""Ps = 5""\fB\fR" 4 1995.ie n .IP "\fB\fB""Pm = 5""\fB\fR" 4
1367.el .IP "\fB\f(CBPs = 5\fB\fR" 4 1996.el .IP "\fB\f(CBPm = 5\fB\fR" 4
1368.IX Item "Ps = 5" 1997.IX Item "Pm = 5"
1369.TS 1998.TS
1370l l . 1999l l .
1371h Reverse Video (DECSCNM) 2000h Reverse Video (DECSCNM)
1372l Normal Video (DECSCNM) 2001l Normal Video (DECSCNM)
1373.TE 2002.TE
1374
1375.ie n .IP "\fB\fB""Ps = 6""\fB\fR" 4 2003.ie n .IP "\fB\fB""Pm = 6""\fB\fR" 4
1376.el .IP "\fB\f(CBPs = 6\fB\fR" 4 2004.el .IP "\fB\f(CBPm = 6\fB\fR" 4
1377.IX Item "Ps = 6" 2005.IX Item "Pm = 6"
1378.TS 2006.TS
1379l l . 2007l l .
1380h Origin Mode (DECOM) 2008h Origin Mode (DECOM)
1381l Normal Cursor Mode (DECOM) 2009l Normal Cursor Mode (DECOM)
1382.TE 2010.TE
1383
1384.ie n .IP "\fB\fB""Ps = 7""\fB\fR" 4 2011.ie n .IP "\fB\fB""Pm = 7""\fB\fR" 4
1385.el .IP "\fB\f(CBPs = 7\fB\fR" 4 2012.el .IP "\fB\f(CBPm = 7\fB\fR" 4
1386.IX Item "Ps = 7" 2013.IX Item "Pm = 7"
1387.TS 2014.TS
1388l l . 2015l l .
1389h Wraparound Mode (DECAWM) 2016h Wraparound Mode (DECAWM)
1390l No Wraparound Mode (DECAWM) 2017l No Wraparound Mode (DECAWM)
1391.TE 2018.TE
1392
1393.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
1394.el .IP "\fB\f(CBPs = 8\fB\fR \fIunimplemented\fR" 4 2020.el .IP "\fB\f(CBPm = 8\fB\fR \fIunimplemented\fR" 4
1395.IX Item "Ps = 8 unimplemented" 2021.IX Item "Pm = 8 unimplemented"
1396.TS 2022.TS
1397l l . 2023l l .
1398h Auto-repeat Keys (DECARM) 2024h Auto-repeat Keys (DECARM)
1399l No Auto-repeat Keys (DECARM) 2025l No Auto-repeat Keys (DECARM)
1400.TE 2026.TE
1401
1402.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
1403.el .IP "\fB\f(CBPs = 9\fB\fR X10 XTerm" 4 2028.el .IP "\fB\f(CBPm = 9\fB\fR X10 XTerm" 4
1404.IX Item "Ps = 9 X10 XTerm" 2029.IX Item "Pm = 9 X10 XTerm"
1405.TS 2030.TS
1406l l . 2031l l .
1407h Send Mouse X & Y on button press. 2032h Send Mouse X & Y on button press.
1408l No mouse reporting. 2033l No mouse reporting.
1409.TE 2034.TE
1410
1411.ie n .IP "\fB\fB""Ps = 10""\fB\fR (\fBrxvt\fR)" 4
1412.el .IP "\fB\f(CBPs = 10\fB\fR (\fBrxvt\fR)" 4
1413.IX Item "Ps = 10 (rxvt)"
1414.TS
1415l l .
1416h menuBar visible
1417l menuBar invisible
1418.TE
1419
1420.ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4 2035.ie n .IP "\fB\fB""Pm = 25""\fB\fR" 4
1421.el .IP "\fB\f(CBPs = 25\fB\fR" 4 2036.el .IP "\fB\f(CBPm = 25\fB\fR" 4
1422.IX Item "Ps = 25" 2037.IX Item "Pm = 25"
1423.TS 2038.TS
1424l l . 2039l l .
1425h Visible cursor {cnorm/cvvis} 2040h Visible cursor {cnorm/cvvis}
1426l Invisible cursor {civis} 2041l Invisible cursor {civis}
1427.TE 2042.TE
1428
1429.ie n .IP "\fB\fB""Ps = 30""\fB\fR" 4 2043.ie n .IP "\fB\fB""Pm = 30""\fB\fR" 4
1430.el .IP "\fB\f(CBPs = 30\fB\fR" 4 2044.el .IP "\fB\f(CBPm = 30\fB\fR" 4
1431.IX Item "Ps = 30" 2045.IX Item "Pm = 30"
1432.TS 2046.TS
1433l l . 2047l l .
1434h scrollBar visisble 2048h scrollBar visisble
1435l scrollBar invisisble 2049l scrollBar invisisble
1436.TE 2050.TE
1437
1438.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
1439.el .IP "\fB\f(CBPs = 35\fB\fR (\fBrxvt\fR)" 4 2052.el .IP "\fB\f(CBPm = 35\fB\fR (\fBrxvt\fR)" 4
1440.IX Item "Ps = 35 (rxvt)" 2053.IX Item "Pm = 35 (rxvt)"
1441.TS 2054.TS
1442l l . 2055l l .
1443h Allow XTerm Shift+key sequences 2056h Allow XTerm Shift+key sequences
1444l Disallow XTerm Shift+key sequences 2057l Disallow XTerm Shift+key sequences
1445.TE 2058.TE
1446
1447.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
1448.el .IP "\fB\f(CBPs = 38\fB\fR \fIunimplemented\fR" 4 2060.el .IP "\fB\f(CBPm = 38\fB\fR \fIunimplemented\fR" 4
1449.IX Item "Ps = 38 unimplemented" 2061.IX Item "Pm = 38 unimplemented"
1450.PD 2062.PD
1451Enter Tektronix Mode (\s-1DECTEK\s0) 2063Enter Tektronix Mode (\s-1DECTEK\s0)
1452.ie n .IP "\fB\fB""Ps = 40""\fB\fR" 4 2064.ie n .IP "\fB\fB""Pm = 40""\fB\fR" 4
1453.el .IP "\fB\f(CBPs = 40\fB\fR" 4 2065.el .IP "\fB\f(CBPm = 40\fB\fR" 4
1454.IX Item "Ps = 40" 2066.IX Item "Pm = 40"
1455.TS 2067.TS
1456l l . 2068l l .
1457h Allow 80/132 Mode 2069h Allow 80/132 Mode
1458l Disallow 80/132 Mode 2070l Disallow 80/132 Mode
1459.TE 2071.TE
1460
1461.PD 0 2072.PD 0
1462.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
1463.el .IP "\fB\f(CBPs = 44\fB\fR \fIunimplemented\fR" 4 2074.el .IP "\fB\f(CBPm = 44\fB\fR \fIunimplemented\fR" 4
1464.IX Item "Ps = 44 unimplemented" 2075.IX Item "Pm = 44 unimplemented"
1465.TS 2076.TS
1466l l . 2077l l .
1467h Turn On Margin Bell 2078h Turn On Margin Bell
1468l Turn Off Margin Bell 2079l Turn Off Margin Bell
1469.TE 2080.TE
1470
1471.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
1472.el .IP "\fB\f(CBPs = 45\fB\fR \fIunimplemented\fR" 4 2082.el .IP "\fB\f(CBPm = 45\fB\fR \fIunimplemented\fR" 4
1473.IX Item "Ps = 45 unimplemented" 2083.IX Item "Pm = 45 unimplemented"
1474.TS 2084.TS
1475l l . 2085l l .
1476h Reverse-wraparound Mode 2086h Reverse-wraparound Mode
1477l No Reverse-wraparound Mode 2087l No Reverse-wraparound Mode
1478.TE 2088.TE
1479
1480.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
1481.el .IP "\fB\f(CBPs = 46\fB\fR \fIunimplemented\fR" 4 2090.el .IP "\fB\f(CBPm = 46\fB\fR \fIunimplemented\fR" 4
1482.IX Item "Ps = 46 unimplemented" 2091.IX Item "Pm = 46 unimplemented"
1483.ie n .IP "\fB\fB""Ps = 47""\fB\fR" 4 2092.ie n .IP "\fB\fB""Pm = 47""\fB\fR" 4
1484.el .IP "\fB\f(CBPs = 47\fB\fR" 4 2093.el .IP "\fB\f(CBPm = 47\fB\fR" 4
1485.IX Item "Ps = 47" 2094.IX Item "Pm = 47"
1486.TS 2095.TS
1487l l . 2096l l .
1488h Use Alternate Screen Buffer 2097h Use Alternate Screen Buffer
1489l Use Normal Screen Buffer 2098l Use Normal Screen Buffer
1490.TE 2099.TE
1491
1492.PD 2100.PD
1493 2101
1494.IX Xref "Priv66" 2102.IX Xref "Priv66"
1495.ie n .IP "\fB\fB""Ps = 66""\fB\fR" 4 2103.ie n .IP "\fB\fB""Pm = 66""\fB\fR" 4
1496.el .IP "\fB\f(CBPs = 66\fB\fR" 4 2104.el .IP "\fB\f(CBPm = 66\fB\fR" 4
1497.IX Item "Ps = 66" 2105.IX Item "Pm = 66"
1498.TS 2106.TS
1499l l . 2107l l .
1500h Application Keypad (DECPAM) == ESC = 2108h Application Keypad (DECPAM) == ESC =
1501l Normal Keypad (DECPNM) == ESC > 2109l Normal Keypad (DECPNM) == ESC >
1502.TE 2110.TE
1503
1504.PD 0 2111.PD 0
1505.ie n .IP "\fB\fB""Ps = 67""\fB\fR" 4 2112.ie n .IP "\fB\fB""Pm = 67""\fB\fR" 4
1506.el .IP "\fB\f(CBPs = 67\fB\fR" 4 2113.el .IP "\fB\f(CBPm = 67\fB\fR" 4
1507.IX Item "Ps = 67" 2114.IX Item "Pm = 67"
1508.TS 2115.TS
1509l l . 2116l l .
1510h Backspace key sends BS (DECBKM) 2117h Backspace key sends BS (DECBKM)
1511l Backspace key sends DEL 2118l Backspace key sends DEL
1512.TE 2119.TE
1513
1514.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
1515.el .IP "\fB\f(CBPs = 1000\fB\fR (X11 XTerm)" 4 2121.el .IP "\fB\f(CBPm = 1000\fB\fR (X11 XTerm)" 4
1516.IX Item "Ps = 1000 (X11 XTerm)" 2122.IX Item "Pm = 1000 (X11 XTerm)"
1517.TS 2123.TS
1518l l . 2124l l .
1519h Send Mouse X & Y on button press and release. 2125h Send Mouse X & Y on button press and release.
1520l No mouse reporting. 2126l No mouse reporting.
1521.TE 2127.TE
1522
1523.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
1524.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
1525.IX Item "Ps = 1001 (X11 XTerm) unimplemented" 2130.IX Item "Pm = 1001 (X11 XTerm) unimplemented"
1526.TS 2131.TS
1527l l . 2132l l .
1528h Use Hilite Mouse Tracking. 2133h Use Hilite Mouse Tracking.
1529l No mouse reporting. 2134l No mouse reporting.
1530.TE 2135.TE
1531
1532.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
1533.el .IP "\fB\f(CBPs = 1010\fB\fR (\fBrxvt\fR)" 4 2137.el .IP "\fB\f(CBPm = 1010\fB\fR (\fBrxvt\fR)" 4
1534.IX Item "Ps = 1010 (rxvt)" 2138.IX Item "Pm = 1010 (rxvt)"
1535.TS 2139.TS
1536l l . 2140l l .
1537h Don't scroll to bottom on TTY output 2141h Don't scroll to bottom on TTY output
1538l Scroll to bottom on TTY output 2142l Scroll to bottom on TTY output
1539.TE 2143.TE
1540
1541.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
1542.el .IP "\fB\f(CBPs = 1011\fB\fR (\fBrxvt\fR)" 4 2145.el .IP "\fB\f(CBPm = 1011\fB\fR (\fBrxvt\fR)" 4
1543.IX Item "Ps = 1011 (rxvt)" 2146.IX Item "Pm = 1011 (rxvt)"
1544.TS 2147.TS
1545l l . 2148l l .
1546h Scroll to bottom when a key is pressed 2149h Scroll to bottom when a key is pressed
1547l Don't scroll to bottom when a key is pressed 2150l Don't scroll to bottom when a key is pressed
1548.TE 2151.TE
1549 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
1550.ie n .IP "\fB\fB""Ps = 1047""\fB\fR" 4 2160.ie n .IP "\fB\fB""Pm = 1047""\fB\fR" 4
1551.el .IP "\fB\f(CBPs = 1047\fB\fR" 4 2161.el .IP "\fB\f(CBPm = 1047\fB\fR" 4
1552.IX Item "Ps = 1047" 2162.IX Item "Pm = 1047"
1553.TS 2163.TS
1554l l . 2164l l .
1555h Use Alternate Screen Buffer 2165h Use Alternate Screen Buffer
1556l 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
1557.TE 2167.TE
1558
1559.ie n .IP "\fB\fB""Ps = 1048""\fB\fR" 4 2168.ie n .IP "\fB\fB""Pm = 1048""\fB\fR" 4
1560.el .IP "\fB\f(CBPs = 1048\fB\fR" 4 2169.el .IP "\fB\f(CBPm = 1048\fB\fR" 4
1561.IX Item "Ps = 1048" 2170.IX Item "Pm = 1048"
1562.TS 2171.TS
1563l l . 2172l l .
1564h Save cursor position 2173h Save cursor position
1565l Restore cursor position 2174l Restore cursor position
1566.TE 2175.TE
1567
1568.ie n .IP "\fB\fB""Ps = 1049""\fB\fR" 4 2176.ie n .IP "\fB\fB""Pm = 1049""\fB\fR" 4
1569.el .IP "\fB\f(CBPs = 1049\fB\fR" 4 2177.el .IP "\fB\f(CBPm = 1049\fB\fR" 4
1570.IX Item "Ps = 1049" 2178.IX Item "Pm = 1049"
1571.TS 2179.TS
1572l l . 2180l l .
1573h 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
1574l Use Normal Screen Buffer 2182l Use Normal Screen Buffer
1575.TE 2183.TE
1576
1577.RE 2184.RE
1578.RS 4 2185.RS 4
1579.RE 2186.RE
1580.PD 2187.PD
1581.PP 2188.PP
1582 2189
1583.IX Xref "XTerm" 2190.IX Xref "XTerm"
1584.SH "XTerm Operating System Commands" 2191.Sh "XTerm Operating System Commands"
1585.IX Header "XTerm Operating System Commands" 2192.IX Subsection "XTerm Operating System Commands"
1586.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
1587.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 2194.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4
1588.IX Item "ESC ] Ps;Pt ST" 2195.IX Item "ESC ] Ps;Pt ST"
1589Set 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,
15900x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any 21970x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any
… …
1599Ps = 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)
1600Ps = 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)
1601Ps = 12 Change colour of text cursor foreground to Pt 2208Ps = 12 Change colour of text cursor foreground to Pt
1602Ps = 13 Change colour of mouse foreground to Pt 2209Ps = 13 Change colour of mouse foreground to Pt
1603Ps = 17 Change colour of highlight characters to Pt 2210Ps = 17 Change colour of highlight characters to Pt
1604Ps = 18 Change colour of bold characters to Pt 2211Ps = 18 Change colour of bold characters to Pt [deprecated, see 706]
1605Ps = 19 Change colour of underlined characters to Pt 2212Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707]
1606Ps = 20 Change default background to Pt 2213Ps = 20 Change background pixmap parameters (see section XPM) (Compile XPM).
1607Ps = 39 Change default foreground colour to Pt rxvt compile-time option 2214Ps = 39 Change default foreground colour to Pt.
1608Ps = 46 Change Log File to Pt unimplemented 2215Ps = 46 Change Log File to Pt unimplemented
1609Ps = 49 Change default background colour to Pt rxvt compile-time option 2216Ps = 49 Change default background colour to Pt.
1610Ps = 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
1611Ps = 55 Log all scrollback buffer and all of screen to Pt 2218Ps = 55 Log all scrollback buffer and all of screen to Pt
1612Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (@@RXVT_NAME@@ extension) 2219Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
1613Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) 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.
1614Ps = 704 Change colour of italic characters to Pt 2221Ps = 704 Change colour of italic characters to Pt
1615Ps = 705 Change background pixmap tint colour to Pt 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
1616Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 2225Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
1617Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. 2226Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
1618Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. 2227Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1619Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. 2228Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
2229Ps = 720 Move viewing window up 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).
1620.TE 2232.TE
1621
1622.PP
1623
1624.IX Xref "menuBar"
1625.SH "menuBar"
1626.IX Header "menuBar"
1627\&\fBThe exact syntax used is \f(BIalmost\fB solidified.\fR
1628In the menus, \fB\s-1DON\s0'T\fR try to use menuBar commands that add or remove a
1629menuBar.
1630.PP
1631Note that in all of the commands, the \fB\f(BI/path/\fB\fR \fIcannot\fR be
1632omitted: use \fB./\fR to specify a menu relative to the current menu.
1633.Sh "Overview of menuBar operation"
1634.IX Subsection "Overview of menuBar operation"
1635For the menuBar XTerm escape sequence \f(CW\*(C`ESC ] 703 ; Pt ST\*(C'\fR, the syntax
1636of \f(CW\*(C`Pt\*(C'\fR can be used for a variety of tasks:
1637.PP
1638At the top level is the current menuBar which is a member of a circular
1639linked-list of other such menuBars.
1640.PP
1641The menuBar acts as a parent for the various drop-down menus, which in
1642turn, may have labels, separator lines, menuItems and subMenus.
1643.PP
1644The menuItems are the useful bits: you can use them to mimic keyboard
1645input or even to send text or escape sequences back to rxvt.
1646.PP
1647The menuBar syntax is intended to provide a simple yet robust method of
1648constructing and manipulating menus and navigating through the
1649menuBars.
1650.PP
1651The first step is to use the tag \fB[menu:\f(BIname\fB]\fR which creates
1652the menuBar called \fIname\fR and allows access. You may now or menus,
1653subMenus, and menuItems. Finally, use the tag \fB[done]\fR to set the
1654menuBar access as \fBreadonly\fR to prevent accidental corruption of the
1655menus. To re-access the current menuBar for alterations, use the tag
1656\&\fB[menu]\fR, make the alterations and then use \fB[done]\fR
1657.PP
1658
1659.IX Xref "menuBarCommands"
1660.Sh "Commands"
1661.IX Subsection "Commands"
1662.IP "\fB[menu:+\f(BIname\fB]\fR" 4
1663.IX Item "[menu:+name]"
1664access the named menuBar for creation or alteration. If a new menuBar
1665is created, it is called \fIname\fR (max of 15 chars) and the current
1666menuBar is pushed onto the stack
1667.IP "\fB[menu]\fR" 4
1668.IX Item "[menu]"
1669access the current menuBar for alteration
1670.IP "\fB[title:+\f(BIstring\fB]\fR" 4
1671.IX Item "[title:+string]"
1672set the current menuBar's title to \fIstring\fR, which may contain the
1673following format specifiers:
1674\&\fB%%\fR : literal \fB%\fR character
1675\&\fB%n\fR : rxvt name (as per the \fB\-name\fR command-line option)
1676\&\fB%v\fR : rxvt version
1677.IP "\fB[done]\fR" 4
1678.IX Item "[done]"
1679set menuBar access as \fBreadonly\fR.
1680End-of-file tag for \fB[read:+\f(BIfile\fB]\fR operations.
1681.IP "\fB[read:+\f(BIfile\fB]\fR" 4
1682.IX Item "[read:+file]"
1683read menu commands directly from \fIfile\fR (extension \*(L".menu\*(R" will be
1684appended 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.
1685.Sp
1686Blank and comment lines (starting with \fB#\fR) are ignored. Actually,
1687since any invalid menu commands are also ignored, almost anything could
1688be construed as a comment line, but this may be tightened up in the
1689future ... so don't count on it!.
1690.IP "\fB[read:+\f(BIfile\fB;+\f(BIname\fB]\fR" 4
1691.IX Item "[read:+file;+name]"
1692The same as \fB[read:+\f(BIfile\fB]\fR, but start reading at a line with
1693\&\fB[menu:+\f(BIname\fB]\fR and continuing until \fB[done:+\f(BIname\fB]\fR or
1694\&\fB[done]\fR is encountered.
1695.IP "\fB[dump]\fR" 4
1696.IX Item "[dump]"
1697dump all menuBars to the file \fB/tmp/rxvt\-PID\fR in a format suitable for
1698later rereading.
1699.IP "\fB[rm:name]\fR" 4
1700.IX Item "[rm:name]"
1701remove the named menuBar
1702.IP "\fB[rm] [rm:]\fR" 4
1703.IX Item "[rm] [rm:]"
1704remove the current menuBar
1705.IP "\fB[rm*] [rm:*]\fR" 4
1706.IX Item "[rm*] [rm:*]"
1707remove all menuBars
1708.IP "\fB[swap]\fR" 4
1709.IX Item "[swap]"
1710swap the top two menuBars
1711.IP "\fB[prev]\fR" 4
1712.IX Item "[prev]"
1713access the previous menuBar
1714.IP "\fB[next]\fR" 4
1715.IX Item "[next]"
1716access the next menuBar
1717.IP "\fB[show]\fR" 4
1718.IX Item "[show]"
1719Enable display of the menuBar
1720.IP "\fB[hide]\fR" 4
1721.IX Item "[hide]"
1722Disable display of the menuBar
1723.IP "\fB[pixmap:+\f(BIname\fB]\fR" 4
1724.IX Item "[pixmap:+name]"
1725.PD 0
1726.IP "\fB[pixmap:+\f(BIname\fB;\f(BIscaling\fB]\fR" 4
1727.IX Item "[pixmap:+name;scaling]"
1728.PD
1729(set the background pixmap globally
1730.Sp
1731\&\fBA Future implementation \f(BImay\fB make this local to the menubar\fR)
1732.IP "\fB[:+\f(BIcommand\fB:]\fR" 4
1733.IX Item "[:+command:]"
1734ignore the menu readonly status and issue a \fIcommand\fR to or a menu or
1735menuitem or change the ; a useful shortcut for setting the quick arrows
1736from a menuBar.
1737.PP
1738
1739.IX Xref "menuBarAdd"
1740.Sh "Adding and accessing menus"
1741.IX Subsection "Adding and accessing menus"
1742The following commands may also be \fB+\fR prefixed.
1743.IP "\fB/+\fR" 4
1744.IX Item "/+"
1745access menuBar top level
1746.IP "\fB./+\fR" 4
1747.IX Item "./+"
1748access current menu level
1749.IP "\fB../+\fR" 4
1750.IX Item "../+"
1751access parent menu (1 level up)
1752.IP "\fB../../\fR" 4
1753.IX Item "../../"
1754access parent menu (multiple levels up)
1755.IP "\fB\f(BI/path/\fBmenu\fR" 4
1756.IX Item "/path/menu"
1757add/access menu
1758.IP "\fB\f(BI/path/\fBmenu/*\fR" 4
1759.IX Item "/path/menu/*"
1760add/access menu and clear it if it exists
1761.IP "\fB\f(BI/path/\fB{\-}\fR" 4
1762.IX Item "/path/{-}"
1763add separator
1764.IP "\fB\f(BI/path/\fB{item}\fR" 4
1765.IX Item "/path/{item}"
1766add \fBitem\fR as a label
1767.IP "\fB\f(BI/path/\fB{item} action\fR" 4
1768.IX Item "/path/{item} action"
1769add/alter \fImenuitem\fR with an associated \fIaction\fR
1770.IP "\fB\f(BI/path/\fB{item}{right\-text}\fR" 4
1771.IX Item "/path/{item}{right-text}"
1772add/alter \fImenuitem\fR with \fBright-text\fR as the right-justified text
1773and as the associated \fIaction\fR
1774.IP "\fB\f(BI/path/\fB{item}{rtext} action\fR" 4
1775.IX Item "/path/{item}{rtext} action"
1776add/alter \fImenuitem\fR with an associated \fIaction\fR and with \fBrtext\fR as
1777the right-justified text.
1778.IP "Special characters in \fIaction\fR must be backslash\-escaped:" 4
1779.IX Item "Special characters in action must be backslash-escaped:"
1780\&\fB\ea \eb \eE \ee \en \er \et \eoctal\fR
1781.IP "or in control-character notation:" 4
1782.IX Item "or in control-character notation:"
1783\&\fB^@, ^A .. ^Z .. ^_, ^?\fR
1784.PP
1785To send a string starting with a \fB\s-1NUL\s0\fR (\fB^@\fR) character to the
1786program, start \fIaction\fR with a pair of \fB\s-1NUL\s0\fR characters (\fB^@^@\fR),
1787the first of which will be stripped off and the balance directed to the
1788program. Otherwise if \fIaction\fR begins with \fB\s-1NUL\s0\fR followed by
1789non\-+\fB\s-1NUL\s0\fR characters, the leading \fB\s-1NUL\s0\fR is stripped off and the
1790balance is sent back to rxvt.
1791.PP
1792As a convenience for the many Emacs-type editors, \fIaction\fR may start
1793with \fBM\-\fR (eg, \fBM\-$\fR is equivalent to \fB\eE$\fR) and a \fB\s-1CR\s0\fR will be
1794appended if missed from \fBM\-x\fR commands.
1795.PP
1796As a convenience for issuing XTerm \fB\s-1ESC\s0 ]\fR sequences from a menubar (or
1797quick arrow), a \fB\s-1BEL\s0\fR (\fB^G\fR) will be appended if needed.
1798.IP "For example," 4
1799.IX Item "For example,"
1800\&\fBM\-xapropos\fR is equivalent to \fB\eExapropos\er\fR
1801.IP "and" 4
1802.IX Item "and"
1803\&\fB\eE]703;mona;100\fR is equivalent to \fB\eE]703;mona;100\ea\fR
1804.PP
1805The option \fB{\f(BIright-rtext\fB}\fR will be right\-justified. In the
1806absence of a specified action, this text will be used as the \fIaction\fR
1807as well.
1808.IP "For example," 4
1809.IX Item "For example,"
1810\&\fB/File/{Open}{^X^F}\fR is equivalent to \fB/File/{Open}{^X^F} ^X^F\fR
1811.PP
1812The left label \fIis\fR necessary, since it's used for matching, but
1813implicitly hiding the left label (by using same name for both left and
1814right labels), or explicitly hiding the left label (by preceeding it
1815with a dot), makes it possible to have right-justified text only.
1816.IP "For example," 4
1817.IX Item "For example,"
1818\&\fB/File/{Open}{Open} Open-File-Action\fR
1819.IP "or hiding it" 4
1820.IX Item "or hiding it"
1821\&\fB/File/{.anylabel}{Open} Open-File-Action\fR
1822.PP
1823
1824.IX Xref "menuBarRemove"
1825.Sh "Removing menus"
1826.IX Subsection "Removing menus"
1827.IP "\fB\-/*+\fR" 4
1828.IX Item "-/*+"
1829remove all menus from the menuBar, the same as \fB[clear]\fR
1830.IP "\fB\-+\f(BI/path\fBmenu+\fR" 4
1831.IX Item "-+/pathmenu+"
1832remove menu
1833.IP "\fB\-+\f(BI/path\fB{item}+\fR" 4
1834.IX Item "-+/path{item}+"
1835remove item
1836.IP "\fB\-+\f(BI/path\fB{\-}\fR" 4
1837.IX Item "-+/path{-}"
1838remove separator)
1839.IP "\fB\-/path/menu/*\fR" 4
1840.IX Item "-/path/menu/*"
1841remove all items, separators and submenus from menu
1842.PP
1843
1844.IX Xref "menuBarArrows"
1845.Sh "Quick Arrows"
1846.IX Subsection "Quick Arrows"
1847The menus also provide a hook for \fIquick arrows\fR to provide easier
1848user access. If nothing has been explicitly set, the default is to
1849emulate the curror keys. The syntax permits each arrow to be altered
1850individually or all four at once without re-entering their common
1851beginning/end text. For example, to explicitly associate cursor actions
1852with the arrows, any of the following forms could be used:
1853.IP "\fB<r>+\f(BIRight\fB\fR" 4
1854.IX Item "<r>+Right"
1855.PD 0
1856.IP "\fB<l>+\f(BILeft\fB\fR" 4
1857.IX Item "<l>+Left"
1858.IP "\fB<u>+\f(BIUp\fB\fR" 4
1859.IX Item "<u>+Up"
1860.IP "\fB<d>+\f(BIDown\fB\fR" 4
1861.IX Item "<d>+Down"
1862.PD
1863Define actions for the respective arrow buttons
1864.IP "\fB<b>+\f(BIBegin\fB\fR" 4
1865.IX Item "<b>+Begin"
1866.PD 0
1867.IP "\fB<e>+\f(BIEnd\fB\fR" 4
1868.IX Item "<e>+End"
1869.PD
1870Define common beginning/end parts for \fIquick arrows\fR which used in
1871conjunction with the above <r> <l> <u> <d> constructs
1872.IP "For example, define arrows individually," 4
1873.IX Item "For example, define arrows individually,"
1874.Vb 1
1875\& <u>\eE[A
1876.Ve
1877.Sp
1878.Vb 1
1879\& <d>\eE[B
1880.Ve
1881.Sp
1882.Vb 1
1883\& <r>\eE[C
1884.Ve
1885.Sp
1886.Vb 1
1887\& <l>\eE[D
1888.Ve
1889.IP "or all at once" 4
1890.IX Item "or all at once"
1891.Vb 1
1892\& <u>\eE[AZ<><d>\eE[BZ<><r>\eE[CZ<><l>\eE[D
1893.Ve
1894.IP "or more compactly (factoring out common parts)" 4
1895.IX Item "or more compactly (factoring out common parts)"
1896.Vb 1
1897\& <b>\eE[<u>AZ<><d>BZ<><r>CZ<><l>D
1898.Ve
1899.PP
1900
1901.IX Xref "menuBarSummary"
1902.Sh "Command Summary"
1903.IX Subsection "Command Summary"
1904A short summary of the most \fIcommon\fR commands:
1905.IP "[menu:name]" 4
1906.IX Item "[menu:name]"
1907use an existing named menuBar or start a new one
1908.IP "[menu]" 4
1909.IX Item "[menu]"
1910use the current menuBar
1911.IP "[title:string]" 4
1912.IX Item "[title:string]"
1913set menuBar title
1914.IP "[done]" 4
1915.IX Item "[done]"
1916set menu access to readonly and, if reading from a file, signal \s-1EOF\s0
1917.IP "[done:name]" 4
1918.IX Item "[done:name]"
1919if reading from a file using [read:file;name] signal \s-1EOF\s0
1920.IP "[rm:name]" 4
1921.IX Item "[rm:name]"
1922remove named menuBar(s)
1923.IP "[rm] [rm:]" 4
1924.IX Item "[rm] [rm:]"
1925remove current menuBar
1926.IP "[rm*] [rm:*]" 4
1927.IX Item "[rm*] [rm:*]"
1928remove all menuBar(s)
1929.IP "[swap]" 4
1930.IX Item "[swap]"
1931swap top two menuBars
1932.IP "[prev]" 4
1933.IX Item "[prev]"
1934access the previous menuBar
1935.IP "[next]" 4
1936.IX Item "[next]"
1937access the next menuBar
1938.IP "[show]" 4
1939.IX Item "[show]"
1940map menuBar
1941.IP "[hide]" 4
1942.IX Item "[hide]"
1943unmap menuBar
1944.IP "[pixmap;file]" 4
1945.IX Item "[pixmap;file]"
1946.PD 0
1947.IP "[pixmap;file;scaling]" 4
1948.IX Item "[pixmap;file;scaling]"
1949.PD
1950set a background pixmap
1951.IP "[read:file]" 4
1952.IX Item "[read:file]"
1953.PD 0
1954.IP "[read:file;name]" 4
1955.IX Item "[read:file;name]"
1956.PD
1957read in a menu from a file
1958.IP "[dump]" 4
1959.IX Item "[dump]"
1960dump out all menuBars to /tmp/rxvt\-PID
1961.IP "/" 4
1962access menuBar top level
1963.IP "./" 4
1964.PD 0
1965.IP "../" 4
1966.IP "../../" 4
1967.PD
1968access current or parent menu level
1969.IP "/path/menu" 4
1970.IX Item "/path/menu"
1971add/access menu
1972.IP "/path/{\-}" 4
1973.IX Item "/path/{-}"
1974add separator
1975.IP "/path/{item}{rtext} action" 4
1976.IX Item "/path/{item}{rtext} action"
1977add/alter menu item
1978.IP "\-/*" 4
1979remove all menus from the menuBar
1980.IP "\-/path/menu" 4
1981.IX Item "-/path/menu"
1982remove menu items, separators and submenus from menu
1983.IP "\-/path/menu" 4
1984.IX Item "-/path/menu"
1985remove menu
1986.IP "\-/path/{item}" 4
1987.IX Item "-/path/{item}"
1988remove item
1989.IP "\-/path/{\-}" 4
1990.IX Item "-/path/{-}"
1991remove separator
1992.IP "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End" 4
1993.IX Item "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End"
1994menu quick arrows
1995.SH "XPM" 2233.SH "XPM"
1996.IX Header "XPM" 2234.IX Header "XPM"
1997For 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
1998of \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
1999sequence of scaling/positioning commands separated by semi\-colons. The 2237sequence of scaling/positioning commands separated by semi\-colons. The
… …
20570 Button1 pressed 22950 Button1 pressed
20581 Button2 pressed 22961 Button2 pressed
20592 Button3 pressed 22972 Button3 pressed
20603 button released (X11 mouse report) 22983 button released (X11 mouse report)
2061.TE 2299.TE
2062
2063.PP 2300.PP
2064The 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
2065button was pressed and are added together (X11 mouse report only): 2302button was pressed and are added together (X11 mouse report only):
2066.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
2067.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
… …
2069.TS 2306.TS
2070l l . 2307l l .
20714 Shift 23084 Shift
20728 Meta 23098 Meta
207316 Control 231016 Control
207432 Double Click (Rxvt extension) 231132 Double Click (rxvt extension)
2075.TE 2312.TE
2076
2077Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR 2313Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR
2078.Sp 2314.Sp
2079Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR 2315Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR
2080.SH "Key Codes" 2316.SH "Key Codes"
2081.IX Header "Key Codes" 2317.IX Header "Key Codes"
… …
2145XK_KP_6 6 ESC O v 2381XK_KP_6 6 ESC O v
2146XK_KP_7 7 ESC O w 2382XK_KP_7 7 ESC O w
2147XK_KP_8 8 ESC O x 2383XK_KP_8 8 ESC O x
2148XK_KP_9 9 ESC O y 2384XK_KP_9 9 ESC O y
2149.TE 2385.TE
2150
2151.SH "CONFIGURE OPTIONS" 2386.SH "CONFIGURE OPTIONS"
2152.IX Header "CONFIGURE OPTIONS" 2387.IX Header "CONFIGURE OPTIONS"
2153General hint: if you get compile errors, then likely your configuration 2388General hint: if you get compile errors, then likely your configuration
2154hasn'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
2155\&./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
2156so 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
2157report 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
2158<rxvt@schmorp.de>. 2393Lehmann <rxvt@schmorp.de>.
2394.PP
2395All
2159.IP "\-\-enable\-everything" 4 2396.IP "\-\-enable\-everything" 4
2160.IX Item "--enable-everything" 2397.IX Item "--enable-everything"
2161Add support for all non-multichoice options listed in \*(L"./configure 2398Add (or remove) support for all non-multichoice options listed in \*(L"./configure
2162\&\-\-help\*(R". Note that unlike other enable options this is order dependant. 2399\&\-\-help\*(R".
2400.Sp
2163You can specify this and then disable options which this enables by 2401You can specify this and then disable options you do not like by
2164\&\fIfollowing\fR this with the appropriate commands. 2402\&\fIfollowing\fR this with the appropriate \f(CW\*(C`\-\-disable\-...\*(C'\fR arguments,
2165.IP "\-\-enable\-xft" 4 2403or you can start with a minimal configuration by specifying
2166.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)"
2167Add support for Xft (anti\-aliases, among others) fonts. Xft fonts are 2408Add support for Xft (anti\-aliases, among others) fonts. Xft fonts are
2168slower 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
2169don't pay for them. 2410don't pay for them.
2170.IP "\-\-enable\-font\-styles" 4 2411.IP "\-\-enable\-font\-styles (default: on)" 4
2171.IX Item "--enable-font-styles" 2412.IX Item "--enable-font-styles (default: on)"
2172Add 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
2173styles. The fonts can be set manually or automatically. 2414styles. The fonts can be set manually or automatically.
2174.IP "\-\-with\-codesets=NAME,..." 4 2415.IP "\-\-with\-codesets=NAME,... (default: all)" 4
2175.IX Item "--with-codesets=NAME,..." 2416.IX Item "--with-codesets=NAME,... (default: all)"
2176Compile in support for additional codeset (encoding) groups (eu, vn are 2417Compile in support for additional codeset (encoding) groups (\f(CW\*(C`eu\*(C'\fR, \f(CW\*(C`vn\*(C'\fR
2177always compiled in, which includes most 8\-bit character sets). These 2418are always compiled in, which includes most 8\-bit character sets). These
2178codeset tables are currently only used for driving X11 core fonts, they 2419codeset tables are used for driving X11 core fonts, they are not required
2179are not required for Xft fonts. Compiling them in will make your binary 2420for Xft fonts, although having them compiled in lets rxvt-unicode choose
2180bigger (together about 700kB), but it doesn't increase memory usage unless 2421replacement fonts more intelligently. Compiling them in will make your
2422binary bigger (all of together cost about 700kB), but it doesn't increase
2181you use an X11 font requiring one of these encodings. 2423memory usage unless you use a font requiring one of these encodings.
2182.TS 2424.TS
2183l l . 2425l l .
2184all all available codeset groups 2426all all available codeset groups
2185zh common chinese encodings 2427zh common chinese encodings
2186zh_ext rarely used but very big chinese encodigs 2428zh_ext rarely used but very big chinese encodigs
2187jp common japanese encodings 2429jp common japanese encodings
2188jp_ext rarely used but big japanese encodings 2430jp_ext rarely used but big japanese encodings
2189kr korean encodings 2431kr korean encodings
2190.TE 2432.TE
2191
2192.IP "\-\-enable\-xim" 4 2433.IP "\-\-enable\-xim (default: on)" 4
2193.IX Item "--enable-xim" 2434.IX Item "--enable-xim (default: on)"
2194Add 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
2195alternative input methods (e.g. kinput2) and will also correctly 2436alternative input methods (e.g. kinput2) and will also correctly
2196set up the input for people using dead keys or compose keys. 2437set up the input for people using dead keys or compose keys.
2197.IP "\-\-enable\-unicode3" 4 2438.IP "\-\-enable\-unicode3 (default: off)" 4
2198.IX Item "--enable-unicode3" 2439.IX Item "--enable-unicode3 (default: off)"
2440Recommended to stay off unless you really need non-BMP characters.
2441.Sp
2199Enable direct support for displaying unicode codepoints above 2442Enable direct support for displaying unicode codepoints above
220065535 (the basic multilingual page). This increases storage 244365535 (the basic multilingual page). This increases storage
2201requirements 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
2202support these extra characters, but Xft does. 2445support these extra characters, but Xft does.
2203.Sp 2446.Sp
2204Please note that rxvt-unicode can store unicode code points >65535 2447Please note that rxvt-unicode can store unicode code points >65535
2205even without this flag, but the number of such characters is 2448even without this flag, but the number of such characters is
2206limited to a view thousand (shared with combining characters, 2449limited to a view thousand (shared with combining characters,
2207see next switch), and right now rxvt-unicode cannot display them 2450see next switch), and right now rxvt-unicode cannot display them
2208(input/output and cut&paste still work, though). 2451(input/output and cut&paste still work, though).
2209.IP "\-\-enable\-combining" 4 2452.IP "\-\-enable\-combining (default: on)" 4
2210.IX Item "--enable-combining" 2453.IX Item "--enable-combining (default: on)"
2211Enable automatic composition of combining characters into 2454Enable automatic composition of combining characters into
2212composite characters. This is required for proper viewing of text 2455composite characters. This is required for proper viewing of text
2213where accents are encoded as seperate unicode characters. This is 2456where accents are encoded as seperate unicode characters. This is
2214done by using precomposited characters when available or creating 2457done by using precomposited characters when available or creating
2215new pseudo-characters when no precomposed form exists. 2458new pseudo-characters when no precomposed form exists.
2216.Sp 2459.Sp
2217Without \-\-enable\-unicode3, the number of additional precomposed 2460Without \-\-enable\-unicode3, the number of additional precomposed
2218characters is rather limited (2048, if this is full, rxvt will use the 2461characters is somewhat limited (the 6400 private use characters will be
2219private use area, extending the number of combinations to 8448). With 2462(ab\-)used). With \-\-enable\-unicode3, no practical limit exists.
2220\&\-\-enable\-unicode3, no practical limit exists. This will also enable 2463.Sp
2221storage of characters >65535. 2464This option will also enable storage (but not display) of characters
2465beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified.
2222.Sp 2466.Sp
2223The combining table also contains entries for arabic presentation forms, 2467The combining table also contains entries for arabic presentation forms,
2224but these are not currently used. Bug me if you want these to be used. 2468but these are not currently used. Bug me if you want these to be used (and
2469tell me how these are to be used...).
2225.IP "\-\-enable\-fallback(=CLASS)" 4 2470.IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4
2226.IX Item "--enable-fallback(=CLASS)" 2471.IX Item "--enable-fallback(=CLASS) (default: Rxvt)"
2227When reading resource settings, also read settings for class \s-1CLASS\s0 2472When reading resource settings, also read settings for class \s-1CLASS\s0. To
2228(default: Rxvt). To disable resource fallback use \-\-disable\-fallback. 2473disable resource fallback use \-\-disable\-fallback.
2229.IP "\-\-with\-res\-name=NAME" 4 2474.IP "\-\-with\-res\-name=NAME (default: urxvt)" 4
2230.IX Item "--with-res-name=NAME" 2475.IX Item "--with-res-name=NAME (default: urxvt)"
2231Use the given name (default: urxvt) as default application name when 2476Use the given name as default application name when
2232reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt. 2477reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt.
2233.IP "\-\-with\-res\-class=CLASS" 4 2478.IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4
2234.IX Item "--with-res-class=CLASS" 2479.IX Item "--with-res-class=CLASS /default: URxvt)"
2235Use the given class (default: URxvt) as default application class 2480Use the given class as default application class
2236when reading resources. Specify \-\-with\-res\-class=Rxvt to replace 2481when reading resources. Specify \-\-with\-res\-class=Rxvt to replace
2237rxvt. 2482rxvt.
2238.IP "\-\-enable\-utmp" 4 2483.IP "\-\-enable\-utmp (default: on)" 4
2239.IX Item "--enable-utmp" 2484.IX Item "--enable-utmp (default: on)"
2240Write 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
2241start of rxvt execution and delete information when rxvt exits. 2486start of rxvt execution and delete information when rxvt exits.
2242.IP "\-\-enable\-wtmp" 4 2487.IP "\-\-enable\-wtmp (default: on)" 4
2243.IX Item "--enable-wtmp" 2488.IX Item "--enable-wtmp (default: on)"
2244Write 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
2245start of rxvt execution and write logout when rxvt exits. This 2490start of rxvt execution and write logout when rxvt exits. This
2246option requires \-\-enable\-utmp to also be specified. 2491option requires \-\-enable\-utmp to also be specified.
2247.IP "\-\-enable\-lastlog" 4 2492.IP "\-\-enable\-lastlog (default: on)" 4
2248.IX Item "--enable-lastlog" 2493.IX Item "--enable-lastlog (default: on)"
2249Write user and tty to lastlog file (used by programs like 2494Write user and tty to lastlog file (used by programs like
2250\&\fIlastlogin\fR) at start of rxvt execution. This option requires 2495\&\fIlastlogin\fR) at start of rxvt execution. This option requires
2251\&\-\-enable\-utmp to also be specified. 2496\&\-\-enable\-utmp to also be specified.
2252.IP "\-\-enable\-xpm\-background" 4 2497.IP "\-\-enable\-xpm\-background (default: on)" 4
2253.IX Item "--enable-xpm-background" 2498.IX Item "--enable-xpm-background (default: on)"
2254Add support for \s-1XPM\s0 background pixmaps. 2499Add support for \s-1XPM\s0 background pixmaps.
2255.IP "\-\-enable\-transparency" 4 2500.IP "\-\-enable\-transparency (default: on)" 4
2256.IX Item "--enable-transparency" 2501.IX Item "--enable-transparency (default: on)"
2257Add support for inheriting parent backgrounds thus giving a fake 2502Add support for inheriting parent backgrounds thus giving a fake
2258transparency to the term. 2503transparency to the term.
2259.IP "\-\-enable\-fading" 4 2504.IP "\-\-enable\-fading (default: on)" 4
2260.IX Item "--enable-fading" 2505.IX Item "--enable-fading (default: on)"
2261Add 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).
2262.IP "\-\-enable\-tinting" 4 2507.IP "\-\-enable\-tinting (default: on)" 4
2263.IX Item "--enable-tinting" 2508.IX Item "--enable-tinting (default: on)"
2264Add support for tinting of transparent backgrounds. 2509Add support for tinting of transparent backgrounds (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR).
2265.IP "\-\-enable\-menubar" 4
2266.IX Item "--enable-menubar"
2267Add support for our menu bar system (this interacts badly with
2268dynamic locale switching currently).
2269.IP "\-\-enable\-rxvt\-scroll" 4 2510.IP "\-\-enable\-rxvt\-scroll (default: on)" 4
2270.IX Item "--enable-rxvt-scroll" 2511.IX Item "--enable-rxvt-scroll (default: on)"
2271Add support for the original rxvt scrollbar. 2512Add support for the original rxvt scrollbar.
2272.IP "\-\-enable\-next\-scroll" 4 2513.IP "\-\-enable\-next\-scroll (default: on)" 4
2273.IX Item "--enable-next-scroll" 2514.IX Item "--enable-next-scroll (default: on)"
2274Add support for a NeXT-like scrollbar. 2515Add support for a NeXT-like scrollbar.
2275.IP "\-\-enable\-xterm\-scroll" 4 2516.IP "\-\-enable\-xterm\-scroll (default: on)" 4
2276.IX Item "--enable-xterm-scroll" 2517.IX Item "--enable-xterm-scroll (default: on)"
2277Add support for an Xterm-like scrollbar. 2518Add support for an Xterm-like scrollbar.
2278.IP "\-\-enable\-plain\-scroll" 4 2519.IP "\-\-enable\-plain\-scroll (default: on)" 4
2279.IX Item "--enable-plain-scroll" 2520.IX Item "--enable-plain-scroll (default: on)"
2280Add support for a very unobtrusive, plain-looking scrollbar that 2521Add support for a very unobtrusive, plain-looking scrollbar that
2281is the favourite of the rxvt-unicode author, having used it for 2522is the favourite of the rxvt-unicode author, having used it for
2282many years. 2523many years.
2283.IP "\-\-enable\-half\-shadow" 4
2284.IX Item "--enable-half-shadow"
2285Make shadows on the scrollbar only half the normal width & height.
2286only applicable to rxvt scrollbars.
2287.IP "\-\-enable\-ttygid" 4 2524.IP "\-\-enable\-ttygid (default: off)" 4
2288.IX Item "--enable-ttygid" 2525.IX Item "--enable-ttygid (default: off)"
2289Change 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
2290your system uses this type of security. 2527your system uses this type of security.
2291.IP "\-\-disable\-backspace\-key" 4 2528.IP "\-\-disable\-backspace\-key" 4
2292.IX Item "--disable-backspace-key" 2529.IX Item "--disable-backspace-key"
2293Disable 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.
2294do it.
2295.IP "\-\-disable\-delete\-key" 4 2531.IP "\-\-disable\-delete\-key" 4
2296.IX Item "--disable-delete-key" 2532.IX Item "--disable-delete-key"
2297Disable 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
2298do it. 2534do it.
2299.IP "\-\-disable\-resources" 4 2535.IP "\-\-disable\-resources" 4
2300.IX Item "--disable-resources" 2536.IX Item "--disable-resources"
2301Remove all resources checking. 2537Removes any support for resource checking.
2302.IP "\-\-enable\-xgetdefault" 4
2303.IX Item "--enable-xgetdefault"
2304Make resources checking via \fIXGetDefault()\fR instead of our small
2305version which only checks ~/.Xdefaults, or if that doesn't exist then
2306~/.Xresources.
2307.Sp
2308Please note that nowadays, things like \s-1XIM\s0 will automatically pull in and
2309use the full X resource manager, so the overhead of using it might be very
2310small, if nonexistant.
2311.IP "\-\-enable\-strings" 4
2312.IX Item "--enable-strings"
2313Add support for our possibly faster \fImemset()\fR function and other
2314various routines, overriding your system's versions which may
2315have been hand-crafted in assembly or may require extra libraries
2316to link in. (this breaks ANSI-C rules and has problems on many
2317GNU/Linux systems).
2318.IP "\-\-disable\-swapscreen" 4 2538.IP "\-\-disable\-swapscreen" 4
2319.IX Item "--disable-swapscreen" 2539.IX Item "--disable-swapscreen"
2320Remove support for swap screen. 2540Remove support for secondary/swap screen.
2321.IP "\-\-enable\-frills" 4 2541.IP "\-\-enable\-frills (default: on)" 4
2322.IX Item "--enable-frills" 2542.IX Item "--enable-frills (default: on)"
2323Add 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
2324have. 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
2325disable this. 2545disable this.
2326.Sp 2546.Sp
2327A 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
2328in combination with other switches) is: 2548in combination with other switches) is:
2329.Sp 2549.Sp
2550.Vb 10
2551\& MWM\-hints
2552\& EWMH\-hints (pid, utf8 names) and protocols (ping)
2553\& seperate underline colour (\-underlineColor)
2554\& settable border widths and borderless switch (\-w, \-b, \-bl)
2555\& visual depth selection (\-depth)
2556\& settable extra linespacing /\-lsp)
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
2330.Vb 11 2571.Vb 11
2331\& MWM-hints 2572\& some round\-trip time optimisations
2332\& seperate underline colour 2573\& nearest color allocation on pseudocolor screens
2333\& settable border widths and borderless switch 2574\& UTF8_STRING supporr for selection
2334\& settable extra linespacing 2575\& sgr modes 90..97 and 100..107
2335\& extra window properties (e.g. UTF-8 window names and PID)
2336\& iso-14755-2 and -3, and visual feedback
2337\& backindex and forwardindex escape sequence 2576\& backindex and forwardindex escape sequences
2577\& view change/zero scorllback esacpe sequences
2578\& locale switching escape sequence
2338\& window op and locale change escape sequences 2579\& window op and some xterm/OSC escape sequences
2339\& tripleclickwords 2580\& rectangular selections
2340\& settable insecure mode 2581\& trailing space removal for selections
2341\& keysym remapping support 2582\& verbose X error handling
2342.Ve 2583.Ve
2343.IP "\-\-enable\-iso14755" 4 2584.IP "\-\-enable\-iso14755 (default: on)" 4
2344.IX Item "--enable-iso14755" 2585.IX Item "--enable-iso14755 (default: on)"
2345Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or 2586Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or
2346\&\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
2347\&\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
2348this switch. 2589this switch.
2349.IP "\-\-enable\-keepscrolling" 4 2590.IP "\-\-enable\-keepscrolling (default: on)" 4
2350.IX Item "--enable-keepscrolling" 2591.IX Item "--enable-keepscrolling (default: on)"
2351Add support for continual scrolling of the display when you hold 2592Add support for continual scrolling of the display when you hold
2352the mouse button down on a scrollbar arrow. 2593the mouse button down on a scrollbar arrow.
2353.IP "\-\-enable\-mousewheel" 4 2594.IP "\-\-enable\-mousewheel (default: on)" 4
2354.IX Item "--enable-mousewheel" 2595.IX Item "--enable-mousewheel (default: on)"
2355Add support for scrolling via mouse wheel or buttons 4 & 5. 2596Add support for scrolling via mouse wheel or buttons 4 & 5.
2356.IP "\-\-enable\-slipwheeling" 4 2597.IP "\-\-enable\-slipwheeling (default: on)" 4
2357.IX Item "--enable-slipwheeling" 2598.IX Item "--enable-slipwheeling (default: on)"
2358Add support for continual scrolling (using the mouse wheel as an 2599Add support for continual scrolling (using the mouse wheel as an
2359accelerator) while the control key is held down. This option 2600accelerator) while the control key is held down. This option
2360requires \-\-enable\-mousewheel to also be specified. 2601requires \-\-enable\-mousewheel to also be specified.
2361.IP "\-\-disable\-new\-selection" 4 2602.IP "\-\-disable\-new\-selection" 4
2362.IX Item "--disable-new-selection" 2603.IX Item "--disable-new-selection"
2363Remove support for mouse selection style like that of xterm. 2604Remove support for mouse selection style like that of xterm.
2364.IP "\-\-enable\-dmalloc" 4 2605.IP "\-\-enable\-dmalloc (default: off)" 4
2365.IX Item "--enable-dmalloc" 2606.IX Item "--enable-dmalloc (default: off)"
2366Use Gray Watson's malloc \- which is good for debugging See 2607Use Gray Watson's malloc \- which is good for debugging See
2367http://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
2368next 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
2369\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. 2610\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places.
2370.Sp 2611.Sp
2371You can only use either this option and the following (should 2612You can only use either this option and the following (should
2372you use either) . 2613you use either) .
2373.IP "\-\-enable\-dlmalloc" 4 2614.IP "\-\-enable\-dlmalloc (default: off)" 4
2374.IX Item "--enable-dlmalloc" 2615.IX Item "--enable-dlmalloc (default: off)"
2375Use Doug Lea's malloc \- which is good for a production version 2616Use Doug Lea's malloc \- which is good for a production version
2376See <http://g.oswego.edu/dl/html/malloc.html> for details. 2617See <http://g.oswego.edu/dl/html/malloc.html> for details.
2377.IP "\-\-enable\-smart\-resize" 4 2618.IP "\-\-enable\-smart\-resize (default: on)" 4
2378.IX Item "--enable-smart-resize" 2619.IX Item "--enable-smart-resize (default: on)"
2379Add smart growth/shrink behaviour when changing font size via from hot 2620Add smart growth/shrink behaviour when changing font size via hot
2380keys. 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
2381closest to a corner of the screen. 2622the screen in a fixed position.
2382.IP "\-\-enable\-cursor\-blink" 4
2383.IX Item "--enable-cursor-blink"
2384Add support for a blinking cursor.
2385.IP "\-\-enable\-pointer\-blank" 4 2623.IP "\-\-enable\-pointer\-blank (default: on)" 4
2386.IX Item "--enable-pointer-blank" 2624.IX Item "--enable-pointer-blank (default: on)"
2387Add 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.
2388.IP "\-\-with\-name=NAME" 4 2633.IP "\-\-with\-name=NAME (default: urxvt)" 4
2389.IX Item "--with-name=NAME" 2634.IX Item "--with-name=NAME (default: urxvt)"
2390Set the basename for the installed binaries (default: \f(CW\*(C`urxvt\*(C'\fR, resulting 2635Set the basename for the installed binaries, resulting
2391in \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
2392\&\f(CW\*(C`rxvt\*(C'\fR. 2637\&\f(CW\*(C`rxvt\*(C'\fR.
2393.IP "\-\-with\-term=NAME" 4 2638.IP "\-\-with\-term=NAME (default: rxvt\-unicode)" 4
2394.IX Item "--with-term=NAME" 2639.IX Item "--with-term=NAME (default: rxvt-unicode)"
2395Change the environmental variable for the terminal to \s-1NAME\s0 (default 2640Change the environmental variable for the terminal to \s-1NAME\s0.
2396\&\f(CW\*(C`rxvt\-unicode\*(C'\fR)
2397.IP "\-\-with\-terminfo=PATH" 4 2641.IP "\-\-with\-terminfo=PATH" 4
2398.IX Item "--with-terminfo=PATH" 2642.IX Item "--with-terminfo=PATH"
2399Change the environmental variable for the path to the terminfo tree to 2643Change the environmental variable for the path to the terminfo tree to
2400\&\s-1PATH\s0. 2644\&\s-1PATH\s0.
2401.IP "\-\-with\-x" 4 2645.IP "\-\-with\-x" 4
… …
2414.IX Header "AUTHORS" 2658.IX Header "AUTHORS"
2415Marc Lehmann <rxvt@schmorp.de> converted this document to pod and 2659Marc Lehmann <rxvt@schmorp.de> converted this document to pod and
2416reworked it from the original Rxvt documentation, which was done by Geoff 2660reworked it from the original Rxvt documentation, which was done by Geoff
2417Wing <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
2418sources. 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