<html>#2321: allow use of LaTeX newcommand in thorn documentation
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>The <code>sim-ThornGuide</code> target merges all TeX documentation files and produces a single PDF file as output. This break is <code>documentation.tex</code> file use <code>\newcommand</code> to define (possibly conflicting commands). Pull request <a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactus/pull-requests/83/cactus-support-newcommand-in-documentation/diff" rel="nofollow">https://bitbucket.org/cactuscode/cactus/pull-requests/83/cactus-support-newcommand-in-documentation/diff</a> encloses the extracted part in a <code>\begingroup</code> … <code>\endgroup</code> thus ensuring that commands are only locally defined for each thorn.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2321/allow-use-of-latex-newcommand-in-thorn'>https://bitbucket.org/einsteintoolkit/tickets/issues/2321/allow-use-of-latex-newcommand-in-thorn</a></p>
</html>