--- rxvt-unicode/doc/rxvt.1.pod	2010/04/12 17:06:55	1.175
+++ rxvt-unicode/doc/rxvt.1.pod	2016/07/14 05:33:25	1.247
@@ -100,7 +100,7 @@
 
 =item B<-depth> I<bitdepth>
 
-Compile I<xft>: Attempt to find a visual with the given bit depth;
+Compile I<frills>: Attempt to find a visual with the given bit depth;
 resource B<depth>.
 
 [Please note that many X servers (and libXft) are buggy with
@@ -108,6 +108,12 @@
 of graphical corruption. This is harmless, but we can't do anything about
 this, so watch out]
 
+=item B<-visual> I<visualID>
+
+Compile I<frills>: Use the given visual (see e.g. C<xdpyinfo> for
+possible visual ids) instead of the default, and also allocate a private
+colormap. All visual types except for DirectColor are supported.
+
 =item B<-geometry> I<geom>
 
 Window geometry (B<-g> still respected); resource B<geometry>.
@@ -124,16 +130,6 @@
 
 Turn on/off skip scrolling (allow multiple screens per refresh); resource B<skipScroll>.
 
-=item B<-tr>|B<+tr>
-
-Turn on/off illusion of a transparent window background; resource B<transparent>.
-
-B<-ip> is still accepted as an obsolete alias but will be removed in
-future versions.
-
-I<Please address all transparency related issues to Sasha Vasko at
-sasha@aftercode.net. Read the FAQ (man 7 @@RXVT_NAME@@)!>
-
 =item B<-fade> I<number>
 
 Fade the text by the given percentage when focus is lost. Small values
@@ -145,48 +141,9 @@
 Fade to this colour when fading is used (see B<-fade>). The default colour
 is opaque black. resource B<fadeColor>.
 
-=item B<-tint> I<colour>
-
-Tint the transparent background pixmap with the given colour when
-transparency is enabled with B<-tr>. This only works for
-non-tiled backgrounds, currently. See also the B<-sh> option that can be
-used to brighten or darken the image in addition to tinting it.
-Please note that certain tint colours can be applied on the server-side,
-thus yielding performance gain of two orders of magnitude. These colours are:
-blue, red, green, cyan, magenta, yellow, and those close to them. Also
-pure black and pure white colors essentially mean no tinting; resource
-I<tintColor>. Example:
-
-   @@RXVT_NAME@@ -tr -tint blue -sh 40
-
-=item B<-sh> I<number>
-
-Darken (0 .. 100) or lighten (100 .. 200) the transparent
-background image in addition to (or instead of) tinting it;
-resource I<shading>.
-
-=item B<-blt> I<string>
-
-Specify background blending type. If background pixmap is specified
-at the same time as transparency - such pixmap will be blended over
-transparency image, using method specified. Supported values are :
-B<add>, B<alphablend>, B<allanon> - color values averaging, B<colorize>,
-B<darken>, B<diff>, B<dissipate>, B<hue>, B<lighten>, B<overlay>,
-B<saturate>, B<screen>, B<sub>, B<tint>, B<value>. The default is
-alpha-blending. Compile I<afterimage>; resource I<blendType>.
-
-=item B<-blr> I<HxV>
-
-Apply Gaussian Blur with the specified radii to the transparent
-background image. If single number is specified - both vertical and
-horizontal radii are considered to be the same. Setting one of the
-radii to 1 and another to a large number creates interesting effects
-on some backgrounds. Maximum radius value is 128. Compile I<afterimage>;
-resource I<blurRadius>.
-
 =item B<-icon> I<file>
 
-Compile I<afterimage>: Use the specified image as application icon. This
+Compile I<pixbuf>: Use the specified image as application icon. This
 is used by many window managers, taskbars and pagers to represent the
 application window; resource I<iconFile>.
 
@@ -198,13 +155,6 @@
 
 Window foreground colour; resource B<foreground>.
 
-=item B<-pixmap> I<file[;geom[:op1][:op2][...]]>
-
-Compile I<afterimage>: Specify image file for the background and also
-optionally specify its scaling with a geometry string. Note you may need to
-add quotes to avoid special shell interpretation of the C<;> in the
-command-line; for more details see resource B<backgroundPixmap>.
-
 =item B<-cr> I<colour>
 
 The cursor colour; resource B<cursorColor>.
@@ -272,6 +222,10 @@
 
 Start as a login-shell/sub-shell; resource B<loginShell>.
 
