Improve the discoverability of Sublime's manifold functionality. Some ideas:
* Optional tips-on-startup dialog (with "don't show next time" checkbox); especially useful for new users of the demo version
* Add a mechanism like `apropos` to search for commands/keybinds that may do what you want. Having a short plain-English description with each command would improve search discoverability. Descriptions would need to be associateable with both commands and specific keybinds. Add a help menu item labeled "I want to..." to open the apropos prompt.
* Add a mechanism for the user to get context-sensitive help for any keyboard command or menu item. Wire it up to a wiki to let the community help build up these docs.
* Add a help menu item "Keyboard shortcuts" which generates a human readable list of the current keybindings in a new buffer. This list could sort the binds by keystroke and include the short `apropos` description for each keybind.
* Require installed packages to provide apropos-style descriptions of all their commands and key bindings.
* Allow package creators to include a help file with their package. Make these help files accessible through a new help menu item "Package Help >".
hi please add RTL (right to left) languages support to sublime text , RTL languages like arabic and hebrew and maybe other languages , sublime text should detect the current language changed in the OS like windows 7 and give support for it ...
I'm aware that .sublime-project files can contain settings but it doesn't appear I can do what I want with them.Some plugins require per-project settings, at present as far as I can tell this is not possible without resorting to creating and using your own settings file somewhere inside the project path.
- For settings within the .sublime-project file to overwrite settings from a plugin's settings file, when applicable.
- For the API to provide a way to obtain these project-specific settings, which also seems to be impossible at present. Bare in mind that the .sublime-project file may not necessarily be stored within the project path and so we can't just manually walk the project path to search for it.
This post explains the problem well. Hash tags like "end" and "class" in the new 1.9 Hash literal format are hightlighted incorrectly. The post contains a fix that works perfectly, namely to edits the Ruby language file by moving the block of code at lines 201-208 to line 1570.
In emacs multiple open panes and views are always editing the same buffer so edits are automatically propagated across the views. It would be really nice if Sublime text behaved in this way.
Customer support service by UserEcho