[OS X TeX] iOS apps

Herbert Schulz herbs at wideopenwest.com
Tue Sep 4 15:18:57 CEST 2012

On Sep 4, 2012, at 7:58 AM, Scot Mcphee <scot.mcphee at gmail.com> wrote:

> On Tuesday, 4 September 2012 at 20:43 , Alain Schremmer wrote:
>> On Sep 4, 2012, at 5:41 AM, Scot Mcphee wrote:
>>> It also will parse \include to show you all the files that are
>>> included from the current one. So even if the bit of the PDF you
>>> click on is in an included file it will jump to that file.
>> So does TeXShop.
> Yes but you have to specifically select "Sync" from the menu.



> I don't really like the multi-document windowing model of TeXShop that much, it's sometimes too easy to lose windows in the background if you've got a lot of files open. Also if you do that and open a file with only a Latex fragment in it, then you have to get back to the original, top level file (in some background window that you may have to now locate) to press "Typeset" and see your changes. Because Texpad sees the set of files as all-one-document (if, of course, you opened it from the top level document), you can 'sync' to a subsidiary file, fix the issue and press "Typeset" and it re-typesets the whole thing. Additionally on the left you've got little navigator / file hierarchy thing that shows you the files included from the top level one, and you can click around that too.

Cmd-Click in the preview (pdf) and the correct source file opens for editing.

Put the line

% !TEX root = path/to/root.tex

(path/to/root.tex is the absolute or relative path to the root file) at the top of the included/input file and then Typesetting will typeset the root file. Not only that, Cmd-Click in the include/input file will go to the correct location in the preview window.

> The editor is not as powerful though. It was worth the twenty buck spend though to have a good look at it. I'm still considering what exactly I will do for an editor ... bear in mind my main writing tool is still MMD format in Scrivener.
> Scot.

Does it have command completion? What about creating or using specialized engines for typesetting (latex [via dvi], pdflatex, xelatex, lualatex, how about the latexmk engines that take care of all the necessary indexing/bibliography/cross-referencing runs)?

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)

More information about the macostex-archives mailing list