Skip to content

Instantly share code, notes, and snippets.

@suntong
Last active December 15, 2019 03:45
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save suntong/8aa8507099edecaab1937e79ceff923b to your computer and use it in GitHub Desktop.
Save suntong/8aa8507099edecaab1937e79ceff923b to your computer and use it in GitHub Desktop.

Install LiteIDE

  • Download http://sourceforge.net/projects/liteide/files
  • Unzip to a directory of your choice and make a shortcut to ./liteide/bin/liteide.exe
  • Recommended to add ./liteide/bin to your PATH
  • Recommended settings in View | Options:
    • LiteApp
      • Display
        • Toolbar Icon Size: 18x18
    • LiteEditor
      • Behavior
        • Clean whitespace when saving files
    • LiteDebug
      • Rebuild before debugging
    • GolangFmt
      • Use goimports instead of gofmt, for code formatting
      • Automatically format code when saving

Useful LiteIDE Keyboard Shortcuts

Shortcut Action
Ctrl+B Build
Ctrl+T Test
Ctrl+R Run
Ctrl+W Close Window
Ctrl+Shift+J Jump to definition
Ctrl+Shift+K Delete line
Ctrl+Shift+U Find usages
Ctrl+Shift+I Show signature / doc when cursor on function
Ctrl+U Select block
Ctrl+L Go to line number
Ctrl+[,Ctrl+] Go to Previous / Next block
Ctrl+E Go to matching brace
Ctrl+Shift+R Refactor name

Add project to LiteIDE

  • File | Add folder
  • Select the folder
  • Expand the folder and double click main.go
  • Try to build the project using Ctrl+B

Setup LiteIDE Dark Theme

  • LiteApp
    • Generic
      • Theme: black.qss
  • LiteOutput
    • Display
      • Font Family: Hack
      • Font Size: 10
      • Check "Use editor color scheme"
  • LiteEditor
    • Font & Colors
      • Font Family: Hack
      • Editor Color Scheme: cobalt black.xml

Tips

  • LiteIDE can get confused when it comes to intellisense on vendored packages. Try copying the contents of the repo's ./vendor to %GOPATH%/src.
  • You probably don't want to step-through debug as much as you would in Visual Studio.
  • Stop execute with the red square next at the top of "Build Output".
  • Some general Go tips.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment