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.18 by root, Mon Feb 21 19:26:06 2005 UTC vs.
Revision 1.22 by root, Wed Jul 13 03:08:57 2005 UTC

… …
83</dd> 83</dd>
84<p></p> 84<p></p>
85<dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br /> 85<dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br />
86</dt> 86</dt>
87<dd> 87<dd>
88The Debian GNU/Linux package of rxvt-unicode contains large patches that 88The Debian GNU/Linux package of rxvt-unicode in sarge contains large
89considerably change the behaviour of rxvt-unicode. Before reporting a 89patches that considerably change the behaviour of rxvt-unicode. Before
90bug to the original rxvt-unicode author please download and install the 90reporting a bug to the original rxvt-unicode author please download and
91genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to 91install the genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>)
92reproduce the problem. If you cannot, chances are that the problems are 92and try to reproduce the problem. If you cannot, chances are that the
93specific to Debian GNU/Linux, in which case it should be reported via the 93problems are specific to Debian GNU/Linux, in which case it should be
94Debian Bug Tracking System (use <code>reportbug</code> to report the bug). 94reported via the Debian Bug Tracking System (use <code>reportbug</code> to report
95the bug).
95</dd> 96</dd>
96<dd> 97<dd>
97<p>For other problems that also affect the Debian package, you can and 98<p>For other problems that also affect the Debian package, you can and
98probably should use the Debian BTS, too, because, after all, it's also a 99probably should use the Debian BTS, too, because, after all, it's also a
99bug in the Debian version and it serves as a reminder for other users that 100bug in the Debian version and it serves as a reminder for other users that
… …
135 URxvt.termName: rxvt</pre> 136 URxvt.termName: rxvt</pre>
136</dd> 137</dd>
137<dd> 138<dd>
138<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace 139<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace
139the rxvt terminfo file with the rxvt-unicode one.</p> 140the rxvt terminfo file with the rxvt-unicode one.</p>
141</dd>
142<p></p>
143<dt><strong><a name="item_tic_outputs_some_error_when_compiling_the_terminfo"><code>tic</code> outputs some error when compiling the terminfo entry.</a></strong><br />
144</dt>
145<dd>
146Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
147<code>enacs=\E[0@</code> and try again.
140</dd> 148</dd>
141<p></p> 149<p></p>
142<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br /> 150<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br />
143</dt> 151</dt>
144<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> 152<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />
… …
371<dd> 379<dd>
372<p>All of this is not a problem when using X11 core fonts, as their bounding 380<p>All of this is not a problem when using X11 core fonts, as their bounding
373box data is correct.</p> 381box data is correct.</p>
374</dd> 382</dd>
375<p></p> 383<p></p>
384<dt><strong><a name="item_on_solaris_9_2c_many_line_2ddrawing_characters_are">On Solaris 9, many line-drawing characters are too wide.</a></strong><br />
385</dt>
386<dd>
387Seems to be a known bug, read
388<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the
389following ugly workaround to get non-double-wide-characters working:
390</dd>
391<dd>
392<pre>
393 #define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>
394</dd>
395<p></p>
376<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br /> 396<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br />
377</dt> 397</dt>
378<dd> 398<dd>
379The most common causes for this are that either your locale is not set 399The most common causes for this are that either your locale is not set
380correctly, or you specified a <strong>preeditStyle</strong> that is not supported by 400correctly, or you specified a <strong>preeditStyle</strong> that is not supported by
… …
438<p>As you might have guessed, FreeBSD does neither define this symobl nor 458<p>As you might have guessed, FreeBSD does neither define this symobl nor
439does it support it. Instead, it uses it's own internal representation of 459does it support it. Instead, it uses it's own internal representation of
440<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> 460<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
441</dd> 461</dd>
442<dd> 462<dd>
463<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
464<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
465</dd>
466<dd>
443<p>However, <code>__STDC_ISO_10646__</code> is the only sane way to support 467<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
444multi-language apps in an OS, as using a locale-dependent (and 468apps in an OS, as using a locale-dependent (and non-standardized)
445non-standardized) representation of <strong>wchar_t</strong> makes it impossible to 469representation of <strong>wchar_t</strong> makes it impossible to convert between
446convert between <strong>wchar_t</strong> (as used by X11 and your applications) and any 470<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding
447other encoding without implementing OS-specific-wrappers for each and 471without implementing OS-specific-wrappers for each and every locale. There
448every locale. There simply are no APIs to convert <strong>wchar_t</strong> into anything 472simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
449except the current locale encoding.</p> 473locale encoding.</p>
450</dd> 474</dd>
451<dd> 475<dd>
452<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this 476<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
453by carrying their own replacement functions for character set handling 477by carrying their own replacement functions for character set handling
454with them, and either implementing OS-dependent hacks or doing multiple 478with them, and either implementing OS-dependent hacks or doing multiple
… …
457</dd> 481</dd>
458<dd> 482<dd>
459<p>The rxvt-unicode author insists that the right way to fix this is in the 483<p>The rxvt-unicode author insists that the right way to fix this is in the
460system libraries once and for all, instead of forcing every app to carry 484system libraries once and for all, instead of forcing every app to carry
461complete replacements for them :)</p> 485complete replacements for them :)</p>
486</dd>
487<p></p>
488<dt><strong><a name="item_i_use_solaris_9_and_it_doesn_27t_compile_2fwork_2f">I use Solaris 9 and it doesn't compile/work/etc.</a></strong><br />
489</dt>
490<dd>
491Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
492problems with <code>wcwidth</code> and a compile problem.
493</dd>
494<p></p>
495<dt><strong><a name="item_how_can_i_use_rxvt_2dunicode_under_cygwin_3f">How can I use rxvt-unicode under cygwin?</a></strong><br />
496</dt>
497<dd>
498rxvt-unicode should compile and run out of the box on cygwin, using
499the X11 libraries that come with cygwin. libW11 emulation is no
500longer supported (and makes no sense, either, as it only supported a
501single font). I recommend starting the X-server in <code>-multiwindow</code> or
502<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
503old libW11 emulation.
504</dd>
505<dd>
506<p>At the time of this writing, cygwin didn't seem to support any multi-byte
507encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
508to 8-bit encodings.</p>
462</dd> 509</dd>
463<p></p> 510<p></p>
464<dt><strong><a name="item_how_does_rxvt_2dunicode_determine_the_encoding_to_">How does rxvt-unicode determine the encoding to use?</a></strong><br /> 511<dt><strong><a name="item_how_does_rxvt_2dunicode_determine_the_encoding_to_">How does rxvt-unicode determine the encoding to use?</a></strong><br />
465</dt> 512</dt>
466<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br /> 513<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />
… …
733</dd> 780</dd>
734<p></p> 781<p></p>
735<dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br /> 782<dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br />
736</dt> 783</dt>
737<dd> 784<dd>
738Despite it's name, rxvtd is not a real daemon, but more like a 785Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
739server that answers rxvtc's requests, so it doesn't background 786display, create the listening socket and then fork.
740itself.
741</dd>
742<dd>
743<p>To ensure rxvtd is listening on it's socket, you can use the
744following method to wait for the startup message before continuing:</p>
745</dd>
746<dd>
747<pre>
748 { rxvtd &amp; } | read</pre>
749</dd> 787</dd>
750<p></p> 788<p></p>
751<dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br /> 789<dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br />
752</dt> 790</dt>
753<dd> 791<dd>
… …
2529</dd> 2567</dd>
2530<p></p> 2568<p></p>
2531<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br /> 2569<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br />
2532</dt> 2570</dt>
2533<dd> 2571<dd>
2534Compile in support for additional codeset (encoding) groups (eu, vn are 2572Compile in support for additional codeset (encoding) groups (<code>eu</code>, <code>vn</code>
2535always compiled in, which includes most 8-bit character sets). These 2573are always compiled in, which includes most 8-bit character sets). These
2536codeset tables are currently only used for driving X11 core fonts, they 2574codeset tables are used for driving X11 core fonts, they are not required
2537are not required for Xft fonts. Compiling them in will make your binary 2575for Xft fonts, although having them compiled in lets rxvt-unicode choose
2538bigger (together about 700kB), but it doesn't increase memory usage unless 2576replacement fonts more intelligently. Compiling them in will make your
2577binary bigger (all of together cost about 700kB), but it doesn't increase
2539you use an X11 font requiring one of these encodings. 2578memory usage unless you use a font requiring one of these encodings.
2540</dd> 2579</dd>
2541<table> 2580<table>
2542<tr><td>all</td><td>all available codeset groups</td></tr> 2581<tr><td>all</td><td>all available codeset groups</td></tr>
2543<tr><td>zh</td><td>common chinese encodings</td></tr> 2582<tr><td>zh</td><td>common chinese encodings</td></tr>
2544<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr> 2583<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr>
… …
2783 backindex and forwardindex escape sequence 2822 backindex and forwardindex escape sequence
2784 window op and some xterm/OSC escape sequences 2823 window op and some xterm/OSC escape sequences
2785 tripleclickwords 2824 tripleclickwords
2786 settable insecure mode 2825 settable insecure mode
2787 keysym remapping support 2826 keysym remapping support
2827 cursor blinking and underline cursor
2788 -embed and -pty-fd options</pre> 2828 -embed and -pty-fd options</pre>
2789</dd> 2829</dd>
2790<p></p> 2830<p></p>
2791<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br /> 2831<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br />
2792</dt> 2832</dt>
… …
2848</dt> 2888</dt>
2849<dd> 2889<dd>
2850Add smart growth/shrink behaviour when changing font size via from hot 2890Add smart growth/shrink behaviour when changing font size via from hot
2851keys. This should keep in a fixed position the rxvt corner which is 2891keys. This should keep in a fixed position the rxvt corner which is
2852closest to a corner of the screen. 2892closest to a corner of the screen.
2853</dd>
2854<p></p>
2855<dt><strong><a name="item__2d_2denable_2dcursor_2dblink">--enable-cursor-blink</a></strong><br />
2856</dt>
2857<dd>
2858Add support for a blinking cursor.
2859</dd> 2893</dd>
2860<p></p> 2894<p></p>
2861<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br /> 2895<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br />
2862</dt> 2896</dt>
2863<dd> 2897<dd>

Diff Legend

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