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

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.59 by sf-exg, Sat Jul 24 14:20:48 2010 UTC vs.
Revision 1.70 by root, Fri Dec 26 22:52:22 2014 UTC

     Before sending me mail, you could go to IRC: "irc.freenode.net", channel
     "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be
     interested in learning about new and exciting problems (but not FAQs :).
    I use Gentoo, and I have a problem...
-    There are three big problems with Gentoo Linux: first of all, most if
+    There are two big problems with Gentoo Linux: first, most if not all
-    not all Gentoo systems are completely broken (missing or mismatched
+    Gentoo systems are completely broken (missing or mismatched header
-    header files, broken compiler etc. are just the tip of the iceberg);
+    files, broken compiler etc. are just the tip of the iceberg); secondly,
-    secondly, the Gentoo maintainer thinks it is a good idea to add broken
+    it should be called Gentoo GNU/Linux.
-    patches to the code; and lastly, it should be called Gentoo GNU/Linux.
     For these reasons, it is impossible to support rxvt-unicode on Gentoo.
     Problems appearing on Gentoo systems will usually simply be ignored
     unless they can be reproduced on non-Gentoo systems.
        # Bourne/Korn/POSIX family of shells:
        [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
        if [ ${TERM:-foo} = xterm ]; then
           stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
-          echo -n '^[Z'
+          printf "\eZ"
           read term_id
           stty icanon echo
           if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
-             echo -n '^[[7n'        # query the rxvt we are in for the DISPLAY string
+             printf '\e[7n'        # query the rxvt we are in for the DISPLAY string
-             read DISPLAY           # set it in our local shell
+             read DISPLAY          # set it in our local shell
           fi
        fi
    How do I compile the manual pages on my own?
     You need to have a recent version of perl installed as /usr/bin/perl,
     the case of rxvt-unicode this hardly matters, as its portability limits
     are defined by things like X11, pseudo terminals, locale support and
     unix domain sockets, which are all less portable than C++ itself.
     Regarding the bloat, see the above question: It's easy to write programs
-    in C that use gobs of memory, an certainly possible to write programs in
+    in C that use gobs of memory, and certainly possible to write programs
-    C++ that don't. C++ also often comes with large libraries, but this is
+    in C++ that don't. C++ also often comes with large libraries, but this
-    not necessarily the case with GCC. Here is what rxvt links against on my
+    is not necessarily the case with GCC. Here is what rxvt links against on
-    system with a minimal config:
+    my system with a minimal config:
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
        libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
        libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
        /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
     No large bloated libraries (of course, none were linked in statically),
     except maybe libX11 :)
   Rendering, Font & Look and Feel Issues
    I can't get transparency working, what am I doing wrong?
-    First of all, please address all transparency related issues to Sasha
+    First of all, transparency isn't officially supported in rxvt-unicode,
-    Vasko at sasha@aftercode.net and do not bug the author about it. Also,
+    so you are mostly on your own. Do not bug the author about it (but you
-    if you can't get it working consider it a rite of passage: ... and you
+    may bug everybody else). Also, if you can't get it working consider it a
-    failed.
+    rite of passage: ... and you failed.
     Here are four ways to get transparency. Do read the manpage and option
     descriptions for the programs mentioned and rxvt-unicode. Really, do it!
     1. Use transparent mode:
        Esetroot wallpaper.jpg
        urxvt -tr -tint red -sh 40
     That works. If you think it doesn't, you lack transparency and tinting
-    support, or you are unable to read.
+    support, or you are unable to read. This method requires that the
+    background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID
+    property. Compatible programs are Esetroot, hsetroot and feh.
     2. Use a simple pixmap and emulate pseudo-transparency. This enables you
     to use effects other than tinting and shading: Just shade/tint/whatever
     your picture with gimp or any other tool:
        convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
        urxvt -pixmap "background.jpg;:root"
