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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.175 by root, Mon Apr 12 17:06:55 2010 UTC vs.
Revision 1.186 by sf-exg, Wed Oct 13 23:36:00 2010 UTC

 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
+pure black and pure white colours essentially mean no tinting; resource
 I<tintColor>. Example:
    @@RXVT_NAME@@ -tr -tint blue -sh 40
 =item B<-sh> I<number>
 =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<add>, B<alphablend>, B<allanon> - colour 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>;
+on some backgrounds. Maximum radius value is 128. Compile I<afterimage> or I<xft>;
 resource I<blurRadius>.
 =item B<-icon> I<file>
-Compile I<afterimage>: Use the specified image as application icon. This
+Compile I<afterimage> or 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>.
 =item B<-bg> I<colour>
 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
+Compile I<afterimage> or I<pixbuf>: 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>
 Use the specified colour for the colour value I<n>, where 0-7
 corresponds to low-intensity (normal) colours and 8-15 corresponds to
 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)).
 Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
 =item B<colorUL:> I<colour>
 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
 foreground colour; option B<-cr>.
 =item B<reverseVideo:> I<boolean>
 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>
 B<True>: specify that jump scrolling should be used. When receiving lots
 of lines, @@RXVT_NAME@@ will only scroll once a whole screen height of lines
 =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
+(default C<100x100+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
+centre (percent).  A scale of 0 displays the image with tiling.
-of 1 displays the image without any scaling. A scale of 2 to 9 specifies
+The maximum permitted scale is 1000.
-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
   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
+blended over transparency image using alpha-blending. If I<afterimage>
-other blending type, specified with B<-blt "type"> option.
+support has been compiled in it is possible to choose other blending
+types with B<-blt "type"> option.
 =item B<path:> I<path>
 Specify the colon-delimited search path for finding background image files.
 large number (e.g. C<987654321>) to effectively disable the timeout.
 =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.
 =item B<deletekey:> I<string>
 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.
+number), see RESOURCES in C<man 7 X> for further 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.
 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
+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 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.
 B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so that
 it can be seen via the I<who(1)> command, and can accept messages.  To
 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
+B<@@RXVT_NAME@@> can display up to 88/256 colours: 8 ANSI colours plus
-high-intensity bold/blink versions of the same). Here is a list of the
+high-intensity (potentially bold/blink) versions of the same, and 72 (or
-colours with their names.
+240 in 256 colour mode) colours arranged in an 4x4x4 (or 6x6x6) colour RGB
+cube plus a 8 (24) colour greyscale ramp.
+Here is a list of the ANSI colours with their names.
 =begin table
 	B<color0>	(black)	= Black
 	B<color1>	(red)	= Red3
 It is also possible to specify the colour values of B<foreground>,
 B<background>, B<cursorColor>, B<cursorColor2>, B<colorBD>, B<colorUL> as
 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
+The following text gives values for the standard 88 colour mode (and
-additional 72 colours. The first 64 of those (with indices 16 to 79)
+values for the 256 colour mode in parentheses).
-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).
+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 * 16 + g) * 16 + b + 16   # r, g, b = 0..15
+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 colour xterm colours. Only
+Together, all those colours implement the 88 (256) colour xterm
-the first 16 can be changed using resources currently, the rest can only
+colours. Only the first 16 can be changed using resources currently, the
-be changed via command sequences ("escape codes").
+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
 I<xterm>(1) where the colours are only swapped if they have not otherwise
 been specified. For example,
 =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:
-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
 all ways to specify a colour.
 =over 4
 =item B</usr/lib/X11/rgb.txt>
-Color names.
+Colour names.
 =back
 =head1 SEE ALSO

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents): Revision 1.175 by root, Mon Apr 12 17:06:55 2010 UTC vs. Revision 1.186 by sf-exg, Wed Oct 13 23:36:00 2010 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.175 by root, Mon Apr 12 17:06:55 2010 UTC vs.
Revision 1.186 by sf-exg, Wed Oct 13 23:36:00 2010 UTC