Commit changelog for Maxima 5.35.
Merge branch 'master' of ssh://git.code.sf.net/p/maxima/code
Merge branch 'master' of ssh://git.code.sf.net/p/maxima/code
Add two more bugs to fixed list.
Does not echo the check_texinfo and warn_texinfo commands

Those two commands mislead the user into thinkink that there is an error
in the .texi files, when there is no problem.
Now past 5.35 branch point on master.
Adds two missing anchors
Merge branch 'master' of ssh://git.code.sf.net/p/maxima/code
Replace non-ASCII hyphens with ASCII.
(cherry picked from commit cce50bf305ef57a171ae8f69abb08f4d36f8bd75)
Restore build_index.pl to list of files to distribute.
Accidentally(?) nuked in commit 89dd74ee.
(cherry picked from commit d5e3d9b946321d908eef3736b9cdb70e6ca5cee9)
Merge branch 'master' of ssh://git.code.sf.net/p/maxima/code
Adds file texi2html.init to files that will be included in the distribution
Merge branch 'master' of ssh://git.code.sf.net/p/maxima/code
Fixes problem with EXTRA_DIST
Fix for bug #2854

This bug meant we got a hang from

    integrate(exp(-x)*sinh(sqrt(x)), x, 0, inf), domain: complex;

It happened in a limit computation in intsubs and was inside a lhospital
invocation. The regression (the computation hasn't always hanged) was
caused by commit 17ca33.

Before that commit, lhospital calculated a limit of the form (a+b)/c by
calling limit on ratsimp(a/c) + ratsimp(b/c). This limit can return a
function containing $UND, which caused a different bug, where a
L'Hospital's rule invocation would merrily return a result of the form
f(und)/g(und). Obviously, that wasn't great.

The "fix" for that bug was to instead call limit on something of the
form multthru(ratsimp((a+b)/c)). It seems that the bug went away because
the limit calculation that was returning $UND now failed and returned
NIL.

This patch re-instates the special behaviour for limits of quotient
whose numerator is a quotient (which fixes #2854). It also checks that
the result of the limit calculation is free of $UND terms, which seems
like a more principled way to fix the latter bug.

I'm not sure whether we should also fail on $IND terms: this patch
doesn't, but it would be pretty trivial to do so.
Avoid an error on limit(ind * inf)

This was triggered because we called $CSIGN from GETSIGNL inside a limit
calculation. Deep inside the sign calculation, it tries to calculate the
sign of $IND. If the special variable LIMITP is set, this just returns
$PNZ, otherwise it raises an error.

Unfortunately, $CSIGN was altered in commit c2bebf5 (in 2009) to bind
LIMITP to nil. To me, that seems like the wrong thing to do but I'm not
absolutely sure so I'm going for the "band-aid" approach and
binding *COMPLEX-SIGN* and calling $SIGN manually from the limit
calculation.

This no longer raises an error, but now SIMPINF-IC (my code, so my
fault!) returns a horrible result that looks like

   ind * limit(x, x, inf)

As a result, this patch also teaches SIMPINF-IC to return its original
argument if it hasn't improved as a result of calling $LIMIT on it.

I've also added a test to rtest_limit.mac which makes sure that
limit(ind*inf) doesn't raise an error.
o Fix plus regression tests for SF bug #2853 abs_integrate hangs after encountering log(0)

o Correct calling supcontext

o Don't load basic--push and pop are in-core