# Strange behavior using TexMaker [closed]

I compiled the source 2 days ago, it worked perfectly. Today, I ran it again, it's broken :(. Tex generated a bunch of errors, however I noticed it still produced the correct .pdf. I can't understand what happened? Anyone experienced this issue can help me out? Thank you.
This is one of the errors:

! Package catchfile Error: File "Expanding Fraction".w18' not found.


Next, I delete all source, just leave

\begin{document}
$x^2 + 2x$
\end{document}


The errors are still the same. There are 5 total:

! Package catchfile Error: File "Expanding Fraction".w18' not found.
! Argument of \zap@space has an extra }.
! Paragraph ended before \zap@space was complete.
! Paragraph ended before \ip@only@six was complete.
! Paragraph ended before \ip@only@six was complete.
! Undefined control sequence.


and they came from this file: /usr/share/texmf-texlive/tex-latex/ifplatform/ifplatform.sty

-
Can you add to your question a minimal, complete version (in the sense of a minimal working example) of your document allowing us to reproduce the problem? – Gonzalo Medina Jul 23 '11 at 2:34
I wish I could, but I'm afraid I won't be able to do so because even I left with a very simple example, it was still broken :(. I guess there were something wrong with the tex system itself, but I haven't figured out why. In fact, I deleted the \newcommand\TestAppExists[3]{#2} \usepackage{minted}, and it worked as expected. However, if I delete these two lines, I can't use minted package though. – Chan Jul 23 '11 at 2:37
I figured it out: if I delete the space of the file name, it works. So instead of Expanding Fraction, I have to rename it as ExpandingFraction. I really didn't know that pdflatex impose this limitation though. – Chan Jul 23 '11 at 2:45
I have had a few cases where existing .aux files cause problems with subsequent runs if changes have been made to the document. Try removing all the temp files that get created and see if that helps. – Peter Grill Jul 23 '11 at 3:06
@Chan: great that you found it out! I guess we could close this question then as too localized since the reason was just in the file name. Spaces in file names are a well known limitation. – Stefan Kottwitz Jul 23 '11 at 9:08
show 1 more comment

## closed as too localized by lockstep, Caramdir, egreg, Stefan Kottwitz♦Jul 24 '11 at 19:16

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.