Live data from Hacker News

Sublime Text 3 Beta

sublimetext.com

81–90 of 374 posts

Re: Sublime Text 3 Beta

#81

Are these changes really worth the "3.0" tag? Goto to symbol is great, but all other bullet points taste like what I expected 2 to have once it left beta (basically, speed and not letting plugins crash my session). Isn't this a clever way to make users buy into a paid upgrade for a stable version of an editor they already bought?

I'd been wondering about the recent slow pace of updates, but I shouldn't have doubted. I've been consistently delighted by the quality of Sublime and the frequency with which it improves. For the amount of work I do with it and its quality premium over competing tools, at least for the features I value, it feels underpriced (on a US salary).

I'll happily pay for the upgrade if it keeps the author cranking away at a similar pace.

Re: Sublime Text 3 Beta

#82

My pet peeve with editors is how they handle files changing underneath them. I do this regularly enough (eg I might make a quick change using vi, source control update), there could be ssh or sshfs involved, or another tool might be better for doing whatever it is that I wanted. Emacs has been the only editor that has never lost a change for me. Whenever you try to make a modification it checks the underlying file is…

Works fine for me - http://i.imgur.com/mnAA8nw.png

If the fine hasn't been changed in SL2, it just reloads it with a message displayed in the status bar. If it has been edited in SL2, it asks if you want to reload the file.

Re: Sublime Text 3 Beta

#83

Earlier quoted context omitted.

I feel you man. I've been stubbornly sticking to Snow Leopard myself, it works great with my late 2008 MBP.

I'm also holding out for a Mac Pro bump that isn't a pisstake. So I guess I'll bite a few bullets at once.

Don't hold your breath -- I felt the same way about xserve before Apple shocked us with the axing of the server line.

Re: Sublime Text 3 Beta

#84

Earlier quoted context omitted.

Yes, that what's I was describing. It works just fine. When I tab back to Sublime, I get the " has changed on disk. Do you want to reload it?" modal dialog box. (If there are no unsaved changes in the Sublime buffer that could be clobbered, it just reloads the file silently as you'd expect.)

It didn't work when I tried a few weeks ago. I am running on Linux.

My test just now was on Windows, but I use it regularly on Mac and Linux as well, and I'm pretty sure I would have noticed if it silently clobbered changes like that. You're sure you had unsaved changes to the Sublime buffer for the file when you conducted your test?

Re: Sublime Text 3 Beta

#85

Are these changes really worth the "3.0" tag? Goto to symbol is great, but all other bullet points taste like what I expected 2 to have once it left beta (basically, speed and not letting plugins crash my session). Isn't this a clever way to make users buy into a paid upgrade for a stable version of an editor they already bought?

Well considering the large development in terms of plugins and this is currently a BETA, we'll have to wait and see how many new features come out with ST3 to justify the 3 tag. Or it can become a Firefox and have ST18 in a couple of years.... ;-)

Re: Sublime Text 3 Beta

#86

Earlier quoted context omitted.

> I tried SL2 and it quite happily ignored the fact that the file had changed. Weird. I use Sublime Text 2 exclusively across all three platforms. Whenever an open file changes (e.g. I sync to Perforce), it pops up a modal dialog box when I bring that file's tab back into focus. If you're referring to a file that's changed in the background as you're actively editing it, I admit I haven't tried that.

Have an edit window open, and then go in via a terminal/vi and change/save the same file. Then see what happens.

The only problem along these lines I've had with it is in renaming files, where it doesn't appear to be locking onto the inode and the previous-named file still remains in editor and can be saved with the old filename. OOB edits do get reflected back into the editor somehow, though.

Re: Sublime Text 3 Beta

#87
post #83

Earlier quoted context omitted.

I'm also holding out for a Mac Pro bump that isn't a pisstake. So I guess I'll bite a few bullets at once.

Don't hold your breath -- I felt the same way about xserve before Apple shocked us with the axing of the server line.

I am certainly concerned that they might give it the official arse.

The only thing that gives me hope is that the Pro fits a small but important niche in the overall ecosystem: a system better suited for the developers of iOS applications than the iMac is.

Re: Sublime Text 3 Beta

#88

Goto definition and goto symbol? Oh my! Quick test and it works fairly well already. Definitely some enhancements I want (text preview) but I can already tell this will be a glorious upgrade.

I've had a good experience using ctags with ST2. Even on windows.

Can't quite figure out this goto definition thing, though of course I'm trying it using a dynamic language, JavaScript. Was praying he worked some secret SublimeText magic into it :/

Re: Sublime Text 3 Beta

#89

Earlier quoted context omitted.

Have an edit window open, and then go in via a terminal/vi and change/save the same file. Then see what happens.

Yes, that what's I was describing. It works just fine. When I tab back to Sublime, I get the " has changed on disk. Do you want to reload it?" modal dialog box. (If there are no unsaved changes in the Sublime buffer that could be clobbered, it just reloads the file silently as you'd expect.)

Same here (on Mac) - it's always had this behavior for me.

Re: Sublime Text 3 Beta

#90

Are these changes really worth the "3.0" tag? Goto to symbol is great, but all other bullet points taste like what I expected 2 to have once it left beta (basically, speed and not letting plugins crash my session). Isn't this a clever way to make users buy into a paid upgrade for a stable version of an editor they already bought?

>Are these changes really worth the "3.0" tag?

Absolutely.

>Goto to symbol is great, but all other bullet points taste like what I expected 2 to have once it left beta (basically, speed and not letting plugins crash my session).

I bought ST2 without expecting all these features. Taking the effort to add out-of-process plugins? That's more that the TextMate guy has done in all 6 years of dabbling with 2.

On top of that, it has other nice stuff I want. It might be OK calling it 2.5, but it's not a scam by any imaginable stretch of the word.

>Isn't this a clever way to make users buy into a paid upgrade for a stable version of an editor they already bought?

No. Did you find ST2 any less stable than any other editor out there? I use it for a year for working on 3-4 different languages and it never has crashed on me.

So, I appreciate the cynicism but it's misguided here.

Post reply on HN