Compiling minted code: *.pyg not available in src

[mike-a]

Started using TeXiFy a few days ago after about 10 years with TesXstudio. Looks like you have done a great project!

When compiling code listings with minted.sty I observe the Pygments [file].pyg being written to auxil folder in IntelliJ IDEA Ultimate. However, by default TeXiFy seems to require compiling the .pyg file to the src folder before final compilation to the out folder so exits after a "Could not find file" notice.

My search-fu didn't discover a solution. Is there a setting to set the folder for .pyg pre-processing?

[PHPirates]

TeXiFy seems to require compiling the .pyg file to the src folder

I just want to point out that if minted does not support using an auxil directory, in my opinion that is an issue with minted and not with TeXiFy.

However, as essentially TeXiFy is one big workaround for LaTeX problems anyway, there are of course plenty of solutions :)

• The quick workaround is of course to not use any auxil directory at all, just put everything in src
• You might want to double check if setting TEXINPUTS or another environment variable helps https://github.com/Hannah-Sten/TeXiFy-IDEA/wiki/Run-configurations#environment-variables
• If all else fails, we can do the same as with makeindex: after running, simply copy back the required files to src (hardcoded in TeXiFy).

A full example would be appreciated.

[PHPirates]

I just want to point out that if minted does not support using an auxil directory,

Actually, it does look like minted might support an auxil directory:

https://tex.stackexchange.com/questions/112953/error-when-using-minted-package-and-output-directory-option

[mike-a]

Thanks for reply. A, hopefuly helpful, assistive philosophical comment from a systems architect with 50+ experience in digital development... when dealing with child projects that rely on parent project packages, it is NEVER the parent that's at fault, it is a misunderstanding. Minted.sty package has successfully been around a long time! ;) If a long-term user of Latex IDE's like me is considering moving to a new product it has a lot of goodness, but always some wrinkles for a while. I accept it may be my misunderstanding, being new to product. :) But...

Example output...

Compilation environment: pdflatex -file-line-error -interaction=nonstopmode -synctex=1 -output-format=pdf -output-directory=/out -aux-directory=/auxil -include-directory=/src -8bit --shell-escape --time-statistics .tex

Compile log extract command...

(_minted-/default.pygstyle)
runsystem(pygmentize -l bash -f latex -P commandprefix=PYG -F tokenmerge -P stripnl=False -o _minted-/881E5C42915F939CBB17F835BFA090D80601E185E2356A0C918D0798704D8651.pygtex .pyg)...executed.

Compile log extract exception...

...sections/InstallHetznerServer.tex:6: Package minted Error: Missing Pygments output; \inputminted was probably given a file that does not exist--otherwise, you may need the outputdir package option, or may be using an incompatible build tool, or may be using frozencache with a missing file.

Compile process...
Outputs .pyg file to auxil folder (correct).
Outputs intermediate file to src/_minted-/default.pygstyle. This behaviour matches other IDEs like TexStudio, so presumably correct.

However, this log file output may be of concern...

