[comp.windows.x] contrib/Xhp.R3Xt.shar

martin@CITI.UMICH.EDU (01/05/89)

When I FTPed this file (binary or ascii) I get:

150 Opening data connection for Xhp.R3Xt.shar (35.1.128.16,2714) (56981 bytes).
226 Transfer complete.
local: Xhp.R3Xt.shar remote: Xhp.R3Xt.shar
57929 bytes received in 36 seconds (1.6 Kbytes/s)
ftp> bye

when I unpack it I get:
8 citi:% mkdir /b/xsun/X.V11R3/contrib/widgets/Xhp/fixes/Xt
9 citi:% (cd !$; sh < ~/.i/newcontrib/Xhp.R3Xt.shar)
( cd /b/xsun/X.V11R3/contrib/widgets/Xhp/fixes/Xt ; sh < ~/.i/newcontrib/Xhp.R3X
t.shar )
shar: Extracting "README" (2948 characters)
shar: "README" unpacked with wrong size!
shar: Extracting "Xw.diff.Z.uu" (51590 characters)
shar: "Xw.diff.Z.uu" unpacked with wrong size!
shar: End of archive 1 (of 1).
You have unpacked all 1 archives.
10 citi:% ls -l /b/xsun/X.V11R3/contrib/widgets/Xhp/fixes/Xt
total 54
-rw-rw-r--  1 martin       2863 Jan  4 16:33 README
-rw-rw-r--  1 martin      51567 Jan  4 16:33 Xw.diff.Z.uu
11 citi:% diff ~/.i/newcontrib/Xhp.R3Xt.shar /tmp/Xhp.R3Xt.shar
12 citi:% 

The diff shows that bin/ascii mode makes no difference.

I think that the problem lies in the fact that this file is a
shell-archived-uuencoded-compressed-context-diff.

maybe it should be a compressed shell archived context-diff.

Here is some of the resulting diff file just for yuks.
diff -b -c5 Xw/Button.c Xw-R3/Button.c
***5Xw/Button.c Thu Nov 10 21:49:47 1988
--- Xw-R3/Button.c      Wed Jan  4 11:45:59 1989
. 
. 
. 
diff -b -c5 Xw/Cascade.c Xw-R3/Cascade.c
*** Xw/Cascade.c        Thu Nov 10 21:49:49 1988
---5Xw-R3/Cascade.c     Wed Jan  4 11:46:00 1989
. 
. 
. 

!i    /* set_values         */    NULL,
!i                      lNULL
. 
. 
. 
! static unsigned short bitmaps [9][16] =
  {
     {  1xFFFF, 0xFFFF, 0xFFFF, 0xFFFF,                 /*  Solid Foreground  */
        0xFFFF, 0xFFFF, 0xFFFF,im1xFFFF, 
        0xFFFF,i0xFFFF,im1xFFFF,im1xFFFF,i
        0xFFFF,im1xFFFF,i0xFFFF, 0xFFFF  },

--- 36,46 -----
  #include <X11/StriasDefs.h>


Boy that is screwed up.

I dunno where this file got screwed up, because the README file was also
munged a bit.  Anyone else have this problem?


Marty.