Sublime Forum

Dev Build 3067

#1

Dev Build 3067 is out now, with a few bits of polish.

Development work on Sublime Text was very quiet in 2014. I don’t intend for that to be the case in 2015.

The next dev build is due out in 2 or 3 weeks. I’m planning on making some changes to the way Build Systems work for that build (see upcoming thread for details), but as a thank you to all the dedicated forum members, I’d like to take some suggestions for what else should go in the next build(s). Please post the feature or two that you’d most like to see, and I’ll see what I can do about it. Features will be loosely ranked by:

(number_of_posts) * (feature_benefit) * (number_of_users_who_will_use_feature) * (1/implementation_time)

Where number_of_posts is your post count on the forum, and feature_benefit is arbitrarily assigned by me, unless you can convince me otherwise :slight_smile:

1 Like

#2

Also, just a heads up if you’re using OSX: subl, the command line tool, has changed the way it talks to the application in this build. The old version of subl won’t be compatible, so ensure you haven’t copied the binary outside of the bundle, and only symlinked it, or otherwise included it in the PATH.

0 Likes

#3

Thanks for the update! Good to see you’re still alive :smile:

Just take a look at posts with many pages (random order out of my memory):

  • printing support;
  • undo/redo jumping bug;
  • a clear and unique way to submit bugs/features/whatever. Sure, it’s nice to have feedback on forum, github, mail, userecho and smoke signals, but I’m not sure it’s the right thing to do…
  • open source the default packages;
  • upgrade the forum software (I, for once, like the Discourse platform);
  • save issues on windows in some situations;
0 Likes

#4

I intend to, but in the short term I’d specifically like to work on the items that would make the core forum members the happiest.

0 Likes

#5

Ditch the damn phpBB! NOW! :mrgreen:

0 Likes

#6

[quote=“jps”]Dev Build 3067 is out now, with a few bits of polish.

Development work on Sublime Text was very quiet in 2014. I don’t intend for that to be the case in 2015.

The next dev build is due out in 2 or 3 weeks. I’m planning on making some changes to the way Build Systems work for that build (see upcoming thread for details), but as a thank you to all the dedicated forum members, I’d like to take some suggestions for what else should go in the next build(s). Please post the feature or two that you’d most like to see, and I’ll see what I can do about it. Features will be loosely ranked by:

(number_of_posts) * (feature_benefit) * (number_of_users_who_will_use_feature) * (1/implementation_time)

Where number_of_posts is your post count on the forum, and feature_benefit is arbitrarily assigned by me, unless you can convince me otherwise :smile:[/quote]

Sublime program told me there is an update so I visit here but I couldn’t see the release note for 3067 and the download link. The latest is 3066. Didn’t you posted yet?

0 Likes

#7

Hit reload in your browser and it’ll show up.

0 Likes

#8

Please address some annoying bugs at first. E.g. file lock issues on Windows: github.com/SublimeTextIssues/Core/issues/143

And then these features:

Plus:

  • platform aware user settings, e.g. User/Preferences (Windows).sublime-settings
0 Likes

#9

Not something very popular, but quick (I think) to implement and really useful when needed.

Hope it’s not a new year resolution that end quickly like most of them :wink:

0 Likes

#10

Unfortunately the update for this build requires elevated privileges on windows (this was never the case before for the updates on my portable installation). For portable installs, can you please remove the need for administrator permissions?

0 Likes

#11

Oh man,
Finally, I’ve been so worried that sublime text was dead.
Such a relief.

Can’t wait for new features and stuff.

0 Likes

#12

It’s really good to hear from you Jon.

  • Printing support, with full syntax highlighting.
  • Improved gutter support so that, as an example, you can use Git Status and Gutter Color plugins at the same time. Or, provide a built in VCS system to show changed files.
  • Sidebar work. Symbolic link icons can’t be changed (as I remember?). Allow us to dynamically modify rows - goes back to VS again.
  • Tooltip API. This is a big one from me. It’d give us the ability to show inline image previews, color pickers, tips on code style etc.
  • Switch from phpBB, Discourse is good. It’ll really help us with communication. Hopefully stop spam too.
  • Build in Sublime Package Control if wbond is up for that. It’d reduce a lot friction for new users looking to install plugins.
  • Show the project name (like the sidebar) in the window, not just the root folder.
  • API for graphical views. There is only so much one can do with the quick panel and views.
  • Split the default packages into GitHub so we, as a community can keep them up to date. I for one would help support the PHP, MySQL, CSS packages etc :smile:
0 Likes

#13

For some reason, ST crashing for me since updating.

Not sure if is a package or not, I’ll update when I’ll be sure.

0 Likes

BracketHighlighter
#14

Something that I’d like to have fixed:

  • Start ST
  • Open file aaa.py (ST applies the Python syntax def)
  • Close ST
  • Delete the Python.tmLanguage file
  • Start ST

(This is better done with a syntax def that isn’t part of the stock packages; Python is simply an example here.)

Now you will get a modal error dialog warning you that the Python.tmLanguage file does not exist. If you have 20 or 200 Python files open, you will see as many error dialogs.

This is very annoying when you’re developing a package and botch the syntax file name, etc. Perhaps an error could be printed to the console instead.

0 Likes

#15

[quote=“iamntz”]

Ditch the damn phpBB! NOW! :mrgreen:[/quote]

Add mail notification!

(phpBB is good for what it’s worth; Discourse would make subforums harder to find IMO. Don’t switch! - Or, maybe, to MyBB?)

0 Likes

#16

As a small forum owner (based on discourse) I have to disagree, mostly because you don’t have subforums per se, but categories. The only downside (only at first; after couple of weeks of content you will see that’s really a feature!) is that you can’t have more than two levels of deepness (so you have cat1 > cat2 and that’s all, you can’t have cat1 > cat2 > catN).

Sure, initial impact of users used to classic forums (phpbb, vbulletin etc) will be huge, because nothing is like they are used to. But after couple of days, it’s just… they way is supposed to be.

Also, upgrading to a newer version (of either forum or plugins) is a breeze: couple of clicks and a minute later and you are on the latest version.

0 Likes

#17

Hi JS! Great to see you’re back :smile:

As for new features I would like to vote for extending “Jump to definition” to support
C/C++/Objective C languages. This is something I greatly miss in my everyday work.

P.S. Please, do not start off topics here. There are suitable places
on this forum for discussions on forum engines and other issues not
related to the thread subject.

Best Regards,
Wojtek

0 Likes

#18

Precisely. This is a support forum with a lot of different general topics. Don’t make it too flat.

0 Likes

#19

Good to see an update!

  • Splitting the default packages out and open source them will be a big win
  • Please give some love to the vintage package, fix some bugs, merge some PRs, I love this.
  • Multi gutter icon…
  • More APIs :smile:
0 Likes

#20

I have no idea if you ever look at the sublime’s forum: 5 subforums (categories) and that’s all. No downside on using Discourse here :smile:

0 Likes