Sublime Forum

Build 4154: Cannot create PDF

#1

Hello!

I did an update to Build 4154 today. I am using Windows (current version) and SumatraPDF. Since that update Sublime does not create a PDF any more. I tried to downgrade to an older version of Sublime (Veeam Agent is my backup software), but that did not help. I still could not create a PDF. I tried with both versions of SumatraPDF: portable and non portable version.

But I think it is a problem of Sublime, not of SumatraPDF.

Compiling seems to work as always, it says: “Basic Builder: running pdflatex…done.” But as I said, after that message no PDF is built.

Kind Regards

Christoph

0 Likes

#2

SumatraPDF is just a viewer.

Which plugin/toolchain is used to create PDF?

0 Likes

#3

Hello deathaxe,

thank you very much for your reply.

I could solve the problem. I deleted all LaTeX auxiliary files which are created automatically. Afterwards it worked as it should.

Other Question: Do you know a better editor for Sublime (Windows)? Which is the most common?

0 Likes

#4

The short answer: no.

I’ve used to use Notepad++ for a long time, but only use ST as my primary general purpose editor these days. Many users seem to hype VS Code, but I find it to bloated, clunky and slow. Not to say it doesn’t support the primary syntaxes I need on a daily basis.

But that heavily depends on personal requirements, taste and capablities.

I didn’t find a better editor back in the days I moved away from Notepad++.

0 Likes

#5

My problem with SumatraPDF is described here:

https://tex.stackexchange.com/questions/460971/sumatra-inverse-search-open-new-window-in-sublime

I could not solve it yet. If I click somewhere in the PDF, Sublime always creates a new file.

0 Likes

#6

ST focuses an already open file when calling sublime_text.exe <file>:<line> reliably regardless the casing of given <file> on Windows. That’s basically what SumatraPDF is asking it for as well.

Behavior depends on at least the following settings:

  • "open_files_in_new_window": "never" (if set to "always", it would open new window for each file).
  • maybe "select_across_groups": true (ST refocused the file regardless this setting on my end, but I am uncertain whether it might be involved).

The only circumstance I am aware of, this might fail is if junctions or symlinks are involved. ST might not be able to find an already open file if its path differs due to those being involved.

0 Likes

#7

Thank you so much! I’ve changed to “never” and now it works perfect!

0 Likes