Re: Making makeinfo --no-split the default?

[Karl Berry]

Hi Jerry,

    Is there any advice you could give us?  Any reason _not_ to use
    --no-split?

It seems gcc.* and gccint.* are both a bit over 1mb.  That still seems
like a fair amount to haul into memory at once merely for a manual,
although not absurdly much these days, true enough.

An in-between alternative would be to use a larger --split-size, say
500,000 for an example.  However, if it eases the distribution to have a
single .info for each GCC .texi, I don't think there's any compelling
reason not to, at this point.

    (One of our developers actually suggested you might consider making
    --no-split the default for makeinfo itself.)

Yes ...  It would be a better default for .info, but for HTML output, I
think having one node per file is still the best default, because of
network bandwidth considerations.  And having the default be one way for
one format and another way for another seems bad.

However, now that I'm writing this, we could achieve the same effect by
increasing the default split-size from 50,000.  I think I'll do that for
the next release.

Thanks,
karl