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.20 by root, Thu Jun 30 14:00:49 2005 UTC vs.
Revision 1.21 by root, Wed Jul 13 02:53:54 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 />
… …
480<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 /> 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 />
481</dt> 489</dt>
482<dd> 490<dd>
483Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst 491Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
484problems with <code>wcwidth</code> and a compile problem. 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>
485</dd> 509</dd>
486<p></p> 510<p></p>
487<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 />
488</dt> 512</dt>
489<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 />

Diff Legend

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