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

commit e5ca63c3757b9295f158fb4971d70664669d193f
Author: Marc Lehmann 
Date:   Sun Jun 26 20:11:22 2005 +0000

    *** empty log message ***

diff --git a/Changes b/Changes

--- a/Changes
+++ b/Changes
@@ -11,7 +11,7 @@ WISH: OnTheSpot editing, or maybe switch to miiiiiiif
 WISH: tabbed windows (hey, just use screen...)
 WISH: just for fun, do shade and tint with XRender.

-5.6
+5.6  Sun Jun 26 22:11:13 CEST 2005
         - R_SB_RXVT bitset value was 0, so rxvt scrollbar was initialised
           every time resulting in display errors (original rxvt also affected).
           Reported by Jasmin Buchert.
@@ -26,7 +26,7 @@ WISH: just for fun, do shade and tint with XRender.
           more than required, but that's better than undershooting and
           cutting pieces off of characters.
         - rxvt is now more restrictive in what font heights it accepts for
-          fonts that will likely overshoot or underhsoot lines.
+          fonts that will likely overshoot or undershoot lines.
         - fix a cosmetic problem with the unfocused cursor on a wide character
           at the end of the line (reported by Mikachu).
         - wide characters not fitting into the end of the line will be
diff --git a/doc/rxvt.7.pod b/doc/rxvt.7.pod

--- a/doc/rxvt.7.pod
+++ b/doc/rxvt.7.pod
@@ -341,6 +341,11 @@ The rxvt-unicode author insists that the right way to fix this is in the
 system libraries once and for all, instead of forcing every app to carry
 complete replacements for them :)

+=item 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.
+
 =item How does rxvt-unicode determine the encoding to use?

 =item Is there an option to switch encodings?

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