I recently upgraded Scrivener to version 3.3.1.
Thanks to the entire L&L team that put this update/upgrade together.
Since the upgrade, Scrivener stopped automatically opening my compiled .tex file within TeXShop, my typesetting application.
Well over three years ago I spent (an unmentionable amount of) time looking for a way to automate my work flow in a feeble, but burgeoning, effort to connect my Scrivener .tex file output to TeXShop, my typesetting application.
If memory (a bit vague at this point) serves me, someone on L&L may have pointed me in the right direction toward the
Compile screen. From there, I could select the
Open compiled document in: and then select the appropriate drop-down item for my particular typesetting app.
Well, today, over three years later, after the update to version 3.3.1, Scrivener stopped automatically opening my compiled .tex file within my typesetting application, TeXShop.
So, after an equivalent amount of an (unstated) embarrassing amount time, searching L&L, SE, and finally the internet, I found an obscure reference to Gwen Hernandez’s post on
Compiling a DOCX in Scrivener 3.
Gwen includes an almost off-the-cuff comment that happens to mention how:
"If you don’t want the file to open automatically after compiling, deselect the option to “Open compiled output in."
After having a kind of Scrivener Groundhog Day … I thought I’d post here the above entry to serve as a possible post for, if/when (in another three years or so) I upgrade my Scrivener software (and AI is still not ready for prime time) and my link between Scrivener and TeXShop breaks.
Hopefully, the above entry will save me from spending an unmentionable amount of time re-connecting the two back together.