Hi all,
As of only very recently, I get the following drop-down error box when I try to typeset a LaTeX document:
| Failure running "Typeset & View (PDF)". | | Typeset & View (PDF):4: undefined method `+' for nil:NilClass (NoMethodError)
I think it was working until 1-2 updates ago.
Andrew
Hi Alan,
On 05/03/2014 15:58, Allan Odgaard wrote:
On 5 Mar 2014, at 21:49, Andrew Jaffe wrote:
| Typeset & View (PDF):4: undefined method `+' for nil:NilClass (NoMethodError)
I think it was working until 1-2 updates ago.
This will happen if you disable the Bundle Support bundle in Preferences → Bundles.
Thanks -- except that it's not disabled! However, if I found that if I did explicitly uninstall (i.e., uncheck in the dialog) and then reinstall (re-check), it works again. Weird.
Yours,
Andrew
On 5 Mar 2014, at 23:23, Andrew Jaffe wrote:
This will happen if you disable the Bundle Support bundle in Preferences → Bundles.
Thanks -- except that it's not disabled! However, if I found that if I did explicitly uninstall (i.e., uncheck in the dialog) and then reinstall (re-check), it works again. Weird.
TextMate relies on its bundle index, so it could be a bug in TextMate causing the index to be wrong.
I recently fixed an issue where a change to a bundle could cause it to be dropped from the index incase TextMate was terminated before it got a chance to write out the updated index.
I’ll probably introduce some sort of index scrubber to ensure it’s clean, relying solely on delta-updating the bundle index from fs-events was probably a bit naive…
Andrew Jaffe <a.h.jaffe@...> writes:
Hi Alan,
On 05/03/2014 15:58, Allan Odgaard wrote:
On 5 Mar 2014, at 21:49, Andrew Jaffe wrote:
| Typeset & View (PDF):4: undefined method `+' for nil:NilClass (NoMethodError)
I think it was working until 1-2 updates ago.
This will happen if you disable the Bundle Support bundle in Preferences → Bundles.
Thanks -- except that it's not disabled! However, if I found that if I did explicitly uninstall (i.e., uncheck in the dialog) and then reinstall (re-check), it works again. Weird.
Yours,
Andrew
Hi,
I have the same problem, getting a "Failure running “Typeset & View (PDF)” when trying to compile the pdf. I unchecked and checked again the Bundle Support, as Andrew suggested, but it didn't work. Any other ideas? (Also I have upgraded to Yosemite beta which causes me problems with Skim… so that might be the reason.)
Grateful for any adivce, Thanks,
Niko
On 29 Aug 2014, at 22:15, Niko wrote:
I have the same problem, getting a "Failure running “Typeset & View (PDF)” when trying to compile the pdf […]
Please quote full error message.
Also try https://github.com/textmate/textmate/wiki/Reverting-To-Defaults
* Skriv a reas Niko (niko.lai@gmx.net):
|> |> I have the same problem, getting a "Failure running “Typeset & View (PDF)” |> when trying to compile the pdf. I unchecked and checked again the Bundle |> Support, as Andrew suggested, but it didn't work. Any other ideas? (Also I |> have upgraded to Yosemite beta which causes me problems with Skim… so |> that might be the reason.)
I experienced the same thing after upgrading to Yosemite beta, because Yosemite points to Ruby 2.0 (/System/Library/Frameworks/Ruby.framework/Versions). I added Ruby 1.8 to make it work again. --Gildas
On 31 Aug 2014, at 18:32, Gildas Hamel wrote:
I experienced the same thing after upgrading to Yosemite beta, because Yosemite points to Ruby 2.0 (/System/Library/Frameworks/Ruby.framework/Versions). I added Ruby 1.8 to make it work again.
TextMate will automatically fetch ruby 1.8 on Yosemite (if running a command that requires it).
So things are supposed to work out-of-the-box on 10.10 without the need to manually edit or install anything.
Hi all,
looks like Skim is pretty much out-of-action with Yosemite for now: seems pdfkit is misbehaving rather chronically. I saw a couple of instances where opening a simple 200KB pdf caused Skim to first expand to 8GB of memory in Activity Monitor (causing "out of memory: quit applications you're no longer using" warnings), and then needed to be forced to quit. In short: probably not worth chasing too hard until some things in pdfkit get some serious attention.
All part of the fun of beta testing 10.10.
Cheers, Paul
On Mon, Sep 1, 2014 at 2:35 AM, Allan Odgaard mailinglist@textmate.org wrote:
On 31 Aug 2014, at 18:32, Gildas Hamel wrote:
I experienced the same thing after upgrading to Yosemite beta, because Yosemite points to Ruby 2.0 (/System/Library/Frameworks/Ruby.framework/Versions). I added Ruby 1.8 to make it work again.
TextMate will automatically fetch ruby 1.8 on Yosemite (if running a command that requires it).
So things are supposed to work out-of-the-box on 10.10 without the need to manually edit or install anything.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Andrew Jaffe -
Gildas Hamel -
Niko -
Paul McCann