+=item B<-mc> I<milliseconds>
+
+Specify the maximum time between multi-click selections.
+
 =item B<-ut>|B<+ut>
 
 Compile I<utmp>: Inhibit/enable writing a utmp entry; resource
@@ -360,6 +314,11 @@
 Compile I<frills>: Sets override-redirect on the window; resource
 B<override-redirect>.
 
+=item B<-dockapp>
+
+Sets the initial state of the window to WithdrawnState, which makes
+window managers that support this extension treat it as a dockapp.
+
 =item B<-sbg>
 
 Compile I<frills>: Disable the usage of the built-in block graphics/line
@@ -423,6 +382,9 @@
 Compile I<XIM>: input style for input method; B<OverTheSpot>,
 B<OffTheSpot>, B<Root>; resource B<preeditType>.
 
+If the perl extension C<xim-onthespot> is used (which is the default),
+then additionally the C<OnTheSpot> preedit type is available.
+
 =item B<-im> I<text>
 
 Compile I<XIM>: input method name. resource B<inputMethod>.
@@ -573,10 +535,10 @@
 starts. @@RXVT_NAME@@ will consult the following files/resources in order,
 with later settings overwriting earlier ones:
 
-  1. system-wide app-defaults file, either locale-dependent OR global
-  2. app-defaults file in $XAPPLRESDIR
-  3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
-  4. SCREEN_RESOURCES for the current screen
+  1. app-defaults file in $XAPPLRESDIR
+  2. $HOME/.Xdefaults
+  3. RESOURCE_MANAGER property on root-window of screen 0
+  4. SCREEN_RESOURCES property on root-window of the current screen
   5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
   6. resources specified via -xrm on the commandline
 
@@ -627,7 +589,7 @@
 high-intensity (bold = bright foreground, blink = bright background)
 colours. The canonical names are as follows: 0=black, 1=red, 2=green,
 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour
-names used are listed in the B<COLORS AND GRAPHICS> section.
+names used are listed in the B<COLOURS AND GRAPHICS> section.
 
 Colours higher than 15 cannot be set using resources (yet), but can be
 changed using an escape command (see @@RXVT_NAME@@(7)).
@@ -648,16 +610,21 @@
 Use the specified colour to display underlined characters when the
 foreground colour is the default.
 
-=item B<colorRV:> I<colour>
-
-Use the specified colour as the background for reverse video characters
-when OPTION_HC is disabled (--disable-frills).
-
 =item B<underlineColor:> I<colour>
 
 If set, use the specified colour as the colour for the underline
 itself. If unset, use the foreground colour.
 
+=item B<highlightColor:> I<colour>
+
+If set, use the specified colour as the background for highlighted
+characters. If unset, use reverse video.
+
+=item B<highlightTextColor:> I<colour>
+
+If set and highlightColor is set, use the specified colour as the
+foreground for highlighted characters.
+
 =item B<cursorColor:> I<colour>
 
 Use the specified colour for the cursor. The default is to use the
@@ -673,7 +640,7 @@
 
 B<True>: simulate reverse video by foreground and background colours;
 option B<-rv>. B<False>: regular screen colours [default]; option
-B<+rv>. See note in B<COLORS AND GRAPHICS> section.
+B<+rv>. See note in B<COLOURS AND GRAPHICS> section.
 
 =item B<jumpScroll:> I<boolean>
 
@@ -697,16 +664,6 @@
 if the refresh is too fast for the human eye to read anything (or the
 monitor to display anything); option B<+ss>.
 
-=item B<transparent:> I<boolean>
-
-Turn on/off illusion of a transparent window background.
-
-B<inheritPixmap> is still accepted as an obsolete alias but will be removed in
-future versions.
-
-I<Please address all transparency related issues to Sasha Vasko at
-sasha@aftercode.net. Read the FAQ (man 7 @@RXVT_NAME@@)!>
-
 =item B<fading:> I<number>
 
 Fade the text by the given percentage when focus is lost; option B<-fade>.
@@ -716,25 +673,6 @@
 Fade to this colour, when fading is used (see B<fading:>). The default
 colour is black; option B<-fadecolor>.
 
-=item B<tintColor:> I<colour>
-
-Tint the transparent background pixmap with the given colour; option
-B<-tint>.
-
-=item B<shading:> I<number>
-
-Darken (0 .. 100) or lighten (-1 .. -100) the transparent background image
-in addition to tinting it; option B<-sh>.
-
-=item B<blendType:> I<string>
-
-Specify background blending type; option B<-blt>.
-
-=item B<blurRadius:> I<number>
-
-Apply gaussian blur with the specified radius to the transparent
-background image; option B<-blr>.
-
 =item B<iconFile:> I<file>
 
 Set the application icon pixmap; option B<-icon>.
