--- rxvt-unicode/README.FAQ	2010/12/13 16:47:27	1.63
+++ rxvt-unicode/README.FAQ	2012/09/09 12:21:25	1.67
@@ -93,12 +93,12 @@
        [ ${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
-             read DISPLAY           # set it in our local shell
+             printf '\e[7n'        # query the rxvt we are in for the DISPLAY string
+             read DISPLAY          # set it in our local shell
           fi
        fi
 
@@ -208,8 +208,8 @@
        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
-    GDK-PixBuf support, or you are unable to read.
+    That works. If you think it doesn't, you lack GDK-PixBuf support, or you
+    are unable to read.
 
     3. Use an ARGB visual:
 
@@ -516,10 +516,9 @@
 
    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
-    that tcsh may use mouse reporting unless it otherwise specified. A quick
-    check is to see if cut/paste works when the Alt or Shift keys are
-    depressed.
+    editors prematurely may leave it active. I've heard that tcsh may use
+    mouse reporting unless it is otherwise specified. A quick check is to
+    see if cut/paste works when the Alt or Shift keys are pressed.
 
    What's with the strange Backspace/Delete key behaviour?
     Assuming that the physical Backspace key corresponds to the Backspace
@@ -535,11 +534,11 @@
 
        # 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
@@ -565,26 +564,14 @@
 
     Here's an example for a URxvt session started using "urxvt -name URxvt"
 
-       URxvt.keysym.Home:          \033[1~
-       URxvt.keysym.End:           \033[4~
-       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.M-Down:        \033<M-Down>
-       URxvt.keysym.M-Left:        \033<M-Left>
-       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
+       URxvt.keysym.Prior:         \033[5~
+       URxvt.keysym.Next:          \033[6~
+       URxvt.keysym.Home:          \033[7~
+       URxvt.keysym.End:           \033[8~
+       URxvt.keysym.Up:            \033[A
+       URxvt.keysym.Down:          \033[B
+       URxvt.keysym.Right:         \033[C
+       URxvt.keysym.Left:          \033[D
 
     See some more examples in the documentation for the keysym resource.
 
@@ -789,7 +776,10 @@
        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