From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeffrey A Law <law@hurl.cygnus.com>
To: craig@jcb-sc.com
Cc: egcs@egcs.cygnus.com
Subject: Re: 1.1.2 bug, news lists 
Date: Wed, 31 Mar 1999 23:46:00 -0000
Message-ID: <27168.921025252@hurl.cygnus.com>
References: <19990309234749.17043.qmail@deer>
X-SW-Source: 1999-03n/msg00364.html
Message-ID: <19990331234600.uj85oPS2PxwY-liLCr8tTkqk4XdGUH0zR5rV-QDKdN4@z>

  In message < 19990309234749.17043.qmail@deer >you write:
  > Jeff, I've finally looked at these.  *Really* nice.  Two things:
  > 
  >   1.  g77_bugs.html grabs the entire "Known Causes Of Trouble..."
  >       section of the manual, which is pretty big.  I think this is
  >       good, at least theoretically, but...
I think it's good too :-)  And pointing into a subsection is more difficult :-)


  >   2.  Chasing a link, even to a node in the currently open page,
  >       can sometimes cause the entire page to be re-read.  (E.g.
  >       this happens starting with g77_bugs.html and chasing "But-Bugs"
  >       in the first menu.  At least for me, using lynx.)
That's because the links, which appear to you to be in the same file are
actually in different files.

ie, you started by looking at g77_news.html  When you follow a link you'll
find that you actually go into something like g77_20.html

If there's a better way to do this I'm open to suggestions.


  > I'm planning on adding links to these resources (g77_toc.html,
  > g77_bugs.html, and g77_news.html) to g77's documentation for egcs 1.2
  > *and*, unless you say otherwise, for egcs 1.1.2.
Please do.

  > But I won't get to it before 11pm tonite at the earliest, and perhaps
  > not until tomorrow or Thursday.  (This is going to be a busy week for me,
  > for reasons unrelated to egcs.)
That should be fine since I'll spin the release on Friday after updating
the version #s and the like.

Thanks,
jef