--- rxvt-unicode/doc/rxvt.7.man.in 2005/02/14 10:44:50 1.14 +++ rxvt-unicode/doc/rxvt.7.man.in 2005/07/13 02:53:54 1.22 @@ -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-14" "" "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 @@ 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@@." @@ -216,8 +222,8 @@ .PD One reason you might want this is that some distributions or operating systems still compile some programs using the long-obsoleted termcap -(Fedora Core's bash is one example) and rely on a termcap entry for -\&\f(CW\*(C`rxvt\-unicode\*(C'\fR. +library (Fedora Core's bash is one example) and rely on a termcap entry +for \f(CW\*(C`rxvt\-unicode\*(C'\fR. .Sp You could use rxvt's termcap entry with resonable results in many cases. You can also create a termcap entry by using terminfo's infocmp program @@ -229,25 +235,26 @@ .Sp Or you could use this termcap entry, generated by the command above: .Sp -.Vb 19 +.Vb 20 \& rxvt-unicode|rxvt-unicode terminal (X Window System):\e \& :am:bw:eo:km:mi:ms:xn:xo:\e -\& :co#80:it#8:li#24:\e +\& :co#80:it#8:li#24:lm#0:\e \& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e \& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e -\& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=^O:al=\eE[L:\e -\& :as=^N:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:cm=\eE[%i%d;%dH:\e -\& :cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:dl=\eE[M:do=^J:\e -\& :ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:\e -\& :im=\eE[4h:is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e -\& :k0=\eE[21~:k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:\e -\& :k5=\eE[15~:k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:\e -\& :kD=\eE[3~:kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:\e -\& :ke=\eE[?1l\eE>:kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:\e -\& :ku=\eEOA:le=^H:mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:\e -\& :nd=\eE[C:rc=\eE8:sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:\e -\& :st=\eEH:ta=^I:te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:\e -\& :up=\eE[A:us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e +\& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=\eE(B:al=\eE[L:\e +\& :as=\eE(0:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:\e +\& :cm=\eE[%i%d;%dH:cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:\e +\& :dl=\eE[M:do=^J:ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:\e +\& :i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:im=\eE[4h:\e +\& :is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e +\& :k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:k5=\eE[15~:\e +\& :k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:kD=\eE[3~:\e +\& :kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:ke=\eE[?1l\eE>:\e +\& :kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:ku=\eEOA:le=^H:\e +\& :mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:nd=\eE[C:rc=\eE8:\e +\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e +\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e +\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e \& :vs=\eE[?25h: .Ve .ie n .IP "Why does ""ls"" no longer have coloured output?" 4 @@ -407,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 @@ -458,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 @@ -475,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 @@ -1614,19 +1649,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 @@ -2186,12 +2223,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 @@ -2343,18 +2381,20 @@ A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly in combination with other switches) is: .Sp -.Vb 11 +.Vb 13 \& MWM-hints +\& EWMH-hints (pid, utf8 names) and protocols (ping) \& seperate underline colour \& settable border widths and borderless switch \& settable extra linespacing -\& extra window properties (e.g. UTF-8 window names and PID) \& 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 .IX Item "--enable-iso14755" @@ -2395,9 +2435,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.