It also shows that pasting command that TexMaker uses into command line effects in properly ended compilation. That is why I madeĪnother recording clearly showing what's going on: youtu.be/ wj8OKjdZu9I
I understand you may not believe me, in fact- pdf could be created before, video doesn't prove that it wasn't. It runs pdflatex and compile bibliographies, indexes and glossaries automatically to get a fully compiled document, that is something similar to: pdfLaTeX + BibTeX + MakeIndex + MakeGlossaries + pdfLaTeX + View PDF.
Pdfatex was launched and compiiled the document, as you can see on the Video compilation started at about 11:55:53, ended about 11:55:58. In WinEdt, the command 'PDFTeXify' is some sort of 'Quick Build' command (also exists 'TeXify' for the DVI cycle). " it proves that the source has never been compiled by pdflatex and that the pdf are not produced by the compilation you're supposed to have launched." - I don't agree here - It doesn't prove anything. "everybody can see on your video (58 s) that the main.pdf file has exactly the same date and time (11:55) than the source main.tex" - I agree "the log file is not displayed automatically as it should be" - I agree! "the pdf process should stop himself in 1 or 2 seconds" - I agree! I suspect there is a strange bug in the Texmaker binaries. No more weird freezes by compiling in the TeXstudio GUI instead of Texmaker. Then I installed TeXstudio 2.5.2 (SVN 3733M) as a replacement for Texmaker. Texlive-binaries, texlive-latex-base, texlive-publishers, texlive-latex-extra Then I decided to totally remove texmaker, but to keep the following packages installed: So crosstesting did not help! And there was never anything wrong with pdflatex or bibtex. tex file using pdflatex and bibtex directly in the Terminal always kept working. I then tried various pdflatex compilation options. Use the Quick Build command to compile and. The compile command is given by clicking the arrow to. Thesis Templates Set the Quick Build command configuration to: PdfLaTeX + Bib(la)tex) + PdfLaTeX (x2) + View Pdf. In the beginning, it worked, but as time moved on, Texmaker would just hang (both QT4 and QT5 versions) on "Process started" and not do anything afterwards, when trying to compile using pdflatex. In Texmaker, Quick Build or PDFLaTeX needs to be chosen in the dropdown menu in the top toolbar. Switching to a fancy editor with trillions of magical functions can be done a few hours later. You learn the basic interaction with the underlying program.
I always recommend to start with a basic editor like Texworks (mentioned in the video and installed with MikTeX). I can confirm Texmaker (all versions) contains strange bugs, especially when trying to compile a. Make sure to save the file with the ending. I have tested TexMaker 3.4 and also Texmaker 4.0.1 using QT5 and QT4 in Ubuntu 13.04 (raring).