(sections/InstallHetznerServer.tex
LaTeX Font Info: Font shape T1/phv/b/n' will be (Font) scaled to size 9.19998pt on input line 1. \openout3 = VanWebsiteMainFmMarkdown.pyg'.

(_minted-VanWebsiteMainFmMarkdown/default.pygstyle)
runsystem(pygmentize -l bash -f latex -P commandprefix=PYG -F tokenmerge -P str
ipnl=False -o _minted-VanWebsiteMainFmMarkdown/881E5C42915F939CBB17F835BFA090D8
0601E185E2356A0C918D0798704D8651.pygtex VanWebsiteMainFmMarkdown.pyg)...executed.

sections/InstallHetznerServer.tex:6: Package minted Error: Missing Pygments out
put; \inputminted was probably given a file that does not exist--otherwise, you may need
the outputdir package option, or may be using an incompatible build tool, or may be using frozencache with a missing file.

It seems the instruction prior to pygmentise instructions has sets a folder path that is then not returned to project root. This made me think there should be some project setting. For the avoidance of doubt, I set the relevant output folder in \RequirePackage[outputdir=<dir>{minted} but that did not work so I returned the package load to \RequirePackage{minted}.

Thanks for link to auxilliary folder. David Carlyle is always right! He's a Latex core author and co-writer of the Latex book. :) I notice other developers have had issues: http://joonro.github.io/blog/posts/org-mode-outputdir-minted-latex-export/

FWIW, if I copy the .pyg file from auxil to src then recompile, it works.

HTH... :)

[PHPirates]

Yeah this is not a parent-child relationship, in fact the support for auxiliary directories is a feature of the compiler, so if using that and minted you will run into this problem even if you're not using an IDE at all but just running from the command line, but as I said this point is moot if minted does support using auxiliary directories.

Can you give example input as well, i.e. a MWE LaTeX source file? Then I can reproduce the problem at least.

[mike-a]

I must attend meetings so will try to provide an MWE later today.

[mike-a]

To help me work out a solution, do you have Texify settings for code formatting you can share from the university?

[PHPirates]

I don't understand your question

[mike-a]

Do you have a Texify example using Minted for code output?

[mike-a]

Okay, question resolved by setting Latex minted.sty path, for example \usepackage[outputdir=../auxil]{minted}.

Minted.sty relies on Python Pygments package, and it's intermediate-stage auxilliary output file during compile. The process: load Latex packages, begin compiling, compile code fragments with Minted package into an intermediate compile file .pyg<...>, collect the file during PDF output, complete PDF output processing. If the intermediate .pyg<...> is not in the expected folder a PDF output exception will occur.

Compiling code with Latex minted.sty package conforms to a normal folder structure. Default TeXiFy plugin settings does not--- it conforms to IntelliJ IDEA Ultimate default structures, which it is inevitably bound to comply with but can be altered in IDEA settings. Accordingly, when TeXiFy IDEA plugin compiles it seeks a .pyg<...> file in the wrong place. By default, here is the compiled structure for the simple MWE below...

Using Latex MWE...

\documentclass[11pt]{article}
% Packages
\usepackage{minted}
% Document
\begin{document}
    \begin{minted}{php}
    <?php
        $x = 1;
        if($x=1){
            echo "x=1";
        } else {
            echo "x=" . $x;
        }
    ?>
    \end{minted}
\end{document}
}

It produces exception...

Error: cannot read infile: [Errno 2] No such file or directory: 'minted-mwe.pyg' Could Not Find P:\Writing-and-WritingSoftware\DevelopmentBooklets\VanElectrical\TexifyMintedTest\src_minted-minted-mwe\097AF5BD36CFF0D87D9991A6653D1FBAC2C2A1FBB8430C5273284E8D3B9D57CD.pygtex

That is correct. The .pyg<...> file should NOT be searched for under \src folder, it is in \auxil folder.

By changing the output folder with the correct file path when loading minted.sty, the compile process will seek the .pyg<...> file in the correct place...

For the avoidance of doubt, I have not experienced this problem in Latex IDEs like TexStudio over the last 10 years. One can understand how it occurs in modern/framework approaches to development that rely on rigid file hierarchies.

Although wasting significant time (to me) on this "default configuration" issue I am so far impressed by TeXiFy plugin within an IntelliJ IDEA environmnet. If Latex writers become aware of it I recognise that products like TeXstudio may have had their day.

Thanks for assistance!

HTH...

[PHPirates]

Thanks for checking this works. I'm still not completely satisfied with it, because now the source code will depend on the name of the auxiliary directory you give to the compiler, which here is TeXiFy-specific default, thus not separating IDE and source code completely. But I don't have a better solution other than not using the auxil directory at all, so I'll just put that in the wiki:
https://github.com/Hannah-Sten/TeXiFy-IDEA/wiki/Auxil-directory
(Please edit if you want)

[PHPirates]

From a TeXiFy perspective, what we could do is write an inspection which warns you when you use an auxil directory but forget to specify the outputdir option to minted - but not super important as the error message is quite clear.