… | |
… | |
14 | |
14 | |
15 | <li><a href="#name">NAME</a></li> |
15 | <li><a href="#name">NAME</a></li> |
16 | <li><a href="#synopsis">SYNOPSIS</a></li> |
16 | <li><a href="#synopsis">SYNOPSIS</a></li> |
17 | <li><a href="#description">DESCRIPTION</a></li> |
17 | <li><a href="#description">DESCRIPTION</a></li> |
18 | <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li> |
18 | <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li> |
|
|
19 | <ul> |
|
|
20 | |
|
|
21 | <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> |
|
|
22 | <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> |
|
|
23 | <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> |
|
|
24 | <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> |
|
|
25 | <li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li> |
|
|
26 | <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> |
|
|
27 | <li><a href="#isn_t_rxvt_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt supposed to be small? Don't all those features bloat?</a></li> |
|
|
28 | <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li> |
|
|
29 | <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> |
|
|
30 | <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> |
|
|
31 | <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> |
|
|
32 | <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> |
|
|
33 | <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> |
|
|
34 | <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> |
|
|
35 | <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> |
|
|
36 | <li><a href="#bash_s_readline_does_not_work_correctly_under_rxvt_"><code>bash</code>'s readline does not work correctly under rxvt.</a></li> |
|
|
37 | <li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li> |
|
|
38 | <li><a href="#why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></li> |
|
|
39 | <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> |
|
|
40 | <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> |
|
|
41 | <li><a href="#why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></li> |
|
|
42 | <li><a href="#my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></li> |
|
|
43 | <li><a href="#rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></li> |
|
|
44 | <li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</a></li> |
|
|
45 | <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> |
|
|
46 | <li><a href="#how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></li> |
|
|
47 | <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> |
|
|
48 | <li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li> |
|
|
49 | <li><a href="#on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></li> |
|
|
50 | <li><a href="#my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></li> |
|
|
51 | <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> |
|
|
52 | <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> |
|
|
53 | <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> |
|
|
54 | <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> |
|
|
55 | <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> |
|
|
56 | <li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li> |
|
|
57 | <li><a href="#how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></li> |
|
|
58 | <li><a href="#is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></li> |
|
|
59 | <li><a href="#can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></li> |
|
|
60 | <li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li> |
|
|
61 | <li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li> |
|
|
62 | <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> |
|
|
63 | <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> |
|
|
64 | <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> |
|
|
65 | <li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li> |
|
|
66 | <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> |
|
|
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_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li> |
|
|
69 | <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> |
|
|
70 | <li><a href="#how_can_i_start_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</a></li> |
|
|
71 | <li><a href="#what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></li> |
|
|
72 | <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> |
|
|
73 | <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_mappings_that_rxvtunicode_doesn_t_recognize_">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize.</a></li> |
|
|
74 | <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li> |
|
|
75 | <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> |
|
|
76 | <li><a href="#how_do_i_compile_the_manual_pages_for_myself">How do I compile the manual pages for myself?</a></li> |
|
|
77 | <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> |
|
|
78 | </ul> |
|
|
79 | |
19 | <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> |
80 | <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> |
20 | <li><a href="#description">DESCRIPTION</a></li> |
81 | <li><a href="#description">DESCRIPTION</a></li> |
21 | <li><a href="#definitions">Definitions</a></li> |
82 | <li><a href="#definitions">Definitions</a></li> |
22 | <li><a href="#values">Values</a></li> |
83 | <li><a href="#values">Values</a></li> |
23 | <li><a href="#escape_sequences">Escape Sequences</a></li> |
84 | <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> |
85 | <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> |
86 | <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> |
87 | <li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li> |
27 | <li><a href="#menubar">menuBar</a></li> |
|
|
28 | <ul> |
|
|
29 | |
|
|
30 | <li><a href="#overview_of_menubar_operation">Overview of menuBar operation</a></li> |
|
|
31 | <li><a href="#commands">Commands</a></li> |
|
|
32 | <li><a href="#adding_and_accessing_menus">Adding and accessing menus</a></li> |
|
|
33 | <li><a href="#removing_menus">Removing menus</a></li> |
|
|
34 | <li><a href="#quick_arrows">Quick Arrows</a></li> |
|
|
35 | <li><a href="#command_summary">Command Summary</a></li> |
|
|
36 | </ul> |
|
|
37 | |
|
|
38 | <li><a href="#xpm">XPM</a></li> |
88 | <li><a href="#xpm">XPM</a></li> |
39 | <li><a href="#mouse_reporting">Mouse Reporting</a></li> |
89 | <li><a href="#mouse_reporting">Mouse Reporting</a></li> |
40 | <li><a href="#key_codes">Key Codes</a></li> |
90 | <li><a href="#key_codes">Key Codes</a></li> |
41 | <li><a href="#configure_options">CONFIGURE OPTIONS</a></li> |
91 | <li><a href="#configure_options">CONFIGURE OPTIONS</a></li> |
42 | <li><a href="#authors">AUTHORS</a></li> |
92 | <li><a href="#authors">AUTHORS</a></li> |
… | |
… | |
65 | </p> |
115 | </p> |
66 | <hr /> |
116 | <hr /> |
67 | <h1><a name="description">DESCRIPTION</a></h1> |
117 | <h1><a name="description">DESCRIPTION</a></h1> |
68 | <p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
118 | <p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
69 | all escape sequences, and other background information.</p> |
119 | all escape sequences, and other background information.</p> |
70 | <p>The newest version of this document is |
120 | <p>The newest version of this document is also available on the World Wide Web at |
71 | also available on the World Wide Web at |
|
|
72 | <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> |
121 | <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> |
73 | <p> |
122 | <p> |
74 | </p> |
123 | </p> |
75 | <hr /> |
124 | <hr /> |
76 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
125 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
77 | <dl> |
126 | <p> |
|
|
127 | </p> |
|
|
128 | <h2><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></h2> |
|
|
129 | <p>If you want to select e.g. alphanumeric words, you can use the following |
|
|
130 | setting:</p> |
|
|
131 | <pre> |
|
|
132 | URxvt.selection.pattern-0: ([[:word:]]+)</pre> |
|
|
133 | <p>If you click more than twice, the selection will be extended |
|
|
134 | more and more.</p> |
|
|
135 | <p>To get a selection that is very similar to the old code, try this pattern:</p> |
|
|
136 | <pre> |
|
|
137 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)</pre> |
|
|
138 | <p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also |
|
|
139 | selects words like the old code.</p> |
|
|
140 | <p> |
|
|
141 | </p> |
|
|
142 | <h2><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></h2> |
|
|
143 | <p>You can disable the perl extension completely by setting the |
|
|
144 | <strong>perl-ext-common</strong> resource to the empty string, which also keeps |
|
|
145 | rxvt-unicode from initialising perl, saving memory.</p> |
|
|
146 | <p>If you only want to disable specific features, you first have to |
|
|
147 | identify which perl extension is responsible. For this, read the section |
|
|
148 | <strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For |
|
|
149 | example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify |
|
|
150 | this <strong>perl-ext-common</strong> resource:</p> |
|
|
151 | <pre> |
|
|
152 | URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre> |
|
|
153 | <p>This will keep the default extensions, but disable the two popup |
|
|
154 | extensions. Some extensions can also be configured, for example, |
|
|
155 | scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any |
|
|
156 | other combination either by setting the <strong>searchable-scrollback</strong> resource:</p> |
|
|
157 | <pre> |
|
|
158 | URxvt.searchable-scrollback: CM-s</pre> |
|
|
159 | <p> |
|
|
160 | </p> |
|
|
161 | <h2><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></h2> |
|
|
162 | <p>See next entry.</p> |
|
|
163 | <p> |
|
|
164 | </p> |
|
|
165 | <h2><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></h2> |
|
|
166 | <p>These are caused by the <code>readline</code> perl extension. Under normal |
|
|
167 | circumstances, it will move your cursor around when you click into the |
|
|
168 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
169 | but when running a program that doesn't parse cursor movements or in some |
|
|
170 | cases during rlogin sessions, it fails to detect this properly.</p> |
|
|
171 | <p>You can permamently switch this feature off by disabling the <code>readline</code> |
|
|
172 | extension:</p> |
|
|
173 | <pre> |
|
|
174 | URxvt.perl-ext-common: default,-readline</pre> |
|
|
175 | <p> |
|
|
176 | </p> |
|
|
177 | <h2><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h2> |
|
|
178 | <p>Well, why, indeed? It does, in a way very similar to other X |
|
|
179 | applications. Most importantly, this means that if you or your OS loads |
|
|
180 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
181 | ignore any resource files in your home directory. It will only read |
|
|
182 | <em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p> |
|
|
183 | <p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that |
|
|
184 | resources are loaded into your X-server. In this case, you have to |
|
|
185 | re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p> |
|
|
186 | <p>Also consider the form resources have to use:</p> |
|
|
187 | <pre> |
|
|
188 | URxvt.resource: value</pre> |
|
|
189 | <p>If you want to use another form (there are lots of different ways of |
|
|
190 | specifying resources), make sure you understand wether and why it |
|
|
191 | works. If unsure, use the form above.</p> |
|
|
192 | <p> |
|
|
193 | </p> |
|
|
194 | <h2><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></h2> |
|
|
195 | <p>First of all, transparency isn't officially supported in rxvt-unicode, so |
|
|
196 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
197 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
198 | of passage: ... and you failed.</p> |
|
|
199 | <p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option |
|
|
200 | descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p> |
|
|
201 | <p>1. Use inheritPixmap:</p> |
|
|
202 | <pre> |
|
|
203 | Esetroot wallpaper.jpg |
|
|
204 | rxvt -ip -tint red -sh 40</pre> |
|
|
205 | <p>That works. If you think it doesn't, you lack transparency and tinting |
|
|
206 | support, or you are unable to read.</p> |
|
|
207 | <p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
|
|
208 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
209 | your picture with gimp:</p> |
|
|
210 | <pre> |
|
|
211 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
212 | rxvt -pixmap background.xpm -pe automove-background</pre> |
|
|
213 | <p>That works. If you think it doesn't, you lack XPM and Perl support, or you |
|
|
214 | are unable to read.</p> |
|
|
215 | <p>3. Use an ARGB visual:</p> |
|
|
216 | <pre> |
|
|
217 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre> |
|
|
218 | <p>This requires XFT support, and the support of your X-server. If that |
|
|
219 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
220 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
221 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
222 | doesn't mean that your WM has the required kludges in place.</p> |
|
|
223 | <p>4. Use xcompmgr and let it do the job:</p> |
|
|
224 | <pre> |
|
|
225 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
226 | -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre> |
|
|
227 | <p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code> |
|
|
228 | by other values to change the degree of opacity. If it doesn't work and |
|
|
229 | your server crashes, you got to keep the pieces.</p> |
|
|
230 | <p> |
|
|
231 | </p> |
78 | <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 /> |
232 | <h2><a name="isn_t_rxvt_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt supposed to be small? Don't all those features bloat?</a></h2> |
79 | </dt> |
|
|
80 | <dd> |
|
|
81 | I often get asked about this, and I think, no, they didn't cause extra |
233 | <p>I often get asked about this, and I think, no, they didn't cause extra |
82 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
234 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
83 | that the urxvt binary is larger (due to some encoding tables always being |
235 | that the urxvt binary is larger (due to some encoding tables always being |
84 | compiled in), but it actually uses less memory (RSS) after startup. Even |
236 | compiled in), but it actually uses less memory (RSS) after startup. Even |
85 | with <code>--disable-everything</code>, this comparison is a bit unfair, as many |
237 | with <code>--disable-everything</code>, this comparison is a bit unfair, as many |
86 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
238 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
87 | already in use in this mode. |
239 | already in use in this mode.</p> |
88 | </dd> |
|
|
89 | <dd> |
|
|
90 | <pre> |
240 | <pre> |
91 | text data bss drs rss filename |
241 | text data bss drs rss filename |
92 | 98398 1664 24 15695 1824 rxvt --disable-everything |
242 | 98398 1664 24 15695 1824 rxvt --disable-everything |
93 | 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> |
243 | 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> |
94 | </dd> |
|
|
95 | <dd> |
|
|
96 | <p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft |
244 | <p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft |
97 | and full locale/XIM support which are quite bloaty inside libX11 and my |
245 | and full locale/XIM support which are quite bloaty inside libX11 and my |
98 | libc), the two diverge, but not unreasnobaly so.</p> |
246 | libc), the two diverge, but not unreasnobaly so.</p> |
99 | </dd> |
|
|
100 | <dd> |
|
|
101 | <pre> |
247 | <pre> |
102 | text data bss drs rss filename |
248 | text data bss drs rss filename |
103 | 163431 2152 24 20123 2060 rxvt --enable-everything |
249 | 163431 2152 24 20123 2060 rxvt --enable-everything |
104 | 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre> |
250 | 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre> |
105 | </dd> |
|
|
106 | <dd> |
|
|
107 | <p>The very large size of the text section is explained by the east-asian |
251 | <p>The very large size of the text section is explained by the east-asian |
108 | encoding tables, which, if unused, take up disk space but nothing else |
252 | encoding tables, which, if unused, take up disk space but nothing else |
109 | and can be compiled out unless you rely on X11 core fonts that use those |
253 | and can be compiled out unless you rely on X11 core fonts that use those |
110 | encodings. The BSS size comes from the 64k emergency buffer that my c++ |
254 | encodings. The BSS size comes from the 64k emergency buffer that my c++ |
111 | compiler allocates (but of course doesn't use unless you are out of |
255 | compiler allocates (but of course doesn't use unless you are out of |
112 | memory). Also, using an xft font instead of a core font immediately adds a |
256 | memory). Also, using an xft font instead of a core font immediately adds a |
113 | few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when |
257 | few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when |
114 | not used.</p> |
258 | not used.</p> |
115 | </dd> |
|
|
116 | <dd> |
|
|
117 | <p>Of course, due to every character using two or four bytes instead of one, |
259 | <p>Of course, due to every character using two or four bytes instead of one, |
118 | a large scrollback buffer will ultimately make rxvt-unicode use more |
260 | a large scrollback buffer will ultimately make rxvt-unicode use more |
119 | memory.</p> |
261 | memory.</p> |
120 | </dd> |
|
|
121 | <dd> |
|
|
122 | <p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
262 | <p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
123 | still fares rather well. And compared to some monsters like gnome-terminal |
263 | still fares rather well. And compared to some monsters like gnome-terminal |
124 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
264 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
125 | 43180k in daemons that stay around after exit, plus half aminute of |
265 | 43180k in daemons that stay around after exit, plus half a minute of |
126 | startup time, including the hundreds of warnings it spits out), it fares |
266 | startup time, including the hundreds of warnings it spits out), it fares |
127 | extremely well *g*.</p> |
267 | extremely well *g*.</p> |
128 | </dd> |
268 | <p> |
129 | <p></p> |
269 | </p> |
130 | <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 /> |
270 | <h2><a name="why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></h2> |
131 | </dt> |
|
|
132 | <dd> |
|
|
133 | Is this a question? :) It comes up very often. The simple answer is: I had |
271 | <p>Is this a question? :) It comes up very often. The simple answer is: I had |
134 | to write it, and C++ allowed me to write and maintain it in a fraction |
272 | to write it, and C++ allowed me to write and maintain it in a fraction |
135 | of the time and effort (which is a scarce resource for me). Put even |
273 | of the time and effort (which is a scarce resource for me). Put even |
136 | shorter: It simply wouldn't exist without C++. |
274 | shorter: It simply wouldn't exist without C++.</p> |
137 | </dd> |
|
|
138 | <dd> |
|
|
139 | <p>My personal stance on this is that C++ is less portable than C, but in |
275 | <p>My personal stance on this is that C++ is less portable than C, but in |
140 | the case of rxvt-unicode this hardly matters, as its portability limits |
276 | the case of rxvt-unicode this hardly matters, as its portability limits |
141 | are defined by things like X11, pseudo terminals, locale support and unix |
277 | are defined by things like X11, pseudo terminals, locale support and unix |
142 | domain sockets, which are all less portable than C++ itself.</p> |
278 | domain sockets, which are all less portable than C++ itself.</p> |
143 | </dd> |
|
|
144 | <dd> |
|
|
145 | <p>Regarding the bloat, see the above question: It's easy to write programs |
279 | <p>Regarding the bloat, see the above question: It's easy to write programs |
146 | in C that use gobs of memory, an certainly possible to write programs in |
280 | in C that use gobs of memory, an certainly possible to write programs in |
147 | C++ that don't. C++ also often comes with large libraries, but this is |
281 | C++ that don't. C++ also often comes with large libraries, but this is |
148 | not necessarily the case with GCC. Here is what rxvt links against on my |
282 | not necessarily the case with GCC. Here is what rxvt links against on my |
149 | system with a minimal config:</p> |
283 | system with a minimal config:</p> |
150 | </dd> |
|
|
151 | <dd> |
|
|
152 | <pre> |
284 | <pre> |
153 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
285 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
154 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
286 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
155 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
287 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
156 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
288 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
157 | </dd> |
|
|
158 | <dd> |
|
|
159 | <p>And here is rxvt-unicode:</p> |
289 | <p>And here is rxvt-unicode:</p> |
160 | </dd> |
|
|
161 | <dd> |
|
|
162 | <pre> |
290 | <pre> |
163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
291 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
292 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
293 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
294 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
295 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
168 | </dd> |
|
|
169 | <dd> |
|
|
170 | <p>No large bloated libraries (of course, none were linked in statically), |
296 | <p>No large bloated libraries (of course, none were linked in statically), |
171 | except maybe libX11 :)</p> |
297 | except maybe libX11 :)</p> |
172 | </dd> |
298 | <p> |
173 | <p></p> |
299 | </p> |
174 | <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 /> |
300 | <h2><a name="does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></h2> |
175 | </dt> |
301 | <p>Beginning with version 7.3, there is a perl extension that implements a |
176 | <dd> |
302 | simple tabbed terminal. It is installed by default, so any of these should |
177 | rxvt-unicode does not directly support tabs. It will work fine with |
303 | give you tabs:</p> |
178 | tabbing functionality of many window managers or similar tabbing programs, |
304 | <pre> |
179 | and its embedding-features allow it to be embedded into other programs, |
305 | rxvt -pe tabbed</pre> |
180 | as witnessed by <em>doc/rxvt-tabbed</em> or the upcoming <code>Gtk2::URxvt</code> perl |
306 | <pre> |
181 | module, which features a tabbed urxvt (murxvt) terminal as an example |
307 | URxvt.perl-ext-common: default,tabbed</pre> |
182 | embedding application. |
308 | <p>It will also work fine with tabbing functionality of many window managers |
183 | </dd> |
309 | or similar tabbing programs, and its embedding-features allow it to be |
184 | <p></p> |
310 | embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or |
|
|
311 | the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt |
|
|
312 | (murxvt) terminal as an example embedding application.</p> |
|
|
313 | <p> |
|
|
314 | </p> |
185 | <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 /> |
315 | <h2><a name="how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></h2> |
186 | </dt> |
|
|
187 | <dd> |
|
|
188 | The version number is displayed with the usage (-h). Also the escape |
316 | <p>The version number is displayed with the usage (-h). Also the escape |
189 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. When |
317 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. When |
190 | using the rxvtc client, the version displayed is that of the |
318 | using the rxvtc client, the version displayed is that of the |
191 | daemon. |
319 | daemon.</p> |
192 | </dd> |
320 | <p> |
193 | <p></p> |
321 | </p> |
194 | <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 /> |
322 | <h2><a name="i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></h2> |
195 | </dt> |
|
|
196 | <dd> |
|
|
197 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
323 | <p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
198 | patches that considerably change the behaviour of rxvt-unicode. Before |
324 | patches that considerably change the behaviour of rxvt-unicode (but |
199 | reporting a bug to the original rxvt-unicode author please download and |
325 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
326 | the original rxvt-unicode author please download and install the genuine |
200 | install the genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) |
327 | version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce |
201 | and try to reproduce the problem. If you cannot, chances are that the |
328 | the problem. If you cannot, chances are that the problems are specific to |
202 | problems are specific to Debian GNU/Linux, in which case it should be |
329 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
203 | reported via the Debian Bug Tracking System (use <code>reportbug</code> to report |
330 | Tracking System (use <code>reportbug</code> to report the bug).</p> |
204 | the bug). |
|
|
205 | </dd> |
|
|
206 | <dd> |
|
|
207 | <p>For other problems that also affect the Debian package, you can and |
331 | <p>For other problems that also affect the Debian package, you can and |
208 | probably should use the Debian BTS, too, because, after all, it's also a |
332 | probably should use the Debian BTS, too, because, after all, it's also a |
209 | bug in the Debian version and it serves as a reminder for other users that |
333 | bug in the Debian version and it serves as a reminder for other users that |
210 | might encounter the same issue.</p> |
334 | might encounter the same issue.</p> |
211 | </dd> |
335 | <p> |
212 | <p></p> |
336 | </p> |
213 | <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 /> |
337 | <h2><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h2> |
214 | </dt> |
338 | <p>You should build one binary with the default options. <em>configure</em> |
215 | <dd> |
339 | now enables most useful options, and the trend goes to making them |
|
|
340 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
|
|
341 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
342 | be enabled, as important functionality (menus, selection, likely more in |
|
|
343 | the future) depends on it.</p> |
|
|
344 | <p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources |
|
|
345 | system-wide (except maybe with <code>defaults</code>). This will result in useful |
|
|
346 | behaviour. If your distribution aims at low memory, add an empty |
|
|
347 | <code>perl-ext-common</code> resource to the app-defaults file. This will keep the |
|
|
348 | perl interpreter disabled until the user enables it.</p> |
|
|
349 | <p>If you can/want build more binaries, I recommend building a minimal |
|
|
350 | one with <code>--disable-everything</code> (very useful) and a maximal one with |
|
|
351 | <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of |
|
|
352 | encodings built-in that increase download times and are rarely used).</p> |
|
|
353 | <p> |
|
|
354 | </p> |
|
|
355 | <h2><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></h2> |
|
|
356 | <p>It should be, starting with release 7.1. You are encouraged to properly |
|
|
357 | install urxvt with privileges necessary for your OS now.</p> |
|
|
358 | <p>When rxvt-unicode detects that it runs setuid or setgid, it will fork |
|
|
359 | into a helper process for privileged operations (pty handling on some |
|
|
360 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
|
|
361 | immediately. This is much safer than most other terminals that keep |
|
|
362 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
363 | things as perl interpreters, which might be ``helpful'' to attackers).</p> |
|
|
364 | <p>This forking is done as the very first within main(), which is very early |
|
|
365 | and reduces possible bugs to initialisation code run before main(), or |
|
|
366 | things like the dynamic loader of your system, which should result in very |
|
|
367 | little risk.</p> |
|
|
368 | <p> |
|
|
369 | </p> |
|
|
370 | <h2><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></h2> |
216 | The terminal description used by rxvt-unicode is not as widely available |
371 | <p>The terminal description used by rxvt-unicode is not as widely available |
217 | as that for xterm, or even rxvt (for which the same problem often arises). |
372 | as that for xterm, or even rxvt (for which the same problem often arises).</p> |
218 | </dd> |
|
|
219 | <dd> |
|
|
220 | <p>The correct solution for this problem is to install the terminfo, this can |
373 | <p>The correct solution for this problem is to install the terminfo, this can |
221 | be done like this (with ncurses' infocmp):</p> |
374 | be done like this (with ncurses' infocmp):</p> |
222 | </dd> |
|
|
223 | <dd> |
|
|
224 | <pre> |
375 | <pre> |
225 | REMOTE=remotesystem.domain |
376 | REMOTE=remotesystem.domain |
226 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"</pre> |
377 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"</pre> |
227 | </dd> |
|
|
228 | <dd> |
|
|
229 | <p>... or by installing rxvt-unicode normally on the remote system,</p> |
378 | <p>... or by installing rxvt-unicode normally on the remote system,</p> |
230 | </dd> |
|
|
231 | <dd> |
|
|
232 | <p>If you cannot or do not want to do this, then you can simply set |
379 | <p>If you cannot or do not want to do this, then you can simply set |
233 | <code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of |
380 | <code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of |
234 | problems arising, which includes wrong keymapping, less and different |
381 | problems arising, which includes wrong keymapping, less and different |
235 | colours and some refresh errors in fullscreen applications. It's a nice |
382 | colours and some refresh errors in fullscreen applications. It's a nice |
236 | quick-and-dirty workaround for rare cases, though.</p> |
383 | quick-and-dirty workaround for rare cases, though.</p> |
237 | </dd> |
|
|
238 | <dd> |
|
|
239 | <p>If you always want to do this (and are fine with the consequences) you |
384 | <p>If you always want to do this (and are fine with the consequences) you |
240 | can either recompile rxvt-unicode with the desired TERM value or use a |
385 | can either recompile rxvt-unicode with the desired TERM value or use a |
241 | resource to set it:</p> |
386 | resource to set it:</p> |
242 | </dd> |
|
|
243 | <dd> |
|
|
244 | <pre> |
387 | <pre> |
245 | URxvt.termName: rxvt</pre> |
388 | URxvt.termName: rxvt</pre> |
246 | </dd> |
|
|
247 | <dd> |
|
|
248 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
389 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
249 | the rxvt terminfo file with the rxvt-unicode one.</p> |
390 | the rxvt terminfo file with the rxvt-unicode one.</p> |
250 | </dd> |
391 | <p> |
251 | <p></p> |
392 | </p> |
252 | <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 /> |
393 | <h2><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h2> |
253 | </dt> |
|
|
254 | <dd> |
|
|
255 | Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
394 | <p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
256 | <code>enacs=\E[0@</code> and try again. |
395 | <code>enacs=\E[0@</code> and try again.</p> |
257 | </dd> |
396 | <p> |
258 | <p></p> |
397 | </p> |
259 | <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 /> |
398 | <h2><a name="bash_s_readline_does_not_work_correctly_under_rxvt_"><code>bash</code>'s readline does not work correctly under rxvt.</a></h2> |
260 | </dt> |
399 | <p>See next entry.</p> |
|
|
400 | <p> |
|
|
401 | </p> |
261 | <dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> |
402 | <h2><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h2> |
262 | </dt> |
|
|
263 | <dd> |
|
|
264 | One reason you might want this is that some distributions or operating |
403 | <p>One reason you might want this is that some distributions or operating |
265 | systems still compile some programs using the long-obsoleted termcap |
404 | systems still compile some programs using the long-obsoleted termcap |
266 | library (Fedora Core's bash is one example) and rely on a termcap entry |
405 | library (Fedora Core's bash is one example) and rely on a termcap entry |
267 | for <code>rxvt-unicode</code>. |
406 | for <code>rxvt-unicode</code>.</p> |
268 | </dd> |
|
|
269 | <dd> |
|
|
270 | <p>You could use rxvt's termcap entry with resonable results in many cases. |
407 | <p>You could use rxvt's termcap entry with resonable results in many cases. |
271 | You can also create a termcap entry by using terminfo's infocmp program |
408 | You can also create a termcap entry by using terminfo's infocmp program |
272 | like this:</p> |
409 | like this:</p> |
273 | </dd> |
|
|
274 | <dd> |
|
|
275 | <pre> |
410 | <pre> |
276 | infocmp -C rxvt-unicode</pre> |
411 | infocmp -C rxvt-unicode</pre> |
277 | </dd> |
|
|
278 | <dd> |
|
|
279 | <p>Or you could use this termcap entry, generated by the command above:</p> |
412 | <p>Or you could use this termcap entry, generated by the command above:</p> |
280 | </dd> |
|
|
281 | <dd> |
|
|
282 | <pre> |
413 | <pre> |
283 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
414 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
284 | :am:bw:eo:km:mi:ms:xn:xo:\ |
415 | :am:bw:eo:km:mi:ms:xn:xo:\ |
285 | :co#80:it#8:li#24:lm#0:\ |
416 | :co#80:it#8:li#24:lm#0:\ |
286 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
417 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
… | |
… | |
298 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
429 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
299 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
430 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
300 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
431 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
301 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
432 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
302 | :vs=\E[?25h:</pre> |
433 | :vs=\E[?25h:</pre> |
303 | </dd> |
434 | <p> |
304 | <p></p> |
435 | </p> |
305 | <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 /> |
436 | <h2><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h2> |
306 | </dt> |
|
|
307 | <dd> |
|
|
308 | The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to |
437 | <p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to |
309 | decide wether a terminal has colour, but uses it's own configuration |
438 | decide wether a terminal has colour, but uses it's own configuration |
310 | file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among |
439 | file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among |
311 | with most other terminals supporting colour). Either add: |
440 | with most other terminals supporting colour). Either add:</p> |
312 | </dd> |
|
|
313 | <dd> |
|
|
314 | <pre> |
441 | <pre> |
315 | TERM rxvt-unicode</pre> |
442 | TERM rxvt-unicode</pre> |
316 | </dd> |
|
|
317 | <dd> |
|
|
318 | <p>to <code>/etc/DIR_COLORS</code> or simply add:</p> |
443 | <p>to <code>/etc/DIR_COLORS</code> or simply add:</p> |
319 | </dd> |
|
|
320 | <dd> |
|
|
321 | <pre> |
444 | <pre> |
322 | alias ls='ls --color=auto'</pre> |
445 | alias ls='ls --color=auto'</pre> |
323 | </dd> |
|
|
324 | <dd> |
|
|
325 | <p>to your <code>.profile</code> or <code>.bashrc</code>.</p> |
446 | <p>to your <code>.profile</code> or <code>.bashrc</code>.</p> |
326 | </dd> |
447 | <p> |
327 | <p></p> |
448 | </p> |
328 | <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 /> |
449 | <h2><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></h2> |
329 | </dt> |
450 | <p>See next entry.</p> |
|
|
451 | <p> |
|
|
452 | </p> |
330 | <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 /> |
453 | <h2><a name="why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></h2> |
331 | </dt> |
454 | <p>See next entry.</p> |
|
|
455 | <p> |
|
|
456 | </p> |
332 | <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 /> |
457 | <h2><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h2> |
333 | </dt> |
|
|
334 | <dd> |
|
|
335 | Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged |
458 | <p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged |
336 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
459 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
337 | by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra |
460 | by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra |
338 | features. Unfortunately, some of these (most notably, again, Debian |
461 | features. Unfortunately, some of these (most notably, again, Debian |
339 | GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo |
462 | GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo |
340 | file, so you will need to install it on your own (See the question <strong>When |
463 | file, so you will need to install it on your own (See the question <strong>When |
341 | I log-in to another system it tells me about missing terminfo data?</strong> on |
464 | I log-in to another system it tells me about missing terminfo data?</strong> on |
342 | how to do this). |
465 | how to do this).</p> |
343 | </dd> |
466 | <p> |
344 | <p></p> |
467 | </p> |
345 | <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 /> |
468 | <h2><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h2> |
346 | </dt> |
|
|
347 | <dd> |
|
|
348 | Some Debian GNUL/Linux users seem to have this problem, although no |
469 | <p>Some Debian GNUL/Linux users seem to have this problem, although no |
349 | specific details were reported so far. It is possible that this is caused |
470 | specific details were reported so far. It is possible that this is caused |
350 | by the wrong <code>TERM</code> setting, although the details of wether and how |
471 | by the wrong <code>TERM</code> setting, although the details of wether and how |
351 | this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible |
472 | this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible |
352 | keymap. See the answer to the previous question, and please report if that |
473 | keymap. See the answer to the previous question, and please report if that |
353 | helped. |
474 | helped.</p> |
354 | </dd> |
475 | <p> |
355 | <p></p> |
476 | </p> |
356 | <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 /> |
477 | <h2><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h2> |
357 | </dt> |
478 | <p>See next entry.</p> |
|
|
479 | <p> |
|
|
480 | </p> |
358 | <dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br /> |
481 | <h2><a name="unicode_does_not_seem_to_work">Unicode does not seem to work?</a></h2> |
359 | </dt> |
|
|
360 | <dd> |
|
|
361 | If you encounter strange problems like typing an accented character but |
482 | <p>If you encounter strange problems like typing an accented character but |
362 | getting two unrelated other characters or similar, or if program output is |
483 | getting two unrelated other characters or similar, or if program output is |
363 | subtly garbled, then you should check your locale settings. |
484 | subtly garbled, then you should check your locale settings.</p> |
364 | </dd> |
|
|
365 | <dd> |
|
|
366 | <p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the |
485 | <p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the |
367 | programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the |
486 | programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the |
368 | login script running within the rxvt-unicode window changes the locale to |
487 | login script running within the rxvt-unicode window changes the locale to |
369 | something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> |
488 | something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> |
370 | </dd> |
|
|
371 | <dd> |
|
|
372 | <p>The best thing is to fix your startup environment, as you will likely run |
489 | <p>The best thing is to fix your startup environment, as you will likely run |
373 | into other problems. If nothing works you can try this in your .profile.</p> |
490 | into other problems. If nothing works you can try this in your .profile.</p> |
374 | </dd> |
|
|
375 | <dd> |
|
|
376 | <pre> |
491 | <pre> |
377 | printf '\e]701;%s\007' "$LC_CTYPE"</pre> |
492 | printf '\e]701;%s\007' "$LC_CTYPE"</pre> |
378 | </dd> |
|
|
379 | <dd> |
|
|
380 | <p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not |
493 | <p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not |
381 | supported on your systems. Some systems have a <code>locale</code> command which |
494 | supported on your systems. Some systems have a <code>locale</code> command which |
382 | displays this (also, <code>perl -e0</code> can be used to check locale settings, as |
495 | displays this (also, <code>perl -e0</code> can be used to check locale settings, as |
383 | it will complain loudly if it cannot set the locale). If it displays something |
496 | it will complain loudly if it cannot set the locale). If it displays something |
384 | like:</p> |
497 | like:</p> |
385 | </dd> |
|
|
386 | <dd> |
|
|
387 | <pre> |
498 | <pre> |
388 | locale: Cannot set LC_CTYPE to default locale: ...</pre> |
499 | locale: Cannot set LC_CTYPE to default locale: ...</pre> |
389 | </dd> |
|
|
390 | <dd> |
|
|
391 | <p>Then the locale you specified is not supported on your system.</p> |
500 | <p>Then the locale you specified is not supported on your system.</p> |
392 | </dd> |
|
|
393 | <dd> |
|
|
394 | <p>If nothing works and you are sure that everything is set correctly then |
501 | <p>If nothing works and you are sure that everything is set correctly then |
395 | you will need to remember a little known fact: Some programs just don't |
502 | you will need to remember a little known fact: Some programs just don't |
396 | support locales :(</p> |
503 | support locales :(</p> |
397 | </dd> |
504 | <p> |
398 | <p></p> |
505 | </p> |
399 | <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 /> |
506 | <h2><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h2> |
400 | </dt> |
507 | <p>See next entry.</p> |
|
|
508 | <p> |
|
|
509 | </p> |
401 | <dt><strong><a name="item_how_does_rxvt_2dunicode_choose_fonts_3f">How does rxvt-unicode choose fonts?</a></strong><br /> |
510 | <h2><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h2> |
402 | </dt> |
|
|
403 | <dd> |
|
|
404 | Most fonts do not contain the full range of Unicode, which is |
511 | <p>Most fonts do not contain the full range of Unicode, which is |
405 | fine. Chances are that the font you (or the admin/package maintainer of |
512 | fine. Chances are that the font you (or the admin/package maintainer of |
406 | your system/os) have specified does not cover all the characters you want |
513 | your system/os) have specified does not cover all the characters you want |
407 | to display. |
514 | to display.</p> |
408 | </dd> |
|
|
409 | <dd> |
|
|
410 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
515 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
411 | font. Often the result is fine, but sometimes the chosen font looks |
516 | font. Often the result is fine, but sometimes the chosen font looks |
412 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
517 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
413 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
518 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
414 | intelligence to detect that a specific glyph is wrong: it has to believe |
519 | intelligence to detect that a specific glyph is wrong: it has to believe |
415 | the font that the characters it claims to contain indeed look correct.</p> |
520 | the font that the characters it claims to contain indeed look correct.</p> |
416 | </dd> |
|
|
417 | <dd> |
|
|
418 | <p>In that case, select a font of your taste and add it to the font list, |
521 | <p>In that case, select a font of your taste and add it to the font list, |
419 | e.g.:</p> |
522 | e.g.:</p> |
420 | </dd> |
|
|
421 | <dd> |
|
|
422 | <pre> |
523 | <pre> |
423 | rxvt -fn basefont,font2,font3...</pre> |
524 | rxvt -fn basefont,font2,font3...</pre> |
424 | </dd> |
|
|
425 | <dd> |
|
|
426 | <p>When rxvt-unicode sees a character, it will first look at the base |
525 | <p>When rxvt-unicode sees a character, it will first look at the base |
427 | font. If the base font does not contain the character, it will go to the |
526 | font. If the base font does not contain the character, it will go to the |
428 | next font, and so on. Specifying your own fonts will also speed up this |
527 | next font, and so on. Specifying your own fonts will also speed up this |
429 | search and use less resources within rxvt-unicode and the X-server.</p> |
528 | search and use less resources within rxvt-unicode and the X-server.</p> |
430 | </dd> |
|
|
431 | <dd> |
|
|
432 | <p>The only limitation is that none of the fonts may be larger than the base |
529 | <p>The only limitation is that none of the fonts may be larger than the base |
433 | font, as the base font defines the terminal character cell size, which |
530 | font, as the base font defines the terminal character cell size, which |
434 | must be the same due to the way terminals work.</p> |
531 | must be the same due to the way terminals work.</p> |
435 | </dd> |
532 | <p> |
436 | <p></p> |
533 | </p> |
437 | <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 /> |
534 | <h2><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h2> |
438 | </dt> |
|
|
439 | <dd> |
|
|
440 | This is because there is a difference between script and language -- |
535 | <p>This is because there is a difference between script and language -- |
441 | rxvt-unicode does not know which language the text that is output is, |
536 | rxvt-unicode does not know which language the text that is output is, |
442 | as it only knows the unicode character codes. If rxvt-unicode first |
537 | as it only knows the unicode character codes. If rxvt-unicode first |
443 | sees a japanese/chinese character, it might choose a japanese font for |
538 | sees a japanese/chinese character, it might choose a japanese font for |
444 | display. Subsequent japanese characters will use that font. Now, many |
539 | display. Subsequent japanese characters will use that font. Now, many |
445 | chinese characters aren't represented in japanese fonts, so when the first |
540 | chinese characters aren't represented in japanese fonts, so when the first |
446 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
541 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
447 | -- unfortunately at this point, it will still use the japanese font for |
542 | -- unfortunately at this point, it will still use the japanese font for |
448 | chinese characters that are also in the japanese font. |
543 | chinese characters that are also in the japanese font.</p> |
449 | </dd> |
|
|
450 | <dd> |
|
|
451 | <p>The workaround is easy: just tag a chinese font at the end of your font |
544 | <p>The workaround is easy: just tag a chinese font at the end of your font |
452 | list (see the previous question). The key is to view the font list as |
545 | list (see the previous question). The key is to view the font list as |
453 | a preference list: If you expect more japanese, list a japanese font |
546 | a preference list: If you expect more japanese, list a japanese font |
454 | first. If you expect more chinese, put a chinese font first.</p> |
547 | first. If you expect more chinese, put a chinese font first.</p> |
455 | </dd> |
|
|
456 | <dd> |
|
|
457 | <p>In the future it might be possible to switch language preferences at |
548 | <p>In the future it might be possible to switch language preferences at |
458 | runtime (the internal data structure has no problem with using different |
549 | runtime (the internal data structure has no problem with using different |
459 | fonts for the same character at the same time, but no interface for this |
550 | fonts for the same character at the same time, but no interface for this |
460 | has been designed yet).</p> |
551 | has been designed yet).</p> |
461 | </dd> |
|
|
462 | <dd> |
|
|
463 | <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> |
552 | <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> |
464 | </dd> |
553 | <p> |
465 | <p></p> |
554 | </p> |
466 | <dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br /> |
555 | <h2><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h2> |
467 | </dt> |
|
|
468 | <dd> |
|
|
469 | Most fonts were not designed for terminal use, which means that character |
556 | <p>Most fonts were not designed for terminal use, which means that character |
470 | size varies a lot. A font that is otherwise fine for terminal use might |
557 | size varies a lot. A font that is otherwise fine for terminal use might |
471 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
558 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
472 | these characters. For characters that are just ``a bit'' too wide a special |
559 | these characters. For characters that are just ``a bit'' too wide a special |
473 | ``careful'' rendering mode is used that redraws adjacent characters. |
560 | ``careful'' rendering mode is used that redraws adjacent characters.</p> |
474 | </dd> |
|
|
475 | <dd> |
|
|
476 | <p>All of this requires that fonts do not lie about character sizes, |
561 | <p>All of this requires that fonts do not lie about character sizes, |
477 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
562 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
478 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
563 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
479 | ask for the character bounding box, which unfortunately is wrong in these |
564 | ask for the character bounding box, which unfortunately is wrong in these |
480 | cases).</p> |
565 | cases).</p> |
481 | </dd> |
|
|
482 | <dd> |
|
|
483 | <p>It's not clear (to me at least), wether this is a bug in Xft, freetype, |
566 | <p>It's not clear (to me at least), wether this is a bug in Xft, freetype, |
484 | or the respective font. If you encounter this problem you might try using |
567 | or the respective font. If you encounter this problem you might try using |
485 | the <code>-lsp</code> option to give the font more height. If that doesn't work, you |
568 | the <code>-lsp</code> option to give the font more height. If that doesn't work, you |
486 | might be forced to use a different font.</p> |
569 | might be forced to use a different font.</p> |
487 | </dd> |
|
|
488 | <dd> |
|
|
489 | <p>All of this is not a problem when using X11 core fonts, as their bounding |
570 | <p>All of this is not a problem when using X11 core fonts, as their bounding |
490 | box data is correct.</p> |
571 | box data is correct.</p> |
491 | </dd> |
572 | <p> |
492 | <p></p> |
573 | </p> |
493 | <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 /> |
574 | <h2><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h2> |
494 | </dt> |
|
|
495 | <dd> |
|
|
496 | Seems to be a known bug, read |
575 | <p>Seems to be a known bug, read |
497 | <a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the |
576 | <a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the |
498 | following ugly workaround to get non-double-wide-characters working: |
577 | following ugly workaround to get non-double-wide-characters working:</p> |
499 | </dd> |
|
|
500 | <dd> |
|
|
501 | <pre> |
578 | <pre> |
502 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)</pre> |
579 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)</pre> |
503 | </dd> |
580 | <p> |
504 | <p></p> |
581 | </p> |
505 | <dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br /> |
582 | <h2><a name="my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></h2> |
506 | </dt> |
|
|
507 | <dd> |
|
|
508 | The most common causes for this are that either your locale is not set |
583 | <p>The most common causes for this are that either your locale is not set |
509 | correctly, or you specified a <strong>preeditStyle</strong> that is not supported by |
584 | correctly, or you specified a <strong>preeditStyle</strong> that is not supported by |
510 | your input method. For example, if you specified <strong>OverTheSpot</strong> and |
585 | your input method. For example, if you specified <strong>OverTheSpot</strong> and |
511 | your input method (e.g. the default input method handling Compose keys) |
586 | your input method (e.g. the default input method handling Compose keys) |
512 | does not support this (for instance because it is not visual), then |
587 | does not support this (for instance because it is not visual), then |
513 | rxvt-unicode will continue without an input method. |
588 | rxvt-unicode will continue without an input method.</p> |
514 | </dd> |
|
|
515 | <dd> |
|
|
516 | <p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than |
589 | <p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than |
517 | one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p> |
590 | one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p> |
518 | </dd> |
591 | <p> |
519 | <p></p> |
592 | </p> |
520 | <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 /> |
593 | <h2><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></h2> |
521 | </dt> |
|
|
522 | <dd> |
|
|
523 | Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on |
594 | <p>Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on |
524 | international keyboards) or simply use ISO 14755 support to your |
595 | international keyboards) or simply use ISO 14755 support to your |
525 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
596 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
526 | codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape |
597 | codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape |
527 | character and so on. |
598 | character and so on.</p> |
528 | </dd> |
599 | <p> |
529 | <p></p> |
600 | </p> |
530 | <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 /> |
601 | <h2><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></h2> |
531 | </dt> |
|
|
532 | <dd> |
|
|
533 | First of all, make sure you are running with the right terminal settings |
602 | <p>First of all, make sure you are running with the right terminal settings |
534 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
603 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
535 | make sure you have specified colours for italic and bold, as otherwise |
604 | make sure you have specified colours for italic and bold, as otherwise |
536 | rxvt-unicode might use reverse video to simulate the effect: |
605 | rxvt-unicode might use reverse video to simulate the effect:</p> |
537 | </dd> |
|
|
538 | <dd> |
|
|
539 | <pre> |
606 | <pre> |
540 | URxvt.colorBD: white |
607 | URxvt.colorBD: white |
541 | URxvt.colorIT: green</pre> |
608 | URxvt.colorIT: green</pre> |
542 | </dd> |
609 | <p> |
543 | <p></p> |
610 | </p> |
544 | <dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br /> |
611 | <h2><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></h2> |
545 | </dt> |
|
|
546 | <dd> |
|
|
547 | For some unexplainable reason, some rare programs assume a very weird |
612 | <p>For some unexplainable reason, some rare programs assume a very weird |
548 | colour palette when confronted with a terminal with more than the standard |
613 | colour palette when confronted with a terminal with more than the standard |
549 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
614 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
550 | these programs not to assume non-ISO colours without very good reasons. |
615 | these programs not to assume non-ISO colours without very good reasons.</p> |
551 | </dd> |
|
|
552 | <dd> |
|
|
553 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
616 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
554 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
617 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
555 | fix colours but keep you from using other rxvt-unicode features.</p> |
618 | fix colours but keep you from using other rxvt-unicode features.</p> |
556 | </dd> |
619 | <p> |
557 | <p></p> |
620 | </p> |
558 | <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 /> |
621 | <h2><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></h2> |
559 | </dt> |
|
|
560 | <dd> |
|
|
561 | Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined |
622 | <p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined |
562 | in your compile environment, or an implementation that implements it, |
623 | in your compile environment, or an implementation that implements it, |
563 | wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that |
624 | wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that |
564 | <strong>wchar_t</strong> is represented as unicode. |
625 | <strong>wchar_t</strong> is represented as unicode.</p> |
565 | </dd> |
|
|
566 | <dd> |
|
|
567 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
626 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
568 | does it support it. Instead, it uses it's own internal representation of |
627 | does it support it. Instead, it uses it's own internal representation of |
569 | <strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> |
628 | <strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> |
570 | </dd> |
|
|
571 | <dd> |
|
|
572 | <p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and |
629 | <p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and |
573 | <code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> |
630 | <code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> |
574 | </dd> |
|
|
575 | <dd> |
|
|
576 | <p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language |
631 | <p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language |
577 | apps in an OS, as using a locale-dependent (and non-standardized) |
632 | apps in an OS, as using a locale-dependent (and non-standardized) |
578 | representation of <strong>wchar_t</strong> makes it impossible to convert between |
633 | representation of <strong>wchar_t</strong> makes it impossible to convert between |
579 | <strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding |
634 | <strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding |
580 | without implementing OS-specific-wrappers for each and every locale. There |
635 | without implementing OS-specific-wrappers for each and every locale. There |
581 | simply are no APIs to convert <strong>wchar_t</strong> into anything except the current |
636 | simply are no APIs to convert <strong>wchar_t</strong> into anything except the current |
582 | locale encoding.</p> |
637 | locale encoding.</p> |
583 | </dd> |
|
|
584 | <dd> |
|
|
585 | <p>Some applications (such as the formidable <strong>mlterm</strong>) work around this |
638 | <p>Some applications (such as the formidable <strong>mlterm</strong>) work around this |
586 | by carrying their own replacement functions for character set handling |
639 | by carrying their own replacement functions for character set handling |
587 | with them, and either implementing OS-dependent hacks or doing multiple |
640 | with them, and either implementing OS-dependent hacks or doing multiple |
588 | conversions (which is slow and unreliable in case the OS implements |
641 | conversions (which is slow and unreliable in case the OS implements |
589 | encodings slightly different than the terminal emulator).</p> |
642 | encodings slightly different than the terminal emulator).</p> |
590 | </dd> |
|
|
591 | <dd> |
|
|
592 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
643 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
593 | system libraries once and for all, instead of forcing every app to carry |
644 | system libraries once and for all, instead of forcing every app to carry |
594 | complete replacements for them :)</p> |
645 | complete replacements for them :)</p> |
595 | </dd> |
646 | <p> |
596 | <p></p> |
647 | </p> |
597 | <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 /> |
648 | <h2><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></h2> |
598 | </dt> |
|
|
599 | <dd> |
|
|
600 | Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst |
649 | <p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst |
601 | problems with <code>wcwidth</code> and a compile problem. |
650 | problems with <code>wcwidth</code> and a compile problem.</p> |
602 | </dd> |
651 | <p> |
603 | <p></p> |
652 | </p> |
604 | <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 /> |
653 | <h2><a name="how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></h2> |
605 | </dt> |
|
|
606 | <dd> |
|
|
607 | rxvt-unicode should compile and run out of the box on cygwin, using |
654 | <p>rxvt-unicode should compile and run out of the box on cygwin, using |
608 | the X11 libraries that come with cygwin. libW11 emulation is no |
655 | the X11 libraries that come with cygwin. libW11 emulation is no |
609 | longer supported (and makes no sense, either, as it only supported a |
656 | longer supported (and makes no sense, either, as it only supported a |
610 | single font). I recommend starting the X-server in <code>-multiwindow</code> or |
657 | single font). I recommend starting the X-server in <code>-multiwindow</code> or |
611 | <code>-rootless</code> mode instead, which will result in similar look&feel as the |
658 | <code>-rootless</code> mode instead, which will result in similar look&feel as the |
612 | old libW11 emulation. |
659 | old libW11 emulation.</p> |
613 | </dd> |
|
|
614 | <dd> |
|
|
615 | <p>At the time of this writing, cygwin didn't seem to support any multi-byte |
660 | <p>At the time of this writing, cygwin didn't seem to support any multi-byte |
616 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
661 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
617 | to 8-bit encodings.</p> |
662 | to 8-bit encodings.</p> |
618 | </dd> |
663 | <p> |
619 | <p></p> |
664 | </p> |
620 | <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 /> |
665 | <h2><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h2> |
621 | </dt> |
666 | <p>See next entry.</p> |
|
|
667 | <p> |
|
|
668 | </p> |
622 | <dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br /> |
669 | <h2><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h2> |
623 | </dt> |
|
|
624 | <dd> |
|
|
625 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
670 | <p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
626 | specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about |
671 | specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about |
627 | UTF-8 or any other encodings with respect to terminal I/O. |
672 | UTF-8 or any other encodings with respect to terminal I/O.</p> |
628 | </dd> |
|
|
629 | <dd> |
|
|
630 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
673 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
631 | the encoding, doing I/O and (most important) communicating this to all |
674 | the encoding, doing I/O and (most important) communicating this to all |
632 | applications so everybody agrees on character properties such as width |
675 | applications so everybody agrees on character properties such as width |
633 | and code number. This mechanism is the <em>locale</em>. Applications not using |
676 | and code number. This mechanism is the <em>locale</em>. Applications not using |
634 | that info will have problems (for example, <code>xterm</code> gets the width of |
677 | that info will have problems (for example, <code>xterm</code> gets the width of |
635 | characters wrong as it uses it's own, locale-independent table under all |
678 | characters wrong as it uses it's own, locale-independent table under all |
636 | locales).</p> |
679 | locales).</p> |
637 | </dd> |
|
|
638 | <dd> |
|
|
639 | <p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All |
680 | <p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All |
640 | programs doing the same (that is, most) will automatically agree in the |
681 | programs doing the same (that is, most) will automatically agree in the |
641 | interpretation of characters.</p> |
682 | interpretation of characters.</p> |
642 | </dd> |
|
|
643 | <dd> |
|
|
644 | <p>Unfortunately, there is no system-independent way to select locales, nor |
683 | <p>Unfortunately, there is no system-independent way to select locales, nor |
645 | is there a standard on how locale specifiers will look like.</p> |
684 | is there a standard on how locale specifiers will look like.</p> |
646 | </dd> |
|
|
647 | <dd> |
|
|
648 | <p>On most systems, the content of the <code>LC_CTYPE</code> environment variable |
685 | <p>On most systems, the content of the <code>LC_CTYPE</code> environment variable |
649 | contains an arbitrary string which corresponds to an already-installed |
686 | contains an arbitrary string which corresponds to an already-installed |
650 | locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>, |
687 | locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>, |
651 | <code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms |
688 | <code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms |
652 | (i.e. <code>de</code> or <code>german</code>) are also common.</p> |
689 | (i.e. <code>de</code> or <code>german</code>) are also common.</p> |
653 | </dd> |
|
|
654 | <dd> |
|
|
655 | <p>Rxvt-unicode ignores all other locale categories, and except for |
690 | <p>Rxvt-unicode ignores all other locale categories, and except for |
656 | the encoding, ignores country or language-specific settings, |
691 | the encoding, ignores country or language-specific settings, |
657 | i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to |
692 | i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to |
658 | rxvt-unicode.</p> |
693 | rxvt-unicode.</p> |
659 | </dd> |
|
|
660 | <dd> |
|
|
661 | <p>If you want to use a specific encoding you have to make sure you start |
694 | <p>If you want to use a specific encoding you have to make sure you start |
662 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
695 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
663 | </dd> |
696 | <p> |
664 | <p></p> |
697 | </p> |
665 | <dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br /> |
698 | <h2><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h2> |
666 | </dt> |
|
|
667 | <dd> |
|
|
668 | Yes, using an escape sequence. Try something like this, which sets |
699 | <p>Yes, using an escape sequence. Try something like this, which sets |
669 | rxvt-unicode's idea of <code>LC_CTYPE</code>. |
700 | rxvt-unicode's idea of <code>LC_CTYPE</code>.</p> |
670 | </dd> |
|
|
671 | <dd> |
|
|
672 | <pre> |
701 | <pre> |
673 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
702 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
674 | </dd> |
|
|
675 | <dd> |
|
|
676 | <p>See also the previous answer.</p> |
703 | <p>See also the previous answer.</p> |
677 | </dd> |
|
|
678 | <dd> |
|
|
679 | <p>Sometimes this capability is rather handy when you want to work in |
704 | <p>Sometimes this capability is rather handy when you want to work in |
680 | one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it |
705 | one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it |
681 | (e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which |
706 | (e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which |
682 | first switches to a locale supported by xjdic and back later:</p> |
707 | first switches to a locale supported by xjdic and back later:</p> |
683 | </dd> |
|
|
684 | <dd> |
|
|
685 | <pre> |
708 | <pre> |
686 | printf '\e]701;%s\007' ja_JP.SJIS |
709 | printf '\e]701;%s\007' ja_JP.SJIS |
687 | xjdic -js |
710 | xjdic -js |
688 | printf '\e]701;%s\007' de_DE.UTF-8</pre> |
711 | printf '\e]701;%s\007' de_DE.UTF-8</pre> |
689 | </dd> |
|
|
690 | <dd> |
|
|
691 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
712 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
692 | for some locales where character width differs between program- and |
713 | for some locales where character width differs between program- and |
693 | rxvt-unicode-locales.</p> |
714 | rxvt-unicode-locales.</p> |
694 | </dd> |
715 | <p> |
695 | <p></p> |
716 | </p> |
696 | <dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br /> |
717 | <h2><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h2> |
697 | </dt> |
|
|
698 | <dd> |
|
|
699 | Yes, using an escape sequence. Try something like this, which has the same |
718 | <p>Yes, using an escape sequence. Try something like this, which has the same |
700 | effect as using the <code>-fn</code> switch, and takes effect immediately: |
719 | effect as using the <code>-fn</code> switch, and takes effect immediately:</p> |
701 | </dd> |
|
|
702 | <dd> |
|
|
703 | <pre> |
720 | <pre> |
704 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
721 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
705 | </dd> |
|
|
706 | <dd> |
|
|
707 | <p>This is useful if you e.g. work primarily with japanese (and prefer a |
722 | <p>This is useful if you e.g. work primarily with japanese (and prefer a |
708 | japanese font), but you have to switch to chinese temporarily, where |
723 | japanese font), but you have to switch to chinese temporarily, where |
709 | japanese fonts would only be in your way.</p> |
724 | japanese fonts would only be in your way.</p> |
710 | </dd> |
|
|
711 | <dd> |
|
|
712 | <p>You can think of this as a kind of manual ISO-2022 switching.</p> |
725 | <p>You can think of this as a kind of manual ISO-2022 switching.</p> |
713 | </dd> |
726 | <p> |
714 | <p></p> |
727 | </p> |
715 | <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 /> |
728 | <h2><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h2> |
716 | </dt> |
|
|
717 | <dd> |
|
|
718 | Many fonts have difficulties with italic characters and hinting. For |
729 | <p>Many fonts have difficulties with italic characters and hinting. For |
719 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
730 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
720 | Mono</code> completely fails in it's italic face. A workaround might be to |
731 | Mono</code> completely fails in it's italic face. A workaround might be to |
721 | enable freetype autohinting, i.e. like this: |
732 | enable freetype autohinting, i.e. like this:</p> |
722 | </dd> |
|
|
723 | <dd> |
|
|
724 | <pre> |
733 | <pre> |
725 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
734 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
726 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
735 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
727 | </dd> |
736 | <p> |
728 | <p></p> |
737 | </p> |
729 | <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 /> |
738 | <h2><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></h2> |
730 | </dt> |
|
|
731 | <dd> |
|
|
732 | You can specify separate locales for the input method and the rest of the |
739 | <p>You can specify separate locales for the input method and the rest of the |
733 | terminal, using the resource <code>imlocale</code>: |
740 | terminal, using the resource <code>imlocale</code>:</p> |
734 | </dd> |
|
|
735 | <dd> |
|
|
736 | <pre> |
741 | <pre> |
737 | URxvt*imlocale: ja_JP.EUC-JP</pre> |
742 | URxvt.imlocale: ja_JP.EUC-JP</pre> |
738 | </dd> |
|
|
739 | <dd> |
|
|
740 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
743 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
741 | use your input method. Please note, however, that you will not be able to |
744 | use your input method. Please note, however, that you will not be able to |
742 | input characters outside <code>EUC-JP</code> in a normal way then, as your input |
745 | input characters outside <code>EUC-JP</code> in a normal way then, as your input |
743 | method limits you.</p> |
746 | method limits you.</p> |
744 | </dd> |
747 | <p> |
745 | <p></p> |
748 | </p> |
746 | <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 /> |
749 | <h2><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h2> |
747 | </dt> |
|
|
748 | <dd> |
|
|
749 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
750 | <p>Unfortunately, this is unavoidable, as the XIM protocol is racy by |
750 | design. Applications can avoid some crashes at the expense of memory |
751 | design. Applications can avoid some crashes at the expense of memory |
751 | leaks, and Input Methods can avoid some crashes by careful ordering at |
752 | leaks, and Input Methods can avoid some crashes by careful ordering at |
752 | exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds, |
753 | exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds, |
753 | while <strong>SCIM</strong> (or similar input methods) fails. In the end, however, |
754 | while <strong>SCIM</strong> (or similar input methods) fails. In the end, however, |
754 | crashes cannot be completely avoided even if both sides cooperate. |
755 | crashes cannot be completely avoided even if both sides cooperate.</p> |
755 | </dd> |
|
|
756 | <dd> |
|
|
757 | <p>So the only workaround is not to kill your Input Method Servers.</p> |
756 | <p>So the only workaround is not to kill your Input Method Servers.</p> |
758 | </dd> |
757 | <p> |
759 | <p></p> |
758 | </p> |
760 | <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 /> |
759 | <h2><a name="rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></h2> |
761 | </dt> |
|
|
762 | <dd> |
|
|
763 | Rxvt-unicode tries to obey the rule of not charging you for something you |
760 | <p>Rxvt-unicode tries to obey the rule of not charging you for something you |
764 | don't use. One thing you should try is to configure out all settings that |
761 | don't use. One thing you should try is to configure out all settings that |
765 | you don't need, for example, Xft support is a resource hog by design, |
762 | you don't need, for example, Xft support is a resource hog by design, |
766 | when used. Compiling it out ensures that no Xft font will be loaded |
763 | when used. Compiling it out ensures that no Xft font will be loaded |
767 | accidentally when rxvt-unicode tries to find a font for your characters. |
764 | accidentally when rxvt-unicode tries to find a font for your characters.</p> |
768 | </dd> |
|
|
769 | <dd> |
|
|
770 | <p>Also, many people (me included) like large windows and even larger |
765 | <p>Also, many people (me included) like large windows and even larger |
771 | scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use |
766 | scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use |
772 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
767 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
773 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
768 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
774 | use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as |
769 | use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as |
775 | rxvt-unicode then uses 8 bytes per screen cell.</p> |
770 | rxvt-unicode then uses 8 bytes per screen cell.</p> |
776 | </dd> |
771 | <p> |
777 | <p></p> |
772 | </p> |
778 | <dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br /> |
773 | <h2><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h2> |
779 | </dt> |
|
|
780 | <dd> |
|
|
781 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
774 | <p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
782 | it is simply slow. If you still want Xft fonts you might try to disable |
775 | it is simply slow. If you still want Xft fonts you might try to disable |
783 | antialiasing (by appending <code>:antialias=false</code>), which saves lots of |
776 | antialiasing (by appending <code>:antialias=false</code>), which saves lots of |
784 | memory and also speeds up rendering considerably. |
777 | memory and also speeds up rendering considerably.</p> |
785 | </dd> |
778 | <p> |
786 | <p></p> |
779 | </p> |
787 | <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 /> |
780 | <h2><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></h2> |
788 | </dt> |
|
|
789 | <dd> |
|
|
790 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
781 | <p>Rxvt-unicode will use whatever you specify as a font. If it needs to |
791 | fall back to it's default font search list it will prefer X11 core |
782 | fall back to it's default font search list it will prefer X11 core |
792 | fonts, because they are small and fast, and then use Xft fonts. It has |
783 | fonts, because they are small and fast, and then use Xft fonts. It has |
793 | antialiasing disabled for most of them, because the author thinks they |
784 | antialiasing disabled for most of them, because the author thinks they |
794 | look best that way. |
785 | look best that way.</p> |
795 | </dd> |
|
|
796 | <dd> |
|
|
797 | <p>If you want antialiasing, you have to specify the fonts manually.</p> |
786 | <p>If you want antialiasing, you have to specify the fonts manually.</p> |
798 | </dd> |
787 | <p> |
799 | <p></p> |
788 | </p> |
800 | <dt><strong><a name="item_mouse_cut_2fpaste_suddenly_no_longer_works_2e">Mouse cut/paste suddenly no longer works.</a></strong><br /> |
789 | <h2><a name="mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></h2> |
801 | </dt> |
|
|
802 | <dd> |
|
|
803 | Make sure that mouse reporting is actually turned off since killing |
790 | <p>Make sure that mouse reporting is actually turned off since killing |
804 | some editors prematurely may leave the mouse in mouse report mode. I've |
791 | some editors prematurely may leave the mouse in mouse report mode. I've |
805 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
792 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
806 | quick check is to see if cut/paste works when the Alt or Shift keys are |
793 | quick check is to see if cut/paste works when the Alt or Shift keys are |
807 | depressed. See <code>rxvt(7)</code> |
794 | depressed.</p> |
808 | </dd> |
795 | <p> |
809 | <p></p> |
796 | </p> |
810 | <dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br /> |
797 | <h2><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h2> |
811 | </dt> |
|
|
812 | <dd> |
|
|
813 | If no bold colour is set via <code>colorBD:</code>, bold will invert text using the |
798 | <p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the |
814 | standard foreground colour. |
799 | standard foreground colour.</p> |
815 | </dd> |
|
|
816 | <dd> |
|
|
817 | <p>For the standard background colour, blinking will actually make the |
800 | <p>For the standard background colour, blinking will actually make the |
818 | text blink when compiled with <code>--enable-blinking</code>. with standard |
801 | text blink when compiled with <code>--enable-blinking</code>. with standard |
819 | colours. Without <code>--enable-blinking</code>, the blink attribute will be |
802 | colours. Without <code>--enable-blinking</code>, the blink attribute will be |
820 | ignored.</p> |
803 | ignored.</p> |
821 | </dd> |
|
|
822 | <dd> |
|
|
823 | <p>On ANSI colours, bold/blink attributes are used to set high-intensity |
804 | <p>On ANSI colours, bold/blink attributes are used to set high-intensity |
824 | foreground/background colors.</p> |
805 | foreground/background colors.</p> |
825 | </dd> |
|
|
826 | <dd> |
|
|
827 | <p>color0-7 are the low-intensity colors.</p> |
806 | <p>color0-7 are the low-intensity colors.</p> |
828 | </dd> |
|
|
829 | <dd> |
|
|
830 | <p>color8-15 are the corresponding high-intensity colors.</p> |
807 | <p>color8-15 are the corresponding high-intensity colors.</p> |
831 | </dd> |
808 | <p> |
832 | <p></p> |
809 | </p> |
833 | <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 /> |
810 | <h2><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></h2> |
834 | </dt> |
|
|
835 | <dd> |
|
|
836 | You can change the screen colors at run-time using <em>~/.Xdefaults</em> |
811 | <p>You can change the screen colors at run-time using <em>~/.Xdefaults</em> |
837 | resources (or as long-options). |
812 | resources (or as long-options).</p> |
838 | </dd> |
|
|
839 | <dd> |
|
|
840 | <p>Here are values that are supposed to resemble a VGA screen, |
813 | <p>Here are values that are supposed to resemble a VGA screen, |
841 | including the murky brown that passes for low-intensity yellow:</p> |
814 | including the murky brown that passes for low-intensity yellow:</p> |
842 | </dd> |
|
|
843 | <dd> |
|
|
844 | <pre> |
815 | <pre> |
845 | URxvt.color0: #000000 |
816 | URxvt.color0: #000000 |
846 | URxvt.color1: #A80000 |
817 | URxvt.color1: #A80000 |
847 | URxvt.color2: #00A800 |
818 | URxvt.color2: #00A800 |
848 | URxvt.color3: #A8A800 |
819 | URxvt.color3: #A8A800 |
849 | URxvt.color4: #0000A8 |
820 | URxvt.color4: #0000A8 |
850 | URxvt.color5: #A800A8 |
821 | URxvt.color5: #A800A8 |
851 | URxvt.color6: #00A8A8 |
822 | URxvt.color6: #00A8A8 |
852 | URxvt.color7: #A8A8A8</pre> |
823 | URxvt.color7: #A8A8A8</pre> |
853 | </dd> |
|
|
854 | <dd> |
|
|
855 | <pre> |
824 | <pre> |
856 | URxvt.color8: #000054 |
825 | URxvt.color8: #000054 |
857 | URxvt.color9: #FF0054 |
826 | URxvt.color9: #FF0054 |
858 | URxvt.color10: #00FF54 |
827 | URxvt.color10: #00FF54 |
859 | URxvt.color11: #FFFF54 |
828 | URxvt.color11: #FFFF54 |
860 | URxvt.color12: #0000FF |
829 | URxvt.color12: #0000FF |
861 | URxvt.color13: #FF00FF |
830 | URxvt.color13: #FF00FF |
862 | URxvt.color14: #00FFFF |
831 | URxvt.color14: #00FFFF |
863 | URxvt.color15: #FFFFFF</pre> |
832 | URxvt.color15: #FFFFFF</pre> |
864 | </dd> |
|
|
865 | <dd> |
|
|
866 | <p>And here is a more complete set of non-standard colors described (not by |
833 | <p>And here is a more complete set of non-standard colors described (not by |
867 | me) as ``pretty girly''.</p> |
834 | me) as ``pretty girly''.</p> |
868 | </dd> |
|
|
869 | <dd> |
|
|
870 | <pre> |
835 | <pre> |
871 | URxvt.cursorColor: #dc74d1 |
836 | URxvt.cursorColor: #dc74d1 |
872 | URxvt.pointerColor: #dc74d1 |
837 | URxvt.pointerColor: #dc74d1 |
873 | URxvt.background: #0e0e0e |
838 | URxvt.background: #0e0e0e |
874 | URxvt.foreground: #4ad5e1 |
839 | URxvt.foreground: #4ad5e1 |
… | |
… | |
884 | URxvt.color13: #9e88f0 |
849 | URxvt.color13: #9e88f0 |
885 | URxvt.color6: #73f7ff |
850 | URxvt.color6: #73f7ff |
886 | URxvt.color14: #73f7ff |
851 | URxvt.color14: #73f7ff |
887 | URxvt.color7: #e1dddd |
852 | URxvt.color7: #e1dddd |
888 | URxvt.color15: #e1dddd</pre> |
853 | URxvt.color15: #e1dddd</pre> |
889 | </dd> |
854 | <p> |
890 | <p></p> |
855 | </p> |
891 | <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 /> |
856 | <h2><a name="how_can_i_start_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</a></h2> |
892 | </dt> |
|
|
893 | <dd> |
|
|
894 | Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
857 | <p>Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
895 | display, create the listening socket and then fork. |
858 | display, create the listening socket and then fork.</p> |
896 | </dd> |
859 | <p> |
897 | <p></p> |
860 | </p> |
898 | <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 /> |
861 | <h2><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h2> |
899 | </dt> |
|
|
900 | <dd> |
|
|
901 | Assuming that the physical Backspace key corresponds to the |
862 | <p>Assuming that the physical Backspace key corresponds to the |
902 | BackSpace keysym (not likely for Linux ... see the following |
863 | BackSpace keysym (not likely for Linux ... see the following |
903 | question) there are two standard values that can be used for |
864 | question) there are two standard values that can be used for |
904 | Backspace: <code>^H</code> and <code>^?</code>. |
865 | Backspace: <code>^H</code> and <code>^?</code>.</p> |
905 | </dd> |
|
|
906 | <dd> |
|
|
907 | <p>Historically, either value is correct, but rxvt-unicode adopts the debian |
866 | <p>Historically, either value is correct, but rxvt-unicode adopts the debian |
908 | policy of using <code>^?</code> when unsure, because it's the one only only correct |
867 | policy of using <code>^?</code> when unsure, because it's the one only only correct |
909 | choice :).</p> |
868 | choice :).</p> |
910 | </dd> |
|
|
911 | <dd> |
|
|
912 | <p>Rxvt-unicode tries to inherit the current stty settings and uses the value |
869 | <p>Rxvt-unicode tries to inherit the current stty settings and uses the value |
913 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
870 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
914 | started from a terminal (say, from a menu or by remote shell), then the |
871 | started from a terminal (say, from a menu or by remote shell), then the |
915 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
872 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
916 | be used (which may not be the same as your stty setting).</p> |
873 | be used (which may not be the same as your stty setting).</p> |
917 | </dd> |
|
|
918 | <dd> |
|
|
919 | <p>For starting a new rxvt-unicode:</p> |
874 | <p>For starting a new rxvt-unicode:</p> |
920 | </dd> |
|
|
921 | <dd> |
|
|
922 | <pre> |
875 | <pre> |
923 | # use Backspace = ^H |
876 | # use Backspace = ^H |
924 | $ stty erase ^H |
877 | $ stty erase ^H |
925 | $ rxvt</pre> |
878 | $ rxvt</pre> |
926 | </dd> |
|
|
927 | <dd> |
|
|
928 | <pre> |
879 | <pre> |
929 | # use Backspace = ^? |
880 | # use Backspace = ^? |
930 | $ stty erase ^? |
881 | $ stty erase ^? |
931 | $ rxvt</pre> |
882 | $ rxvt</pre> |
932 | </dd> |
|
|
933 | <dd> |
|
|
934 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in rxvt(7).</p> |
883 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p> |
935 | </dd> |
|
|
936 | <dd> |
|
|
937 | <p>For an existing rxvt-unicode:</p> |
884 | <p>For an existing rxvt-unicode:</p> |
938 | </dd> |
|
|
939 | <dd> |
|
|
940 | <pre> |
885 | <pre> |
941 | # use Backspace = ^H |
886 | # use Backspace = ^H |
942 | $ stty erase ^H |
887 | $ stty erase ^H |
943 | $ echo -n "^[[36h"</pre> |
888 | $ echo -n "^[[36h"</pre> |
944 | </dd> |
|
|
945 | <dd> |
|
|
946 | <pre> |
889 | <pre> |
947 | # use Backspace = ^? |
890 | # use Backspace = ^? |
948 | $ stty erase ^? |
891 | $ stty erase ^? |
949 | $ echo -n "^[[36l"</pre> |
892 | $ echo -n "^[[36l"</pre> |
950 | </dd> |
|
|
951 | <dd> |
|
|
952 | <p>This helps satisfy some of the Backspace discrepancies that occur, but |
893 | <p>This helps satisfy some of the Backspace discrepancies that occur, but |
953 | if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value |
894 | if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value |
954 | properly reflects that.</p> |
895 | properly reflects that.</p> |
955 | </dd> |
|
|
956 | <dd> |
|
|
957 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
896 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
958 | To avoid confusion between the Backspace and Delete keys, the Delete |
897 | To avoid confusion between the Backspace and Delete keys, the Delete |
959 | key has been assigned an escape sequence to match the vt100 for Execute |
898 | key has been assigned an escape sequence to match the vt100 for Execute |
960 | (<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> |
899 | (<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> |
961 | </dd> |
|
|
962 | <dd> |
|
|
963 | <p>Some other Backspace problems:</p> |
900 | <p>Some other Backspace problems:</p> |
964 | </dd> |
|
|
965 | <dd> |
|
|
966 | <p>some editors use termcap/terminfo, |
901 | <p>some editors use termcap/terminfo, |
967 | some editors (vim I'm told) expect Backspace = ^H, |
902 | some editors (vim I'm told) expect Backspace = ^H, |
968 | GNU Emacs (and Emacs-like editors) use ^H for help.</p> |
903 | GNU Emacs (and Emacs-like editors) use ^H for help.</p> |
969 | </dd> |
|
|
970 | <dd> |
|
|
971 | <p>Perhaps someday this will all be resolved in a consistent manner.</p> |
904 | <p>Perhaps someday this will all be resolved in a consistent manner.</p> |
972 | </dd> |
905 | <p> |
973 | <p></p> |
906 | </p> |
974 | <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 /> |
907 | <h2><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></h2> |
975 | </dt> |
|
|
976 | <dd> |
|
|
977 | There are some compile-time selections available via configure. Unless |
908 | <p>There are some compile-time selections available via configure. Unless |
978 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
909 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
979 | use the `keysym' resource to alter the keystrings associated with keysyms. |
910 | use the `keysym' resource to alter the keystrings associated with keysyms.</p> |
980 | </dd> |
|
|
981 | <dd> |
|
|
982 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
911 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
983 | </dd> |
|
|
984 | <dd> |
|
|
985 | <pre> |
912 | <pre> |
986 | URxvt.keysym.Home: \033[1~ |
913 | URxvt.keysym.Home: \033[1~ |
987 | URxvt.keysym.End: \033[4~ |
914 | URxvt.keysym.End: \033[4~ |
988 | URxvt.keysym.C-apostrophe: \033<C-'> |
915 | URxvt.keysym.C-apostrophe: \033<C-'> |
989 | URxvt.keysym.C-slash: \033<C-/> |
916 | URxvt.keysym.C-slash: \033<C-/> |
… | |
… | |
1001 | URxvt.keysym.M-Left: \033<M-Left> |
928 | URxvt.keysym.M-Left: \033<M-Left> |
1002 | URxvt.keysym.M-Right: \033<M-Right> |
929 | URxvt.keysym.M-Right: \033<M-Right> |
1003 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
930 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
1004 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
931 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
1005 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> |
932 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> |
1006 | </dd> |
|
|
1007 | <dd> |
|
|
1008 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
933 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
1009 | </dd> |
934 | <p> |
1010 | <p></p> |
935 | </p> |
1011 | <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. |
936 | <h2><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_mappings_that_rxvtunicode_doesn_t_recognize_">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize.</a></h2> |
1012 | How do I make use of them? For example, the Sun Keyboard type 4 |
|
|
1013 | has the following mappings that rxvt-unicode doesn't recognize.</a></strong><br /> |
|
|
1014 | </dt> |
|
|
1015 | <dd> |
|
|
1016 | <pre> |
937 | <pre> |
1017 | KP_Insert == Insert |
938 | KP_Insert == Insert |
1018 | F22 == Print |
939 | F22 == Print |
1019 | F27 == Home |
940 | F27 == Home |
1020 | F29 == Prior |
941 | F29 == Prior |
1021 | F33 == End |
942 | F33 == End |
1022 | F35 == Next</pre> |
943 | F35 == Next</pre> |
1023 | </dd> |
|
|
1024 | <dd> |
|
|
1025 | <p>Rather than have rxvt-unicode try to accommodate all the various possible |
944 | <p>Rather than have rxvt-unicode try to accommodate all the various possible |
1026 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
945 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
1027 | required for your particular machine.</p> |
946 | required for your particular machine.</p> |
1028 | </dd> |
947 | <p> |
1029 | <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? |
948 | </p> |
1030 | I need this to decide about setting colors etc.</a></strong><br /> |
949 | <h2><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h2> |
1031 | </dt> |
|
|
1032 | <dd> |
|
|
1033 | rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
950 | <p>rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
1034 | check and see if that is set. Note that several programs, JED, slrn, |
951 | check and see if that is set. Note that several programs, JED, slrn, |
1035 | Midnight Commander automatically check this variable to decide whether or |
952 | Midnight Commander automatically check this variable to decide whether or |
1036 | not to use color. |
953 | not to use color.</p> |
1037 | </dd> |
954 | <p> |
1038 | <p></p> |
955 | </p> |
1039 | <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 /> |
956 | <h2><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></h2> |
1040 | </dt> |
|
|
1041 | <dd> |
|
|
1042 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
957 | <p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
1043 | insecure mode then it is possible to use the following shell script |
958 | insecure mode then it is possible to use the following shell script |
1044 | snippets to correctly set the display. If your version of rxvt-unicode |
959 | snippets to correctly set the display. If your version of rxvt-unicode |
1045 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
960 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
1046 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
961 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
1047 | regular xterm. |
962 | regular xterm.</p> |
1048 | </dd> |
|
|
1049 | <dd> |
|
|
1050 | <p>Courtesy of Chuck Blake <<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>> with the following shell script |
963 | <p>Courtesy of Chuck Blake <<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>> with the following shell script |
1051 | snippets:</p> |
964 | snippets:</p> |
1052 | </dd> |
|
|
1053 | <dd> |
|
|
1054 | <pre> |
965 | <pre> |
1055 | # Bourne/Korn/POSIX family of shells: |
966 | # Bourne/Korn/POSIX family of shells: |
1056 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
967 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
1057 | if [ ${TERM:-foo} = xterm ]; then |
968 | if [ ${TERM:-foo} = xterm ]; then |
1058 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
969 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
… | |
… | |
1062 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
973 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
1063 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
974 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
1064 | read DISPLAY # set it in our local shell |
975 | read DISPLAY # set it in our local shell |
1065 | fi |
976 | fi |
1066 | fi</pre> |
977 | fi</pre> |
1067 | </dd> |
978 | <p> |
1068 | <p></p> |
979 | </p> |
1069 | <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 /> |
980 | <h2><a name="how_do_i_compile_the_manual_pages_for_myself">How do I compile the manual pages for myself?</a></h2> |
1070 | </dt> |
|
|
1071 | <dd> |
|
|
1072 | You need to have a recent version of perl installed as <em>/usr/bin/perl</em>, |
981 | <p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>, |
1073 | one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to |
982 | one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to |
1074 | the doc subdirectory and enter <code>make alldoc</code>. |
983 | the doc subdirectory and enter <code>make alldoc</code>.</p> |
1075 | </dd> |
984 | <p> |
1076 | <p></p> |
985 | </p> |
1077 | <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 /> |
986 | <h2><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></h2> |
1078 | </dt> |
|
|
1079 | <dd> |
|
|
1080 | Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>, |
987 | <p>Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>, |
1081 | channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be |
988 | channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be |
1082 | interested in learning about new and exciting problems (but not FAQs :). |
989 | interested in learning about new and exciting problems (but not FAQs :).</p> |
1083 | </dd> |
|
|
1084 | <p></p></dl> |
|
|
1085 | <p> |
990 | <p> |
1086 | </p> |
991 | </p> |
1087 | <hr /> |
992 | <hr /> |
1088 | <h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> |
993 | <h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> |
1089 | <p> |
994 | <p> |
1090 | </p> |
995 | </p> |
1091 | <hr /> |
996 | <hr /> |
1092 | <h1><a name="description">DESCRIPTION</a></h1> |
997 | <h1><a name="description">DESCRIPTION</a></h1> |
1093 | <p>The rest of this document describes various technical aspects of |
998 | <p>The rest of this document describes various technical aspects of |
1094 | <strong>rxvt-unicode</strong>. First the description of supported command sequences, |
999 | <strong>rxvt-unicode</strong>. First the description of supported command sequences, |
1095 | followed by menu and pixmap support and last by a description of all |
1000 | followed by pixmap support and last by a description of all features |
1096 | features selectable at <code>configure</code> time.</p> |
1001 | selectable at <code>configure</code> time.</p> |
1097 | <p> |
1002 | <p> |
1098 | </p> |
1003 | </p> |
1099 | <hr /> |
1004 | <hr /> |
1100 | <h1><a name="definitions">Definitions</a></h1> |
1005 | <h1><a name="definitions">Definitions</a></h1> |
1101 | <dl> |
1006 | <dl> |
… | |
… | |
1734 | </table><dt><strong><a name="item_ps__3d_9_x10_xterm"><strong><code>Ps = 9</code> </strong>> X10 XTerm</a></strong><br /> |
1639 | </table><dt><strong><a name="item_ps__3d_9_x10_xterm"><strong><code>Ps = 9</code> </strong>> X10 XTerm</a></strong><br /> |
1735 | </dt> |
1640 | </dt> |
1736 | <table> |
1641 | <table> |
1737 | <tr><td>h</td><td>Send Mouse X & Y on button press.</td></tr> |
1642 | <tr><td>h</td><td>Send Mouse X & Y on button press.</td></tr> |
1738 | <tr><td>l</td><td>No mouse reporting.</td></tr> |
1643 | <tr><td>l</td><td>No mouse reporting.</td></tr> |
1739 | </table><dt><strong><a name="item_10"><strong><code>Ps = 10</code> </strong>> (<strong>rxvt</strong>)</a></strong><br /> |
|
|
1740 | </dt> |
|
|
1741 | <table> |
|
|
1742 | <tr><td>h</td><td>menuBar visible</td></tr> |
|
|
1743 | <tr><td>l</td><td>menuBar invisible</td></tr> |
|
|
1744 | </table><dt><strong><a name="item_ps__3d_25"><strong><code>Ps = 25</code> </strong>></a></strong><br /> |
1644 | </table><dt><strong><a name="item_ps__3d_25"><strong><code>Ps = 25</code> </strong>></a></strong><br /> |
1745 | </dt> |
1645 | </dt> |
1746 | <table> |
1646 | <table> |
1747 | <tr><td>h</td><td>Visible cursor {cnorm/cvvis}</td></tr> |
1647 | <tr><td>h</td><td>Visible cursor {cnorm/cvvis}</td></tr> |
1748 | <tr><td>l</td><td>Invisible cursor {civis}</td></tr> |
1648 | <tr><td>l</td><td>Invisible cursor {civis}</td></tr> |
… | |
… | |
1859 | <tr><td>Ps = 10</td><td>Change colour of text foreground to Pt (NB: may change in future)</td></tr> |
1759 | <tr><td>Ps = 10</td><td>Change colour of text foreground to Pt (NB: may change in future)</td></tr> |
1860 | <tr><td>Ps = 11</td><td>Change colour of text background to Pt (NB: may change in future)</td></tr> |
1760 | <tr><td>Ps = 11</td><td>Change colour of text background to Pt (NB: may change in future)</td></tr> |
1861 | <tr><td>Ps = 12</td><td>Change colour of text cursor foreground to Pt</td></tr> |
1761 | <tr><td>Ps = 12</td><td>Change colour of text cursor foreground to Pt</td></tr> |
1862 | <tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr> |
1762 | <tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr> |
1863 | <tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr> |
1763 | <tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr> |
1864 | <tr><td>Ps = 18</td><td>Change colour of bold characters to Pt</td></tr> |
1764 | <tr><td>Ps = 18</td><td>Change colour of bold characters to Pt [deprecated, see 706]</td></tr> |
1865 | <tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt</td></tr> |
1765 | <tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt [deprecated, see 707]</td></tr> |
1866 | <tr><td>Ps = 20</td><td>Change default background to Pt</td></tr> |
1766 | <tr><td>Ps = 20</td><td>Change background pixmap parameters (see section XPM) (Compile XPM).</td></tr> |
1867 | <tr><td>Ps = 39</td><td>Change default foreground colour to Pt.</td></tr> |
1767 | <tr><td>Ps = 39</td><td>Change default foreground colour to Pt.</td></tr> |
1868 | <tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr> |
1768 | <tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr> |
1869 | <tr><td>Ps = 49</td><td>Change default background colour to Pt.</td></tr> |
1769 | <tr><td>Ps = 49</td><td>Change default background colour to Pt.</td></tr> |
1870 | <tr><td>Ps = 50</td><td>Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n</td></tr> |
1770 | <tr><td>Ps = 50</td><td>Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n</td></tr> |
1871 | <tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr> |
1771 | <tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr> |
1872 | <tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).</td></tr> |
1772 | <tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).</td></tr> |
1873 | <tr><td>Ps = 703</td><td>Menubar command Pt (Compile menubar).</td></tr> |
1773 | <tr><td>Ps = 702</td><td>Request version if Pt is ?, returning rxvt-unicode, the resource name, the major and minor version numbers, e.g. ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST.</td></tr> |
1874 | <tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr> |
1774 | <tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr> |
1875 | <tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt (Compile transparency).</td></tr> |
1775 | <tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt (Compile transparency).</td></tr> |
|
|
1776 | <tr><td>Ps = 706</td><td>Change colour of bold characters to Pt</td></tr> |
|
|
1777 | <tr><td>Ps = 707</td><td>Change colour of underlined characters to Pt</td></tr> |
1876 | <tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr> |
1778 | <tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr> |
1877 | <tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
1779 | <tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
1878 | <tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
1780 | <tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
1879 | <tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
1781 | <tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
1880 | <tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
1782 | <tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
1881 | <tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
1783 | <tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
1882 | <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> |
1784 | <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> |
1883 | </table><p></p></dl> |
1785 | </table><p></p></dl> |
1884 | <p></p> |
1786 | <p></p> |
1885 | <p> |
|
|
1886 | </p> |
|
|
1887 | <hr /> |
|
|
1888 | <h1><a name="menubar">menuBar</a></h1> |
|
|
1889 | <p><strong>The exact syntax used is <em>almost</em> solidified. </strong>> |
|
|
1890 | In the menus, <strong>DON'T</strong> try to use menuBar commands that add or remove a |
|
|
1891 | menuBar.</p> |
|
|
1892 | <p>Note that in all of the commands, the <strong><em>/path/</em> </strong>> <em>cannot</em> be |
|
|
1893 | omitted: use <strong>./</strong> to specify a menu relative to the current menu.</p> |
|
|
1894 | <p> |
|
|
1895 | </p> |
|
|
1896 | <h2><a name="overview_of_menubar_operation">Overview of menuBar operation</a></h2> |
|
|
1897 | <p>For the menuBar XTerm escape sequence <code>ESC ] 703 ; Pt ST</code>, the syntax |
|
|
1898 | of <a href="#item_pt"><code>Pt</code></a> can be used for a variety of tasks:</p> |
|
|
1899 | <p>At the top level is the current menuBar which is a member of a circular |
|
|
1900 | linked-list of other such menuBars.</p> |
|
|
1901 | <p>The menuBar acts as a parent for the various drop-down menus, which in |
|
|
1902 | turn, may have labels, separator lines, menuItems and subMenus.</p> |
|
|
1903 | <p>The menuItems are the useful bits: you can use them to mimic keyboard |
|
|
1904 | input or even to send text or escape sequences back to rxvt.</p> |
|
|
1905 | <p>The menuBar syntax is intended to provide a simple yet robust method of |
|
|
1906 | constructing and manipulating menus and navigating through the |
|
|
1907 | menuBars.</p> |
|
|
1908 | <p>The first step is to use the tag <strong>[menu:<em>name</em>] </strong>> which creates |
|
|
1909 | the menuBar called <em>name</em> and allows access. You may now or menus, |
|
|
1910 | subMenus, and menuItems. Finally, use the tag <strong>[done]</strong> to set the |
|
|
1911 | menuBar access as <strong>readonly</strong> to prevent accidental corruption of the |
|
|
1912 | menus. To re-access the current menuBar for alterations, use the tag |
|
|
1913 | <strong>[menu]</strong>, make the alterations and then use <strong>[done]</strong></p> |
|
|
1914 | <p></p> |
|
|
1915 | <p> |
|
|
1916 | </p> |
|
|
1917 | <h2><a name="commands">Commands</a></h2> |
|
|
1918 | <dl> |
|
|
1919 | <dt><strong><a name="item__5bmenu_3a_2bname_5d"><strong>[menu:+<em>name</em>] </strong>></a></strong><br /> |
|
|
1920 | </dt> |
|
|
1921 | <dd> |
|
|
1922 | access the named menuBar for creation or alteration. If a new menuBar |
|
|
1923 | is created, it is called <em>name</em> (max of 15 chars) and the current |
|
|
1924 | menuBar is pushed onto the stack |
|
|
1925 | </dd> |
|
|
1926 | <p></p> |
|
|
1927 | <dt><strong><a name="item__5bmenu_5d"><strong>[menu]</strong></a></strong><br /> |
|
|
1928 | </dt> |
|
|
1929 | <dd> |
|
|
1930 | access the current menuBar for alteration |
|
|
1931 | </dd> |
|
|
1932 | <p></p> |
|
|
1933 | <dt><strong><a name="item__5btitle_3a_2bstring_5d"><strong>[title:+<em>string</em>] </strong>></a></strong><br /> |
|
|
1934 | </dt> |
|
|
1935 | <dd> |
|
|
1936 | set the current menuBar's title to <em>string</em>, which may contain the |
|
|
1937 | following format specifiers: |
|
|
1938 | </dd> |
|
|
1939 | <dd> |
|
|
1940 | <pre> |
|
|
1941 | B<%n> rxvt name (as per the B<-name> command-line option) |
|
|
1942 | B<%v> rxvt version |
|
|
1943 | B<%%> literal B<%> character</pre> |
|
|
1944 | </dd> |
|
|
1945 | <p></p> |
|
|
1946 | <dt><strong><a name="item__5bdone_5d"><strong>[done]</strong></a></strong><br /> |
|
|
1947 | </dt> |
|
|
1948 | <dd> |
|
|
1949 | set menuBar access as <strong>readonly</strong>. |
|
|
1950 | End-of-file tag for <strong>[read:+<em>file</em>] </strong>> operations. |
|
|
1951 | </dd> |
|
|
1952 | <p></p> |
|
|
1953 | <dt><strong><a name="item__5bread_3a_2bfile_5d"><strong>[read:+<em>file</em>] </strong>></a></strong><br /> |
|
|
1954 | </dt> |
|
|
1955 | <dd> |
|
|
1956 | read menu commands directly from <em>file</em> (extension ``.menu'' will be |
|
|
1957 | appended if required.) Start reading at a line with <strong>[menu]</strong> or <strong>< |
|
|
1958 | [menu:+<em>name</em> </strong>> and continuing until <strong>[done]</strong> is encountered. |
|
|
1959 | </dd> |
|
|
1960 | <dd> |
|
|
1961 | <p>Blank and comment lines (starting with <strong>#</strong>) are ignored. Actually, |
|
|
1962 | since any invalid menu commands are also ignored, almost anything could |
|
|
1963 | be construed as a comment line, but this may be tightened up in the |
|
|
1964 | future ... so don't count on it!.</p> |
|
|
1965 | </dd> |
|
|
1966 | <p></p> |
|
|
1967 | <dt><strong><a name="item__5bread_3a_2bfile_3b_2bname_5d"><strong>[read:+<em>file</em>;+<em>name</em>] </strong>></a></strong><br /> |
|
|
1968 | </dt> |
|
|
1969 | <dd> |
|
|
1970 | The same as <strong>[read:+<em>file</em>] </strong>>, but start reading at a line with |
|
|
1971 | <strong>[menu:+<em>name</em>] </strong>> and continuing until <strong>[done:+<em>name</em>] </strong>> or |
|
|
1972 | <strong>[done]</strong> is encountered. |
|
|
1973 | </dd> |
|
|
1974 | <p></p> |
|
|
1975 | <dt><strong><a name="item__5bdump_5d"><strong>[dump]</strong></a></strong><br /> |
|
|
1976 | </dt> |
|
|
1977 | <dd> |
|
|
1978 | dump all menuBars to the file <strong>/tmp/rxvt-PID</strong> in a format suitable for |
|
|
1979 | later rereading. |
|
|
1980 | </dd> |
|
|
1981 | <p></p> |
|
|
1982 | <dt><strong><a name="item__5brm_3aname_5d"><strong>[rm:name]</strong></a></strong><br /> |
|
|
1983 | </dt> |
|
|
1984 | <dd> |
|
|
1985 | remove the named menuBar |
|
|
1986 | </dd> |
|
|
1987 | <p></p> |
|
|
1988 | <dt><strong><a name="item__5brm_5d__5brm_3a_5d"><strong>[rm] [rm:]</strong></a></strong><br /> |
|
|
1989 | </dt> |
|
|
1990 | <dd> |
|
|
1991 | remove the current menuBar |
|
|
1992 | </dd> |
|
|
1993 | <p></p> |
|
|
1994 | <dt><strong><a name="item__5brm_2a_5d__5brm_3a_2a_5d"><strong>[rm*] [rm:*]</strong></a></strong><br /> |
|
|
1995 | </dt> |
|
|
1996 | <dd> |
|
|
1997 | remove all menuBars |
|
|
1998 | </dd> |
|
|
1999 | <p></p> |
|
|
2000 | <dt><strong><a name="item__5bswap_5d"><strong>[swap]</strong></a></strong><br /> |
|
|
2001 | </dt> |
|
|
2002 | <dd> |
|
|
2003 | swap the top two menuBars |
|
|
2004 | </dd> |
|
|
2005 | <p></p> |
|
|
2006 | <dt><strong><a name="item__5bprev_5d"><strong>[prev]</strong></a></strong><br /> |
|
|
2007 | </dt> |
|
|
2008 | <dd> |
|
|
2009 | access the previous menuBar |
|
|
2010 | </dd> |
|
|
2011 | <p></p> |
|
|
2012 | <dt><strong><a name="item__5bnext_5d"><strong>[next]</strong></a></strong><br /> |
|
|
2013 | </dt> |
|
|
2014 | <dd> |
|
|
2015 | access the next menuBar |
|
|
2016 | </dd> |
|
|
2017 | <p></p> |
|
|
2018 | <dt><strong><a name="item__5bshow_5d"><strong>[show]</strong></a></strong><br /> |
|
|
2019 | </dt> |
|
|
2020 | <dd> |
|
|
2021 | Enable display of the menuBar |
|
|
2022 | </dd> |
|
|
2023 | <p></p> |
|
|
2024 | <dt><strong><a name="item__5bhide_5d"><strong>[hide]</strong></a></strong><br /> |
|
|
2025 | </dt> |
|
|
2026 | <dd> |
|
|
2027 | Disable display of the menuBar |
|
|
2028 | </dd> |
|
|
2029 | <p></p> |
|
|
2030 | <dt><strong><a name="item__5bpixmap_3a_2bname_5d"><strong>[pixmap:+<em>name</em>] </strong>></a></strong><br /> |
|
|
2031 | </dt> |
|
|
2032 | <dt><strong><a name="item__5bpixmap_3a_2bname_3bscaling_5d"><strong>[pixmap:+<em>name</em>;<em>scaling</em>] </strong>></a></strong><br /> |
|
|
2033 | </dt> |
|
|
2034 | <dd> |
|
|
2035 | (set the background pixmap globally |
|
|
2036 | </dd> |
|
|
2037 | <dd> |
|
|
2038 | <p><strong>A Future implementation <em>may</em> make this local to the menubar </strong>>)</p> |
|
|
2039 | </dd> |
|
|
2040 | <p></p> |
|
|
2041 | <dt><strong><a name="item__5b_3a_2bcommand_3a_5d"><strong>[:+<em>command</em>:] </strong>></a></strong><br /> |
|
|
2042 | </dt> |
|
|
2043 | <dd> |
|
|
2044 | ignore the menu readonly status and issue a <em>command</em> to or a menu or |
|
|
2045 | menuitem or change the ; a useful shortcut for setting the quick arrows |
|
|
2046 | from a menuBar. |
|
|
2047 | </dd> |
|
|
2048 | <p></p></dl> |
|
|
2049 | <p></p> |
|
|
2050 | <p> |
|
|
2051 | </p> |
|
|
2052 | <h2><a name="adding_and_accessing_menus">Adding and accessing menus</a></h2> |
|
|
2053 | <p>The following commands may also be <strong>+</strong> prefixed.</p> |
|
|
2054 | <dl> |
|
|
2055 | <dt><strong><a name="item__2f_2b"><strong>/+</strong></a></strong><br /> |
|
|
2056 | </dt> |
|
|
2057 | <dd> |
|
|
2058 | access menuBar top level |
|
|
2059 | </dd> |
|
|
2060 | <p></p> |
|
|
2061 | <dt><strong><a name="item__2e_2f_2b"><strong>./+</strong></a></strong><br /> |
|
|
2062 | </dt> |
|
|
2063 | <dd> |
|
|
2064 | access current menu level |
|
|
2065 | </dd> |
|
|
2066 | <p></p> |
|
|
2067 | <dt><strong><a name="item__2e_2e_2f_2b"><strong>../+</strong></a></strong><br /> |
|
|
2068 | </dt> |
|
|
2069 | <dd> |
|
|
2070 | access parent menu (1 level up) |
|
|
2071 | </dd> |
|
|
2072 | <p></p> |
|
|
2073 | <dt><strong><a name="item__2e_2e_2f_2e_2e_2f"><strong>../../</strong></a></strong><br /> |
|
|
2074 | </dt> |
|
|
2075 | <dd> |
|
|
2076 | access parent menu (multiple levels up) |
|
|
2077 | </dd> |
|
|
2078 | <p></p> |
|
|
2079 | <dt><strong><a name="item__2fpath_2fmenu"><strong><em>/path/</em>menu </strong>></a></strong><br /> |
|
|
2080 | </dt> |
|
|
2081 | <dd> |
|
|
2082 | add/access menu |
|
|
2083 | </dd> |
|
|
2084 | <p></p> |
|
|
2085 | <dt><strong><a name="item__2fpath_2fmenu_2f_2a"><strong><em>/path/</em>menu/* </strong>></a></strong><br /> |
|
|
2086 | </dt> |
|
|
2087 | <dd> |
|
|
2088 | add/access menu and clear it if it exists |
|
|
2089 | </dd> |
|
|
2090 | <p></p> |
|
|
2091 | <dt><strong><a name="item__2fpath_2f_7b_2d_7d"><strong><em>/path/</em>{-} </strong>></a></strong><br /> |
|
|
2092 | </dt> |
|
|
2093 | <dd> |
|
|
2094 | add separator |
|
|
2095 | </dd> |
|
|
2096 | <p></p> |
|
|
2097 | <dt><strong><a name="item__2fpath_2f_7bitem_7d"><strong><em>/path/</em>{item} </strong>></a></strong><br /> |
|
|
2098 | </dt> |
|
|
2099 | <dd> |
|
|
2100 | add <strong>item</strong> as a label |
|
|
2101 | </dd> |
|
|
2102 | <p></p> |
|
|
2103 | <dt><strong><a name="item__2fpath_2f_7bitem_7d_action"><strong><em>/path/</em>{item} action </strong>></a></strong><br /> |
|
|
2104 | </dt> |
|
|
2105 | <dd> |
|
|
2106 | add/alter <em>menuitem</em> with an associated <em>action</em> |
|
|
2107 | </dd> |
|
|
2108 | <p></p> |
|
|
2109 | <dt><strong><a name="item__2fpath_2f_7bitem_7d_7bright_2dtext_7d"><strong><em>/path/</em>{item}{right-text} </strong>></a></strong><br /> |
|
|
2110 | </dt> |
|
|
2111 | <dd> |
|
|
2112 | add/alter <em>menuitem</em> with <strong>right-text</strong> as the right-justified text |
|
|
2113 | and as the associated <em>action</em> |
|
|
2114 | </dd> |
|
|
2115 | <p></p> |
|
|
2116 | <dt><strong><a name="item__2fpath_2f_7bitem_7d_7brtext_7d_action"><strong><em>/path/</em>{item}{rtext} action </strong>></a></strong><br /> |
|
|
2117 | </dt> |
|
|
2118 | <dd> |
|
|
2119 | add/alter <em>menuitem</em> with an associated <em>action</em> and with <strong>rtext</strong> as |
|
|
2120 | the right-justified text. |
|
|
2121 | </dd> |
|
|
2122 | <p></p></dl> |
|
|
2123 | <dl> |
|
|
2124 | <dt><strong><a name="item_special_characters_in_action_must_be_backslash_2de">Special characters in <em>action</em> must be backslash-escaped:</a></strong><br /> |
|
|
2125 | </dt> |
|
|
2126 | <dd> |
|
|
2127 | <strong>\a \b \E \e \n \r \t \octal</strong> |
|
|
2128 | </dd> |
|
|
2129 | <p></p> |
|
|
2130 | <dt><strong><a name="item_or_in_control_2dcharacter_notation_3a">or in control-character notation:</a></strong><br /> |
|
|
2131 | </dt> |
|
|
2132 | <dd> |
|
|
2133 | <strong>^@, ^A .. ^Z .. ^_, ^?</strong> |
|
|
2134 | </dd> |
|
|
2135 | <p></p></dl> |
|
|
2136 | <p>To send a string starting with a <strong>NUL</strong> (<strong>^@</strong>) character to the |
|
|
2137 | program, start <em>action</em> with a pair of <strong>NUL</strong> characters (<strong>^@^@</strong>), |
|
|
2138 | the first of which will be stripped off and the balance directed to the |
|
|
2139 | program. Otherwise if <em>action</em> begins with <strong>NUL</strong> followed by |
|
|
2140 | non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the |
|
|
2141 | balance is sent back to rxvt.</p> |
|
|
2142 | <p>As a convenience for the many Emacs-type editors, <em>action</em> may start |
|
|
2143 | with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be |
|
|
2144 | appended if missed from <strong>M-x</strong> commands.</p> |
|
|
2145 | <p>As a convenience for issuing XTerm <strong>ESC ]</strong> sequences from a menubar (or |
|
|
2146 | quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p> |
|
|
2147 | <dl> |
|
|
2148 | <dt><strong><a name="item_for_example_2c">For example,</a></strong><br /> |
|
|
2149 | </dt> |
|
|
2150 | <dd> |
|
|
2151 | <strong>M-xapropos</strong> is equivalent to <strong>\Exapropos\r</strong> |
|
|
2152 | </dd> |
|
|
2153 | <p></p> |
|
|
2154 | <dt><strong><a name="item_and">and</a></strong><br /> |
|
|
2155 | </dt> |
|
|
2156 | <dd> |
|
|
2157 | <strong>\E]703;mona;100</strong> is equivalent to <strong>\E]703;mona;100\a</strong> |
|
|
2158 | </dd> |
|
|
2159 | <p></p></dl> |
|
|
2160 | <p>The option <strong>{<em>right-rtext</em>} </strong>> will be right-justified. In the |
|
|
2161 | absence of a specified action, this text will be used as the <em>action</em> |
|
|
2162 | as well.</p> |
|
|
2163 | <dl> |
|
|
2164 | <dt><strong>For example,</strong><br /> |
|
|
2165 | </dt> |
|
|
2166 | <dd> |
|
|
2167 | <strong>/File/{Open}{^X^F}</strong> is equivalent to <strong>/File/{Open}{^X^F} ^X^F</strong> |
|
|
2168 | </dd> |
|
|
2169 | <p></p></dl> |
|
|
2170 | <p>The left label <em>is</em> necessary, since it's used for matching, but |
|
|
2171 | implicitly hiding the left label (by using same name for both left and |
|
|
2172 | right labels), or explicitly hiding the left label (by preceeding it |
|
|
2173 | with a dot), makes it possible to have right-justified text only.</p> |
|
|
2174 | <dl> |
|
|
2175 | <dt><strong>For example,</strong><br /> |
|
|
2176 | </dt> |
|
|
2177 | <dd> |
|
|
2178 | <strong>/File/{Open}{Open} Open-File-Action</strong> |
|
|
2179 | </dd> |
|
|
2180 | <p></p> |
|
|
2181 | <dt><strong><a name="item_or_hiding_it">or hiding it</a></strong><br /> |
|
|
2182 | </dt> |
|
|
2183 | <dd> |
|
|
2184 | <strong>/File/{.anylabel}{Open} Open-File-Action</strong> |
|
|
2185 | </dd> |
|
|
2186 | <p></p></dl> |
|
|
2187 | <p></p> |
|
|
2188 | <p> |
|
|
2189 | </p> |
|
|
2190 | <h2><a name="removing_menus">Removing menus</a></h2> |
|
|
2191 | <dl> |
|
|
2192 | <dt><strong><a name="item__2d_2f_2a_2b"><strong>-/*+ </strong>></a></strong><br /> |
|
|
2193 | </dt> |
|
|
2194 | <dd> |
|
|
2195 | remove all menus from the menuBar, the same as <strong>[clear]</strong> |
|
|
2196 | </dd> |
|
|
2197 | <p></p> |
|
|
2198 | <dt><strong><a name="item__2d_2b_2fpathmenu_2b"><strong>-+<em>/path</em>menu+ </strong>></a></strong><br /> |
|
|
2199 | </dt> |
|
|
2200 | <dd> |
|
|
2201 | remove menu |
|
|
2202 | </dd> |
|
|
2203 | <p></p> |
|
|
2204 | <dt><strong><a name="item__2d_2b_2fpath_7bitem_7d_2b"><strong>-+<em>/path</em>{item}+ </strong>></a></strong><br /> |
|
|
2205 | </dt> |
|
|
2206 | <dd> |
|
|
2207 | remove item |
|
|
2208 | </dd> |
|
|
2209 | <p></p> |
|
|
2210 | <dt><strong><a name="item__2d_2b_2fpath_7b_2d_7d"><strong>-+<em>/path</em>{-} </strong>></a></strong><br /> |
|
|
2211 | </dt> |
|
|
2212 | <dd> |
|
|
2213 | remove separator) |
|
|
2214 | </dd> |
|
|
2215 | <p></p> |
|
|
2216 | <dt><strong><a name="item__2d_2fpath_2fmenu_2f_2a"><strong>-/path/menu/*</strong></a></strong><br /> |
|
|
2217 | </dt> |
|
|
2218 | <dd> |
|
|
2219 | remove all items, separators and submenus from menu |
|
|
2220 | </dd> |
|
|
2221 | <p></p></dl> |
|
|
2222 | <p></p> |
|
|
2223 | <p> |
|
|
2224 | </p> |
|
|
2225 | <h2><a name="quick_arrows">Quick Arrows</a></h2> |
|
|
2226 | <p>The menus also provide a hook for <em>quick arrows</em> to provide easier |
|
|
2227 | user access. If nothing has been explicitly set, the default is to |
|
|
2228 | emulate the curror keys. The syntax permits each arrow to be altered |
|
|
2229 | individually or all four at once without re-entering their common |
|
|
2230 | beginning/end text. For example, to explicitly associate cursor actions |
|
|
2231 | with the arrows, any of the following forms could be used:</p> |
|
|
2232 | <dl> |
|
|
2233 | <dt><strong><a name="item__3cr_3e_2bright"><strong><r</strong>+<em>Right</em> >></a></strong><br /> |
|
|
2234 | </dt> |
|
|
2235 | <dt><strong><a name="item__3cl_3e_2bleft"><strong><l</strong>+<em>Left</em> >></a></strong><br /> |
|
|
2236 | </dt> |
|
|
2237 | <dt><strong><a name="item__3cu_3e_2bup"><strong><u</strong>+<em>Up</em> >></a></strong><br /> |
|
|
2238 | </dt> |
|
|
2239 | <dt><strong><a name="item__3cd_3e_2bdown"><strong><d</strong>+<em>Down</em> >></a></strong><br /> |
|
|
2240 | </dt> |
|
|
2241 | <dd> |
|
|
2242 | Define actions for the respective arrow buttons |
|
|
2243 | </dd> |
|
|
2244 | <p></p> |
|
|
2245 | <dt><strong><a name="item__3cb_3e_2bbegin"><strong><b</strong>+<em>Begin</em> >></a></strong><br /> |
|
|
2246 | </dt> |
|
|
2247 | <dt><strong><a name="item__3ce_3e_2bend"><strong><e</strong>+<em>End</em> >></a></strong><br /> |
|
|
2248 | </dt> |
|
|
2249 | <dd> |
|
|
2250 | Define common beginning/end parts for <em>quick arrows</em> which used in |
|
|
2251 | conjunction with the above <r> <l> <u> <d> constructs |
|
|
2252 | </dd> |
|
|
2253 | <p></p></dl> |
|
|
2254 | <dl> |
|
|
2255 | <dt><strong><a name="item_for_example_2c_define_arrows_individually_2c">For example, define arrows individually,</a></strong><br /> |
|
|
2256 | </dt> |
|
|
2257 | <dd> |
|
|
2258 | <pre> |
|
|
2259 | <u>\E[A</pre> |
|
|
2260 | </dd> |
|
|
2261 | <dd> |
|
|
2262 | <pre> |
|
|
2263 | <d>\E[B</pre> |
|
|
2264 | </dd> |
|
|
2265 | <dd> |
|
|
2266 | <pre> |
|
|
2267 | <r>\E[C</pre> |
|
|
2268 | </dd> |
|
|
2269 | <dd> |
|
|
2270 | <pre> |
|
|
2271 | <l>\E[D</pre> |
|
|
2272 | </dd> |
|
|
2273 | <dt><strong><a name="item_or_all_at_once">or all at once</a></strong><br /> |
|
|
2274 | </dt> |
|
|
2275 | <dd> |
|
|
2276 | <pre> |
|
|
2277 | <u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D</pre> |
|
|
2278 | </dd> |
|
|
2279 | <dt><strong><a name="item_compactly">or more compactly (factoring out common parts)</a></strong><br /> |
|
|
2280 | </dt> |
|
|
2281 | <dd> |
|
|
2282 | <pre> |
|
|
2283 | <b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D</pre> |
|
|
2284 | </dd> |
|
|
2285 | </dl> |
|
|
2286 | <p></p> |
|
|
2287 | <p> |
|
|
2288 | </p> |
|
|
2289 | <h2><a name="command_summary">Command Summary</a></h2> |
|
|
2290 | <p>A short summary of the most <em>common</em> commands:</p> |
|
|
2291 | <dl> |
|
|
2292 | <dt><strong><a name="item__5bmenu_3aname_5d">[menu:name]</a></strong><br /> |
|
|
2293 | </dt> |
|
|
2294 | <dd> |
|
|
2295 | use an existing named menuBar or start a new one |
|
|
2296 | </dd> |
|
|
2297 | <p></p> |
|
|
2298 | <dt><strong>[menu]</strong><br /> |
|
|
2299 | </dt> |
|
|
2300 | <dd> |
|
|
2301 | use the current menuBar |
|
|
2302 | </dd> |
|
|
2303 | <p></p> |
|
|
2304 | <dt><strong><a name="item__5btitle_3astring_5d">[title:string]</a></strong><br /> |
|
|
2305 | </dt> |
|
|
2306 | <dd> |
|
|
2307 | set menuBar title |
|
|
2308 | </dd> |
|
|
2309 | <p></p> |
|
|
2310 | <dt><strong>[done]</strong><br /> |
|
|
2311 | </dt> |
|
|
2312 | <dd> |
|
|
2313 | set menu access to readonly and, if reading from a file, signal EOF |
|
|
2314 | </dd> |
|
|
2315 | <p></p> |
|
|
2316 | <dt><strong><a name="item__5bdone_3aname_5d">[done:name]</a></strong><br /> |
|
|
2317 | </dt> |
|
|
2318 | <dd> |
|
|
2319 | if reading from a file using [read:file;name] signal EOF |
|
|
2320 | </dd> |
|
|
2321 | <p></p> |
|
|
2322 | <dt><strong>[rm:name]</strong><br /> |
|
|
2323 | </dt> |
|
|
2324 | <dd> |
|
|
2325 | remove named <code>menuBar(s)</code> |
|
|
2326 | </dd> |
|
|
2327 | <p></p> |
|
|
2328 | <dt><strong>[rm] [rm:]</strong><br /> |
|
|
2329 | </dt> |
|
|
2330 | <dd> |
|
|
2331 | remove current menuBar |
|
|
2332 | </dd> |
|
|
2333 | <p></p> |
|
|
2334 | <dt><strong>[rm*] [rm:*]</strong><br /> |
|
|
2335 | </dt> |
|
|
2336 | <dd> |
|
|
2337 | remove all <code>menuBar(s)</code> |
|
|
2338 | </dd> |
|
|
2339 | <p></p> |
|
|
2340 | <dt><strong>[swap]</strong><br /> |
|
|
2341 | </dt> |
|
|
2342 | <dd> |
|
|
2343 | swap top two menuBars |
|
|
2344 | </dd> |
|
|
2345 | <p></p> |
|
|
2346 | <dt><strong>[prev]</strong><br /> |
|
|
2347 | </dt> |
|
|
2348 | <dd> |
|
|
2349 | access the previous menuBar |
|
|
2350 | </dd> |
|
|
2351 | <p></p> |
|
|
2352 | <dt><strong>[next]</strong><br /> |
|
|
2353 | </dt> |
|
|
2354 | <dd> |
|
|
2355 | access the next menuBar |
|
|
2356 | </dd> |
|
|
2357 | <p></p> |
|
|
2358 | <dt><strong>[show]</strong><br /> |
|
|
2359 | </dt> |
|
|
2360 | <dd> |
|
|
2361 | map menuBar |
|
|
2362 | </dd> |
|
|
2363 | <p></p> |
|
|
2364 | <dt><strong>[hide]</strong><br /> |
|
|
2365 | </dt> |
|
|
2366 | <dd> |
|
|
2367 | unmap menuBar |
|
|
2368 | </dd> |
|
|
2369 | <p></p> |
|
|
2370 | <dt><strong><a name="item__5bpixmap_3bfile_5d">[pixmap;file]</a></strong><br /> |
|
|
2371 | </dt> |
|
|
2372 | <dt><strong><a name="item__5bpixmap_3bfile_3bscaling_5d">[pixmap;file;scaling]</a></strong><br /> |
|
|
2373 | </dt> |
|
|
2374 | <dd> |
|
|
2375 | set a background pixmap |
|
|
2376 | </dd> |
|
|
2377 | <p></p> |
|
|
2378 | <dt><strong><a name="item__5bread_3afile_5d">[read:file]</a></strong><br /> |
|
|
2379 | </dt> |
|
|
2380 | <dt><strong><a name="item__5bread_3afile_3bname_5d">[read:file;name]</a></strong><br /> |
|
|
2381 | </dt> |
|
|
2382 | <dd> |
|
|
2383 | read in a menu from a file |
|
|
2384 | </dd> |
|
|
2385 | <p></p> |
|
|
2386 | <dt><strong>[dump]</strong><br /> |
|
|
2387 | </dt> |
|
|
2388 | <dd> |
|
|
2389 | dump out all menuBars to /tmp/rxvt-PID |
|
|
2390 | </dd> |
|
|
2391 | <p></p> |
|
|
2392 | <dt><strong><a name="item__2f">/</a></strong><br /> |
|
|
2393 | </dt> |
|
|
2394 | <dd> |
|
|
2395 | access menuBar top level |
|
|
2396 | </dd> |
|
|
2397 | <p></p> |
|
|
2398 | <dt><strong><a name="item__2e_2f">./</a></strong><br /> |
|
|
2399 | </dt> |
|
|
2400 | <dt><strong><a name="item__2e_2e_2f">../</a></strong><br /> |
|
|
2401 | </dt> |
|
|
2402 | <dt><strong>../../</strong><br /> |
|
|
2403 | </dt> |
|
|
2404 | <dd> |
|
|
2405 | access current or parent menu level |
|
|
2406 | </dd> |
|
|
2407 | <p></p> |
|
|
2408 | <dt><strong>/path/menu</strong><br /> |
|
|
2409 | </dt> |
|
|
2410 | <dd> |
|
|
2411 | add/access menu |
|
|
2412 | </dd> |
|
|
2413 | <p></p> |
|
|
2414 | <dt><strong>/path/{-}</strong><br /> |
|
|
2415 | </dt> |
|
|
2416 | <dd> |
|
|
2417 | add separator |
|
|
2418 | </dd> |
|
|
2419 | <p></p> |
|
|
2420 | <dt><strong>/path/{item}{rtext} action</strong><br /> |
|
|
2421 | </dt> |
|
|
2422 | <dd> |
|
|
2423 | add/alter menu item |
|
|
2424 | </dd> |
|
|
2425 | <p></p> |
|
|
2426 | <dt><strong><a name="item__2d_2f_2a">-/*</a></strong><br /> |
|
|
2427 | </dt> |
|
|
2428 | <dd> |
|
|
2429 | remove all menus from the menuBar |
|
|
2430 | </dd> |
|
|
2431 | <p></p> |
|
|
2432 | <dt><strong><a name="item__2d_2fpath_2fmenu">-/path/menu</a></strong><br /> |
|
|
2433 | </dt> |
|
|
2434 | <dd> |
|
|
2435 | remove menu items, separators and submenus from menu |
|
|
2436 | </dd> |
|
|
2437 | <p></p> |
|
|
2438 | <dt><strong>-/path/menu</strong><br /> |
|
|
2439 | </dt> |
|
|
2440 | <dd> |
|
|
2441 | remove menu |
|
|
2442 | </dd> |
|
|
2443 | <p></p> |
|
|
2444 | <dt><strong><a name="item__2d_2fpath_2f_7bitem_7d">-/path/{item}</a></strong><br /> |
|
|
2445 | </dt> |
|
|
2446 | <dd> |
|
|
2447 | remove item |
|
|
2448 | </dd> |
|
|
2449 | <p></p> |
|
|
2450 | <dt><strong><a name="item__2d_2fpath_2f_7b_2d_7d">-/path/{-}</a></strong><br /> |
|
|
2451 | </dt> |
|
|
2452 | <dd> |
|
|
2453 | remove separator |
|
|
2454 | </dd> |
|
|
2455 | <p></p> |
|
|
2456 | <dt><strong><a name="item__3cb_3ebegin_3cr_3eright_3cl_3eleft_3cu_3eup_3cd_3"><b>Begin<r>Right<l>Left<u>Up<d>Down<e>End</a></strong><br /> |
|
|
2457 | </dt> |
|
|
2458 | <dd> |
|
|
2459 | menu quick arrows |
|
|
2460 | </dd> |
|
|
2461 | <p></p></dl> |
|
|
2462 | <p> |
1787 | <p> |
2463 | </p> |
1788 | </p> |
2464 | <hr /> |
1789 | <hr /> |
2465 | <h1><a name="xpm">XPM</a></h1> |
1790 | <h1><a name="xpm">XPM</a></h1> |
2466 | <p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>> then value |
1791 | <p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>> then value |
… | |
… | |
2715 | </dd> |
2040 | </dd> |
2716 | <p></p> |
2041 | <p></p> |
2717 | <dt><strong><a name="item_unicode3">--enable-unicode3 (default: off)</a></strong><br /> |
2042 | <dt><strong><a name="item_unicode3">--enable-unicode3 (default: off)</a></strong><br /> |
2718 | </dt> |
2043 | </dt> |
2719 | <dd> |
2044 | <dd> |
|
|
2045 | Recommended to stay off unless you really need non-BMP characters. |
|
|
2046 | </dd> |
|
|
2047 | <dd> |
2720 | Enable direct support for displaying unicode codepoints above |
2048 | <p>Enable direct support for displaying unicode codepoints above |
2721 | 65535 (the basic multilingual page). This increases storage |
2049 | 65535 (the basic multilingual page). This increases storage |
2722 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2050 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2723 | support these extra characters, but Xft does. |
2051 | support these extra characters, but Xft does.</p> |
2724 | </dd> |
2052 | </dd> |
2725 | <dd> |
2053 | <dd> |
2726 | <p>Please note that rxvt-unicode can store unicode code points >65535 |
2054 | <p>Please note that rxvt-unicode can store unicode code points >65535 |
2727 | even without this flag, but the number of such characters is |
2055 | even without this flag, but the number of such characters is |
2728 | limited to a view thousand (shared with combining characters, |
2056 | limited to a view thousand (shared with combining characters, |
… | |
… | |
2738 | where accents are encoded as seperate unicode characters. This is |
2066 | where accents are encoded as seperate unicode characters. This is |
2739 | done by using precomposited characters when available or creating |
2067 | done by using precomposited characters when available or creating |
2740 | new pseudo-characters when no precomposed form exists. |
2068 | new pseudo-characters when no precomposed form exists. |
2741 | </dd> |
2069 | </dd> |
2742 | <dd> |
2070 | <dd> |
2743 | <p>Without --enable-unicode3, the number of additional precomposed characters |
2071 | <p>Without --enable-unicode3, the number of additional precomposed |
2744 | is rather limited (2048, if this is full, rxvt-unicode will use the |
2072 | characters is somewhat limited (the 6400 private use characters will be |
2745 | private use area, extending the number of combinations to 8448). With |
|
|
2746 | --enable-unicode3, no practical limit exists.</p> |
2073 | (ab-)used). With --enable-unicode3, no practical limit exists.</p> |
2747 | </dd> |
2074 | </dd> |
2748 | <dd> |
2075 | <dd> |
2749 | <p>This option will also enable storage (but not display) of characters |
2076 | <p>This option will also enable storage (but not display) of characters |
2750 | beyond plane 0 (>65535) when --enable-unicode3 was not specified.</p> |
2077 | beyond plane 0 (>65535) when --enable-unicode3 was not specified.</p> |
2751 | </dd> |
2078 | </dd> |
… | |
… | |
2756 | </dd> |
2083 | </dd> |
2757 | <p></p> |
2084 | <p></p> |
2758 | <dt><strong><a name="item_fallback">--enable-fallback(=CLASS) (default: Rxvt)</a></strong><br /> |
2085 | <dt><strong><a name="item_fallback">--enable-fallback(=CLASS) (default: Rxvt)</a></strong><br /> |
2759 | </dt> |
2086 | </dt> |
2760 | <dd> |
2087 | <dd> |
2761 | When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback. |
2088 | When reading resource settings, also read settings for class CLASS. To |
|
|
2089 | disable resource fallback use --disable-fallback. |
2762 | </dd> |
2090 | </dd> |
2763 | <p></p> |
2091 | <p></p> |
2764 | <dt><strong><a name="item_name">--with-res-name=NAME (default: urxvt)</a></strong><br /> |
2092 | <dt><strong><a name="item_name">--with-res-name=NAME (default: urxvt)</a></strong><br /> |
2765 | </dt> |
2093 | </dt> |
2766 | <dd> |
2094 | <dd> |
… | |
… | |
2797 | Write user and tty to lastlog file (used by programs like |
2125 | Write user and tty to lastlog file (used by programs like |
2798 | <em>lastlogin</em>) at start of rxvt execution. This option requires |
2126 | <em>lastlogin</em>) at start of rxvt execution. This option requires |
2799 | --enable-utmp to also be specified. |
2127 | --enable-utmp to also be specified. |
2800 | </dd> |
2128 | </dd> |
2801 | <p></p> |
2129 | <p></p> |
2802 | <dt><strong><a name="item_background">--enable-xpm-background (default: off)</a></strong><br /> |
2130 | <dt><strong><a name="item_background">--enable-xpm-background (default: on)</a></strong><br /> |
2803 | </dt> |
2131 | </dt> |
2804 | <dd> |
2132 | <dd> |
2805 | Add support for XPM background pixmaps. |
2133 | Add support for XPM background pixmaps. |
2806 | </dd> |
2134 | </dd> |
2807 | <p></p> |
2135 | <p></p> |
2808 | <dt><strong><a name="item_transparency">--enable-transparency (default: off)</a></strong><br /> |
2136 | <dt><strong><a name="item_transparency">--enable-transparency (default: on)</a></strong><br /> |
2809 | </dt> |
2137 | </dt> |
2810 | <dd> |
2138 | <dd> |
2811 | Add support for inheriting parent backgrounds thus giving a fake |
2139 | Add support for inheriting parent backgrounds thus giving a fake |
2812 | transparency to the term. |
2140 | transparency to the term. |
2813 | </dd> |
2141 | </dd> |
… | |
… | |
2820 | <p></p> |
2148 | <p></p> |
2821 | <dt><strong><a name="item_tinting">--enable-tinting (default: on)</a></strong><br /> |
2149 | <dt><strong><a name="item_tinting">--enable-tinting (default: on)</a></strong><br /> |
2822 | </dt> |
2150 | </dt> |
2823 | <dd> |
2151 | <dd> |
2824 | Add support for tinting of transparent backgrounds (requires <code>--enable-transparency</code>). |
2152 | Add support for tinting of transparent backgrounds (requires <code>--enable-transparency</code>). |
2825 | </dd> |
|
|
2826 | <p></p> |
|
|
2827 | <dt><strong><a name="item_menubar">--enable-menubar (default: off)</a></strong><br /> |
|
|
2828 | </dt> |
|
|
2829 | <dd> |
|
|
2830 | Add support for our menu bar system (this interacts badly with |
|
|
2831 | dynamic locale switching currently). |
|
|
2832 | </dd> |
2153 | </dd> |
2833 | <p></p> |
2154 | <p></p> |
2834 | <dt><strong><a name="item_scroll">--enable-rxvt-scroll (default: on)</a></strong><br /> |
2155 | <dt><strong><a name="item_scroll">--enable-rxvt-scroll (default: on)</a></strong><br /> |
2835 | </dt> |
2156 | </dt> |
2836 | <dd> |
2157 | <dd> |
… | |
… | |
2855 | Add support for a very unobtrusive, plain-looking scrollbar that |
2176 | Add support for a very unobtrusive, plain-looking scrollbar that |
2856 | is the favourite of the rxvt-unicode author, having used it for |
2177 | is the favourite of the rxvt-unicode author, having used it for |
2857 | many years. |
2178 | many years. |
2858 | </dd> |
2179 | </dd> |
2859 | <p></p> |
2180 | <p></p> |
2860 | <dt><strong><a name="item_shadow">--enable-half-shadow (default: off)</a></strong><br /> |
|
|
2861 | </dt> |
|
|
2862 | <dd> |
|
|
2863 | Make shadows on the scrollbar only half the normal width & height. |
|
|
2864 | only applicable to rxvt scrollbars. |
|
|
2865 | </dd> |
|
|
2866 | <p></p> |
|
|
2867 | <dt><strong><a name="item_ttygid">--enable-ttygid (default: off)</a></strong><br /> |
2181 | <dt><strong><a name="item_ttygid">--enable-ttygid (default: off)</a></strong><br /> |
2868 | </dt> |
2182 | </dt> |
2869 | <dd> |
2183 | <dd> |
2870 | Change tty device setting to group ``tty'' - only use this if |
2184 | Change tty device setting to group ``tty'' - only use this if |
2871 | your system uses this type of security. |
2185 | your system uses this type of security. |
… | |
… | |
2886 | <p></p> |
2200 | <p></p> |
2887 | <dt><strong><a name="item__2d_2ddisable_2dresources">--disable-resources</a></strong><br /> |
2201 | <dt><strong><a name="item__2d_2ddisable_2dresources">--disable-resources</a></strong><br /> |
2888 | </dt> |
2202 | </dt> |
2889 | <dd> |
2203 | <dd> |
2890 | Removes any support for resource checking. |
2204 | Removes any support for resource checking. |
2891 | </dd> |
|
|
2892 | <p></p> |
|
|
2893 | <dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br /> |
|
|
2894 | </dt> |
|
|
2895 | <dd> |
|
|
2896 | Make resources checking via <code>XGetDefault()</code> instead of our small |
|
|
2897 | version which only checks ~/.Xdefaults, or if that doesn't exist then |
|
|
2898 | ~/.Xresources. |
|
|
2899 | </dd> |
|
|
2900 | <dd> |
|
|
2901 | <p>Please note that nowadays, things like XIM will automatically pull in and |
|
|
2902 | use the full X resource manager, so the overhead of using it might be very |
|
|
2903 | small, if nonexistant.</p> |
|
|
2904 | </dd> |
|
|
2905 | <p></p> |
|
|
2906 | <dt><strong><a name="item_strings">--enable-strings (default: off)</a></strong><br /> |
|
|
2907 | </dt> |
|
|
2908 | <dd> |
|
|
2909 | Add support for our possibly faster <code>memset()</code> function and other |
|
|
2910 | various routines, overriding your system's versions which may |
|
|
2911 | have been hand-crafted in assembly or may require extra libraries |
|
|
2912 | to link in. (this breaks ANSI-C rules and has problems on many |
|
|
2913 | GNU/Linux systems). |
|
|
2914 | </dd> |
2205 | </dd> |
2915 | <p></p> |
2206 | <p></p> |
2916 | <dt><strong><a name="item__2d_2ddisable_2dswapscreen">--disable-swapscreen</a></strong><br /> |
2207 | <dt><strong><a name="item__2d_2ddisable_2dswapscreen">--disable-swapscreen</a></strong><br /> |
2917 | </dt> |
2208 | </dt> |
2918 | <dd> |
2209 | <dd> |
… | |
… | |
2934 | <pre> |
2225 | <pre> |
2935 | MWM-hints |
2226 | MWM-hints |
2936 | EWMH-hints (pid, utf8 names) and protocols (ping) |
2227 | EWMH-hints (pid, utf8 names) and protocols (ping) |
2937 | seperate underline colour (-underlineColor) |
2228 | seperate underline colour (-underlineColor) |
2938 | settable border widths and borderless switch (-w, -b, -bl) |
2229 | settable border widths and borderless switch (-w, -b, -bl) |
|
|
2230 | visual depth selection (-depth) |
2939 | settable extra linespacing /-lsp) |
2231 | settable extra linespacing /-lsp) |
2940 | iso-14755-2 and -3, and visual feedback |
2232 | iso-14755-2 and -3, and visual feedback |
2941 | backindex and forwardindex escape sequence |
|
|
2942 | window op and some xterm/OSC escape sequences |
|
|
2943 | tripleclickwords (-tcw) |
2233 | tripleclickwords (-tcw) |
2944 | settable insecure mode (-insecure) |
2234 | settable insecure mode (-insecure) |
2945 | keysym remapping support |
2235 | keysym remapping support |
2946 | cursor blinking and underline cursor (-cb, -uc) |
2236 | cursor blinking and underline cursor (-cb, -uc) |
2947 | XEmbed support (-embed) |
2237 | XEmbed support (-embed) |
2948 | user-pty (-pty-fd) |
2238 | user-pty (-pty-fd) |
2949 | hold on exit (-hold) |
2239 | hold on exit (-hold) |
2950 | skip builtin block graphics (-sbg) |
2240 | skip builtin block graphics (-sbg)</pre> |
|
|
2241 | </dd> |
|
|
2242 | <dd> |
|
|
2243 | <p>It also enabled some non-essential features otherwise disabled, such as:</p> |
|
|
2244 | </dd> |
|
|
2245 | <dd> |
|
|
2246 | <pre> |
|
|
2247 | some round-trip time optimisations |
|
|
2248 | nearest color allocation on pseudocolor screens |
|
|
2249 | UTF8_STRING supporr for selection |
2951 | sgr modes 90..97 and 100..107</pre> |
2250 | sgr modes 90..97 and 100..107 |
|
|
2251 | backindex and forwardindex escape sequences |
|
|
2252 | view change/zero scorllback esacpe sequences |
|
|
2253 | locale switching escape sequence |
|
|
2254 | window op and some xterm/OSC escape sequences |
|
|
2255 | rectangular selections |
|
|
2256 | trailing space removal for selections |
|
|
2257 | verbose X error handling</pre> |
2952 | </dd> |
2258 | </dd> |
2953 | <p></p> |
2259 | <p></p> |
2954 | <dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br /> |
2260 | <dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br /> |
2955 | </dt> |
2261 | </dt> |
2956 | <dd> |
2262 | <dd> |
… | |
… | |
3019 | </dt> |
2325 | </dt> |
3020 | <dd> |
2326 | <dd> |
3021 | Add support to have the pointer disappear when typing or inactive. |
2327 | Add support to have the pointer disappear when typing or inactive. |
3022 | </dd> |
2328 | </dd> |
3023 | <p></p> |
2329 | <p></p> |
3024 | <dt><strong><a name="item_perl">--enable-perl (default: off)</a></strong><br /> |
2330 | <dt><strong><a name="item_perl">--enable-perl (default: on)</a></strong><br /> |
3025 | </dt> |
2331 | </dt> |
3026 | <dd> |
2332 | <dd> |
3027 | Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong> |
2333 | Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong> |
3028 | manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files |
2334 | manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files |
3029 | in <em>src/perl-ext/</em> for the extensions that are installed by default. The |
2335 | in <em>src/perl-ext/</em> for the extensions that are installed by default. The |