@@ -753,36 +691,6 @@
 The colour of the border around the text area and between the scrollbar
 and the text.
 
-=item B<backgroundPixmap:> I<file[;geom[:op1][:op2][...]]>
-
-Use the specified image file for the background and also
-optionally specify its scaling with a geometry string B<WxH+X+Y>,
-(default C<0x0+50+50>) in which B<"W" / "H"> specify the
-horizontal/vertical scale (percent), and B<"X" / "Y"> locate the image
-centre (percent).  A scale of 0 displays the image with tiling. A scale
-of 1 displays the image without any scaling. A scale of 2 to 9 specifies
-an integer number of images in that direction. No image will be magnified
-beyond 10 times its original size. The maximum permitted scale is 1000.
-Additional operations can be specified after colon B<:op1:op2...>.
-Supported operations are:
-
-  tile        force background image to be tiled and not scaled. Equivalent to 0x0
-  propscale   will scale image keeping proportions
-  auto        will scale image to match window size. Equivalent to 100x100
-  hscale      will scale image horizontally to the window size
-  vscale      will scale image vertically to the window size
-  scale       will scale image to match window size
-  root        will tile image as if it was a root window background, auto-adjusting
-              whenever terminal window moves
-
-If used in conjunction with B<-tr> option, the specified pixmap will be
-blended over transparency image using either alpha-blending, or any
-other blending type, specified with B<-blt "type"> option.
-
-=item B<path:> I<path>
-
-Specify the colon-delimited search path for finding background image files.
-
 =item B<font:> I<fontlist>
 
 Select the fonts to be used. This is a comma separated list of font names
@@ -888,6 +796,11 @@
 the shell; option B<-ls>. B<False>: start as a normal sub-shell
 [default]; option B<+ls>.
 
+=item B<multiClickTime:> I<number>
+
+Specify the maximum time in milliseconds between multi-click select
+events. The default is 500 milliseconds; option B<-mc>.
+
 =item B<utmpInhibit:> I<boolean>
 
 B<True>: inhibit writing record into the system log file B<utmp>;
@@ -914,6 +827,10 @@
 Set scrollbar style to B<rxvt>, B<plain>, B<next> or B<xterm>. B<plain> is
 the author's favourite.
 
+=item B<thickness:> I<number>
+
+Set the scrollbar width in pixels.
+
 =item B<scrollBar:> I<boolean>
 
 B<True>: enable the scrollbar [default]; option B<-sb>. B<False>:
@@ -942,9 +859,10 @@
 
 =item B<scrollWithBuffer:> I<boolean>
 
-B<True>: scroll with scrollback buffer when tty receives new lines (and
-B<scrollTtyOutput> is False); option B<-sw>. B<False>: do not scroll
-with scrollback buffer when tty receives new lines; option B<+sw>.
+B<True>: scroll with scrollback buffer when tty receives new lines (i.e.
+try to show the same lines) and B<scrollTtyOutput> is False; option
+B<-sw>. B<False>: do not scroll with scrollback buffer when tty receives
+new lines; option B<+sw>.
 
 =item B<scrollTtyKeypress:> I<boolean>
 
@@ -955,8 +873,7 @@
 
 =item B<saveLines:> I<number>
 
-Save I<number> lines in the scrollback buffer [default 64]. This
-resource is limited on most machines to 65535; option B<-sl>.
+Save I<number> lines in the scrollback buffer [default 1000]; option B<-sl>.
 
 =item B<internalBorder:> I<number>
 
@@ -1029,6 +946,12 @@
 
 Mouse pointer background colour.
 
+=item B<pointerShape:> I<string>
+
+Compile I<frills>: Specifies the name of the mouse pointer shape
+[default B<xterm>]. See the macros in the B<X11/cursorfont.h> include
+file for possible values (omit the C<XC_> prefix).
+
 =item B<pointerBlankDelay:> I<number>
 
 Specifies number of seconds before blanking the pointer [default 2]. Use a
@@ -1037,7 +960,7 @@
 =item B<backspacekey:> I<string>
 
 The string to send when the backspace key is pressed. If set to B<DEC>
-or unset it will send B<Delete> (code 127) or, if shifted, B<Backspace>
+or unset it will send B<Delete> (code 127) or, with control, B<Backspace>
 (code 8) - which can be reversed with the appropriate DEC private mode
 escape sequence.
 
@@ -1064,7 +987,7 @@
 
 =item B<preeditType:> I<style>
 
