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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.48 by root, Thu Feb 17 12:00:33 2005 UTC vs.
Revision 1.73 by root, Mon Jan 9 01:54:43 2006 UTC

 =head1 FREQUENTLY ASKED QUESTIONS
 =over 4
+=item 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) after startup. Even
+with C<--disable-everything>, this comparison is a bit unfair, as many
+features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
+already in use in this mode.
+    text    data     bss     drs     rss filename
+   98398    1664      24   15695    1824 rxvt --disable-everything
+  188985    9048   66616   18222    1788 urxvt --disable-everything
+When you C<--enable-everything> (which _is_ unfair, as this involves xft
+and full locale/XIM support which are quite bloaty inside libX11 and my
+libc), the two diverge, but not unreasnobaly so.
+    text    data     bss     drs     rss filename
+  163431    2152      24   20123    2060 rxvt --enable-everything
+ 1035683   49680   66648   29096    3680 urxvt --enable-everything
+The very large size of the text section is explained by the east-asian
+encoding tables, which, if unused, take up disk space but nothing else
+and can be compiled out unless you rely on X11 core fonts that use those
+encodings. The BSS size comes from the 64k emergency buffer that my c++
+compiler allocates (but of course doesn't use unless you are out of
+memory). Also, using an xft font instead of a core font immediately adds a
+few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
+not used.
+Of course, due to every character using two or four bytes instead of one,
+a large scrollback buffer will ultimately make rxvt-unicode use more
+memory.
+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 warnings it spits out), it fares
+extremely well *g*.
+=item 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 fraction
+of the time and effort (which is a scarce resource for me). Put even
+shorter: It simply wouldn't exist without C++.
+My personal stance on this is that C++ is less portable than C, but in
+the case of rxvt-unicode this hardly matters, as its portability limits
+are defined by things like X11, pseudo terminals, locale support and unix
+domain sockets, which are all less portable than C++ itself.
+Regarding the bloat, see the above question: It's easy to write programs
+in C that use gobs of memory, an certainly possible to write programs in
+C++ that don't. C++ also often comes with large libraries, but this is
+not necessarily the case with GCC. Here is what rxvt links against on my
+system with a minimal config:
+   libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
+   libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
+   libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
+   /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+And here is rxvt-unicode:
+   libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
+   libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
+   libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
+   libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
+   /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+No large bloated libraries (of course, none were linked in statically),
+except maybe libX11 :)
+=item Does it support tabs, can I have a tabbed rxvt-unicode?
+rxvt-unicode does not directly support tabs. It will work fine with
+tabbing functionality of many window managers or similar tabbing programs,
+and its embedding-features allow it to be embedded into other programs,
+as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl
+module, which features a tabbed urxvt (murxvt) terminal as an example
+embedding application.
 =item How do I know which rxvt-unicode version I'm using?
 The version number is displayed with the usage (-h). Also the escape
-sequence C<ESC [ 8 n> sets the window title to the version number.
+sequence C<ESC [ 8 n> sets the window title to the version number. When
+using the @@RXVT_NAME@@c client, the version displayed is that of the
+daemon.
 =item I am using Debian GNU/Linux and have a problem...
-The Debian GNU/Linux package of rxvt-unicode contains large patches that
+The Debian GNU/Linux package of rxvt-unicode in sarge contains large
-considerably change the behaviour of rxvt-unicode. Before reporting a
+patches that considerably change the behaviour of rxvt-unicode. Before
-bug to the original rxvt-unicode author please download and install the
+reporting a bug to the original rxvt-unicode author please download and
-genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to
+install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
-reproduce the problem. If you cannot, chances are that the problems are
+and try to reproduce the problem. If you cannot, chances are that the
-specific to Debian GNU/Linux, in which case it should be reported via the
+problems are specific to Debian GNU/Linux, in which case it should be
-Debian Bug Tracking System (use C<reportbug> to report the bug).
+reported via the Debian Bug Tracking System (use C<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.
+=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
+You should build one binary with the default options. F<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 C<perl-ext-common> snd C<perl-ext> resources
+system-wide (except maybe with C<defaults>). This will result in useful
+behaviour. If your distribution aims at low memory, add an empty
+C<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 C<--disable-everything> (very useful) and a maximal one with
+C<--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).
+=item 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 + ... + 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.
+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). If rxvt-unicode doesn't support
+the library/setuid helper that your OS needs I'll be happy to assist you
+in implementing support for it.
+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.
 =item 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).
    URxvt.termName: rxvt
 If you don't plan to use B<rxvt> (quite common...) you could also replace
 the rxvt terminfo file with the rxvt-unicode one.
