# Tag Info

## New answers tagged debugging

0

The error message hints that a figure or a table are lost, but I saw this a few times with no text or float loss. The problem may be that a float is used inside a box. What makes it tricky to nail is the fact that the error might not arise immediately, but only after text is added elsewhere. Try replacing \marginpar with \marginnote (of the marginnote ...

3

This is a “feature” of LaTeX, I'm afraid. Since amsart automatically loads amsfonts, which defines \mathfrak; it appears that redefining commands defined with \DeclareMathAlphabet is not possible with the current kernel. The problem shows up with a very minimal document: \documentclass{amsart} \usepackage[frak=boondox]{mathalfa} \begin{document} {\small ...

1

The error has nothing to do with TikZ. It appears to be an incompatibility between mathalfa, amsart, \scriptsize $something$.... This is not a complete diagnosis but it narrows it down a bit. (At least we can eliminate TikZ.) Minimal example I can get to reproduce the error: \documentclass{amsart}% substitute article for working code \usepackage [ ...

0

May not be a complete answer but here's what works for me after trial and error, they key point is ordering of the various \usepackage commands. %Better refs \usepackage{varioref} \usepackage{hyperref} \usepackage[nameinlink]{cleveref} \usepackage[usenames,dvipsnames]{xcolor} \usepackage[square,sort,comma,numbers]{natbib} \usepackage[color]{showkeys} and ...

1

Can it be something else than a bug?! Yes. Opened files should be closed (with close(filename))... The following code works. file fout=stdout; // to write on Terminal for(int j=1;j<=30;j=j+1) { write(fout,'\n'); write(fout,j); for (int i=j; i<50; i=i+1) { file in1=input("gag.dat").line().csv(); close(in1); // ...

0

I had the message: Unable to find target command: make_pdf after I had successfully installed the LatexTools package on ST3, and had the build command working. However, after restarting my system on mac OS X, the build command no longer worked. The solution in this case was to restart ST3 from the terminal command line using subl

7

If you update etex.sty to version 2.3 (which will be reaching ctan mirrors in the next day or so) then the original document runs without error, but with a warning explaining the original problem. I have added a check for this case to the package. Package etex Warning: Extended allocation already in use. (etex) etex.sty code will not be used. ...

Top 50 recent answers are included