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