From b754fa61f9e7d3f01307d3c65c7d81dd18946043 Mon Sep 17 00:00:00 2001 From: root Date: Wed, 13 Jul 2005 02:53:54 +0000 Subject: [PATCH] *** empty log message *** --- README.FAQ | 24 +++++++++++++++++++---- doc/etc/rxvt-unicode.termcap | 2 +- doc/rxvt.7.html | 38 +++++++++++++++++++++++++++++------- doc/rxvt.7.man.in | 34 ++++++++++++++++++++++++-------- doc/rxvt.7.txt | 24 +++++++++++++++++++---- doc/rxvtd.1.html | 2 +- doc/rxvtd.1.man.in | 6 +++--- doc/rxvtd.1.txt | 2 +- 8 files changed, 103 insertions(+), 29 deletions(-) diff --git a/README.FAQ b/README.FAQ index c60c1cf8..a8ef3076 100644 --- a/README.FAQ +++ b/README.FAQ @@ -4,10 +4,10 @@ FREQUENTLY ASKED QUESTIONS 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 () 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 @@ -47,6 +47,10 @@ FREQUENTLY ASKED QUESTIONS 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 @@ -314,6 +318,18 @@ FREQUENTLY ASKED QUESTIONS 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, diff --git a/doc/etc/rxvt-unicode.termcap b/doc/etc/rxvt-unicode.termcap index bd689e35..4303a20b 100644 --- a/doc/etc/rxvt-unicode.termcap +++ b/doc/etc/rxvt-unicode.termcap @@ -1,4 +1,4 @@ -# 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:\ diff --git a/doc/rxvt.7.html b/doc/rxvt.7.html index 2fccb1e5..d6b3434e 100644 --- a/doc/rxvt.7.html +++ b/doc/rxvt.7.html @@ -85,13 +85,14 @@ 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 (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 reportbug 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 reportbug to report +the bug).

For other problems that also affect the Debian package, you can and @@ -139,6 +140,13 @@ resource to set it:

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.
@@ -484,6 +492,22 @@ 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?
diff --git a/doc/rxvt.7.man.in b/doc/rxvt.7.man.in index 32e32040..2181c6f6 100644 --- a/doc/rxvt.7.man.in +++ b/doc/rxvt.7.man.in @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .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" @@ -164,13 +164,14 @@ The version number is displayed with the usage (\-h). Also the escape 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 () 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 () +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 @@ -207,6 +208,11 @@ resource to set it: .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@@." @@ -492,6 +498,18 @@ complete replacements for them :) .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 diff --git a/doc/rxvt.7.txt b/doc/rxvt.7.txt index 62cce146..52585826 100644 --- a/doc/rxvt.7.txt +++ b/doc/rxvt.7.txt @@ -25,10 +25,10 @@ FREQUENTLY ASKED QUESTIONS 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 () 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 @@ -68,6 +68,10 @@ FREQUENTLY ASKED QUESTIONS 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 @@ -335,6 +339,18 @@ FREQUENTLY ASKED QUESTIONS 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, diff --git a/doc/rxvtd.1.html b/doc/rxvtd.1.html index 01b4c388..cd597c7c 100644 --- a/doc/rxvtd.1.html +++ b/doc/rxvtd.1.html @@ -61,7 +61,7 @@ options is not yet supported.

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). +will suppress this message (errors and warnings will still be logged).

-o, --opendisplay
diff --git a/doc/rxvtd.1.man.in b/doc/rxvtd.1.man.in index dde9c3b8..a3bfce61 100644 --- a/doc/rxvtd.1.man.in +++ b/doc/rxvtd.1.man.in @@ -1,4 +1,4 @@ -.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 +.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3 .\" .\" Standard preamble: .\" ======================================================================== @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .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" @@ -161,7 +161,7 @@ options is not yet supported. .IX Item "-q, --quiet" Normally, \fB@@RXVT_NAME@@d\fR outputs the message \f(CW\*(C`rxvt\-unicode daemon listening on \*(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 diff --git a/doc/rxvtd.1.txt b/doc/rxvtd.1.txt index d907bb0b..b7df60fc 100644 --- a/doc/rxvtd.1.txt +++ b/doc/rxvtd.1.txt @@ -29,7 +29,7 @@ OPTIONS -q, --quiet Normally, rxvtd outputs the message "rxvt-unicode daemon listening on " 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 -- 2.34.1