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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.177 by root, Sun May 23 00:48:53 2010 UTC vs.
Revision 1.201 by sf-exg, Wed Aug 10 07:34:35 2011 UTC

 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>.
+Turn on/off pseudo-transparency by using the root pixmap as 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
 fade a little only, 100 completely replaces all colours by the fade
 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
+Tint the transparent background with the given colour;
-transparency is enabled with B<-tr>. This only works for
+resource I<tintColor>.
-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 colours 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
+Darken (0 .. 99) or lighten (101 .. 200) the transparent background.
-background image in addition to (or instead of) tinting it;
+A value of 100 means no shading; resource I<shading>.
-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 :
+the transparent background, using the method specified. Supported values are:
 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
+background. If a 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;
 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>
 You can set and change the resources using X11 tools like B<xrdb>. Many
 distribution do also load settings from the B<~/.Xresources> file when X
 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
+  1. app-defaults file in $XAPPLRESDIR
+  2. $HOME/.Xdefaults
-  3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
+  3. RESOURCE_MANAGER property on root-window of screen 0
-  4. SCREEN_RESOURCES for the current screen
+  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
 Note that when reading X resources, B<@@RXVT_NAME@@> recognizes two class
 names: B<Rxvt> and B<URxvt>. The class name B<Rxvt> allows resources
 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.
+Turn on/off pseudo-transparency by using the root pixmap as 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>.
 =item B<fadeColor:> I<colour>
 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
+Tint the transparent background with the given colour. If the RENDER
-B<-tint>.
+extension is not available only black, red, green, yellow, blue,
+magenta, cyan and white tints can be performed server-side. Note that
+a black tint yields a completely black image while a white tint yields
+the image unchanged; option B<-tint>.
 =item B<shading:> I<number>
-Darken (0 .. 100) or lighten (-1 .. -100) the transparent background image
+Darken (0 .. 99) or lighten (101 .. 200) the transparent background.
-in addition to tinting it; option B<-sh>.
+A value of 100 means no shading; 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>.
+background; option B<-blr>.
 =item B<iconFile:> I<file>
 Set the application icon pixmap; option B<-icon>.
 =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 disables scaling.
-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
+  tile        will tile image
   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
+  center      will center image with no scaling
   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 the transparent background 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.
 =item B<scrollstyle:> I<mode>
 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>:
 disable the scrollbar; option B<+sb>.
 B<False>: do not scroll to bottom when tty receives output; option
 B<+si>.
 =item B<scrollWithBuffer:> I<boolean>
-B<True>: scroll with scrollback buffer when tty receives new lines (and
+B<True>: scroll with scrollback buffer when tty receives new lines (i.e.
-B<scrollTtyOutput> is False); option B<-sw>. B<False>: do not scroll
+try to show the same lines) and B<scrollTtyOutput> is False; option
-with scrollback buffer when tty receives new lines; option B<+sw>.
+B<-sw>. B<False>: do not scroll with scrollback buffer when tty receives
+new lines; option B<+sw>.
 =item B<scrollTtyKeypress:> I<boolean>
 B<True>: scroll to bottom when a non-special key is pressed. Special keys
 are those which are intercepted by rxvt-unicode for special handling and
 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.
 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-0x61:    \033<a>
-  URxvt.keysym.Meta-Control-0x62:    \033<M-C-b>
+  URxvt.keysym.Meta-Control-0x62:    \033<b>
-  URxvt.keysym.Meta-Control-0x63:    \033<M-C-c>
+  URxvt.keysym.Meta-Control-0x63:    \033<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>
 when Control-Meta-c is being pressed":
 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.
 on some systems or setgid to root or to some other group on others.
 =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 colour 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 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
 =item B<RXVT_SOCKET>
 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/.rxvt-unicode-I<< <nodename> >> >>>.
 =item B<HOME>
 Used to locate the default directory for the unix domain socket for
 daemon communications and to locate various resource files (such as
 C<.Xdefaults>)
 =item B<XAPPLRESDIR>
-Directory where various X resource files are being located.
+Directory where application-specific X resource files are located.
 =item B<XENVIRONMENT>
 If set and accessible, gives the name of a X resource file to be loaded by
 @@RXVT_NAME@@.
 Project Coordinator (Changes 1.0 -)
 =item Emanuele Giaquinta L<< <e.giaquinta@glauco.it> >>
-Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugfixing.
+pty/utmp code rewrite, image code improvements, many random hacks and bugfixes.
 =back

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents): Revision 1.177 by root, Sun May 23 00:48:53 2010 UTC vs. Revision 1.201 by sf-exg, Wed Aug 10 07:34:35 2011 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.177 by root, Sun May 23 00:48:53 2010 UTC vs.
Revision 1.201 by sf-exg, Wed Aug 10 07:34:35 2011 UTC