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

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.62 by root, Thu Dec 9 10:36:51 2010 UTC vs.
Revision 1.67 by root, Sun Sep 9 12:21:25 2012 UTC

        # 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
     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 "^?".
     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.
     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
        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.
+    $HOME/.terminfo for this to work. Debian systems have a broken tic which
+    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
    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
+    version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to
-    the problem. If you cannot, chances are that the problems are specific
+    reproduce the problem. If you cannot, chances are that the problems are
-    to Debian GNU/Linux, in which case it should be reported via the Debian
+    specific to Debian GNU/Linux, in which case it should be reported via
-    Bug Tracking System (use "reportbug" to report the bug).
+    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.

Diff Legend

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

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.62 by root, Thu Dec 9 10:36:51 2010 UTC vs. Revision 1.67 by root, Sun Sep 9 12:21:25 2012 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.62 by root, Thu Dec 9 10:36:51 2010 UTC vs.
Revision 1.67 by root, Sun Sep 9 12:21:25 2012 UTC