ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.html
Revision: 1.81
Committed: Sun Jun 24 22:12:18 2007 UTC (17 years, 1 month ago) by root
Content type: text/html
Branch: MAIN
Changes since 1.80: +1358 -1809 lines
Log Message:
use pod2xhtml and our stylesheet

File Contents

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