![]() Removing the second call to pdflatex does cut compilation time in half, but then any new references show up as (?) in the outputted pdf until I run it again. Bet there's a flag somewhere I can toggle or a command to include to keep them out and just compile the text while writing. ![]() but maybe just as slow as two separate calls to pdflatex would be? Probably also cos I have a a few MB of pdf figures being loaded in. Users/me/scripts/pdflatex-bibtex.sh: line 9: pdflatex: command not foundīut prepending the calls to pdflatex and bibtex in the shell script with /Library/TeX/texbin/ (ie providing the absolute path) gets rid of that and enables my single-run compilation! It is a bit slow (takes around 3s start to finish). Users/me/scripts/pdflatex-bibtex.sh: line 8: pdflatex: command not found Users/me/scripts/pdflatex-bibtex.sh: line 7: bibtex: command not found Trying out your supplied shell script, I get the errors: /Users/me/scripts/pdflatex-bibtex.sh: line 6: pdflatex: command not found Unless error was exceeding maximum runs, or warnings treated as errors. Latexmk: Use the -f option to force complete processing, Ĭollected error summary (may duplicate other messages):īibtex companion_paper: Command for 'bibtex companion_paper' gave return code 32512 ![]() When I config the latexmk tool with -pdflatex -bibtex -synctex=1 -silent $fullname, it outputs Latexmk: Run number 1 of rule 'bibtex companion_paper'įor rule 'bibtex companion_paper', running '&run_bibtex( )'. So before, my "Console output" window would pop up for a split second and then do nothing. Mistakenly thought that was from a previous attempt to get this "one-click-compilation" thing to work. That was from a previous attempt to get GraphViz to work for a diagram. Or if you are working on a script you prefer, post it here and I'll tell you what I think may or may not be causing it not to work.Īh whoops! No I do not. Save that as pdflatex-bibtex.sh, make it executable chmod a+x pdflatex-bibtex.sh call it like you are, but with $fullname as the only argument in TeXworks. (Remove the second repeated pdflatex command if that's too slow.) Pdflatex -synctex=1 -interaction=batchmode "$basename" With that as the only argument, you could try: Most likely, you don't want other arguments to it besides $fullname, but put the rest in the script. If that doesn't work, then you should be able to get it to work with a shell script. You didn't say how you failed with latexmk, i.e., what happened when you tried, but with an up to date latexmk, I would try with these arguments: Then I tried making a new tool with latexmk, copying over various configurations from decade-old stackoverflow threads( e.g., with variations, like including a -bibtex in there), but that also failed.Īny ideas how I can specify my tool config to save me from having to run multiple commands? Thanks for any help!ĭo you really need -shell-escape? What for? And I'm almost positive you don't need -enable-write18. I tried writing an executable *.sh script and then passing over $fullname and basename with -shell-escape and -enable_write18 enabled, but that didn't work ( e.g., I know I don't have things in the right order, was trying to just get it to do something other than throw an error message). So I tried today to figure out how to get all this down to one command, without much luck. ![]() I also like to obsessively recompile my document often to make sure changes have propagated. What I don't like, though, is having to cmd+T BibTeX, go in the drop down menu, switch to pdfLaTeX, and then cmt+T that twice. in LaTeX in macOS, and also like Zotero w/ chrome plugin & Better BibTeX extension for seamlessly integrating and updating my. I like using the TeXworks GUI for writing papers etc. Hi all - happy long-time user of LaTeX, by which I mean I snag templates online and fiddle with them and know very little about how anything works under the hood.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |