--- rxvt-unicode/doc/rxvt.7.man.in 2005/02/20 19:45:30 1.18 +++ 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-02-20" "5.2" "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 @@ -459,13 +474,16 @@ does it support it. Instead, it uses it's own internal representation of \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. .Sp -However, \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support -multi-language apps in an \s-1OS\s0, as using a locale-dependent (and -non\-standardized) representation of \fBwchar_t\fR makes it impossible to -convert between \fBwchar_t\fR (as used by X11 and your applications) and any -other encoding without implementing OS-specific-wrappers for each and -every locale. There simply are no APIs to convert \fBwchar_t\fR into anything -except the current locale encoding. +However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and +\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. +.Sp +\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language +apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) +representation of \fBwchar_t\fR makes it impossible to convert between +\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding +without implementing OS-specific-wrappers for each and every locale. There +simply are no APIs to convert \fBwchar_t\fR into anything except the current +locale encoding. .Sp Some applications (such as the formidable \fBmlterm\fR) work around this by carrying their own replacement functions for character set handling @@ -476,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 @@ -605,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?" @@ -694,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 @@ -1615,19 +1641,21 @@ Ps = 18 Change colour of bold characters to Pt Ps = 19 Change colour of underlined characters to Pt Ps = 20 Change default background to Pt -Ps = 39 Change default foreground colour to Pt rxvt compile-time option +Ps = 39 Change default foreground colour to Pt. Ps = 46 Change Log File to Pt unimplemented -Ps = 49 Change default background colour to Pt rxvt compile-time option +Ps = 49 Change default background colour to Pt. Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n Ps = 55 Log all scrollback buffer and all of screen to Pt -Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (@@RXVT_NAME@@ extension) -Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) +Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). +Ps = 703 Menubar command Pt (Compile menubar). Ps = 704 Change colour of italic characters to Pt -Ps = 705 Change background pixmap tint colour to Pt +Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). Ps = 710 Set normal fontset to Pt. Same as Ps = 50. -Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. -Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. -Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. +Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles). +Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles). +Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles). +Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). +Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). .TE .PP @@ -2187,12 +2215,13 @@ styles. The fonts can be set manually or automatically. .IP "\-\-with\-codesets=NAME,..." 4 .IX Item "--with-codesets=NAME,..." -Compile in support for additional codeset (encoding) groups (eu, vn are -always compiled in, which includes most 8\-bit character sets). These -codeset tables are currently only used for driving X11 core fonts, they -are not required for Xft fonts. Compiling them in will make your binary -bigger (together about 700kB), but it doesn't increase memory usage unless -you use an X11 font requiring one of these encodings. +Compile in support for additional codeset (encoding) groups (\f(CW\*(C`eu\*(C'\fR, \f(CW\*(C`vn\*(C'\fR +are always compiled in, which includes most 8\-bit character sets). These +codeset tables are used for driving X11 core fonts, they are not required +for Xft fonts, although having them compiled in lets rxvt-unicode choose +replacement fonts more intelligently. Compiling them in will make your +binary bigger (all of together cost about 700kB), but it doesn't increase +memory usage unless you use a font requiring one of these encodings. .TS l l . all all available codeset groups @@ -2344,7 +2373,7 @@ A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly in combination with other switches) is: .Sp -.Vb 12 +.Vb 13 \& MWM-hints \& EWMH-hints (pid, utf8 names) and protocols (ping) \& seperate underline colour @@ -2352,10 +2381,11 @@ \& settable extra linespacing \& iso-14755-2 and -3, and visual feedback \& backindex and forwardindex escape sequence -\& window op and locale change escape sequences +\& window op and some xterm/OSC escape sequences \& tripleclickwords \& settable insecure mode \& keysym remapping support +\& cursor blinking and underline cursor \& -embed and -pty-fd options .Ve .IP "\-\-enable\-iso14755" 4 @@ -2397,9 +2427,6 @@ Add smart growth/shrink behaviour when changing font size via from hot keys. This should keep in a fixed position the rxvt corner which is closest to a corner of the screen. -.IP "\-\-enable\-cursor\-blink" 4 -.IX Item "--enable-cursor-blink" -Add support for a blinking cursor. .IP "\-\-enable\-pointer\-blank" 4 .IX Item "--enable-pointer-blank" Add support to have the pointer disappear when typing or inactive.