Sublime Forum

Sublime Text 3 Beta

#50

[quote=“jboner”]Yeah. That is what is happening. The Goto Symbol works fine as usual, but Goto Definition returns: ‘Unable to find X’
How can I make this work?[/quote]

Firstly, you can see what symbols will be indexed for the current file via entering this in the console:

view.indexed_symbols()

You can also do view.symbols() to see what will be shown in the regular symbol view.

Indexed symbols are controlled by the showInIndexedSymbolList preference, which is defined in .tmPreferences files. Most syntax definitions are covered by the contents of Default/Symbols.tmPreferences, but the scala syntax definition appears to assign scope names differently.

In short, you need to edit “Packages/Scala/Symbols.tmPreferences” and change it to:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>name</key>
	<string>Symbol List</string>
	<key>scope</key>
	<string>entity.name.function.declaration, entity.name.class.declaration, entity.name.val.declaration, entity.name.type.declaration</string>
	<key>settings</key>
	<dict>
		<key>showInSymbolList</key>
		<integer>1</integer>
		<key>showInIndexedSymbolList</key>
		<integer>1</integer>
	</dict>
	<key>uuid</key>
	<string>31262BFB-520A-4253-A81C-60023C0CFC8B</string>
</dict>
</plist>

The changed lines above are just adding the value for showInIndexedSymbolList. I’ll make this change for the next build, but you can make it locally in the mean time. You’ll need to save the above contents into the Packages/Scala/Symbols.tmPreferences file. This will then override the version that’s stored in Scala.sublime-package.

0 Likes

Navigate to next/previous symbol?
#51

I agree with lyubenblagoev’s sentiment - I understand you’ve been hard at work on the new features for ST3 and appreciate what you’ve been working on, but it does seem that ST2 was beta for a long, long time - got released and now we’re basically paying for another beta period where potentially the app will have issues and not be stable. And I’d say apart from the work you’ve done on symbol loading, many of the features do seem more like a 2.1 release rather than a whole 3.0 release.

Edit: and on top that, most useful plugins won’t be initially compatible, and we’ll have to wait until the author can, or even will, get round to porting these (and that a new version of package manager is made available to support this). Overall it doesn’t feel right that at least some of these improvements aren’t back-ported into ST2.

With that in mid, I’ve already found one bug with HTML autocomplete that will stop be using it for now. I’ve included a screenshot to show it: cl.ly/image/1Z1a2m063A0s

This happens where I type <h and then press tab.

0 Likes

#52

The first version of Sublime Text 2 was available to registered users on September 17, 2010, with the most recent build being on September 18, 2012. 2 years of continuous updates is a massive amount. In reality, counting should start from January 18, 2008, as everyone who purchased then received updates until September 2012, four and a half years later.

0 Likes

#53

How to make a smooth jump? After copying the Library (complete) and change any reference from /Applications/Sublime Text 2.app to /Applications/Sublime Text.app most of my keyboard shortcuts do not work nor latex build… etc.

0 Likes

#54

I meant the life cycle of a full featured release, which is meant to be the final version, the major release.
Since a code editor is something all of us uses all the time I’m not interested in using beta, unstable versions of this kind of software. As I noted I bought V2 after it was in beta for a long time. So how long it took to get to a stable release is not something that users appreciate when they give their money for something.

0 Likes

#55

I don’t understand that. If you don’t want a unstable version you can use the stable st2 you paid for. It’s not going away and I’m sure it will get bug fixes when needed.

I’ve not read anything about an end of life of st2… was there something in the announcement I overread ? I think there are more people still using python 2 and nobody forces anyone on using python 3 … isn’t it the same with st2 and st3 ?

0 Likes

#56

One thing I have noticed: I can’t “Hide” the sidebar until I show something in it. The menu item is disabled.

0 Likes

#57

In fact, this folder is already in the project.
Once the file isn’t open anymore, it can’t find the symbol. But if I open the file, it can find the symbol.

0 Likes

#58

Thanx jps, i just installed ST3 and I see: the upsetting line break problem has been solved, this is essential to me as I use ST for prose writing!!! :smile:

Nice sanx a lot to John

Greetz

0 Likes

#59

[quote=“lyubenblagoev”]I meant the life cycle of a full featured release, which is meant to be the final version, the major release.
Since a code editor is something all of us uses all the time I’m not interested in using beta, unstable versions of this kind of software. As I noted I bought V2 after it was in beta for a long time. So how long it took to get to a stable release is not something that users appreciate when they give their money for something.[/quote]

