The MWE below yields:

     Missing number, treated as zero.
     <to be read again> 

for the itemize list. The enumerate list is fine.

If I remove the \usepackage[realmainfile]{currfile}, or \setlist{leftmargin=*}, things work fine, but I have those there for reasons as per the linked questions.




%% https://tex.stackexchange.com/questions/68684/corrupted-texlive2012-installation-option-clash-for-currfile


%% https://tex.stackexchange.com/questions/21669/enumitem-itemize-environment-shifts-text-into-margin-or-overlaps-other-text

    \begin{itemize}%    This does not work!!
        \item testing.
    \begin{enumerate}% This works fine.
        \item testing.
  • Actually package bugs are not on-topic on a Q&A site. It would be better to sent bug reports for packages direct to the package author(s), or at least notify them about them as well. In this specific case I happen to be the author of currfile, but I still sometimes miss these kinds of "questions" here. – Martin Scharrer Oct 28 '12 at 8:59
  • Works with currfile v0.6 but not with v0.7. However the error message seems to come from enumitem. I wonder if it uses currfile in any way... – Martin Scharrer Oct 28 '12 at 9:06
  • Found it:enumitem loads some new font at \begin{itemize} which changes the currfiledepth counter when the file is entered and left again. However, enumitem already locally changed the meaning of \value which is used by currfile in an numeric test. \value is supposed to return a numeric value but in this case no longer does, which triggers the error message. After checking the enumitem manual I noticed that the author is aware about the fact that changing \value is "tricky". I can change the code of currfile to avoid this, but actually enumitem should leave \value alone. – Martin Scharrer Oct 28 '12 at 9:32
  • I just uploaded currfile v0.7a 2012/10/28 to CTAN which avoids this error by not using \value. You can find the code as well at bitbucket.org/martin_scharrer/currfile. I should notify the enumitem author too. I will close this "question" as "too localized (in time)" now. This is usually done with bug reports on this site. – Martin Scharrer Oct 28 '12 at 9:45
  • It seems a bug in enumitem, indeed. I'll have a look at it. – Javier Bezos Oct 28 '12 at 12:05