I am using TexMaker and SumatraPDF for a viewer. Everything works fine. I then wanted to change the pdf name when compiling using the following command:

%& -job-name=SLR-Review

This placed on top works and creates a completely new pdf. THe issue however is that, the view now shows an old file in pdfviewer and does not update it continously. Further the file is the old filename and not the new.

Is there any way of accommodating this issue, to make the external pdf viewer show the changed output file?

Or should I simply only use the method %& -job-name=SLR-Review when the document is finished (kind of defeats the purpose of using the method)?

  • I'm not familiar with TeXmaker, but most editors like that have a settings window that specifies the command-line call to the viewer with all kinds of options and possible variables. Usually these variables are variations on the source .tex filename/path or a project's "main file" name/path, so it might not be possible to use \jobname in this command string. – Paul Gessler Apr 28 '15 at 11:47
  • 1
    By the way: Welcome to TeX.SX! – Paul Gessler Apr 28 '15 at 11:47
  • To which end are you renaming the PDF? – Keks Dose Apr 28 '15 at 12:00
  • @PaulGessler Thx! I have tried introducing it in the build options, but could not get it to work. So you might be right in jobname not existing. But I would not rule it out with my limited knowledge on TexMaker :) – JTIM Apr 28 '15 at 12:03
  • 1
    In my editor (winedt) it would be imho possible to record --jobname and use this to open the file. I have been thinking a bit about this but it isn't easy to design a sensible workflow, even more as I'm often compiling more than one document. So I avoid --jobname if possible and use wrapper files if I want different outputs from one document. – Ulrike Fischer Apr 28 '15 at 13:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.