--- rxvt-unicode/README.FAQ	2006/01/02 15:11:05	1.21
+++ rxvt-unicode/README.FAQ	2006/01/16 14:48:39	1.29
@@ -1,4 +1,44 @@
 FREQUENTLY ASKED QUESTIONS
+    The new selection selects pieces that are too big, how can I select
+    single words?
+        Yes. For example, if you want to select alphanumeric words, you can
+        use the following resource:
+
+           URxvt.selection.pattern-0: ([[:word:]]+)
+
+        If you click more than twice, the selection will be extended more
+        and more.
+
+        To get a selection that is very similar to the old code, try this
+        pattern:
+
+           URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
+
+        Please also note that the *LeftClick Shift-LeftClik* combination
+        also selects words like the old code.
+
+    I don't like the new selection/popups/hotkeys/perl, how do I
+    change/disable it?
+        You can disable the perl extension completely by setting the
+        perl-ext-common resource to the empty string, which also keeps
+        rxvt-unicode from initialising perl, saving memory.
+
+        If you only want to disable specific features, you first have to
+        identify which perl extension is responsible. For this, read the
+        section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For
+        example, to disable the selection-popup and option-popup, specify
+        this perl-ext-common resource:
+
+           URxvt.perl-ext-common: default,-selection-popup,-option-popup
+
+        This will keep the default extensions, but disable the two popup
+        extensions. Some extensions can also be configured, for example,
+        scrollback search mode is triggered by M-s. You can move it to any
+        other combination either by setting the searchable-scrollback
+        resource:
+
+           URxvt.searchable-scrollback: CM-s
+
     Isn't rxvt supposed to be small? Don't all those features bloat?
         I often get asked about this, and I think, no, they didn't cause
         extra bloat. If you compare a minimal rxvt and a minimal urxvt, you
@@ -37,7 +77,7 @@
         this still fares rather well. And compared to some monsters like
         gnome-terminal (21152k + extra 4204k in separate processes) or
         konsole (22200k + extra 43180k in daemons that stay around after
-        exit, plus half aminute of startup time, including the hundreds of
+        exit, plus half a minute of startup time, including the hundreds of
         warnings it spits out), it fares extremely well *g*.
 
     Why C++, isn't that unportable/bloated/uncool?
@@ -103,6 +143,49 @@
         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 enbaling
+        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 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.
+
+        If you can/want build more binaries, I recommend building a minimal
+        one with "--disable-everything" (very useful) and a maximal one with
+        "--enable-everything" (less useful, it will be very big due to a lot
+        of encodings built-in that increase download times and are rarely
+        used).
+
+    I need to make it setuid/setgid to support utmp/ptys on my OS, is this
+    safe?
+        Likely not. While I honestly try to make it secure, and am probably
+        not bad at it, I think it is simply unreasonable to expect all of
+        freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode
+        itself to all be secure. Also, rxvt-unicode disables some options
+        when it detects that it runs setuid or setgid, which is not nice.
+        Besides, with the embedded perl interpreter the possibility for
+        security problems easily multiplies.
+
+        Elevated privileges are only required for utmp and pty operations on
+        some systems (for example, GNU/Linux doesn't need any extra
+        privileges for ptys, but some need it for utmp support). It is
+        planned to mvoe this into a forked handler process, but this is not
+        yet done.
+
+        So, while setuid/setgid operation is supported and not a problem on
+        your typical single-user-no-other-logins unix desktop, always
+        remember that its an awful lot of code, most of which isn't checked
+        for security issues regularly.
+
     When I log-in to another system it tells me about missing terminfo data?
         The terminal description used by rxvt-unicode is not as widely
         available as that for xterm, or even rxvt (for which the same
@@ -552,7 +635,7 @@
         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. See rxvt(7)
+        or Shift keys are depressed.
 
     What's with this bold/blink stuff?
         If no bold colour is set via "colorBD:", bold will invert text using
@@ -648,7 +731,7 @@
            $ stty erase ^?
            $ rxvt
 
-        Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
+        Toggle with "ESC [ 36 h" / "ESC [ 36 l".
 
         For an existing rxvt-unicode: