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

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.57 by root, Wed Dec 30 06:14:03 2009 UTC vs.
Revision 1.60 by root, Fri Oct 15 21:30:51 2010 UTC

     This tries to create a new terminal, and if fails with exit status 2,
     meaning it couldn't connect to the daemon, it will start the daemon and
     re-run the command. Subsequent invocations of the script will re-use the
     existing daemon.
-   How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
+   How do I distinguish whether I'm running rxvt-unicode or a regular
+xterm? I need this to decide about setting colours etc.
     The original rxvt and rxvt-unicode always export the variable
     "COLORTERM", so you can check and see if that is set. Note that several
     programs, JED, slrn, Midnight Commander automatically check this
-    variable to decide whether or not to use color.
+    variable to decide whether or not to use colour.
    How do I set the correct, full IP address for the DISPLAY variable?
     If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
     insecure mode then it is possible to use the following shell script
     snippets to correctly set the display. If your version of rxvt-unicode
     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 libAfterImage or
-    are unable to read.
+    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
     For the standard background colour, blinking will actually make the text
     blink when compiled with "--enable-text-blink". Without
     "--enable-text-blink", the blink attribute will be ignored.
     On ANSI colours, bold/blink attributes are used to set high-intensity
-    foreground/background colors.
+    foreground/background colours.
-    color0-7 are the low-intensity colors.
+    color0-7 are the low-intensity colours.
-    color8-15 are the corresponding high-intensity colors.
+    color8-15 are the corresponding high-intensity colours.
-   I don't like the screen colors.  How do I change them?
+   I don't like the screen colours.  How do I change them?
-    You can change the screen colors at run-time using ~/.Xdefaults
+    You can change the screen colours at run-time using ~/.Xdefaults
     resources (or as long-options).
     Here are values that are supposed to resemble a VGA screen, including
     the murky brown that passes for low-intensity yellow:
        URxvt.color12:  #0000FF
        URxvt.color13:  #FF00FF
        URxvt.color14:  #00FFFF
        URxvt.color15:  #FFFFFF
-    And here is a more complete set of non-standard colors.
+    And here is a more complete set of non-standard colours.
        URxvt.cursorColor:  #dc74d1
        URxvt.pointerColor: #dc74d1
        URxvt.background:   #0e0e0e
        URxvt.foreground:   #4ad5e1
     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
+       $ echo -n "^[[?67h"
        # use Backspace = ^?
        $ stty erase ^?
-       $ urxvt
-    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"
+       $ echo -n "^[[?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.
     develop for myself mostly, so I actually use most of the extensions I
     write.
     The selection stuff mainly makes the selection perl-error-message aware
     and tells it to convert perl error messages into vi-commands to load the
-    relevant file and go tot he error line number.
+    relevant file and go to the error line number.
        URxvt.scrollstyle:      plain
        URxvt.secondaryScroll:  true
     As the documentation says: plain is the preferred scrollbar for the
     my purposes, it works, and gives a different look, as my normal
     (Non-bold) font is already bold, and I want to see a difference between
     bold and normal fonts.
     Please note that I used the "urxvt" instance name and not the "URxvt"
-    class name. Thats because I use different configs for different
+    class name. That is because I use different configs for different
     purposes, for example, my IRC window is started with "-name IRC", and
     uses these defaults:
        IRC*title:              IRC
        IRC*geometry:           87x12+535+542
     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
     runtime-switchable, too, so there is usually no drawback to enabling
     them, except higher disk and possibly memory usage. The perl interpreter
     should be enabled, as important functionality (menus, selection, likely
     more in the future) depends on it.
-    You should not overwrite the "perl-ext-common" snd "perl-ext" resources
+    You should not overwrite the "perl-ext-common" and "perl-ext" resources
     system-wide (except maybe with "defaults"). This will result in useful
     behaviour. If your distribution aims at low memory, add an empty
     "perl-ext-common" resource to the app-defaults file. This will keep the
     perl interpreter disabled until the user enables it.
     The solution is to upgrade your system or switch to a better one. A
     possibly working workaround is to use a wcwidth implementation like
     http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
-   I want 256 colors
-    Are you sure you need 256 colors? 88 colors should be enough for most
-    purposes. If you really need more, there is an unsupported patch for it
-    in the doc directory, but please do not ask for it to be applied.

Diff Legend

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

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.57 by root, Wed Dec 30 06:14:03 2009 UTC vs. Revision 1.60 by root, Fri Oct 15 21:30:51 2010 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.57 by root, Wed Dec 30 06:14:03 2009 UTC vs.
Revision 1.60 by root, Fri Oct 15 21:30:51 2010 UTC