[OS X TeX] command-click on the name of a console file
garleanu at haas.berkeley.edu
Thu Nov 15 21:47:52 CET 2012
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.
From: macosx-tex-bounces at email.esm.psu.edu [mailto:macosx-tex-bounces at email.esm.psu.edu] On Behalf Of Themis Matsoukas
Sent: Thursday, November 15, 2012 2:35 AM
To: TeX on Mac OS X Mailing List
Subject: Re: [OS X TeX] command-click on the name of a console file
On Nov 14, 2012, at 4:06 PM, Herbert Schulz <herbs at wideopenwest.com> wrote:
> The Console window is like a Terminal window and you can see the input and output of the various things that go one when you compile a file.
...but with a difference: for each latex source, TS generates a new console (unlike terminal, which gives a continuous history of previous actions). Moreover, each new console window hides *behind* the previous one (at least when you've checked "show console only when error occurs". This has confused several times: I usually watch the scrolling of output in console window on the background as an indication of whether typesetting is over, but when the active console is hidden behind an inactive console window, it looks as if nothing is happening. Since some errors do not cause the console to come forward, this can lead to frustration when such errors occur. I would suggest then that TS show the active console always as the top console window. Is there really a need for multiple console windows?
More information about the macostex-archives