[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.7.txt

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents):
Revision 1.33 by root, Wed Jan 4 21:50:12 2006 UTC vs.
Revision 1.40 by root, Thu Jan 12 05:37:34 2006 UTC

     The newest version of this document is also available on the World Wide
     Web at
     <http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
 FREQUENTLY ASKED QUESTIONS
+    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
         can see that the urxvt binary is larger (due to some encoding tables
         always being compiled in), but it actually uses less memory (RSS)
         Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k),
         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?
         Is this a question? :) It comes up very often. The simple answer is:
         I had to write it, and C++ allowed me to write and maintain it in a
         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 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
         problem often arises).
            Ps = 10         Change colour of text foreground to Pt (NB: may change in future)
            Ps = 11         Change colour of text background to Pt (NB: may change in future)
            Ps = 12         Change colour of text cursor foreground to Pt
            Ps = 13         Change colour of mouse foreground to Pt
            Ps = 17         Change colour of highlight characters to Pt
-           Ps = 18         Change colour of bold characters to Pt
+           Ps = 18         Change colour of bold characters to Pt [deprecated, see 706]
-           Ps = 19         Change colour of underlined characters to Pt
+           Ps = 19         Change colour of underlined characters to Pt [deprecated, see 707]
            Ps = 20         Change default background to Pt
            Ps = 39         Change default foreground colour to Pt.
            Ps = 46         Change Log File to Pt unimplemented
            Ps = 49         Change default background colour to Pt.
            Ps = 50         Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n
            Ps = 55         Log all scrollback buffer and all of screen to Pt
            Ps = 701        Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
            Ps = 703        Menubar command Pt (Compile menubar).
            Ps = 704        Change colour of italic characters to Pt
            Ps = 705        Change background pixmap tint colour to Pt (Compile transparency).
+           Ps = 706        Change colour of bold characters to Pt
+           Ps = 707        Change colour of underlined characters to Pt
            Ps = 710        Set normal fontset to Pt. Same as Ps = 50.
            Ps = 711        Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
            Ps = 712        Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).
            Ps = 713        Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
            Ps = 720        Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
     --enable-lastlog (default: on)
         Write user and tty to lastlog file (used by programs like lastlogin)
         at start of rxvt execution. This option requires --enable-utmp to
         also be specified.
-    --enable-xpm-background (default: off)
+    --enable-xpm-background (default: on)
         Add support for XPM background pixmaps.
-    --enable-transparency (default: off)
+    --enable-transparency (default: on)
         Add support for inheriting parent backgrounds thus giving a fake
         transparency to the term.
     --enable-fading (default: on)
         Add support for fading the text when focus is lost (requires
     --enable-tinting (default: on)
         Add support for tinting of transparent backgrounds (requires
         "--enable-transparency").
-    --enable-menubar (default: off)
+    --enable-menubar (default: off) [DEPRECATED]
         Add support for our menu bar system (this interacts badly with
-        dynamic locale switching currently).
+        dynamic locale switching currently). This option is DEPRECATED and
+        will be removed in the future.
     --enable-rxvt-scroll (default: on)
         Add support for the original rxvt scrollbar.
     --enable-next-scroll (default: on)
         Removes any handling of the delete key by us - let the X server do
         it.
     --disable-resources
         Removes any support for resource checking.
-    --enable-xgetdefault
-        Make resources checking via XGetDefault() instead of our small
-        version which only checks ~/.Xdefaults, or if that doesn't exist
-        then ~/.Xresources.
-        Please note that nowadays, things like XIM will automatically pull
-        in and use the full X resource manager, so the overhead of using it
-        might be very small, if nonexistant.
     --enable-strings (default: off)
         Add support for our possibly faster memset() function and other
         various routines, overriding your system's versions which may have
         been hand-crafted in assembly or may require extra libraries to link

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents): Revision 1.33 by root, Wed Jan 4 21:50:12 2006 UTC vs. Revision 1.40 by root, Thu Jan 12 05:37:34 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents):
Revision 1.33 by root, Wed Jan 4 21:50:12 2006 UTC vs.
Revision 1.40 by root, Thu Jan 12 05:37:34 2006 UTC