ctrl+l broken on Sublime Text 3.1 (Build 3170)

Question

ctrl+l broken on Sublime Text 3.1 (Build 3170)

seshness opened this issue 6 years ago · 8 comments

seshness commented 6 years ago

Steps to repro

Press ctrl+l.

Expected

Sublime view is centered on line of text.

Actual

Error in Sublime Text console:

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 1072, in run_
    return self.run(edit)
  File "/Users/seshadri/Library/Application Support/Sublime Text 3/Installed Packages/Emacs Pro Essentials.sublime-package/lib/misc.py", line 144, in run
AttributeError: 'SbpCenterViewCommand' object has no attribute 'jove_cmd_name'

Additional Notes

Thanks for creating such a great Sublime package!

Answer 1 · 2018-05-07T20:33:58.000Z

Huh - I use that command all the time … I am on 3168 though, not 3170. Fascinating. I will quit and see if I get a new release and if I can reproduce it, I’ll sort it out.

Answer 2 · 2018-05-07T20:35:25.000Z

I just updated but got 3169 and not 3170 ... what's up with 3170? I am getting dev builds ... just not that one.

Answer 3 · 2018-05-07T21:24:01.000Z

I use it all the time too!

I see a similar error with option+backspace:

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 1066, in run_
    return self.run(edit, **args)
  File "/Users/seshadri/Library/Application Support/Sublime Text 3/Installed Packages/Emacs Pro Essentials.sublime-package/lib/misc.py", line 144, in run
AttributeError: 'SbpMoveThenDeleteCommand' object has no attribute 'jove_cmd_name'

It looks like Sublime Text 3.1 just released today: https://www.sublimetext.com/blog/articles/sublime-text-3-point-1

Possibly unrelated: My about screen is in the strange state of claiming I have "Version 3.0, Build 3170":

Answer 4 · 2018-05-07T21:27:40.000Z

Try downgrading?

Answer 5 · 2018-05-07T21:30:34.000Z

Dev Channel, Build 3169 works fine. I guess I'll stick to this build for now.

Answer 6 · 2018-05-07T21:31:59.000Z

Wow - I see that 3.1 has been released. That must be the 3170 build?

That's really bad that it broke this. It appears a module initialisation feature might no longer be working ...

Answer 7 · 2018-05-07T21:44:36.000Z

Yeah, Sublime's Changelog https://www.sublimetext.com/3#changelog confirms that correspondence: 3.1 (BUILD 3170).

Answer 8 · 2018-05-08T03:45:26.000Z

I upgraded to 3170 w/out any issues. So I will close this. Maybe you should ... try again or something?