Development of margo & GoSublime is funded by oyato cloud
and generous supporters on Open Collective and Patreon.

Migrating to GoSublime's development branch
Updated 2018/09/30 16:00

See /b/hello-margo for a short introduction to margo

See /b/motd for details about being notified when GoSublime has a new release.

If you use a Package Control version of GoSublime, we encourage you to switch to the development branch:

These instructions assume that you're inside the Sublime Text Packages directory.
  • Read the extension example and make sure you understand its contents. File an issue if you have any concerns.
  • Uninstall GoSublime
  • Run the command git clone to install GoSublime from the development branch.
  • Restart Sublime Text. The status bar should instruct you to press ctrl+.,ctrl+x or cmd+.,cmd+x which creates the margo extension file. Please read all comments in the file.
    If you've already switched to the new margo implementation, it might help to check the extension example for changes as there are some API breakages.

What else changed?

In addition to the new gocode implementation, these are a few more improvements:

  • You can write your own extensions in Go
  • Gocode calltips now show argument markers
  • You can write your own commands and execute them through the 9o command line or a command palette
  • Linting works
  • You can hook into all events that margo uses and update things like the status bar

What's the catch?

The down-side is that most GoSublime settings no longer work due to being replaced by similar features in the new implementation of margo.

There is also a lack of polish due to time constraints. File an issue if there are any problems.

The majour broken settings are listed in the extension example, with the // gs: comments.

Other updates