Compiling using Latexmk produces DVI output no matter what dropdown option is set in the output format.

Type of JetBrains IDE (IntelliJ, PyCharm, etc.) and version

PyCharm 2020.2

Operating System

Windows 10

TeXiFy IDEA version

0.7.1-alpha.3

What I did (steps to reproduce)

Compiled a .tex file using Latexmk with the following .latexmkrc options:

$latex = 'latex  %O  --shell-escape %S';
$pdflatex = 'lualatex  %O  --shell-escape %S';

and “PDF” selected in the output format dropdown.

Expected behavior

A .PDF file is produced.

Actual behavior

A .DVI file is produced (which often results in compilation errors such as “Cannot determine size of graphic” for \includegraphics)

Temporary Fix

Adding -pdf to the Custom compiler arguments fixes the problem.

[PHPirates]

I think the best default behaviour is to allow the run configuration to append to what is in the .latexmkrc file

This is what happens, in fact it is unavoidable: latexmk will simply read the latexmkrc file first (it did that in the old situation too, as it’s a latexmk feature), and after that apply the command line arguments given by TeXiFy. Since this meant that configurations in latexmkrc files were always overridden by TeXiFy for some arguments like output format (example in #1586) it was not possible in the old sitation to use latexmkrc files as intended, because output format would be always overridden to be pdf. I have to check but it might be the case that the output format is the only setting that should default to ‘use latexmkrc configuration’, as other default arguments are not reflected in the UI.

[ralphieraccoon]

I see, so that’s why it worked before, I wasn’t using any output format arguments in my .latexmkrc file so I never noticed a problem and it worked for my use case. Going forward your default argument idea seems like the best option, I don’t know about others but I tend to use a mix of both, use the .latexmkrc for a number of .tex files in the same folder for options that apply to all of them (like using LuaLaTeX to typeset huge datasets) and then have a run configuration for each individual file with command line arguments and output format only for that file.

I think latexmk uses DVI by default unless I’m mistaken. Another option might be to disable the drop down if $-pdf; or $-dvi; are detected in the .latexmkrc file, as then it’s clear the user is using it to determine the output format.