Date: Tue, 9 Sep 1997 19:34:09 -0700 (PDT)
Message-Id: <199709100234.TAA28530@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: Suggestion: emacs handling gzipped info files
Cc: djgpp AT delorie DOT com
Precedence: bulk

At 02:39  9/9/1997 +0300, Eli Zaretskii wrote:
>
>On Mon, 8 Sep 1997, Nate Eldredge wrote:
>
>> I made the GCC info file as one big file (with makeinfo --no-split). It
>> works fine when not gzipped, but when I gzip it (to gcc.inz), info can't
>> find nodes that came from included files in the original texinfo source.
>
>Sorry, I don't have time to do this myself, so here's what I'd ask you
>to check:
>
>   1) Does gcc.inz work with the standalone Info?
Yes it does.
Also, I was wrong about the exact symptoms. It isn't to do with included
files. When I view it in Emacs, one particular node is garbled, almost
dissociated-looking, and every node after that is inaccessible. Which node
it is varies with the compression I tell gzip to use (i.e. -7 vs. -8), and
probably the phase of the moon. :)
>
>   2) Try this:
>
>      gunzip -c gcc.inz > gcc2.inf
The resulting file works with both info and Emacs, so gunzip is not at fault.

Also, running dtou doesn't change anything.

So it looks like the problem is with Emacs. This should be a fun one to
track down (yeah, right).

Nate Eldredge
eldredge AT ap DOT net