Texmaker and TeXstudioPossible to show complete log when running custom build?

Information and discussion about Texmaker, an integrated LaTeX environment for several platforms, and the related TeXstudio
Post Reply
belonesox
Posts: 4
Joined: Fri May 08, 2015 6:31 pm

Possible to show complete log when running custom build?

Post by belonesox »

Hello!

TeXMaker show and parse log only from last tex-compiling command (from %1.log).

It is OK when building consist of only one texbuilding command but is not OK if we need using complex custom build (make, scons, etc), because all output (except last %1.log from last tex-compiling) is lost.

Or may be possible to configure TexMaker (or something else) to show complete output log in Log Window?
(Yes, it possible to hack build process and redirect all output to %.log, but may be where is a some config magic in TexMaker?)

Recommended reading 2024:

LaTeXguide.org • LaTeX-Cookbook.net • TikZ.org

NEW: TikZ book now 40% off at Amazon.com for a short time.

User avatar
Johannes_B
Site Moderator
Posts: 4182
Joined: Thu Nov 01, 2012 4:08 pm

Re: Possible to show complete log when running custom build?

Post by Johannes_B »

Hi and welcome,

LaTeX will overwrite the log-file of the previous run.

If we manually compile, the first run will produce some auxiliary files, all of those are read with the start of the next run and at the end, the updated files are written to be read at the next file, and so on and so on. You can immidiately check the logs and aux files.

When working with a script, batch job or make file, this manually checking chance is lost and the script takes over. Same for TeXmaker.

Can you elaborate on what you are trying to do? We might find a better solution
The smart way: Calm down and take a deep breath, read posts and provided links attentively, try to understand and ask if necessary.
belonesox
Posts: 4
Joined: Fri May 08, 2015 6:31 pm

Re: Possible to show complete log when running custom build?

Post by belonesox »

Hi!

In my Latex workflow lots of tasks are runned:
* Graphviz -> PDF
* Python -> LateX -> PDF
* Gnuplot -> LateX

a lot of other.


All these tasks output to stdout/stderr.
I worked with lot of editors, all of them simply display in log window all output, and then parse log for LaTeX errors or other errors.

It is very convienient — see log of all build process and recognize different type of errors (biber/makeindex errors, errors in dot/neato-files, errors in python code, etc)

It seems TeXMaker completely ignored all these outputs, just showing latex log for main latex file.

Yes, probably it possible to capture all these output, then append it to last latex log for TexMaker...
But this solution looks ugly, and I wish to be sure, that it is impossible to configure TexMaker for doing this task by a right way.
Post Reply