… | |
… | |
24 | <li><a href="#my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></li> |
24 | <li><a href="#my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></li> |
25 | <li><a href="#does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></li> |
25 | <li><a href="#does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></li> |
26 | <li><a href="#how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></li> |
26 | <li><a href="#how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></li> |
27 | <li><a href="#rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></li> |
27 | <li><a href="#rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></li> |
28 | <li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li> |
28 | <li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li> |
|
|
29 | <li><a href="#how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></li> |
29 | <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li> |
30 | <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li> |
30 | <li><a href="#how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></li> |
31 | <li><a href="#how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></li> |
31 | <li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li> |
32 | <li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li> |
32 | <li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li> |
33 | <li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li> |
33 | <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li> |
34 | <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li> |
… | |
… | |
206 | <h3><a name="how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></h3> |
207 | <h3><a name="how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></h3> |
207 | <p>Try <code>urxvtd -f -o</code>, which tells urxvtd to open the |
208 | <p>Try <code>urxvtd -f -o</code>, which tells urxvtd to open the |
208 | display, create the listening socket and then fork.</p> |
209 | display, create the listening socket and then fork.</p> |
209 | <p> |
210 | <p> |
210 | </p> |
211 | </p> |
|
|
212 | <h3><a name="how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></h3> |
|
|
213 | <p>If you want to start urxvtd automatically whenever you run |
|
|
214 | urxvtc and the daemon isn't running yet, use this script:</p> |
|
|
215 | <pre> |
|
|
216 | #!/bin/sh |
|
|
217 | urxvtc "$@" |
|
|
218 | if [ $? -eq 2 ]; then |
|
|
219 | urxvtd -q -o -f |
|
|
220 | urxvtc "$@" |
|
|
221 | fi</pre> |
|
|
222 | <p>This tries to create a new terminal, and if fails with exit status 2, |
|
|
223 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
224 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
225 | existing daemon.</p> |
|
|
226 | <p> |
|
|
227 | </p> |
211 | <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> |
228 | <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> |
212 | <p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'', |
229 | <p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'', |
213 | so you can check and see if that is set. Note that several programs, JED, |
230 | so you can check and see if that is set. Note that several programs, JED, |
214 | slrn, Midnight Commander automatically check this variable to decide |
231 | slrn, Midnight Commander automatically check this variable to decide |
215 | whether or not to use color.</p> |
232 | whether or not to use color.</p> |