-    That works. If you think it doesn't, you lack AfterImage support, or you
+    That works. If you think it doesn't, you lack GDK-PixBuf support, or you
     are unable to read.
     3. Use an ARGB visual:
        urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
     You can permanently switch this feature off by disabling the "readline"
     extension:
        URxvt.perl-ext-common: default,-readline
-   My numerical keypad acts weird and generates differing output?
+   My numeric keypad acts weird and generates differing output?
-    Some Debian GNUL/Linux users seem to have this problem, although no
+    Some Debian GNU/Linux users seem to have this problem, although no
     specific details were reported so far. It is possible that this is
     caused by the wrong "TERM" setting, although the details of whether and
     how this can happen are unknown, as "TERM=rxvt" should offer a
     compatible keymap. See the answer to the previous question, and please
     report if that helped.
    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
+    correctly, or you specified a preeditType 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 keys) does not
     support this (for instance because it is not visual), then rxvt-unicode
     will continue without an input method.
-    In this case either do not specify a preeditStyle or specify more than
+    In this case either do not specify a preeditType or specify more than
     one pre-edit style, such as OverTheSpot,Root,None.
     If it still doesn't work, then maybe your input method doesn't support
     compose sequences - to fall back to the built-in one, make sure you
     don't specify an input method via "-im" or "XMODIFIERS".
     other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
     escape character and so on.
    Mouse cut/paste suddenly no longer works.
     Make sure that mouse reporting is actually turned off since killing some
-    editors prematurely may leave the mouse in mouse report mode. I've heard
+    editors prematurely may leave it active. I've heard that tcsh may use
-    that tcsh may use mouse reporting unless it otherwise specified. A quick
+    mouse reporting unless it is otherwise specified. A quick check is to
-    check is to see if cut/paste works when the Alt or Shift keys are
+    see if cut/paste works when the Alt or Shift keys are pressed.
-    depressed.
    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 Backspace: "^H" and "^?".
     Historically, either value is correct, but rxvt-unicode adopts the
     debian policy of using "^?" when unsure, because it's the one and only
     correct choice :).
-    Rxvt-unicode tries to inherit the current stty settings and uses the
+    It is possible to toggle between "^H" and "^?" with the DECBKM private
-    value of `erase' to guess the value for backspace. If rxvt-unicode
+    mode:
-    wasn't started from a terminal (say, from a menu or by remote shell),
-    then the system value of `erase', which corresponds to CERASE in
-    <termios.h>, will be used (which may not be the same as your stty
-    setting).
-    For starting a new rxvt-unicode:
        # use Backspace = ^H
        $ stty erase ^H
-       $ urxvt
+       $ printf "\e[?67h"
        # use Backspace = ^?
        $ stty erase ^?
