--- rxvt-unicode/doc/rxvt.7.pod 2006/02/02 15:22:19 1.112 +++ rxvt-unicode/doc/rxvt.7.pod 2007/08/02 00:09:54 1.143 @@ -19,7 +19,7 @@ all escape sequences, and other background information. The newest version of this document is also available on the World Wide Web at -L. +L. =head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS @@ -75,7 +75,7 @@ Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the display, create the listening socket and then fork. -=head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c? +=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c? If you want to start @@URXVT_NAME@@d automatically whenever you run @@URXVT_NAME@@c and the daemon isn't running yet, use this script: @@ -92,7 +92,7 @@ re-run the command. Subsequent invocations of the script will re-use the existing daemon. -=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. +=head3 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors 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, @@ -127,8 +127,8 @@ =head3 How do I compile the manual pages on my own? You need to have a recent version of perl installed as F, -one that comes with F, F and F. Then go to -the doc subdirectory and enter C. +one that comes with F, F and F (from +F). Then go to the doc subdirectory and enter C. =head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat? @@ -146,7 +146,7 @@ When you C<--enable-everything> (which I 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. +libc), the two diverge, but not unreasonably so. text data bss drs rss filename 163431 2152 24 20123 2060 rxvt --enable-everything @@ -243,7 +243,7 @@ This requires XFT support, and the support of your X-server. If that doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't -there yet, no matter what they claim. Rxvt-Unicode contains the neccessary +there yet, no matter what they claim. Rxvt-Unicode contains the necessary bugfixes and workarounds for Xft and Xlib to make it work, but that doesn't mean that your WM has the required kludges in place. @@ -270,7 +270,7 @@ ask for the character bounding box, which unfortunately is wrong in these cases). -It's not clear (to me at least), wether this is a bug in Xft, freetype, +It's not clear (to me at least), whether this is a bug in Xft, freetype, or the respective font. If you encounter this problem you might try using the C<-lsp> option to give the font more height. If that doesn't work, you might be forced to use a different font. @@ -304,7 +304,7 @@ Yes, using an escape sequence. Try something like this, which has the same effect as using the C<-fn> switch, and takes effect immediately: - printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" + printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic" This is useful if you e.g. work primarily with japanese (and prefer a japanese font), but you have to switch to chinese temporarily, where @@ -316,7 +316,7 @@ Many fonts have difficulties with italic characters and hinting. For example, the otherwise very nicely hinted font C completely fails in it's italic face. A workaround might be to +Mono> completely fails in its italic face. A workaround might be to enable freetype autohinting, i.e. like this: URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true @@ -332,7 +332,7 @@ =head3 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 -fall back to it's default font search list it will prefer X11 core +fall back to its default font search list it will prefer X11 core fonts, because they are small and fast, and then use Xft fonts. It has antialiasing disabled for most of them, because the author thinks they look best that way. @@ -514,7 +514,7 @@ but when running a program that doesn't parse cursor movements or in some cases during rlogin sessions, it fails to detect this properly. -You can permamently switch this feature off by disabling the C +You can permanently switch this feature off by disabling the C extension: URxvt.perl-ext-common: default,-readline @@ -523,7 +523,7 @@ Some Debian GNUL/Linux users seem to have this problem, although no specific details were reported so far. It is possible that this is caused -by the wrong C setting, although the details of wether and how +by the wrong C setting, although the details of whether and how this can happen are unknown, as C should offer a compatible keymap. See the answer to the previous question, and please report if that helped. @@ -559,12 +559,12 @@ =head3 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 +Backspace keysym (not likely for Linux ... see the following question) there are two standard values that can be used for Backspace: C<^H> and C<^?>. Historically, either value is correct, but rxvt-unicode adopts the debian -policy of using C<^?> when unsure, because it's the one only only correct +policy of using C<^?> when unsure, because it's the one and only correct choice :). Rxvt-unicode tries to inherit the current stty settings and uses the value @@ -660,6 +660,160 @@ =head2 Terminal Configuration +=head3 Can I see a typical configuration? + +The default configuration tries to be xterm-like, which I don't like that +much, but it's least surprise to regular users. + +As a rxvt or rxvt-unicode user, you are practically supposed to invest +time into customising your terminal. To get you started, here is the +author's .Xdefaults entries, with comments on what they do. It's certainly +not I, but what's typical... + + URxvt.cutchars: "()*,<>[]{}|' + URxvt.print-pipe: cat >/tmp/xxx + +These are just for testing stuff. + + URxvt.imLocale: ja_JP.UTF-8 + URxvt.preeditType: OnTheSpot,None + +This tells rxvt-unicode to use a special locale when communicating with +the X Input Method, and also tells it to only use the OnTheSpot pre-edit +type, which requires the C perl extension but rewards me +with correct-looking fonts. + + URxvt.perl-lib: /root/lib/urxvt + URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard + URxvt.selection.pattern-0: ( at .*? line \\d+) + URxvt.selection.pattern-1: ^(/[^:]+):\ + URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/ + URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/ + +This is my perl configuration. The first two set the perl library +directory and also tells urxvt to use a large number of extensions. I +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. + + URxvt.scrollstyle: plain + URxvt.secondaryScroll: true + +As the documentation says: plain is the preferred scrollbar for the +author. The C configures urxvt to scroll in full-screen +apps, like screen, so lines scrolled out of screen end up in urxvt's +scrollback buffer. + + URxvt.background: #000000 + URxvt.foreground: gray90 + URxvt.color7: gray90 + URxvt.colorBD: #ffffff + URxvt.cursorColor: #e0e080 + URxvt.throughColor: #8080f0 + URxvt.highlightColor: #f0f0f0 + +Some colours. Not sure which ones are being used or even non-defaults, but +these are in my .Xdefaults. Most notably, they set foreground/background +to light gray/black, and also make sure that the colour 7 matches the +default foreground colour. + + URxvt.underlineColor: yellow + +Another colour, makes underline lines look different. Sometimes hurts, but +is mostly a nice effect. + + URxvt.geometry: 154x36 + URxvt.loginShell: false + URxvt.meta: ignore + URxvt.utmpInhibit: true + +Uh, well, should be mostly self-explanatory. By specifying some defaults +manually, I can quickly switch them for testing. + + URxvt.saveLines: 8192 + +A large scrollback buffer is essential. Really. + + URxvt.mapAlert: true + +The only case I use it is for my IRC window, which I like to keep +iconified till people msg me (which beeps). + + URxvt.visualBell: true + +The audible bell is often annoying, especially when in a crowd. + + URxvt.insecure: true + +Please don't hack my mutt! Ooops... + + URxvt.pastableTabs: false + +I once thought this is a great idea. + + urxvt.font: 9x15bold,\ + -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ + -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ + [codeset=JISX0208]xft:Kochi Gothic, \ + xft:Bitstream Vera Sans Mono:autohint=true, \ + xft:Code2000:antialias=false + urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 + urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true + urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true + +I wrote rxvt-unicode to be able to specify fonts exactly. So don't be +overwhelmed. A special note: the C<9x15bold> mentioned above is actually +the version from XFree-3.3, as XFree-4 replaced it by a totally different +font (different glyphs for C<;> and many other harmless characters), +while the second font is actually the C<9x15bold> from XFree4/XOrg. The +bold version has less chars than the medium version, so I use it for rare +characters, too. When editing sources with vim, I use italic for comments +and other stuff, which looks quite good with Bitstream Vera anti-aliased. + +Terminus is a quite bad font (many very wrong glyphs), but for most of 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 C instance name and not the C +class name. Thats because I use different configs for different purposes, +for example, my IRC window is started with C<-name IRC>, and uses these +defaults: + + IRC*title: IRC + IRC*geometry: 87x12+535+542 + IRC*saveLines: 0 + IRC*mapAlert: true + IRC*font: suxuseuro + IRC*boldFont: suxuseuro + IRC*colorBD: white + IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 + IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 + +C and C switch between two different font +sizes. C allows me to keep an eye (and actually read) +stuff while 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 C<.Xdefaults> (I don't use C<.Xresources> nor +C). I also have some resources in a separate C<.Xdefaults-hostname> +file for different hosts, for example, on ym 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 + URxvt.keysym.C-M-p: perl:test + +The first for keysym definitions allow me to quickly bring some windows +in the layout I like most. Ion users might start laughing but will stop +immediately when I tell them that I use my own Fvwm2 module for much the +same effect as Ion provides, and I only very rarely use the above key +combinations :-> + =head3 Why doesn't rxvt-unicode read my resources? Well, why, indeed? It does, in a way very similar to other X @@ -677,7 +831,7 @@ URxvt.resource: value If you want to use another form (there are lots of different ways of -specifying resources), make sure you understand wether and why it +specifying resources), make sure you understand whether and why it works. If unsure, use the form above. =head3 When I log-in to another system it tells me about missing terminfo data? @@ -686,13 +840,16 @@ as that for xterm, or even rxvt (for which the same problem often arises). The correct solution for this problem is to install the terminfo, this can -be done like this (with ncurses' infocmp): +be done like this (with ncurses' infocmp and works as user and admin): REMOTE=remotesystem.domain - infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" + infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" ... or by installing rxvt-unicode normally on the remote system, +One some systems you might need to set C<$TERMINFO> to the full path of +F<$HOME/.terminfo> for this to work. + If you cannot or do not want to do this, then you can simply set C or even C, and live with the small number of problems arising, which includes wrong keymapping, less and different @@ -724,7 +881,7 @@ library (Fedora Core's bash is one example) and rely on a termcap entry for C. -You could use rxvt's termcap entry with resonable results in many cases. +You could use rxvt's termcap entry with reasonable results in many cases. You can also create a termcap entry by using terminfo's infocmp program like this: @@ -756,8 +913,8 @@ =head3 Why does C no longer have coloured output? The C in the GNU coreutils unfortunately doesn't use terminfo to -decide wether a terminal has colour, but uses it's own configuration -file. Needless to say, C is not in it's default file (among +decide whether a terminal has colour, but uses its own configuration +file. Needless to say, C is not in its default file (among with most other terminals supporting colour). Either add: TERM rxvt-unicode @@ -801,14 +958,15 @@ subtly garbled, then you should check your locale settings. Rxvt-unicode must be started with the same C setting as the -programs. Often rxvt-unicode is started in the C locale, while the -login script running within the rxvt-unicode window changes the locale to -something else, e.g. C. Needless to say, this is not going to work. +programs running in it. Often rxvt-unicode is started in the C locale, +while the login script running within the rxvt-unicode window changes the +locale to something else, e.g. C. Needless to say, this is +not going to work, and is the most common cause for problems. The best thing is to fix your startup environment, as you will likely run into other problems. If nothing works you can try this in your .profile. - printf '\e]701;%s\007' "$LC_CTYPE" + printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too If this doesn't work, then maybe you use a C specification not supported on your systems. Some systems have a C command which @@ -839,7 +997,7 @@ applications so everybody agrees on character properties such as width and code number. This mechanism is the I. Applications not using that info will have problems (for example, C gets the width of -characters wrong as it uses it's own, locale-independent table under all +characters wrong as it uses its own, locale-independent table under all locales). Rxvt-unicode uses the C locale category to select encoding. All @@ -868,7 +1026,7 @@ Yes, using an escape sequence. Try something like this, which sets rxvt-unicode's idea of C. - printf '\e]701;%s\007' ja_JP.SJIS + printf '\33]701;%s\007' ja_JP.SJIS See also the previous answer. @@ -877,9 +1035,9 @@ (e.g. UTF-8). For example, I use this script to start C, which first switches to a locale supported by xjdic and back later: - printf '\e]701;%s\007' ja_JP.SJIS + printf '\33]701;%s\007' ja_JP.SJIS xjdic -js - printf '\e]701;%s\007' de_DE.UTF-8 + printf '\33]701;%s\007' de_DE.UTF-8 You can also use xterm's C program, which usually works fine, except for some locales where character width differs between program- and @@ -907,7 +1065,7 @@ =item - Make sure the C environment variable is set correctly when I rxvt-unicode. When you want to use e.g. B, it must be set to -C<@im=kinput2>. For B, use C<@im=SCIM>. Youc an see what input +C<@im=kinput2>. For B, use C<@im=SCIM>. You can see what input method servers are running with this command: xprop -root XIM_SERVERS @@ -962,7 +1120,7 @@ You should build one binary with the default options. F now enables most useful options, and the trend goes to making them -runtime-switchable, too, so there is usually no drawback to enbaling them, +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. @@ -995,23 +1153,15 @@ things like the dynamic loader of your system, which should result in very little risk. -=head3 On Solaris 9, many line-drawing characters are too wide. - -Seems to be a known bug, read -L. Some people use the -following ugly workaround to get non-double-wide-characters working: - - #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) - =head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined in your compile environment, or an implementation that implements it, -wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that +whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that B is represented as unicode. -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 +As you might have guessed, FreeBSD does neither define this symbol nor +does it support it. Instead, it uses its own internal representation of B. This is, of course, completely fine with respect to standards. However, that means rxvt-unicode only works in C, C and @@ -1035,11 +1185,6 @@ system libraries once and for all, instead of forcing every app to carry complete replacements for them :) -=head3 I use Solaris 9 and it doesn't compile/work/etc. - -Try the diff in F as a base. It fixes the worst -problems with C and a compile problem. - =head3 How can I use rxvt-unicode under cygwin? rxvt-unicode should compile and run out of the box on cygwin, using @@ -1053,6 +1198,19 @@ encodings (you might try C), so you are likely limited to 8-bit encodings. +=head3 Character widths are not correct. + +urxvt uses the system wcwidth function to know the information about +the width of characters, so on systems with incorrect locale data you +will likely get bad results. Two notorious examples are Solaris 9, +where single-width characters like U+2514 are reported as double-width, +and Darwin 8, where combining chars are reported having width 1. + +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 + =head1 RXVT-UNICODE TECHNICAL REFERENCE The rest of this document describes various technical aspects of @@ -1555,7 +1713,7 @@ =over 4 -=item B<< C >> (DECCKM) +=item B<< C >> (DECCKM) =begin table @@ -1564,7 +1722,7 @@ =end table -=item B<< C >> (ANSI/VT52 mode) +=item B<< C >> (ANSI/VT52 mode) =begin table @@ -1573,7 +1731,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1582,7 +1740,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1591,7 +1749,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1600,7 +1758,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1609,7 +1767,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1618,7 +1776,7 @@ =end table -=item B<< C >> I +=item B<< C >> I =begin table @@ -1627,7 +1785,7 @@ =end table -=item B<< C >> X10 XTerm +=item B<< C >> X10 XTerm =begin table @@ -1636,7 +1794,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1645,7 +1803,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1654,7 +1812,7 @@ =end table -=item B<< C >> (B) +=item B<< C >> (B) =begin table @@ -1663,11 +1821,11 @@ =end table -=item B<< C >> I +=item B<< C >> I Enter Tektronix Mode (DECTEK) -=item B<< C >> +=item B<< C >> =begin table @@ -1676,7 +1834,7 @@ =end table -=item B<< C >> I +=item B<< C >> I =begin table @@ -1685,7 +1843,7 @@ =end table -=item B<< C >> I +=item B<< C >> I =begin table @@ -1694,9 +1852,9 @@ =end table -=item B<< C >> I +=item B<< C >> I -=item B<< C >> +=item B<< C >> =begin table @@ -1707,7 +1865,7 @@ X -=item B<< C >> +=item B<< C >> =begin table @@ -1716,7 +1874,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1725,7 +1883,7 @@ =end table -=item B<< C >> (X11 XTerm) +=item B<< C >> (X11 XTerm) =begin table @@ -1734,7 +1892,7 @@ =end table -=item B<< C >> (X11 XTerm) I +=item B<< C >> (X11 XTerm) I =begin table @@ -1743,7 +1901,7 @@ =end table -=item B<< C >> (B) +=item B<< C >> (B) =begin table @@ -1752,7 +1910,7 @@ =end table -=item B<< C >> (B) +=item B<< C >> (B) =begin table @@ -1761,7 +1919,7 @@ =end table -=item B<< C >> (B) +=item B<< C >> (B) =begin table @@ -1770,7 +1928,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1779,7 +1937,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -1788,7 +1946,7 @@ =end table -=item B<< C >> +=item B<< C >> =begin table @@ -2045,10 +2203,9 @@ General hint: if you get compile errors, then likely your configuration hasn't been tested well. Either try with C<--enable-everything> or use -the F<./reconf> script as a base for experiments. F<./reconf> is used by -myself, so it should generally be a working config. Of course, you should -always report when a combination doesn't work, so it can be fixed. Marc -Lehmann . +the default configuration (i.e. C<--enable-xxx> or C<--disable-xxx>). Of +course, you should always report when a combination doesn't work, so it +can be fixed. Marc Lehmann . All @@ -2090,7 +2247,7 @@ all all available codeset groups zh common chinese encodings - zh_ext rarely used but very big chinese encodigs + zh_ext rarely used but very big chinese encodings jp common japanese encodings jp_ext rarely used but big japanese encodings kr korean encodings @@ -2114,7 +2271,7 @@ Please note that rxvt-unicode can store unicode code points >65535 even without this flag, but the number of such characters is -limited to a view thousand (shared with combining characters, +limited to a few thousand (shared with combining characters, see next switch), and right now rxvt-unicode cannot display them (input/output and cut&paste still work, though). @@ -2170,9 +2327,20 @@ F) at start of rxvt execution. This option requires --enable-utmp to also be specified. -=item --enable-xpm-background (default: on) +=item --enable-afterimage (default: on) -Add support for XPM background pixmaps. +Add support for libAfterImage to be used for transparency and background +images. It adds support for many file formats including JPG, PNG, +SVG, TIFF, GIF, XPM, BMP, ICO, XCF, TGA and AfterStep image XML +(L). + +This option also adds such eye candy as blending an image over the root +background, as well as dynamic scaling and bluring of background images. + +Note that with this option enabled, @@RXVT_NAME@@'s memory footprint might +increase by a few megabytes even if no extra features are used (mostly due +to third-party libraries used by libAI). Memory footprint may somewhat be +lowered if libAfterImage is configured without support for SVG. =item --enable-transparency (default: on) @@ -2181,7 +2349,7 @@ =item --enable-fading (default: on) -Add support for fading the text when focus is lost (requires C<--enable-transparency>). +Add support for fading the text when focus is lost. =item --enable-tinting (default: on) @@ -2238,11 +2406,12 @@ MWM-hints EWMH-hints (pid, utf8 names) and protocols (ping) + urgency hint seperate underline colour (-underlineColor) settable border widths and borderless switch (-w, -b, -bl) visual depth selection (-depth) settable extra linespacing /-lsp) - iso-14755-2 and -3, and visual feedback + iso-14755 5.1 (basic) support tripleclickwords (-tcw) settable insecure mode (-insecure) keysym remapping support @@ -2251,15 +2420,16 @@ user-pty (-pty-fd) hold on exit (-hold) skip builtin block graphics (-sbg) + separate highlightcolor support (-hc) -It also enabled some non-essential features otherwise disabled, such as: +It also enables some non-essential features otherwise disabled, such as: some round-trip time optimisations nearest color allocation on pseudocolor screens - UTF8_STRING supporr for selection + UTF8_STRING support for selection sgr modes 90..97 and 100..107 backindex and forwardindex escape sequences - view change/zero scorllback esacpe sequences + view change/zero scrollback escape sequences locale switching escape sequence window op and some xterm/OSC escape sequences rectangular selections @@ -2278,6 +2448,11 @@ Add support for continual scrolling of the display when you hold the mouse button down on a scrollbar arrow. +=item --enable-selectionscrolling (default: on) + +Add support for scrolling when the selection moves to the top or +bottom of the screen. + =item --enable-mousewheel (default: on) Add support for scrolling via mouse wheel or buttons 4 & 5. @@ -2288,29 +2463,10 @@ accelerator) while the control key is held down. This option requires --enable-mousewheel to also be specified. -=item --disable-new-selection +=item --enable-smart-resize (default: off) -Remove support for mouse selection style like that of xterm. - -=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 (default: off) - -Use Doug Lea's malloc - which is good for a production version -See L for details. - -=item --enable-smart-resize (default: on) - -Add smart growth/shrink behaviour when changing font size via hot -keys. This should keep the window corner which is closest to a corner of +Add smart growth/shrink behaviour when resizing. +This should keep the window corner which is closest to a corner of the screen in a fixed position. =item --enable-pointer-blank (default: on) @@ -2320,10 +2476,17 @@ =item --enable-perl (default: on) Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)> -manpage (F) for more info on this feature, or the files -in F for the extensions that are installed by default. The -perl interpreter that is used can be specified via the C environment -variable when running configure. +manpage (F) for more info on this feature, or the +files in F for the extensions that are installed by +default. The perl interpreter that is used can be specified via the +C environment variable when running configure. Even when compiled +in, perl will I be initialised when all extensions have been disabled +C<-pe "" --perl-ext-common "">, so it should be safe to enable from a +resource standpoint. + +=item --with-afterimage-config=DIR + +Look for the libAfterImage config script in DIR. =item --with-name=NAME (default: urxvt) @@ -2344,18 +2507,6 @@ Use the X Window System (pretty much default, eh?). -=item --with-xpm-includes=DIR - -Look for the XPM includes in DIR. - -=item --with-xpm-library=DIR - -Look for the XPM library in DIR. - -=item --with-xpm - -Not needed - define via --enable-xpm-background. - =back =head1 AUTHORS