Re: Problem with @setcontentsaftertitlepage

[Karl Berry]

    motivation for this change in the first place.

The motivation was simple enough: compatibility (what else).

For many years, every Texinfo file had @contents (and optionally
@shortcontents) at the end, because that was the way rms originally
wrote texinfo.tex, so that the TOC would be typeset using the info from
that run.  People used dviselect to move the toc page(s) to the right
place.

When I eventually changed texinfo.tex to read a .toc from a previous
run, so that @contents could be put in the normal place in the input
file, I also implemented @setcontentsafter... (and
@setshortcontentsafter...) so that people could get the right output
from existing Texinfo files without changing them, via texi2dvi -t
@setcontentsafter...

Whether anyone actually made use of that, I don't know.  I never heard,
one way or another.

    I don't think that there's a good reason to use
    @setcontentsaftertitlepage in any Texinfo file anyway, 

Indeed, not any more.  I surmise the @set*contentsafter... commands
could be non-implemented by an \errmessage saying "move your @*contents
command".  -k