… | |
… | |
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> |
19 | <ul> |
20 | |
20 | |
21 | <li><a href="#the_new_selection_selects_pieces_that_are_too_big__how_can_i_select">The new selection selects pieces that are too big, how can I select</a></li> |
21 | <li><a href="#the_new_selection_selects_pieces_that_are_too_big__how_can_i_select">The new selection selects pieces that are too big, how can I select</a></li> |
|
|
22 | <li><a href="#i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i">I don't like the new selection/popups/hotkeys/perl, how do I</a></li> |
|
|
23 | <li><a href="#the_cursor_moves_when_selecting_text_in_the_current_input_line__how">The cursor moves when selecting text in the current input line, how</a></li> |
|
|
24 | <li><a href="#during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor</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">I am maintaining rxvt-unicode for distribution/OS XXX, any</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_">I'm using keyboard model XXX that has extra Prior/Next/Insert keys.</a></li> |
|
|
74 | <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm">How do I distinguish wether I'm running rxvt-unicode or a regular xterm?</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> |
22 | </ul> |
78 | </ul> |
23 | |
79 | |
24 | <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> |
80 | <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> |
25 | <li><a href="#description">DESCRIPTION</a></li> |
81 | <li><a href="#description">DESCRIPTION</a></li> |
26 | <li><a href="#definitions">Definitions</a></li> |
82 | <li><a href="#definitions">Definitions</a></li> |
… | |
… | |
69 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
125 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
70 | <p> |
126 | <p> |
71 | </p> |
127 | </p> |
72 | <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 |
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 |
73 | single words?</a></h2> |
129 | single words?</a></h2> |
74 | <p>Yes. For example, if you want to select alphanumeric words, you can use |
130 | <p>If you want to select e.g. alphanumeric words, you can use the following |
75 | the following resource:</p> |
131 | setting:</p> |
76 | <pre> |
132 | <pre> |
77 | URxvt.selection.pattern-0: ([[:word:]]+)</pre> |
133 | URxvt.selection.pattern-0: ([[:word:]]+)</pre> |
78 | <p>If you click more than twice, the selection will be extended |
134 | <p>If you click more than twice, the selection will be extended |
79 | more and more.</p> |
135 | more and more.</p> |
80 | <p>To get a selection that is very similar to the old code, try this pattern:</p> |
136 | <p>To get a selection that is very similar to the old code, try this pattern:</p> |
81 | <pre> |
137 | <pre> |
82 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)</pre> |
138 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)</pre> |
83 | <p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also |
139 | <p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also |
84 | selects words like the old code.</p> |
140 | selects words like the old code.</p> |
85 | <dl> |
141 | <p> |
|
|
142 | </p> |
86 | <dt><strong><a name="item_i_don_27t_like_the_new_selection_2fpopups_2fhotkey">I don't like the new selection/popups/hotkeys/perl, how do I |
143 | <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 |
87 | change/disable it?</a></strong><br /> |
144 | change/disable it?</a></h2> |
88 | </dt> |
|
|
89 | <dd> |
|
|
90 | You can disable the perl extension completely by setting the |
145 | <p>You can disable the perl extension completely by setting the |
91 | <strong>perl-ext-common</strong> resource to the empty string, which also keeps |
146 | <strong>perl-ext-common</strong> resource to the empty string, which also keeps |
92 | rxvt-unicode from initialising perl, saving memory. |
147 | rxvt-unicode from initialising perl, saving memory.</p> |
93 | </dd> |
|
|
94 | <dd> |
|
|
95 | <p>If you only want to disable specific features, you first have to |
148 | <p>If you only want to disable specific features, you first have to |
96 | identify which perl extension is responsible. For this, read the section |
149 | identify which perl extension is responsible. For this, read the section |
97 | <strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For |
150 | <strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For |
98 | example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify |
151 | example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify |
99 | this <strong>perl-ext-common</strong> resource:</p> |
152 | this <strong>perl-ext-common</strong> resource:</p> |
100 | </dd> |
|
|
101 | <dd> |
|
|
102 | <pre> |
153 | <pre> |
103 | URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre> |
154 | URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre> |
104 | </dd> |
|
|
105 | <dd> |
|
|
106 | <p>This will keep the default extensions, but disable the two popup |
155 | <p>This will keep the default extensions, but disable the two popup |
107 | extensions. Some extensions can also be configured, for example, |
156 | extensions. Some extensions can also be configured, for example, |
108 | scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any |
157 | scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any |
109 | other combination either by setting the <strong>searchable-scrollback</strong> resource:</p> |
158 | other combination either by setting the <strong>searchable-scrollback</strong> resource:</p> |
110 | </dd> |
|
|
111 | <dd> |
|
|
112 | <pre> |
159 | <pre> |
113 | URxvt.searchable-scrollback: CM-s</pre> |
160 | URxvt.searchable-scrollback: CM-s</pre> |
114 | </dd> |
161 | <p> |
115 | <p></p> |
162 | </p> |
116 | <dt><strong><a name="item_the_cursor_moves_when_selecting_text_in_the_curren">The cursor moves when selecting text in the current input line, how |
163 | <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 |
117 | do I switch this off?</a></strong><br /> |
164 | do I switch this off?</a></h2> |
118 | </dt> |
165 | <p> |
119 | <dt><strong><a name="item_during_rlogin_2fssh_2ftelnet_2fetc_2e_sessions_2c_">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor |
166 | </p> |
|
|
167 | <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 |
120 | outputs strange escape sequences, how do I fix this?</a></strong><br /> |
168 | outputs strange escape sequences, how do I fix this?</a></h2> |
121 | </dt> |
|
|
122 | <dd> |
|
|
123 | These are caused by the <code>readline</code> perl extension. Under normal |
169 | <p>These are caused by the <code>readline</code> perl extension. Under normal |
124 | circumstances, it will move your cursor around when you click into the |
170 | circumstances, it will move your cursor around when you click into the |
125 | line that contains it. It tries hard not to do this at the wrong moment, |
171 | line that contains it. It tries hard not to do this at the wrong moment, |
126 | but when running a program that doesn't parse cursor movements or in some |
172 | but when running a program that doesn't parse cursor movements or in some |
127 | cases during rlogin sessions, it fails to detect this properly. |
173 | cases during rlogin sessions, it fails to detect this properly.</p> |
128 | </dd> |
|
|
129 | <dd> |
|
|
130 | <p>You can permamently switch this feature off by disabling the <code>readline</code> |
174 | <p>You can permamently switch this feature off by disabling the <code>readline</code> |
131 | extension:</p> |
175 | extension:</p> |
132 | </dd> |
|
|
133 | <dd> |
|
|
134 | <pre> |
176 | <pre> |
135 | URxvt.perl-ext-common: default,-readline</pre> |
177 | URxvt.perl-ext-common: default,-readline</pre> |
136 | </dd> |
178 | <p> |
137 | <p></p> |
179 | </p> |
138 | <dt><strong><a name="item_why_doesn_27t_rxvt_2dunicode_read_my_resources_3f">Why doesn't rxvt-unicode read my resources?</a></strong><br /> |
180 | <h2><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h2> |
139 | </dt> |
|
|
140 | <dd> |
|
|
141 | Well, why, indeed? It does, in a way very similar to other X |
181 | <p>Well, why, indeed? It does, in a way very similar to other X |
142 | applications. Most importantly, this means that if you or your OS loads |
182 | applications. Most importantly, this means that if you or your OS loads |
143 | resources into the X display (the right way to do it), rxvt-unicode will |
183 | resources into the X display (the right way to do it), rxvt-unicode will |
144 | ignore any resource files in your home directory. It will only read |
184 | ignore any resource files in your home directory. It will only read |
145 | <em>$HOME/.Xdefaults</em> when no resources are attached to the display. |
185 | <em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p> |
146 | </dd> |
|
|
147 | <dd> |
|
|
148 | <p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that |
186 | <p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that |
149 | resources are loaded into your X-server. In this case, you have to |
187 | resources are loaded into your X-server. In this case, you have to |
150 | re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p> |
188 | re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p> |
151 | </dd> |
|
|
152 | <dd> |
|
|
153 | <p>Also consider the form resources have to use:</p> |
189 | <p>Also consider the form resources have to use:</p> |
154 | </dd> |
|
|
155 | <dd> |
|
|
156 | <pre> |
190 | <pre> |
157 | URxvt.resource: value</pre> |
191 | URxvt.resource: value</pre> |
158 | </dd> |
|
|
159 | <dd> |
|
|
160 | <p>If you want to use another form (there are lots of different ways of |
192 | <p>If you want to use another form (there are lots of different ways of |
161 | specifying resources), make sure you understand wether and why it |
193 | specifying resources), make sure you understand wether and why it |
162 | works. If unsure, use the form above.</p> |
194 | works. If unsure, use the form above.</p> |
163 | </dd> |
195 | <p> |
164 | <p></p> |
196 | </p> |
165 | <dt><strong><a name="item_i_can_27t_get_transparency_working_2c_what_am_i_do">I can't get transparency working, what am I doing wrong?</a></strong><br /> |
197 | <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> |
166 | </dt> |
|
|
167 | <dd> |
|
|
168 | First of all, transparency isn't officially supported in rxvt-unicode, so |
198 | <p>First of all, transparency isn't officially supported in rxvt-unicode, so |
169 | you are mostly on your own. Do not bug the author about it (but you may |
199 | you are mostly on your own. Do not bug the author about it (but you may |
170 | bug everybody else). Also, if you can't get it working consider it a rite |
200 | bug everybody else). Also, if you can't get it working consider it a rite |
171 | of passage: ... and you failed. |
201 | of passage: ... and you failed.</p> |
172 | </dd> |
|
|
173 | <dd> |
|
|
174 | <p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option |
202 | <p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option |
175 | descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p> |
203 | descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p> |
176 | </dd> |
|
|
177 | <dd> |
|
|
178 | <p>1. Use inheritPixmap:</p> |
204 | <p>1. Use inheritPixmap:</p> |
179 | </dd> |
|
|
180 | <dd> |
|
|
181 | <pre> |
205 | <pre> |
182 | Esetroot wallpaper.jpg |
206 | Esetroot wallpaper.jpg |
183 | rxvt -ip -tint red -sh 40</pre> |
207 | rxvt -ip -tint red -sh 40</pre> |
184 | </dd> |
|
|
185 | <dd> |
|
|
186 | <p>That works. If you think it doesn't, you lack transparency and tinting |
208 | <p>That works. If you think it doesn't, you lack transparency and tinting |
187 | support, or you are unable to read.</p> |
209 | support, or you are unable to read.</p> |
188 | </dd> |
|
|
189 | <dd> |
|
|
190 | <p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
210 | <p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
191 | to use effects other than tinting and shading: Just shade/tint/whatever |
211 | to use effects other than tinting and shading: Just shade/tint/whatever |
192 | your picture with gimp:</p> |
212 | your picture with gimp:</p> |
193 | </dd> |
|
|
194 | <dd> |
|
|
195 | <pre> |
213 | <pre> |
196 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
214 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
197 | rxvt -pixmap background.xpm -pe automove-background</pre> |
215 | rxvt -pixmap background.xpm -pe automove-background</pre> |
198 | </dd> |
|
|
199 | <dd> |
|
|
200 | <p>That works. If you think it doesn't, you lack XPM and Perl support, or you |
216 | <p>That works. If you think it doesn't, you lack XPM and Perl support, or you |
201 | are unable to read.</p> |
217 | are unable to read.</p> |
202 | </dd> |
|
|
203 | <dd> |
|
|
204 | <p>3. Use an ARGB visual:</p> |
218 | <p>3. Use an ARGB visual:</p> |
205 | </dd> |
|
|
206 | <dd> |
|
|
207 | <pre> |
219 | <pre> |
208 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre> |
220 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre> |
209 | </dd> |
|
|
210 | <dd> |
|
|
211 | <p>This requires XFT support, and the support of your X-server. If that |
221 | <p>This requires XFT support, and the support of your X-server. If that |
212 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
222 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
213 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
223 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
214 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
224 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
215 | doesn't mean that your WM has the required kludges in place.</p> |
225 | doesn't mean that your WM has the required kludges in place.</p> |
216 | </dd> |
|
|
217 | <dd> |
|
|
218 | <p>4. Use xcompmgr and let it do the job:</p> |
226 | <p>4. Use xcompmgr and let it do the job:</p> |
219 | </dd> |
|
|
220 | <dd> |
|
|
221 | <pre> |
227 | <pre> |
222 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
228 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
223 | -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre> |
229 | -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre> |
224 | </dd> |
|
|
225 | <dd> |
|
|
226 | <p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code> |
230 | <p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code> |
227 | by other values to change the degree of opacity. If it doesn't work and |
231 | by other values to change the degree of opacity. If it doesn't work and |
228 | your server crashes, you got to keep the pieces.</p> |
232 | your server crashes, you got to keep the pieces.</p> |
229 | </dd> |
233 | <p> |
230 | <p></p> |
234 | </p> |
231 | <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 /> |
235 | <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> |
232 | </dt> |
|
|
233 | <dd> |
|
|
234 | I often get asked about this, and I think, no, they didn't cause extra |
236 | <p>I often get asked about this, and I think, no, they didn't cause extra |
235 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
237 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
236 | that the urxvt binary is larger (due to some encoding tables always being |
238 | that the urxvt binary is larger (due to some encoding tables always being |
237 | compiled in), but it actually uses less memory (RSS) after startup. Even |
239 | compiled in), but it actually uses less memory (RSS) after startup. Even |
238 | with <code>--disable-everything</code>, this comparison is a bit unfair, as many |
240 | with <code>--disable-everything</code>, this comparison is a bit unfair, as many |
239 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
241 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
240 | already in use in this mode. |
242 | already in use in this mode.</p> |
241 | </dd> |
|
|
242 | <dd> |
|
|
243 | <pre> |
243 | <pre> |
244 | text data bss drs rss filename |
244 | text data bss drs rss filename |
245 | 98398 1664 24 15695 1824 rxvt --disable-everything |
245 | 98398 1664 24 15695 1824 rxvt --disable-everything |
246 | 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> |
246 | 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> |
247 | </dd> |
|
|
248 | <dd> |
|
|
249 | <p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft |
247 | <p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft |
250 | and full locale/XIM support which are quite bloaty inside libX11 and my |
248 | and full locale/XIM support which are quite bloaty inside libX11 and my |
251 | libc), the two diverge, but not unreasnobaly so.</p> |
249 | libc), the two diverge, but not unreasnobaly so.</p> |
252 | </dd> |
|
|
253 | <dd> |
|
|
254 | <pre> |
250 | <pre> |
255 | text data bss drs rss filename |
251 | text data bss drs rss filename |
256 | 163431 2152 24 20123 2060 rxvt --enable-everything |
252 | 163431 2152 24 20123 2060 rxvt --enable-everything |
257 | 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre> |
253 | 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre> |
258 | </dd> |
|
|
259 | <dd> |
|
|
260 | <p>The very large size of the text section is explained by the east-asian |
254 | <p>The very large size of the text section is explained by the east-asian |
261 | encoding tables, which, if unused, take up disk space but nothing else |
255 | encoding tables, which, if unused, take up disk space but nothing else |
262 | and can be compiled out unless you rely on X11 core fonts that use those |
256 | and can be compiled out unless you rely on X11 core fonts that use those |
263 | encodings. The BSS size comes from the 64k emergency buffer that my c++ |
257 | encodings. The BSS size comes from the 64k emergency buffer that my c++ |
264 | compiler allocates (but of course doesn't use unless you are out of |
258 | compiler allocates (but of course doesn't use unless you are out of |
265 | memory). Also, using an xft font instead of a core font immediately adds a |
259 | memory). Also, using an xft font instead of a core font immediately adds a |
266 | few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when |
260 | few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when |
267 | not used.</p> |
261 | not used.</p> |
268 | </dd> |
|
|
269 | <dd> |
|
|
270 | <p>Of course, due to every character using two or four bytes instead of one, |
262 | <p>Of course, due to every character using two or four bytes instead of one, |
271 | a large scrollback buffer will ultimately make rxvt-unicode use more |
263 | a large scrollback buffer will ultimately make rxvt-unicode use more |
272 | memory.</p> |
264 | memory.</p> |
273 | </dd> |
|
|
274 | <dd> |
|
|
275 | <p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
265 | <p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
276 | still fares rather well. And compared to some monsters like gnome-terminal |
266 | still fares rather well. And compared to some monsters like gnome-terminal |
277 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
267 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
278 | 43180k in daemons that stay around after exit, plus half a minute of |
268 | 43180k in daemons that stay around after exit, plus half a minute of |
279 | startup time, including the hundreds of warnings it spits out), it fares |
269 | startup time, including the hundreds of warnings it spits out), it fares |
280 | extremely well *g*.</p> |
270 | extremely well *g*.</p> |
281 | </dd> |
271 | <p> |
282 | <p></p> |
272 | </p> |
283 | <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 /> |
273 | <h2><a name="why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></h2> |
284 | </dt> |
|
|
285 | <dd> |
|
|
286 | Is this a question? :) It comes up very often. The simple answer is: I had |
274 | <p>Is this a question? :) It comes up very often. The simple answer is: I had |
287 | to write it, and C++ allowed me to write and maintain it in a fraction |
275 | to write it, and C++ allowed me to write and maintain it in a fraction |
288 | of the time and effort (which is a scarce resource for me). Put even |
276 | of the time and effort (which is a scarce resource for me). Put even |
289 | shorter: It simply wouldn't exist without C++. |
277 | shorter: It simply wouldn't exist without C++.</p> |
290 | </dd> |
|
|
291 | <dd> |
|
|
292 | <p>My personal stance on this is that C++ is less portable than C, but in |
278 | <p>My personal stance on this is that C++ is less portable than C, but in |
293 | the case of rxvt-unicode this hardly matters, as its portability limits |
279 | the case of rxvt-unicode this hardly matters, as its portability limits |
294 | are defined by things like X11, pseudo terminals, locale support and unix |
280 | are defined by things like X11, pseudo terminals, locale support and unix |
295 | domain sockets, which are all less portable than C++ itself.</p> |
281 | domain sockets, which are all less portable than C++ itself.</p> |
296 | </dd> |
|
|
297 | <dd> |
|
|
298 | <p>Regarding the bloat, see the above question: It's easy to write programs |
282 | <p>Regarding the bloat, see the above question: It's easy to write programs |
299 | in C that use gobs of memory, an certainly possible to write programs in |
283 | in C that use gobs of memory, an certainly possible to write programs in |
300 | C++ that don't. C++ also often comes with large libraries, but this is |
284 | C++ that don't. C++ also often comes with large libraries, but this is |
301 | not necessarily the case with GCC. Here is what rxvt links against on my |
285 | not necessarily the case with GCC. Here is what rxvt links against on my |
302 | system with a minimal config:</p> |
286 | system with a minimal config:</p> |
303 | </dd> |
|
|
304 | <dd> |
|
|
305 | <pre> |
287 | <pre> |
306 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
288 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
307 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
289 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
308 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
290 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
309 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
291 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
310 | </dd> |
|
|
311 | <dd> |
|
|
312 | <p>And here is rxvt-unicode:</p> |
292 | <p>And here is rxvt-unicode:</p> |
313 | </dd> |
|
|
314 | <dd> |
|
|
315 | <pre> |
293 | <pre> |
316 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
294 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
317 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
295 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
318 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
296 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
319 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
297 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
320 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
298 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
321 | </dd> |
|
|
322 | <dd> |
|
|
323 | <p>No large bloated libraries (of course, none were linked in statically), |
299 | <p>No large bloated libraries (of course, none were linked in statically), |
324 | except maybe libX11 :)</p> |
300 | except maybe libX11 :)</p> |
325 | </dd> |
301 | <p> |
326 | <p></p> |
302 | </p> |
327 | <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 /> |
303 | <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> |
328 | </dt> |
|
|
329 | <dd> |
|
|
330 | Beginning with version 7.3, there is a perl extension that implements a |
304 | <p>Beginning with version 7.3, there is a perl extension that implements a |
331 | simple tabbed terminal. It is installed by default, so any of these should |
305 | simple tabbed terminal. It is installed by default, so any of these should |
332 | give you tabs: |
306 | give you tabs:</p> |
333 | </dd> |
|
|
334 | <dd> |
|
|
335 | <pre> |
307 | <pre> |
336 | rxvt -pe tabbed</pre> |
308 | rxvt -pe tabbed</pre> |
337 | </dd> |
|
|
338 | <dd> |
|
|
339 | <pre> |
309 | <pre> |
340 | URxvt.perl-ext-common: default,tabbed</pre> |
310 | URxvt.perl-ext-common: default,tabbed</pre> |
341 | </dd> |
|
|
342 | <dd> |
|
|
343 | <p>It will also work fine with tabbing functionality of many window managers |
311 | <p>It will also work fine with tabbing functionality of many window managers |
344 | or similar tabbing programs, and its embedding-features allow it to be |
312 | or similar tabbing programs, and its embedding-features allow it to be |
345 | embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or |
313 | embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or |
346 | the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt |
314 | the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt |
347 | (murxvt) terminal as an example embedding application.</p> |
315 | (murxvt) terminal as an example embedding application.</p> |
348 | </dd> |
316 | <p> |
349 | <p></p> |
317 | </p> |
350 | <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 /> |
318 | <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> |
351 | </dt> |
|
|
352 | <dd> |
|
|
353 | The version number is displayed with the usage (-h). Also the escape |
319 | <p>The version number is displayed with the usage (-h). Also the escape |
354 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. When |
320 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. When |
355 | using the rxvtc client, the version displayed is that of the |
321 | using the rxvtc client, the version displayed is that of the |
356 | daemon. |
322 | daemon.</p> |
357 | </dd> |
323 | <p> |
358 | <p></p> |
324 | </p> |
359 | <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 /> |
325 | <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> |
360 | </dt> |
|
|
361 | <dd> |
|
|
362 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
326 | <p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
363 | patches that considerably change the behaviour of rxvt-unicode (but |
327 | patches that considerably change the behaviour of rxvt-unicode (but |
364 | unfortunately this notice has been removed). Before reporting a bug to |
328 | unfortunately this notice has been removed). Before reporting a bug to |
365 | the original rxvt-unicode author please download and install the genuine |
329 | the original rxvt-unicode author please download and install the genuine |
366 | version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce |
330 | version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce |
367 | the problem. If you cannot, chances are that the problems are specific to |
331 | the problem. If you cannot, chances are that the problems are specific to |
368 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
332 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
369 | Tracking System (use <code>reportbug</code> to report the bug). |
333 | Tracking System (use <code>reportbug</code> to report the bug).</p> |
370 | </dd> |
|
|
371 | <dd> |
|
|
372 | <p>For other problems that also affect the Debian package, you can and |
334 | <p>For other problems that also affect the Debian package, you can and |
373 | probably should use the Debian BTS, too, because, after all, it's also a |
335 | probably should use the Debian BTS, too, because, after all, it's also a |
374 | bug in the Debian version and it serves as a reminder for other users that |
336 | bug in the Debian version and it serves as a reminder for other users that |
375 | might encounter the same issue.</p> |
337 | might encounter the same issue.</p> |
376 | </dd> |
338 | <p> |
377 | <p></p> |
339 | </p> |
378 | <dt><strong><a name="item_i_am_maintaining_rxvt_2dunicode_for_distribution_2">I am maintaining rxvt-unicode for distribution/OS XXX, any |
340 | <h2><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any |
379 | recommendation?</a></strong><br /> |
341 | recommendation?</a></h2> |
380 | </dt> |
|
|
381 | <dd> |
|
|
382 | You should build one binary with the default options. <em>configure</em> |
342 | <p>You should build one binary with the default options. <em>configure</em> |
383 | now enables most useful options, and the trend goes to making them |
343 | now enables most useful options, and the trend goes to making them |
384 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
344 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
385 | except higher disk and possibly memory usage. The perl interpreter should |
345 | except higher disk and possibly memory usage. The perl interpreter should |
386 | be enabled, as important functionality (menus, selection, likely more in |
346 | be enabled, as important functionality (menus, selection, likely more in |
387 | the future) depends on it. |
347 | the future) depends on it.</p> |
388 | </dd> |
|
|
389 | <dd> |
|
|
390 | <p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources |
348 | <p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources |
391 | system-wide (except maybe with <code>defaults</code>). This will result in useful |
349 | system-wide (except maybe with <code>defaults</code>). This will result in useful |
392 | behaviour. If your distribution aims at low memory, add an empty |
350 | behaviour. If your distribution aims at low memory, add an empty |
393 | <code>perl-ext-common</code> resource to the app-defaults file. This will keep the |
351 | <code>perl-ext-common</code> resource to the app-defaults file. This will keep the |
394 | perl interpreter disabled until the user enables it.</p> |
352 | perl interpreter disabled until the user enables it.</p> |
395 | </dd> |
|
|
396 | <dd> |
|
|
397 | <p>If you can/want build more binaries, I recommend building a minimal |
353 | <p>If you can/want build more binaries, I recommend building a minimal |
398 | one with <code>--disable-everything</code> (very useful) and a maximal one with |
354 | one with <code>--disable-everything</code> (very useful) and a maximal one with |
399 | <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of |
355 | <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of |
400 | encodings built-in that increase download times and are rarely used).</p> |
356 | encodings built-in that increase download times and are rarely used).</p> |
401 | </dd> |
357 | <p> |
402 | <p></p> |
358 | </p> |
403 | <dt><strong><a name="item_i_need_to_make_it_setuid_2fsetgid_to_support_utmp_">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></strong><br /> |
359 | <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> |
404 | </dt> |
|
|
405 | <dd> |
|
|
406 | It should be, starting with release 7.1. You are encouraged to properly |
360 | <p>It should be, starting with release 7.1. You are encouraged to properly |
407 | install urxvt with privileges necessary for your OS now. |
361 | install urxvt with privileges necessary for your OS now.</p> |
408 | </dd> |
|
|
409 | <dd> |
|
|
410 | <p>When rxvt-unicode detects that it runs setuid or setgid, it will fork |
362 | <p>When rxvt-unicode detects that it runs setuid or setgid, it will fork |
411 | into a helper process for privileged operations (pty handling on some |
363 | into a helper process for privileged operations (pty handling on some |
412 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
364 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
413 | immediately. This is much safer than most other terminals that keep |
365 | immediately. This is much safer than most other terminals that keep |
414 | privileges while running (but is more relevant to urxvt, as it contains |
366 | privileges while running (but is more relevant to urxvt, as it contains |
415 | things as perl interpreters, which might be ``helpful'' to attackers).</p> |
367 | things as perl interpreters, which might be ``helpful'' to attackers).</p> |
416 | </dd> |
|
|
417 | <dd> |
|
|
418 | <p>This forking is done as the very first within main(), which is very early |
368 | <p>This forking is done as the very first within main(), which is very early |
419 | and reduces possible bugs to initialisation code run before main(), or |
369 | and reduces possible bugs to initialisation code run before main(), or |
420 | things like the dynamic loader of your system, which should result in very |
370 | things like the dynamic loader of your system, which should result in very |
421 | little risk.</p> |
371 | little risk.</p> |
422 | </dd> |
372 | <p> |
423 | <p></p> |
373 | </p> |
424 | <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 /> |
374 | <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> |
425 | </dt> |
|
|
426 | <dd> |
|
|
427 | The terminal description used by rxvt-unicode is not as widely available |
375 | <p>The terminal description used by rxvt-unicode is not as widely available |
428 | as that for xterm, or even rxvt (for which the same problem often arises). |
376 | as that for xterm, or even rxvt (for which the same problem often arises).</p> |
429 | </dd> |
|
|
430 | <dd> |
|
|
431 | <p>The correct solution for this problem is to install the terminfo, this can |
377 | <p>The correct solution for this problem is to install the terminfo, this can |
432 | be done like this (with ncurses' infocmp):</p> |
378 | be done like this (with ncurses' infocmp):</p> |
433 | </dd> |
|
|
434 | <dd> |
|
|
435 | <pre> |
379 | <pre> |
436 | REMOTE=remotesystem.domain |
380 | REMOTE=remotesystem.domain |
437 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"</pre> |
381 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"</pre> |
438 | </dd> |
|
|
439 | <dd> |
|
|
440 | <p>... or by installing rxvt-unicode normally on the remote system,</p> |
382 | <p>... or by installing rxvt-unicode normally on the remote system,</p> |
441 | </dd> |
|
|
442 | <dd> |
|
|
443 | <p>If you cannot or do not want to do this, then you can simply set |
383 | <p>If you cannot or do not want to do this, then you can simply set |
444 | <code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of |
384 | <code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of |
445 | problems arising, which includes wrong keymapping, less and different |
385 | problems arising, which includes wrong keymapping, less and different |
446 | colours and some refresh errors in fullscreen applications. It's a nice |
386 | colours and some refresh errors in fullscreen applications. It's a nice |
447 | quick-and-dirty workaround for rare cases, though.</p> |
387 | quick-and-dirty workaround for rare cases, though.</p> |
448 | </dd> |
|
|
449 | <dd> |
|
|
450 | <p>If you always want to do this (and are fine with the consequences) you |
388 | <p>If you always want to do this (and are fine with the consequences) you |
451 | can either recompile rxvt-unicode with the desired TERM value or use a |
389 | can either recompile rxvt-unicode with the desired TERM value or use a |
452 | resource to set it:</p> |
390 | resource to set it:</p> |
453 | </dd> |
|
|
454 | <dd> |
|
|
455 | <pre> |
391 | <pre> |
456 | URxvt.termName: rxvt</pre> |
392 | URxvt.termName: rxvt</pre> |
457 | </dd> |
|
|
458 | <dd> |
|
|
459 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
393 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
460 | the rxvt terminfo file with the rxvt-unicode one.</p> |
394 | the rxvt terminfo file with the rxvt-unicode one.</p> |
461 | </dd> |
395 | <p> |
462 | <p></p> |
396 | </p> |
463 | <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 /> |
397 | <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> |
464 | </dt> |
|
|
465 | <dd> |
|
|
466 | Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
398 | <p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
467 | <code>enacs=\E[0@</code> and try again. |
399 | <code>enacs=\E[0@</code> and try again.</p> |
468 | </dd> |
400 | <p> |
469 | <p></p> |
401 | </p> |
470 | <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 /> |
402 | <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> |
471 | </dt> |
403 | <p> |
|
|
404 | </p> |
472 | <dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> |
405 | <h2><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h2> |
473 | </dt> |
|
|
474 | <dd> |
|
|
475 | One reason you might want this is that some distributions or operating |
406 | <p>One reason you might want this is that some distributions or operating |
476 | systems still compile some programs using the long-obsoleted termcap |
407 | systems still compile some programs using the long-obsoleted termcap |
477 | library (Fedora Core's bash is one example) and rely on a termcap entry |
408 | library (Fedora Core's bash is one example) and rely on a termcap entry |
478 | for <code>rxvt-unicode</code>. |
409 | for <code>rxvt-unicode</code>.</p> |
479 | </dd> |
|
|
480 | <dd> |
|
|
481 | <p>You could use rxvt's termcap entry with resonable results in many cases. |
410 | <p>You could use rxvt's termcap entry with resonable results in many cases. |
482 | You can also create a termcap entry by using terminfo's infocmp program |
411 | You can also create a termcap entry by using terminfo's infocmp program |
483 | like this:</p> |
412 | like this:</p> |
484 | </dd> |
|
|
485 | <dd> |
|
|
486 | <pre> |
413 | <pre> |
487 | infocmp -C rxvt-unicode</pre> |
414 | infocmp -C rxvt-unicode</pre> |
488 | </dd> |
|
|
489 | <dd> |
|
|
490 | <p>Or you could use this termcap entry, generated by the command above:</p> |
415 | <p>Or you could use this termcap entry, generated by the command above:</p> |
491 | </dd> |
|
|
492 | <dd> |
|
|
493 | <pre> |
416 | <pre> |
494 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
417 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
495 | :am:bw:eo:km:mi:ms:xn:xo:\ |
418 | :am:bw:eo:km:mi:ms:xn:xo:\ |
496 | :co#80:it#8:li#24:lm#0:\ |
419 | :co#80:it#8:li#24:lm#0:\ |
497 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
420 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
… | |
… | |
509 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
432 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
510 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
433 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
511 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
434 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
512 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
435 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
513 | :vs=\E[?25h:</pre> |
436 | :vs=\E[?25h:</pre> |
514 | </dd> |
437 | <p> |
515 | <p></p> |
438 | </p> |
516 | <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 /> |
439 | <h2><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h2> |
517 | </dt> |
|
|
518 | <dd> |
|
|
519 | The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to |
440 | <p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to |
520 | decide wether a terminal has colour, but uses it's own configuration |
441 | decide wether a terminal has colour, but uses it's own configuration |
521 | file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among |
442 | file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among |
522 | with most other terminals supporting colour). Either add: |
443 | with most other terminals supporting colour). Either add:</p> |
523 | </dd> |
|
|
524 | <dd> |
|
|
525 | <pre> |
444 | <pre> |
526 | TERM rxvt-unicode</pre> |
445 | TERM rxvt-unicode</pre> |
527 | </dd> |
|
|
528 | <dd> |
|
|
529 | <p>to <code>/etc/DIR_COLORS</code> or simply add:</p> |
446 | <p>to <code>/etc/DIR_COLORS</code> or simply add:</p> |
530 | </dd> |
|
|
531 | <dd> |
|
|
532 | <pre> |
447 | <pre> |
533 | alias ls='ls --color=auto'</pre> |
448 | alias ls='ls --color=auto'</pre> |
534 | </dd> |
|
|
535 | <dd> |
|
|
536 | <p>to your <code>.profile</code> or <code>.bashrc</code>.</p> |
449 | <p>to your <code>.profile</code> or <code>.bashrc</code>.</p> |
537 | </dd> |
450 | <p> |
538 | <p></p> |
451 | </p> |
539 | <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 /> |
452 | <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> |
540 | </dt> |
453 | <p> |
|
|
454 | </p> |
541 | <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 /> |
455 | <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> |
542 | </dt> |
456 | <p> |
|
|
457 | </p> |
543 | <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 /> |
458 | <h2><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h2> |
544 | </dt> |
|
|
545 | <dd> |
|
|
546 | Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged |
459 | <p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged |
547 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
460 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
548 | by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra |
461 | by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra |
549 | features. Unfortunately, some of these (most notably, again, Debian |
462 | features. Unfortunately, some of these (most notably, again, Debian |
550 | GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo |
463 | GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo |
551 | file, so you will need to install it on your own (See the question <strong>When |
464 | file, so you will need to install it on your own (See the question <strong>When |
552 | I log-in to another system it tells me about missing terminfo data?</strong> on |
465 | I log-in to another system it tells me about missing terminfo data?</strong> on |
553 | how to do this). |
466 | how to do this).</p> |
554 | </dd> |
467 | <p> |
555 | <p></p> |
468 | </p> |
556 | <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 /> |
469 | <h2><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h2> |
557 | </dt> |
|
|
558 | <dd> |
|
|
559 | Some Debian GNUL/Linux users seem to have this problem, although no |
470 | <p>Some Debian GNUL/Linux users seem to have this problem, although no |
560 | specific details were reported so far. It is possible that this is caused |
471 | specific details were reported so far. It is possible that this is caused |
561 | by the wrong <code>TERM</code> setting, although the details of wether and how |
472 | by the wrong <code>TERM</code> setting, although the details of wether and how |
562 | this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible |
473 | this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible |
563 | keymap. See the answer to the previous question, and please report if that |
474 | keymap. See the answer to the previous question, and please report if that |
564 | helped. |
475 | helped.</p> |
565 | </dd> |
476 | <p> |
566 | <p></p> |
477 | </p> |
567 | <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 /> |
478 | <h2><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h2> |
568 | </dt> |
479 | <p> |
|
|
480 | </p> |
569 | <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> |
570 | </dt> |
|
|
571 | <dd> |
|
|
572 | If you encounter strange problems like typing an accented character but |
482 | <p>If you encounter strange problems like typing an accented character but |
573 | 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 |
574 | subtly garbled, then you should check your locale settings. |
484 | subtly garbled, then you should check your locale settings.</p> |
575 | </dd> |
|
|
576 | <dd> |
|
|
577 | <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 |
578 | 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 |
579 | 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 |
580 | 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> |
581 | </dd> |
|
|
582 | <dd> |
|
|
583 | <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 |
584 | 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> |
585 | </dd> |
|
|
586 | <dd> |
|
|
587 | <pre> |
491 | <pre> |
588 | printf '\e]701;%s\007' "$LC_CTYPE"</pre> |
492 | printf '\e]701;%s\007' "$LC_CTYPE"</pre> |
589 | </dd> |
|
|
590 | <dd> |
|
|
591 | <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 |
592 | 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 |
593 | 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 |
594 | 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 |
595 | like:</p> |
497 | like:</p> |
596 | </dd> |
|
|
597 | <dd> |
|
|
598 | <pre> |
498 | <pre> |
599 | locale: Cannot set LC_CTYPE to default locale: ...</pre> |
499 | locale: Cannot set LC_CTYPE to default locale: ...</pre> |
600 | </dd> |
|
|
601 | <dd> |
|
|
602 | <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> |
603 | </dd> |
|
|
604 | <dd> |
|
|
605 | <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 |
606 | 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 |
607 | support locales :(</p> |
503 | support locales :(</p> |
608 | </dd> |
504 | <p> |
609 | <p></p> |
505 | </p> |
610 | <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> |
611 | </dt> |
507 | <p> |
|
|
508 | </p> |
612 | <dt><strong><a name="item_how_does_rxvt_2dunicode_choose_fonts_3f">How does rxvt-unicode choose fonts?</a></strong><br /> |
509 | <h2><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h2> |
613 | </dt> |
|
|
614 | <dd> |
|
|
615 | Most fonts do not contain the full range of Unicode, which is |
510 | <p>Most fonts do not contain the full range of Unicode, which is |
616 | fine. Chances are that the font you (or the admin/package maintainer of |
511 | fine. Chances are that the font you (or the admin/package maintainer of |
617 | your system/os) have specified does not cover all the characters you want |
512 | your system/os) have specified does not cover all the characters you want |
618 | to display. |
513 | to display.</p> |
619 | </dd> |
|
|
620 | <dd> |
|
|
621 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
514 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
622 | font. Often the result is fine, but sometimes the chosen font looks |
515 | font. Often the result is fine, but sometimes the chosen font looks |
623 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
516 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
624 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
517 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
625 | intelligence to detect that a specific glyph is wrong: it has to believe |
518 | intelligence to detect that a specific glyph is wrong: it has to believe |
626 | the font that the characters it claims to contain indeed look correct.</p> |
519 | the font that the characters it claims to contain indeed look correct.</p> |
627 | </dd> |
|
|
628 | <dd> |
|
|
629 | <p>In that case, select a font of your taste and add it to the font list, |
520 | <p>In that case, select a font of your taste and add it to the font list, |
630 | e.g.:</p> |
521 | e.g.:</p> |
631 | </dd> |
|
|
632 | <dd> |
|
|
633 | <pre> |
522 | <pre> |
634 | rxvt -fn basefont,font2,font3...</pre> |
523 | rxvt -fn basefont,font2,font3...</pre> |
635 | </dd> |
|
|
636 | <dd> |
|
|
637 | <p>When rxvt-unicode sees a character, it will first look at the base |
524 | <p>When rxvt-unicode sees a character, it will first look at the base |
638 | font. If the base font does not contain the character, it will go to the |
525 | font. If the base font does not contain the character, it will go to the |
639 | next font, and so on. Specifying your own fonts will also speed up this |
526 | next font, and so on. Specifying your own fonts will also speed up this |
640 | search and use less resources within rxvt-unicode and the X-server.</p> |
527 | search and use less resources within rxvt-unicode and the X-server.</p> |
641 | </dd> |
|
|
642 | <dd> |
|
|
643 | <p>The only limitation is that none of the fonts may be larger than the base |
528 | <p>The only limitation is that none of the fonts may be larger than the base |
644 | font, as the base font defines the terminal character cell size, which |
529 | font, as the base font defines the terminal character cell size, which |
645 | must be the same due to the way terminals work.</p> |
530 | must be the same due to the way terminals work.</p> |
646 | </dd> |
531 | <p> |
647 | <p></p> |
532 | </p> |
648 | <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 /> |
533 | <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> |
649 | </dt> |
|
|
650 | <dd> |
|
|
651 | This is because there is a difference between script and language -- |
534 | <p>This is because there is a difference between script and language -- |
652 | rxvt-unicode does not know which language the text that is output is, |
535 | rxvt-unicode does not know which language the text that is output is, |
653 | as it only knows the unicode character codes. If rxvt-unicode first |
536 | as it only knows the unicode character codes. If rxvt-unicode first |
654 | sees a japanese/chinese character, it might choose a japanese font for |
537 | sees a japanese/chinese character, it might choose a japanese font for |
655 | display. Subsequent japanese characters will use that font. Now, many |
538 | display. Subsequent japanese characters will use that font. Now, many |
656 | chinese characters aren't represented in japanese fonts, so when the first |
539 | chinese characters aren't represented in japanese fonts, so when the first |
657 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
540 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
658 | -- unfortunately at this point, it will still use the japanese font for |
541 | -- unfortunately at this point, it will still use the japanese font for |
659 | chinese characters that are also in the japanese font. |
542 | chinese characters that are also in the japanese font.</p> |
660 | </dd> |
|
|
661 | <dd> |
|
|
662 | <p>The workaround is easy: just tag a chinese font at the end of your font |
543 | <p>The workaround is easy: just tag a chinese font at the end of your font |
663 | list (see the previous question). The key is to view the font list as |
544 | list (see the previous question). The key is to view the font list as |
664 | a preference list: If you expect more japanese, list a japanese font |
545 | a preference list: If you expect more japanese, list a japanese font |
665 | first. If you expect more chinese, put a chinese font first.</p> |
546 | first. If you expect more chinese, put a chinese font first.</p> |
666 | </dd> |
|
|
667 | <dd> |
|
|
668 | <p>In the future it might be possible to switch language preferences at |
547 | <p>In the future it might be possible to switch language preferences at |
669 | runtime (the internal data structure has no problem with using different |
548 | runtime (the internal data structure has no problem with using different |
670 | fonts for the same character at the same time, but no interface for this |
549 | fonts for the same character at the same time, but no interface for this |
671 | has been designed yet).</p> |
550 | has been designed yet).</p> |
672 | </dd> |
|
|
673 | <dd> |
|
|
674 | <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> |
551 | <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> |
675 | </dd> |
552 | <p> |
676 | <p></p> |
553 | </p> |
677 | <dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br /> |
554 | <h2><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h2> |
678 | </dt> |
|
|
679 | <dd> |
|
|
680 | Most fonts were not designed for terminal use, which means that character |
555 | <p>Most fonts were not designed for terminal use, which means that character |
681 | size varies a lot. A font that is otherwise fine for terminal use might |
556 | size varies a lot. A font that is otherwise fine for terminal use might |
682 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
557 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
683 | these characters. For characters that are just ``a bit'' too wide a special |
558 | these characters. For characters that are just ``a bit'' too wide a special |
684 | ``careful'' rendering mode is used that redraws adjacent characters. |
559 | ``careful'' rendering mode is used that redraws adjacent characters.</p> |
685 | </dd> |
|
|
686 | <dd> |
|
|
687 | <p>All of this requires that fonts do not lie about character sizes, |
560 | <p>All of this requires that fonts do not lie about character sizes, |
688 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
561 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
689 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
562 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
690 | ask for the character bounding box, which unfortunately is wrong in these |
563 | ask for the character bounding box, which unfortunately is wrong in these |
691 | cases).</p> |
564 | cases).</p> |
692 | </dd> |
|
|
693 | <dd> |
|
|
694 | <p>It's not clear (to me at least), wether this is a bug in Xft, freetype, |
565 | <p>It's not clear (to me at least), wether this is a bug in Xft, freetype, |
695 | or the respective font. If you encounter this problem you might try using |
566 | or the respective font. If you encounter this problem you might try using |
696 | the <code>-lsp</code> option to give the font more height. If that doesn't work, you |
567 | the <code>-lsp</code> option to give the font more height. If that doesn't work, you |
697 | might be forced to use a different font.</p> |
568 | might be forced to use a different font.</p> |
698 | </dd> |
|
|
699 | <dd> |
|
|
700 | <p>All of this is not a problem when using X11 core fonts, as their bounding |
569 | <p>All of this is not a problem when using X11 core fonts, as their bounding |
701 | box data is correct.</p> |
570 | box data is correct.</p> |
702 | </dd> |
571 | <p> |
703 | <p></p> |
572 | </p> |
704 | <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 /> |
573 | <h2><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h2> |
705 | </dt> |
|
|
706 | <dd> |
|
|
707 | Seems to be a known bug, read |
574 | <p>Seems to be a known bug, read |
708 | <a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the |
575 | <a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the |
709 | following ugly workaround to get non-double-wide-characters working: |
576 | following ugly workaround to get non-double-wide-characters working:</p> |
710 | </dd> |
|
|
711 | <dd> |
|
|
712 | <pre> |
577 | <pre> |
713 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)</pre> |
578 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)</pre> |
714 | </dd> |
579 | <p> |
715 | <p></p> |
580 | </p> |
716 | <dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br /> |
581 | <h2><a name="my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></h2> |
717 | </dt> |
|
|
718 | <dd> |
|
|
719 | The most common causes for this are that either your locale is not set |
582 | <p>The most common causes for this are that either your locale is not set |
720 | correctly, or you specified a <strong>preeditStyle</strong> that is not supported by |
583 | correctly, or you specified a <strong>preeditStyle</strong> that is not supported by |
721 | your input method. For example, if you specified <strong>OverTheSpot</strong> and |
584 | your input method. For example, if you specified <strong>OverTheSpot</strong> and |
722 | your input method (e.g. the default input method handling Compose keys) |
585 | your input method (e.g. the default input method handling Compose keys) |
723 | does not support this (for instance because it is not visual), then |
586 | does not support this (for instance because it is not visual), then |
724 | rxvt-unicode will continue without an input method. |
587 | rxvt-unicode will continue without an input method.</p> |
725 | </dd> |
|
|
726 | <dd> |
|
|
727 | <p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than |
588 | <p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than |
728 | one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p> |
589 | one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p> |
729 | </dd> |
590 | <p> |
730 | <p></p> |
591 | </p> |
731 | <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 /> |
592 | <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> |
732 | </dt> |
|
|
733 | <dd> |
|
|
734 | Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on |
593 | <p>Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on |
735 | international keyboards) or simply use ISO 14755 support to your |
594 | international keyboards) or simply use ISO 14755 support to your |
736 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
595 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
737 | codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape |
596 | codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape |
738 | character and so on. |
597 | character and so on.</p> |
739 | </dd> |
598 | <p> |
740 | <p></p> |
599 | </p> |
741 | <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 /> |
600 | <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> |
742 | </dt> |
|
|
743 | <dd> |
|
|
744 | First of all, make sure you are running with the right terminal settings |
601 | <p>First of all, make sure you are running with the right terminal settings |
745 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
602 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
746 | make sure you have specified colours for italic and bold, as otherwise |
603 | make sure you have specified colours for italic and bold, as otherwise |
747 | rxvt-unicode might use reverse video to simulate the effect: |
604 | rxvt-unicode might use reverse video to simulate the effect:</p> |
748 | </dd> |
|
|
749 | <dd> |
|
|
750 | <pre> |
605 | <pre> |
751 | URxvt.colorBD: white |
606 | URxvt.colorBD: white |
752 | URxvt.colorIT: green</pre> |
607 | URxvt.colorIT: green</pre> |
753 | </dd> |
608 | <p> |
754 | <p></p> |
609 | </p> |
755 | <dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br /> |
610 | <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> |
756 | </dt> |
|
|
757 | <dd> |
|
|
758 | For some unexplainable reason, some rare programs assume a very weird |
611 | <p>For some unexplainable reason, some rare programs assume a very weird |
759 | colour palette when confronted with a terminal with more than the standard |
612 | colour palette when confronted with a terminal with more than the standard |
760 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
613 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
761 | these programs not to assume non-ISO colours without very good reasons. |
614 | these programs not to assume non-ISO colours without very good reasons.</p> |
762 | </dd> |
|
|
763 | <dd> |
|
|
764 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
615 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
765 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
616 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
766 | fix colours but keep you from using other rxvt-unicode features.</p> |
617 | fix colours but keep you from using other rxvt-unicode features.</p> |
767 | </dd> |
618 | <p> |
768 | <p></p> |
619 | </p> |
769 | <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 /> |
620 | <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> |
770 | </dt> |
|
|
771 | <dd> |
|
|
772 | Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined |
621 | <p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined |
773 | in your compile environment, or an implementation that implements it, |
622 | in your compile environment, or an implementation that implements it, |
774 | wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that |
623 | wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that |
775 | <strong>wchar_t</strong> is represented as unicode. |
624 | <strong>wchar_t</strong> is represented as unicode.</p> |
776 | </dd> |
|
|
777 | <dd> |
|
|
778 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
625 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
779 | does it support it. Instead, it uses it's own internal representation of |
626 | does it support it. Instead, it uses it's own internal representation of |
780 | <strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> |
627 | <strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> |
781 | </dd> |
|
|
782 | <dd> |
|
|
783 | <p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and |
628 | <p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and |
784 | <code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> |
629 | <code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> |
785 | </dd> |
|
|
786 | <dd> |
|
|
787 | <p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language |
630 | <p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language |
788 | apps in an OS, as using a locale-dependent (and non-standardized) |
631 | apps in an OS, as using a locale-dependent (and non-standardized) |
789 | representation of <strong>wchar_t</strong> makes it impossible to convert between |
632 | representation of <strong>wchar_t</strong> makes it impossible to convert between |
790 | <strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding |
633 | <strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding |
791 | without implementing OS-specific-wrappers for each and every locale. There |
634 | without implementing OS-specific-wrappers for each and every locale. There |
792 | simply are no APIs to convert <strong>wchar_t</strong> into anything except the current |
635 | simply are no APIs to convert <strong>wchar_t</strong> into anything except the current |
793 | locale encoding.</p> |
636 | locale encoding.</p> |
794 | </dd> |
|
|
795 | <dd> |
|
|
796 | <p>Some applications (such as the formidable <strong>mlterm</strong>) work around this |
637 | <p>Some applications (such as the formidable <strong>mlterm</strong>) work around this |
797 | by carrying their own replacement functions for character set handling |
638 | by carrying their own replacement functions for character set handling |
798 | with them, and either implementing OS-dependent hacks or doing multiple |
639 | with them, and either implementing OS-dependent hacks or doing multiple |
799 | conversions (which is slow and unreliable in case the OS implements |
640 | conversions (which is slow and unreliable in case the OS implements |
800 | encodings slightly different than the terminal emulator).</p> |
641 | encodings slightly different than the terminal emulator).</p> |
801 | </dd> |
|
|
802 | <dd> |
|
|
803 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
642 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
804 | system libraries once and for all, instead of forcing every app to carry |
643 | system libraries once and for all, instead of forcing every app to carry |
805 | complete replacements for them :)</p> |
644 | complete replacements for them :)</p> |
806 | </dd> |
645 | <p> |
807 | <p></p> |
646 | </p> |
808 | <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 /> |
647 | <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> |
809 | </dt> |
|
|
810 | <dd> |
|
|
811 | Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst |
648 | <p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst |
812 | problems with <code>wcwidth</code> and a compile problem. |
649 | problems with <code>wcwidth</code> and a compile problem.</p> |
813 | </dd> |
650 | <p> |
814 | <p></p> |
651 | </p> |
815 | <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 /> |
652 | <h2><a name="how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></h2> |
816 | </dt> |
|
|
817 | <dd> |
|
|
818 | rxvt-unicode should compile and run out of the box on cygwin, using |
653 | <p>rxvt-unicode should compile and run out of the box on cygwin, using |
819 | the X11 libraries that come with cygwin. libW11 emulation is no |
654 | the X11 libraries that come with cygwin. libW11 emulation is no |
820 | longer supported (and makes no sense, either, as it only supported a |
655 | longer supported (and makes no sense, either, as it only supported a |
821 | single font). I recommend starting the X-server in <code>-multiwindow</code> or |
656 | single font). I recommend starting the X-server in <code>-multiwindow</code> or |
822 | <code>-rootless</code> mode instead, which will result in similar look&feel as the |
657 | <code>-rootless</code> mode instead, which will result in similar look&feel as the |
823 | old libW11 emulation. |
658 | old libW11 emulation.</p> |
824 | </dd> |
|
|
825 | <dd> |
|
|
826 | <p>At the time of this writing, cygwin didn't seem to support any multi-byte |
659 | <p>At the time of this writing, cygwin didn't seem to support any multi-byte |
827 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
660 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
828 | to 8-bit encodings.</p> |
661 | to 8-bit encodings.</p> |
829 | </dd> |
662 | <p> |
830 | <p></p> |
663 | </p> |
831 | <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 /> |
664 | <h2><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h2> |
832 | </dt> |
665 | <p> |
|
|
666 | </p> |
833 | <dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br /> |
667 | <h2><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h2> |
834 | </dt> |
|
|
835 | <dd> |
|
|
836 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
668 | <p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
837 | specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about |
669 | specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about |
838 | UTF-8 or any other encodings with respect to terminal I/O. |
670 | UTF-8 or any other encodings with respect to terminal I/O.</p> |
839 | </dd> |
|
|
840 | <dd> |
|
|
841 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
671 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
842 | the encoding, doing I/O and (most important) communicating this to all |
672 | the encoding, doing I/O and (most important) communicating this to all |
843 | applications so everybody agrees on character properties such as width |
673 | applications so everybody agrees on character properties such as width |
844 | and code number. This mechanism is the <em>locale</em>. Applications not using |
674 | and code number. This mechanism is the <em>locale</em>. Applications not using |
845 | that info will have problems (for example, <code>xterm</code> gets the width of |
675 | that info will have problems (for example, <code>xterm</code> gets the width of |
846 | characters wrong as it uses it's own, locale-independent table under all |
676 | characters wrong as it uses it's own, locale-independent table under all |
847 | locales).</p> |
677 | locales).</p> |
848 | </dd> |
|
|
849 | <dd> |
|
|
850 | <p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All |
678 | <p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All |
851 | programs doing the same (that is, most) will automatically agree in the |
679 | programs doing the same (that is, most) will automatically agree in the |
852 | interpretation of characters.</p> |
680 | interpretation of characters.</p> |
853 | </dd> |
|
|
854 | <dd> |
|
|
855 | <p>Unfortunately, there is no system-independent way to select locales, nor |
681 | <p>Unfortunately, there is no system-independent way to select locales, nor |
856 | is there a standard on how locale specifiers will look like.</p> |
682 | is there a standard on how locale specifiers will look like.</p> |
857 | </dd> |
|
|
858 | <dd> |
|
|
859 | <p>On most systems, the content of the <code>LC_CTYPE</code> environment variable |
683 | <p>On most systems, the content of the <code>LC_CTYPE</code> environment variable |
860 | contains an arbitrary string which corresponds to an already-installed |
684 | contains an arbitrary string which corresponds to an already-installed |
861 | locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>, |
685 | locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>, |
862 | <code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms |
686 | <code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms |
863 | (i.e. <code>de</code> or <code>german</code>) are also common.</p> |
687 | (i.e. <code>de</code> or <code>german</code>) are also common.</p> |
864 | </dd> |
|
|
865 | <dd> |
|
|
866 | <p>Rxvt-unicode ignores all other locale categories, and except for |
688 | <p>Rxvt-unicode ignores all other locale categories, and except for |
867 | the encoding, ignores country or language-specific settings, |
689 | the encoding, ignores country or language-specific settings, |
868 | i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to |
690 | i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to |
869 | rxvt-unicode.</p> |
691 | rxvt-unicode.</p> |
870 | </dd> |
|
|
871 | <dd> |
|
|
872 | <p>If you want to use a specific encoding you have to make sure you start |
692 | <p>If you want to use a specific encoding you have to make sure you start |
873 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
693 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
874 | </dd> |
694 | <p> |
875 | <p></p> |
695 | </p> |
876 | <dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br /> |
696 | <h2><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h2> |
877 | </dt> |
|
|
878 | <dd> |
|
|
879 | Yes, using an escape sequence. Try something like this, which sets |
697 | <p>Yes, using an escape sequence. Try something like this, which sets |
880 | rxvt-unicode's idea of <code>LC_CTYPE</code>. |
698 | rxvt-unicode's idea of <code>LC_CTYPE</code>.</p> |
881 | </dd> |
|
|
882 | <dd> |
|
|
883 | <pre> |
699 | <pre> |
884 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
700 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
885 | </dd> |
|
|
886 | <dd> |
|
|
887 | <p>See also the previous answer.</p> |
701 | <p>See also the previous answer.</p> |
888 | </dd> |
|
|
889 | <dd> |
|
|
890 | <p>Sometimes this capability is rather handy when you want to work in |
702 | <p>Sometimes this capability is rather handy when you want to work in |
891 | one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it |
703 | one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it |
892 | (e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which |
704 | (e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which |
893 | first switches to a locale supported by xjdic and back later:</p> |
705 | first switches to a locale supported by xjdic and back later:</p> |
894 | </dd> |
|
|
895 | <dd> |
|
|
896 | <pre> |
706 | <pre> |
897 | printf '\e]701;%s\007' ja_JP.SJIS |
707 | printf '\e]701;%s\007' ja_JP.SJIS |
898 | xjdic -js |
708 | xjdic -js |
899 | printf '\e]701;%s\007' de_DE.UTF-8</pre> |
709 | printf '\e]701;%s\007' de_DE.UTF-8</pre> |
900 | </dd> |
|
|
901 | <dd> |
|
|
902 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
710 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
903 | for some locales where character width differs between program- and |
711 | for some locales where character width differs between program- and |
904 | rxvt-unicode-locales.</p> |
712 | rxvt-unicode-locales.</p> |
905 | </dd> |
713 | <p> |
906 | <p></p> |
714 | </p> |
907 | <dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br /> |
715 | <h2><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h2> |
908 | </dt> |
|
|
909 | <dd> |
|
|
910 | Yes, using an escape sequence. Try something like this, which has the same |
716 | <p>Yes, using an escape sequence. Try something like this, which has the same |
911 | effect as using the <code>-fn</code> switch, and takes effect immediately: |
717 | effect as using the <code>-fn</code> switch, and takes effect immediately:</p> |
912 | </dd> |
|
|
913 | <dd> |
|
|
914 | <pre> |
718 | <pre> |
915 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
719 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
916 | </dd> |
|
|
917 | <dd> |
|
|
918 | <p>This is useful if you e.g. work primarily with japanese (and prefer a |
720 | <p>This is useful if you e.g. work primarily with japanese (and prefer a |
919 | japanese font), but you have to switch to chinese temporarily, where |
721 | japanese font), but you have to switch to chinese temporarily, where |
920 | japanese fonts would only be in your way.</p> |
722 | japanese fonts would only be in your way.</p> |
921 | </dd> |
|
|
922 | <dd> |
|
|
923 | <p>You can think of this as a kind of manual ISO-2022 switching.</p> |
723 | <p>You can think of this as a kind of manual ISO-2022 switching.</p> |
924 | </dd> |
724 | <p> |
925 | <p></p> |
725 | </p> |
926 | <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 /> |
726 | <h2><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h2> |
927 | </dt> |
|
|
928 | <dd> |
|
|
929 | Many fonts have difficulties with italic characters and hinting. For |
727 | <p>Many fonts have difficulties with italic characters and hinting. For |
930 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
728 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
931 | Mono</code> completely fails in it's italic face. A workaround might be to |
729 | Mono</code> completely fails in it's italic face. A workaround might be to |
932 | enable freetype autohinting, i.e. like this: |
730 | enable freetype autohinting, i.e. like this:</p> |
933 | </dd> |
|
|
934 | <dd> |
|
|
935 | <pre> |
731 | <pre> |
936 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
732 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
937 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
733 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
938 | </dd> |
734 | <p> |
939 | <p></p> |
735 | </p> |
940 | <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 /> |
736 | <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> |
941 | </dt> |
|
|
942 | <dd> |
|
|
943 | You can specify separate locales for the input method and the rest of the |
737 | <p>You can specify separate locales for the input method and the rest of the |
944 | terminal, using the resource <code>imlocale</code>: |
738 | terminal, using the resource <code>imlocale</code>:</p> |
945 | </dd> |
|
|
946 | <dd> |
|
|
947 | <pre> |
739 | <pre> |
948 | URxvt.imlocale: ja_JP.EUC-JP</pre> |
740 | URxvt.imlocale: ja_JP.EUC-JP</pre> |
949 | </dd> |
|
|
950 | <dd> |
|
|
951 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
741 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
952 | use your input method. Please note, however, that you will not be able to |
742 | use your input method. Please note, however, that you will not be able to |
953 | input characters outside <code>EUC-JP</code> in a normal way then, as your input |
743 | input characters outside <code>EUC-JP</code> in a normal way then, as your input |
954 | method limits you.</p> |
744 | method limits you.</p> |
955 | </dd> |
745 | <p> |
956 | <p></p> |
746 | </p> |
957 | <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 /> |
747 | <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> |
958 | </dt> |
|
|
959 | <dd> |
|
|
960 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
748 | <p>Unfortunately, this is unavoidable, as the XIM protocol is racy by |
961 | design. Applications can avoid some crashes at the expense of memory |
749 | design. Applications can avoid some crashes at the expense of memory |
962 | leaks, and Input Methods can avoid some crashes by careful ordering at |
750 | leaks, and Input Methods can avoid some crashes by careful ordering at |
963 | exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds, |
751 | exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds, |
964 | while <strong>SCIM</strong> (or similar input methods) fails. In the end, however, |
752 | while <strong>SCIM</strong> (or similar input methods) fails. In the end, however, |
965 | crashes cannot be completely avoided even if both sides cooperate. |
753 | crashes cannot be completely avoided even if both sides cooperate.</p> |
966 | </dd> |
|
|
967 | <dd> |
|
|
968 | <p>So the only workaround is not to kill your Input Method Servers.</p> |
754 | <p>So the only workaround is not to kill your Input Method Servers.</p> |
969 | </dd> |
755 | <p> |
970 | <p></p> |
756 | </p> |
971 | <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 /> |
757 | <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> |
972 | </dt> |
|
|
973 | <dd> |
|
|
974 | Rxvt-unicode tries to obey the rule of not charging you for something you |
758 | <p>Rxvt-unicode tries to obey the rule of not charging you for something you |
975 | don't use. One thing you should try is to configure out all settings that |
759 | don't use. One thing you should try is to configure out all settings that |
976 | you don't need, for example, Xft support is a resource hog by design, |
760 | you don't need, for example, Xft support is a resource hog by design, |
977 | when used. Compiling it out ensures that no Xft font will be loaded |
761 | when used. Compiling it out ensures that no Xft font will be loaded |
978 | accidentally when rxvt-unicode tries to find a font for your characters. |
762 | accidentally when rxvt-unicode tries to find a font for your characters.</p> |
979 | </dd> |
|
|
980 | <dd> |
|
|
981 | <p>Also, many people (me included) like large windows and even larger |
763 | <p>Also, many people (me included) like large windows and even larger |
982 | scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use |
764 | scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use |
983 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
765 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
984 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
766 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
985 | use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as |
767 | use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as |
986 | rxvt-unicode then uses 8 bytes per screen cell.</p> |
768 | rxvt-unicode then uses 8 bytes per screen cell.</p> |
987 | </dd> |
769 | <p> |
988 | <p></p> |
770 | </p> |
989 | <dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br /> |
771 | <h2><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h2> |
990 | </dt> |
|
|
991 | <dd> |
|
|
992 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
772 | <p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
993 | it is simply slow. If you still want Xft fonts you might try to disable |
773 | it is simply slow. If you still want Xft fonts you might try to disable |
994 | antialiasing (by appending <code>:antialias=false</code>), which saves lots of |
774 | antialiasing (by appending <code>:antialias=false</code>), which saves lots of |
995 | memory and also speeds up rendering considerably. |
775 | memory and also speeds up rendering considerably.</p> |
996 | </dd> |
776 | <p> |
997 | <p></p> |
777 | </p> |
998 | <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 /> |
778 | <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> |
999 | </dt> |
|
|
1000 | <dd> |
|
|
1001 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
779 | <p>Rxvt-unicode will use whatever you specify as a font. If it needs to |
1002 | fall back to it's default font search list it will prefer X11 core |
780 | fall back to it's default font search list it will prefer X11 core |
1003 | fonts, because they are small and fast, and then use Xft fonts. It has |
781 | fonts, because they are small and fast, and then use Xft fonts. It has |
1004 | antialiasing disabled for most of them, because the author thinks they |
782 | antialiasing disabled for most of them, because the author thinks they |
1005 | look best that way. |
783 | look best that way.</p> |
1006 | </dd> |
|
|
1007 | <dd> |
|
|
1008 | <p>If you want antialiasing, you have to specify the fonts manually.</p> |
784 | <p>If you want antialiasing, you have to specify the fonts manually.</p> |
1009 | </dd> |
785 | <p> |
1010 | <p></p> |
786 | </p> |
1011 | <dt><strong><a name="item_mouse_cut_2fpaste_suddenly_no_longer_works_2e">Mouse cut/paste suddenly no longer works.</a></strong><br /> |
787 | <h2><a name="mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></h2> |
1012 | </dt> |
|
|
1013 | <dd> |
|
|
1014 | Make sure that mouse reporting is actually turned off since killing |
788 | <p>Make sure that mouse reporting is actually turned off since killing |
1015 | some editors prematurely may leave the mouse in mouse report mode. I've |
789 | some editors prematurely may leave the mouse in mouse report mode. I've |
1016 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
790 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
1017 | quick check is to see if cut/paste works when the Alt or Shift keys are |
791 | quick check is to see if cut/paste works when the Alt or Shift keys are |
1018 | depressed. |
792 | depressed.</p> |
1019 | </dd> |
793 | <p> |
1020 | <p></p> |
794 | </p> |
1021 | <dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br /> |
795 | <h2><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h2> |
1022 | </dt> |
|
|
1023 | <dd> |
|
|
1024 | If no bold colour is set via <code>colorBD:</code>, bold will invert text using the |
796 | <p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the |
1025 | standard foreground colour. |
797 | standard foreground colour.</p> |
1026 | </dd> |
|
|
1027 | <dd> |
|
|
1028 | <p>For the standard background colour, blinking will actually make the |
798 | <p>For the standard background colour, blinking will actually make the |
1029 | text blink when compiled with <code>--enable-blinking</code>. with standard |
799 | text blink when compiled with <code>--enable-blinking</code>. with standard |
1030 | colours. Without <code>--enable-blinking</code>, the blink attribute will be |
800 | colours. Without <code>--enable-blinking</code>, the blink attribute will be |
1031 | ignored.</p> |
801 | ignored.</p> |
1032 | </dd> |
|
|
1033 | <dd> |
|
|
1034 | <p>On ANSI colours, bold/blink attributes are used to set high-intensity |
802 | <p>On ANSI colours, bold/blink attributes are used to set high-intensity |
1035 | foreground/background colors.</p> |
803 | foreground/background colors.</p> |
1036 | </dd> |
|
|
1037 | <dd> |
|
|
1038 | <p>color0-7 are the low-intensity colors.</p> |
804 | <p>color0-7 are the low-intensity colors.</p> |
1039 | </dd> |
|
|
1040 | <dd> |
|
|
1041 | <p>color8-15 are the corresponding high-intensity colors.</p> |
805 | <p>color8-15 are the corresponding high-intensity colors.</p> |
1042 | </dd> |
806 | <p> |
1043 | <p></p> |
807 | </p> |
1044 | <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 /> |
808 | <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> |
1045 | </dt> |
|
|
1046 | <dd> |
|
|
1047 | You can change the screen colors at run-time using <em>~/.Xdefaults</em> |
809 | <p>You can change the screen colors at run-time using <em>~/.Xdefaults</em> |
1048 | resources (or as long-options). |
810 | resources (or as long-options).</p> |
1049 | </dd> |
|
|
1050 | <dd> |
|
|
1051 | <p>Here are values that are supposed to resemble a VGA screen, |
811 | <p>Here are values that are supposed to resemble a VGA screen, |
1052 | including the murky brown that passes for low-intensity yellow:</p> |
812 | including the murky brown that passes for low-intensity yellow:</p> |
1053 | </dd> |
|
|
1054 | <dd> |
|
|
1055 | <pre> |
813 | <pre> |
1056 | URxvt.color0: #000000 |
814 | URxvt.color0: #000000 |
1057 | URxvt.color1: #A80000 |
815 | URxvt.color1: #A80000 |
1058 | URxvt.color2: #00A800 |
816 | URxvt.color2: #00A800 |
1059 | URxvt.color3: #A8A800 |
817 | URxvt.color3: #A8A800 |
1060 | URxvt.color4: #0000A8 |
818 | URxvt.color4: #0000A8 |
1061 | URxvt.color5: #A800A8 |
819 | URxvt.color5: #A800A8 |
1062 | URxvt.color6: #00A8A8 |
820 | URxvt.color6: #00A8A8 |
1063 | URxvt.color7: #A8A8A8</pre> |
821 | URxvt.color7: #A8A8A8</pre> |
1064 | </dd> |
|
|
1065 | <dd> |
|
|
1066 | <pre> |
822 | <pre> |
1067 | URxvt.color8: #000054 |
823 | URxvt.color8: #000054 |
1068 | URxvt.color9: #FF0054 |
824 | URxvt.color9: #FF0054 |
1069 | URxvt.color10: #00FF54 |
825 | URxvt.color10: #00FF54 |
1070 | URxvt.color11: #FFFF54 |
826 | URxvt.color11: #FFFF54 |
1071 | URxvt.color12: #0000FF |
827 | URxvt.color12: #0000FF |
1072 | URxvt.color13: #FF00FF |
828 | URxvt.color13: #FF00FF |
1073 | URxvt.color14: #00FFFF |
829 | URxvt.color14: #00FFFF |
1074 | URxvt.color15: #FFFFFF</pre> |
830 | URxvt.color15: #FFFFFF</pre> |
1075 | </dd> |
|
|
1076 | <dd> |
|
|
1077 | <p>And here is a more complete set of non-standard colors described (not by |
831 | <p>And here is a more complete set of non-standard colors described (not by |
1078 | me) as ``pretty girly''.</p> |
832 | me) as ``pretty girly''.</p> |
1079 | </dd> |
|
|
1080 | <dd> |
|
|
1081 | <pre> |
833 | <pre> |
1082 | URxvt.cursorColor: #dc74d1 |
834 | URxvt.cursorColor: #dc74d1 |
1083 | URxvt.pointerColor: #dc74d1 |
835 | URxvt.pointerColor: #dc74d1 |
1084 | URxvt.background: #0e0e0e |
836 | URxvt.background: #0e0e0e |
1085 | URxvt.foreground: #4ad5e1 |
837 | URxvt.foreground: #4ad5e1 |
… | |
… | |
1095 | URxvt.color13: #9e88f0 |
847 | URxvt.color13: #9e88f0 |
1096 | URxvt.color6: #73f7ff |
848 | URxvt.color6: #73f7ff |
1097 | URxvt.color14: #73f7ff |
849 | URxvt.color14: #73f7ff |
1098 | URxvt.color7: #e1dddd |
850 | URxvt.color7: #e1dddd |
1099 | URxvt.color15: #e1dddd</pre> |
851 | URxvt.color15: #e1dddd</pre> |
1100 | </dd> |
852 | <p> |
1101 | <p></p> |
853 | </p> |
1102 | <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 /> |
854 | <h2><a name="how_can_i_start_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</a></h2> |
1103 | </dt> |
|
|
1104 | <dd> |
|
|
1105 | Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
855 | <p>Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
1106 | display, create the listening socket and then fork. |
856 | display, create the listening socket and then fork.</p> |
1107 | </dd> |
857 | <p> |
1108 | <p></p> |
858 | </p> |
1109 | <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 /> |
859 | <h2><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h2> |
1110 | </dt> |
|
|
1111 | <dd> |
|
|
1112 | Assuming that the physical Backspace key corresponds to the |
860 | <p>Assuming that the physical Backspace key corresponds to the |
1113 | BackSpace keysym (not likely for Linux ... see the following |
861 | BackSpace keysym (not likely for Linux ... see the following |
1114 | question) there are two standard values that can be used for |
862 | question) there are two standard values that can be used for |
1115 | Backspace: <code>^H</code> and <code>^?</code>. |
863 | Backspace: <code>^H</code> and <code>^?</code>.</p> |
1116 | </dd> |
|
|
1117 | <dd> |
|
|
1118 | <p>Historically, either value is correct, but rxvt-unicode adopts the debian |
864 | <p>Historically, either value is correct, but rxvt-unicode adopts the debian |
1119 | policy of using <code>^?</code> when unsure, because it's the one only only correct |
865 | policy of using <code>^?</code> when unsure, because it's the one only only correct |
1120 | choice :).</p> |
866 | choice :).</p> |
1121 | </dd> |
|
|
1122 | <dd> |
|
|
1123 | <p>Rxvt-unicode tries to inherit the current stty settings and uses the value |
867 | <p>Rxvt-unicode tries to inherit the current stty settings and uses the value |
1124 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
868 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
1125 | started from a terminal (say, from a menu or by remote shell), then the |
869 | started from a terminal (say, from a menu or by remote shell), then the |
1126 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
870 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
1127 | be used (which may not be the same as your stty setting).</p> |
871 | be used (which may not be the same as your stty setting).</p> |
1128 | </dd> |
|
|
1129 | <dd> |
|
|
1130 | <p>For starting a new rxvt-unicode:</p> |
872 | <p>For starting a new rxvt-unicode:</p> |
1131 | </dd> |
|
|
1132 | <dd> |
|
|
1133 | <pre> |
873 | <pre> |
1134 | # use Backspace = ^H |
874 | # use Backspace = ^H |
1135 | $ stty erase ^H |
875 | $ stty erase ^H |
1136 | $ rxvt</pre> |
876 | $ rxvt</pre> |
1137 | </dd> |
|
|
1138 | <dd> |
|
|
1139 | <pre> |
877 | <pre> |
1140 | # use Backspace = ^? |
878 | # use Backspace = ^? |
1141 | $ stty erase ^? |
879 | $ stty erase ^? |
1142 | $ rxvt</pre> |
880 | $ rxvt</pre> |
1143 | </dd> |
|
|
1144 | <dd> |
|
|
1145 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p> |
881 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p> |
1146 | </dd> |
|
|
1147 | <dd> |
|
|
1148 | <p>For an existing rxvt-unicode:</p> |
882 | <p>For an existing rxvt-unicode:</p> |
1149 | </dd> |
|
|
1150 | <dd> |
|
|
1151 | <pre> |
883 | <pre> |
1152 | # use Backspace = ^H |
884 | # use Backspace = ^H |
1153 | $ stty erase ^H |
885 | $ stty erase ^H |
1154 | $ echo -n "^[[36h"</pre> |
886 | $ echo -n "^[[36h"</pre> |
1155 | </dd> |
|
|
1156 | <dd> |
|
|
1157 | <pre> |
887 | <pre> |
1158 | # use Backspace = ^? |
888 | # use Backspace = ^? |
1159 | $ stty erase ^? |
889 | $ stty erase ^? |
1160 | $ echo -n "^[[36l"</pre> |
890 | $ echo -n "^[[36l"</pre> |
1161 | </dd> |
|
|
1162 | <dd> |
|
|
1163 | <p>This helps satisfy some of the Backspace discrepancies that occur, but |
891 | <p>This helps satisfy some of the Backspace discrepancies that occur, but |
1164 | if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value |
892 | if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value |
1165 | properly reflects that.</p> |
893 | properly reflects that.</p> |
1166 | </dd> |
|
|
1167 | <dd> |
|
|
1168 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
894 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
1169 | To avoid confusion between the Backspace and Delete keys, the Delete |
895 | To avoid confusion between the Backspace and Delete keys, the Delete |
1170 | key has been assigned an escape sequence to match the vt100 for Execute |
896 | key has been assigned an escape sequence to match the vt100 for Execute |
1171 | (<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> |
897 | (<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> |
1172 | </dd> |
|
|
1173 | <dd> |
|
|
1174 | <p>Some other Backspace problems:</p> |
898 | <p>Some other Backspace problems:</p> |
1175 | </dd> |
|
|
1176 | <dd> |
|
|
1177 | <p>some editors use termcap/terminfo, |
899 | <p>some editors use termcap/terminfo, |
1178 | some editors (vim I'm told) expect Backspace = ^H, |
900 | some editors (vim I'm told) expect Backspace = ^H, |
1179 | GNU Emacs (and Emacs-like editors) use ^H for help.</p> |
901 | GNU Emacs (and Emacs-like editors) use ^H for help.</p> |
1180 | </dd> |
|
|
1181 | <dd> |
|
|
1182 | <p>Perhaps someday this will all be resolved in a consistent manner.</p> |
902 | <p>Perhaps someday this will all be resolved in a consistent manner.</p> |
1183 | </dd> |
903 | <p> |
1184 | <p></p> |
904 | </p> |
1185 | <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 /> |
905 | <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> |
1186 | </dt> |
|
|
1187 | <dd> |
|
|
1188 | There are some compile-time selections available via configure. Unless |
906 | <p>There are some compile-time selections available via configure. Unless |
1189 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
907 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
1190 | use the `keysym' resource to alter the keystrings associated with keysyms. |
908 | use the `keysym' resource to alter the keystrings associated with keysyms.</p> |
1191 | </dd> |
|
|
1192 | <dd> |
|
|
1193 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
909 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
1194 | </dd> |
|
|
1195 | <dd> |
|
|
1196 | <pre> |
910 | <pre> |
1197 | URxvt.keysym.Home: \033[1~ |
911 | URxvt.keysym.Home: \033[1~ |
1198 | URxvt.keysym.End: \033[4~ |
912 | URxvt.keysym.End: \033[4~ |
1199 | URxvt.keysym.C-apostrophe: \033<C-'> |
913 | URxvt.keysym.C-apostrophe: \033<C-'> |
1200 | URxvt.keysym.C-slash: \033<C-/> |
914 | URxvt.keysym.C-slash: \033<C-/> |
… | |
… | |
1212 | URxvt.keysym.M-Left: \033<M-Left> |
926 | URxvt.keysym.M-Left: \033<M-Left> |
1213 | URxvt.keysym.M-Right: \033<M-Right> |
927 | URxvt.keysym.M-Right: \033<M-Right> |
1214 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
928 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
1215 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
929 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
1216 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> |
930 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> |
1217 | </dd> |
|
|
1218 | <dd> |
|
|
1219 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
931 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
1220 | </dd> |
932 | <p> |
1221 | <p></p> |
933 | </p> |
1222 | <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. |
934 | <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. |
1223 | How do I make use of them? For example, the Sun Keyboard type 4 |
935 | How do I make use of them? For example, the Sun Keyboard type 4 |
1224 | has the following mappings that rxvt-unicode doesn't recognize.</a></strong><br /> |
936 | has the following mappings that rxvt-unicode doesn't recognize.</a></h2> |
1225 | </dt> |
|
|
1226 | <dd> |
|
|
1227 | <pre> |
937 | <pre> |
1228 | KP_Insert == Insert |
938 | KP_Insert == Insert |
1229 | F22 == Print |
939 | F22 == Print |
1230 | F27 == Home |
940 | F27 == Home |
1231 | F29 == Prior |
941 | F29 == Prior |
1232 | F33 == End |
942 | F33 == End |
1233 | F35 == Next</pre> |
943 | F35 == Next</pre> |
1234 | </dd> |
|
|
1235 | <dd> |
|
|
1236 | <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 |
1237 | 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 |
1238 | required for your particular machine.</p> |
946 | required for your particular machine.</p> |
1239 | </dd> |
947 | <p> |
1240 | <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> |
|
|
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? |
1241 | I need this to decide about setting colors etc.</a></strong><br /> |
950 | I need this to decide about setting colors etc.</a></h2> |
1242 | </dt> |
|
|
1243 | <dd> |
|
|
1244 | rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
951 | <p>rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
1245 | check and see if that is set. Note that several programs, JED, slrn, |
952 | check and see if that is set. Note that several programs, JED, slrn, |
1246 | Midnight Commander automatically check this variable to decide whether or |
953 | Midnight Commander automatically check this variable to decide whether or |
1247 | not to use color. |
954 | not to use color.</p> |
1248 | </dd> |
955 | <p> |
1249 | <p></p> |
956 | </p> |
1250 | <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 /> |
957 | <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> |
1251 | </dt> |
|
|
1252 | <dd> |
|
|
1253 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
958 | <p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
1254 | insecure mode then it is possible to use the following shell script |
959 | insecure mode then it is possible to use the following shell script |
1255 | snippets to correctly set the display. If your version of rxvt-unicode |
960 | snippets to correctly set the display. If your version of rxvt-unicode |
1256 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
961 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
1257 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
962 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
1258 | regular xterm. |
963 | regular xterm.</p> |
1259 | </dd> |
|
|
1260 | <dd> |
|
|
1261 | <p>Courtesy of Chuck Blake <<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>> with the following shell script |
964 | <p>Courtesy of Chuck Blake <<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>> with the following shell script |
1262 | snippets:</p> |
965 | snippets:</p> |
1263 | </dd> |
|
|
1264 | <dd> |
|
|
1265 | <pre> |
966 | <pre> |
1266 | # Bourne/Korn/POSIX family of shells: |
967 | # Bourne/Korn/POSIX family of shells: |
1267 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
968 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
1268 | if [ ${TERM:-foo} = xterm ]; then |
969 | if [ ${TERM:-foo} = xterm ]; then |
1269 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
970 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
… | |
… | |
1273 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
974 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
1274 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
975 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
1275 | read DISPLAY # set it in our local shell |
976 | read DISPLAY # set it in our local shell |
1276 | fi |
977 | fi |
1277 | fi</pre> |
978 | fi</pre> |
1278 | </dd> |
979 | <p> |
1279 | <p></p> |
980 | </p> |
1280 | <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 /> |
981 | <h2><a name="how_do_i_compile_the_manual_pages_for_myself">How do I compile the manual pages for myself?</a></h2> |
1281 | </dt> |
|
|
1282 | <dd> |
|
|
1283 | You need to have a recent version of perl installed as <em>/usr/bin/perl</em>, |
982 | <p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>, |
1284 | one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to |
983 | one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to |
1285 | the doc subdirectory and enter <code>make alldoc</code>. |
984 | the doc subdirectory and enter <code>make alldoc</code>.</p> |
1286 | </dd> |
985 | <p> |
1287 | <p></p> |
986 | </p> |
1288 | <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 /> |
987 | <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> |
1289 | </dt> |
|
|
1290 | <dd> |
|
|
1291 | Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>, |
988 | <p>Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>, |
1292 | channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be |
989 | channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be |
1293 | interested in learning about new and exciting problems (but not FAQs :). |
990 | interested in learning about new and exciting problems (but not FAQs :).</p> |
1294 | </dd> |
|
|
1295 | <p></p></dl> |
|
|
1296 | <p> |
991 | <p> |
1297 | </p> |
992 | </p> |
1298 | <hr /> |
993 | <hr /> |
1299 | <h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> |
994 | <h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> |
1300 | <p> |
995 | <p> |