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

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.65 by root, Thu Jan 19 13:04:12 2012 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,
     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 libAfterImage or
+    That works. If you think it doesn't, you lack GDK-PixBuf support, or you
-    GDK-PixBuf support, or you are unable to read.
+    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".
     It is possible to toggle between "^H" and "^?" with the DECBKM private
     mode:
        # use Backspace = ^H
        $ stty erase ^H
-       $ echo -n "^[[?67h"
+       $ printf "\e[?67h"
        # use Backspace = ^?
        $ stty erase ^?
-       $ echo -n "^[[?67l"
+       $ printf "\e[?67l"
     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.
        REMOTE=remotesystem.domain
        infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
     One some systems you might need to set $TERMINFO to the full path of
-    $HOME/.terminfo for this to work. Debian systems have a broken tic which
+    $HOME/.terminfo for this to work.
-    will not be able to overwrite the existing rxvt-unicode terminfo entry -
-    you might have to manually delete all traces of rxvt-unicode* from
-    /etc/terminfo.
     If you cannot or do not want to do this, then you can simply set
     "TERM=rxvt" or even "TERM=xterm", and live with the small number of
     problems arising, which includes wrong keymapping, less and different
     colours and some refresh errors in fullscreen applications. It's a nice
    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/pkg/rxvt-unicode.html>) 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.65 by root, Thu Jan 19 13:04:12 2012 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.65 by root, Thu Jan 19 13:04:12 2012 UTC vs.
Revision 1.70 by root, Fri Dec 26 22:52:22 2014 UTC