gopls: move known issues higher

Rebecca Stambler 2019-06-18 13:09:07 -04:00
parent 26d967ab58
commit 61a8bb1e17

@ -6,8 +6,8 @@ For folks with questions about integrating gopls within an editor, see https://g
# Table of Contents # Table of Contents
[Status](#status) [Status](#status)
[Troubleshooting](#troubleshooting) [Troubleshooting](#troubleshooting)
[Installation](#installation)
[Known Issues](#known-issues) [Known Issues](#known-issues)
[Installation](#installation)
[Contributing](#contributing) [Contributing](#contributing)
[FAQ](#faq) [FAQ](#faq)
[Additional Information](#additional-information) [Additional Information](#additional-information)
@ -28,6 +28,13 @@ You can then try to restart your `gopls` instance by restarting your editor, whi
Feel free to ask questions about `gopls` on the `#gopls` [Gopher Slack](https://invite.slack.golangbridge.org) channel. Feel free to ask questions about `gopls` on the `#gopls` [Gopher Slack](https://invite.slack.golangbridge.org) channel.
## Known Issues
* Cursor resets to the beginning or end of file on format: [#31937](https://github.com/golang/go/issues/31937).
* Editing multiple modules in one editor window: https://github.com/golang/go/issues/32394.
* "no room in queue" error: [#32467](https://github.com/golang/go/issues/32467).
* File contents reverted after saving: [#32643](https://github.com/golang/go/issues/32643).
## Installation ## Installation
First, install `gopls` by running `go get -u golang.org/x/tools/cmd/gopls`. First, install `gopls` by running `go get -u golang.org/x/tools/cmd/gopls`.
@ -206,12 +213,6 @@ After doing the above, you might want to take a look at the LSP package's settin
--- ---
## Known Issues
* Cursor resets to the beginning or end of file on format: [#31937](https://github.com/golang/go/issues/31937).
* "no room in queue" error: [#32467](https://github.com/golang/go/issues/32467).
* file contents reverted after saving: [#32643](https://github.com/golang/go/issues/32643).
## Contributing ## Contributing
Contributions are welcome, but since development is so active, we request that you file an issue and claim it before starting to work on something. Otherwise, it is likely that we might already be working on a fix for your issue. Contributions are welcome, but since development is so active, we request that you file an issue and claim it before starting to work on something. Otherwise, it is likely that we might already be working on a fix for your issue.