clemos / haxe-sublime-bundle

Sublime Text bundle for Haxe programming language
Apache License 2.0
237 stars 86 forks source link

Shortcuts stopped working #124

Closed jonathanhirz closed 10 years ago

jonathanhirz commented 10 years ago

I'm not sure what happened or what I changed, but shortcuts have stopped working. Ctrl-Shift-B to switch output, Ctrl-Enter to build...they just stopped working. The only thing I can think of is I just updated to haxeflixel 3.0.3 OS X, Sublime Text 2

jonathanhirz commented 10 years ago

ok this might be something weird with my computer or some plugin I have installed on ST2...I can't even type an open parenthesis in sublime...wth

So I can type '(' in other files in ST2, but in open haxeflixel project files I can't type that character. Maybe something is blocking that shift key or something, and this is making the shortcuts not work? I'm very confused, and help?

ghost commented 10 years ago

I'm getting the same issues. Not sure if it's related, but I've also stopped getting autocompletion suggestions since these issues began. Nothing on my systems (getting the problem on all my machines) has changed. I suppose Package Control automatically updated my Haxe package.

Here's the error that gets printed in the Sublime console when loading the plugin:

Reloading plugin /Users/****/Library/Application Support/Sublime Text 2/Packages/Haxe/HaxeComplete.py
Traceback (most recent call last):
  File "./sublime_plugin.py", line 62, in reload_plugin
  File "./HaxeComplete.py", line 26, in <module>
    from .HaxeHelper import runcmd, show_quick_panel
ValueError: Attempted relative import in non-package
Reloading plugin /Users/****/Library/Application Support/Sublime Text 2/Packages/Haxe/HaxeHelper.py
clemos commented 10 years ago

mm We refactored things a little bit with @underscorediscovery but I guess it broke ST2/Python 2 compatibility :\ I'll look into it ASAP, but meanwhile you may want to either upgrade to ST3 or revert to a previous version... Sorry for that :p

ruby0x1 commented 10 years ago

I will also take a look a bit, I think it's possible to keep support, but ST3 is already much better and package control works with it now (that used to be a blocking feature)

ghost commented 10 years ago

I've already upgraded to ST3 assuming it would have worked, and it does. I'm just going to stay with it, even with backwards compatibility. The features in ST3 are great!

ruby0x1 commented 10 years ago

see #126, @clemos said he will merge when he has a chance :)

jonathanhirz commented 10 years ago

I haven't even looked at st3 yet, I guess this would be as good a reason as any to upgrade.

clemos commented 10 years ago

Ok it should work again thanks to @underscorediscovery ;) Please confirm.

jonathanhirz commented 10 years ago

Looks good. Thanks for magically fixing my dev tools over the internet @clemos and @underscorediscovery!

wilbefast commented 10 years ago

@clemos this fixes my #125 problem :) cheers man!