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