… | |
… | |
13 | <ul> |
13 | <ul> |
14 | |
14 | |
15 | <li><a href="#name">NAME</a></li> |
15 | <li><a href="#name">NAME</a></li> |
16 | <li><a href="#synopsis">SYNOPSIS</a></li> |
16 | <li><a href="#synopsis">SYNOPSIS</a></li> |
17 | <li><a href="#description">DESCRIPTION</a></li> |
17 | <li><a href="#description">DESCRIPTION</a></li> |
18 | <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li> |
18 | <li><a href="#rxvtunicode_urxvt_frequently_asked_questions">RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS</a></li> |
19 | <ul> |
19 | <ul> |
20 | |
20 | |
21 | <li><a href="#meta__features___commandline_issues">Meta, Features & Commandline Issues</a></li> |
21 | <li><a href="#meta__features___commandline_issues">Meta, Features & Commandline Issues</a></li> |
22 | <ul> |
22 | <ul> |
23 | |
23 | |
24 | <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> |
24 | <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> |
25 | <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> |
25 | <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> |
26 | <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> |
26 | <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> |
27 | <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> |
27 | <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> |
28 | <li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li> |
28 | <li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li> |
|
|
29 | <li><a href="#how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></li> |
29 | <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li> |
30 | <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li> |
30 | <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> |
31 | <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> |
31 | <li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li> |
32 | <li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li> |
32 | <li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li> |
33 | <li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li> |
33 | <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li> |
34 | <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li> |
… | |
… | |
35 | |
36 | |
36 | <li><a href="#rendering__font___look_and_feel_issues">Rendering, Font & Look and Feel Issues</a></li> |
37 | <li><a href="#rendering__font___look_and_feel_issues">Rendering, Font & Look and Feel Issues</a></li> |
37 | <ul> |
38 | <ul> |
38 | |
39 | |
39 | <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> |
40 | <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> |
40 | <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> |
|
|
41 | <li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li> |
41 | <li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li> |
42 | <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> |
42 | <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> |
43 | <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> |
43 | <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> |
44 | <li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li> |
44 | <li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li> |
45 | <li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li> |
45 | <li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li> |
46 | <li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li> |
46 | <li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li> |
47 | <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> |
47 | <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> |
48 | <li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li> |
48 | <li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li> |
49 | <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> |
49 | <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> |
50 | <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> |
50 | <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> |
|
|
51 | <li><a href="#how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></li> |
|
|
52 | <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> |
51 | </ul> |
53 | </ul> |
52 | |
54 | |
53 | <li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse & User Interaction</a></li> |
55 | <li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse & User Interaction</a></li> |
54 | <ul> |
56 | <ul> |
55 | |
57 | |
… | |
… | |
67 | </ul> |
69 | </ul> |
68 | |
70 | |
69 | <li><a href="#terminal_configuration">Terminal Configuration</a></li> |
71 | <li><a href="#terminal_configuration">Terminal Configuration</a></li> |
70 | <ul> |
72 | <ul> |
71 | |
73 | |
|
|
74 | <li><a href="#can_i_see_a_typical_configuration">Can I see a typical configuration?</a></li> |
72 | <li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li> |
75 | <li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li> |
73 | <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> |
76 | <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> |
74 | <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> |
77 | <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> |
75 | <li><a href="#bash_s_readline_does_not_work_correctly_under_urxvt_"><code>bash</code>'s readline does not work correctly under urxvt.</a></li> |
78 | <li><a href="#bash_s_readline_does_not_work_correctly_under_urxvt_"><code>bash</code>'s readline does not work correctly under urxvt.</a></li> |
76 | <li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li> |
79 | <li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li> |
… | |
… | |
86 | <li><a href="#rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></li> |
89 | <li><a href="#rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></li> |
87 | <li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</a></li> |
90 | <li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</a></li> |
88 | <li><a href="#how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></li> |
91 | <li><a href="#how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></li> |
89 | <li><a href="#is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></li> |
92 | <li><a href="#is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></li> |
90 | <li><a href="#can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></li> |
93 | <li><a href="#can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></li> |
|
|
94 | <li><a href="#i_have_problems_getting_my_input_method_working_">I have problems getting my input method working.</a></li> |
91 | <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> |
95 | <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> |
92 | <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> |
96 | <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> |
93 | </ul> |
97 | </ul> |
94 | |
98 | |
95 | <li><a href="#operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></li> |
99 | <li><a href="#operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></li> |
… | |
… | |
104 | <li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li> |
108 | <li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li> |
105 | </ul> |
109 | </ul> |
106 | |
110 | |
107 | </ul> |
111 | </ul> |
108 | |
112 | |
109 | <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> |
113 | <li><a href="#rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></li> |
110 | <li><a href="#description">DESCRIPTION</a></li> |
114 | <ul> |
|
|
115 | |
111 | <li><a href="#definitions">Definitions</a></li> |
116 | <li><a href="#definitions">Definitions</a></li> |
112 | <li><a href="#values">Values</a></li> |
117 | <li><a href="#values">Values</a></li> |
113 | <li><a href="#escape_sequences">Escape Sequences</a></li> |
118 | <li><a href="#escape_sequences">Escape Sequences</a></li> |
114 | <li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li> |
119 | <li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li> |
115 | <li><a href="#dec_private_modes">DEC Private Modes</a></li> |
120 | <li><a href="#dec_private_modes">DEC Private Modes</a></li> |
116 | <li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li> |
121 | <li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li> |
|
|
122 | </ul> |
|
|
123 | |
117 | <li><a href="#xpm">XPM</a></li> |
124 | <li><a href="#xpm">XPM</a></li> |
118 | <li><a href="#mouse_reporting">Mouse Reporting</a></li> |
125 | <li><a href="#mouse_reporting">Mouse Reporting</a></li> |
119 | <li><a href="#key_codes">Key Codes</a></li> |
126 | <li><a href="#key_codes">Key Codes</a></li> |
120 | <li><a href="#configure_options">CONFIGURE OPTIONS</a></li> |
127 | <li><a href="#configure_options">CONFIGURE OPTIONS</a></li> |
121 | <li><a href="#authors">AUTHORS</a></li> |
128 | <li><a href="#authors">AUTHORS</a></li> |
… | |
… | |
149 | <p>The newest version of this document is also available on the World Wide Web at |
156 | <p>The newest version of this document is also available on the World Wide Web at |
150 | <a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p> |
157 | <a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p> |
151 | <p> |
158 | <p> |
152 | </p> |
159 | </p> |
153 | <hr /> |
160 | <hr /> |
154 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
161 | <h1><a name="rxvtunicode_urxvt_frequently_asked_questions">RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS</a></h1> |
155 | <p> |
162 | <p> |
156 | </p> |
163 | </p> |
157 | <h2><a name="meta__features___commandline_issues">Meta, Features & Commandline Issues</a></h2> |
164 | <h2><a name="meta__features___commandline_issues">Meta, Features & Commandline Issues</a></h2> |
158 | <p> |
165 | <p> |
159 | </p> |
166 | </p> |
… | |
… | |
202 | <h3><a name="how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></h3> |
209 | <h3><a name="how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></h3> |
203 | <p>Try <code>urxvtd -f -o</code>, which tells urxvtd to open the |
210 | <p>Try <code>urxvtd -f -o</code>, which tells urxvtd to open the |
204 | display, create the listening socket and then fork.</p> |
211 | display, create the listening socket and then fork.</p> |
205 | <p> |
212 | <p> |
206 | </p> |
213 | </p> |
|
|
214 | <h3><a name="how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></h3> |
|
|
215 | <p>If you want to start urxvtd automatically whenever you run |
|
|
216 | urxvtc and the daemon isn't running yet, use this script:</p> |
|
|
217 | <pre> |
|
|
218 | #!/bin/sh |
|
|
219 | urxvtc "$@" |
|
|
220 | if [ $? -eq 2 ]; then |
|
|
221 | urxvtd -q -o -f |
|
|
222 | urxvtc "$@" |
|
|
223 | fi</pre> |
|
|
224 | <p>This tries to create a new terminal, and if fails with exit status 2, |
|
|
225 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
226 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
227 | existing daemon.</p> |
|
|
228 | <p> |
|
|
229 | </p> |
207 | <h3><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3> |
230 | <h3><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3> |
208 | <p>rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
231 | <p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'', |
209 | check and see if that is set. Note that several programs, JED, slrn, |
232 | so you can check and see if that is set. Note that several programs, JED, |
210 | Midnight Commander automatically check this variable to decide whether or |
233 | slrn, Midnight Commander automatically check this variable to decide |
211 | not to use color.</p> |
234 | whether or not to use color.</p> |
212 | <p> |
235 | <p> |
213 | </p> |
236 | </p> |
214 | <h3><a name="how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></h3> |
237 | <h3><a name="how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></h3> |
215 | <p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
238 | <p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
216 | insecure mode then it is possible to use the following shell script |
239 | insecure mode then it is possible to use the following shell script |
… | |
… | |
251 | already in use in this mode.</p> |
274 | already in use in this mode.</p> |
252 | <pre> |
275 | <pre> |
253 | text data bss drs rss filename |
276 | text data bss drs rss filename |
254 | 98398 1664 24 15695 1824 rxvt --disable-everything |
277 | 98398 1664 24 15695 1824 rxvt --disable-everything |
255 | 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> |
278 | 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> |
256 | <p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft |
279 | <p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which <em>is</em> unfair, as this involves xft |
257 | and full locale/XIM support which are quite bloaty inside libX11 and my |
280 | and full locale/XIM support which are quite bloaty inside libX11 and my |
258 | libc), the two diverge, but not unreasnobaly so.</p> |
281 | libc), the two diverge, but not unreasnobaly so.</p> |
259 | <pre> |
282 | <pre> |
260 | text data bss drs rss filename |
283 | text data bss drs rss filename |
261 | 163431 2152 24 20123 2060 rxvt --enable-everything |
284 | 163431 2152 24 20123 2060 rxvt --enable-everything |
… | |
… | |
348 | <p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code> |
371 | <p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code> |
349 | by other values to change the degree of opacity. If it doesn't work and |
372 | by other values to change the degree of opacity. If it doesn't work and |
350 | your server crashes, you got to keep the pieces.</p> |
373 | your server crashes, you got to keep the pieces.</p> |
351 | <p> |
374 | <p> |
352 | </p> |
375 | </p> |
|
|
376 | <h3><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h3> |
|
|
377 | <p>Most fonts were not designed for terminal use, which means that character |
|
|
378 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
379 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
380 | these characters. For characters that are just ``a bit'' too wide a special |
|
|
381 | ``careful'' rendering mode is used that redraws adjacent characters.</p> |
|
|
382 | <p>All of this requires that fonts do not lie about character sizes, |
|
|
383 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
384 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
385 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
386 | cases).</p> |
|
|
387 | <p>It's not clear (to me at least), wether this is a bug in Xft, freetype, |
|
|
388 | or the respective font. If you encounter this problem you might try using |
|
|
389 | the <code>-lsp</code> option to give the font more height. If that doesn't work, you |
|
|
390 | might be forced to use a different font.</p> |
|
|
391 | <p>All of this is not a problem when using X11 core fonts, as their bounding |
|
|
392 | box data is correct.</p> |
|
|
393 | <p> |
|
|
394 | </p> |
|
|
395 | <h3><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h3> |
|
|
396 | <p>First of all, make sure you are running with the right terminal settings |
|
|
397 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
|
|
398 | make sure you have specified colours for italic and bold, as otherwise |
|
|
399 | rxvt-unicode might use reverse video to simulate the effect:</p> |
|
|
400 | <pre> |
|
|
401 | URxvt.colorBD: white |
|
|
402 | URxvt.colorIT: green</pre> |
|
|
403 | <p> |
|
|
404 | </p> |
|
|
405 | <h3><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h3> |
|
|
406 | <p>For some unexplainable reason, some rare programs assume a very weird |
|
|
407 | colour palette when confronted with a terminal with more than the standard |
|
|
408 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
|
|
409 | these programs not to assume non-ISO colours without very good reasons.</p> |
|
|
410 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
|
|
411 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
|
|
412 | fix colours but keep you from using other rxvt-unicode features.</p> |
|
|
413 | <p> |
|
|
414 | </p> |
|
|
415 | <h3><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h3> |
|
|
416 | <p>Yes, using an escape sequence. Try something like this, which has the same |
|
|
417 | effect as using the <code>-fn</code> switch, and takes effect immediately:</p> |
|
|
418 | <pre> |
|
|
419 | printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
|
|
420 | <p>This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
421 | japanese font), but you have to switch to chinese temporarily, where |
|
|
422 | japanese fonts would only be in your way.</p> |
|
|
423 | <p>You can think of this as a kind of manual ISO-2022 switching.</p> |
|
|
424 | <p> |
|
|
425 | </p> |
|
|
426 | <h3><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h3> |
|
|
427 | <p>Many fonts have difficulties with italic characters and hinting. For |
|
|
428 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
|
|
429 | Mono</code> completely fails in it's italic face. A workaround might be to |
|
|
430 | enable freetype autohinting, i.e. like this:</p> |
|
|
431 | <pre> |
|
|
432 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
433 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
|
|
434 | <p> |
|
|
435 | </p> |
|
|
436 | <h3><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h3> |
|
|
437 | <p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
438 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
439 | antialiasing (by appending <code>:antialias=false</code>), which saves lots of |
|
|
440 | memory and also speeds up rendering considerably.</p> |
|
|
441 | <p> |
|
|
442 | </p> |
|
|
443 | <h3><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h3> |
|
|
444 | <p>Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
445 | fall back to it's default font search list it will prefer X11 core |
|
|
446 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
447 | antialiasing disabled for most of them, because the author thinks they |
|
|
448 | look best that way.</p> |
|
|
449 | <p>If you want antialiasing, you have to specify the fonts manually.</p> |
|
|
450 | <p> |
|
|
451 | </p> |
|
|
452 | <h3><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h3> |
|
|
453 | <p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the |
|
|
454 | standard foreground colour.</p> |
|
|
455 | <p>For the standard background colour, blinking will actually make the |
|
|
456 | text blink when compiled with <code>--enable-blinking</code>. with standard |
|
|
457 | colours. Without <code>--enable-blinking</code>, the blink attribute will be |
|
|
458 | ignored.</p> |
|
|
459 | <p>On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
460 | foreground/background colors.</p> |
|
|
461 | <p>color0-7 are the low-intensity colors.</p> |
|
|
462 | <p>color8-15 are the corresponding high-intensity colors.</p> |
|
|
463 | <p> |
|
|
464 | </p> |
|
|
465 | <h3><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></h3> |
|
|
466 | <p>You can change the screen colors at run-time using <em>~/.Xdefaults</em> |
|
|
467 | resources (or as long-options).</p> |
|
|
468 | <p>Here are values that are supposed to resemble a VGA screen, |
|
|
469 | including the murky brown that passes for low-intensity yellow:</p> |
|
|
470 | <pre> |
|
|
471 | URxvt.color0: #000000 |
|
|
472 | URxvt.color1: #A80000 |
|
|
473 | URxvt.color2: #00A800 |
|
|
474 | URxvt.color3: #A8A800 |
|
|
475 | URxvt.color4: #0000A8 |
|
|
476 | URxvt.color5: #A800A8 |
|
|
477 | URxvt.color6: #00A8A8 |
|
|
478 | URxvt.color7: #A8A8A8</pre> |
|
|
479 | <pre> |
|
|
480 | URxvt.color8: #000054 |
|
|
481 | URxvt.color9: #FF0054 |
|
|
482 | URxvt.color10: #00FF54 |
|
|
483 | URxvt.color11: #FFFF54 |
|
|
484 | URxvt.color12: #0000FF |
|
|
485 | URxvt.color13: #FF00FF |
|
|
486 | URxvt.color14: #00FFFF |
|
|
487 | URxvt.color15: #FFFFFF</pre> |
|
|
488 | <p>And here is a more complete set of non-standard colors.</p> |
|
|
489 | <pre> |
|
|
490 | URxvt.cursorColor: #dc74d1 |
|
|
491 | URxvt.pointerColor: #dc74d1 |
|
|
492 | URxvt.background: #0e0e0e |
|
|
493 | URxvt.foreground: #4ad5e1 |
|
|
494 | URxvt.color0: #000000 |
|
|
495 | URxvt.color8: #8b8f93 |
|
|
496 | URxvt.color1: #dc74d1 |
|
|
497 | URxvt.color9: #dc74d1 |
|
|
498 | URxvt.color2: #0eb8c7 |
|
|
499 | URxvt.color10: #0eb8c7 |
|
|
500 | URxvt.color3: #dfe37e |
|
|
501 | URxvt.color11: #dfe37e |
|
|
502 | URxvt.color5: #9e88f0 |
|
|
503 | URxvt.color13: #9e88f0 |
|
|
504 | URxvt.color6: #73f7ff |
|
|
505 | URxvt.color14: #73f7ff |
|
|
506 | URxvt.color7: #e1dddd |
|
|
507 | URxvt.color15: #e1dddd</pre> |
|
|
508 | <p>They have been described (not by me) as ``pretty girly''.</p> |
|
|
509 | <p> |
|
|
510 | </p> |
|
|
511 | <h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3> |
|
|
512 | <p>See next entry.</p> |
|
|
513 | <p> |
|
|
514 | </p> |
|
|
515 | <h3><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h3> |
|
|
516 | <p>Most fonts do not contain the full range of Unicode, which is |
|
|
517 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
518 | your system/os) have specified does not cover all the characters you want |
|
|
519 | to display.</p> |
|
|
520 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
|
|
521 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
522 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
523 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
524 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
525 | the font that the characters it claims to contain indeed look correct.</p> |
|
|
526 | <p>In that case, select a font of your taste and add it to the font list, |
|
|
527 | e.g.:</p> |
|
|
528 | <pre> |
|
|
529 | urxvt -fn basefont,font2,font3...</pre> |
|
|
530 | <p>When rxvt-unicode sees a character, it will first look at the base |
|
|
531 | font. If the base font does not contain the character, it will go to the |
|
|
532 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
533 | search and use less resources within rxvt-unicode and the X-server.</p> |
|
|
534 | <p>The only limitation is that none of the fonts may be larger than the base |
|
|
535 | font, as the base font defines the terminal character cell size, which |
|
|
536 | must be the same due to the way terminals work.</p> |
|
|
537 | <p> |
|
|
538 | </p> |
353 | <h3><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h3> |
539 | <h3><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h3> |
354 | <p>This is because there is a difference between script and language -- |
540 | <p>This is because there is a difference between script and language -- |
355 | rxvt-unicode does not know which language the text that is output is, |
541 | rxvt-unicode does not know which language the text that is output is, |
356 | as it only knows the unicode character codes. If rxvt-unicode first |
542 | as it only knows the unicode character codes. If rxvt-unicode first |
357 | sees a japanese/chinese character, it might choose a japanese font for |
543 | sees a japanese/chinese character, it might choose a japanese font for |
… | |
… | |
367 | <p>In the future it might be possible to switch language preferences at |
553 | <p>In the future it might be possible to switch language preferences at |
368 | runtime (the internal data structure has no problem with using different |
554 | runtime (the internal data structure has no problem with using different |
369 | fonts for the same character at the same time, but no interface for this |
555 | fonts for the same character at the same time, but no interface for this |
370 | has been designed yet).</p> |
556 | has been designed yet).</p> |
371 | <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> |
557 | <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> |
372 | <p> |
|
|
373 | </p> |
|
|
374 | <h3><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h3> |
|
|
375 | <p>Most fonts were not designed for terminal use, which means that character |
|
|
376 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
377 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
378 | these characters. For characters that are just ``a bit'' too wide a special |
|
|
379 | ``careful'' rendering mode is used that redraws adjacent characters.</p> |
|
|
380 | <p>All of this requires that fonts do not lie about character sizes, |
|
|
381 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
382 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
383 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
384 | cases).</p> |
|
|
385 | <p>It's not clear (to me at least), wether this is a bug in Xft, freetype, |
|
|
386 | or the respective font. If you encounter this problem you might try using |
|
|
387 | the <code>-lsp</code> option to give the font more height. If that doesn't work, you |
|
|
388 | might be forced to use a different font.</p> |
|
|
389 | <p>All of this is not a problem when using X11 core fonts, as their bounding |
|
|
390 | box data is correct.</p> |
|
|
391 | <p> |
|
|
392 | </p> |
|
|
393 | <h3><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h3> |
|
|
394 | <p>First of all, make sure you are running with the right terminal settings |
|
|
395 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
|
|
396 | make sure you have specified colours for italic and bold, as otherwise |
|
|
397 | rxvt-unicode might use reverse video to simulate the effect:</p> |
|
|
398 | <pre> |
|
|
399 | URxvt.colorBD: white |
|
|
400 | URxvt.colorIT: green</pre> |
|
|
401 | <p> |
|
|
402 | </p> |
|
|
403 | <h3><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h3> |
|
|
404 | <p>For some unexplainable reason, some rare programs assume a very weird |
|
|
405 | colour palette when confronted with a terminal with more than the standard |
|
|
406 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
|
|
407 | these programs not to assume non-ISO colours without very good reasons.</p> |
|
|
408 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
|
|
409 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
|
|
410 | fix colours but keep you from using other rxvt-unicode features.</p> |
|
|
411 | <p> |
|
|
412 | </p> |
|
|
413 | <h3><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h3> |
|
|
414 | <p>Yes, using an escape sequence. Try something like this, which has the same |
|
|
415 | effect as using the <code>-fn</code> switch, and takes effect immediately:</p> |
|
|
416 | <pre> |
|
|
417 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
|
|
418 | <p>This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
419 | japanese font), but you have to switch to chinese temporarily, where |
|
|
420 | japanese fonts would only be in your way.</p> |
|
|
421 | <p>You can think of this as a kind of manual ISO-2022 switching.</p> |
|
|
422 | <p> |
|
|
423 | </p> |
|
|
424 | <h3><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h3> |
|
|
425 | <p>Many fonts have difficulties with italic characters and hinting. For |
|
|
426 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
|
|
427 | Mono</code> completely fails in it's italic face. A workaround might be to |
|
|
428 | enable freetype autohinting, i.e. like this:</p> |
|
|
429 | <pre> |
|
|
430 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
431 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
|
|
432 | <p> |
|
|
433 | </p> |
|
|
434 | <h3><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h3> |
|
|
435 | <p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
436 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
437 | antialiasing (by appending <code>:antialias=false</code>), which saves lots of |
|
|
438 | memory and also speeds up rendering considerably.</p> |
|
|
439 | <p> |
|
|
440 | </p> |
|
|
441 | <h3><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h3> |
|
|
442 | <p>Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
443 | fall back to it's default font search list it will prefer X11 core |
|
|
444 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
445 | antialiasing disabled for most of them, because the author thinks they |
|
|
446 | look best that way.</p> |
|
|
447 | <p>If you want antialiasing, you have to specify the fonts manually.</p> |
|
|
448 | <p> |
|
|
449 | </p> |
|
|
450 | <h3><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h3> |
|
|
451 | <p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the |
|
|
452 | standard foreground colour.</p> |
|
|
453 | <p>For the standard background colour, blinking will actually make the |
|
|
454 | text blink when compiled with <code>--enable-blinking</code>. with standard |
|
|
455 | colours. Without <code>--enable-blinking</code>, the blink attribute will be |
|
|
456 | ignored.</p> |
|
|
457 | <p>On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
458 | foreground/background colors.</p> |
|
|
459 | <p>color0-7 are the low-intensity colors.</p> |
|
|
460 | <p>color8-15 are the corresponding high-intensity colors.</p> |
|
|
461 | <p> |
|
|
462 | </p> |
|
|
463 | <h3><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></h3> |
|
|
464 | <p>You can change the screen colors at run-time using <em>~/.Xdefaults</em> |
|
|
465 | resources (or as long-options).</p> |
|
|
466 | <p>Here are values that are supposed to resemble a VGA screen, |
|
|
467 | including the murky brown that passes for low-intensity yellow:</p> |
|
|
468 | <pre> |
|
|
469 | URxvt.color0: #000000 |
|
|
470 | URxvt.color1: #A80000 |
|
|
471 | URxvt.color2: #00A800 |
|
|
472 | URxvt.color3: #A8A800 |
|
|
473 | URxvt.color4: #0000A8 |
|
|
474 | URxvt.color5: #A800A8 |
|
|
475 | URxvt.color6: #00A8A8 |
|
|
476 | URxvt.color7: #A8A8A8</pre> |
|
|
477 | <pre> |
|
|
478 | URxvt.color8: #000054 |
|
|
479 | URxvt.color9: #FF0054 |
|
|
480 | URxvt.color10: #00FF54 |
|
|
481 | URxvt.color11: #FFFF54 |
|
|
482 | URxvt.color12: #0000FF |
|
|
483 | URxvt.color13: #FF00FF |
|
|
484 | URxvt.color14: #00FFFF |
|
|
485 | URxvt.color15: #FFFFFF</pre> |
|
|
486 | <p>And here is a more complete set of non-standard colors described (not by |
|
|
487 | me) as ``pretty girly''.</p> |
|
|
488 | <pre> |
|
|
489 | URxvt.cursorColor: #dc74d1 |
|
|
490 | URxvt.pointerColor: #dc74d1 |
|
|
491 | URxvt.background: #0e0e0e |
|
|
492 | URxvt.foreground: #4ad5e1 |
|
|
493 | URxvt.color0: #000000 |
|
|
494 | URxvt.color8: #8b8f93 |
|
|
495 | URxvt.color1: #dc74d1 |
|
|
496 | URxvt.color9: #dc74d1 |
|
|
497 | URxvt.color2: #0eb8c7 |
|
|
498 | URxvt.color10: #0eb8c7 |
|
|
499 | URxvt.color3: #dfe37e |
|
|
500 | URxvt.color11: #dfe37e |
|
|
501 | URxvt.color5: #9e88f0 |
|
|
502 | URxvt.color13: #9e88f0 |
|
|
503 | URxvt.color6: #73f7ff |
|
|
504 | URxvt.color14: #73f7ff |
|
|
505 | URxvt.color7: #e1dddd |
|
|
506 | URxvt.color15: #e1dddd</pre> |
|
|
507 | <p> |
|
|
508 | </p> |
|
|
509 | <h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3> |
|
|
510 | <pre> |
|
|
511 | |
|
|
512 | See next entry.</pre> |
|
|
513 | <pre> |
|
|
514 | |
|
|
515 | =head3 How does rxvt-unicode choose fonts?</pre> |
|
|
516 | <pre> |
|
|
517 | |
|
|
518 | Most fonts do not contain the full range of Unicode, which is |
|
|
519 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
520 | your system/os) have specified does not cover all the characters you want |
|
|
521 | to display.</pre> |
|
|
522 | <pre> |
|
|
523 | |
|
|
524 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
|
|
525 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
526 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
527 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
528 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
529 | the font that the characters it claims to contain indeed look correct.</pre> |
|
|
530 | <pre> |
|
|
531 | |
|
|
532 | In that case, select a font of your taste and add it to the font list, |
|
|
533 | e.g.:</pre> |
|
|
534 | <pre> |
|
|
535 | |
|
|
536 | urxvt -fn basefont,font2,font3...</pre> |
|
|
537 | <pre> |
|
|
538 | |
|
|
539 | When rxvt-unicode sees a character, it will first look at the base |
|
|
540 | font. If the base font does not contain the character, it will go to the |
|
|
541 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
542 | search and use less resources within rxvt-unicode and the X-server.</pre> |
|
|
543 | <pre> |
|
|
544 | |
|
|
545 | The only limitation is that none of the fonts may be larger than the base |
|
|
546 | font, as the base font defines the terminal character cell size, which |
|
|
547 | must be the same due to the way terminals work.</pre> |
|
|
548 | <p> |
558 | <p> |
549 | </p> |
559 | </p> |
550 | <h2><a name="keyboard__mouse___user_interaction">Keyboard, Mouse & User Interaction</a></h2> |
560 | <h2><a name="keyboard__mouse___user_interaction">Keyboard, Mouse & User Interaction</a></h2> |
551 | <p> |
561 | <p> |
552 | </p> |
562 | </p> |
… | |
… | |
724 | <p> |
734 | <p> |
725 | </p> |
735 | </p> |
726 | <h2><a name="terminal_configuration">Terminal Configuration</a></h2> |
736 | <h2><a name="terminal_configuration">Terminal Configuration</a></h2> |
727 | <p> |
737 | <p> |
728 | </p> |
738 | </p> |
|
|
739 | <h3><a name="can_i_see_a_typical_configuration">Can I see a typical configuration?</a></h3> |
|
|
740 | <p>The default configuration tries to be xterm-like, which I don't like that |
|
|
741 | much, but it's least surprise to regular users.</p> |
|
|
742 | <p>As a rxvt or rxvt-unicode user, you are practically supposed to invest |
|
|
743 | time into customising your terminal. To get you started, here is the |
|
|
744 | author's .Xdefaults entries, with comments on what they do. It's certainly |
|
|
745 | not <em>typical</em>, but what's typical...</p> |
|
|
746 | <pre> |
|
|
747 | URxvt.cutchars: "()*,<>[]{}|' |
|
|
748 | URxvt.print-pipe: cat >/tmp/xxx</pre> |
|
|
749 | <p>These are just for testing stuff.</p> |
|
|
750 | <pre> |
|
|
751 | URxvt.imLocale: ja_JP.UTF-8 |
|
|
752 | URxvt.preeditType: OnTheSpot,None</pre> |
|
|
753 | <p>This tells rxvt-unicode to use a special locale when communicating with |
|
|
754 | the X Input Method, and also tells it to only use the OnTheSpot pre-edit |
|
|
755 | type, which requires the <code>xim-onthespot</code> perl extension but rewards me |
|
|
756 | with correct-looking fonts.</p> |
|
|
757 | <pre> |
|
|
758 | URxvt.perl-lib: /root/lib/urxvt |
|
|
759 | URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard |
|
|
760 | URxvt.selection.pattern-0: ( at .*? line \\d+) |
|
|
761 | URxvt.selection.pattern-1: ^(/[^:]+):\ |
|
|
762 | URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
763 | URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/</pre> |
|
|
764 | <p>This is my perl configuration. The first two set the perl library |
|
|
765 | directory and also tells urxvt to use a large number of extensions. I |
|
|
766 | develop for myself mostly, so I actually use most of the extensions I |
|
|
767 | write.</p> |
|
|
768 | <p>The selection stuff mainly makes the selection perl-error-message aware |
|
|
769 | and tells it to convert pelr error mssages into vi-commands to load the |
|
|
770 | relevant file and go tot he error line number.</p> |
|
|
771 | <pre> |
|
|
772 | URxvt.scrollstyle: plain |
|
|
773 | URxvt.secondaryScroll: true</pre> |
|
|
774 | <p>As the documentation says: plain is the preferred scrollbar for the |
|
|
775 | author. The <code>secondaryScroll</code> confgiures urxvt to scroll in full-screen |
|
|
776 | apps, like screen, so lines scorlled out of screen end up in urxvt's |
|
|
777 | scrollback buffer.</p> |
|
|
778 | <pre> |
|
|
779 | URxvt.background: #000000 |
|
|
780 | URxvt.foreground: gray90 |
|
|
781 | URxvt.color7: gray90 |
|
|
782 | URxvt.colorBD: #ffffff |
|
|
783 | URxvt.cursorColor: #e0e080 |
|
|
784 | URxvt.throughColor: #8080f0 |
|
|
785 | URxvt.highlightColor: #f0f0f0</pre> |
|
|
786 | <p>Some colours. Not sure which ones are being used or even non-defaults, but |
|
|
787 | these are in my .Xdefaults. Most notably, they set foreground/background |
|
|
788 | to light gray/black, and also make sure that the colour 7 matches the |
|
|
789 | default foreground colour.</p> |
|
|
790 | <pre> |
|
|
791 | URxvt.underlineColor: yellow</pre> |
|
|
792 | <p>Another colour, makes underline lines look different. Sometimes hurts, but |
|
|
793 | is mostly a nice effect.</p> |
|
|
794 | <pre> |
|
|
795 | URxvt.geometry: 154x36 |
|
|
796 | URxvt.loginShell: false |
|
|
797 | URxvt.meta: ignore |
|
|
798 | URxvt.utmpInhibit: true</pre> |
|
|
799 | <p>Uh, well, should be mostly self-explanatory. By specifying some defaults |
|
|
800 | manually, I can quickly switch them for testing.</p> |
|
|
801 | <pre> |
|
|
802 | URxvt.saveLines: 8192</pre> |
|
|
803 | <p>A large scrollback buffer is essential. Really.</p> |
|
|
804 | <pre> |
|
|
805 | URxvt.mapAlert: true</pre> |
|
|
806 | <p>The only case I use it is for my IRC window, which I like to keep |
|
|
807 | iconified till people msg me (which beeps).</p> |
|
|
808 | <pre> |
|
|
809 | URxvt.visualBell: true</pre> |
|
|
810 | <p>The audible bell is often annoying, especially when in a crowd.</p> |
|
|
811 | <pre> |
|
|
812 | URxvt.insecure: true</pre> |
|
|
813 | <p>Please don't hack my mutt! Ooops...</p> |
|
|
814 | <pre> |
|
|
815 | URxvt.pastableTabs: false</pre> |
|
|
816 | <p>I once thought this is a great idea.</p> |
|
|
817 | <pre> |
|
|
818 | urxvt.font: 9x15bold,\ |
|
|
819 | -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
|
|
820 | -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
|
|
821 | [codeset=JISX0208]xft:Kochi Gothic, \ |
|
|
822 | xft:Bitstream Vera Sans Mono:autohint=true, \ |
|
|
823 | xft:Code2000:antialias=false |
|
|
824 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
|
|
825 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
826 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
|
|
827 | <p>I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
|
|
828 | overwhelmed. A special note: the <code>9x15bold</code> mentioend above is actually |
|
|
829 | the version from XFree-3.3, as XFree-4 replaced it by a totally different |
|
|
830 | font (different glyphs for <code>;</code> and many other harmless characters), |
|
|
831 | while the second font is actually the <code>9x15bold</code> from XFree4/XOrg. The |
|
|
832 | bold version has less chars than the medium version, so I use it for rare |
|
|
833 | characters, too. Whene ditign sources with vim, I use italic for comments |
|
|
834 | and other stuff, which looks quite good with Bitstream Vera anti-aliased.</p> |
|
|
835 | <p>Terminus is a quite bad font (many very wrong glyphs), but for most of my |
|
|
836 | purposes, it works, and gives a different look, as my normal (Non-bold) |
|
|
837 | font is already bold, and I want to see a difference between bold and |
|
|
838 | normal fonts.</p> |
|
|
839 | <p>Please note that I used the <code>urxvt</code> instance name and not the <code>URxvt</code> |
|
|
840 | class name. Thats because I use different configs for different purposes, |
|
|
841 | for example, my IRC window is started with <code>-name IRC</code>, and uses these |
|
|
842 | defaults:</p> |
|
|
843 | <pre> |
|
|
844 | IRC*title: IRC |
|
|
845 | IRC*geometry: 87x12+535+542 |
|
|
846 | IRC*saveLines: 0 |
|
|
847 | IRC*mapAlert: true |
|
|
848 | IRC*font: suxuseuro |
|
|
849 | IRC*boldFont: suxuseuro |
|
|
850 | IRC*colorBD: white |
|
|
851 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
|
|
852 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007</pre> |
|
|
853 | <p><code>Alt-Shift-1</code> and <code>Alt-Shift-2</code> switch between two different font |
|
|
854 | sizes. <code>suxuseuro</code> allows me to keep an eye (and actually read) |
|
|
855 | stuff while keeping a very small window. If somebody pastes something |
|
|
856 | complicated (e.g. japanese), I temporarily switch to a larger font.</p> |
|
|
857 | <p>The above is all in my <code>.Xdefaults</code> (I don't use <code>.Xresources</code> nor |
|
|
858 | <code>xrdb</code>). I also have some resources in a separate <code>.Xdefaults-hostname</code> |
|
|
859 | file for different hosts, for example, on ym main desktop, I use:</p> |
|
|
860 | <pre> |
|
|
861 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
|
|
862 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
|
|
863 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
|
|
864 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
|
|
865 | URxvt.keysym.C-M-p: perl:test</pre> |
|
|
866 | <p>The first for keysym definitions allow me to quickly bring some windows |
|
|
867 | in the layout I like most. Ion users might start laughing but will stop |
|
|
868 | immediately when I tell them that I use my own Fvwm2 module for much the |
|
|
869 | same effect as Ion provides, and I only very rarely use the above key |
|
|
870 | combinations :-></p> |
|
|
871 | <p> |
|
|
872 | </p> |
729 | <h3><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h3> |
873 | <h3><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h3> |
730 | <p>Well, why, indeed? It does, in a way very similar to other X |
874 | <p>Well, why, indeed? It does, in a way very similar to other X |
731 | applications. Most importantly, this means that if you or your OS loads |
875 | applications. Most importantly, this means that if you or your OS loads |
732 | resources into the X display (the right way to do it), rxvt-unicode will |
876 | resources into the X display (the right way to do it), rxvt-unicode will |
733 | ignore any resource files in your home directory. It will only read |
877 | ignore any resource files in your home directory. It will only read |
… | |
… | |
761 | can either recompile rxvt-unicode with the desired TERM value or use a |
905 | can either recompile rxvt-unicode with the desired TERM value or use a |
762 | resource to set it:</p> |
906 | resource to set it:</p> |
763 | <pre> |
907 | <pre> |
764 | URxvt.termName: rxvt</pre> |
908 | URxvt.termName: rxvt</pre> |
765 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
909 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
766 | the rxvt terminfo file with the rxvt-unicode one.</p> |
910 | the rxvt terminfo file with the rxvt-unicode one and use <code>TERM=rxvt</code>.</p> |
767 | <p> |
911 | <p> |
768 | </p> |
912 | </p> |
769 | <h3><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h3> |
913 | <h3><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h3> |
770 | <p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
914 | <p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
771 | <code>enacs=\E[0@</code> and try again.</p> |
915 | <code>enacs=\E[0@</code> and try again.</p> |
… | |
… | |
857 | login script running within the rxvt-unicode window changes the locale to |
1001 | login script running within the rxvt-unicode window changes the locale to |
858 | something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> |
1002 | something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> |
859 | <p>The best thing is to fix your startup environment, as you will likely run |
1003 | <p>The best thing is to fix your startup environment, as you will likely run |
860 | into other problems. If nothing works you can try this in your .profile.</p> |
1004 | into other problems. If nothing works you can try this in your .profile.</p> |
861 | <pre> |
1005 | <pre> |
862 | printf '\e]701;%s\007' "$LC_CTYPE"</pre> |
1006 | printf '\33]701;%s\007' "$LC_CTYPE"</pre> |
863 | <p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not |
1007 | <p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not |
864 | supported on your systems. Some systems have a <code>locale</code> command which |
1008 | supported on your systems. Some systems have a <code>locale</code> command which |
865 | displays this (also, <code>perl -e0</code> can be used to check locale settings, as |
1009 | displays this (also, <code>perl -e0</code> can be used to check locale settings, as |
866 | it will complain loudly if it cannot set the locale). If it displays something |
1010 | it will complain loudly if it cannot set the locale). If it displays something |
867 | like:</p> |
1011 | like:</p> |
… | |
… | |
908 | </p> |
1052 | </p> |
909 | <h3><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h3> |
1053 | <h3><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h3> |
910 | <p>Yes, using an escape sequence. Try something like this, which sets |
1054 | <p>Yes, using an escape sequence. Try something like this, which sets |
911 | rxvt-unicode's idea of <code>LC_CTYPE</code>.</p> |
1055 | rxvt-unicode's idea of <code>LC_CTYPE</code>.</p> |
912 | <pre> |
1056 | <pre> |
913 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
1057 | printf '\33]701;%s\007' ja_JP.SJIS</pre> |
914 | <p>See also the previous answer.</p> |
1058 | <p>See also the previous answer.</p> |
915 | <p>Sometimes this capability is rather handy when you want to work in |
1059 | <p>Sometimes this capability is rather handy when you want to work in |
916 | one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it |
1060 | one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it |
917 | (e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which |
1061 | (e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which |
918 | first switches to a locale supported by xjdic and back later:</p> |
1062 | first switches to a locale supported by xjdic and back later:</p> |
919 | <pre> |
1063 | <pre> |
920 | printf '\e]701;%s\007' ja_JP.SJIS |
1064 | printf '\33]701;%s\007' ja_JP.SJIS |
921 | xjdic -js |
1065 | xjdic -js |
922 | printf '\e]701;%s\007' de_DE.UTF-8</pre> |
1066 | printf '\33]701;%s\007' de_DE.UTF-8</pre> |
923 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
1067 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
924 | for some locales where character width differs between program- and |
1068 | for some locales where character width differs between program- and |
925 | rxvt-unicode-locales.</p> |
1069 | rxvt-unicode-locales.</p> |
926 | <p> |
1070 | <p> |
927 | </p> |
1071 | </p> |
|
|
1072 | <h3><a name="i_have_problems_getting_my_input_method_working_">I have problems getting my input method working.</a></h3> |
|
|
1073 | <p>Try a search engine, as this is slightly different for every input method server.</p> |
|
|
1074 | <p>Here is a checklist:</p> |
|
|
1075 | <dl> |
|
|
1076 | <dt><strong><a name="item__2d_make_sure_your_locale_and_the_imlocale_are_sup">- Make sure your locale <em>and</em> the imLocale are supported on your OS.</a></strong><br /> |
|
|
1077 | </dt> |
|
|
1078 | <dd> |
|
|
1079 | Try <code>locale -a</code> or check the documentation for your OS. |
|
|
1080 | </dd> |
|
|
1081 | <p></p> |
|
|
1082 | <dt><strong><a name="item__2d_make_sure_your_locale_or_imlocale_matches_a_lo">- Make sure your locale or imLocale matches a locale supported by your XIM.</a></strong><br /> |
|
|
1083 | </dt> |
|
|
1084 | <dd> |
|
|
1085 | For example, <strong>kinput2</strong> does not support UTF-8 locales, you should use |
|
|
1086 | <code>ja_JP.EUC-JP</code> or equivalent. |
|
|
1087 | </dd> |
|
|
1088 | <p></p> |
|
|
1089 | <dt><strong><a name="item__2d_make_sure_your_xim_server_is_actually_running_">- Make sure your XIM server is actually running.</a></strong><br /> |
|
|
1090 | </dt> |
|
|
1091 | <dt><strong><a name="item__2d_make_sure_the_xmodifiers_environment_variable_">- Make sure the <code>XMODIFIERS</code> environment variable is set correctly when <em>starting</em> rxvt-unicode.</a></strong><br /> |
|
|
1092 | </dt> |
|
|
1093 | <dd> |
|
|
1094 | When you want to use e.g. <strong>kinput2</strong>, it must be set to |
|
|
1095 | <code>@im=kinput2</code>. For <strong>scim</strong>, use <code>@im=SCIM</code>. Youc an see what input |
|
|
1096 | method servers are running with this command: |
|
|
1097 | </dd> |
|
|
1098 | <dd> |
|
|
1099 | <pre> |
|
|
1100 | xprop -root XIM_SERVERS</pre> |
|
|
1101 | </dd> |
|
|
1102 | <p></p> |
|
|
1103 | <dt></dt> |
|
|
1104 | </dl> |
|
|
1105 | <p> |
|
|
1106 | </p> |
928 | <h3><a name="my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants <some encoding> but I want UTF-8, what can I do?</a></h3> |
1107 | <h3><a name="my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants <some encoding> but I want UTF-8, what can I do?</a></h3> |
929 | <p>You can specify separate locales for the input method and the rest of the |
1108 | <p>You can specify separate locales for the input method and the rest of the |
930 | terminal, using the resource <code>imlocale</code>:</p> |
1109 | terminal, using the resource <code>imlocale</code>:</p> |
931 | <pre> |
1110 | <pre> |
932 | URxvt.imlocale: ja_JP.EUC-JP</pre> |
1111 | URxvt.imlocale: ja_JP.EUC-JP</pre> |
933 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
1112 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
934 | use your input method. Please note, however, that you will not be able to |
1113 | use your input method. Please note, however, that, depending on your Xlib |
935 | input characters outside <code>EUC-JP</code> in a normal way then, as your input |
1114 | version, you may not be able to input characters outside <code>EUC-JP</code> in a |
936 | method limits you.</p> |
1115 | normal way then, as your input method limits you.</p> |
937 | <p> |
1116 | <p> |
938 | </p> |
1117 | </p> |
939 | <h3><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h3> |
1118 | <h3><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h3> |
940 | <p>Unfortunately, this is unavoidable, as the XIM protocol is racy by |
1119 | <p>Unfortunately, this is unavoidable, as the XIM protocol is racy by |
941 | design. Applications can avoid some crashes at the expense of memory |
1120 | design. Applications can avoid some crashes at the expense of memory |
… | |
… | |
1048 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
1227 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
1049 | to 8-bit encodings.</p> |
1228 | to 8-bit encodings.</p> |
1050 | <p> |
1229 | <p> |
1051 | </p> |
1230 | </p> |
1052 | <hr /> |
1231 | <hr /> |
1053 | <h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> |
1232 | <h1><a name="rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></h1> |
1054 | <p> |
|
|
1055 | </p> |
|
|
1056 | <hr /> |
|
|
1057 | <h1><a name="description">DESCRIPTION</a></h1> |
|
|
1058 | <p>The rest of this document describes various technical aspects of |
1233 | <p>The rest of this document describes various technical aspects of |
1059 | <strong>rxvt-unicode</strong>. First the description of supported command sequences, |
1234 | <strong>rxvt-unicode</strong>. First the description of supported command sequences, |
1060 | followed by pixmap support and last by a description of all features |
1235 | followed by pixmap support and last by a description of all features |
1061 | selectable at <code>configure</code> time.</p> |
1236 | selectable at <code>configure</code> time.</p> |
1062 | <p> |
1237 | <p> |
1063 | </p> |
1238 | </p> |
1064 | <hr /> |
|
|
1065 | <h1><a name="definitions">Definitions</a></h1> |
1239 | <h2><a name="definitions">Definitions</a></h2> |
1066 | <dl> |
1240 | <dl> |
1067 | <dt><strong><a name="item_c"><strong><code>c</code> </strong>></a></strong><br /> |
1241 | <dt><strong><a name="item_c"><strong><code>c</code> </strong>></a></strong><br /> |
1068 | </dt> |
1242 | </dt> |
1069 | <dd> |
1243 | <dd> |
1070 | The literal character c. |
1244 | The literal character c. |
… | |
… | |
1096 | A text parameter composed of printable characters. |
1270 | A text parameter composed of printable characters. |
1097 | </dd> |
1271 | </dd> |
1098 | <p></p></dl> |
1272 | <p></p></dl> |
1099 | <p> |
1273 | <p> |
1100 | </p> |
1274 | </p> |
1101 | <hr /> |
|
|
1102 | <h1><a name="values">Values</a></h1> |
1275 | <h2><a name="values">Values</a></h2> |
1103 | <dl> |
1276 | <dl> |
1104 | <dt><strong><a name="item_enq"><strong><code>ENQ</code> </strong>></a></strong><br /> |
1277 | <dt><strong><a name="item_enq"><strong><code>ENQ</code> </strong>></a></strong><br /> |
1105 | </dt> |
1278 | </dt> |
1106 | <dd> |
1279 | <dd> |
1107 | Enquiry (Ctrl-E) = Send Device Attributes (DA) |
1280 | Enquiry (Ctrl-E) = Send Device Attributes (DA) |
… | |
… | |
1170 | Space Character |
1343 | Space Character |
1171 | </dd> |
1344 | </dd> |
1172 | <p></p></dl> |
1345 | <p></p></dl> |
1173 | <p> |
1346 | <p> |
1174 | </p> |
1347 | </p> |
1175 | <hr /> |
|
|
1176 | <h1><a name="escape_sequences">Escape Sequences</a></h1> |
1348 | <h2><a name="escape_sequences">Escape Sequences</a></h2> |
1177 | <dl> |
1349 | <dl> |
1178 | <dt><strong><a name="item_esc__23_8"><strong><code>ESC # 8</code> </strong>></a></strong><br /> |
1350 | <dt><strong><a name="item_esc__23_8"><strong><code>ESC # 8</code> </strong>></a></strong><br /> |
1179 | </dt> |
1351 | </dt> |
1180 | <dd> |
1352 | <dd> |
1181 | DEC Screen Alignment Test (DECALN) |
1353 | DEC Screen Alignment Test (DECALN) |
… | |
… | |
1314 | <tr><td>C = K </td><td>German character set unimplemented</td></tr> |
1486 | <tr><td>C = K </td><td>German character set unimplemented</td></tr> |
1315 | </table><p></p></dl> |
1487 | </table><p></p></dl> |
1316 | <p></p> |
1488 | <p></p> |
1317 | <p> |
1489 | <p> |
1318 | </p> |
1490 | </p> |
1319 | <hr /> |
|
|
1320 | <h1><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h1> |
1491 | <h2><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h2> |
1321 | <dl> |
1492 | <dl> |
1322 | <dt><strong><a name="item_esc__5b_ps__40"><strong><code>ESC [ Ps @</code> </strong>></a></strong><br /> |
1493 | <dt><strong><a name="item_esc__5b_ps__40"><strong><code>ESC [ Ps @</code> </strong>></a></strong><br /> |
1323 | </dt> |
1494 | </dt> |
1324 | <dd> |
1495 | <dd> |
1325 | Insert <strong><a href="#item_ps"><code>Ps</code></a> </strong>> (Blank) <code>Character(s)</code> [default: 1] (ICH) |
1496 | Insert <strong><a href="#item_ps"><code>Ps</code></a> </strong>> (Blank) <code>Character(s)</code> [default: 1] (ICH) |
… | |
… | |
1621 | </dd> |
1792 | </dd> |
1622 | <p></p></dl> |
1793 | <p></p></dl> |
1623 | <p></p> |
1794 | <p></p> |
1624 | <p> |
1795 | <p> |
1625 | </p> |
1796 | </p> |
1626 | <hr /> |
|
|
1627 | <h1><a name="dec_private_modes">DEC Private Modes</a></h1> |
1797 | <h2><a name="dec_private_modes">DEC Private Modes</a></h2> |
1628 | <dl> |
1798 | <dl> |
1629 | <dt><strong><a name="item_esc__5b__3f_pm_h"><strong><code>ESC [ ? Pm h</code> </strong>></a></strong><br /> |
1799 | <dt><strong><a name="item_esc__5b__3f_pm_h"><strong><code>ESC [ ? Pm h</code> </strong>></a></strong><br /> |
1630 | </dt> |
1800 | </dt> |
1631 | <dd> |
1801 | <dd> |
1632 | DEC Private Mode Set (DECSET) |
1802 | DEC Private Mode Set (DECSET) |
… | |
… | |
1798 | </table></dl> |
1968 | </table></dl> |
1799 | </dl> |
1969 | </dl> |
1800 | <p></p> |
1970 | <p></p> |
1801 | <p> |
1971 | <p> |
1802 | </p> |
1972 | </p> |
1803 | <hr /> |
|
|
1804 | <h1><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h1> |
1973 | <h2><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h2> |
1805 | <dl> |
1974 | <dl> |
1806 | <dt><strong><a name="item_esc__5d_ps_3bpt_st"><strong><code>ESC ] Ps;Pt ST</code> </strong>></a></strong><br /> |
1975 | <dt><strong><a name="item_esc__5d_ps_3bpt_st"><strong><code>ESC ] Ps;Pt ST</code> </strong>></a></strong><br /> |
1807 | </dt> |
1976 | </dt> |
1808 | <dd> |
1977 | <dd> |
1809 | Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b, |
1978 | Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b, |
… | |
… | |
1841 | <tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
2010 | <tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr> |
1842 | <tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
2011 | <tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
1843 | <tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
2012 | <tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr> |
1844 | <tr><td>Ps = 777</td><td>Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).</td></tr> |
2013 | <tr><td>Ps = 777</td><td>Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).</td></tr> |
1845 | </table><p></p></dl> |
2014 | </table><p></p></dl> |
1846 | <p></p> |
|
|
1847 | <p> |
2015 | <p> |
1848 | </p> |
2016 | </p> |
1849 | <hr /> |
2017 | <hr /> |
1850 | <h1><a name="xpm">XPM</a></h1> |
2018 | <h1><a name="xpm">XPM</a></h1> |
1851 | <p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>> then value |
2019 | <p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>> then value |
… | |
… | |
1956 | </dt> |
2124 | </dt> |
1957 | <table> |
2125 | <table> |
1958 | <tr><td>4</td><td>Shift</td></tr> |
2126 | <tr><td>4</td><td>Shift</td></tr> |
1959 | <tr><td>8</td><td>Meta</td></tr> |
2127 | <tr><td>8</td><td>Meta</td></tr> |
1960 | <tr><td>16</td><td>Control</td></tr> |
2128 | <tr><td>16</td><td>Control</td></tr> |
1961 | <tr><td>32</td><td>Double Click (Rxvt extension)</td></tr> |
2129 | <tr><td>32</td><td>Double Click (rxvt extension)</td></tr> |
1962 | </table><p>Col = <strong><code><x> - SPACE</code> </strong>></p> |
2130 | </table><p>Col = <strong><code><x> - SPACE</code> </strong>></p> |
1963 | <p>Row = <strong><code><y> - SPACE</code> </strong>></p> |
2131 | <p>Row = <strong><code><y> - SPACE</code> </strong>></p> |
1964 | </dl> |
2132 | </dl> |
1965 | <p> |
2133 | <p> |
1966 | </p> |
2134 | </p> |
… | |
… | |
2426 | <p></p> |
2594 | <p></p> |
2427 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dincludes_3ddir">--with-xpm-includes=DIR</a></strong><br /> |
2595 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dincludes_3ddir">--with-xpm-includes=DIR</a></strong><br /> |
2428 | </dt> |
2596 | </dt> |
2429 | <dd> |
2597 | <dd> |
2430 | Look for the XPM includes in DIR. |
2598 | Look for the XPM includes in DIR. |
2431 | |
|
|
2432 | |
|
|
2433 | </dd> |
2599 | </dd> |
2434 | <p></p> |
2600 | <p></p> |
2435 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br /> |
2601 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br /> |
2436 | </dt> |
2602 | </dt> |
2437 | <dd> |
2603 | <dd> |
2438 | Look for the XPM library in DIR. |
2604 | Look for the XPM library in DIR. |
2439 | |
|
|
2440 | |
|
|
2441 | </dd> |
2605 | </dd> |
2442 | <p></p> |
2606 | <p></p> |
2443 | <dt><strong><a name="item__2d_2dwith_2dxpm">--with-xpm</a></strong><br /> |
2607 | <dt><strong><a name="item__2d_2dwith_2dxpm">--with-xpm</a></strong><br /> |
2444 | </dt> |
2608 | </dt> |
2445 | <dd> |
2609 | <dd> |
2446 | Not needed - define via --enable-xpm-background. |
2610 | Not needed - define via --enable-xpm-background. |
2447 | |
|
|
2448 | |
|
|
2449 | </dd> |
2611 | </dd> |
2450 | <p></p></dl> |
2612 | <p></p></dl> |
2451 | <p> |
2613 | <p> |
2452 | </p> |
2614 | </p> |
2453 | <hr /> |
2615 | <hr /> |
2454 | <h1><a name="authors">AUTHORS</a></h1> |
2616 | <h1><a name="authors">AUTHORS</a></h1> |
2455 | <p>Marc Lehmann <<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>> converted this document to pod and |
2617 | <p>Marc Lehmann <<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>> converted this document to pod and |
2456 | reworked it from the original Rxvt documentation, which was done by Geoff |
2618 | reworked it from the original Rxvt documentation, which was done by Geoff |
2457 | Wing <<a href="mailto:gcw@pobox.com">gcw@pobox.com</a>>, who in turn used the XTerm documentation and other |
2619 | Wing <<a href="mailto:gcw@pobox.com">gcw@pobox.com</a>>, who in turn used the XTerm documentation and other |
2458 | sources. |
2620 | sources.</p> |
2459 | |
|
|
2460 | </p> |
|
|
2461 | |
2621 | |
2462 | </body> |
2622 | </body> |
2463 | |
2623 | |
2464 | </html> |
2624 | </html> |