[OS X TeX] command-click on the name of a console file
herbs at wideopenwest.com
Thu Nov 15 16:19:08 EST 2012
On Nov 15, 2012, at 3:08 PM, Nicolae Garleanu <garleanu at haas.berkeley.edu> wrote:
> It means that you don't have to close windows all the time -- they disappear as soon as the problem is solved, or simply the compiler is told to skip it. I know how to close an extra window, I just wished I didn't have to. I am also sure it is technically feasible, thus could be part of a future release: when compilation reaches end, close window automatically.
> A bit like my earlier post about being able to double-click in the source to search the pdf and vice-versa, rather than Cmd-click -- in principle feasible, nice to have (for some people, at least) although not a sine-qua-non.
> -----Original Message-----
> From: macosx-tex-bounces at email.esm.psu.edu [mailto:macosx-tex-bounces at email.esm.psu.edu] On Behalf Of Herbert Schulz
> Sent: Thursday, November 15, 2012 1:03 PM
> To: TeX on Mac OS X Mailing List
> Subject: Re: [OS X TeX] command-click on the name of a console file
> On Nov 15, 2012, at 2:47 PM, Nicolae Garleanu <garleanu at haas.berkeley.edu> wrote:
>> Furthermore, why not have an option for the console window to actually close on its own once the user went through all the errors (by typing <enter> or <r>) and the compilation ended? Or, at least, once one recompiles after fixing all the errors, and thus no errors are generated? It's odd that one must continue to have these windows.
>> As a point of comparison, on my Windows machine I run Miktex from WinEdt and use the ``run in the background'' console attribute. I would much prefer to be able to do the same on the Mac.
> Cmd-W when you're done will close the console window. :-)
> Don't quite understand what `run in the background' really means since I don't use Windows. For me, with fairly recent Macs, the compiles go so fast I could care less about background processing; and I'm going through multiple compiles, with a possible run of bibtex/biber in between, for dealing with cross-references, Table of Contents, etc., using the pdflatexmk engine.
> Good Luck,
> Herb Schulz
> (herbs at wideopenwest dot com)
I guess I like having the console window hanging around (by the way, I have the console window always come to the font when I compile---it drops behind the Preview when compilation is complete) since I can then trace everything that has happened (even if it's a line that doesn't break nicely) quickly.
I admit that my work habit is to only be working on and compiling one root source file at a time although I may have other source files open at the same time being used for reference, etc.
(herbs at wideopenwest dot com)
More information about the MacOSX-TeX