Dev Build 2041

[jps]

scroll_left and scroll_right should already work as bindable buttons.

[jps]

Not sure if that's related but the thing I wanted to do is to put "Copy full file path" item into tab's context menu.

In general, only commands that take "group" and "index" arguments should be used in the tab context menu, that way they'll apply to the correct tab (commands that are independent of the clicked on tab, like new_file, are fine too). It's not possible to make commands that do this with the API yet, unfortunately.

[rchl]

Added:

{ "button": "scroll_left", "modifiers": [], "command": "prev_view" },
{ "button": "scroll_right", "modifiers": [], "command": "next_view" },

but didn't really have any success with that.

[jps]

scroll_left and right aren't usable for mouse bindings by themselves, as they'll get eaten for scrolling. They have to be used with at least one modifier (but note that ctrl and shift modifiers don't work with scroll_left and scroll_right in this version, I'll fix it for the next one).

[atomi]

For some reason none of the completions/snippets that use ":" are ever working for me.

For example groovy has "m:" as a tab target but pressing "m"+":"+"tab" never works.
Same goes for the "<:" in text.xml scope.

anyone else experiencing this?

I'm using Sublime Text 2 Build 2042 Win x64 (portable zip).

[atomi]

I'd guess it's because of the 'prefixer' used. ie the function used to determine the region extents of the word behind the cursor.

It probably sees just the ':' as the prefix.

You know what?
I'm figuring that colon is used to differentiate between snippets and completions in the completions drop down list (ctrl+space) and is not part of the tab target.

What is interesting is that the text.xml scope has long-tag and short-tag snippets and the tab targets for those do include a trailing colon. Yet those don't trigger. In source.groovy's completions drop down list there's "::" "key value pair (hash) and "!:" "assert" and others that do not include a trailing colon in the snippet's tab target yet they don't fire on tab either.

I think the problem lies in some ST2's function not recognizing non-alpha-numeric characters as tag triggers.
So, definitely a bug.

[jps]

Snippets don't trigger on non-alphanumeric triggers. This was introduced in the recent snippet rework, it's on the TODO list to enable it again.

[atomi]

Snippets don't trigger on non-alphanumeric triggers. This was introduced in the recent snippet rework, it's on the TODO list to enable it again.

Thanks for confirming this

[RNHurt]

I'm on OS X and switching between tabs with the keyboard shortcut is not working reliably. Previously, using CMD+SHIFT+} to go to the next tab worked very well but after this update it seems to break when ST2 loses focus. I'm forced to go to the File->Switch Files->Next File menu item and then the keyboard shortcuts seem to start working again.

I can't reproduce the problem with 100% certainty and at first I thought it was my imagination. But it's happened several times in the past several hours and I'm pretty sure its a bug. If there is a better place to file a bug report please let me know and I'll make it official.

Build 2042 solved this problem.

Thanx!
Richard

[adzenith]

Bug report in OS X:
With no windows open:

• Create a new document (creates a new window)
• Open Goto Anything
• Press cmd+w twice (once to close the document, once to close the window)

Sublime Text 2 crashes.

Also, in Google Chrome, pressing cmd+l with no open windows will create a new window and then focus on the address bar there. Could similar behavior be added to Sublime Text? I.e., if I press cmd+p with no open windows, it'd be nice if a window could open to show the panel, or if the panel could show without a window. That's how I hit this bug—I hit cmd+n to make a new window just so I could hit cmd+p to bring up the panel and cmd+w to close the temporary document I made.