mattn / mattn/vim-lsp-settings
Go file gets mangled in conjunction with vim-go
Nobody has claimed this yet.
- Dominant language
- Vim Script
- Stars
- 1.4k
- Forks
- 245
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
Starting with 19aef037e198fa5694b98a052f23e285bf113550, when used alongside vim-go, my files get extra package lines prepended, but only when it's the first file specified on the command line:
Similarly, on a new file, I see this:
I previously opened fatih/vim-go#3734, but I closed that when I determined it was vim-lsp-settings, the one thing I didn't look closely at before.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with vim-go using a Go file as the first command-line argument, including a new file, and compare that behavior with later file arguments. Inspect the change introduced by commit 19aef037e198fa5694b98a052f23e285bf113550 and the vim-lsp-settings configuration involved; done means files no longer receive extra package lines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, vim
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100