Sublime Text 2 is a text editor for OS X, Linux and Windows, currently in beta.
No similar topics found.
+4
Keep fullscreen between sessions
Most of the time I like to use ST2 in fullscreen.
It's a pain to make it fullscreen every time I restart the application.
Full screen state should be kept between sessions.
Or at least an option to set fullscreen to default.
+4
Select command - Display a dialogue containing all commands (like the select files or projects one)
It would be great to have a command with keybinding that would open a dialogue - like the select project/file one - that listed all the commands. Allowing you to search and filter them. Also if it could display the key bindings that would be awesome.
+4
fine-grained auto_match_enabled behavior?
so, it would be really awesome if we could have a bit more fine-grained control over what gets auto_match-ed. so, for instance, in lisp i dont want to have to delete the automatically-appearing ' when i type in some data. but i dont want to turn off auto_match completely (especially in lisp, with all thoes parens all around.... i'm just learning it so it's kind of scary :P )
thanks!!
+4
Better word-left/right movement on OS X
The usual behavior of word-left/right movement on OS X is to skip groups of word-separating characters. For example, using | to indicate caret position, word-left from "foo-bar-|baz" is "foo-|bar-baz", just as word-left from "foo bar |baz" is "foo |bar baz". In Sublime Text 2, on the other hand, word-left from "foo-bar-|baz" is "foo-bar|-baz".
Having the default word-movement and selection behavior in ST differ from the rest of my system is really confusing. (Compare to Mail, Safari, TextMate, Xcode.)
+4
Under Windows, middle clicking Sublime Text 2 doesn't open a new window
Under Windows Vista and 7, you can middle-click an application's taskbar button to start a new instance or open a new window. For example, middle-clicking Firefox's button will open a second Firefox window with your homepage loaded in a tab. Sublime Text 2 doesn't honor this and instead performs no action. Instead, it should open a new window with no files open.
+4
trim trailing whitespace as sublime command
I wanted to be able to trim trailing whitespace on my file by opening the Command Palette and just typing it in. I was about to write my own plugin, when I noticed that the "trim_trailing_white_space_on_save" option was implemented in the Default plugin -- so I just modified that! I've put together a patch file which you can download at http://www.davidbaumgold.com/files/trim-trailing-whitespace.patch (or view at http://paste.pocoo.org/show/580870/).
The patch adds a text command to run "Trim Trailing Whitespace" from the command palette, and it operates either on the whole file, or on just the part that you have selected.
+4
stdin not supported
ST2 does not support the stdin,for python language,the 'input()' can not be excable with a EOF error.
addition, python debug is not being supported.
wish a improvement !
+4
Smarter, Context-Sensitive Auto-Bracket Insertion
I write a *lot* of JavaScript. Mostly in MooTools, but even jQuery and "vanilla" writers would benefit from the following, I think:
If I type out the following (the | is my cursor):
window.addEvent ('domready', function () {|
Sublime will somewhat dumbly do the following when I press return:
window.addEvent ('domready', function () {
|
}
Now, I'm grateful that it's trying, but in cases like this, it's actually more of a nuisance. What I would love for it to do, instead:
window.addEvent ('domready', function () {
|
});
Yeah. Getting shivers? How awesome would that be? It would add the semi-colon and the closing round bracket. It could even be super smart and put an invisible insertion marker between the } and ) in the event this function has more arguments, and I could just tab past it to the right of the semi-colon if it didn't.
There is another instance in which the current auto-bracket closing is frustrating:
var App = new Class ({
'initialize': function (options) {|
'method': function () {
// some stuff here
}
});
Pressing return with my insertion point where it is above would yield:
var App = new Class ({
'initialize': function (options) {
|
} // <-- SYNTAX ERROR HERE
'method': function () {
// some stuff here
}
});
See the syntax error? It would have to place a comma after the automatically-inserted bracket. Now, that's probably asking a lot, but even if it added the comma EVERY time in this context, it'd be a lot easier for developers to remove the superfluous comma than to continually go in and add one every. single. time.
I think that about covers my most frequently-encountered quirks with the bracket-closing magic of Sublime. I am 100% oblivious to the complexity of implementing such improvements, but I do feel like Sublime, which is scopes and such, is probably in the best position of all editors to make it happen.
Thank you for reading!
- Aaron Wright
+4
The autocomplete menu should open above the cursor, not below, if the window lacks enough space to show the menu.
When I use the autocomplete menu near the end of a file (as I often do when writing new code), the menu opens "off screen" -- below the cursor. There isn't enough space to see the menu, and I can't scroll down any farther in the file.
OS 10.7, build 2190.
+4
Tab close button is easily accidentally clicked
This is going to sound weird, but I'm constantly accidentally clicking the close button on files, especially when I have many tabs open.
In the below image you can see that the close button, even though visually is small, actually takes up half of the tab space.
I believe that I usually aim for the middle of the tab, which could explain why I accidentally click the close button.
This is how I believe the hit zone should actually be:
I'm using Beta Build 2162.
In the below image you can see that the close button, even though visually is small, actually takes up half of the tab space.
I believe that I usually aim for the middle of the tab, which could explain why I accidentally click the close button.
This is how I believe the hit zone should actually be:
I'm using Beta Build 2162.
Customer support service by UserEcho
