… | |
… | |
16 | <li><a href="#synopsis">SYNOPSIS</a></li> |
16 | <li><a href="#synopsis">SYNOPSIS</a></li> |
17 | <li><a href="#description">DESCRIPTION</a></li> |
17 | <li><a href="#description">DESCRIPTION</a></li> |
18 | <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li> |
18 | <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li> |
19 | <ul> |
19 | <ul> |
20 | |
20 | |
|
|
21 | <li><a href="#meta__features___commandline_issues">Meta, Features & Commandline Issues</a></li> |
|
|
22 | <ul> |
|
|
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> |
|
|
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> |
|
|
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_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</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_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="#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 | </ul> |
|
|
35 | |
|
|
36 | <li><a href="#rendering__font___look_and_feel_issues">Rendering, Font & Look and Feel Issues</a></li> |
|
|
37 | <ul> |
|
|
38 | |
|
|
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="#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> |
|
|
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> |
|
|
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> |
|
|
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> |
|
|
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> |
|
|
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 | </ul> |
|
|
52 | |
|
|
53 | <li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse & User Interaction</a></li> |
|
|
54 | <ul> |
|
|
55 | |
21 | <li><a href="#the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></li> |
56 | <li><a href="#the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></li> |
22 | <li><a href="#i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></li> |
57 | <li><a href="#i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></li> |
23 | <li><a href="#the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></li> |
58 | <li><a href="#the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></li> |
24 | <li><a href="#during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></li> |
59 | <li><a href="#during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></li> |
25 | <li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li> |
|
|
26 | <li><a href="#i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></li> |
|
|
27 | <li><a href="#isn_t_rxvt_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt supposed to be small? Don't all those features bloat?</a></li> |
|
|
28 | <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li> |
|
|
29 | <li><a href="#does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></li> |
|
|
30 | <li><a href="#how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></li> |
|
|
31 | <li><a href="#i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></li> |
|
|
32 | <li><a href="#i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></li> |
|
|
33 | <li><a href="#i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></li> |
|
|
34 | <li><a href="#when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></li> |
|
|
35 | <li><a href="#tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></li> |
|
|
36 | <li><a href="#bash_s_readline_does_not_work_correctly_under_rxvt_"><code>bash</code>'s readline does not work correctly under rxvt.</a></li> |
|
|
37 | <li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li> |
|
|
38 | <li><a href="#why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></li> |
|
|
39 | <li><a href="#why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></li> |
|
|
40 | <li><a href="#why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></li> |
|
|
41 | <li><a href="#why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></li> |
|
|
42 | <li><a href="#my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></li> |
60 | <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> |
61 | <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> |
62 | <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> |
63 | <li><a href="#mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</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> |
64 | <li><a href="#what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</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> |
65 | <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> |
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> |
66 | <li><a href="#i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></li> |
56 | <li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li> |
67 | </ul> |
|
|
68 | |
|
|
69 | <li><a href="#terminal_configuration">Terminal Configuration</a></li> |
|
|
70 | <ul> |
|
|
71 | |
|
|
72 | <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> |
|
|
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> |
|
|
75 | <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> |
|
|
76 | <li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li> |
|
|
77 | <li><a href="#why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></li> |
|
|
78 | <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> |
|
|
79 | <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> |
|
|
80 | <li><a href="#why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></li> |
|
|
81 | </ul> |
|
|
82 | |
|
|
83 | <li><a href="#encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></li> |
|
|
84 | <ul> |
|
|
85 | |
|
|
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> |
|
|
87 | <li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</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> |
88 | <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> |
89 | <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> |
90 | <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> |
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> |
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> |
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> |
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> |
93 | </ul> |
65 | <li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li> |
94 | |
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> |
95 | <li><a href="#operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></li> |
67 | <li><a href="#mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></li> |
96 | <ul> |
68 | <li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li> |
97 | |
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> |
98 | <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> |
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> |
99 | <li><a href="#i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></li> |
71 | <li><a href="#what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></li> |
100 | <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> |
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> |
101 | <li><a href="#on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></li> |
73 | <li><a href="#i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_mappings_that_rxvtunicode_doesn_t_recognize_">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize.</a></li> |
102 | <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> |
74 | <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li> |
103 | <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> |
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> |
104 | <li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</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> |
105 | </ul> |
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> |
106 | |
78 | </ul> |
107 | </ul> |
79 | |
108 | |
80 | <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> |
109 | <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> |
81 | <li><a href="#description">DESCRIPTION</a></li> |
110 | <li><a href="#description">DESCRIPTION</a></li> |
82 | <li><a href="#definitions">Definitions</a></li> |
111 | <li><a href="#definitions">Definitions</a></li> |
… | |
… | |
123 | </p> |
152 | </p> |
124 | <hr /> |
153 | <hr /> |
125 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
154 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
126 | <p> |
155 | <p> |
127 | </p> |
156 | </p> |
128 | <h2><a name="the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></h2> |
157 | <h2><a name="meta__features___commandline_issues">Meta, Features & Commandline Issues</a></h2> |
129 | <p>If you want to select e.g. alphanumeric words, you can use the following |
|
|
130 | setting:</p> |
|
|
131 | <pre> |
|
|
132 | URxvt.selection.pattern-0: ([[:word:]]+)</pre> |
|
|
133 | <p>If you click more than twice, the selection will be extended |
|
|
134 | more and more.</p> |
|
|
135 | <p>To get a selection that is very similar to the old code, try this pattern:</p> |
|
|
136 | <pre> |
|
|
137 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)</pre> |
|
|
138 | <p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also |
|
|
139 | selects words like the old code.</p> |
|
|
140 | <p> |
|
|
141 | </p> |
158 | <p> |
142 | <h2><a name="i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></h2> |
|
|
143 | <p>You can disable the perl extension completely by setting the |
|
|
144 | <strong>perl-ext-common</strong> resource to the empty string, which also keeps |
|
|
145 | rxvt-unicode from initialising perl, saving memory.</p> |
|
|
146 | <p>If you only want to disable specific features, you first have to |
|
|
147 | identify which perl extension is responsible. For this, read the section |
|
|
148 | <strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For |
|
|
149 | example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify |
|
|
150 | this <strong>perl-ext-common</strong> resource:</p> |
|
|
151 | <pre> |
|
|
152 | URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre> |
|
|
153 | <p>This will keep the default extensions, but disable the two popup |
|
|
154 | extensions. Some extensions can also be configured, for example, |
|
|
155 | scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any |
|
|
156 | other combination either by setting the <strong>searchable-scrollback</strong> resource:</p> |
|
|
157 | <pre> |
|
|
158 | URxvt.searchable-scrollback: CM-s</pre> |
|
|
159 | <p> |
159 | </p> |
|
|
160 | <h3><a name="my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></h3> |
|
|
161 | <p>Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>, |
|
|
162 | channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be |
|
|
163 | interested in learning about new and exciting problems (but not FAQs :).</p> |
160 | </p> |
164 | <p> |
161 | <h2><a name="the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></h2> |
|
|
162 | <p>See next entry.</p> |
|
|
163 | <p> |
165 | </p> |
164 | </p> |
166 | <h3><a name="does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></h3> |
165 | <h2><a name="during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></h2> |
167 | <p>Beginning with version 7.3, there is a perl extension that implements a |
166 | <p>These are caused by the <code>readline</code> perl extension. Under normal |
168 | simple tabbed terminal. It is installed by default, so any of these should |
167 | circumstances, it will move your cursor around when you click into the |
169 | give you tabs:</p> |
168 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
169 | but when running a program that doesn't parse cursor movements or in some |
|
|
170 | cases during rlogin sessions, it fails to detect this properly.</p> |
|
|
171 | <p>You can permamently switch this feature off by disabling the <code>readline</code> |
|
|
172 | extension:</p> |
|
|
173 | <pre> |
170 | <pre> |
|
|
171 | rxvt -pe tabbed</pre> |
|
|
172 | <pre> |
174 | URxvt.perl-ext-common: default,-readline</pre> |
173 | URxvt.perl-ext-common: default,tabbed</pre> |
175 | <p> |
174 | <p>It will also work fine with tabbing functionality of many window managers |
|
|
175 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
176 | embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or |
|
|
177 | the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt |
|
|
178 | (murxvt) terminal as an example embedding application.</p> |
176 | </p> |
179 | <p> |
177 | <h2><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h2> |
|
|
178 | <p>Well, why, indeed? It does, in a way very similar to other X |
|
|
179 | applications. Most importantly, this means that if you or your OS loads |
|
|
180 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
181 | ignore any resource files in your home directory. It will only read |
|
|
182 | <em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p> |
|
|
183 | <p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that |
|
|
184 | resources are loaded into your X-server. In this case, you have to |
|
|
185 | re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p> |
|
|
186 | <p>Also consider the form resources have to use:</p> |
|
|
187 | <pre> |
|
|
188 | URxvt.resource: value</pre> |
|
|
189 | <p>If you want to use another form (there are lots of different ways of |
|
|
190 | specifying resources), make sure you understand wether and why it |
|
|
191 | works. If unsure, use the form above.</p> |
|
|
192 | <p> |
180 | </p> |
|
|
181 | <h3><a name="how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></h3> |
|
|
182 | <p>The version number is displayed with the usage (-h). Also the escape |
|
|
183 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. When |
|
|
184 | using the rxvtc client, the version displayed is that of the |
|
|
185 | daemon.</p> |
193 | </p> |
186 | <p> |
194 | <h2><a name="i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></h2> |
|
|
195 | <p>First of all, transparency isn't officially supported in rxvt-unicode, so |
|
|
196 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
197 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
198 | of passage: ... and you failed.</p> |
|
|
199 | <p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option |
|
|
200 | descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p> |
|
|
201 | <p>1. Use inheritPixmap:</p> |
|
|
202 | <pre> |
|
|
203 | Esetroot wallpaper.jpg |
|
|
204 | rxvt -ip -tint red -sh 40</pre> |
|
|
205 | <p>That works. If you think it doesn't, you lack transparency and tinting |
|
|
206 | support, or you are unable to read.</p> |
|
|
207 | <p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
|
|
208 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
209 | your picture with gimp:</p> |
|
|
210 | <pre> |
|
|
211 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
212 | rxvt -pixmap background.xpm -pe automove-background</pre> |
|
|
213 | <p>That works. If you think it doesn't, you lack XPM and Perl support, or you |
|
|
214 | are unable to read.</p> |
|
|
215 | <p>3. Use an ARGB visual:</p> |
|
|
216 | <pre> |
|
|
217 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre> |
|
|
218 | <p>This requires XFT support, and the support of your X-server. If that |
|
|
219 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
220 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
221 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
222 | doesn't mean that your WM has the required kludges in place.</p> |
|
|
223 | <p>4. Use xcompmgr and let it do the job:</p> |
|
|
224 | <pre> |
|
|
225 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
226 | -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre> |
|
|
227 | <p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code> |
|
|
228 | by other values to change the degree of opacity. If it doesn't work and |
|
|
229 | your server crashes, you got to keep the pieces.</p> |
|
|
230 | <p> |
187 | </p> |
|
|
188 | <h3><a name="rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></h3> |
|
|
189 | <p>Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
190 | don't use. One thing you should try is to configure out all settings that |
|
|
191 | you don't need, for example, Xft support is a resource hog by design, |
|
|
192 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
193 | accidentally when rxvt-unicode tries to find a font for your characters.</p> |
|
|
194 | <p>Also, many people (me included) like large windows and even larger |
|
|
195 | scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use |
|
|
196 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
197 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
198 | use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as |
|
|
199 | rxvt-unicode then uses 8 bytes per screen cell.</p> |
231 | </p> |
200 | <p> |
|
|
201 | </p> |
|
|
202 | <h3><a name="how_can_i_start_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</a></h3> |
|
|
203 | <p>Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
|
|
204 | display, create the listening socket and then fork.</p> |
|
|
205 | <p> |
|
|
206 | </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> |
|
|
208 | <p>rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
|
|
209 | check and see if that is set. Note that several programs, JED, slrn, |
|
|
210 | Midnight Commander automatically check this variable to decide whether or |
|
|
211 | not to use color.</p> |
|
|
212 | <p> |
|
|
213 | </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> |
|
|
215 | <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 |
|
|
217 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
218 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
|
|
219 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
220 | regular xterm.</p> |
|
|
221 | <p>Courtesy of Chuck Blake <<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>> with the following shell script |
|
|
222 | snippets:</p> |
|
|
223 | <pre> |
|
|
224 | # Bourne/Korn/POSIX family of shells: |
|
|
225 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
226 | if [ ${TERM:-foo} = xterm ]; then |
|
|
227 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
228 | echo -n '^[Z' |
|
|
229 | read term_id |
|
|
230 | stty icanon echo |
|
|
231 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
232 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
233 | read DISPLAY # set it in our local shell |
|
|
234 | fi |
|
|
235 | fi</pre> |
|
|
236 | <p> |
|
|
237 | </p> |
|
|
238 | <h3><a name="how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></h3> |
|
|
239 | <p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>, |
|
|
240 | one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to |
|
|
241 | the doc subdirectory and enter <code>make alldoc</code>.</p> |
|
|
242 | <p> |
|
|
243 | </p> |
232 | <h2><a name="isn_t_rxvt_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt supposed to be small? Don't all those features bloat?</a></h2> |
244 | <h3><a name="isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></h3> |
233 | <p>I often get asked about this, and I think, no, they didn't cause extra |
245 | <p>I often get asked about this, and I think, no, they didn't cause extra |
234 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
246 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
235 | that the urxvt binary is larger (due to some encoding tables always being |
247 | that the urxvt binary is larger (due to some encoding tables always being |
236 | compiled in), but it actually uses less memory (RSS) after startup. Even |
248 | compiled in), but it actually uses less memory (RSS) after startup. Even |
237 | with <code>--disable-everything</code>, this comparison is a bit unfair, as many |
249 | with <code>--disable-everything</code>, this comparison is a bit unfair, as many |
… | |
… | |
265 | 43180k in daemons that stay around after exit, plus half a minute of |
277 | 43180k in daemons that stay around after exit, plus half a minute of |
266 | startup time, including the hundreds of warnings it spits out), it fares |
278 | startup time, including the hundreds of warnings it spits out), it fares |
267 | extremely well *g*.</p> |
279 | extremely well *g*.</p> |
268 | <p> |
280 | <p> |
269 | </p> |
281 | </p> |
270 | <h2><a name="why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></h2> |
282 | <h3><a name="why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></h3> |
271 | <p>Is this a question? :) It comes up very often. The simple answer is: I had |
283 | <p>Is this a question? :) It comes up very often. The simple answer is: I had |
272 | to write it, and C++ allowed me to write and maintain it in a fraction |
284 | to write it, and C++ allowed me to write and maintain it in a fraction |
273 | of the time and effort (which is a scarce resource for me). Put even |
285 | of the time and effort (which is a scarce resource for me). Put even |
274 | shorter: It simply wouldn't exist without C++.</p> |
286 | shorter: It simply wouldn't exist without C++.</p> |
275 | <p>My personal stance on this is that C++ is less portable than C, but in |
287 | <p>My personal stance on this is that C++ is less portable than C, but in |
… | |
… | |
295 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
307 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
296 | <p>No large bloated libraries (of course, none were linked in statically), |
308 | <p>No large bloated libraries (of course, none were linked in statically), |
297 | except maybe libX11 :)</p> |
309 | except maybe libX11 :)</p> |
298 | <p> |
310 | <p> |
299 | </p> |
311 | </p> |
300 | <h2><a name="does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></h2> |
312 | <h2><a name="rendering__font___look_and_feel_issues">Rendering, Font & Look and Feel Issues</a></h2> |
301 | <p>Beginning with version 7.3, there is a perl extension that implements a |
|
|
302 | simple tabbed terminal. It is installed by default, so any of these should |
|
|
303 | give you tabs:</p> |
|
|
304 | <pre> |
313 | <p> |
305 | rxvt -pe tabbed</pre> |
314 | </p> |
|
|
315 | <h3><a name="i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></h3> |
|
|
316 | <p>First of all, transparency isn't officially supported in rxvt-unicode, so |
|
|
317 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
318 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
319 | of passage: ... and you failed.</p> |
|
|
320 | <p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option |
|
|
321 | descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p> |
|
|
322 | <p>1. Use inheritPixmap:</p> |
|
|
323 | <pre> |
|
|
324 | Esetroot wallpaper.jpg |
|
|
325 | rxvt -ip -tint red -sh 40</pre> |
|
|
326 | <p>That works. If you think it doesn't, you lack transparency and tinting |
|
|
327 | support, or you are unable to read.</p> |
|
|
328 | <p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
|
|
329 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
330 | your picture with gimp or any other tool:</p> |
|
|
331 | <pre> |
|
|
332 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
333 | rxvt -pixmap background.xpm -pe automove-background</pre> |
|
|
334 | <p>That works. If you think it doesn't, you lack XPM and Perl support, or you |
|
|
335 | are unable to read.</p> |
|
|
336 | <p>3. Use an ARGB visual:</p> |
|
|
337 | <pre> |
|
|
338 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre> |
|
|
339 | <p>This requires XFT support, and the support of your X-server. If that |
|
|
340 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
341 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
342 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
343 | doesn't mean that your WM has the required kludges in place.</p> |
|
|
344 | <p>4. Use xcompmgr and let it do the job:</p> |
|
|
345 | <pre> |
|
|
346 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
347 | -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre> |
|
|
348 | <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 |
|
|
350 | your server crashes, you got to keep the pieces.</p> |
306 | <pre> |
351 | <p> |
|
|
352 | </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> |
|
|
354 | <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, |
|
|
356 | 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 |
|
|
358 | display. Subsequent japanese characters will use that font. Now, many |
|
|
359 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
360 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
361 | -- unfortunately at this point, it will still use the japanese font for |
|
|
362 | chinese characters that are also in the japanese font.</p> |
|
|
363 | <p>The workaround is easy: just tag a chinese font at the end of your font |
|
|
364 | list (see the previous question). The key is to view the font list as |
|
|
365 | a preference list: If you expect more japanese, list a japanese font |
|
|
366 | first. If you expect more chinese, put a chinese font first.</p> |
|
|
367 | <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 |
|
|
369 | fonts for the same character at the same time, but no interface for this |
|
|
370 | 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> |
|
|
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 | rxvt -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> |
|
|
549 | </p> |
|
|
550 | <h2><a name="keyboard__mouse___user_interaction">Keyboard, Mouse & User Interaction</a></h2> |
|
|
551 | <p> |
|
|
552 | </p> |
|
|
553 | <h3><a name="the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></h3> |
|
|
554 | <p>If you want to select e.g. alphanumeric words, you can use the following |
|
|
555 | setting:</p> |
|
|
556 | <pre> |
|
|
557 | URxvt.selection.pattern-0: ([[:word:]]+)</pre> |
|
|
558 | <p>If you click more than twice, the selection will be extended |
|
|
559 | more and more.</p> |
|
|
560 | <p>To get a selection that is very similar to the old code, try this pattern:</p> |
|
|
561 | <pre> |
|
|
562 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)</pre> |
|
|
563 | <p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also |
|
|
564 | selects words like the old code.</p> |
|
|
565 | <p> |
|
|
566 | </p> |
|
|
567 | <h3><a name="i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></h3> |
|
|
568 | <p>You can disable the perl extension completely by setting the |
|
|
569 | <strong>perl-ext-common</strong> resource to the empty string, which also keeps |
|
|
570 | rxvt-unicode from initialising perl, saving memory.</p> |
|
|
571 | <p>If you only want to disable specific features, you first have to |
|
|
572 | identify which perl extension is responsible. For this, read the section |
|
|
573 | <strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For |
|
|
574 | example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify |
|
|
575 | this <strong>perl-ext-common</strong> resource:</p> |
|
|
576 | <pre> |
|
|
577 | URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre> |
|
|
578 | <p>This will keep the default extensions, but disable the two popup |
|
|
579 | extensions. Some extensions can also be configured, for example, |
|
|
580 | scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any |
|
|
581 | other combination either by setting the <strong>searchable-scrollback</strong> resource:</p> |
|
|
582 | <pre> |
|
|
583 | URxvt.searchable-scrollback: CM-s</pre> |
|
|
584 | <p> |
|
|
585 | </p> |
|
|
586 | <h3><a name="the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></h3> |
|
|
587 | <p>See next entry.</p> |
|
|
588 | <p> |
|
|
589 | </p> |
|
|
590 | <h3><a name="during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></h3> |
|
|
591 | <p>These are caused by the <code>readline</code> perl extension. Under normal |
|
|
592 | circumstances, it will move your cursor around when you click into the |
|
|
593 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
594 | but when running a program that doesn't parse cursor movements or in some |
|
|
595 | cases during rlogin sessions, it fails to detect this properly.</p> |
|
|
596 | <p>You can permamently switch this feature off by disabling the <code>readline</code> |
|
|
597 | extension:</p> |
|
|
598 | <pre> |
307 | URxvt.perl-ext-common: default,tabbed</pre> |
599 | URxvt.perl-ext-common: default,-readline</pre> |
308 | <p>It will also work fine with tabbing functionality of many window managers |
|
|
309 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
310 | embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or |
|
|
311 | the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt |
|
|
312 | (murxvt) terminal as an example embedding application.</p> |
|
|
313 | <p> |
|
|
314 | </p> |
600 | <p> |
315 | <h2><a name="how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></h2> |
|
|
316 | <p>The version number is displayed with the usage (-h). Also the escape |
|
|
317 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. When |
|
|
318 | using the rxvtc client, the version displayed is that of the |
|
|
319 | daemon.</p> |
|
|
320 | <p> |
601 | </p> |
|
|
602 | <h3><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h3> |
|
|
603 | <p>Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
604 | specific details were reported so far. It is possible that this is caused |
|
|
605 | by the wrong <code>TERM</code> setting, although the details of wether and how |
|
|
606 | this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible |
|
|
607 | keymap. See the answer to the previous question, and please report if that |
|
|
608 | helped.</p> |
321 | </p> |
609 | <p> |
322 | <h2><a name="i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></h2> |
|
|
323 | <p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
324 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
325 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
326 | the original rxvt-unicode author please download and install the genuine |
|
|
327 | version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce |
|
|
328 | the problem. If you cannot, chances are that the problems are specific to |
|
|
329 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
|
|
330 | Tracking System (use <code>reportbug</code> to report the bug).</p> |
|
|
331 | <p>For other problems that also affect the Debian package, you can and |
|
|
332 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
333 | bug in the Debian version and it serves as a reminder for other users that |
|
|
334 | might encounter the same issue.</p> |
|
|
335 | <p> |
610 | </p> |
|
|
611 | <h3><a name="my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></h3> |
|
|
612 | <p>The most common causes for this are that either your locale is not set |
|
|
613 | correctly, or you specified a <strong>preeditStyle</strong> that is not supported by |
|
|
614 | your input method. For example, if you specified <strong>OverTheSpot</strong> and |
|
|
615 | your input method (e.g. the default input method handling Compose keys) |
|
|
616 | does not support this (for instance because it is not visual), then |
|
|
617 | rxvt-unicode will continue without an input method.</p> |
|
|
618 | <p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than |
|
|
619 | one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p> |
336 | </p> |
620 | <p> |
337 | <h2><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h2> |
|
|
338 | <p>You should build one binary with the default options. <em>configure</em> |
|
|
339 | now enables most useful options, and the trend goes to making them |
|
|
340 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
|
|
341 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
342 | be enabled, as important functionality (menus, selection, likely more in |
|
|
343 | the future) depends on it.</p> |
|
|
344 | <p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources |
|
|
345 | system-wide (except maybe with <code>defaults</code>). This will result in useful |
|
|
346 | behaviour. If your distribution aims at low memory, add an empty |
|
|
347 | <code>perl-ext-common</code> resource to the app-defaults file. This will keep the |
|
|
348 | perl interpreter disabled until the user enables it.</p> |
|
|
349 | <p>If you can/want build more binaries, I recommend building a minimal |
|
|
350 | one with <code>--disable-everything</code> (very useful) and a maximal one with |
|
|
351 | <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of |
|
|
352 | encodings built-in that increase download times and are rarely used).</p> |
|
|
353 | <p> |
621 | </p> |
|
|
622 | <h3><a name="i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></h3> |
|
|
623 | <p>Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on |
|
|
624 | international keyboards) or simply use ISO 14755 support to your |
|
|
625 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
626 | codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape |
|
|
627 | character and so on.</p> |
354 | </p> |
628 | <p> |
355 | <h2><a name="i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></h2> |
|
|
356 | <p>It should be, starting with release 7.1. You are encouraged to properly |
|
|
357 | install urxvt with privileges necessary for your OS now.</p> |
|
|
358 | <p>When rxvt-unicode detects that it runs setuid or setgid, it will fork |
|
|
359 | into a helper process for privileged operations (pty handling on some |
|
|
360 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
|
|
361 | immediately. This is much safer than most other terminals that keep |
|
|
362 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
363 | things as perl interpreters, which might be ``helpful'' to attackers).</p> |
|
|
364 | <p>This forking is done as the very first within main(), which is very early |
|
|
365 | and reduces possible bugs to initialisation code run before main(), or |
|
|
366 | things like the dynamic loader of your system, which should result in very |
|
|
367 | little risk.</p> |
|
|
368 | <p> |
629 | </p> |
|
|
630 | <h3><a name="mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></h3> |
|
|
631 | <p>Make sure that mouse reporting is actually turned off since killing |
|
|
632 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
633 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
634 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
635 | depressed.</p> |
369 | </p> |
636 | <p> |
|
|
637 | </p> |
|
|
638 | <h3><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h3> |
|
|
639 | <p>Assuming that the physical Backspace key corresponds to the |
|
|
640 | BackSpace keysym (not likely for Linux ... see the following |
|
|
641 | question) there are two standard values that can be used for |
|
|
642 | Backspace: <code>^H</code> and <code>^?</code>.</p> |
|
|
643 | <p>Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
644 | policy of using <code>^?</code> when unsure, because it's the one only only correct |
|
|
645 | choice :).</p> |
|
|
646 | <p>Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
647 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
648 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
649 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
|
|
650 | be used (which may not be the same as your stty setting).</p> |
|
|
651 | <p>For starting a new rxvt-unicode:</p> |
|
|
652 | <pre> |
|
|
653 | # use Backspace = ^H |
|
|
654 | $ stty erase ^H |
|
|
655 | $ rxvt</pre> |
|
|
656 | <pre> |
|
|
657 | # use Backspace = ^? |
|
|
658 | $ stty erase ^? |
|
|
659 | $ rxvt</pre> |
|
|
660 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p> |
|
|
661 | <p>For an existing rxvt-unicode:</p> |
|
|
662 | <pre> |
|
|
663 | # use Backspace = ^H |
|
|
664 | $ stty erase ^H |
|
|
665 | $ echo -n "^[[36h"</pre> |
|
|
666 | <pre> |
|
|
667 | # use Backspace = ^? |
|
|
668 | $ stty erase ^? |
|
|
669 | $ echo -n "^[[36l"</pre> |
|
|
670 | <p>This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
671 | if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value |
|
|
672 | properly reflects that.</p> |
|
|
673 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
674 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
675 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
676 | (<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> |
|
|
677 | <p>Some other Backspace problems:</p> |
|
|
678 | <p>some editors use termcap/terminfo, |
|
|
679 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
680 | GNU Emacs (and Emacs-like editors) use ^H for help.</p> |
|
|
681 | <p>Perhaps someday this will all be resolved in a consistent manner.</p> |
|
|
682 | <p> |
|
|
683 | </p> |
|
|
684 | <h3><a name="i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></h3> |
|
|
685 | <p>There are some compile-time selections available via configure. Unless |
|
|
686 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
|
|
687 | use the `keysym' resource to alter the keystrings associated with keysyms.</p> |
|
|
688 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
|
|
689 | <pre> |
|
|
690 | URxvt.keysym.Home: \033[1~ |
|
|
691 | URxvt.keysym.End: \033[4~ |
|
|
692 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
693 | URxvt.keysym.C-slash: \033<C-/> |
|
|
694 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
695 | URxvt.keysym.C-grave: \033<C-`> |
|
|
696 | URxvt.keysym.C-comma: \033<C-,> |
|
|
697 | URxvt.keysym.C-period: \033<C-.> |
|
|
698 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
699 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
700 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
701 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
702 | URxvt.keysym.S-space: \033<S-Space> |
|
|
703 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
704 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
705 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
706 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
707 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
708 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
709 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> |
|
|
710 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
|
|
711 | <p> |
|
|
712 | </p> |
|
|
713 | <h3><a name="i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_map">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map</a></h3> |
|
|
714 | <pre> |
|
|
715 | KP_Insert == Insert |
|
|
716 | F22 == Print |
|
|
717 | F27 == Home |
|
|
718 | F29 == Prior |
|
|
719 | F33 == End |
|
|
720 | F35 == Next</pre> |
|
|
721 | <p>Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
722 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
723 | required for your particular machine.</p> |
|
|
724 | <p> |
|
|
725 | </p> |
|
|
726 | <h2><a name="terminal_configuration">Terminal Configuration</a></h2> |
|
|
727 | <p> |
|
|
728 | </p> |
|
|
729 | <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 |
|
|
731 | 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 |
|
|
733 | ignore any resource files in your home directory. It will only read |
|
|
734 | <em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p> |
|
|
735 | <p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that |
|
|
736 | resources are loaded into your X-server. In this case, you have to |
|
|
737 | re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p> |
|
|
738 | <p>Also consider the form resources have to use:</p> |
|
|
739 | <pre> |
|
|
740 | URxvt.resource: value</pre> |
|
|
741 | <p>If you want to use another form (there are lots of different ways of |
|
|
742 | specifying resources), make sure you understand wether and why it |
|
|
743 | works. If unsure, use the form above.</p> |
|
|
744 | <p> |
|
|
745 | </p> |
370 | <h2><a name="when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></h2> |
746 | <h3><a name="when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></h3> |
371 | <p>The terminal description used by rxvt-unicode is not as widely available |
747 | <p>The terminal description used by rxvt-unicode is not as widely available |
372 | as that for xterm, or even rxvt (for which the same problem often arises).</p> |
748 | as that for xterm, or even rxvt (for which the same problem often arises).</p> |
373 | <p>The correct solution for this problem is to install the terminfo, this can |
749 | <p>The correct solution for this problem is to install the terminfo, this can |
374 | be done like this (with ncurses' infocmp):</p> |
750 | be done like this (with ncurses' infocmp):</p> |
375 | <pre> |
751 | <pre> |
… | |
… | |
388 | URxvt.termName: rxvt</pre> |
764 | URxvt.termName: rxvt</pre> |
389 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
765 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
390 | the rxvt terminfo file with the rxvt-unicode one.</p> |
766 | the rxvt terminfo file with the rxvt-unicode one.</p> |
391 | <p> |
767 | <p> |
392 | </p> |
768 | </p> |
393 | <h2><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h2> |
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> |
394 | <p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
770 | <p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
395 | <code>enacs=\E[0@</code> and try again.</p> |
771 | <code>enacs=\E[0@</code> and try again.</p> |
396 | <p> |
772 | <p> |
397 | </p> |
773 | </p> |
398 | <h2><a name="bash_s_readline_does_not_work_correctly_under_rxvt_"><code>bash</code>'s readline does not work correctly under rxvt.</a></h2> |
774 | <h3><a name="bash_s_readline_does_not_work_correctly_under_rxvt_"><code>bash</code>'s readline does not work correctly under rxvt.</a></h3> |
399 | <p>See next entry.</p> |
775 | <p>See next entry.</p> |
400 | <p> |
776 | <p> |
401 | </p> |
777 | </p> |
402 | <h2><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h2> |
778 | <h3><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h3> |
403 | <p>One reason you might want this is that some distributions or operating |
779 | <p>One reason you might want this is that some distributions or operating |
404 | systems still compile some programs using the long-obsoleted termcap |
780 | systems still compile some programs using the long-obsoleted termcap |
405 | library (Fedora Core's bash is one example) and rely on a termcap entry |
781 | library (Fedora Core's bash is one example) and rely on a termcap entry |
406 | for <code>rxvt-unicode</code>.</p> |
782 | for <code>rxvt-unicode</code>.</p> |
407 | <p>You could use rxvt's termcap entry with resonable results in many cases. |
783 | <p>You could use rxvt's termcap entry with resonable results in many cases. |
… | |
… | |
431 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
807 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
432 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
808 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
433 | :vs=\E[?25h:</pre> |
809 | :vs=\E[?25h:</pre> |
434 | <p> |
810 | <p> |
435 | </p> |
811 | </p> |
436 | <h2><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h2> |
812 | <h3><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h3> |
437 | <p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to |
813 | <p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to |
438 | decide wether a terminal has colour, but uses it's own configuration |
814 | decide wether a terminal has colour, but uses it's own configuration |
439 | file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among |
815 | file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among |
440 | with most other terminals supporting colour). Either add:</p> |
816 | with most other terminals supporting colour). Either add:</p> |
441 | <pre> |
817 | <pre> |
… | |
… | |
444 | <pre> |
820 | <pre> |
445 | alias ls='ls --color=auto'</pre> |
821 | alias ls='ls --color=auto'</pre> |
446 | <p>to your <code>.profile</code> or <code>.bashrc</code>.</p> |
822 | <p>to your <code>.profile</code> or <code>.bashrc</code>.</p> |
447 | <p> |
823 | <p> |
448 | </p> |
824 | </p> |
449 | <h2><a name="why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></h2> |
825 | <h3><a name="why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></h3> |
450 | <p>See next entry.</p> |
826 | <p>See next entry.</p> |
451 | <p> |
827 | <p> |
452 | </p> |
828 | </p> |
453 | <h2><a name="why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></h2> |
829 | <h3><a name="why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></h3> |
454 | <p>See next entry.</p> |
830 | <p>See next entry.</p> |
455 | <p> |
831 | <p> |
456 | </p> |
832 | </p> |
457 | <h2><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h2> |
833 | <h3><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h3> |
458 | <p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged |
834 | <p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged |
459 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
835 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
460 | by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra |
836 | by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra |
461 | features. Unfortunately, some of these (most notably, again, Debian |
837 | features. Unfortunately, some of these (most notably, again, Debian |
462 | GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo |
838 | GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo |
463 | file, so you will need to install it on your own (See the question <strong>When |
839 | file, so you will need to install it on your own (See the question <strong>When |
464 | I log-in to another system it tells me about missing terminfo data?</strong> on |
840 | I log-in to another system it tells me about missing terminfo data?</strong> on |
465 | how to do this).</p> |
841 | how to do this).</p> |
466 | <p> |
842 | <p> |
467 | </p> |
843 | </p> |
468 | <h2><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h2> |
844 | <h2><a name="encoding___locale___input_method_issues">Encoding / Locale / Input Method Issues</a></h2> |
469 | <p>Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
470 | specific details were reported so far. It is possible that this is caused |
|
|
471 | by the wrong <code>TERM</code> setting, although the details of wether and how |
|
|
472 | this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible |
|
|
473 | keymap. See the answer to the previous question, and please report if that |
|
|
474 | helped.</p> |
|
|
475 | <p> |
|
|
476 | </p> |
845 | <p> |
|
|
846 | </p> |
477 | <h2><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h2> |
847 | <h3><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h3> |
478 | <p>See next entry.</p> |
848 | <p>See next entry.</p> |
479 | <p> |
849 | <p> |
480 | </p> |
850 | </p> |
481 | <h2><a name="unicode_does_not_seem_to_work">Unicode does not seem to work?</a></h2> |
851 | <h3><a name="unicode_does_not_seem_to_work">Unicode does not seem to work?</a></h3> |
482 | <p>If you encounter strange problems like typing an accented character but |
852 | <p>If you encounter strange problems like typing an accented character but |
483 | getting two unrelated other characters or similar, or if program output is |
853 | getting two unrelated other characters or similar, or if program output is |
484 | subtly garbled, then you should check your locale settings.</p> |
854 | subtly garbled, then you should check your locale settings.</p> |
485 | <p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the |
855 | <p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the |
486 | programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the |
856 | programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the |
… | |
… | |
501 | <p>If nothing works and you are sure that everything is set correctly then |
871 | <p>If nothing works and you are sure that everything is set correctly then |
502 | you will need to remember a little known fact: Some programs just don't |
872 | you will need to remember a little known fact: Some programs just don't |
503 | support locales :(</p> |
873 | support locales :(</p> |
504 | <p> |
874 | <p> |
505 | </p> |
875 | </p> |
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> |
876 | <h3><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h3> |
507 | <p>See next entry.</p> |
877 | <p>See next entry.</p> |
508 | <p> |
878 | <p> |
509 | </p> |
879 | </p> |
510 | <h2><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h2> |
|
|
511 | <p>Most fonts do not contain the full range of Unicode, which is |
|
|
512 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
513 | your system/os) have specified does not cover all the characters you want |
|
|
514 | to display.</p> |
|
|
515 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
|
|
516 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
517 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
518 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
519 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
520 | the font that the characters it claims to contain indeed look correct.</p> |
|
|
521 | <p>In that case, select a font of your taste and add it to the font list, |
|
|
522 | e.g.:</p> |
|
|
523 | <pre> |
|
|
524 | rxvt -fn basefont,font2,font3...</pre> |
|
|
525 | <p>When rxvt-unicode sees a character, it will first look at the base |
|
|
526 | font. If the base font does not contain the character, it will go to the |
|
|
527 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
528 | search and use less resources within rxvt-unicode and the X-server.</p> |
|
|
529 | <p>The only limitation is that none of the fonts may be larger than the base |
|
|
530 | font, as the base font defines the terminal character cell size, which |
|
|
531 | must be the same due to the way terminals work.</p> |
|
|
532 | <p> |
|
|
533 | </p> |
|
|
534 | <h2><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h2> |
|
|
535 | <p>This is because there is a difference between script and language -- |
|
|
536 | rxvt-unicode does not know which language the text that is output is, |
|
|
537 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
538 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
539 | display. Subsequent japanese characters will use that font. Now, many |
|
|
540 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
541 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
542 | -- unfortunately at this point, it will still use the japanese font for |
|
|
543 | chinese characters that are also in the japanese font.</p> |
|
|
544 | <p>The workaround is easy: just tag a chinese font at the end of your font |
|
|
545 | list (see the previous question). The key is to view the font list as |
|
|
546 | a preference list: If you expect more japanese, list a japanese font |
|
|
547 | first. If you expect more chinese, put a chinese font first.</p> |
|
|
548 | <p>In the future it might be possible to switch language preferences at |
|
|
549 | runtime (the internal data structure has no problem with using different |
|
|
550 | fonts for the same character at the same time, but no interface for this |
|
|
551 | has been designed yet).</p> |
|
|
552 | <p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p> |
|
|
553 | <p> |
|
|
554 | </p> |
|
|
555 | <h2><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h2> |
|
|
556 | <p>Most fonts were not designed for terminal use, which means that character |
|
|
557 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
558 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
559 | these characters. For characters that are just ``a bit'' too wide a special |
|
|
560 | ``careful'' rendering mode is used that redraws adjacent characters.</p> |
|
|
561 | <p>All of this requires that fonts do not lie about character sizes, |
|
|
562 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
563 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
564 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
565 | cases).</p> |
|
|
566 | <p>It's not clear (to me at least), wether this is a bug in Xft, freetype, |
|
|
567 | or the respective font. If you encounter this problem you might try using |
|
|
568 | the <code>-lsp</code> option to give the font more height. If that doesn't work, you |
|
|
569 | might be forced to use a different font.</p> |
|
|
570 | <p>All of this is not a problem when using X11 core fonts, as their bounding |
|
|
571 | box data is correct.</p> |
|
|
572 | <p> |
|
|
573 | </p> |
|
|
574 | <h2><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h2> |
|
|
575 | <p>Seems to be a known bug, read |
|
|
576 | <a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the |
|
|
577 | following ugly workaround to get non-double-wide-characters working:</p> |
|
|
578 | <pre> |
|
|
579 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)</pre> |
|
|
580 | <p> |
|
|
581 | </p> |
|
|
582 | <h2><a name="my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></h2> |
|
|
583 | <p>The most common causes for this are that either your locale is not set |
|
|
584 | correctly, or you specified a <strong>preeditStyle</strong> that is not supported by |
|
|
585 | your input method. For example, if you specified <strong>OverTheSpot</strong> and |
|
|
586 | your input method (e.g. the default input method handling Compose keys) |
|
|
587 | does not support this (for instance because it is not visual), then |
|
|
588 | rxvt-unicode will continue without an input method.</p> |
|
|
589 | <p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than |
|
|
590 | one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p> |
|
|
591 | <p> |
|
|
592 | </p> |
|
|
593 | <h2><a name="i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></h2> |
|
|
594 | <p>Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on |
|
|
595 | international keyboards) or simply use ISO 14755 support to your |
|
|
596 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
597 | codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape |
|
|
598 | character and so on.</p> |
|
|
599 | <p> |
|
|
600 | </p> |
|
|
601 | <h2><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h2> |
|
|
602 | <p>First of all, make sure you are running with the right terminal settings |
|
|
603 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
|
|
604 | make sure you have specified colours for italic and bold, as otherwise |
|
|
605 | rxvt-unicode might use reverse video to simulate the effect:</p> |
|
|
606 | <pre> |
|
|
607 | URxvt.colorBD: white |
|
|
608 | URxvt.colorIT: green</pre> |
|
|
609 | <p> |
|
|
610 | </p> |
|
|
611 | <h2><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h2> |
|
|
612 | <p>For some unexplainable reason, some rare programs assume a very weird |
|
|
613 | colour palette when confronted with a terminal with more than the standard |
|
|
614 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
|
|
615 | these programs not to assume non-ISO colours without very good reasons.</p> |
|
|
616 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
|
|
617 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
|
|
618 | fix colours but keep you from using other rxvt-unicode features.</p> |
|
|
619 | <p> |
|
|
620 | </p> |
|
|
621 | <h2><a name="i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></h2> |
|
|
622 | <p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined |
|
|
623 | in your compile environment, or an implementation that implements it, |
|
|
624 | wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that |
|
|
625 | <strong>wchar_t</strong> is represented as unicode.</p> |
|
|
626 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
|
|
627 | does it support it. Instead, it uses it's own internal representation of |
|
|
628 | <strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> |
|
|
629 | <p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and |
|
|
630 | <code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> |
|
|
631 | <p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language |
|
|
632 | apps in an OS, as using a locale-dependent (and non-standardized) |
|
|
633 | representation of <strong>wchar_t</strong> makes it impossible to convert between |
|
|
634 | <strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding |
|
|
635 | without implementing OS-specific-wrappers for each and every locale. There |
|
|
636 | simply are no APIs to convert <strong>wchar_t</strong> into anything except the current |
|
|
637 | locale encoding.</p> |
|
|
638 | <p>Some applications (such as the formidable <strong>mlterm</strong>) work around this |
|
|
639 | by carrying their own replacement functions for character set handling |
|
|
640 | with them, and either implementing OS-dependent hacks or doing multiple |
|
|
641 | conversions (which is slow and unreliable in case the OS implements |
|
|
642 | encodings slightly different than the terminal emulator).</p> |
|
|
643 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
|
|
644 | system libraries once and for all, instead of forcing every app to carry |
|
|
645 | complete replacements for them :)</p> |
|
|
646 | <p> |
|
|
647 | </p> |
|
|
648 | <h2><a name="i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></h2> |
|
|
649 | <p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst |
|
|
650 | problems with <code>wcwidth</code> and a compile problem.</p> |
|
|
651 | <p> |
|
|
652 | </p> |
|
|
653 | <h2><a name="how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></h2> |
|
|
654 | <p>rxvt-unicode should compile and run out of the box on cygwin, using |
|
|
655 | the X11 libraries that come with cygwin. libW11 emulation is no |
|
|
656 | longer supported (and makes no sense, either, as it only supported a |
|
|
657 | single font). I recommend starting the X-server in <code>-multiwindow</code> or |
|
|
658 | <code>-rootless</code> mode instead, which will result in similar look&feel as the |
|
|
659 | old libW11 emulation.</p> |
|
|
660 | <p>At the time of this writing, cygwin didn't seem to support any multi-byte |
|
|
661 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
|
|
662 | to 8-bit encodings.</p> |
|
|
663 | <p> |
|
|
664 | </p> |
|
|
665 | <h2><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h2> |
|
|
666 | <p>See next entry.</p> |
|
|
667 | <p> |
|
|
668 | </p> |
|
|
669 | <h2><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h2> |
880 | <h3><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h3> |
670 | <p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
881 | <p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
671 | specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about |
882 | specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about |
672 | UTF-8 or any other encodings with respect to terminal I/O.</p> |
883 | UTF-8 or any other encodings with respect to terminal I/O.</p> |
673 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
884 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
674 | the encoding, doing I/O and (most important) communicating this to all |
885 | the encoding, doing I/O and (most important) communicating this to all |
… | |
… | |
693 | rxvt-unicode.</p> |
904 | rxvt-unicode.</p> |
694 | <p>If you want to use a specific encoding you have to make sure you start |
905 | <p>If you want to use a specific encoding you have to make sure you start |
695 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
906 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
696 | <p> |
907 | <p> |
697 | </p> |
908 | </p> |
698 | <h2><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h2> |
909 | <h3><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h3> |
699 | <p>Yes, using an escape sequence. Try something like this, which sets |
910 | <p>Yes, using an escape sequence. Try something like this, which sets |
700 | rxvt-unicode's idea of <code>LC_CTYPE</code>.</p> |
911 | rxvt-unicode's idea of <code>LC_CTYPE</code>.</p> |
701 | <pre> |
912 | <pre> |
702 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
913 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
703 | <p>See also the previous answer.</p> |
914 | <p>See also the previous answer.</p> |
… | |
… | |
712 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
923 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
713 | for some locales where character width differs between program- and |
924 | for some locales where character width differs between program- and |
714 | rxvt-unicode-locales.</p> |
925 | rxvt-unicode-locales.</p> |
715 | <p> |
926 | <p> |
716 | </p> |
927 | </p> |
717 | <h2><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h2> |
|
|
718 | <p>Yes, using an escape sequence. Try something like this, which has the same |
|
|
719 | effect as using the <code>-fn</code> switch, and takes effect immediately:</p> |
|
|
720 | <pre> |
|
|
721 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
|
|
722 | <p>This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
723 | japanese font), but you have to switch to chinese temporarily, where |
|
|
724 | japanese fonts would only be in your way.</p> |
|
|
725 | <p>You can think of this as a kind of manual ISO-2022 switching.</p> |
|
|
726 | <p> |
|
|
727 | </p> |
|
|
728 | <h2><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h2> |
|
|
729 | <p>Many fonts have difficulties with italic characters and hinting. For |
|
|
730 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
|
|
731 | Mono</code> completely fails in it's italic face. A workaround might be to |
|
|
732 | enable freetype autohinting, i.e. like this:</p> |
|
|
733 | <pre> |
|
|
734 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
735 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
|
|
736 | <p> |
|
|
737 | </p> |
|
|
738 | <h2><a name="my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants <some encoding> but I want UTF-8, what can I do?</a></h2> |
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> |
739 | <p>You can specify separate locales for the input method and the rest of the |
929 | <p>You can specify separate locales for the input method and the rest of the |
740 | terminal, using the resource <code>imlocale</code>:</p> |
930 | terminal, using the resource <code>imlocale</code>:</p> |
741 | <pre> |
931 | <pre> |
742 | URxvt.imlocale: ja_JP.EUC-JP</pre> |
932 | URxvt.imlocale: ja_JP.EUC-JP</pre> |
743 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
933 | <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still |
744 | use your input method. Please note, however, that you will not be able to |
934 | use your input method. Please note, however, that you will not be able to |
745 | input characters outside <code>EUC-JP</code> in a normal way then, as your input |
935 | input characters outside <code>EUC-JP</code> in a normal way then, as your input |
746 | method limits you.</p> |
936 | method limits you.</p> |
747 | <p> |
937 | <p> |
748 | </p> |
938 | </p> |
749 | <h2><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h2> |
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> |
750 | <p>Unfortunately, this is unavoidable, as the XIM protocol is racy by |
940 | <p>Unfortunately, this is unavoidable, as the XIM protocol is racy by |
751 | design. Applications can avoid some crashes at the expense of memory |
941 | design. Applications can avoid some crashes at the expense of memory |
752 | leaks, and Input Methods can avoid some crashes by careful ordering at |
942 | leaks, and Input Methods can avoid some crashes by careful ordering at |
753 | exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds, |
943 | exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds, |
754 | while <strong>SCIM</strong> (or similar input methods) fails. In the end, however, |
944 | while <strong>SCIM</strong> (or similar input methods) fails. In the end, however, |
755 | crashes cannot be completely avoided even if both sides cooperate.</p> |
945 | crashes cannot be completely avoided even if both sides cooperate.</p> |
756 | <p>So the only workaround is not to kill your Input Method Servers.</p> |
946 | <p>So the only workaround is not to kill your Input Method Servers.</p> |
757 | <p> |
947 | <p> |
758 | </p> |
948 | </p> |
759 | <h2><a name="rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></h2> |
949 | <h2><a name="operating_systems___package_maintaining">Operating Systems / Package Maintaining</a></h2> |
760 | <p>Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
761 | don't use. One thing you should try is to configure out all settings that |
|
|
762 | you don't need, for example, Xft support is a resource hog by design, |
|
|
763 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
764 | accidentally when rxvt-unicode tries to find a font for your characters.</p> |
|
|
765 | <p>Also, many people (me included) like large windows and even larger |
|
|
766 | scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use |
|
|
767 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
768 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
769 | use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as |
|
|
770 | rxvt-unicode then uses 8 bytes per screen cell.</p> |
|
|
771 | <p> |
|
|
772 | </p> |
950 | <p> |
773 | <h2><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h2> |
|
|
774 | <p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
775 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
776 | antialiasing (by appending <code>:antialias=false</code>), which saves lots of |
|
|
777 | memory and also speeds up rendering considerably.</p> |
|
|
778 | <p> |
951 | </p> |
|
|
952 | <h3><a name="i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></h3> |
|
|
953 | <p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
954 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
955 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
956 | the original rxvt-unicode author please download and install the genuine |
|
|
957 | version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce |
|
|
958 | the problem. If you cannot, chances are that the problems are specific to |
|
|
959 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
|
|
960 | Tracking System (use <code>reportbug</code> to report the bug).</p> |
|
|
961 | <p>For other problems that also affect the Debian package, you can and |
|
|
962 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
963 | bug in the Debian version and it serves as a reminder for other users that |
|
|
964 | might encounter the same issue.</p> |
779 | </p> |
965 | <p> |
780 | <h2><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h2> |
|
|
781 | <p>Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
782 | fall back to it's default font search list it will prefer X11 core |
|
|
783 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
784 | antialiasing disabled for most of them, because the author thinks they |
|
|
785 | look best that way.</p> |
|
|
786 | <p>If you want antialiasing, you have to specify the fonts manually.</p> |
|
|
787 | <p> |
966 | </p> |
|
|
967 | <h3><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h3> |
|
|
968 | <p>You should build one binary with the default options. <em>configure</em> |
|
|
969 | now enables most useful options, and the trend goes to making them |
|
|
970 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
|
|
971 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
972 | be enabled, as important functionality (menus, selection, likely more in |
|
|
973 | the future) depends on it.</p> |
|
|
974 | <p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources |
|
|
975 | system-wide (except maybe with <code>defaults</code>). This will result in useful |
|
|
976 | behaviour. If your distribution aims at low memory, add an empty |
|
|
977 | <code>perl-ext-common</code> resource to the app-defaults file. This will keep the |
|
|
978 | perl interpreter disabled until the user enables it.</p> |
|
|
979 | <p>If you can/want build more binaries, I recommend building a minimal |
|
|
980 | one with <code>--disable-everything</code> (very useful) and a maximal one with |
|
|
981 | <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of |
|
|
982 | encodings built-in that increase download times and are rarely used).</p> |
788 | </p> |
983 | <p> |
789 | <h2><a name="mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></h2> |
|
|
790 | <p>Make sure that mouse reporting is actually turned off since killing |
|
|
791 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
792 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
793 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
794 | depressed.</p> |
|
|
795 | <p> |
984 | </p> |
|
|
985 | <h3><a name="i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></h3> |
|
|
986 | <p>It should be, starting with release 7.1. You are encouraged to properly |
|
|
987 | install urxvt with privileges necessary for your OS now.</p> |
|
|
988 | <p>When rxvt-unicode detects that it runs setuid or setgid, it will fork |
|
|
989 | into a helper process for privileged operations (pty handling on some |
|
|
990 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
|
|
991 | immediately. This is much safer than most other terminals that keep |
|
|
992 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
993 | things as perl interpreters, which might be ``helpful'' to attackers).</p> |
|
|
994 | <p>This forking is done as the very first within main(), which is very early |
|
|
995 | and reduces possible bugs to initialisation code run before main(), or |
|
|
996 | things like the dynamic loader of your system, which should result in very |
|
|
997 | little risk.</p> |
796 | </p> |
998 | <p> |
797 | <h2><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h2> |
|
|
798 | <p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the |
|
|
799 | standard foreground colour.</p> |
|
|
800 | <p>For the standard background colour, blinking will actually make the |
|
|
801 | text blink when compiled with <code>--enable-blinking</code>. with standard |
|
|
802 | colours. Without <code>--enable-blinking</code>, the blink attribute will be |
|
|
803 | ignored.</p> |
|
|
804 | <p>On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
805 | foreground/background colors.</p> |
|
|
806 | <p>color0-7 are the low-intensity colors.</p> |
|
|
807 | <p>color8-15 are the corresponding high-intensity colors.</p> |
|
|
808 | <p> |
999 | </p> |
|
|
1000 | <h3><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h3> |
|
|
1001 | <p>Seems to be a known bug, read |
|
|
1002 | <a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the |
|
|
1003 | following ugly workaround to get non-double-wide-characters working:</p> |
|
|
1004 | <pre> |
|
|
1005 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)</pre> |
809 | </p> |
1006 | <p> |
810 | <h2><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></h2> |
|
|
811 | <p>You can change the screen colors at run-time using <em>~/.Xdefaults</em> |
|
|
812 | resources (or as long-options).</p> |
|
|
813 | <p>Here are values that are supposed to resemble a VGA screen, |
|
|
814 | including the murky brown that passes for low-intensity yellow:</p> |
|
|
815 | <pre> |
|
|
816 | URxvt.color0: #000000 |
|
|
817 | URxvt.color1: #A80000 |
|
|
818 | URxvt.color2: #00A800 |
|
|
819 | URxvt.color3: #A8A800 |
|
|
820 | URxvt.color4: #0000A8 |
|
|
821 | URxvt.color5: #A800A8 |
|
|
822 | URxvt.color6: #00A8A8 |
|
|
823 | URxvt.color7: #A8A8A8</pre> |
|
|
824 | <pre> |
|
|
825 | URxvt.color8: #000054 |
|
|
826 | URxvt.color9: #FF0054 |
|
|
827 | URxvt.color10: #00FF54 |
|
|
828 | URxvt.color11: #FFFF54 |
|
|
829 | URxvt.color12: #0000FF |
|
|
830 | URxvt.color13: #FF00FF |
|
|
831 | URxvt.color14: #00FFFF |
|
|
832 | URxvt.color15: #FFFFFF</pre> |
|
|
833 | <p>And here is a more complete set of non-standard colors described (not by |
|
|
834 | me) as ``pretty girly''.</p> |
|
|
835 | <pre> |
|
|
836 | URxvt.cursorColor: #dc74d1 |
|
|
837 | URxvt.pointerColor: #dc74d1 |
|
|
838 | URxvt.background: #0e0e0e |
|
|
839 | URxvt.foreground: #4ad5e1 |
|
|
840 | URxvt.color0: #000000 |
|
|
841 | URxvt.color8: #8b8f93 |
|
|
842 | URxvt.color1: #dc74d1 |
|
|
843 | URxvt.color9: #dc74d1 |
|
|
844 | URxvt.color2: #0eb8c7 |
|
|
845 | URxvt.color10: #0eb8c7 |
|
|
846 | URxvt.color3: #dfe37e |
|
|
847 | URxvt.color11: #dfe37e |
|
|
848 | URxvt.color5: #9e88f0 |
|
|
849 | URxvt.color13: #9e88f0 |
|
|
850 | URxvt.color6: #73f7ff |
|
|
851 | URxvt.color14: #73f7ff |
|
|
852 | URxvt.color7: #e1dddd |
|
|
853 | URxvt.color15: #e1dddd</pre> |
|
|
854 | <p> |
1007 | </p> |
|
|
1008 | <h3><a name="i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></h3> |
|
|
1009 | <p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined |
|
|
1010 | in your compile environment, or an implementation that implements it, |
|
|
1011 | wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that |
|
|
1012 | <strong>wchar_t</strong> is represented as unicode.</p> |
|
|
1013 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
|
|
1014 | does it support it. Instead, it uses it's own internal representation of |
|
|
1015 | <strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> |
|
|
1016 | <p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and |
|
|
1017 | <code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> |
|
|
1018 | <p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language |
|
|
1019 | apps in an OS, as using a locale-dependent (and non-standardized) |
|
|
1020 | representation of <strong>wchar_t</strong> makes it impossible to convert between |
|
|
1021 | <strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding |
|
|
1022 | without implementing OS-specific-wrappers for each and every locale. There |
|
|
1023 | simply are no APIs to convert <strong>wchar_t</strong> into anything except the current |
|
|
1024 | locale encoding.</p> |
|
|
1025 | <p>Some applications (such as the formidable <strong>mlterm</strong>) work around this |
|
|
1026 | by carrying their own replacement functions for character set handling |
|
|
1027 | with them, and either implementing OS-dependent hacks or doing multiple |
|
|
1028 | conversions (which is slow and unreliable in case the OS implements |
|
|
1029 | encodings slightly different than the terminal emulator).</p> |
|
|
1030 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
|
|
1031 | system libraries once and for all, instead of forcing every app to carry |
|
|
1032 | complete replacements for them :)</p> |
855 | </p> |
1033 | <p> |
856 | <h2><a name="how_can_i_start_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</a></h2> |
|
|
857 | <p>Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
|
|
858 | display, create the listening socket and then fork.</p> |
|
|
859 | <p> |
1034 | </p> |
|
|
1035 | <h3><a name="i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></h3> |
|
|
1036 | <p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst |
|
|
1037 | problems with <code>wcwidth</code> and a compile problem.</p> |
860 | </p> |
1038 | <p> |
861 | <h2><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h2> |
|
|
862 | <p>Assuming that the physical Backspace key corresponds to the |
|
|
863 | BackSpace keysym (not likely for Linux ... see the following |
|
|
864 | question) there are two standard values that can be used for |
|
|
865 | Backspace: <code>^H</code> and <code>^?</code>.</p> |
|
|
866 | <p>Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
867 | policy of using <code>^?</code> when unsure, because it's the one only only correct |
|
|
868 | choice :).</p> |
|
|
869 | <p>Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
870 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
871 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
872 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
|
|
873 | be used (which may not be the same as your stty setting).</p> |
|
|
874 | <p>For starting a new rxvt-unicode:</p> |
|
|
875 | <pre> |
|
|
876 | # use Backspace = ^H |
|
|
877 | $ stty erase ^H |
|
|
878 | $ rxvt</pre> |
|
|
879 | <pre> |
|
|
880 | # use Backspace = ^? |
|
|
881 | $ stty erase ^? |
|
|
882 | $ rxvt</pre> |
|
|
883 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p> |
|
|
884 | <p>For an existing rxvt-unicode:</p> |
|
|
885 | <pre> |
|
|
886 | # use Backspace = ^H |
|
|
887 | $ stty erase ^H |
|
|
888 | $ echo -n "^[[36h"</pre> |
|
|
889 | <pre> |
|
|
890 | # use Backspace = ^? |
|
|
891 | $ stty erase ^? |
|
|
892 | $ echo -n "^[[36l"</pre> |
|
|
893 | <p>This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
894 | if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value |
|
|
895 | properly reflects that.</p> |
|
|
896 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
897 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
898 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
899 | (<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> |
|
|
900 | <p>Some other Backspace problems:</p> |
|
|
901 | <p>some editors use termcap/terminfo, |
|
|
902 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
903 | GNU Emacs (and Emacs-like editors) use ^H for help.</p> |
|
|
904 | <p>Perhaps someday this will all be resolved in a consistent manner.</p> |
|
|
905 | <p> |
1039 | </p> |
906 | </p> |
1040 | <h3><a name="how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></h3> |
907 | <h2><a name="i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></h2> |
1041 | <p>rxvt-unicode should compile and run out of the box on cygwin, using |
908 | <p>There are some compile-time selections available via configure. Unless |
1042 | the X11 libraries that come with cygwin. libW11 emulation is no |
909 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
1043 | longer supported (and makes no sense, either, as it only supported a |
910 | use the `keysym' resource to alter the keystrings associated with keysyms.</p> |
1044 | single font). I recommend starting the X-server in <code>-multiwindow</code> or |
911 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
1045 | <code>-rootless</code> mode instead, which will result in similar look&feel as the |
912 | <pre> |
1046 | old libW11 emulation.</p> |
913 | URxvt.keysym.Home: \033[1~ |
1047 | <p>At the time of this writing, cygwin didn't seem to support any multi-byte |
914 | URxvt.keysym.End: \033[4~ |
1048 | encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited |
915 | URxvt.keysym.C-apostrophe: \033<C-'> |
1049 | to 8-bit encodings.</p> |
916 | URxvt.keysym.C-slash: \033<C-/> |
|
|
917 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
918 | URxvt.keysym.C-grave: \033<C-`> |
|
|
919 | URxvt.keysym.C-comma: \033<C-,> |
|
|
920 | URxvt.keysym.C-period: \033<C-.> |
|
|
921 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
922 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
923 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
924 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
925 | URxvt.keysym.S-space: \033<S-Space> |
|
|
926 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
927 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
928 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
929 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
930 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
931 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
932 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> |
|
|
933 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
|
|
934 | <p> |
|
|
935 | </p> |
|
|
936 | <h2><a name="i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_mappings_that_rxvtunicode_doesn_t_recognize_">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize.</a></h2> |
|
|
937 | <pre> |
|
|
938 | KP_Insert == Insert |
|
|
939 | F22 == Print |
|
|
940 | F27 == Home |
|
|
941 | F29 == Prior |
|
|
942 | F33 == End |
|
|
943 | F35 == Next</pre> |
|
|
944 | <p>Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
945 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
946 | required for your particular machine.</p> |
|
|
947 | <p> |
|
|
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? I need this to decide about setting colors etc.</a></h2> |
|
|
950 | <p>rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
|
|
951 | check and see if that is set. Note that several programs, JED, slrn, |
|
|
952 | Midnight Commander automatically check this variable to decide whether or |
|
|
953 | not to use color.</p> |
|
|
954 | <p> |
|
|
955 | </p> |
|
|
956 | <h2><a name="how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></h2> |
|
|
957 | <p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
|
|
958 | insecure mode then it is possible to use the following shell script |
|
|
959 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
960 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
|
|
961 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
962 | regular xterm.</p> |
|
|
963 | <p>Courtesy of Chuck Blake <<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>> with the following shell script |
|
|
964 | snippets:</p> |
|
|
965 | <pre> |
|
|
966 | # Bourne/Korn/POSIX family of shells: |
|
|
967 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
968 | if [ ${TERM:-foo} = xterm ]; then |
|
|
969 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
970 | echo -n '^[Z' |
|
|
971 | read term_id |
|
|
972 | stty icanon echo |
|
|
973 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
974 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
975 | read DISPLAY # set it in our local shell |
|
|
976 | fi |
|
|
977 | fi</pre> |
|
|
978 | <p> |
|
|
979 | </p> |
|
|
980 | <h2><a name="how_do_i_compile_the_manual_pages_for_myself">How do I compile the manual pages for myself?</a></h2> |
|
|
981 | <p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>, |
|
|
982 | one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to |
|
|
983 | the doc subdirectory and enter <code>make alldoc</code>.</p> |
|
|
984 | <p> |
|
|
985 | </p> |
|
|
986 | <h2><a name="my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></h2> |
|
|
987 | <p>Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>, |
|
|
988 | channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be |
|
|
989 | interested in learning about new and exciting problems (but not FAQs :).</p> |
|
|
990 | <p> |
1050 | <p> |
991 | </p> |
1051 | </p> |
992 | <hr /> |
1052 | <hr /> |
993 | <h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> |
1053 | <h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> |
994 | <p> |
1054 | <p> |
… | |
… | |
2366 | <p></p> |
2426 | <p></p> |
2367 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dincludes_3ddir">--with-xpm-includes=DIR</a></strong><br /> |
2427 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dincludes_3ddir">--with-xpm-includes=DIR</a></strong><br /> |
2368 | </dt> |
2428 | </dt> |
2369 | <dd> |
2429 | <dd> |
2370 | Look for the XPM includes in DIR. |
2430 | Look for the XPM includes in DIR. |
|
|
2431 | |
|
|
2432 | |
2371 | </dd> |
2433 | </dd> |
2372 | <p></p> |
2434 | <p></p> |
2373 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br /> |
2435 | <dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br /> |
2374 | </dt> |
2436 | </dt> |
2375 | <dd> |
2437 | <dd> |
2376 | Look for the XPM library in DIR. |
2438 | Look for the XPM library in DIR. |
|
|
2439 | |
|
|
2440 | |
2377 | </dd> |
2441 | </dd> |
2378 | <p></p> |
2442 | <p></p> |
2379 | <dt><strong><a name="item__2d_2dwith_2dxpm">--with-xpm</a></strong><br /> |
2443 | <dt><strong><a name="item__2d_2dwith_2dxpm">--with-xpm</a></strong><br /> |
2380 | </dt> |
2444 | </dt> |
2381 | <dd> |
2445 | <dd> |
2382 | Not needed - define via --enable-xpm-background. |
2446 | Not needed - define via --enable-xpm-background. |
|
|
2447 | |
|
|
2448 | |
2383 | </dd> |
2449 | </dd> |
2384 | <p></p></dl> |
2450 | <p></p></dl> |
2385 | <p> |
2451 | <p> |
2386 | </p> |
2452 | </p> |
2387 | <hr /> |
2453 | <hr /> |
2388 | <h1><a name="authors">AUTHORS</a></h1> |
2454 | <h1><a name="authors">AUTHORS</a></h1> |
2389 | <p>Marc Lehmann <<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>> converted this document to pod and |
2455 | <p>Marc Lehmann <<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>> converted this document to pod and |
2390 | reworked it from the original Rxvt documentation, which was done by Geoff |
2456 | reworked it from the original Rxvt documentation, which was done by Geoff |
2391 | Wing <<a href="mailto:gcw@pobox.com">gcw@pobox.com</a>>, who in turn used the XTerm documentation and other |
2457 | Wing <<a href="mailto:gcw@pobox.com">gcw@pobox.com</a>>, who in turn used the XTerm documentation and other |
2392 | sources.</p> |
2458 | sources. |
|
|
2459 | |
|
|
2460 | </p> |
2393 | |
2461 | |
2394 | </body> |
2462 | </body> |
2395 | |
2463 | |
2396 | </html> |
2464 | </html> |