+=item C<tic> outputs some error when compiling the terminfo entry.
+Most likely it's the empty definition for C<enacs=>. Just replace it by
+C<enacs=\E[0@> and try again.
 =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@.
 =item I need a termcap file entry.
 might be forced to use a different font.
 All of this is not a problem when using X11 core fonts, as their bounding
 box data is correct.
+=item On Solaris 9, many line-drawing characters are too wide.
+Seems to be a known bug, read
+L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
+following ugly workaround to get non-double-wide-characters working:
+   #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
 =item My Compose (Multi_key) key is no longer working.
 The most common causes for this are that either your locale is not set
 correctly, or you specified a B<preeditStyle> that is not supported by
 your input method. For example, if you specified B<OverTheSpot> and
 As you might have guessed, FreeBSD does neither define this symobl nor
 does it support it. Instead, it uses it's own internal representation of
 B<wchar_t>. This is, of course, completely fine with respect to standards.
+However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
+C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
-However, C<__STDC_ISO_10646__> is the only sane way to support
+C<__STDC_ISO_10646__> is the only sane way to support multi-language
-multi-language apps in an OS, as using a locale-dependent (and
+apps in an OS, as using a locale-dependent (and non-standardized)
-non-standardized) representation of B<wchar_t> makes it impossible to
+representation of B<wchar_t> makes it impossible to convert between
-convert between B<wchar_t> (as used by X11 and your applications) and any
+B<wchar_t> (as used by X11 and your applications) and any other encoding
-other encoding without implementing OS-specific-wrappers for each and
+without implementing OS-specific-wrappers for each and every locale. There
-every locale. There simply are no APIs to convert B<wchar_t> into anything
+simply are no APIs to convert B<wchar_t> into anything except the current
-except the current locale encoding.
+locale encoding.
 Some applications (such as the formidable B<mlterm>) work around this
 by carrying their own replacement functions for character set handling
 with them, and either implementing OS-dependent hacks or doing multiple
 conversions (which is slow and unreliable in case the OS implements
 encodings slightly different than the terminal emulator).
 The rxvt-unicode author insists that the right way to fix this is in the
 system libraries once and for all, instead of forcing every app to carry
 complete replacements for them :)
+=item I use Solaris 9 and it doesn't compile/work/etc.
+Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
+problems with C<wcwidth> and a compile problem.
+=item How can I use rxvt-unicode under cygwin?
+rxvt-unicode should compile and run out of the box on cygwin, using
+the X11 libraries that come with cygwin. libW11 emulation is no
+longer supported (and makes no sense, either, as it only supported a
+single font). I recommend starting the X-server in C<-multiwindow> or
+C<-rootless> mode instead, which will result in similar look&feel as the
+old libW11 emulation.
+At the time of this writing, cygwin didn't seem to support any multi-byte
+encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
+to 8-bit encodings.
 =item How does rxvt-unicode determine the encoding to use?
 =item Is there an option to switch encodings?
 =item Can I speed up Xft rendering somehow?
 Yes, the most obvious way to speed it up is to avoid Xft entirely, as
 it is simply slow. If you still want Xft fonts you might try to disable
