Sublime Forum

Sublime Text 3 Beta

#5

Hopefully plugin authors will be quick on making change and/or they find a smart way to keep plugins to work on both 2 and 3.

Any news on tooltip and sidebar API? Are you planning to implement this (ever? :mrgreen: )

Also, from this sentence:

We should understand that ST is not a one man show anymore?

0 Likes

#6

:astonished:

0 Likes

#7

It’s something I very much want to get done, but at this stage I don’t know when that will be.

There will be something to say on that front soon.

0 Likes

#8

A most sincere request for some sweet sweet loving :smile:

0 Likes

#9

Yay!

0 Likes

#10

It’s worth mentioning that I haven’t gotten around to updating the API reference yet, but you can now see the full API by looking through sublime.py, which lives next to the executable.

The plugin API itself has moved from using boost.python in S2 to the raw Python C API in S3, with sublime.py wrapping the C level API to provide something mostly compatible with the S2 API.

0 Likes

#11

async on_query_completions ?

0 Likes

#12

Jon,

Do you have a short list of features you plan on implementing for 3 or is it a “wait and see” situation?

0 Likes

#13
AttributeError: 'View' object has no attribute 'score_selector'
0 Likes

#14

atomi: There are a couple of not-yet-implemented methods that I’m aware of, and presumably some in that I’m not aware of too. view.score_selector falls into the latter camp, I’ll fix it for the next build.

0 Likes

#15

Okay. Thanks. Congrats on shipping by the way :smile:

0 Likes

#16

Hopefully the $15 upgrade version starts from purchases made 12/2012 and on considering that’s within the last 30 days!

0 Likes

#17

Thanks jps \o/

How could I buy the upgrade licence ?

0 Likes

#18

Upgrade licenses aren’t available yet, nor are they required. The plan is that upgrading won’t need to happen until 3.0 is released, and I don’t want anyone paying before they need to.

0 Likes

Mandatory Paid Upgrade
#19

Did Cmd+Return stopped working as insert new line?

0 Likes

#20

It’s working for me. If you enter “sublime.log_commands(True)” and “sublime.log_input(True)” in the console, what output do you when when you press cmd+return?

0 Likes

#21

Awesome, so far v3 easily beats v2. Seems to be a lot faster than v2, almost on par with v1. And I finally get to disable animations :smile:

Just a couple of questions:

Is there a theme that copies v1? Tabs are hard to distinguish in 2/3 and they take up more space.
How do I completely hide the folder view? view -> folders is grayed out.
What font rendering was used in v1? Trying the various pixel rendering options I’m getting close, but not quite there yet.
How can I view char encoding for a file? In v1, hovering over the tab will display the file name as well as encoding in the status bar.

And I think the status text isn’t affected by the font rendering settings (things like tab count in the status bar). Is this intentional or a bug?

Thanks Jon.

(apologies if some those features were provided by plugins, been using the same setup for almost 3 years and have probably forgotten a plugin I installed)

0 Likes

#22

Without begin_edit, how do I do something like this:

                    self.__view.run_command("adb_add_line", {"some_data": data, "instance": self})
                    # or
                    self.__view.run_command("adb_add_line", {"some_data": data, "callback": self.callback})

This currently gives me:

sublime_api.view_run_command(self.view_id, cmd, args) TypeError: Value required

Do I have to expand it to self.__view.run_command("adb_add_line", {"every": single, "data": needed, "to": run, "this": command})?

0 Likes

#23

quarnster: the latter option:

self.view.run_command("adb_add_line", {"every": single, "data": needed, "to": run, "this": command})

The advantage of this approach is that issued commands will work correct with repeat, as well as with macros.

0 Likes

#24

FFFFF :confused: Yeah, not such a huge fan either

Yeah, it would be nice if you could somehow run arbitrary functions as commands, with access to closures, so you don’t have to do all that explicit dependency marshaling.

Note there’s lots of times from inside an on_change callback passed to show_input_panel that you need an Edit object to make sure sublime paints updates you make therein.

Or from timeouts, or … etc

0 Likes