I had TextMate set up to download "Cutting edge" and it just downloaded a new upgrade the other day. Before the download, I had everything working just fine with TeXniscope, but after I installed the upgrade, whenever I compile a LaTeX file in TextMate, it doesn't open TeXniscope. TeXniscope does update the PDF file (or open it if it's not already open) but it doesn't bring that file into focus like it did before. Even if I type Cmd-Opt-Ctrl-O nothing happens. In the typesetting dialog that comes up, there's a button that says "Preferences" and I have the "Show pdf automatically" option enabled, but it still doesn't bring TeXniscope into focus. Any ideas?
Keith
On Oct 22, 2007, at 6:46 AM, Keith Penrod wrote:
I had TextMate set up to download "Cutting edge" and it just downloaded a new upgrade the other day. Before the download, I had everything working just fine with TeXniscope, but after I installed the upgrade, whenever I compile a LaTeX file in TextMate, it doesn't open TeXniscope. TeXniscope does update the PDF file (or open it if it's not already open) but it doesn't bring that file into focus like it did before. Even if I type Cmd-Opt-Ctrl-O nothing happens. In the typesetting dialog that comes up, there's a button that says "Preferences" and I have the "Show pdf automatically" option enabled, but it still doesn't bring TeXniscope into focus. Any ideas?
Keith
Skim is now the supported reader. http://skim-app.sourceforge.net/
See if that works for you.
Jenny
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Le 22 oct. 07 à 15:46, Keith Penrod a écrit :
I had TextMate set up to download "Cutting edge" and it just downloaded a new upgrade the other day. Before the download, I had everything working just fine with TeXniscope, but after I installed the upgrade, whenever I compile a LaTeX file in TextMate, it doesn't open TeXniscope. TeXniscope does update the PDF file (or open it if it's not already open) but it doesn't bring that file into focus like it did before. Even if I type Cmd-Opt-Ctrl-O nothing happens. In the typesetting dialog that comes up, there's a button that says "Preferences" and I have the "Show pdf automatically" option enabled, but it still doesn't bring TeXniscope into focus. Any ideas?
hello :)
Is it the same with Skim ?
Regards Alain
Skim is still having the same problem. I downloaded and changed all the settings I thought I needed to. It does update the PDF file in Skim, but it still doesn't bring the window into focus. But at least it "almost" brings it into focus (leaving TextMate still active, but showing up immediately behind that).
Keith
On Oct 22, 2007, at 6:46 AM, Keith Penrod wrote:
I had TextMate set up to download "Cutting edge" and it just downloaded a new upgrade the other day. Before the download, I had everything working just fine with TeXniscope, but after I installed the upgrade, whenever I compile a LaTeX file in TextMate, it doesn't open TeXniscope. TeXniscope does update the PDF file (or open it if it's not already open) but it doesn't bring that file into focus like it did before. Even if I type Cmd-Opt-Ctrl-O nothing happens. In the typesetting dialog that comes up, there's a button that says "Preferences" and I have the "Show pdf automatically" option enabled, but it still doesn't bring TeXniscope into focus. Any ideas?
Keith
Skim is now the supported reader. http://skim-app.sourceforge.net/
See if that works for you.
Jenny
For new threads USE THIS: textmate at lists.macromates.com (threading gets destroyed and the universe will collapse if you
don't)
On Oct 22, 2007, at 6:46 AM, Keith Penrod wrote:
I had TextMate set up to download "Cutting edge" and it just downloaded a new upgrade the other day. Before the download, I had everything working just fine with TeXniscope, but after I installed the upgrade, whenever I compile a LaTeX file in TextMate, it doesn't open TeXniscope. TeXniscope does update the PDF file (or open it if it's not already open) but it doesn't bring that file into focus like it did before. Even if I type Cmd-Opt-Ctrl-O nothing happens. In the typesetting dialog that comes up, there's a button that says "Preferences" and I have the "Show pdf automatically" option enabled, but it still doesn't bring TeXniscope into focus. Any ideas?
Keith
Skim is now the supported reader. http://skim-app.sourceforge.net/
See if that works for you.
Jenny
On Oct 22, 2007, at 10:04 AM, Keith Penrod wrote:
Skim is still having the same problem. I downloaded and changed all the settings I thought I needed to. It does update the PDF file in Skim, but it still doesn't bring the window into focus. But at least it "almost" brings it into focus (leaving TextMate still active, but showing up immediately behind that).
Keith
I am having the same problem and it is new. The powers-that-be will surely sort this out soon.
Jenny
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Oct 22, 2007, at 1:53 PM, Jenny Harrison wrote:
On Oct 22, 2007, at 10:04 AM, Keith Penrod wrote:
Skim is still having the same problem. I downloaded and changed all the settings I thought I needed to. It does update the PDF file in Skim, but it still doesn't bring the window into focus. But at least it "almost" brings it into focus (leaving TextMate still active, but showing up immediately behind that).
Keith
I am having the same problem and it is new. The powers-that-be will surely sort this out soon.
I can confirm the problem, and it occurred during the move from revision 8128 to 8129. The change at that point added an osascript call to open the viewer, which is likely what is causing the problem. Since no code was removed at that update, I am puzzled as to how it was working before.
Hopefully Brad can shed some light in the matter he's the texMate.py expert. Those of you are that really bothered by this and already have the subversion version of the bundle, you can use the terminal to navigate to the Latex.tmbundle subdirectory, and there issue the command:
svn up -r8128 Support/bin/texMate.py
This will return the offending file to an older version of it that was working. Hopefully this won't be causing any major side effects.
Or you can just wait if it is not really that bothersome.
Jenny
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On 10/22/07, Charilaos Skiadas cskiadas@gmail.com wrote:
On Oct 22, 2007, at 1:53 PM, Jenny Harrison wrote:
On Oct 22, 2007, at 10:04 AM, Keith Penrod wrote:
Skim is still having the same problem. I downloaded and changed all the settings I thought I needed to. It does update the PDF file in Skim, but it still doesn't bring the window into focus. But at least it "almost" brings it into focus (leaving TextMate still active, but showing up immediately behind that).
Keith
I am having the same problem and it is new. The powers-that-be will surely sort this out soon.
I can confirm the problem, and it occurred during the move from revision 8128 to 8129. The change at that point added an osascript call to open the viewer, which is likely what is causing the problem. Since no code was removed at that update, I am puzzled as to how it was working before.
Hopefully Brad can shed some light in the matter he's the texMate.py expert. Those of you are that really bothered by this and already have the subversion version of the bundle, you can use the terminal to navigate to the Latex.tmbundle subdirectory, and there issue the command:
svn up -r8128 Support/bin/texMate.py
This will return the offending file to an older version of it that was working. Hopefully this won't be causing any major side effects.
Or you can just wait if it is not really that bothersome.
Jenny
Haris Skiadas Department of Mathematics and Computer Science Hanover College
I've just checked in a change that may fix the problem. If any part of your path had spaces in it then I can see what was going on. As of now I cannot reproduce the problem, and I don't recall ever having the problem you are describing.
Brad
______________________________________________________________________
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Hi Brad, On Oct 23, 2007, at 8:45 AM, Brad Miller wrote:
I've just checked in a change that may fix the problem. If any part of your path had spaces in it then I can see what was going on. As of now I cannot reproduce the problem, and I don't recall ever having the problem you are describing.
I can confirm that your change fixes the problem in my case. However, in my case the path did not have any spaces in it to begin with, but the problem was there. The path was:
/Users/haris/Documents/HanoverPublic/currentCourse/2007Math217/ exercises/due1002.tex
Brad
Haris Skiadas Department of Mathematics and Computer Science Hanover College
Is there a way to revert without the subversion bundle, or is there another way to fix the problem?
Keith On Oct 22, 2007, at 2:21 PM, Charilaos Skiadas wrote:
On Oct 22, 2007, at 1:53 PM, Jenny Harrison wrote:
On Oct 22, 2007, at 10:04 AM, Keith Penrod wrote:
Skim is still having the same problem. I downloaded and changed all the settings I thought I needed to. It does update the PDF file in Skim, but it still doesn't bring the window into focus. But at least it "almost" brings it into focus (leaving TextMate still active, but showing up immediately behind that).
Keith
I am having the same problem and it is new. The powers-that-be will surely sort this out soon.
I can confirm the problem, and it occurred during the move from revision 8128 to 8129. The change at that point added an osascript call to open the viewer, which is likely what is causing the problem. Since no code was removed at that update, I am puzzled as to how it was working before.
Hopefully Brad can shed some light in the matter he's the texMate.py expert. Those of you are that really bothered by this and already have the subversion version of the bundle, you can use the terminal to navigate to the Latex.tmbundle subdirectory, and there issue the command:
svn up -r8128 Support/bin/texMate.py
This will return the offending file to an older version of it that was working. Hopefully this won't be causing any major side effects.
Or you can just wait if it is not really that bothersome.
Jenny
Haris Skiadas Department of Mathematics and Computer Science Hanover College
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Keith,
I committed a change to the subversion repository that fixes the problem for Haris. I have not been able to reproduce the problem you reported on my machine at all.
While you do not need the subversion bundle, you do need subversion in order to get this fix.
Brad
On 10/24/07, Keith Penrod keith.penrod@gmail.com wrote:
Is there a way to revert without the subversion bundle, or is there another way to fix the problem?
Keith On Oct 22, 2007, at 2:21 PM, Charilaos Skiadas wrote:
On Oct 22, 2007, at 1:53 PM, Jenny Harrison wrote:
On Oct 22, 2007, at 10:04 AM, Keith Penrod wrote:
Skim is still having the same problem. I downloaded and changed all the settings I thought I needed to. It does update the PDF file in Skim, but it still doesn't bring the window into focus. But at least it "almost" brings it into focus (leaving TextMate still active, but showing up immediately behind that).
Keith
I am having the same problem and it is new. The powers-that-be will surely sort this out soon.
I can confirm the problem, and it occurred during the move from revision 8128 to 8129. The change at that point added an osascript call to open the viewer, which is likely what is causing the problem. Since no code was removed at that update, I am puzzled as to how it was working before.
Hopefully Brad can shed some light in the matter he's the texMate.py expert. Those of you are that really bothered by this and already have the subversion version of the bundle, you can use the terminal to navigate to the Latex.tmbundle subdirectory, and there issue the command:
svn up -r8128 Support/bin/texMate.py
This will return the offending file to an older version of it that was working. Hopefully this won't be causing any major side effects.
Or you can just wait if it is not really that bothersome.
Jenny
Haris Skiadas Department of Mathematics and Computer Science Hanover College
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Oct 24, 2007, at 8:00 PM, Brad Miller wrote:
I committed a change to the subversion repository that fixes the problem for Haris. I have not been able to reproduce the problem you reported on my machine at all.
hi brad,
i updated to 8334 but the problem isn't gone (i'm using skim instead of texniscope). however, i'm not quite sure if we were talking about the same problem:
the preview window used to get raised to the front if there were no problems. otherwise the log window would stay in the frontmost position. currently, skim gets raised if there are windows in front of skim itself but it never gets raised to the frontmost position, that is, the log window still stays in front of it.
changing the preferences in the typeset & view window, that is, removing the tick in front of "Keep log window open" raises skim to the top position.
reverting to the 8128 version of texMate.py as you suggested in your email of october 23 doesn't change the situation.
christoph
On 10/25/07, Christoph Eyrich ceyrich@gmx.net wrote:
On Oct 24, 2007, at 8:00 PM, Brad Miller wrote:
I committed a change to the subversion repository that fixes the problem for Haris. I have not been able to reproduce the problem you reported on my machine at all.
hi brad,
i updated to 8334 but the problem isn't gone (i'm using skim instead of texniscope). however, i'm not quite sure if we were talking about the same problem:
the preview window used to get raised to the front if there were no problems. otherwise the log window would stay in the frontmost position. currently, skim gets raised if there are windows in front of skim itself but it never gets raised to the frontmost position, that is, the log window still stays in front of it.
changing the preferences in the typeset & view window, that is, removing the tick in front of "Keep log window open" raises skim to the top position.
reverting to the 8128 version of texMate.py as you suggested in your email of october 23 doesn't change the situation.
christoph
Thanks for clarifying. Unfortunately I get the behavior you describe as correct. With the keep log window open option checked, Skim is raised to the front most position after a successful typesetting run.
I'm certainly no Applescript expert so its possible that something subtle has escaped my attention.
What version of Skim do you have? What about OS X?
Brad
______________________________________________________________________
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Oct 25, 2007, at 6:50 PM, Brad Miller wrote:
Unfortunately I get the behavior you describe as correct. With the keep log window open option checked, Skim is raised to the front most position after a successful typesetting run.
i noticed that it works this way the first time i run 'typeset & view' on a new document. with each subseqent run, the log window keeps its front position.
I'm certainly no Applescript expert so its possible that something subtle has escaped my attention.
neither am i. unfortunately, i have no idea if this is a simple configuration problem of my system or something more basic. but it's a relatively recent one.
What version of Skim do you have?
Version 0.9.3 (v15)
What about OS X?
10.4.10 (intel) (this might change on saturday :-)
christoph
On 10/25/07, Christoph Eyrich ceyrich@gmx.net wrote:
On Oct 25, 2007, at 6:50 PM, Brad Miller wrote:
Unfortunately I get the behavior you describe as correct. With the keep log window open option checked, Skim is raised to the front most position after a successful typesetting run.
i noticed that it works this way the first time i run 'typeset & view' on a new document. with each subseqent run, the log window keeps its front position.
I'm certainly no Applescript expert so its possible that something subtle has escaped my attention.
neither am i. unfortunately, i have no idea if this is a simple configuration problem of my system or something more basic. but it's a relatively recent one.
What version of Skim do you have?
Version 0.9.3 (v15)
What about OS X?
10.4.10 (intel) (this might change on saturday :-)
Well we appear to be using the same version of things, although with luck I'll change OS's tomorrow.
The last meesage in the Typeset & View window should be something like: Telling Skim to Refresh "filename.pdf"
Do you see that message even when Skim does not come all the way forward?
Brad
christoph
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Oct 25, 2007, at 10:03 PM, Brad Miller wrote:
The last meesage in the Typeset & View window should be something like: Telling Skim to Refresh "filename.pdf"
Do you see that message even when Skim does not come all the way forward?
yes. but perhaps this is an important point: i'm not sure but maybe the begin of current behaviour (with the log windows remaining in front of the skim window) dates back to this internal change of the refreshing process. some weeks ago skim had to watch the pdf file and reload it if there was a change, and back then, i think, skim was raised to the front if the run was successful. now this is handled by this script and doesn't work in the former way. (well, i don't want to go back!)
christoph
-
Alain Matthes -
Brad Miller -
Charilaos Skiadas -
Christoph Eyrich -
Jenny Harrison -
Keith Penrod