-B<OverTheSpot>, B<OffTheSpot>, B<Root>; option B<-pt>.
+B<OnTheSpot>, B<OverTheSpot>, B<OffTheSpot>, B<Root>; option B<-pt>.
 
 =item B<inputMethod:> I<name>
 
@@ -1143,78 +1066,98 @@
 @@RXVT_NAME@@ to start. If it isn't specified then the current working
 directory will be used; option B<-cd>.
 
-=item B<keysym.>I<sym>: I<string>
+=item B<keysym.>I<sym>: I<action>
+
+Compile I<frills>: Associate I<action> with keysym I<sym>. The intervening
+resource name B<keysym.> cannot be omitted.
 
-Compile I<frills>: Associate I<string> with keysym I<sym>. The
-intervening resource name B<keysym.> cannot be omitted.
+Using this resource, you can map key combinations such as
+C<Ctrl-Shift-BackSpace> to various actions, such as outputting a different
+string than would normally result from that combination, making the
+terminal scroll up or down the way you want it, or any other thing an
+extension might provide.
 
-The format of I<sym> is "I<(modifiers-)key>", where I<modifiers> can be
-any combination of B<ISOLevel3>, B<AppKeypad>, B<Control>, B<NumLock>,
-B<Shift>, B<Meta>, B<Lock>, B<Mod1>, B<Mod2>, B<Mod3>, B<Mod4>, B<Mod5>,
-and the abbreviated B<I>, B<K>, B<C>, B<N>, B<S>, B<M>, B<A>, B<L>, B<1>,
-B<2>, B<3>, B<4>, B<5>.
+The key combination that triggers the action, I<sym>, has the following format:
+
+   (modifiers-)key
+
+Where I<modifiers> can be any combination of B<ISOLevel3>, B<AppKeypad>,
+B<Control>, B<NumLock>, B<Shift>, B<Meta>, B<Lock>, B<Mod1>, B<Mod2>,
+B<Mod3>, B<Mod4>, B<Mod5>, and the abbreviated B<I>, B<K>, B<C>, B<N>,
+B<S>, B<M>, B<A>, B<L>, B<1>, B<2>, B<3>, B<4>, B<5>.
 
 The B<NumLock>, B<Meta> and B<ISOLevel3> modifiers are usually aliased to
 whatever modifier the NumLock key, Meta/Alt keys or ISO Level3 Shift/AltGr
 keys are being mapped. B<AppKeypad> is a synthetic modifier mapped to the
 current application keymap mode state.
 
-The spellings of I<key> can be obtained by using B<xev>(1) command or
-searching keysym macros from B</usr/X11R6/include/X11/keysymdef.h> and
-omitting the prefix B<XK_>. Alternatively you can specify I<key> by its hex
-keysym value (B<0x0000 - 0xFFFF>). Note that the lookup of I<sym>s is not
-performed in an exact manner; however, the closest match is assured.
-
-I<string> may contain escape values (C<\n>: newline, C<\000>: octal
-number), see RESOURCES in C<man 7 X> for futher details.
-
-You can define a range of keysyms in one shot by providing a I<string>
-with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where the delimiter `/'
-should be a character not used by the strings.
+Due the the large number of modifier combinations, a key mapping will
+match if I<at least> the specified identifiers are being set, and no other
+key mappings with those and more bits are being defined. That means that
+defining a mapping for C<a> will automatically provide definitions for
+C<Meta-a>, C<Shift-a> and so on, unless some of those are defined mappings
+themselves. See the C<builtin:> action, below, for a way to work around
+this when this is a problem.
+
+The spelling of I<key> depends on your implementation of X. An easy way to
+find a key name is to use the B<xev>(1) command. You can find a list by
+looking for the C<XK_> macros in the B<X11/keysymdef.h> include file (omit
+the C<XK_> prefix). Alternatively you can specify I<key> by its hex keysym
+value (B<0x0000 - 0xFFFF>).
+
+As with any resource value, the I<action> string may contain backslash
+escape sequences (C<\n>: newline, C<\\>: backslash, C<\000>: octal
+number), see RESOURCES in C<man 7 X> for further details.
+
+An action starts with an action prefix that selects a certain type
+of action, followed by a colon. An action string without colons is
+interpreted as a literal string to pass to the tty (as if it was
+prefixed with C<string:>).
+
+The following action prefixes are known - extensions can provide
+additional prefixes:
+
+=over 4
+
+=item string:STRING
+
+If the I<action> starts with C<string:> (or otherwise contains no colons),
+then the remaining C<STRING> will be passed to the program running in the
+terminal. For example, you could replace whatever Shift-Tab outputs by the
+string C<echo rm -rf /> followed by a newline:
+
+   URxvt.keysym.Shift-Tab: string:echo rm -rf /\n
+
+This could in theory be used to completely redefine your keymap.
+
+In addition, for actions of this type, you can define a range of
+keysyms in one shot by loading the C<keysym-list> perl extension and
+providing an I<action> with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where
+the delimiter `/' should be a character not used by the strings.
 
 Its usage can be demonstrated by an example:
 
