wish-list: automatically run bibtex

[texworks]

wish-list: automatically run bibtex

[GoogleCodeExporter]

Original comment by st.loeffler on 22 Aug 2009 at 3:29

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Using latexmk as engine allows you to do this.
Simply define a new typesetting tool with the program "latexmk" and the 
following
list of arguments:
-e
$pdflatex=q/pdflatex -synctex=1 %O %S/
-pdf
$fullname

Note that:
* you need to have latexmk installed (MiKTeX and TeXlive both have them 
packaged)
* latexmk requires Perl. If this is not handled by your TeX package manager 
(i.e. if
you can't run latexmk after it was installed), head over to 
http://www.perl.org/ to
get it.
* I have only tested this on Linux so far (though it should work on all other 
systems
as well)
* latexmk not only handles running BibTeX, but also running (pdf)latex often 
enough
to resolve cross references, running makeindex, ...
* latexmk has many more capabilities - read its documentation to lear more

Original comment by st.loeffler on 13 Dec 2009 at 8:27

[GoogleCodeExporter]

Adding a shortcut to the different typesetting engines would be nice:

e.g. CTRL+T -> pdflatex, CTRL+Shift+T -> BibTeX, etc...

Original comment by david.haberthuer on 4 Feb 2010 at 2:12

[GoogleCodeExporter]

Though a little bit off-topic, the attached patch should make it possible to 
assign
custom shortcuts to each typesetting engine using a shortcuts.ini file (see
TipsAndTricks on the wiki). The action names are of the form typesetEngine-1 
(where 1
should be replaced by the one-based index of the engine).

Notes:
 * This is not ideal, as rearranging engines in the preferences dialog also changes
key bindings. A name-based approach may be better (though it would suffer from a
similar problem when engines are renamed), but it would require extensive 
checking
and cleaning of engine names to make them suitable for inclusion in ini files.
 * There are no default shortcuts defined. This could easily be done (e.g. defining
shortcuts of the form Ctrl+1 to Ctrl+9), but I felt that it would clutter the 
UI, and
many of them probably won't be used by the majority of users
 * This does not complete fulfills David's request, in that this only provides
shortcuts for changing the engine. After this, the document still has to be 
typeset
(e.g. by using Ctrl+T). So the typical use-case would be Ctrl+1,Ctrl+T or
Ctrl+Shift+T, Ctrl+T (assuming according shortcut definitions)

Original comment by st.loeffler on 4 Feb 2010 at 6:07

Attachments:

• issue-24_shortcuts-for-engines.diff

[GoogleCodeExporter]

I confirm that latexmk solution works for me. Please add it as a default preset 
to
TeXWorks!

Original comment by yury.v.zaytsev on 23 Mar 2010 at 12:45

[GoogleCodeExporter]

Although the solutions above certainly fix the problem, my understanding is 
that this isn't sufficient to jive with the mission statement of TexWorks, 
"lowering the entry barrier to the TeX world".  It should be standard that 
TexWorks automatically runs BibTeX and LaTeX as many times as necessary to 
ensure that all the references are good (i.e., do not appear as "??" unless 
there is an error on the user's part).

Also, I'd like to emphasize that this problem of needing to run LaTeX multiple 
times exists even for normal equation references, not just BibTeX citations.

Original comment by [email protected] on 21 Sep 2010 at 4:00

[GoogleCodeExporter]

What are you talking about? latexmk is a great tool to do exactly this kind of 
job. Why re-invent the wheel and re-implement code from latexmk inside TexWorks?

Original comment by yury.v.zaytsev on 22 Sep 2010 at 4:48

[GoogleCodeExporter]

I would like to note that I'm trying to get latexmk to work through TeXworks on 
Win7 now, and so far it doesn't. When I run the typesetting program as written 
in http://code.google.com/p/texworks/wiki/AdvancedTypesettingTools, I get the 
same error message each time "latexmk.exe: The Perl interpreter could not be 
found"
There is no problem in running latexmk from cmd.exe, and perl works fine too. I 
have already added c:\strawberry as one of the bin-paths. 

Any suggestions?

Original comment by [email protected] on 17 Dec 2010 at 9:15

[GoogleCodeExporter]

"The Perl interpreter could not be found";same problem here...windows7

Original comment by [email protected] on 21 Feb 2011 at 7:51

[GoogleCodeExporter]

I also got the "The Perl interpreter could not be found" error. I had installed 
strawberry perl while teXworks was running and continuously got this error 
until I closed TexWorks and restarted it. It works since then.

I just looked how I did this on my old pc and found out that I used texify 
there to run pdfLaTeX, MakeIndex and BibTEX in one go.
These are the options:

texify.exe
--pdf
--tex-option=$synctexoption
$fullname

I have not tried these this time as latexmk works nicely now. But this might be 
an easier solution for those who do not want to install perl. But if I remember 
correctly, it does not take care of compiling several times, so I think you 
need to compile several times manually if needed.

Original comment by [email protected] on 15 Jan 2014 at 2:05