`latexmk` with cleanup and `-pvc`latexmk -pvc option breaks when compiling beamer classlatexmk -pvc doesn't...

Unexpected email from Yorkshire Bank

Meaning of Bloch representation

Noun clause (singular all the time?)

Please, smoke with good manners

Will a top journal at least read my introduction?

Was there a Viking Exchange as well as a Columbian one?

Examples of subgroups where it's nontrivial to show closure under multiplication?

Repelling Blast: Must targets always be pushed back?

How can I practically buy stocks?

What do the phrase "Reeyan's seacrest" and the word "fraggle" mean in a sketch?

How do I reattach a shelf to the wall when it ripped out of the wall?

Pulling the rope with one hand is as heavy as with two hands?

What is the difference between `command a[bc]d` and `command `a{b,c}d`

A ​Note ​on ​N!

Fizzy, soft, pop and still drinks

What is the strongest case that can be made in favour of the UK regaining some control over fishing policy after Brexit?

What does KSP mean?

What route did the Hindenburg take when traveling from Germany to the U.S.?

How to make a pipeline wait for end-of-file or stop after an error?

What's the polite way to say "I need to urinate"?

Adjust deraillers after changing chain?

Phrase for the opposite of "foolproof"

Was there a shared-world project before "Thieves World"?

Exchange,swap or switch



`latexmk` with cleanup and `-pvc`


latexmk -pvc option breaks when compiling beamer classlatexmk -pvc doesn't recompile if included files changeTeXworks and pvc parameter of latexmkAUCTeX -output-directory + copy *.pdf to working directoryUsing LaTeXmk with mylatexformatlatexmk cleanupMake utility deletes PDF when Ctrl-C'ing out of continuous previewHow can I run a latexmk cleanup for subdirectory?Latexmk pvc inactivity timeoutErrors with latexmk -c (cleanup) option













0















I am unable to put the -pvc (preview continuously) and -c (clean up) options together for latexmk.



latexmk -pdf -pvc -c file.tex


My observation: After giving -c option, the file gets compiled, (regeneratable) files are deleted and I am back to the command prompt.



Is it possible to achieve this?



-- Mike










share|improve this question














bumped to the homepage by Community 10 mins ago


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
















  • I'm not quite understanding. -pvc implies continuous compilation, which needs the auxiliary files, which means they can't be deleted. Or are you wanting the auxiliary files to be regenerated whenever you make a change? Why not just leave them around?

    – Teepeemm
    Sep 29 '18 at 18:42











  • @Teepeemm This is precisely I want! I would like to regenerate all auxiliary files every time src file.tex is updated. and get deleted upon successful compilation. I need this as I have some restrictions on bandwidth and filesystem in terms of number of files. (Weird, huh?)

    – Mike V.D.C.
    Sep 30 '18 at 6:36
















0















I am unable to put the -pvc (preview continuously) and -c (clean up) options together for latexmk.



latexmk -pdf -pvc -c file.tex


My observation: After giving -c option, the file gets compiled, (regeneratable) files are deleted and I am back to the command prompt.



Is it possible to achieve this?



-- Mike










share|improve this question














bumped to the homepage by Community 10 mins ago


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
















  • I'm not quite understanding. -pvc implies continuous compilation, which needs the auxiliary files, which means they can't be deleted. Or are you wanting the auxiliary files to be regenerated whenever you make a change? Why not just leave them around?

    – Teepeemm
    Sep 29 '18 at 18:42











  • @Teepeemm This is precisely I want! I would like to regenerate all auxiliary files every time src file.tex is updated. and get deleted upon successful compilation. I need this as I have some restrictions on bandwidth and filesystem in terms of number of files. (Weird, huh?)

    – Mike V.D.C.
    Sep 30 '18 at 6:36














0












0








0








I am unable to put the -pvc (preview continuously) and -c (clean up) options together for latexmk.



latexmk -pdf -pvc -c file.tex


My observation: After giving -c option, the file gets compiled, (regeneratable) files are deleted and I am back to the command prompt.



Is it possible to achieve this?



-- Mike










share|improve this question














I am unable to put the -pvc (preview continuously) and -c (clean up) options together for latexmk.



latexmk -pdf -pvc -c file.tex


My observation: After giving -c option, the file gets compiled, (regeneratable) files are deleted and I am back to the command prompt.



Is it possible to achieve this?



-- Mike







latexmk






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 29 '18 at 17:43









Mike V.D.C.Mike V.D.C.

1407




1407





bumped to the homepage by Community 10 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 10 mins ago


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















  • I'm not quite understanding. -pvc implies continuous compilation, which needs the auxiliary files, which means they can't be deleted. Or are you wanting the auxiliary files to be regenerated whenever you make a change? Why not just leave them around?

    – Teepeemm
    Sep 29 '18 at 18:42











  • @Teepeemm This is precisely I want! I would like to regenerate all auxiliary files every time src file.tex is updated. and get deleted upon successful compilation. I need this as I have some restrictions on bandwidth and filesystem in terms of number of files. (Weird, huh?)

    – Mike V.D.C.
    Sep 30 '18 at 6:36



















  • I'm not quite understanding. -pvc implies continuous compilation, which needs the auxiliary files, which means they can't be deleted. Or are you wanting the auxiliary files to be regenerated whenever you make a change? Why not just leave them around?

    – Teepeemm
    Sep 29 '18 at 18:42











  • @Teepeemm This is precisely I want! I would like to regenerate all auxiliary files every time src file.tex is updated. and get deleted upon successful compilation. I need this as I have some restrictions on bandwidth and filesystem in terms of number of files. (Weird, huh?)

    – Mike V.D.C.
    Sep 30 '18 at 6:36

















I'm not quite understanding. -pvc implies continuous compilation, which needs the auxiliary files, which means they can't be deleted. Or are you wanting the auxiliary files to be regenerated whenever you make a change? Why not just leave them around?

– Teepeemm
Sep 29 '18 at 18:42





I'm not quite understanding. -pvc implies continuous compilation, which needs the auxiliary files, which means they can't be deleted. Or are you wanting the auxiliary files to be regenerated whenever you make a change? Why not just leave them around?

– Teepeemm
Sep 29 '18 at 18:42













@Teepeemm This is precisely I want! I would like to regenerate all auxiliary files every time src file.tex is updated. and get deleted upon successful compilation. I need this as I have some restrictions on bandwidth and filesystem in terms of number of files. (Weird, huh?)

– Mike V.D.C.
Sep 30 '18 at 6:36





@Teepeemm This is precisely I want! I would like to regenerate all auxiliary files every time src file.tex is updated. and get deleted upon successful compilation. I need this as I have some restrictions on bandwidth and filesystem in terms of number of files. (Weird, huh?)

– Mike V.D.C.
Sep 30 '18 at 6:36










1 Answer
1






active

oldest

votes


















0














You can write a small shell script:



f=/tmp/$$.tmp
touch $f
src=foo.tex
src="$1";
echo -e "$src -- $fn";

while true
do
if [ ${src} -nt ${f} ];
then
echo "File modified";
latexmk -c ${src}
sleep 5;
fi;
touch ${f};
sleep 5; # This is essential.
done





share|improve this answer
























  • Welcome to TeX.SX!

    – Bobyandbob
    Sep 29 '18 at 18:26











  • If one has to use bash script, why use latexmk in that case? Just put pdflatex, followed by rm -f commands... I believe this can be achieved with the power of latexmk.

    – Mike V.D.C.
    Sep 29 '18 at 18:36











  • I may be overlooking things, but I'm not seeing how you accomplish the -pvc portion.

    – Teepeemm
    Sep 29 '18 at 18:40











  • @MikeV.D.C. latexmk can do much more than just a single rub of pdflatex - e.g. it will repeatedly compile the document until all the cross references, tables of contents, indexes, etc, are self-consistent, but only do the minimum number of recompiles to reach that state. (That's why it seems pointless to me to delete all the auxiliary files every time you run latexmk - it is just making latexmk work harder for no obvious reason).

    – alephzero
    Sep 29 '18 at 21:33













  • @Teepeemm, I suspect that @user5325 is using some *nix system (e.g. ubuntu). So the default previewer (e.g. evince on ubuntu), once opened, automatically update the document on every change. Thus achieving -pvc.

    – Mike V.D.C.
    Sep 30 '18 at 6:42












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',
autoActivateHeartbeat: false,
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%2f453108%2flatexmk-with-cleanup-and-pvc%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









0














You can write a small shell script:



f=/tmp/$$.tmp
touch $f
src=foo.tex
src="$1";
echo -e "$src -- $fn";

while true
do
if [ ${src} -nt ${f} ];
then
echo "File modified";
latexmk -c ${src}
sleep 5;
fi;
touch ${f};
sleep 5; # This is essential.
done





share|improve this answer
























  • Welcome to TeX.SX!

    – Bobyandbob
    Sep 29 '18 at 18:26











  • If one has to use bash script, why use latexmk in that case? Just put pdflatex, followed by rm -f commands... I believe this can be achieved with the power of latexmk.

    – Mike V.D.C.
    Sep 29 '18 at 18:36











  • I may be overlooking things, but I'm not seeing how you accomplish the -pvc portion.

    – Teepeemm
    Sep 29 '18 at 18:40











  • @MikeV.D.C. latexmk can do much more than just a single rub of pdflatex - e.g. it will repeatedly compile the document until all the cross references, tables of contents, indexes, etc, are self-consistent, but only do the minimum number of recompiles to reach that state. (That's why it seems pointless to me to delete all the auxiliary files every time you run latexmk - it is just making latexmk work harder for no obvious reason).

    – alephzero
    Sep 29 '18 at 21:33













  • @Teepeemm, I suspect that @user5325 is using some *nix system (e.g. ubuntu). So the default previewer (e.g. evince on ubuntu), once opened, automatically update the document on every change. Thus achieving -pvc.

    – Mike V.D.C.
    Sep 30 '18 at 6:42
















0














You can write a small shell script:



f=/tmp/$$.tmp
touch $f
src=foo.tex
src="$1";
echo -e "$src -- $fn";

while true
do
if [ ${src} -nt ${f} ];
then
echo "File modified";
latexmk -c ${src}
sleep 5;
fi;
touch ${f};
sleep 5; # This is essential.
done





share|improve this answer
























  • Welcome to TeX.SX!

    – Bobyandbob
    Sep 29 '18 at 18:26











  • If one has to use bash script, why use latexmk in that case? Just put pdflatex, followed by rm -f commands... I believe this can be achieved with the power of latexmk.

    – Mike V.D.C.
    Sep 29 '18 at 18:36











  • I may be overlooking things, but I'm not seeing how you accomplish the -pvc portion.

    – Teepeemm
    Sep 29 '18 at 18:40











  • @MikeV.D.C. latexmk can do much more than just a single rub of pdflatex - e.g. it will repeatedly compile the document until all the cross references, tables of contents, indexes, etc, are self-consistent, but only do the minimum number of recompiles to reach that state. (That's why it seems pointless to me to delete all the auxiliary files every time you run latexmk - it is just making latexmk work harder for no obvious reason).

    – alephzero
    Sep 29 '18 at 21:33













  • @Teepeemm, I suspect that @user5325 is using some *nix system (e.g. ubuntu). So the default previewer (e.g. evince on ubuntu), once opened, automatically update the document on every change. Thus achieving -pvc.

    – Mike V.D.C.
    Sep 30 '18 at 6:42














0












0








0







You can write a small shell script:



f=/tmp/$$.tmp
touch $f
src=foo.tex
src="$1";
echo -e "$src -- $fn";

while true
do
if [ ${src} -nt ${f} ];
then
echo "File modified";
latexmk -c ${src}
sleep 5;
fi;
touch ${f};
sleep 5; # This is essential.
done





share|improve this answer













You can write a small shell script:



f=/tmp/$$.tmp
touch $f
src=foo.tex
src="$1";
echo -e "$src -- $fn";

while true
do
if [ ${src} -nt ${f} ];
then
echo "File modified";
latexmk -c ${src}
sleep 5;
fi;
touch ${f};
sleep 5; # This is essential.
done






share|improve this answer












share|improve this answer



share|improve this answer










answered Sep 29 '18 at 18:09









user5325user5325

213




213













  • Welcome to TeX.SX!

    – Bobyandbob
    Sep 29 '18 at 18:26











  • If one has to use bash script, why use latexmk in that case? Just put pdflatex, followed by rm -f commands... I believe this can be achieved with the power of latexmk.

    – Mike V.D.C.
    Sep 29 '18 at 18:36











  • I may be overlooking things, but I'm not seeing how you accomplish the -pvc portion.

    – Teepeemm
    Sep 29 '18 at 18:40











  • @MikeV.D.C. latexmk can do much more than just a single rub of pdflatex - e.g. it will repeatedly compile the document until all the cross references, tables of contents, indexes, etc, are self-consistent, but only do the minimum number of recompiles to reach that state. (That's why it seems pointless to me to delete all the auxiliary files every time you run latexmk - it is just making latexmk work harder for no obvious reason).

    – alephzero
    Sep 29 '18 at 21:33













  • @Teepeemm, I suspect that @user5325 is using some *nix system (e.g. ubuntu). So the default previewer (e.g. evince on ubuntu), once opened, automatically update the document on every change. Thus achieving -pvc.

    – Mike V.D.C.
    Sep 30 '18 at 6:42



















  • Welcome to TeX.SX!

    – Bobyandbob
    Sep 29 '18 at 18:26











  • If one has to use bash script, why use latexmk in that case? Just put pdflatex, followed by rm -f commands... I believe this can be achieved with the power of latexmk.

    – Mike V.D.C.
    Sep 29 '18 at 18:36











  • I may be overlooking things, but I'm not seeing how you accomplish the -pvc portion.

    – Teepeemm
    Sep 29 '18 at 18:40











  • @MikeV.D.C. latexmk can do much more than just a single rub of pdflatex - e.g. it will repeatedly compile the document until all the cross references, tables of contents, indexes, etc, are self-consistent, but only do the minimum number of recompiles to reach that state. (That's why it seems pointless to me to delete all the auxiliary files every time you run latexmk - it is just making latexmk work harder for no obvious reason).

    – alephzero
    Sep 29 '18 at 21:33













  • @Teepeemm, I suspect that @user5325 is using some *nix system (e.g. ubuntu). So the default previewer (e.g. evince on ubuntu), once opened, automatically update the document on every change. Thus achieving -pvc.

    – Mike V.D.C.
    Sep 30 '18 at 6:42

















Welcome to TeX.SX!

– Bobyandbob
Sep 29 '18 at 18:26





Welcome to TeX.SX!

– Bobyandbob
Sep 29 '18 at 18:26













If one has to use bash script, why use latexmk in that case? Just put pdflatex, followed by rm -f commands... I believe this can be achieved with the power of latexmk.

– Mike V.D.C.
Sep 29 '18 at 18:36





If one has to use bash script, why use latexmk in that case? Just put pdflatex, followed by rm -f commands... I believe this can be achieved with the power of latexmk.

– Mike V.D.C.
Sep 29 '18 at 18:36













I may be overlooking things, but I'm not seeing how you accomplish the -pvc portion.

– Teepeemm
Sep 29 '18 at 18:40





I may be overlooking things, but I'm not seeing how you accomplish the -pvc portion.

– Teepeemm
Sep 29 '18 at 18:40













@MikeV.D.C. latexmk can do much more than just a single rub of pdflatex - e.g. it will repeatedly compile the document until all the cross references, tables of contents, indexes, etc, are self-consistent, but only do the minimum number of recompiles to reach that state. (That's why it seems pointless to me to delete all the auxiliary files every time you run latexmk - it is just making latexmk work harder for no obvious reason).

– alephzero
Sep 29 '18 at 21:33







@MikeV.D.C. latexmk can do much more than just a single rub of pdflatex - e.g. it will repeatedly compile the document until all the cross references, tables of contents, indexes, etc, are self-consistent, but only do the minimum number of recompiles to reach that state. (That's why it seems pointless to me to delete all the auxiliary files every time you run latexmk - it is just making latexmk work harder for no obvious reason).

– alephzero
Sep 29 '18 at 21:33















@Teepeemm, I suspect that @user5325 is using some *nix system (e.g. ubuntu). So the default previewer (e.g. evince on ubuntu), once opened, automatically update the document on every change. Thus achieving -pvc.

– Mike V.D.C.
Sep 30 '18 at 6:42





@Teepeemm, I suspect that @user5325 is using some *nix system (e.g. ubuntu). So the default previewer (e.g. evince on ubuntu), once opened, automatically update the document on every change. Thus achieving -pvc.

– Mike V.D.C.
Sep 30 '18 at 6:42


















draft saved

draft discarded




















































Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f453108%2flatexmk-with-cleanup-and-pvc%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

Can't compile dgruyter and caption packagesLaTeX templates/packages for writing a patent specificationLatex...

Schneeberg (Smreczany) Bibliografia | Menu...

Hans Bellmer Spis treści Życiorys | Upamiętnienie | Przypisy | Bibliografia | Linki zewnętrzne |...