I have a simple template whose codes I copy over to a new document each time. But once in a while, when I compile the new document, the old template still shows up as the dvi (despite multiple re-compilation).

I would tweak this and that, restart WinEdt, etc., and would get it to work. But not knowing the reason really bugs me.

It sounds like it has an obvious reason that I simply do not know. Can anyone help?

  • 1
    Welcome to TeX.sx! Please add a minimal working example (MWE) that illustrates your problem. It is considered a lot better to put in some code that will compile, as it makes it a lot easier for us to copy it into our text editor and work with it, and see exactly what it is you are trying to do. – hpesoj626 Oct 28 '12 at 8:22
  • 2
    In these cases the log file should show an error that it can not right to the dvi file. I have not seen that with dvi, but it is very common with pdf, if you use acrobat to view the pdf it holds the file locked for writing so pdflatex can not make a new file. If that isn't the problem (ie the log shows no error) you will need to give more information. – David Carlisle Oct 28 '12 at 10:55
  • thank you for trying to help, but the problem is the code is always the same. Yet when I compiled it the first few times, winedt compiled a CLOSED document instead of the one opening. Then I tried to compile the same code again, and suddenly it works... – Heisenberg Oct 28 '12 at 17:57
  • 1
    @user19506: I changed the title of your question because your issue is a problem with WinEdt, not LaTeX. For me it sounds that you make the (closed) template the main file ... – Mensch Oct 29 '12 at 14:06
  • 1
    You are probably working inside a project and once in a while clicking the view button instead of the compile button and WinEDT is opening the master document in the viewer. – percusse Nov 2 '12 at 16:41

As is the case for many other editors, in WinEdt one can define a project in which there exists a main file that we PDFLaTeXify. In this main file there are usually lots of \include{my other chapter} and/or preamble specifications.

Usually compile and view shortcuts point to the main file to prevent the compilation of TeX file fragments (standalone chapter files, figures that don't have a proper TeX preamble etc.).

In your example you might have defined a main file for a project in a template and probably View buttons are still pointing to your original main file's DVI or PDF output.

| improve this answer | |

I encountered exactly the same problem and I would like to improve this post.

It is not like what @percusse and @David had described the issue. And it really has to do with WinEdt, the editor and compiler. It is WinEdt that keeps compiling the same file and there is no problem of directing.

Though I am not sure where exactly did WinEdt went wrong, I would offer an easy cure of the problem: just to uninstall full (deleting everything) and reinstall the program again. This had fixed my problem.

| improve this answer | |
  • Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format. This solution does not really treat the root cause of the issue. – Paul Gessler May 7 '14 at 22:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.