1
0
mirror of https://github.com/golang/go synced 2024-09-30 14:18:32 -06:00
go/gopls
Rob Findley 30fd94b347 internal/lsp/lsprpc: expose configuration for auto-started daemon
Three new flags are added to the serve command, and threaded through to
the LSP forwarder:
 -remote.listen.timeout: -listen.timeout for the auto-started daemon
 -remote.debug: -debug for the auto-started daemon
 -remote.logfile: -logfile for the auto-started daemon

As part of this change, no longer enable debugging the daemon by
default.

Notably none of this configuration affects serving, so modifying this
configuration has been chosen not to change the path to the automatic
daemon. In other words, this configuration has effect only for the
forwarder process that starts the daemon: all others will connect to the
daemon and inherit whatever configuration it had at startup. This should
be OK, because in the common case this configuration should be static
across all clients (e.g., many Vim sessions all sharing the same
.vimrc).

Exposing this configuration made the signature of lsprpc.NewForwarder
a bit hard to understand, so I decided to go ahead and switch to a
variadic options pattern for initializing both the Forwarder and
StreamServer, the latter just for consistency with the Forwarder.

Updates golang/go#34111

Change-Id: Iefb71e337befe08b23e451477d19fd57e69f36c6
Reviewed-on: https://go-review.googlesource.com/c/tools/+/222670
Run-TryBot: Robert Findley <rfindley@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
Reviewed-by: Heschi Kreinick <heschi@google.com>
2020-03-12 19:43:16 +00:00
..
doc internal/lsp: support textDocument/formatting for .mod extension 2020-03-06 13:51:27 +00:00
integration gopls/integration/govim: update to go1.14 images 2020-03-09 17:26:05 +00:00
internal/hooks internal/lsp: remove nilness analyzer 2020-02-12 21:32:43 +00:00
test internal/lsp/lsprpc: expose configuration for auto-started daemon 2020-03-12 19:43:16 +00:00
go.mod gopls: update staticcheck to 2020.1.3 2020-02-25 18:52:58 +00:00
go.sum all: upgrade outdated dependencies 2020-03-03 20:20:40 +00:00
main.go gopls: add the link to the gopls/README.md 2020-02-03 22:28:49 +00:00
README.md fix: using section links to IDE specific doc 2019-12-17 14:12:49 +00:00

gopls documentation

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

Status

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.

Roadmap

The current goal is a fully stable build with the existing feature set, aiming for the first half of 2020, with release candidates earlier in the year.

This will be the first build that we recommend people use, and will be tagged as the 1.0 version. You can see the set of things being worked on in the 1.0 milestone, in general we are focused on stability, specifically, making sure we have a reliable service that produces an experience in module mode that is not a retrograde step from the old tools in GOPATH mode.

There is also considerable effort being put into testing in order to make sure that we both have a stable service and also that we do not regress after launch.

While we may continue to accept contributions for new features, they may be turned off behind a configuration flag if they are not yet stable. See the gopls unplanned milestone for deprioritized features.

This is just a milestone for gopls itself. We work with editor integrators to make sure they can use the latest builds of gopls, and will help them use the 1.0 version as soon as it is ready, but that does not imply anything about the stability, supported features or version of the plugins.

Using

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

To install for your specific editor you can follow the following instructions

See the user guide for more information, including the how to install gopls by hand if you need.

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