> Uwe Brauer <o...@mat.ucm.es> writes: > I admit I don't understand the above. Can you please assemble a minimal > file (structure) exhibiting the problem? And also telling us how > exactly you ran latexmk? I've never used latexmk so I'm clueless about > what it does and doesn't.
Sorry, in a nutshell this is all about the variable *TeX-output-dir*
,----
| TeX-output-dir is a variable defined in ‘tex.el’.
|
| Its value is "build"
| Original value was nil
|
| The path of the directory where output files should be placed.
|
| A relative path is interpreted as being relative to the master
| file in ‘TeX-master’. The path cannot contain a directory that
| starts with ’.’. If this variable is nil, the output directory
| is assumed to be the same as the directory of ‘TeX-master’.
`----
This functionality was provided by Al Haji-Ali
Here is how that works.
1. Suppose I have all my tex documents in a directory called
publications, in particular
- publications/section1.tex
- publications/section2.tex
- etc
2. When I compile say section1.tex, all files that are generated
during compilation, log, aux, pdf etc are saved in
publications/build
3. That functionality leaves the directory publications clutter free
4. And important point is that after compilation TeX-view «finds»
the corresponding pdf/dvi file in the TeX-output-dir.
That being said, let us turn now to LaTeXMk.
1. This new function seems to ignore, TeX-output-dir and therefore
the directory publications is cluttered with the files generated
by the compilation process.
2. Worse however is that TeX-view now does not find the generated
pdf/dvi, because it looks in the TeX-output-dir
Did I explain the problem now better?
Uwe
--
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the EU and NATO membership of Ukraine.
smime.p7s
Description: S/MIME cryptographic signature
