[Tex/LaTex] Not having pdfLaTeX+MakeIndex+BibTeX in TexWorks

compilingtexworks

Because of some problems (like getting stuck while compiling) I deleted my miktex and reinstalled the last version from its website (basic-miktex-20.11.x64.exe). Then I downloaded TextWorks from here(.zip file). It seems that this TexWorks is a portable version. Now when I start TexWork I only have separate processing tools of: pdfLatex, BibTex, XeLatex,… . But I need something like pdfLaTeX+MakeIndex+BibTeX That I had before. When I compile my file with only pdfLatex, my citations get like this [?] and not known. How can I enable these combined processing tools? (I don't have them in Edit/Preferences/typesetting/processing tools list too).

Best Answer

to edit the option pdfLaTeX+MakeIndex+BibTeX you can click Edit-> settings. Then the settings look like this:

Add a new programm(cross at the bottom right; Command is texify.exe; Arguments are '--pdf', --synctex=1, --clean and $fullname; also tick the show pdf afterwards, if you like

Related Solutions

[Tex/LaTex] TeXworks with XeLaTeX + MakeIndex + BiBTeX + shell escape

latexmk has a switch called -shell-escape that should do what you want. It takes care of makeindex and bibtex anyway.

so this should work

Name: xelatexmk
Program: latexmk

Arguments: -xelatex
           -shell-escape
           -e
           $synctexoption %O %S/
           $fullname

[Tex/LaTex] Problems compiling arXiv LaTeX source files

Try adding the .tex extension back on to the file. I'm not sure why arXiv would remove it, but many editors will assume that it's there when running compile sequences.

To see what I mean, compare the compilation for pdfLaTeX and BibTeX:

$ pdflatex myfile.tex
$ bibtex myfile

Note that bibtex doesn't need the file extension since it also looks at the files generated by the LaTeX run. Editors like TeXworks (and others, no doubt) will run these sequences for you automatically, but this requires that it knows where the extension is so that it can remove it. When there is no extension to remove, ambiguities will arise:

$ pdflatex myfile
$ bibtex myfile

It's likely that one of these programs picked up on the 'wrong' myfile, causing the error that you saw. (For example, take a look inside the aux file; running pdflatex directly on this file would certainly throw an error.)

Best Answer

Related Solutions

[Tex/LaTex] TeXworks with XeLaTeX + MakeIndex + BiBTeX + shell escape

[Tex/LaTex] Problems compiling arXiv LaTeX source files

Related Question