Comments on: Last update in 2010

By: admin

admin — Sat, 01 Jan 2011 18:13:00 +0000

It should be clear, that it needs more cpu than pdflatex itself. I wrote a new parser that is faster and has no bugs (I hope).

By: Petter

Petter — Sat, 01 Jan 2011 17:49:11 +0000

Well, at least it can compile my project without crashing now. However, it does so while using a lot of CPU — even more than pdflatex itself at times. There are still problems with filenames sometimes appearing as “filename.ext)” in the Report, i.e. with a trailing right parenthesis.

By: admin

admin — Fri, 31 Dec 2010 16:11:12 +0000

A new version is uploaded.

By: Nils

Nils — Thu, 30 Dec 2010 14:51:35 +0000

You can use Inlage 4.4 until this bug is fixed.

By: Nils

Nils — Wed, 29 Dec 2010 16:16:48 +0000

Working on it…

Could you send me the files via Email, that crashes the ouput parser, please?

By: Petter

Petter — Wed, 29 Dec 2010 13:44:10 +0000

I’m not sure my crash reports arrive. I click ‘yes’ to send the exception report but I cannot see any data being transferred in the Task Manager and Inlage completely crashes shortly after. I have had to stop using Inlage to compile my document and go back to the command line. My main project is crashing 100% of the time.

By: Kim

Kim — Tue, 28 Dec 2010 21:52:13 +0000

I have the same problem for files that worked well in last version: crash

By: Petter

Petter — Tue, 28 Dec 2010 01:49:03 +0000

The pdflatex output parser sometimes crashes Inlage. I’ve sent a couple of crash reports.

By: Petter

Petter — Mon, 27 Dec 2010 13:43:43 +0000

If one uses a “.synctex.gz” file instead of a “.synctex” file, one has to press F9 in the main project file. Pressing F9 with the cursor in any chapter tex files results in an error.