--- rxvt-unicode/doc/rxvt.7.man.in 2005/04/17 22:36:13 1.20 +++ rxvt-unicode/doc/rxvt.7.man.in 2005/08/10 01:44:35 1.24 @@ -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 7" -.TH rxvt 7 "2005-04-17" "5.3" "RXVT-UNICODE" +.TH rxvt 7 "2005-08-05" "5.7" "RXVT-UNICODE" .SH "NAME" RXVT REFERENCE \- FAQ, command sequences and other background information .SH "SYNOPSIS" @@ -164,13 +164,14 @@ 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 @@ .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@@." @@ -408,6 +414,15 @@ .Sp All of this is not a problem when using X11 core fonts, as their bounding box data is correct. +.IP "On Solaris 9, many line-drawing characters are too wide." 4 +.IX Item "On Solaris 9, many line-drawing characters are too wide." +Seems to be a known bug, read +. Some people use the +following ugly workaround to get non-double-wide-characters working: +.Sp +.Vb 1 +\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) +.Ve .IP "My Compose (Multi_key) key is no longer working." 4 .IX Item "My Compose (Multi_key) key is no longer working." The most common causes for this are that either your locale is not set @@ -479,6 +494,22 @@ The rxvt-unicode author insists that the right way to fix this is in the system libraries once and for all, instead of forcing every app to carry complete replacements for them :) +.IP "I use Solaris 9 and it doesn't compile/work/etc." 4 +.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 @@ -608,7 +639,7 @@ .IX Item "Can I speed up Xft rendering somehow?" Yes, the most obvious way to speed it up is to avoid Xft entirely, as it is simply slow. If you still want Xft fonts you might try to disable -antialiasing (by appending \f(CW\*(C`:antialiasing=false\*(C'\fR), which saves lots of +antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of memory and also speeds up rendering considerably. .IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 .IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" @@ -697,16 +728,8 @@ .Ve .IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 .IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" -Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a -server that answers @@RXVT_NAME@@c's requests, so it doesn't background -itself. -.Sp -To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the -following method to wait for the startup message before continuing: -.Sp -.Vb 1 -\& { @@RXVT_NAME@@d & } | read -.Ve +Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the +display, create the listening socket and then fork. .IP "What's with the strange Backspace/Delete key behaviour?" 4 .IX Item "What's with the strange Backspace/Delete key behaviour?" Assuming that the physical Backspace key corresponds to the