1
0
mirror of https://github.com/golang/go synced 2024-10-01 03:38:32 -06:00
go/gopls
Ainar Garipov 1ccc110ba9 gopls/doc/vim.md: enable suppress_stderr for natebosch/vim-lsc
By default, github.com/natebosch/vim-lsc shows messages from stderr in
vim's :messages, which may cause problems and is generally annoying.
Suggest disabling that by setting suppress_stderr to v:true.

Change-Id: If997b8f8fd036a1ac08ba74a3886f33ff71413c2
Reviewed-on: https://go-review.googlesource.com/c/tools/+/194137
Reviewed-by: Ian Cottrell <iancottrell@google.com>
2019-09-16 02:06:55 +00:00
..
doc gopls/doc/vim.md: enable suppress_stderr for natebosch/vim-lsc 2019-09-16 02:06:55 +00:00
go.mod internal/lsp: update go.mod for next version 2019-09-11 23:05:05 +00:00
go.sum internal/lsp: update gopls mod file 2019-09-11 19:57:40 +00:00
main.go internal/lsp: have tests report a different application name to the main gopls binary 2019-07-18 23:01:26 +00:00
README.md cmd/gopls: add documentation 2019-08-27 15:23:08 +00:00

gopls documentation

gopls (pronounced: "go please") is the official language server for the Go language.

It is currently in alpha, so it is not stable. You can see more information about the status of gopls and its supported features here.

In general you should not need to know anything about gopls, it should be integrated into your editor for you.

See the installing section of the user guide if you need to install or update gopls by hand.

Issues

If you are having issues with gopls, please first check the known issues before following the troubleshooting guide. If that does not give you the information you need, reach out to us.

You can chat with us on:

If you think you have an issue that needs fixing, or a feature suggestion, then please make sure you follow the steps to file an issue with the right information to allow us to address it.

If you need to talk to us directly (for instance to file an issue with confidential information in it) you can reach out directly to @stamblerre or @ianthehat.

More information

If you want to know more about it, have an unusual use case, or want to contribute, please read the following documents