-  URxvt.keysym.M-C-0x61:    list|\033<M-C-|abc|>
+  URxvt.keysym.M-C-0x61:    list|\033<|abc|>
 
 The above line is equivalent to the following three lines:
 
-  URxvt.keysym.Meta-Control-0x61:    \033<M-C-a>
-  URxvt.keysym.Meta-Control-0x62:    \033<M-C-b>
-  URxvt.keysym.Meta-Control-0x63:    \033<M-C-c>
-
-If I<string> takes the form of C<command:STRING>, the specified B<STRING>
-is interpreted and executed as @@RXVT_NAME@@'s control sequence. For
-example the following means "change the current locale to C<zh_CN.GBK>
+  URxvt.keysym.Meta-Control-0x61:    string:\033<a>
+  URxvt.keysym.Meta-Control-0x62:    string:\033<b>
+  URxvt.keysym.Meta-Control-0x63:    string:\033<c>
+
+=item command:STRING
+
+If I<action> takes the form of C<command:STRING>, the specified B<STRING>
+is interpreted and executed as @@RXVT_NAME@@'s control sequence (basically
+the opposite of C<string:> - instead of sending it to the program running
+in the terminal, it will be treated as if it were program output). This is
+most useful to feed command sequences into @@RXVT_NAME@@.
+
+For example the following means "change the current locale to C<zh_CN.GBK>
 when Control-Meta-c is being pressed":
 
   URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007
 
-If I<string> takes the form C<perl:STRING>, then the specified B<STRING>
-is passed to the C<on_user_command> perl handler. See the @@RXVT_NAME@@perl(3)
-manpage. For example, the F<selection> extension (activated via
-C<@@RXVT_NAME@@ -pe selection>) listens for C<selection:rot13> events:
-
-  URxvt.keysym.M-C-c: perl:selection:rot13
-
-Due the the large number of modifier combinations, a defined key mapping
-will match if at I<at least> the specified identifiers are being set, and
-no other key mappings with those and more bits are being defined. That
-means that defining a key map for C<a> will automatically provide
-definitions for C<Meta-a>, C<Shift-a> and so on, unless some of those are defined
-mappings themselves.
-
-Unfortunately, this will override built-in key mappings. For example
-if you overwrite the C<Insert> key you will disable @@RXVT_NAME@@'s
-C<Shift-Insert> mapping. To re-enable that, you can poke "holes" into the
-user-defined keymap using the C<builtin:> replacement:
-
-  URxvt.keysym.Insert: <my insert key sequence>
-  URxvt.keysym.S-Insert: builtin:
-
-The first line defines a mapping for C<Insert> and I<any> combination
-of modifiers. The second line re-establishes the default mapping for
-C<Shift-Insert>.
-
 The following example will map Control-Meta-1 and Control-Meta-2 to
 the fonts C<suxuseuro> and C<9x15bold>, so you can have some limited
 font-switching at runtime:
