Many of new Sublime Text users (and me) are coming from Notepad++ folks. It's a reflex to click on an item with icon under "Open" item. To preserve this reflex, Sublime Text should include an icon on it's context menu item.

Here's some how-to's to do this manually:

• http://www.jetmore.org/john/blog/2012/05/adding-an-icon-to-the-edit-with-sublime-text-2-contextual-menu-item/
  
• http://sublimetext.userecho.com/topic/43345-windows-context-menu-right-click-edit-with-sublime-notepad-style/#comment_172190
  
• http://www.sublimetext.com/forum/viewtopic.php?t=3159&f=4#p15311
  

I found sublime text 3 beta is supporting ubuntu package.

I think it can support rpm package too.

because rpm package also popular in desktop linux and enterprise linux

The "overlay_scroll_bars" setting in Sublime is not true to the OS X system preference value 'When scrolling', when using an external mouse on a Mac laptop. With values 'system' or 'enabled', the scrollbars will show as overlayed when scrolling with the touchpad on the laptop, however if scrolling with an external mouse (I use a Logitech), the scroll bars do not show. With this mouse I can only get the scrollbars to show when setting the value to 'disabled' or using the OS system preference values 'Automatically based on mouse or trackpad' or 'Always'.

The behaviour to show the scrollbars when scrolling with an external mouse on OS setting 'When scrolling' works as it should in other apps. It would be great to get this working as it should in Sublime!

Sometimes it would be useful to "fork" the file while editing. For example when you work on a file and you would like to check, i.e. two ways of implementation of some functionality. What you usually do is implementation of first version, then you comment it and implement second version (i.e. to compare speed or something else). This is the situation when file "forking" would be useful. How it should work? Its easy:

1. You open the file (let's name it A)
2. You fork the file (some keyboard shortcut maybe) - you get A1 file. Technically this is the second file buffer (copy) with its own view pointing to the same location on HDD
4. Now you can work on two versions of the same file simultaneously. When you save changes in A, this file will be written to HDD under its original location. When you save A1, the file will overwrite A, but not change anything in view to A (and vice-versa).

And what about version stored on HDD? Simply it is the latest you saved.

Please note that this is NOT file cloning, which is now implemented in Sublime. The main difference is that when you clone the file, each change is propagated between clone and original file. Forked file will not propagate the changes between each other.