Automatically Move Auxiliary Files to Subdir with Auto-Compiling Vimtex











up vote
1
down vote

favorite












I've seen numerous ways to move auxiliary files to a given directory via latexmk, or pdflatex (ex. latexmk -auxdir=/tmp <file>). But I am using vimtex with auto-compiling, so that whenever I save my tex file, it is automatically compiled and my pdf viewer (just using evince) is updated too.



What I'd like is for vimtex to create a subdir called aux in whichever directory my current texfile is, and put any of these auxiliary files in there at each compilation -- keeping just my .tex and .pdf file in the working dir. I feel like I should be able to specify this in .latexmkrc but haven't read any mention of specifying such settings there.






pdftex auxiliary-files latexmk vim evince







share|improve this question
















bumped to the homepage by Community♦ 25 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • There is a vim tag. I've added it.
    – Henri Menke
    Aug 22 '17 at 23:39










  • Note that /aux would be a directory in the root of the file system and not the current directory. ./aux or aux is what you mean, I take it.
    – cfr
    Jul 29 at 3:51















up vote
1
down vote

favorite












I've seen numerous ways to move auxiliary files to a given directory via latexmk, or pdflatex (ex. latexmk -auxdir=/tmp <file>). But I am using vimtex with auto-compiling, so that whenever I save my tex file, it is automatically compiled and my pdf viewer (just using evince) is updated too.



What I'd like is for vimtex to create a subdir called aux in whichever directory my current texfile is, and put any of these auxiliary files in there at each compilation -- keeping just my .tex and .pdf file in the working dir. I feel like I should be able to specify this in .latexmkrc but haven't read any mention of specifying such settings there.






pdftex auxiliary-files latexmk vim evince







share|improve this question
















bumped to the homepage by Community♦ 25 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • There is a vim tag. I've added it.
    – Henri Menke
    Aug 22 '17 at 23:39










  • Note that /aux would be a directory in the root of the file system and not the current directory. ./aux or aux is what you mean, I take it.
    – cfr
    Jul 29 at 3:51













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I've seen numerous ways to move auxiliary files to a given directory via latexmk, or pdflatex (ex. latexmk -auxdir=/tmp <file>). But I am using vimtex with auto-compiling, so that whenever I save my tex file, it is automatically compiled and my pdf viewer (just using evince) is updated too.



What I'd like is for vimtex to create a subdir called aux in whichever directory my current texfile is, and put any of these auxiliary files in there at each compilation -- keeping just my .tex and .pdf file in the working dir. I feel like I should be able to specify this in .latexmkrc but haven't read any mention of specifying such settings there.






pdftex auxiliary-files latexmk vim evince







share|improve this question















I've seen numerous ways to move auxiliary files to a given directory via latexmk, or pdflatex (ex. latexmk -auxdir=/tmp <file>). But I am using vimtex with auto-compiling, so that whenever I save my tex file, it is automatically compiled and my pdf viewer (just using evince) is updated too.



What I'd like is for vimtex to create a subdir called aux in whichever directory my current texfile is, and put any of these auxiliary files in there at each compilation -- keeping just my .tex and .pdf file in the working dir. I feel like I should be able to specify this in .latexmkrc but haven't read any mention of specifying such settings there.






pdftex auxiliary-files latexmk vim evince




pdftex auxiliary-files latexmk vim evince






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 29 at 3:51









cfr

155k7180377




155k7180377










asked Aug 22 '17 at 21:05









RACKGNOME

1061




1061





bumped to the homepage by Community♦ 25 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community♦ 25 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • There is a vim tag. I've added it.
    – Henri Menke
    Aug 22 '17 at 23:39










  • Note that /aux would be a directory in the root of the file system and not the current directory. ./aux or aux is what you mean, I take it.
    – cfr
    Jul 29 at 3:51


















  • There is a vim tag. I've added it.
    – Henri Menke
    Aug 22 '17 at 23:39










  • Note that /aux would be a directory in the root of the file system and not the current directory. ./aux or aux is what you mean, I take it.
    – cfr
    Jul 29 at 3:51
















There is a vim tag. I've added it.
– Henri Menke
Aug 22 '17 at 23:39




There is a vim tag. I've added it.
– Henri Menke
Aug 22 '17 at 23:39












Note that /aux would be a directory in the root of the file system and not the current directory. ./aux or aux is what you mean, I take it.
– cfr
Jul 29 at 3:51




Note that /aux would be a directory in the root of the file system and not the current directory. ./aux or aux is what you mean, I take it.
– cfr
Jul 29 at 3:51










1 Answer
1






active

oldest

votes

















up vote
0
down vote













You can mostly achieve this using vimtex's build_dir setting (see vimtex help :h vimtex_compiler_latexmk and this conversation explaining that "this allows to define an output directory where all generated files are put when compiling".). However, your pdf will also be moved to this directory.






share|improve this answer





















  • Yeah the pdf going to that directory is not ideal. The ideal would be to separate the auxiliary files from the desired, generated pdf file.
    – RACKGNOME
    Jul 30 at 17:22











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f387722%2fautomatically-move-auxiliary-files-to-subdir-with-auto-compiling-vimtex%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













You can mostly achieve this using vimtex's build_dir setting (see vimtex help :h vimtex_compiler_latexmk and this conversation explaining that "this allows to define an output directory where all generated files are put when compiling".). However, your pdf will also be moved to this directory.






share|improve this answer





















  • Yeah the pdf going to that directory is not ideal. The ideal would be to separate the auxiliary files from the desired, generated pdf file.
    – RACKGNOME
    Jul 30 at 17:22















up vote
0
down vote













You can mostly achieve this using vimtex's build_dir setting (see vimtex help :h vimtex_compiler_latexmk and this conversation explaining that "this allows to define an output directory where all generated files are put when compiling".). However, your pdf will also be moved to this directory.






share|improve this answer





















  • Yeah the pdf going to that directory is not ideal. The ideal would be to separate the auxiliary files from the desired, generated pdf file.
    – RACKGNOME
    Jul 30 at 17:22













up vote
0
down vote










up vote
0
down vote









You can mostly achieve this using vimtex's build_dir setting (see vimtex help :h vimtex_compiler_latexmk and this conversation explaining that "this allows to define an output directory where all generated files are put when compiling".). However, your pdf will also be moved to this directory.






share|improve this answer












You can mostly achieve this using vimtex's build_dir setting (see vimtex help :h vimtex_compiler_latexmk and this conversation explaining that "this allows to define an output directory where all generated files are put when compiling".). However, your pdf will also be moved to this directory.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 29 at 2:11









pierre

1




1












  • Yeah the pdf going to that directory is not ideal. The ideal would be to separate the auxiliary files from the desired, generated pdf file.
    – RACKGNOME
    Jul 30 at 17:22


















  • Yeah the pdf going to that directory is not ideal. The ideal would be to separate the auxiliary files from the desired, generated pdf file.
    – RACKGNOME
    Jul 30 at 17:22
















Yeah the pdf going to that directory is not ideal. The ideal would be to separate the auxiliary files from the desired, generated pdf file.
– RACKGNOME
Jul 30 at 17:22




Yeah the pdf going to that directory is not ideal. The ideal would be to separate the auxiliary files from the desired, generated pdf file.
– RACKGNOME
Jul 30 at 17:22


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f387722%2fautomatically-move-auxiliary-files-to-subdir-with-auto-compiling-vimtex%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Contact image not getting when fetch all contact list from iPhone by CNContact

Image
up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
Read more

count number of partitions of a set with n elements into k subsets

Image
up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
Read more

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
Read more