-antialiasing (by appending C<:antialiasing=false>), which saves lots of
+antialiasing (by appending C<:antialias=false>), which saves lots of
 memory and also speeds up rendering considerably.
 =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
 Rxvt-unicode will use whatever you specify as a font. If it needs to
    URxvt.color7:       #e1dddd
    URxvt.color15:      #e1dddd
 =item How can I start @@RXVT_NAME@@d in a race-free way?
-Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a
+Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
-server that answers @@RXVT_NAME@@c's requests, so it doesn't background
+display, create the listening socket and then fork.
-itself.
-To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
-following method to wait for the startup message before continuing:
-  { @@RXVT_NAME@@d & } | read
 =item 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
 	B<< C<h> >>	Scroll to bottom when a key is pressed
 	B<< C<l> >>	Don't scroll to bottom when a key is pressed
 =end table
+=item B<< C<Ps = 1021> >> (B<rxvt>)
+=begin table
+	B<< C<h> >>	Bold/italic implies high intensity (see option B<-is>)
+	B<< C<l> >>	Font styles have no effect on intensity (Compile styles)
+=end table
 =item B<< C<Ps = 1047> >>
 =begin table
 	B<< C<h> >>	Use Alternate Screen Buffer
 	B<< C<Ps = 13> >>	Change colour of mouse foreground to B<< C<Pt> >>
 	B<< C<Ps = 17> >>	Change colour of highlight characters to B<< C<Pt> >>
 	B<< C<Ps = 18> >>	Change colour of bold characters to B<< C<Pt> >>
 	B<< C<Ps = 19> >>	Change colour of underlined characters to B<< C<Pt> >>
 	B<< C<Ps = 20> >>	Change default background to B<< C<Pt> >>
-	B<< C<Ps = 39> >>	Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option>
+	B<< C<Ps = 39> >>	Change default foreground colour to B<< C<Pt> >>.
 	B<< C<Ps = 46> >>	Change Log File to B<< C<Pt> >> I<unimplemented>
-	B<< C<Ps = 49> >>	Change default background colour to B<< C<Pt> >> I<rxvt compile-time option>
+	B<< C<Ps = 49> >>	Change default background colour to B<< C<Pt> >>.
 	B<< C<Ps = 50> >>	Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >>
 	B<< C<Ps = 55> >>	Log all scrollback buffer and all of screen to B<< C<Pt> >>
-	B<< C<Ps = 701> >>	Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (@@RXVT_NAME@@ extension)
+	B<< C<Ps = 701> >>	Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills).
-	B<< C<Ps = 703> >>	Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension)
+	B<< C<Ps = 703> >>	Menubar command B<< C<Pt> >> (Compile menubar).
 	B<< C<Ps = 704> >>	Change colour of italic characters to B<< C<Pt> >>
-	B<< C<Ps = 705> >>	Change background pixmap tint colour to B<< C<Pt> >>
+	B<< C<Ps = 705> >>	Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency).
 	B<< C<Ps = 710> >>	Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>.
-	B<< C<Ps = 711> >>	Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
+	B<< C<Ps = 711> >>	Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
-	B<< C<Ps = 712> >>	Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
+	B<< C<Ps = 712> >>	Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
-	B<< C<Ps = 713> >>	Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>.
+	B<< C<Ps = 713> >>	Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles).
+	B<< C<Ps = 720> >>	Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
+	B<< C<Ps = 721> >>	Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills).
+	B<< C<Ps = 777> >>	Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
 =end table
 =back
 =end table
 =head1 CONFIGURE OPTIONS
 General hint: if you get compile errors, then likely your configuration
-hasn't been tested well. Either try with --enable-everything or use the
+hasn't been tested well. Either try with C<--enable-everything> or use
-./reconf script as a base for experiments. ./reconf is used by myself,
+the F<./reconf> script as a base for experiments. F<./reconf> is used by
-so it should generally be a working config. Of course, you should always
+myself, so it should generally be a working config. Of course, you should
-report when a combination doesn't work, so it can be fixed. Marc Lehmann
+always report when a combination doesn't work, so it can be fixed. Marc
-<rxvt@schmorp.de>.
+Lehmann <rxvt@schmorp.de>.
+All
 =over 4
 =item --enable-everything