@@ -1228,6 +1171,75 @@
   URxvt.keysym.M-C-3: command:\033[8;25;80t
   URxvt.keysym.M-C-4: command:\033[8;48;110t
 
+=item builtin:
+
+The builtin action is the action that @@RXVT_NAME@@ would execute if no
+key binding existed for the key combination. The obvious use is to undo
+the effect of existing bindings. The not so obvious use is to reinstate
+bindings when another binding overrides too many modifiers.
+
+For example if you overwrite the C<Insert> key you will disable
+@@RXVT_NAME@@'s C<Shift-Insert> mapping. To re-enable that, you can poke
+"holes" into the user-defined keymap using the C<builtin:> replacement:
+
+  URxvt.keysym.Insert: <my insert key sequence>
+  URxvt.keysym.S-Insert: builtin:
+
+The first line defines a mapping for C<Insert> and I<any> combination
+of modifiers. The second line re-establishes the default mapping for
+C<Shift-Insert>.
+
+=item builtin-string:
+
+This action is mainly useful to restore string mappings for keys that
+have predefined actions in @@RXVT_NAME@@. The exact semantics are a bit
+difficult to explain - basically, this action will send the string to the
+application that would be sent if @@RXVT_NAME@@ wouldn't have a built-in
+action for it.
+
+An example might make it clearer: @@RXVT_NAME@@ normally pastes the
+selection when you press C<Shift-Insert>. With the following bindings, it
+would instead emit the (undocumented, but what applications running in the
+terminal might expect) sequence C<ESC [ 2 $> instead:
+
+   URxvt.keysym.S-Insert: builtin-string:
+   URxvt.keysym.C-S-Insert: builtin:
+
+The first line disables the paste functionality for that key
+combination, and the second reinstates the default behaviour for
+C<Control-Shift-Insert>, which would otherwise be overridden.
+
+Similarly, to let applications gain access to the C<C-M-c> (copy to
+clipboard) and C<C-M-v> (paste clipboard) key combination, you can do
+this:
+
+   URxvt.keysym.C-M-c: builtin-string:
+   URxvt.keysym.C-M-v: builtin-string:
+
+=item EXTENSION:STRING
+
+An action of this form invokes the action B<STRING>, if any, provided
+by the @@RXVT_NAME@@perl(3) extension B<EXTENSION>. The extension will
+be loaded automatically if necessary.
+
+Not all extensions define actions, but popular extensions that do
+include the I<selection> and I<matcher> extensions (documented in their
+own manpages, @@RXVT_NAME@@-selection(1) and @@RXVT_NAME@@-matcher(1),
+respectively).
+
+From the silly examples department, this will rot13-"encrypt"
+@@RXVT_NAME@@'s selection when Alt-Control-c is pressed on typical PC
+keyboards:
+
+  URxvt.keysym.M-C-c: selection:rot13
+
+=item perl:STRING *DEPRECATED*
+
+This is a deprecated way of invoking commands provided by perl
+extensions. It is still supported, but should not be used anymore.
+
+=back
+
 =item B<perl-ext-common>: I<string>
 
 =item B<perl-ext>: I<string>
@@ -1238,20 +1250,23 @@
 Extension names can be prefixed with a C<-> sign to prohibit using
 them. This can be useful to selectively disable some extensions loaded
 by default, or specified via the C<perl-ext-common> resource. For
-example, C<default,-selection> will use all the default extension except
+example, C<default,-selection> will use all the default extensions except
 C<selection>.
 
-Extension names can also be followed by an argument in angle brackets
-(e.g.  C<< searchable-scrollback<M-s> >>, which binds the hotkey for
-searchable scrollback to Alt/Meta-s). Mentioning the same extension
-multiple times with different arguments will pass multiple arguments to
-the extension.
+The default set includes the C<selection>, C<option-popup>,
+C<selection-popup>, C<readline> and C<searchable-scrollback>
+extensions, and extensions which are mentioned in B<keysym> resources.
+
+Any extension such that a corresponding resource is given on the
+command line is automatically appended to B<perl-ext>.
 
 Each extension is looked up in the library directories, loaded if
-necessary, and bound to the current terminal instance.
+necessary, and bound to the current terminal instance. When the library
+search path contains multiple extension files of the same name, then the
+first one found will be used.
 
-If both of these resources are the empty string, then the perl
-interpreter will not be initialized. The idea behind two options is that
+If both of these resources are the empty string, then the perl interpreter
+will not be initialized. The rationale for having two options is that
 B<perl-ext-common> will be used for extensions that should be available to
 all instances, while B<perl-ext> is used for specific instances.
 
@@ -1263,9 +1278,9 @@
 =item B<perl-lib>: I<path>
 
 Colon-separated list of additional directories that hold extension
-scripts. When looking for extensions specified by the C<perl> resource,
-@@RXVT_NAME@@ will first look in these directories and then in
-F<@@RXVT_LIBDIR@@/urxvt/perl/>.
+scripts. When looking for perl extensions, @@RXVT_NAME@@ will first look
+in these directories, then in C<$URXVT_PERL_LIB>, F<$HOME/.urxvt/ext> and
+lastly in F<@@RXVT_LIBDIR@@/urxvt/perl/>.
 
 See the @@RXVT_NAME@@perl(3) manpage.
 
@@ -1279,12 +1294,14 @@
 Selection auto-transform patterns, see the @@RXVT_NAME@@perl(3) manpage
 for details.
 
-=item B<searchable-scrollback:> I<keysym>
+=item B<searchable-scrollback:> I<keysym> *DEPRECATED*
 
-Sets the hotkey that starts the incremental scrollback buffer search
-(default: C<M-s>).
+This resource is deprecated and will be removed. Use a B<keysym> resource
+instead, e.g.:
 
-=item B<urlLauncher>: I<string>
+   URxvt.keysym.M-s: searchable-scrollback:start
+
+=item B<url-launcher>: I<string>
 
 Specifies the program to be started with a URL argument. Used by the
 C<selection-popup> and C<matcher> perl extensions.
@@ -1363,6 +1380,12 @@
 Pressing B<Shift-Insert> causes the value of the PRIMARY selection to be
 inserted too.
 
+rxvt-unicode also provides the bindings B<Ctrl-Meta-c> and
+<Ctrl-Meta-v> to interact with the CLIPBOARD selection. The first
+binding causes the value of the internal selection to be copied to the
+CLIPBOARD selection, while the second binding causes the value of the
+CLIPBOARD selection to be inserted.
+
 =back
 
 =head1 CHANGING FONTS
@@ -1453,12 +1476,24 @@
 allow this feature, B<@@RXVT_NAME@@> may need to be installed setuid root
 on some systems or setgid to root or to some other group on others.
 
-=head1 COLORS AND GRAPHICS
+=head1 COLOURS AND GRAPHICS
 
 In addition to the default foreground and background colours,
-B<@@RXVT_NAME@@> can display up to 16 colours (8 ANSI colours plus
-high-intensity bold/blink versions of the same). Here is a list of the
-colours with their names.
+B<@@RXVT_NAME@@> can display up to 88/256 colours: 8 ANSI colours plus
+high-intensity (potentially bold/blink) versions of the same, and 72 (or
+240 in 256 colour mode) colours arranged in an 4x4x4 (or 6x6x6) colour RGB
+cube plus a 8 (24) colour greyscale ramp.
+
+B<@@RXVT_NAME@@> supports direct 24-bit fg/bg RGB colour escapes
+C< ESC [ 38 ; 2 ; R ; G ; Bm > / C< ESC [ 48 ; 2; R ; G ; Bm >. However the
+number of 24-bit colours that can be used is limited: an internal 7x7x5 (256
+colour mode) or 6x6x4 (88 colour mode) colour cube is used to index into the
+24-bit colour space. When indexing collisions happen, the nearest old colour in
+the cube will be adapted to the new 24-bit RGB colour. That means one cannot
+use many similar 24-bit colours. It's typically not a problem in common
+scenarios.
+
+Here is a list of the ANSI colours with their names.
 
 =begin table
 
@@ -1488,14 +1523,24 @@
 a number 0-15, as a convenient shorthand to reference the colour name of
 color0-color15.
 
-In addition to the colours defined above, @@RXVT_NAME@@ offers an
-additional 72 colours. The first 64 of those (with indices 16 to 79)
-consist of a 4*4*4 RGB colour cube (i.e. I<index = r * 16 + g * 4 + b +
-16>), followed by 8 additional shades of gray (with indices 80 to 87).
-
-Together, all those colours implement the 88 colour xterm colours. Only
-the first 16 can be changed using resources currently, the rest can only
-be changed via command sequences ("escape codes").
+The following text gives values for the standard 88 colour mode (and
+values for the 256 colour mode in parentheses).
+
+The RGB cube uses indices 16..79 (16..231) using the following formulas:
+
+   index_88  = (r * 4 + g) * 4 + b + 16   # r, g, b = 0..3
+   index_256 = (r * 6 + g) * 6 + b + 16   # r, g, b = 0..5
+
+The grayscale ramp uses indices 80..87 (232..239), from 10% to 90% in 10%
+steps (1/26 to 25/26 in 1/26 steps) - black and white are already part of
+the RGB cube.
+
+Together, all those colours implement the 88 (256) colour xterm
+colours. Only the first 16 can be changed using resources currently, the
+rest can only be changed via command sequences ("escape codes").
+
+Applications are advised to use terminfo or command sequences to discover
+number and RGB values of all colours (yes, you can query this...).
 
 Note that B<-rv> (B<"reverseVideo: True">) simulates reverse video by
 always swapping the foreground/background colours. This is in contrast to
@@ -1510,11 +1555,11 @@
 =head2 ALPHA CHANNEL SUPPORT
 
 If Xft support has been compiled in and as long as Xft/Xrender/X don't get
-their act together, rxvt-unicode will do it's own alpha channel management:
+their act together, rxvt-unicode will do its own alpha channel management:
 
-You can prefix any color with an opaquenes percentage enclosed in
+You can prefix any colour with an opaqueness percentage enclosed in
 brackets, i.e. C<[percent]>, where C<percent> is a decimal percentage
-(0-100) that specifies the opacity of the color, where C<0> is completely
+(0-100) that specifies the opacity of the colour, where C<0> is completely
 transparent and C<100> is completely opaque. For example, C<[50]red> is a
 half-transparent red, while C<[95]#00ff00> is an almost opaque green. This
 is the recommended format to specify transparency values, and works with
@@ -1602,12 +1647,22 @@
 
 The shell to be used for command execution, defaults to C</bin/sh>.
 
-=item B<RXVT_SOCKET>
+=item B<RXVT_SOCKET> [I<sic>]
 
 The unix domain socket path used by @@RXVT_NAME@@c(1) and
 @@RXVT_NAME@@d(1).
 
-Default F<<< $HOME/.rxvt-unicode-I<< <nodename >> >>>.
+Default F<<< $HOME/.urxvt/urxvtd-I<< <nodename> >> >>>.
+
+=item B<URXVT_PERL_LIB>
+
+Additional F<:>-separated library search path for perl extensions. Will be
+searched after B<-perl-lib> but before F<~/.urxvt/ext> and the system library
+directory.
+
+=item B<URXVT_PERL_VERBOSITY>
+
+See L<@@RXVT_NAME@@perl>(3).
 
 =item B<HOME>
 
@@ -1617,7 +1672,7 @@
 
 =item B<XAPPLRESDIR>
 
-Directory where various X resource files are being located.
+Directory where application-specific X resource files are located.
 
 =item B<XENVIRONMENT>
 
@@ -1632,13 +1687,14 @@
 
 =item B</usr/lib/X11/rgb.txt>
 
-Color names.
+Colour names.
 
 =back
 
 =head1 SEE ALSO
 
-@@RXVT_NAME@@(7), @@RXVT_NAME@@c(1), @@RXVT_NAME@@d(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)
+@@RXVT_NAME@@(7), @@RXVT_NAME@@c(1), @@RXVT_NAME@@d(1), @@RXVT_NAME@@-extensions(1),
+@@RXVT_NAME@@perl(3), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)
 
 =head1 CURRENT PROJECT COORDINATOR
 
@@ -1646,7 +1702,7 @@
 
 =item Project Coordinator
 
-Marc A. Lehmann L<< <rxvt-unicode@schmorp.de> >>
+Marc A. Lehmann <rxvt-unicode@schmorp.de>.
 
 L<http://software.schmorp.de/pkg/rxvt-unicode.html>
 
@@ -1660,40 +1716,40 @@
 
 University of Kent, 1992, wrote the original Xvt.
 
-=item Rob Nation L<< <nation@rocket.sanders.lockheed.com> >>
+=item Rob Nation <nation@rocket.sanders.lockheed.com>
 
 very heavily modified Xvt and came up with Rxvt
 
-=item Angelo Haritsis L<< <ah@doc.ic.ac.uk> >>
+=item Angelo Haritsis <ah@doc.ic.ac.uk>
 
 wrote the Greek Keyboard Input (no longer in code)
 
-=item mj olesen L<< <olesen@me.QueensU.CA> >>
+=item mj olesen <olesen@me.QueensU.CA>
 
 Wrote the menu system.
 
 Project Coordinator (changes.txt 2.11 to 2.21)
 
-=item Oezguer Kesim L<< <kesim@math.fu-berlin.de> >>
+=item Oezguer Kesim <kesim@math.fu-berlin.de>
 
 Project Coordinator (changes.txt 2.21a to 2.4.5)
 
-=item Geoff Wing L<< <gcw@pobox.com> >>
+=item Geoff Wing <gcw@pobox.com>
 
 Rewrote screen display and text selection routines.
 
 Project Coordinator (changes.txt 2.4.6 - rxvt-unicode)
 
-=item Marc Alexander Lehmann L<< <rxvt-unicode@schmorp.de> >>
+=item Marc Alexander Lehmann <rxvt-unicode@schmorp.de>
 
 Forked rxvt-unicode, unicode support, rewrote almost all the code, perl
 extension, random hacks, numerous bugfixes and extensions.
 
 Project Coordinator (Changes 1.0 -)
 
-=item Emanuele Giaquinta L<< <e.giaquinta@glauco.it> >>
+=item Emanuele Giaquinta <emanuele.giaquinta@gmail.com>
 
-Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugfixing.
+pty/utmp code rewrite, image code improvements, many random hacks and bugfixes.
 
 =back