Thanks. Did you intend for this to also do something with respect to auto indenting in go.mod files?

For example, starting with:

module mod.com

go 1.14

require (_)

(which is typically a position I find myself in because I use auto-pairs) with the cursor at the position _, if I then hit <Enter> I get:

module mod.com

go 1.14

require (

    )

Sure, I can write an indent file. I agree it would be nice to have. Looks like vim-go doesn't have one, though.

@myitcv I wrote a simple indent file for go.mod. I've never written an indent file before but this seems like a pretty basic filetype so hopefully this will cover all the important cases for now. PTAL.

Then if you don't mind squashing the commits and providing a helpful commit message in the mould of previous commits https://github.com/govim/govim/commits/master. Use a prefix of cmd/govim to indicate this relates to the plugin.

Done, though it seems like a strange convention to use cmd/govim to tag changes which are entirely distinct from the cmd/govim code and which do not touch the cmd/govim path.

though it seems like a strange convention to use cmd/govim to tag changes which are entirely distinct from the cmd/govim code and which do not touch the cmd/govim path.

There is some attempt at logic behind this rather strange approach.

github.com/govim/govim is a package in and of itself that should be used by people looking to write Vim plugins in Go.

github.com/govim/govim/cmd/govim is the plugin commonly known as govim.

Using the Go project convention here of using package paths for issue/PR prefixes, because this change relates to github.com/govim/govim/cmd/govim (albeit Vim files that live in parent directories) we use the cmd/govim prefix.

Not ideal when mixing repos like this, but that's the current logic FWIW.

I'm going to merge this once #653 has landed.