-Add support for all non-multichoice options listed in "./configure
+Add (or remove) support for all non-multichoice options listed in "./configure
---help". Note that unlike other enable options this is order dependant.
+--help".
-You can specify this and then disable options which this enables by
+You can specify this and then disable options you do not like by
-I<following> this with the appropriate commands.
+I<following> this with the appropriate C<--disable-...> arguments,
+or you can start with a minimal configuration by specifying
+C<--disable-everything> and than adding just the C<--enable-...> arguments
+you want.
-=item --enable-xft
+=item --enable-xft (default: enabled)
 Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
 slower and require lots of memory, but as long as you don't use them, you
 don't pay for them.
-=item --enable-font-styles
+=item --enable-font-styles (default: on)
 Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
 styles. The fonts can be set manually or automatically.
-=item --with-codesets=NAME,...
+=item --with-codesets=NAME,... (default: all)
-Compile in support for additional codeset (encoding) groups (eu, vn are
+Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
-always compiled in, which includes most 8-bit character sets). These
+are always compiled in, which includes most 8-bit character sets). These
-codeset tables are currently only used for driving X11 core fonts, they
+codeset tables are used for driving X11 core fonts, they are not required
-are not required for Xft fonts. Compiling them in will make your binary
+for Xft fonts, although having them compiled in lets rxvt-unicode choose
-bigger (together about 700kB), but it doesn't increase memory usage unless
+replacement fonts more intelligently. Compiling them in will make your
+binary bigger (all of together cost about 700kB), but it doesn't increase
-you use an X11 font requiring one of these encodings.
+memory usage unless you use a font requiring one of these encodings.
 =begin table
 	all	all available codeset groups
 	zh	common chinese encodings
 	jp_ext	rarely used but big japanese encodings
 	kr	korean encodings
 =end table
-=item --enable-xim
+=item --enable-xim (default: on)
 Add support for XIM (X Input Method) protocol. This allows using
 alternative input methods (e.g. kinput2) and will also correctly
 set up the input for people using dead keys or compose keys.
-=item --enable-unicode3
+=item --enable-unicode3 (default: off)
 Enable direct support for displaying unicode codepoints above
 65535 (the basic multilingual page). This increases storage
 requirements per character from 2 to 4 bytes. X11 fonts do not yet
 support these extra characters, but Xft does.
 even without this flag, but the number of such characters is
 limited to a view thousand (shared with combining characters,
 see next switch), and right now rxvt-unicode cannot display them
 (input/output and cut&paste still work, though).
-=item --enable-combining
+=item --enable-combining (default: on)
 Enable automatic composition of combining characters into
 composite characters. This is required for proper viewing of text
 where accents are encoded as seperate unicode characters. This is
 done by using precomposited characters when available or creating
 The combining table also contains entries for arabic presentation forms,
 but these are not currently used. Bug me if you want these to be used (and
 tell me how these are to be used...).
-=item --enable-fallback(=CLASS)
+=item --enable-fallback(=CLASS) (default: Rxvt)
-When reading resource settings, also read settings for class CLASS
+When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback.
-(default: Rxvt). To disable resource fallback use --disable-fallback.
-=item --with-res-name=NAME
+=item --with-res-name=NAME (default: urxvt)
-Use the given name (default: urxvt) as default application name when
+Use the given name as default application name when
 reading resources. Specify --with-res-name=rxvt to replace rxvt.
-=item --with-res-class=CLASS
+=item --with-res-class=CLASS /default: URxvt)
-Use the given class (default: URxvt) as default application class
+Use the given class as default application class
-when reading resources.  Specify --with-res-class=Rxvt to replace
+when reading resources. Specify --with-res-class=Rxvt to replace
 rxvt.
