Sublime Text 2 is a text editor for OS X, Linux and Windows, currently in beta.
No similar topics found.
+3
"open all with current extension as..." doesn't seem to work
The "open all with current extension as..." feature in the bottom-right menu doesn't seem to work: whatever I choose, the checkbox remains on the filetype predefined by Sublime.
I wanted to use this to change .cgi association from Ruby to Perl.
I'm using the latest 2126 build, but this also happened with 2111 (I wasn't using the excellent Sublime Text before that).
I wanted to use this to change .cgi association from Ruby to Perl.
I'm using the latest 2126 build, but this also happened with 2111 (I wasn't using the excellent Sublime Text before that).
+3
Selected file in file list should always correspond to current file
For example, when the current tab is changed, the selected file in the file list should change to highlight that file if visible, or deselect if not. Having the file selected implies it is the current file and can be confusing.
+3
Mac sidebar highlight needs to be more mac like
The highlighted file in the sidebar needs to look more osx like. The highlighted color needs to be darker and the text needs to be white like so: http://screencast.com/t/xXhnwDrh
+3
Call plugin_unloaded when Sublime Text 3 exits or quits
Plugins need to cleanup things, but Sublime Text 3 exits/quits without calling the plugin_unloaded() function. It's unclear in the api docs whether plugin_unloaded() was meant to be called when Sublime exits. If this is not a bug, is there another way for plugins to cleanup when Sublime Text 3 exits?
+3
Open files on second mouse _up_ instead of mouse _down_
When double clicking a file (in windows at least) it opens on the second mousedown event instead of the second mouseup event. This causes the file view to be moved down before the opening action is completed.
+3
Equivalent of mate_wait for subl
Sublime Text 2 can be invoked from the command line with `subl` and there is an option `-w` which enables it to wait until the file is closed and then return it so that ST2 can be used as an editor for command line executables that call upon an `$EDITOR`.
However, setting `EDITOR` to `path/to/subl -w` doesn't work for some commands like `crontab` that expect the editor to be just a path to an executable.
TextMate solved this by allowing you to create an alias to `mate` with the suffix `_wait`, e.g. `mate_wait` which would be executed as if the `-w` option had been used.
It would be great if Sublime Text 2 could also add this valuable feature.
+3
An option to quit Sublime automatically when the last document is closed
I wish Sublime for Mac has an option to quit itself automatically when the last document is closed.
+3
merge sublime settings recursively
Sublime settings files are consulted in a certain order , and files loaded later may overwrite values in files loaded earlier. That way, they may override values and change settings.
When trying PythonTestST3, I tried to change the 'python_test.command' setting in my syntax specific settings, whereas the 'python_test.working_dir' key should be changed in the project settings.
Doing it that way will leave me with settings that only contain the 'python_test.command' key, but not the 'python_test.working_dir' key, as the settings files are apparently not merged recursively, but only for the top-level key.
A recursive algorithm would allow people to layer configurations, and keep values on the level where they belong.
In that particular case, it would be practical to define 'python_test.command' on a per-user or per-machine level, whereas all other configuration could be coming with the project settings, which are shared by everyone.
When trying PythonTestST3, I tried to change the 'python_test.command' setting in my syntax specific settings, whereas the 'python_test.working_dir' key should be changed in the project settings.
Doing it that way will leave me with settings that only contain the 'python_test.command' key, but not the 'python_test.working_dir' key, as the settings files are apparently not merged recursively, but only for the top-level key.
A recursive algorithm would allow people to layer configurations, and keep values on the level where they belong.
In that particular case, it would be practical to define 'python_test.command' on a per-user or per-machine level, whereas all other configuration could be coming with the project settings, which are shared by everyone.
+3
highlight arbitrary lines
I would like to be able to highlight arbitrary lines of text, especially when working on plain text that is not subject to any sort of syntax highlighting.
Customer support service by UserEcho
