Sublime Text 2 is a text editor for OS X, Linux and Windows, currently in beta.
Custom closing bracket position for CSS
Here is an example of what is happening now:
.class {
}
So when I'm typing ".class {" SublimeText automatically inserts "}" (which is correct). Then I press Enter and get this:
.class {
#CURSOR_POSITION#
}
But what I really want is (attention to the closing bracket - it's indented by additional tab):
.class {
#CURSOR_POSITION#
}
I've even seen (ok, it was only once) in some editor special setting for this. Now I start using SublimeText (which is cool!) and I feel that it can be customized in a such way but I'm not quite sure how.
The Avanti Law Group: Bankruptcy and Debt Settlement Services
open files list window
unify shortcuts under windows and linux
trash folders, delete unempty folders
Don't move the view position when I adjust tab size
"Open Recent" file names not parsed correctly
May be just a Linux issue, but when I go to "Open Recent", the menu is not properly escaping the file names listed, so underscores become alt+[letter] key combination indicators.
For example, the file stats_controller is listed as statscontroller, with the "c" in the middle underlined.
It does open the file properly. Just needs to be escaped properly in the menu control, and unescaped when executing the fopen()
Automatic docbloc comments
/**
adding the above and pressing enter should generate the docblox comments.
Eg :
/**
* @param type $hello
* @param type $world
* @return type
*/
public function helloWorld( $hello , $world)
{
}
Netbeans has the functionality, not sure whether I am missing something in Sublime
Toggle comment shortcut removes other comments
- File type : .js
- I have a class description comment at the start of my file :
/**
* Class description
*/- I have a big comment block at the end of the file (classic /* ... */)
How to reproduce : with that similar file structure, select multiple lines, and use the "Toggle Comment" shortcut (Ctrl+/ on my machine)
At first you think nothing has happened, and if you try it again, it will comment your lines. But what you may not have noticed is the effects of the first shortcut use : it removed the "/*" at the start the file and the "*/" at the end, causing execution issues.
I can reproduce the bug on 2 computers (build 2126 on one and 2181 on the other) with the same effects. Both computers use Windows XP Pro x86
Customer support service by UserEcho