Sublime Text 3 port? #22
Comments
|
I just opened up #23 to resolve this. |
vishr
pushed a commit
that referenced
this issue
May 29, 2016
Fixed #22, fixed #30, fixed #39, fixed #40, fixed #50, fixed #52, fixed #53, fixed #55, fixed #56, fixed #58, fixed #59. * Rename Context.sublime-menu to menus/Context.sublime-menu * Update Context.sublime-menu * Rename Main.sublime-menu to menus/Main.sublime-menu * Update Main.sublime-menu * Rename Default.sublime-commands to commands/Default.sublime-commands * Update Default.sublime-commands * Update and rename LocalHistory.sublime-settings to settings/Local History.sublime-settings * Update package-metadata.json * Update and rename history.py to Local History.py * Delete package-metadata.json * Update README.md * Update Main.sublime-menu * Add files via upload * Create context-menu.png * Delete context-menu.png * Delete tools-menu.png * Create .gitkeep * Add files via upload * Delete .gitkeep * Update README.md * Update README.md * Update README.md * Update README.md * Update Local History.sublime-settings * Update Local History.sublime-settings * Update README.md * Update and rename Local History.py to LocalHistory.py * Rename Local History.sublime-settings to LocalHistory.sublime-settings * fix path target for read-only settings * Update Main.sublime-menu * add seperator for visuals to menu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there any way this could be ported to ST3? Running 2to3 on it only made one small change to a
print()command, but it still threw up an error in Sublime itself.The text was updated successfully, but these errors were encountered: