Date: Wed, 11 Jul 2001 18:52:50 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "chris.danx" <chris DOT danx AT ntlworld DOT com>
Message-Id: <2950-Wed11Jul2001185249+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: djgpp AT delorie DOT com
In-reply-to: <dTX27.26235$B56.4610229@news2-win.server.ntlworld.com>
	(chris DOT danx AT ntlworld DOT com)
Subject: Re: Question on GPP 2.8.1 and DJGPP
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010711081652 DOT 1314F-100000 AT is> <dTX27.26235$B56 DOT 4610229 AT news2-win DOT server DOT ntlworld DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "chris.danx" <chris DOT danx AT ntlworld DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Wed, 11 Jul 2001 13:46:16 +0100
> >
> > I think a much less painful way would be to edit the patch file, and
> > manuall modify the file names to their original long names.  If done
> > carefully, this will produce a patch that will simply work with no fuss.
> 
> I've modified some of the file names in the patch file, but with
> each file comes more hunks that don't work.

Sorry, I don't understand this sentence.  Could you give an example?

> I don't even know what a hunk

A hunk is a fragment of the patch file which describes a change to a
contiguous range of source file lines.  Each hunk begins with a header
that states the affected lines' numbers, and then the actual changed
lines.

Here's an example of a hunk:

    @@ -999,6 +999,9 @@ IT_write_glyphs (struct glyph *str, int 
	      register GLYPH g = GLYPH_FROM_CHAR_GLYPH (*str);
	      int glyph_not_in_table = 0;

    +	  /* If g is negative, it means we have a multibyte character
    +	     in *str.  That's what GLYPH_FROM_CHAR_GLYPH returns for
    +	     multibyte characters.  */
	      if (g < 0 || g >= tlen)
		{
		  /* This glyph doesn't have an entry in Vglyph_table.  */
    @@ -1034,7 +1037,7 @@ IT_write_glyphs (struct glyph *str, int 

	      /* If the face of this glyph is different from the current
		 screen face, update the screen attribute byte.  */
    -	  cf = FAST_GLYPH_FACE (g);
    +	  cf = str->face_id;
	      if (cf != screen_face)
		IT_set_face (cf);	/* handles invalid faces gracefully */