ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.html
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.75 by root, Mon Jul 17 19:20:29 2006 UTC vs.
Revision 1.76 by root, Mon Aug 7 16:17:30 2006 UTC

… …
27 <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> 27 <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>
28 <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> 28 <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>
29 <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> 29 <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>
30 <li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li> 30 <li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li>
31 <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> 31 <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>
32 <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> 32 <li><a href="#how_do_i_distinguish_whether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li>
33 <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> 33 <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>
34 <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> 34 <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>
35 <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> 35 <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>
36 <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li> 36 <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li>
37 </ul> 37 </ul>
… …
227meaning it couldn't connect to the daemon, it will start the daemon and 227meaning it couldn't connect to the daemon, it will start the daemon and
228re-run the command. Subsequent invocations of the script will re-use the 228re-run the command. Subsequent invocations of the script will re-use the
229existing daemon.</p> 229existing daemon.</p>
230<p> 230<p>
231</p> 231</p>
232<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> 232<h3><a name="how_do_i_distinguish_whether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3>
233<p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'', 233<p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'',
234so you can check and see if that is set. Note that several programs, JED, 234so you can check and see if that is set. Note that several programs, JED,
235slrn, Midnight Commander automatically check this variable to decide 235slrn, Midnight Commander automatically check this variable to decide
236whether or not to use color.</p> 236whether or not to use color.</p>
237<p> 237<p>
… …
278 text data bss drs rss filename 278 text data bss drs rss filename
279 98398 1664 24 15695 1824 rxvt --disable-everything 279 98398 1664 24 15695 1824 rxvt --disable-everything
280 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> 280 188985 9048 66616 18222 1788 urxvt --disable-everything</pre>
281<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which <em>is</em> unfair, as this involves xft 281<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which <em>is</em> unfair, as this involves xft
282and full locale/XIM support which are quite bloaty inside libX11 and my 282and full locale/XIM support which are quite bloaty inside libX11 and my
283libc), the two diverge, but not unreasnobaly so.</p> 283libc), the two diverge, but not unreasonably so.</p>
284<pre> 284<pre>
285 text data bss drs rss filename 285 text data bss drs rss filename
286 163431 2152 24 20123 2060 rxvt --enable-everything 286 163431 2152 24 20123 2060 rxvt --enable-everything
287 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre> 287 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre>
288<p>The very large size of the text section is explained by the east-asian 288<p>The very large size of the text section is explained by the east-asian
… …
361<p>3. Use an ARGB visual:</p> 361<p>3. Use an ARGB visual:</p>
362<pre> 362<pre>
363 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre> 363 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>
364<p>This requires XFT support, and the support of your X-server. If that 364<p>This requires XFT support, and the support of your X-server. If that
365doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't 365doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
366there yet, no matter what they claim. Rxvt-Unicode contains the neccessary 366there yet, no matter what they claim. Rxvt-Unicode contains the necessary
367bugfixes and workarounds for Xft and Xlib to make it work, but that 367bugfixes and workarounds for Xft and Xlib to make it work, but that
368doesn't mean that your WM has the required kludges in place.</p> 368doesn't mean that your WM has the required kludges in place.</p>
369<p>4. Use xcompmgr and let it do the job:</p> 369<p>4. Use xcompmgr and let it do the job:</p>
370<pre> 370<pre>
371 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ 371 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
… …
384<p>All of this requires that fonts do not lie about character sizes, 384<p>All of this requires that fonts do not lie about character sizes,
385however: Xft fonts often draw glyphs larger than their acclaimed bounding 385however: Xft fonts often draw glyphs larger than their acclaimed bounding
386box, and rxvt-unicode has no way of detecting this (the correct way is to 386box, and rxvt-unicode has no way of detecting this (the correct way is to
387ask for the character bounding box, which unfortunately is wrong in these 387ask for the character bounding box, which unfortunately is wrong in these
388cases).</p> 388cases).</p>
389<p>It's not clear (to me at least), wether this is a bug in Xft, freetype, 389<p>It's not clear (to me at least), whether this is a bug in Xft, freetype,
390or the respective font. If you encounter this problem you might try using 390or the respective font. If you encounter this problem you might try using
391the <code>-lsp</code> option to give the font more height. If that doesn't work, you 391the <code>-lsp</code> option to give the font more height. If that doesn't work, you
392might be forced to use a different font.</p> 392might be forced to use a different font.</p>
393<p>All of this is not a problem when using X11 core fonts, as their bounding 393<p>All of this is not a problem when using X11 core fonts, as their bounding
394box data is correct.</p> 394box data is correct.</p>
… …
603<p>These are caused by the <code>readline</code> perl extension. Under normal 603<p>These are caused by the <code>readline</code> perl extension. Under normal
604circumstances, it will move your cursor around when you click into the 604circumstances, it will move your cursor around when you click into the
605line that contains it. It tries hard not to do this at the wrong moment, 605line that contains it. It tries hard not to do this at the wrong moment,
606but when running a program that doesn't parse cursor movements or in some 606but when running a program that doesn't parse cursor movements or in some
607cases during rlogin sessions, it fails to detect this properly.</p> 607cases during rlogin sessions, it fails to detect this properly.</p>
608<p>You can permamently switch this feature off by disabling the <code>readline</code> 608<p>You can permanently switch this feature off by disabling the <code>readline</code>
609extension:</p> 609extension:</p>
610<pre> 610<pre>
611 URxvt.perl-ext-common: default,-readline</pre> 611 URxvt.perl-ext-common: default,-readline</pre>
612<p> 612<p>
613</p> 613</p>
614<h3><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h3> 614<h3><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h3>
615<p>Some Debian GNUL/Linux users seem to have this problem, although no 615<p>Some Debian GNUL/Linux users seem to have this problem, although no
616specific details were reported so far. It is possible that this is caused 616specific details were reported so far. It is possible that this is caused
617by the wrong <code>TERM</code> setting, although the details of wether and how 617by the wrong <code>TERM</code> setting, although the details of whether and how
618this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible 618this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
619keymap. See the answer to the previous question, and please report if that 619keymap. See the answer to the previous question, and please report if that
620helped.</p> 620helped.</p>
621<p> 621<p>
622</p> 622</p>
… …
647depressed.</p> 647depressed.</p>
648<p> 648<p>
649</p> 649</p>
650<h3><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h3> 650<h3><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h3>
651<p>Assuming that the physical Backspace key corresponds to the 651<p>Assuming that the physical Backspace key corresponds to the
652BackSpace keysym (not likely for Linux ... see the following 652Backspace keysym (not likely for Linux ... see the following
653question) there are two standard values that can be used for 653question) there are two standard values that can be used for
654Backspace: <code>^H</code> and <code>^?</code>.</p> 654Backspace: <code>^H</code> and <code>^?</code>.</p>
655<p>Historically, either value is correct, but rxvt-unicode adopts the debian 655<p>Historically, either value is correct, but rxvt-unicode adopts the debian
656policy of using <code>^?</code> when unsure, because it's the one only only correct 656policy of using <code>^?</code> when unsure, because it's the one only only correct
657choice :).</p> 657choice :).</p>
… …
766<p>This is my perl configuration. The first two set the perl library 766<p>This is my perl configuration. The first two set the perl library
767directory and also tells urxvt to use a large number of extensions. I 767directory and also tells urxvt to use a large number of extensions. I
768develop for myself mostly, so I actually use most of the extensions I 768develop for myself mostly, so I actually use most of the extensions I
769write.</p> 769write.</p>
770<p>The selection stuff mainly makes the selection perl-error-message aware 770<p>The selection stuff mainly makes the selection perl-error-message aware
771and tells it to convert pelr error mssages into vi-commands to load the 771and tells it to convert perl error messages into vi-commands to load the
772relevant file and go tot he error line number.</p> 772relevant file and go tot he error line number.</p>
773<pre> 773<pre>
774 URxvt.scrollstyle: plain 774 URxvt.scrollstyle: plain
775 URxvt.secondaryScroll: true</pre> 775 URxvt.secondaryScroll: true</pre>
776<p>As the documentation says: plain is the preferred scrollbar for the 776<p>As the documentation says: plain is the preferred scrollbar for the
777author. The <code>secondaryScroll</code> confgiures urxvt to scroll in full-screen 777author. The <code>secondaryScroll</code> configures urxvt to scroll in full-screen
778apps, like screen, so lines scorlled out of screen end up in urxvt's 778apps, like screen, so lines scrolled out of screen end up in urxvt's
779scrollback buffer.</p> 779scrollback buffer.</p>
780<pre> 780<pre>
781 URxvt.background: #000000 781 URxvt.background: #000000
782 URxvt.foreground: gray90 782 URxvt.foreground: gray90
783 URxvt.color7: gray90 783 URxvt.color7: gray90
… …
825 xft:Code2000:antialias=false 825 xft:Code2000:antialias=false
826 urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 826 urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
827 urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 827 urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
828 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> 828 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
829<p>I wrote rxvt-unicode to be able to specify fonts exactly. So don't be 829<p>I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
830overwhelmed. A special note: the <code>9x15bold</code> mentioend above is actually 830overwhelmed. A special note: the <code>9x15bold</code> mentioned above is actually
831the version from XFree-3.3, as XFree-4 replaced it by a totally different 831the version from XFree-3.3, as XFree-4 replaced it by a totally different
832font (different glyphs for <code>;</code> and many other harmless characters), 832font (different glyphs for <code>;</code> and many other harmless characters),
833while the second font is actually the <code>9x15bold</code> from XFree4/XOrg. The 833while the second font is actually the <code>9x15bold</code> from XFree4/XOrg. The
834bold version has less chars than the medium version, so I use it for rare 834bold version has less chars than the medium version, so I use it for rare
835characters, too. Whene ditign sources with vim, I use italic for comments 835characters, too. When editing sources with vim, I use italic for comments
836and other stuff, which looks quite good with Bitstream Vera anti-aliased.</p> 836and other stuff, which looks quite good with Bitstream Vera anti-aliased.</p>
837<p>Terminus is a quite bad font (many very wrong glyphs), but for most of my 837<p>Terminus is a quite bad font (many very wrong glyphs), but for most of my
838purposes, it works, and gives a different look, as my normal (Non-bold) 838purposes, it works, and gives a different look, as my normal (Non-bold)
839font is already bold, and I want to see a difference between bold and 839font is already bold, and I want to see a difference between bold and
840normal fonts.</p> 840normal fonts.</p>
… …
883re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p> 883re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p>
884<p>Also consider the form resources have to use:</p> 884<p>Also consider the form resources have to use:</p>
885<pre> 885<pre>
886 URxvt.resource: value</pre> 886 URxvt.resource: value</pre>
887<p>If you want to use another form (there are lots of different ways of 887<p>If you want to use another form (there are lots of different ways of
888specifying resources), make sure you understand wether and why it 888specifying resources), make sure you understand whether and why it
889works. If unsure, use the form above.</p> 889works. If unsure, use the form above.</p>
890<p> 890<p>
891</p> 891</p>
892<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> 892<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>
893<p>The terminal description used by rxvt-unicode is not as widely available 893<p>The terminal description used by rxvt-unicode is not as widely available
… …
924<h3><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h3> 924<h3><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h3>
925<p>One reason you might want this is that some distributions or operating 925<p>One reason you might want this is that some distributions or operating
926systems still compile some programs using the long-obsoleted termcap 926systems still compile some programs using the long-obsoleted termcap
927library (Fedora Core's bash is one example) and rely on a termcap entry 927library (Fedora Core's bash is one example) and rely on a termcap entry
928for <code>rxvt-unicode</code>.</p> 928for <code>rxvt-unicode</code>.</p>
929<p>You could use rxvt's termcap entry with resonable results in many cases. 929<p>You could use rxvt's termcap entry with reasonable results in many cases.
930You can also create a termcap entry by using terminfo's infocmp program 930You can also create a termcap entry by using terminfo's infocmp program
931like this:</p> 931like this:</p>
932<pre> 932<pre>
933 infocmp -C rxvt-unicode</pre> 933 infocmp -C rxvt-unicode</pre>
934<p>Or you could use this termcap entry, generated by the command above:</p> 934<p>Or you could use this termcap entry, generated by the command above:</p>
… …
955 :vs=\E[?25h:</pre> 955 :vs=\E[?25h:</pre>
956<p> 956<p>
957</p> 957</p>
958<h3><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h3> 958<h3><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h3>
959<p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to 959<p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to
960decide wether a terminal has colour, but uses its own configuration 960decide whether a terminal has colour, but uses its own configuration
961file. Needless to say, <code>rxvt-unicode</code> is not in its default file (among 961file. Needless to say, <code>rxvt-unicode</code> is not in its default file (among
962with most other terminals supporting colour). Either add:</p> 962with most other terminals supporting colour). Either add:</p>
963<pre> 963<pre>
964 TERM rxvt-unicode</pre> 964 TERM rxvt-unicode</pre>
965<p>to <code>/etc/DIR_COLORS</code> or simply add:</p> 965<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>
… …
1092 1092
1093<dt><strong><a name="item__2d_make_sure_the_xmodifiers_environment_variable_">- Make sure the <code>XMODIFIERS</code> environment variable is set correctly when <em>starting</em> rxvt-unicode.</a></strong> 1093<dt><strong><a name="item__2d_make_sure_the_xmodifiers_environment_variable_">- Make sure the <code>XMODIFIERS</code> environment variable is set correctly when <em>starting</em> rxvt-unicode.</a></strong>
1094 1094
1095<dd> 1095<dd>
1096<p>When you want to use e.g. <strong>kinput2</strong>, it must be set to 1096<p>When you want to use e.g. <strong>kinput2</strong>, it must be set to
1097<code>@im=kinput2</code>. For <strong>scim</strong>, use <code>@im=SCIM</code>. Youc an see what input 1097<code>@im=kinput2</code>. For <strong>scim</strong>, use <code>@im=SCIM</code>. You can see what input
1098method servers are running with this command:</p> 1098method servers are running with this command:</p>
1099</dd> 1099</dd>
1100<dd> 1100<dd>
1101<pre> 1101<pre>
1102 xprop -root XIM_SERVERS</pre> 1102 xprop -root XIM_SERVERS</pre>
… …
1146<p> 1146<p>
1147</p> 1147</p>
1148<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> 1148<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>
1149<p>You should build one binary with the default options. <em>configure</em> 1149<p>You should build one binary with the default options. <em>configure</em>
1150now enables most useful options, and the trend goes to making them 1150now enables most useful options, and the trend goes to making them
1151runtime-switchable, too, so there is usually no drawback to enbaling them, 1151runtime-switchable, too, so there is usually no drawback to enabling them,
1152except higher disk and possibly memory usage. The perl interpreter should 1152except higher disk and possibly memory usage. The perl interpreter should
1153be enabled, as important functionality (menus, selection, likely more in 1153be enabled, as important functionality (menus, selection, likely more in
1154the future) depends on it.</p> 1154the future) depends on it.</p>
1155<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources 1155<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
1156system-wide (except maybe with <code>defaults</code>). This will result in useful 1156system-wide (except maybe with <code>defaults</code>). This will result in useful
… …
1187<p> 1187<p>
1188</p> 1188</p>
1189<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> 1189<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>
1190<p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined 1190<p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined
1191in your compile environment, or an implementation that implements it, 1191in your compile environment, or an implementation that implements it,
1192wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that 1192whether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that
1193<strong>wchar_t</strong> is represented as unicode.</p> 1193<strong>wchar_t</strong> is represented as unicode.</p>
1194<p>As you might have guessed, FreeBSD does neither define this symobl nor 1194<p>As you might have guessed, FreeBSD does neither define this symbol nor
1195does it support it. Instead, it uses its own internal representation of 1195does it support it. Instead, it uses its own internal representation of
1196<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> 1196<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
1197<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and 1197<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
1198<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> 1198<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
1199<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language 1199<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
… …
2497</dd> 2497</dd>
2498</li> 2498</li>
2499<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong> 2499<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong>
2500 2500
2501<dd> 2501<dd>
2502<p>Enable extended ISO 14755 support (see urxvt(1), or 2502<p>Enable extended ISO 14755 support (see rxvt(1), or
2503<em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by 2503<em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by
2504<code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with 2504<code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with
2505this switch.</p> 2505this switch.</p>
2506</dd> 2506</dd>
2507</li> 2507</li>
… …
2567</dd> 2567</dd>
2568</li> 2568</li>
2569<dt><strong><a name="item_perl">--enable-perl (default: on)</a></strong> 2569<dt><strong><a name="item_perl">--enable-perl (default: on)</a></strong>
2570 2570
2571<dd> 2571<dd>
2572<p>Enable an embedded perl interpreter. See the <strong>urxvtperl(3)</strong> 2572<p>Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
2573manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files 2573manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files
2574in <em>src/perl-ext/</em> for the extensions that are installed by default. The 2574in <em>src/perl-ext/</em> for the extensions that are installed by default. The
2575perl interpreter that is used can be specified via the <code>PERL</code> environment 2575perl interpreter that is used can be specified via the <code>PERL</code> environment
2576variable when running configure.</p> 2576variable when running configure.</p>
2577</dd> 2577</dd>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines