--- In SubEthaEdit@yahoogroups.com
, "jug.florian" <florian.jug@...> wrote:
> In total I have 3 Questions:
> (2) Who knows a good way to go forwards from SubEtha to PDF
> (3) Does anybody know any further tricks you think are helpful when TeXing with SubEtha?
> PS: the reason why I do not use the typeset button that comes with SubEtha is mainly that I get ZERO feedback in case typesetting causes errors.
This is not the whole story. The LaTeX mode is customizable, so you can change how the document is compiled. This lets you pipe the output of the typesetter (which you can choose) to another program for viewing the output. There's a description of how to show the output from latexmk in a SEE window at <http://appliedabstraction.blogspot.com/search/label/SEEing%20LaTeX
That said, I make no recommendation that you actually should take that approach. Personally, I've come around to using latexmk -pvc in a Terminal window to continuously compile and update the preview, much like you're doing.
My main use of LaTeX is also scientific writing. Scientific writing is a significant task, so my main trick is to treat it like any other significant *programmatic* task -- keep it under version control, use a makefile for the entire project, and automate what I can using shell scripts. With this approach, I'll always have Terminal around anyway, so keeping latexmk -pvc going is pretty natural.
You can save key scripts with a .command ending, which lets you double-click them in the Finder to run them. One nice use of this is to launch latexmk. Another is to open up the currently relevant documents for the paper as tabs in SEE, or another application, depending on the type of document.
Hope that helps.