-       $ urxvt
+       $ printf "\e[?67l"
-    Toggle with "ESC [ 36 h" / "ESC [ 36 l".
-    For an existing rxvt-unicode:
-       # use Backspace = ^H
-       $ stty erase ^H
-       $ echo -n "^[[36h"
-       # use Backspace = ^?
-       $ stty erase ^?
-       $ echo -n "^[[36l"
     This helps satisfy some of the Backspace discrepancies that occur, but
     if you use Backspace = "^H", make sure that the termcap/terminfo value
     properly reflects that.
     use the `keysym' resource to alter the keystrings associated with
     keysyms.
     Here's an example for a URxvt session started using "urxvt -name URxvt"
+       URxvt.keysym.Prior:         \033[5~
+       URxvt.keysym.Next:          \033[6~
-       URxvt.keysym.Home:          \033[1~
+       URxvt.keysym.Home:          \033[7~
-       URxvt.keysym.End:           \033[4~
+       URxvt.keysym.End:           \033[8~
-       URxvt.keysym.C-apostrophe:  \033<C-'>
-       URxvt.keysym.C-slash:       \033<C-/>
-       URxvt.keysym.C-semicolon:   \033<C-;>
-       URxvt.keysym.C-grave:       \033<C-`>
-       URxvt.keysym.C-comma:       \033<C-,>
-       URxvt.keysym.C-period:      \033<C-.>
-       URxvt.keysym.C-0x60:        \033<C-`>
-       URxvt.keysym.C-Tab:         \033<C-Tab>
-       URxvt.keysym.C-Return:      \033<C-Return>
-       URxvt.keysym.S-Return:      \033<S-Return>
-       URxvt.keysym.S-space:       \033<S-Space>
-       URxvt.keysym.M-Up:          \033<M-Up>
+       URxvt.keysym.Up:            \033[A
-       URxvt.keysym.M-Down:        \033<M-Down>
+       URxvt.keysym.Down:          \033[B
+       URxvt.keysym.Right:         \033[C
-       URxvt.keysym.M-Left:        \033<M-Left>
+       URxvt.keysym.Left:          \033[D
-       URxvt.keysym.M-Right:       \033<M-Right>
-       URxvt.keysym.M-C-0:         list \033<M-C- 0123456789 >
-       URxvt.keysym.M-C-a:         list \033<M-C- abcdefghijklmnopqrstuvwxyz >
-       URxvt.keysym.F12:           command:\033]701;zh_CN.GBK\007
     See some more examples in the documentation for the keysym resource.
    I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map
        KP_Insert == Insert
     keeping a very small window. If somebody pastes something complicated
     (e.g. japanese), I temporarily switch to a larger font.
     The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
     "xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
-    file for different hosts, for example, on ym main desktop, I use:
+    file for different hosts, for example, on my main desktop, I use:
        URxvt.keysym.C-M-q: command:\033[3;5;5t
        URxvt.keysym.C-M-y: command:\033[3;5;606t
        URxvt.keysym.C-M-e: command:\033[3;1605;5t
        URxvt.keysym.C-M-c: command:\033[3;1605;606t
    Why doesn't vim/emacs etc. make use of italic?
     See next entry.
    Why are the secondary screen-related options not working properly?
     Make sure you are using "TERM=rxvt-unicode". Some pre-packaged
-    distributions (most notably Debian GNU/Linux) break rxvt-unicode by
+    distributions break rxvt-unicode by setting "TERM" to "rxvt", which
-    setting "TERM" to "rxvt", which doesn't have these extra features.
+    doesn't have these extra features. Unfortunately, some of these
-    Unfortunately, some of these (most notably, again, Debian GNU/Linux)
     furthermore fail to even install the "rxvt-unicode" terminfo file, so
     you will need to install it on your own (See the question When I log-in
     to another system it tells me about missing terminfo data? on how to do
     this).
         For scim, use "@im=SCIM". You can see what input method servers are
         running with this command:
            xprop -root XIM_SERVERS
    My input method wants <some encoding> but I want UTF-8, what can I do?
     You can specify separate locales for the input method and the rest of
     the terminal, using the resource "imlocale":
        URxvt.imlocale: ja_JP.EUC-JP
     cannot be completely avoided even if both sides cooperate.
     So the only workaround is not to kill your Input Method Servers.
   Operating Systems / Package Maintaining
-   I am using Debian GNU/Linux and have a problem...
-    The Debian GNU/Linux package of rxvt-unicode in sarge contains large
-    patches that considerably change the behaviour of rxvt-unicode (but
-    unfortunately this notice has been removed). 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
-    probably should use the Debian BTS, too, because, after all, it's also a
-    bug in the Debian version and it serves as a reminder for other users
-    that might encounter the same issue.
    I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
     You should build one binary with the default options. configure now
     enables most useful options, and the trend goes to making them
     runtime-switchable, too, so there is usually no drawback to enabling
     them, except higher disk and possibly memory usage. The perl interpreter

Diff Legend

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

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.59 by sf-exg, Sat Jul 24 14:20:48 2010 UTC vs. Revision 1.70 by root, Fri Dec 26 22:52:22 2014 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.59 by sf-exg, Sat Jul 24 14:20:48 2010 UTC vs.
Revision 1.70 by root, Fri Dec 26 22:52:22 2014 UTC