bibtexmactexpdftex
Recently, I switched to MacTex, I somehow get used to run the following sequence on a Windows command terminal:
However, now when I launch a terminal on Mac(Yosemite), running latex *.tex
would directly generate the final pdf without the intermediate steps, seems to me "latex" is hardlinked to a combination of commands? Is there a way to follow the same steps as I used to ?
TeXShop doesn't do the BibTeX run by itself.
Here's how the window should appear
Choose BibTeX from the dropdown menu
Click on the "Typeset" button (or hit Command-T)
Then return to LaTeX and compile again.
You can run BibTeX when you need it, you don't need it to be run at each LaTeX run; only when references are added or removed.
First off just want to thank you all for your help -- greatly appreciated!! I reached out to Herb Schulz who is a prominent "aider and abettor" on MacTex at tug.org. He thought it likely that the Applescript Bibliography macro had been broken by the upgrade to Yosemite. He suggested that I use the pdflatexmk engine in TeXShop to take care of all the compiling steps automatically, which I am now doing.
I can do no better than to quote Herb's own words as follows:
"First, in the Source window toolbar there should be a popup menu listing all the available engines. In all recent versions of TeXShop you should see a pdflatexmk engine. If you are compiling using pdflatex you're set. If you don't see the pdflatexmk engine on that list (that would happen if you have been using TeXShop for a long time) or you need the latexmk engine you'll have to move those engines into place. First quit TeXShop. Then move all the files with extension .engine from ~/Library/TeXShop/Engines/Inactive/Latexmk two levels up, to ~/Library/TeXShop/Engines. (Note: ~/Library is the Library folder in your HOME folder. Under OS X 10.7 and later it is invisible by default. To open that folder Click on the Go Menu in Finder and press the Option key and a new menu item for Library will appear; click on that item.) Open TeXShop and see that the additional engines (including the pdflatexmk and latexmk) are now shown in the popup menu in the Source window toolbar.
Once the pdflatexmk/latexmk engine is shown you activate it for a source file by placing the line
% !TEX TS-program = pdflatexmk
at the top of the file (or replace pdflatexmk above with latexmk if you compile with latex rather than pdflatex). From then on simply clicking on Typeset->Typeset (Cmd-T) should take you through all the steps necessary to compile your document automatically."
A relevant web page is
This strategy will also work with Biblatex/biber and has the advantage that the "BibTex Engine" settings in the "Engine" tab of the TexShop Preferences do not have to be changed from bibtex to biber -- it all happens automatically.
Best Answer
The
latexprogram is actuallypdflatexrunning indvimode. According tolatex --help, the output format can be set withSo you can try to force the
dvioutput by compiling with:What you have though actually does the same, if
latexis giving you apdffile, and if that's what you want, you can just runlatex,bibtex,latex,latexand it will give you the right pdf file, so unless you specifically want thedvifile there's no any reason to produce it.