-=item --enable-utmp
+=item --enable-utmp (default: on)
 Write user and tty to utmp file (used by programs like F<w>) at
 start of rxvt execution and delete information when rxvt exits.
-=item --enable-wtmp
+=item --enable-wtmp (default: on)
 Write user and tty to wtmp file (used by programs like F<last>) at
 start of rxvt execution and write logout when rxvt exits.  This
 option requires --enable-utmp to also be specified.
-=item --enable-lastlog
+=item --enable-lastlog (default: on)
 Write user and tty to lastlog file (used by programs like
 F<lastlogin>) at start of rxvt execution.  This option requires
 --enable-utmp to also be specified.
-=item --enable-xpm-background
+=item --enable-xpm-background (default: on)
 Add support for XPM background pixmaps.
-=item --enable-transparency
+=item --enable-transparency (default: on)
 Add support for inheriting parent backgrounds thus giving a fake
 transparency to the term.
-=item --enable-fading
+=item --enable-fading (default: on)
-Add support for fading the text when focus is lost.
+Add support for fading the text when focus is lost (requires C<--enable-transparency>).
-=item --enable-tinting
+=item --enable-tinting (default: on)
-Add support for tinting of transparent backgrounds.
+Add support for tinting of transparent backgrounds (requires C<--enable-transparency>).
-=item --enable-menubar
+=item --enable-menubar (default: off) [DEPRECATED]
-Add support for our menu bar system (this interacts badly with
+Add support for our menu bar system (this interacts badly with dynamic
-dynamic locale switching currently).
+locale switching currently). This option is DEPRECATED and will be removed
+in the future.
-=item --enable-rxvt-scroll
+=item --enable-rxvt-scroll (default: on)
 Add support for the original rxvt scrollbar.
-=item --enable-next-scroll
+=item --enable-next-scroll (default: on)
 Add support for a NeXT-like scrollbar.
-=item --enable-xterm-scroll
+=item --enable-xterm-scroll (default: on)
 Add support for an Xterm-like scrollbar.
-=item --enable-plain-scroll
+=item --enable-plain-scroll (default: on)
 Add support for a very unobtrusive, plain-looking scrollbar that
 is the favourite of the rxvt-unicode author, having used it for
 many years.
-=item --enable-half-shadow
+=item --enable-half-shadow (default: off)
 Make shadows on the scrollbar only half the normal width & height.
 only applicable to rxvt scrollbars.
-=item --enable-ttygid
+=item --enable-ttygid (default: off)
 Change tty device setting to group "tty" - only use this if
 your system uses this type of security.
 =item --disable-backspace-key
-Disable any handling of the backspace key by us - let the X server
+Removes any handling of the backspace key by us - let the X server do it.
+=item --disable-delete-key
+Removes any handling of the delete key by us - let the X server
 do it.
-=item --disable-delete-key
-Disable any handling of the delete key by us - let the X server
-do it.
 =item --disable-resources
-Remove all resources checking.
+Removes any support for resource checking.
 =item --enable-xgetdefault
 Make resources checking via XGetDefault() instead of our small
 version which only checks ~/.Xdefaults, or if that doesn't exist then
 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.
-=item --enable-strings
+=item --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 in. (this breaks ANSI-C rules and has problems on many
 GNU/Linux systems).
 =item --disable-swapscreen
-Remove support for swap screen.
+Remove support for secondary/swap screen.
-=item --enable-frills
+=item --enable-frills (default: on)
 Add support for many small features that are not essential but nice to
 have. Normally you want this, but for very small binaries you may want to
 disable this.
 A non-exhaustive list of features enabled by C<--enable-frills> (possibly
 in combination with other switches) is:
   MWM-hints
+  EWMH-hints (pid, utf8 names) and protocols (ping)
-  seperate underline colour
+  seperate underline colour (-underlineColor)
-  settable border widths and borderless switch
+  settable border widths and borderless switch (-w, -b, -bl)
-  settable extra linespacing
+  settable extra linespacing /-lsp)
-  extra window properties (e.g. UTF-8 window names and PID)
   iso-14755-2 and -3, and visual feedback
   backindex and forwardindex escape sequence
-  window op and locale change escape sequences
+  window op and some xterm/OSC escape sequences
-  tripleclickwords
+  tripleclickwords (-tcw)
-  settable insecure mode
+  settable insecure mode (-insecure)
   keysym remapping support
+  cursor blinking and underline cursor (-cb, -uc)
+  XEmbed support (-embed)
+  user-pty (-pty-fd)
+  hold on exit (-hold)
+  skip builtin block graphics (-sbg)
+  sgr modes 90..97 and 100..107
-=item --enable-iso14755
+=item --enable-iso14755 (default: on)
 Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
 F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by
 C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with
 this switch.
-=item --enable-keepscrolling
+=item --enable-keepscrolling (default: on)
 Add support for continual scrolling of the display when you hold
 the mouse button down on a scrollbar arrow.
-=item --enable-mousewheel
+=item --enable-mousewheel (default: on)
 Add support for scrolling via mouse wheel or buttons 4 & 5.
-=item --enable-slipwheeling
+=item --enable-slipwheeling (default: on)
 Add support for continual scrolling (using the mouse wheel as an
 accelerator) while the control key is held down.  This option
 requires --enable-mousewheel to also be specified.
 =item --disable-new-selection
 Remove support for mouse selection style like that of xterm.
-=item --enable-dmalloc
+=item --enable-dmalloc (default: off)
 Use Gray Watson's malloc - which is good for debugging See
 http://www.letters.com/dmalloc/ for details If you use either this or the
 next option, you may need to edit src/Makefile after compiling to point
 DINCLUDE and DLIB to the right places.
 You can only use either this option and the following (should
 you use either) .
-=item --enable-dlmalloc
+=item --enable-dlmalloc (default: off)
 Use Doug Lea's malloc - which is good for a production version
 See L<http://g.oswego.edu/dl/html/malloc.html> for details.
-=item --enable-smart-resize
+=item --enable-smart-resize (default: on)
-Add smart growth/shrink behaviour when changing font size via from hot
+Add smart growth/shrink behaviour when changing font size via hot
-keys. This should keep in a fixed position the rxvt corner which is
+keys. This should keep the window corner which is closest to a corner of
-closest to a corner of the screen.
+the screen in a fixed position.
-=item --enable-cursor-blink
-Add support for a blinking cursor.
-=item --enable-pointer-blank
+=item --enable-pointer-blank (default: on)
 Add support to have the pointer disappear when typing or inactive.
-=item --with-name=NAME
+=item --enable-perl (default: off)
+Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)>
+manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files
+in F<src/perl-ext/> for the extensions that are installed by default. The
+perl interpreter that is used can be specified via the C<PERL> environment
+variable when running configure.
+=item --with-name=NAME (default: urxvt)
-Set the basename for the installed binaries (default: C<urxvt>, resulting
+Set the basename for the installed binaries, resulting
 in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with
 C<rxvt>.
-=item --with-term=NAME
+=item --with-term=NAME (default: rxvt-unicode)
-Change the environmental variable for the terminal to NAME (default
+Change the environmental variable for the terminal to NAME.
-C<rxvt-unicode>)
 =item --with-terminfo=PATH
 Change the environmental variable for the path to the terminfo tree to
 PATH.

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents): Revision 1.48 by root, Thu Feb 17 12:00:33 2005 UTC vs. Revision 1.73 by root, Mon Jan 9 01:54:43 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.48 by root, Thu Feb 17 12:00:33 2005 UTC vs.
Revision 1.73 by root, Mon Jan 9 01:54:43 2006 UTC