search

msiniscalchi / atom-latextools

Port of the LaTeXTools package to the Atom editor
MIT License
58 stars 21 forks source link

Debuging latex codes in Latextools is annoying. Please add separate command options for "pdflatex" and "bibtex". #75

Open pxdu opened 8 years ago

pxdu commented 8 years ago

I have used Latextools intensively. The "ctrl-alt-b" is working very nicely but is very hard to debug.

The current build command in Latextools "ctrl-alt-b" gives the "texify" command in MikTeX or "latexmk" in TeXlive or MacTeX. However this command (texify or latexmk) does not give good error analysis which is not clear enough to debug latex codes. I think it because `texify' combines many steps together, pdflatex + bibtex and so on.... Many times I had to go back to a command line to run pdflatex and bibtex one by one to debug the latex codes.

Could you please add choices to do "pdflatex" and "bibtex" separately so that the debug step is easier for us? This will be so wonderful.

Thanks very much in advance for any possible help.

ig0774 commented 8 years ago

Eventually, more customisable builders will be coming that will handle this.

However, could you be a bit clearer about what you mean by "debugging" and "good error analysis"? LaTeXTools behaviour is to try to read any errors and warnings from the generated logs and display them in the LaTeXTools console. Are you saying there are error and / or warnings that appear in you log file but not in the console? Because, if so, simply changing the command that is run will not help with anything, since the messages displayed in the console are filtered through the same log parsing code each time.

pxdu commented 8 years ago

The error messages from the log file of Latextools are really helpful. I depend on it most of the time. However, they from the log file are not working at best since cntrl-alt-b combines many processes at the same time. Furthermore in the latex codes that use under development packages such as pgfplots, tikz,...., Miktex/Texlive frequently just hangs. In that case, the error messages may not show up properly and clearly enough. I try rebuilding (ctrl-alt-b) and restarting atom but they are not helpful. We need a kill (like ctrl-c in linux) comand to kill Miktex/Texlive running processes so that the error messages may show up.

I want to say more about the pdflex and bibtex. We only compile the bibtex a couple of times and we use pdflatex more than a hundred times during the writing of a paper. Thus separate these is essential for latex users.