[ViewVC] Diff of: cvs/rxvt-unicode/README.FAQ

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.11 by root, Mon Feb 14 18:47:54 2005 UTC vs.
Revision 1.17 by root, Wed Aug 10 01:44:35 2005 UTC

     How do I know which rxvt-unicode version I'm using?
         The version number is displayed with the usage (-h). Also the escape
         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
+        The Debian GNU/Linux package of rxvt-unicode in sarge contains large
-        that considerably change the behaviour of rxvt-unicode. Before
+        patches that considerably change the behaviour of rxvt-unicode.
-        reporting a bug to the original rxvt-unicode author please download
+        Before reporting a bug to the original rxvt-unicode author please
-        and install the genuine version
+        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).
            URxvt.termName: rxvt
         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
         operating systems still compile some programs using the
         long-obsoleted termcap library (Fedora Core's bash is one example)
            rxvt-unicode|rxvt-unicode terminal (X Window System):\
                    :am:bw:eo:km:mi:ms:xn:xo:\
                    :co#80:it#8:li#24:lm#0:\
                    :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
                    :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
-                   :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\
+                   :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
-                   :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\
+                   :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
-                   :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\
+                   :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
-                   :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\
+                   :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
+                   :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
-                   :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
+                   :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
                    :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
                    :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
                    :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
                    :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
                    :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
         that doesn't work, you might be forced to use a different font.
         All of this is not a problem when using X11 core fonts, as their
         bounding box data is correct.
+    On Solaris 9, many line-drawing characters are too wide.
+        Seems to be a known bug, read
+        <http://nixdoc.net/files/forum/about34198.html>. Some people use the
+        following ugly workaround to get non-double-wide-characters working:
+           #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
     My Compose (Multi_key) key is no longer working.
         The most common causes for this are that either your locale is not
         set correctly, or you specified a preeditStyle that is not supported
         by your input method. For example, if you specified OverTheSpot and
         your input method (e.g. the default input method handling Compose
         As you might have guessed, FreeBSD does neither define this symobl
         nor does it support it. Instead, it uses it's own internal
         representation of wchar_t. This is, of course, completely fine with
         respect to standards.
+        However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
+        and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
-        However, "__STDC_ISO_10646__" is the only sane way to support
+        "__STDC_ISO_10646__" is the only sane way to support multi-language
-        multi-language apps in an OS, as using a locale-dependent (and
+        apps in an OS, as using a locale-dependent (and non-standardized)
-        non-standardized) representation of wchar_t makes it impossible to
+        representation of wchar_t makes it impossible to convert between
-        convert between wchar_t (as used by X11 and your applications) and
+        wchar_t (as used by X11 and your applications) and any other
-        any other encoding without implementing OS-specific-wrappers for
+        encoding without implementing OS-specific-wrappers for each and
-        each and every locale. There simply are no APIs to convert wchar_t
+        every locale. There simply are no APIs to convert wchar_t into
-        into anything except the current locale encoding.
+        anything except the current locale encoding.
         Some applications (such as the formidable mlterm) work around this
         by carrying their own replacement functions for character set
         handling with them, and either implementing OS-dependent hacks or
         doing multiple conversions (which is slow and unreliable in case the
         emulator).
         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 :)
+    I use Solaris 9 and it doesn't compile/work/etc.
+        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,
         and no specific "utf-8" mode, such as xterm. In fact, it doesn't
         it gets worse, as rxvt-unicode then uses 8 bytes per screen cell.
     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 ":antialiasing=false"), which
+        disable antialiasing (by appending ":antialias=false"), which saves
-        saves lots of memory and also speeds up rendering considerably.
+        lots of memory and also speeds up rendering considerably.
     Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
         Rxvt-unicode will use whatever you specify as a font. If it needs to
         fall back to it's default font search list it will prefer X11 core
         fonts, because they are small and fast, and then use Xft fonts. It
            URxvt.color14:      #73f7ff
            URxvt.color7:       #e1dddd
            URxvt.color15:      #e1dddd
     How can I start rxvtd in a race-free way?
-        Despite it's name, rxvtd is not a real daemon, but more like a
+        Try "rxvtd -f -o", which tells rxvtd to open the display, create the
-        server that answers rxvtc's requests, so it doesn't background
+        listening socket and then fork.
-        itself.
-        To ensure rxvtd is listening on it's socket, you can use the
-        following method to wait for the startup message before continuing:
-          { rxvtd & } | read
     What's with the strange Backspace/Delete key behaviour?
         Assuming that the physical Backspace key corresponds to the
         BackSpace keysym (not likely for Linux ... see the following
         question) there are two standard values that can be used for

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.11 by root, Mon Feb 14 18:47:54 2005 UTC vs. Revision 1.17 by root, Wed Aug 10 01:44:35 2005 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.11 by root, Mon Feb 14 18:47:54 2005 UTC vs.
Revision 1.17 by root, Wed Aug 10 01:44:35 2005 UTC