<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: TeX capacity exceeded error</title>
	<atom:link href="http://handyfloss.net/2006.11/tex-capacity-exceeded-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/</link>
	<description>Because FLOSS is handy, isn&#039;t it?</description>
	<lastBuildDate>Thu, 09 Sep 2010 04:46:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: bill</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-71614</link>
		<dc:creator>bill</dc:creator>
		<pubDate>Fri, 03 Sep 2010 19:51:07 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-71614</guid>
		<description>I also encountered this error with MiKTeX and TeXnicCenter on Windows 7.
What did the trick for me was to delete the temporary junk files (i.e. all except the .tex and .bib).
Maybe I should also mention, that they were left overs from working on some linux machine...</description>
		<content:encoded><![CDATA[<p>I also encountered this error with MiKTeX and TeXnicCenter on Windows 7.<br />
What did the trick for me was to delete the temporary junk files (i.e. all except the .tex and .bib).<br />
Maybe I should also mention, that they were left overs from working on some linux machine&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: didietok</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-59886</link>
		<dc:creator>didietok</dc:creator>
		<pubDate>Wed, 19 May 2010 01:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-59886</guid>
		<description>OMG, how stupid am I? i forgot to write {} after \begin{block}</description>
		<content:encoded><![CDATA[<p>OMG, how stupid am I? i forgot to write {} after \begin{block}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luca</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-59410</link>
		<dc:creator>Luca</dc:creator>
		<pubDate>Fri, 07 May 2010 14:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-59410</guid>
		<description>Thank you so much Johann, it was the same for me. The problem was a \begin{block} without the required title in Beamer.</description>
		<content:encoded><![CDATA[<p>Thank you so much Johann, it was the same for me. The problem was a \begin{block} without the required title in Beamer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dai</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-43215</link>
		<dc:creator>Dai</dc:creator>
		<pubDate>Sun, 15 Nov 2009 16:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-43215</guid>
		<description>Should have mentioned that my problems were also encountered with Beamer</description>
		<content:encoded><![CDATA[<p>Should have mentioned that my problems were also encountered with Beamer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dai</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-43214</link>
		<dc:creator>Dai</dc:creator>
		<pubDate>Sun, 15 Nov 2009 16:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-43214</guid>
		<description>Thanks to Johan for highlighting what, for me, was the problem: always put a pair of curly braces when starting each block, i.e.

\begin{block}{}</description>
		<content:encoded><![CDATA[<p>Thanks to Johan for highlighting what, for me, was the problem: always put a pair of curly braces when starting each block, i.e.</p>
<p>\begin{block}{}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: isilanes</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-32608</link>
		<dc:creator>isilanes</dc:creator>
		<pubDate>Thu, 26 Mar 2009 11:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-32608</guid>
		<description>Thanks for your input, kok!</description>
		<content:encoded><![CDATA[<p>Thanks for your input, kok!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kok</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-32606</link>
		<dc:creator>kok</dc:creator>
		<pubDate>Thu, 26 Mar 2009 10:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-32606</guid>
		<description>To add to the list:

I got this error because I changed the spacing between items

\let\origitemize\itemize
\def\itemize{\origitemize\itemsep-0.5\baselineskip}

As this is a common tip to change the line space within an item environment, others might encounter the same problem.</description>
		<content:encoded><![CDATA[<p>To add to the list:</p>
<p>I got this error because I changed the spacing between items</p>
<p>\let\origitemize\itemize<br />
\def\itemize{\origitemize\itemsep-0.5\baselineskip}</p>
<p>As this is a common tip to change the line space within an item environment, others might encounter the same problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: isilanes</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-10616</link>
		<dc:creator>isilanes</dc:creator>
		<pubDate>Tue, 04 Nov 2008 14:34:03 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-10616</guid>
		<description>Thank you all for your comments. Apparently this error can be triggered in many ways. But the bottom line in most/all cases is that it is a stupid error from the user side, yet a simple (syntax) test that the LaTeX compiler doesn&#039;t run. It would be great to have a &quot;pre-processor&quot; that read the .tex file looking for obvious errors such as the above, then warn about them, instead of trying to compile and fail.</description>
		<content:encoded><![CDATA[<p>Thank you all for your comments. Apparently this error can be triggered in many ways. But the bottom line in most/all cases is that it is a stupid error from the user side, yet a simple (syntax) test that the LaTeX compiler doesn&#8217;t run. It would be great to have a &#8220;pre-processor&#8221; that read the .tex file looking for obvious errors such as the above, then warn about them, instead of trying to compile and fail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fernando Rozenblit</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-10415</link>
		<dc:creator>Fernando Rozenblit</dc:creator>
		<pubDate>Mon, 03 Nov 2008 17:50:02 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-10415</guid>
		<description>For me it was a &quot;\begin{block}&quot; that should be &quot;\begin{block}{}&quot;, using beamer.</description>
		<content:encoded><![CDATA[<p>For me it was a &#8220;\begin{block}&#8221; that should be &#8220;\begin{block}{}&#8221;, using beamer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TeX capacity exceeded error &#171; handyfloss</title>
		<link>http://handyfloss.net/2006.11/tex-capacity-exceeded-error/comment-page-1/#comment-5319</link>
		<dc:creator>TeX capacity exceeded error &#171; handyfloss</dc:creator>
		<pubDate>Wed, 17 Sep 2008 08:43:27 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=148#comment-5319</guid>
		<description>[...] Entry available at: http://handyfloss.net/2006.11/tex-capacity-exceeded-error/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Entry available at: <a href="http://handyfloss.net/2006.11/tex-capacity-exceeded-error/" rel="nofollow">http://handyfloss.net/2006.11/tex-capacity-exceeded-error/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
