repo: rxvt-unicode-sixel
action: commit
revision: 
path_from: 
revision_from: 0ab0fd1c8e9f54a9e5f0e4247fc4620f1f4010aa:
path_to: 
revision_to: 

commit 0ab0fd1c8e9f54a9e5f0e4247fc4620f1f4010aa
Author: Marc Lehmann 
Date:   Sun May 23 00:48:53 2010 +0000

    256c enable docs, fix speling to colour everywhere

diff --git a/doc/rxvt.1.pod b/doc/rxvt.1.pod

--- a/doc/rxvt.1.pod
+++ b/doc/rxvt.1.pod
@@ -154,7 +154,7 @@ 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. Example:

    @@RXVT_NAME@@ -tr -tint blue -sh 40
@@ -170,7 +170,7 @@ resource I.
 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, B, B - color values averaging, B,
+B, B, B - colour values averaging, B,
 B, B, B, B, B, B,
 B, B, B, B, B. The default is
 alpha-blending. Compile I; resource I.
@@ -627,7 +627,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 section.
+names used are listed in the B section.

 Colours higher than 15 cannot be set using resources (yet), but can be
 changed using an escape command (see @@RXVT_NAME@@(7)).
@@ -678,7 +678,7 @@ use the background colour.

 B: simulate reverse video by foreground and background colours;
 option B<-rv>. B: regular screen colours [default]; option
-B<+rv>. See note in B section.
+B<+rv>. See note in B section.

 =item B I

@@ -1458,7 +1458,7 @@ it can be seen via the I 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
@@ -1517,9 +1517,9 @@ White.
 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 opaquenes percentage enclosed in
 brackets, i.e. C<[percent]>, where C 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
@@ -1637,7 +1637,7 @@ If set and accessible, gives the name of a X resource file to be loaded by

 =item B

-Color names.
+Colour names.

 =back

diff --git a/doc/rxvt.7.pod b/doc/rxvt.7.pod

--- a/doc/rxvt.7.pod
+++ b/doc/rxvt.7.pod
@@ -107,12 +107,13 @@ meaning it couldn't connect to the daemon, it will start the daemon and
 re-run the command. Subsequent invocations of the script will re-use the
 existing daemon.

-=head3 How do I distinguish whether 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 colours 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,
 slrn, Midnight Commander automatically check this variable to decide
-whether or not to use color.
+whether or not to use colour.

 =head3 How do I set the correct, full IP address for the DISPLAY variable?

@@ -363,15 +364,15 @@ the text blink when compiled with C<--enable-text-blink>. Without
 C<--enable-text-blink>, the blink attribute will be ignored.

 On ANSI colours, bold/blink attributes are used to set high-intensity
-foreground/background colors.
+foreground/background colours.

-color0-7 are the low-intensity colors.
+color0-7 are the low-intensity colours.

-color8-15 are the corresponding high-intensity colors.
+color8-15 are the corresponding high-intensity colours.

-=head3 I don't like the screen colors.  How do I change them?
+=head3 I don't like the screen colours.  How do I change them?

-You can change the screen colors at run-time using F<~/.Xdefaults>
+You can change the screen colours at run-time using F<~/.Xdefaults>
 resources (or as long-options).

 Here are values that are supposed to resemble a VGA screen,
@@ -395,7 +396,7 @@ including the murky brown that passes for low-intensity yellow:
    URxvt.color14:  #00FFFF
    URxvt.color15:  #FFFFFF

-And here is a more complete set of non-standard colors.
+And here is a more complete set of non-standard colours.

    URxvt.cursorColor:  #dc74d1
    URxvt.pointerColor: #dc74d1
@@ -1625,7 +1626,7 @@ Character Attributes (SGR)
 	B<< C >>	fg/bg Blue
 	B<< C >>	fg/bg Magenta
 	B<< C >>	fg/bg Cyan
-	B<< C >>	set fg/bg to color #m (ISO 8613-6)
+	B<< C >>	set fg/bg to colour #m (ISO 8613-6)
 	B<< C >>	fg/bg White
 	B<< C >>	fg/bg Default
 	B<< C >>	fg/bg Bright Black
@@ -2254,8 +2255,9 @@ All

 =item --enable-everything

-Add (or remove) support for all non-multichoice options listed in
-C<./configure --help>, except for C<--enable-assert>.
+Add (or remove) support for all non-multichoice options listed
+in C<./configure --help>, except for C<--enable-assert> and
+C<--enable-256-color>.

 You can specify this and then disable options you do not like by
 I this with the appropriate C<--disable-...> arguments,
@@ -2263,10 +2265,6 @@ 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-256-color (default: off)
-
-Add support for 256 colors.
-
 =item --enable-xft (default: enabled)

 Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
@@ -2455,7 +2453,7 @@ in combination with other switches) is:
 It also enables some non-essential features otherwise disabled, such as:

   some round-trip time optimisations
-  nearest color allocation on pseudocolor screens
+  nearest colour allocation on pseudocolor screens
   UTF8_STRING support for selection
   sgr modes 90..97 and 100..107
   backindex and forwardindex escape sequences
@@ -2522,6 +2520,19 @@ resource standpoint.
 Enables the assertions in the code, normally disabled. This switch is only
 useful when developing rxvt-unicode.

+=item --enable-256-color (default: off)
+
+Force use of so-called 256 colour mode, to work around buggy applications
+that do not support termcap/terminfo, or simply improve support for
+applications hardcoding the xterm 256 colour table.
+
+This switch breaks termcap/terminfo compatibility to C,
+and consequently sets C to C by default
+(F conatins termcap/terminfo defintiions for both).
+
+It also results in higher memory usage and can slow down @@RXVT_NAME@@
+dramatically when more than six fonts are in use by a terminal instance.
+
 =item --with-afterimage-config=DIR

 Look for the libAfterImage config script in DIR.

-----END OF PAGE-----