sequence "ESC [ 8 n" sets the window title to the version number.
I am using Debian GNU/Linux and have a problem...
- The Debian GNU/Linux package of rxvt-unicode contains large patches
- that considerably change the behaviour of rxvt-unicode. Before
- reporting a bug to the original rxvt-unicode author please download
- and install the genuine version
+ The Debian GNU/Linux package of rxvt-unicode in sarge contains large
+ patches that considerably change the behaviour of rxvt-unicode.
+ Before reporting a bug to the original rxvt-unicode author please
+ download and install the genuine version
(<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
problem. If you cannot, chances are that the problems are specific
to Debian GNU/Linux, in which case it should be reported via the
If you don't plan to use rxvt (quite common...) you could also
replace the rxvt terminfo file with the rxvt-unicode one.
+ "tic" outputs some error when compiling the terminfo entry.
+ Most likely it's the empty definition for "enacs=". Just replace it
+ by "enacs=\E[0@" and try again.
+
"bash"'s readline does not work correctly under rxvt.
I need a termcap file entry.
One reason you might want this is that some distributions or
Try the diff in doc/solaris9.patch as a base. It fixes the worst
problems with "wcwidth" and a compile problem.
+ How can I use rxvt-unicode under cygwin?
+ rxvt-unicode should compile and run out of the box on cygwin, using
+ the X11 libraries that come with cygwin. libW11 emulation is no
+ longer supported (and makes no sense, either, as it only supported a
+ single font). I recommend starting the X-server in "-multiwindow" or
+ "-rootless" mode instead, which will result in similar look&feel as
+ the old libW11 emulation.
+
+ At the time of this writing, cygwin didn't seem to support any
+ multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
+ likely limited to 8-bit encodings.
+
How does rxvt-unicode determine the encoding to use?
Is there an option to switch encodings?
Unlike some other terminals, rxvt-unicode has no encoding switch,
-# Reconstructed via infocmp from file: /usr/share/terminfo/r/rxvt-unicode
+# Reconstructed via infocmp from file: /etc/terminfo/r/rxvt-unicode
# (untranslatable capabilities removed to fit entry within 1023 bytes)
rxvt-unicode|rxvt-unicode terminal (X Window System):\
:am:bw:eo:km:mi:ms:xn:xo:\
<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 />
</dt>
<dd>
-The Debian GNU/Linux package of rxvt-unicode contains large patches that
-considerably change the behaviour of rxvt-unicode. Before reporting a
-bug to the original rxvt-unicode author please download and install the
-genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to
-reproduce the problem. If you cannot, chances are that the problems are
-specific to Debian GNU/Linux, in which case it should be reported via the
-Debian Bug Tracking System (use <code>reportbug</code> to report the bug).
+The Debian GNU/Linux package of rxvt-unicode in sarge contains large
+patches that considerably change the behaviour of rxvt-unicode. Before
+reporting a bug to the original rxvt-unicode author please download and
+install the genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>)
+and try to reproduce the problem. If you cannot, chances are that the
+problems are specific to Debian GNU/Linux, in which case it should be
+reported via the Debian Bug Tracking System (use <code>reportbug</code> to report
+the bug).
</dd>
<dd>
<p>For other problems that also affect the Debian package, you can and
the rxvt terminfo file with the rxvt-unicode one.</p>
</dd>
<p></p>
+<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 />
+</dt>
+<dd>
+Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
+<code>enacs=\E[0@</code> and try again.
+</dd>
+<p></p>
<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 />
</dt>
<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />
problems with <code>wcwidth</code> and a compile problem.
</dd>
<p></p>
+<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 />
+</dt>
+<dd>
+rxvt-unicode should compile and run out of the box on cygwin, using
+the X11 libraries that come with cygwin. libW11 emulation is no
+longer supported (and makes no sense, either, as it only supported a
+single font). I recommend starting the X-server in <code>-multiwindow</code> or
+<code>-rootless</code> mode instead, which will result in similar look&feel as the
+old libW11 emulation.
+</dd>
+<dd>
+<p>At the time of this writing, cygwin didn't seem to support any multi-byte
+encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
+to 8-bit encodings.</p>
+</dd>
+<p></p>
<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 />
</dt>
<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />
.\" ========================================================================
.\"
.IX Title "rxvt 7"
-.TH rxvt 7 "2005-06-26" "5.6" "RXVT-UNICODE"
+.TH rxvt 7 "2005-07-13" "5.7" "RXVT-UNICODE"
.SH "NAME"
RXVT REFERENCE \- FAQ, command sequences and other background information
.SH "SYNOPSIS"
sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number.
.IP "I am using Debian GNU/Linux and have a problem..." 4
.IX Item "I am using Debian GNU/Linux and have a problem..."
-The Debian GNU/Linux package of rxvt-unicode contains large patches that
-considerably change the behaviour of rxvt\-unicode. Before reporting a
-bug to the original rxvt-unicode author please download and install the
-genuine version (<http://software.schmorp.de#rxvt\-unicode>) and try to
-reproduce the problem. If you cannot, chances are that the problems are
-specific to Debian GNU/Linux, in which case it should be reported via the
-Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
+The Debian GNU/Linux package of rxvt-unicode in sarge contains large
+patches that considerably change the behaviour of rxvt\-unicode. Before
+reporting a bug to the original rxvt-unicode author please download and
+install the genuine version (<http://software.schmorp.de#rxvt\-unicode>)
+and try to reproduce the problem. If you cannot, chances are that the
+problems are specific to Debian GNU/Linux, in which case it should be
+reported via the Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report
+the bug).
.Sp
For other problems that also affect the Debian package, you can and
probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a
.Sp
If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
the rxvt terminfo file with the rxvt-unicode one.
+.ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4
+.el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4
+.IX Item "tic outputs some error when compiling the terminfo entry."
+Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
+\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4
.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4
.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@."
.IX Item "I use Solaris 9 and it doesn't compile/work/etc."
Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
+.IP "How can I use rxvt-unicode under cygwin?" 4
+.IX Item "How can I use rxvt-unicode under cygwin?"
+rxvt-unicode should compile and run out of the box on cygwin, using
+the X11 libraries that come with cygwin. libW11 emulation is no
+longer supported (and makes no sense, either, as it only supported a
+single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
+\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
+old libW11 emulation.
+.Sp
+At the time of this writing, cygwin didn't seem to support any multi-byte
+encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
+to 8\-bit encodings.
.IP "How does rxvt-unicode determine the encoding to use?" 4
.IX Item "How does rxvt-unicode determine the encoding to use?"
.PD 0
sequence "ESC [ 8 n" sets the window title to the version number.
I am using Debian GNU/Linux and have a problem...
- The Debian GNU/Linux package of rxvt-unicode contains large patches
- that considerably change the behaviour of rxvt-unicode. Before
- reporting a bug to the original rxvt-unicode author please download
- and install the genuine version
+ The Debian GNU/Linux package of rxvt-unicode in sarge contains large
+ patches that considerably change the behaviour of rxvt-unicode.
+ Before reporting a bug to the original rxvt-unicode author please
+ download and install the genuine version
(<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
problem. If you cannot, chances are that the problems are specific
to Debian GNU/Linux, in which case it should be reported via the
If you don't plan to use rxvt (quite common...) you could also
replace the rxvt terminfo file with the rxvt-unicode one.
+ "tic" outputs some error when compiling the terminfo entry.
+ Most likely it's the empty definition for "enacs=". Just replace it
+ by "enacs=\E[0@" and try again.
+
"bash"'s readline does not work correctly under rxvt.
I need a termcap file entry.
One reason you might want this is that some distributions or
Try the diff in doc/solaris9.patch as a base. It fixes the worst
problems with "wcwidth" and a compile problem.
+ How can I use rxvt-unicode under cygwin?
+ rxvt-unicode should compile and run out of the box on cygwin, using
+ the X11 libraries that come with cygwin. libW11 emulation is no
+ longer supported (and makes no sense, either, as it only supported a
+ single font). I recommend starting the X-server in "-multiwindow" or
+ "-rootless" mode instead, which will result in similar look&feel as
+ the old libW11 emulation.
+
+ At the time of this writing, cygwin didn't seem to support any
+ multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
+ likely limited to 8-bit encodings.
+
How does rxvt-unicode determine the encoding to use?
Is there an option to switch encodings?
Unlike some other terminals, rxvt-unicode has no encoding switch,
<dd>
Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon
listening on <path></code> after binding to its control socket. This option
-will suppress this message (errors and warnings will still be output).
+will suppress this message (errors and warnings will still be logged).
</dd>
<p></p>
<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong><br />
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "rxvt 1"
-.TH rxvt 1 "2005-07-07" "5.6" "RXVT-UNICODE"
+.TH rxvt 1 "2005-07-13" "5.7" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@d \- @@RXVT_NAME@@ terminal daemon
.SH "SYNOPSIS"
.IX Item "-q, --quiet"
Normally, \fB@@RXVT_NAME@@d\fR outputs the message \f(CW\*(C`rxvt\-unicode daemon
listening on <path>\*(C'\fR after binding to its control socket. This option
-will suppress this message (errors and warnings will still be output).
+will suppress this message (errors and warnings will still be logged).
.IP "\fB\-o\fR, \fB\-\-opendisplay\fR" 4
.IX Item "-o, --opendisplay"
This forces \fB@@RXVT_NAME@@d\fR to open a connection to the current
-q, --quiet
Normally, rxvtd outputs the message "rxvt-unicode daemon listening
on <path>" after binding to its control socket. This option will
- suppress this message (errors and warnings will still be output).
+ suppress this message (errors and warnings will still be logged).
-o, --opendisplay
This forces rxvtd to open a connection to the current $DISPLAY and
projects / dana / urxvt.git / commitdiff