Upon updating my bundle to the latest svn source of the latex bundle I got a similar html output window. Reverting to revision 10669 returned the expected output.
Thanks again for all the effort that goes into improving the Latex bundle, your efforts are greatly appreciated!
Peter
On Sun, Oct 5, 2008 at 4:43 AM, Niels Kobschaetzki n.kobschaetzki@googlemail.com wrote:
Hi!
In addition to my TeX-typesetting-problem I noticed that the HTML-output-window suddenly looks just plain wrong. I attached a screenshot. Some of the text is huge, other parts are very small and behind the huge stuff.
Niels
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Oct 7, 2008, at 7:52 AM, Peter Cowan wrote:
Upon updating my bundle to the latest svn source of the latex bundle I got a similar html output window. Reverting to revision 10669 returned the expected output.
Thanks again for all the effort that goes into improving the Latex bundle, your efforts are greatly appreciated!
Peter
On Sun, Oct 5, 2008 at 4:43 AM, Niels Kobschaetzki n.kobschaetzki@googlemail.com wrote:
Hi!
In addition to my TeX-typesetting-problem I noticed that the HTML-output-window suddenly looks just plain wrong. I attached a screenshot. Some of the text is huge, other parts are very small and behind the huge stuff.
Could either of you paste the html source of the window? I'm assuming that you also have a recent Support folder?
—alex
On Tue, Oct 7, 2008 at 10:23 AM, Alex Ross tm-alex@rosiba.com wrote:
On Oct 7, 2008, at 7:52 AM, Peter Cowan wrote:
Upon updating my bundle to the latest svn source of the latex bundle I got a similar html output window. Reverting to revision 10669 returned the expected output.
Thanks again for all the effort that goes into improving the Latex bundle, your efforts are greatly appreciated!
Peter
On Sun, Oct 5, 2008 at 4:43 AM, Niels Kobschaetzki n.kobschaetzki@googlemail.com wrote:
Hi!
In addition to my TeX-typesetting-problem I noticed that the HTML-output-window suddenly looks just plain wrong. I attached a screenshot. Some of the text is huge, other parts are very small and behind the huge stuff.
Could either of you paste the html source of the window? I'm assuming that you also have a recent Support folder?
I have a recent Support folder.
The html-source of the output-window <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html; charset=utf-8"> <title>Typesetting "technologiepolitikarbeit.tex"…</title>
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/default/style.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/bright/style.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/dark/style.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/halloween/style.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/night/style.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/shiny/style.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/default/style.css" type="text/css" charset="utf-8" media="screen"> <link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/default/print.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/bright/style.css" type="text/css" charset="utf-8" media="screen"> <link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/bright/print.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/dark/style.css" type="text/css" charset="utf-8" media="screen"> <link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/dark/print.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/halloween/style.css" type="text/css" charset="utf-8" media="screen"> <link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/halloween/print.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/shiny/style.css" type="text/css" charset="utf-8" media="screen"> <link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Bundles/Latex.tmbundle/Support/css/shiny/print.css" type="text/css" charset="utf-8" media="screen">
<link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/default/print.css" type="text/css" charset="utf-8" media="print"> <link rel="stylesheet" href="file:///Users/nik/Library/Application%20Support/TextMate/Themes/Webpreview//print.css" type="text/css" charset="utf-8" media="print"> <script src="file:///Users/nik/Library/Application%20Support/TextMate/Support/script/default.js" type="text/javascript" charset="utf-8"></script> <script src="file:///Users/nik/Library/Application%20Support/TextMate/Support/script/webpreview.js" type="text/javascript" charset="utf-8"></script> <script src="file:///Users/nik/Library/Application%20Support/TextMate/Support/script/sortable.js" type="text/javascript" charset="utf-8"></script> <script type="text/javascript" charset="utf-8"> var image_path = "file:///Users/nik/Library/Application%20Support/TextMate/Support/images/"; </script>
</head> <body id="tm_webpreview_body" class="shiny"> <div id="tm_webpreview_header"> <img id="gradient" src="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/shiny/images/header.png" alt="header"> <p class="headline">Typesetting "technologiepolitikarbeit.tex"…</p> <p class="type"><p class="error">Error: xelatex is not found, you need to install LaTeX or be sure that your PATH is setup properly.</p> sh: line 0: type: xelatex: not found </p> <img id="teaser" src="file:///Users/nik/Library/Application%20Support/TextMate/Support/themes/shiny/images/teaser.png" alt="teaser"> <div id="theme_switcher"> <form action="#" onsubmit="return false;"> <div> Theme: <select onchange="selectTheme(event);" id="theme_selector"> <optgroup label="TextMate">
<option value="default" title="/Users/nik/Library/Application%20Support/TextMate/Support/themes/">default</option>
<option value="bright" title="/Users/nik/Library/Application%20Support/TextMate/Support/themes/">bright</option>
<option value="dark" title="/Users/nik/Library/Application%20Support/TextMate/Support/themes/">dark</option>
<option value="halloween" title="/Users/nik/Library/Application%20Support/TextMate/Support/themes/">halloween</option>
<option value="night" title="/Users/nik/Library/Application%20Support/TextMate/Support/themes/">night</option>
<option value="shiny" title="/Users/nik/Library/Application%20Support/TextMate/Support/themes/">shiny</option>
</optgroup> <optgroup label="User">
</optgroup> </select> </div> <script type="text/javascript" charset="utf-8"> document.getElementById('theme_selector').value = 'shiny'; </script> </form> </div> </div> <div id="tm_webpreview_content" class="shiny"> sh: line 0: type: xelatex: not found <p class="error">Error: xelatex is not found, you need to install LaTeX or be sure that your PATH is setup properly.</p> </div> </body> </html>
Niels
On Oct 7, 2008, at 9:23 PM, Niels Kobschaetzki wrote:
On Tue, Oct 7, 2008 at 10:23 AM, Alex Ross tm-alex@rosiba.com wrote:
On Oct 7, 2008, at 7:52 AM, Peter Cowan wrote:
Upon updating my bundle to the latest svn source of the latex bundle I got a similar html output window. Reverting to revision 10669 returned the expected output.
Thanks again for all the effort that goes into improving the Latex bundle, your efforts are greatly appreciated!
Peter
On Sun, Oct 5, 2008 at 4:43 AM, Niels Kobschaetzki n.kobschaetzki@googlemail.com wrote:
Hi!
In addition to my TeX-typesetting-problem I noticed that the HTML-output-window suddenly looks just plain wrong. I attached a screenshot. Some of the text is huge, other parts are very small and behind the huge stuff.
Could either of you paste the html source of the window? I'm assuming that you also have a recent Support folder?
I have a recent Support folder.
<div id="tm_webpreview_content" class="shiny"> sh: line 0: type: xelatex: not found <p class="error">Error: xelatex is not found, you need to install LaTeX or be sure that your PATH is setup properly.</p> </div> </body> </html>
You must set up your PATH variable in TextMate's preference panel. —Alex
On Tue, Oct 7, 2008 at 2:32 PM, Alex Ross tm-alex@rosiba.com wrote:
On Oct 7, 2008, at 9:23 PM, Niels Kobschaetzki wrote:
On Tue, Oct 7, 2008 at 10:23 AM, Alex Ross tm-alex@rosiba.com wrote:
On Oct 7, 2008, at 7:52 AM, Peter Cowan wrote:
Upon updating my bundle to the latest svn source of the latex bundle I got a similar html output window. Reverting to revision 10669 returned the expected output.
Thanks again for all the effort that goes into improving the Latex bundle, your efforts are greatly appreciated!
Peter
On Sun, Oct 5, 2008 at 4:43 AM, Niels Kobschaetzki n.kobschaetzki@googlemail.com wrote:
Hi!
In addition to my TeX-typesetting-problem I noticed that the HTML-output-window suddenly looks just plain wrong. I attached a screenshot. Some of the text is huge, other parts are very small and behind the huge stuff.
Could either of you paste the html source of the window? I'm assuming that you also have a recent Support folder?
I have a recent Support folder.
<div id="tm_webpreview_content" class="shiny"> sh: line 0: type: xelatex: not found <p class="error">Error: xelatex is not found, you need to install LaTeX or be sure that your PATH is setup properly.</p> </div> </body> </html>
You must set up your PATH variable in TextMate's preference panel.
Indeed, this fixed my issue, thank you. Sorry for missing that.
Peter
—Alex
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 7 Oct 2008, at 22:32, Alex Ross wrote:
You must set up your PATH variable in TextMate's preference panel. —Alex
I had the same problem and that resolved it as well. Why is it that we must set the PATH variable now? Didn't it use to work out of the box before the last revision?
Thanks,
enas
On Oct 8, 2008, at 9:38 AM, enas wrote:
On 7 Oct 2008, at 22:32, Alex Ross wrote:
You must set up your PATH variable in TextMate's preference panel. —Alex
I had the same problem and that resolved it as well. Why is it that we must set the PATH variable now? Didn't it use to work out of the box before the last revision?
In previous versions, a shell script was run before most commands, which tried to make the environment that the commands see be the same as the one the Terminal sees. This involved sourcing files like .bash_profile etc. These files often expect that they are run by a terminal application, with complications ensuing some times. Allan and others can probably explain this better, but the bottom line is that a GUI application could get into trouble sometimes for sourcing these shell configuration files. It was thought better therefore to slowly drop the support on such files, and move to this alternative system. I guess this was the version where the plug was finally pulled.
So it is not just the PATH variable that needs to be set, it's everything else you might need that is defined in .bash_profile. Unless I'm mistaken, I've been on the sidelines lately.
Thanks,
enas
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On Oct 8, 2008, at 4:49 PM, Charilaos Skiadas wrote:
On Oct 8, 2008, at 9:38 AM, enas wrote:
On 7 Oct 2008, at 22:32, Alex Ross wrote:
You must set up your PATH variable in TextMate's preference panel. —Alex
I had the same problem and that resolved it as well. Why is it that we must set the PATH variable now? Didn't it use to work out of the box before the last revision?
In previous versions, a shell script was run before most commands, which tried to make the environment that the commands see be the same as the one the Terminal sees. This involved sourcing files like .bash_profile etc. These files often expect that they are run by a terminal application, with complications ensuing some times. Allan and others can probably explain this better, but the bottom line is that a GUI application could get into trouble sometimes for sourcing these shell configuration files. It was thought better therefore to slowly drop the support on such files, and move to this alternative system. I guess this was the version where the plug was finally pulled.
Sourcing .bash_profile is also the source of some bizarre bugs. TextMate's Support folder has a builder.rb and this is in conflict with a standard ruby library of the same name. Another user had a `bash` in his .profile which caused all textmate commands to call bash recursively until an exception occurred. You can imagine how long it took for us to figure THAT one out in ##textmate.
So it is not just the PATH variable that needs to be set, it's everything else you might need that is defined in .bash_profile. Unless I'm mistaken, I've been on the sidelines lately.
For most TextMate commands it is mostly just the PATH variable that needs to be initialized.
—Alex
On 8 Oct 2008, at 18:20, Alex Ross wrote:
Sourcing .bash_profile is also the source of some bizarre bugs. TextMate's Support folder has a builder.rb and this is in conflict with a standard ruby library of the same name. Another user had a `bash` in his .profile which caused all textmate commands to call bash recursively until an exception occurred. You can imagine how long it took for us to figure THAT one out in ##textmate.
I'm very well aware how much of a pain these things can get (though most of the times I'd tend to think it's the users making bad things in their .profiles, but still, it's to the system to adapt to the user and not the other way around).
I would suggest however that at some point that gets clearly stated, as it's quite disturbing to face that weird output.
Anyway thanks again for your answers,
enas
On Oct 8, 2008, at 9:39 PM, enas wrote:
On 8 Oct 2008, at 18:20, Alex Ross wrote:
Sourcing .bash_profile is also the source of some bizarre bugs. TextMate's Support folder has a builder.rb and this is in conflict with a standard ruby library of the same name. Another user had a `bash` in his .profile which caused all textmate commands to call bash recursively until an exception occurred. You can imagine how long it took for us to figure THAT one out in ##textmate.
I'm very well aware how much of a pain these things can get (though most of the times I'd tend to think it's the users making bad things in their .profiles, but still, it's to the system to adapt to the user and not the other way around).
But here we want to protect users from bad things they may have put in their shells, and also avoid running code that is only meant to be executed when logging in. I agree that having to set up the PATH is slightly annoying, but it's something that only needs to be done once. And probably it will be made easier in the future…
I would suggest however that at some point that gets clearly stated, as it's quite disturbing to face that weird output.
Yes, the command should be made to show a more friendly error when it can't find the correct path — but remember you are using prerelease code so this kind of thing should be expected from time to time. Thanks for catching the bug, btw. :)
On 9 Oct 2008, at 00:07, Alex Ross wrote:
I'm very well aware how much of a pain these things can get (though most of the times I'd tend to think it's the users making bad things in their .profiles, but still, it's to the system to adapt to the user and not the other way around).
But here we want to protect users from bad things they may have put in their shells, and also avoid running code that is only meant to be executed when logging in. I agree that having to set up the PATH is slightly annoying, but it's something that only needs to be done once. And probably it will be made easier in the future…
I think I didn't express myself very well, but we're basically saying the same thing (TextMate should work no matter what exotic things one might have done in his shell).
I would suggest however that at some point that gets clearly stated, as it's quite disturbing to face that weird output.
Yes, the command should be made to show a more friendly error when it can't find the correct path — but remember you are using prerelease code so this kind of thing should be expected from time to time.
Sure I'm aware of that :) Just gave my 2 cents, as people say.
Thanks for catching the bug, btw. :)
I wasn't the one who actually caught the bug, though I'm happy I faced it at the same time someone else did (I think the OP was Niels Kobschaetzki).
enas
-
Alex Ross -
Charilaos Skiadas -
enas -
Niels Kobschaetzki -
Peter Cowan