I somewhat agree with your feeling as it looks like there’s no more support for ST2.
But OTOH, as a long times user of ST2 back to early beta, I can say that every beta builds of ST2 was more stable than most final builds of most other software.
Maybe it’s a little early now to jump in the ST3 wagon but wait a few weeks and I’m pretty sure the ST3 builds will be perfectly usable as your main editor (if we do not take into account missing plugins).

0 Likes

#60

[quote=“dafire”]

I don’t understand that. If you don’t want a unstable version you can use the stable st2 you paid for. It’s not going away and I’m sure it will get bug fixes when needed.

I’ve not read anything about an end of life of st2… was there something in the announcement I overread ? I think there are more people still using python 2 and nobody forces anyone on using python 3 … isn’t it the same with st2 and st3 ?[/quote]

There was no mention of anything to do with ST2’s life cycle and that’s kind of the point - we don’t know that, as users who paid during during the beta period, if we’re getting any new 2.x features - for example:

That to me reads more like ‘I found a bunch of bugs and I’ve fixed the plugin system to it doesn’t crash as much’.

0 Likes

#61

any news on this?

Edited: for posterity

0 Likes

#62

Great news. thanks a lot. i just bought a license in december 2012 and if st3 will be released, and it matches with my workflow that i have with st2, i’ll buy a license of st3. if here will be a upgrade license for less money, it will be nice. if not, i’ll also get it. for me st2 already paid off in a really short time. and i’ll suggest my boss to order company licenses.

tonight i’ll give st3 beta a try :smile:

0 Likes

#63

[quote=“tanepiper”]

There was no mention of anything to do with ST2’s life cycle and that’s kind of the point - we don’t know that, as users who paid during during the beta period, if we’re getting any new 2.x features - for example:

That to me reads more like ‘I found a bunch of bugs and I’ve fixed the plugin system to it doesn’t crash as much’.[/quote]

Do you have a problem with bugs and crashes on st2 ?

Obviously there are major changes to the plugin system and I don’t think that you would want that in st2. Switching vom python 2 to python 3 will probably break most existing addons so it simply won’t make sense to do this for st2.

0 Likes

#64

When is Sublime Text 4 likely to be released, requiring another payment?

Serious question, because the fact I’m so surprised by 2 being obsoleted so soon implies I’ve misunderstood how things work here.

0 Likes

#65

Feels like this site needs an account area that can properly track purchases etc. I only say this as the mention of people who very recently bought get a discount etc (I bought my copy yesterday, mind you I’m only paying $5 on top so that’s cool), but it feels a bit disjointed not being able to look up my current license status, upgrade options etc, and I imagine doing so would take some workload off of the support team (I can only imagine you’d have to contact via support to get the upgrade discount, rather than have your purchase date registered in a DB, check that against the conditions of the discount and apply it via checkout).

Just a mention. With the mention of issues ill just stick to ST2 for now; I have a lot of master yet.

0 Likes

#66

[quote=“jps”]
Indexing is fully asynchronous, and does no work in the main thread. I do most of my testing using the chromium project (>100k files), and observe no slowdowns.[/quote]

Is there any way to debug issue that cause editor to lag even when typing the text? I want to find solution for this because it’s really annoying.
This happening only on this huge project - all others smaller projects works great.

0 Likes

#67

I have some suggestions for default Preferences.sublime-settings.

Line 267

    // OS X 10.7 only: Set to true to disable Lion style full screen support.

Now that Sublime Text 3 only supports OS X 10.7 and later, this should be like this.

    // OS X only: Set to true to disable Lion style full screen support.

Line 271 to 275

    // OS X only. Valid values are true, false, and "auto". Auto will enable
    // the setting when running on a screen 2880 pixels or wider (i.e., a
    // Retina display). When this setting is enabled, OpenGL is used to
    // accelerate drawing. Sublime Text must be restarted for changes to take
    // effect.

The threshold of screen width should be 2560, not 2880, because the screen resolution of MacBook Pro 13-inch Retina is 2560 by 1600.

0 Likes

#68

>>> import urllib.request Traceback (most recent call last): File "<string>", line 1, in <module> File "X/urllib/request.py", line 88, in <module> File "X/http/client.py", line 69, in <module> File "X/email/parser.py", line 12, in <module> File "X/email/feedparser.py", line 27, in <module> File "X/email/message.py", line 16, in <module> ImportError: cannot import name utils
Win7 32bit

0 Likes

#69

:astonished:

0 Likes