Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Jan 3, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

arp242 and others added 30 commits March 24, 2020 15:33
* Check the last line of output from go version

This makes `gopher.vim` work in my particular environment, where `go` is a shell wrapper and is outputting extra text before printing the version. Instead of expecting the entirety of `go version` output to contain the version information, this instead uses only the last line.

* Refactor 'version_check' to return the error message and expect that the 'go version' may be in the middle of the 'go version' output

* Fix the tests

They failed because \n isn't expanded in single quotes

* Revert echoerr

This was initially changed, because I was not seeing the error messages, but this should be addressed separately, if actually needed.

* Remove accidentally committed file, and fix lint warning

Co-authored-by: Martin Tournoij <[email protected]>
Should give greater guarantee people actually see this; see #34
Rather obscure edge case, but might as well fix it.

Also set compiler to "go" for go.mod.
The previous implementation was correct (AFAIK) and IMHO better, because
method names didn't get highlighted:

  fun (t T) delete() { }
  fun (t T) int() { }

But it's also very complex, and slow. I started getting noticable
slow-downs, which is a shame becase I spent quite some time optimising
the rest of the syntax.

So ... probably not worth it.
…nabled

I'm not sure why I always applied the folding pattern (it's been a few
years since I wrote it), but I can't find any good reason for it, and as
far as I can see it works well. Maybe some other change affected this?
Or maybe I was just stupid...

It's rather slow for larger files; and actually runs out of memory in
gtk.go in mattn/go-gtk.
* Add :GoFrob fill

* Found another bug

* Fix stuff

* Remove fillswitch as it doesn't work with modules

* Update docs

* Fix bugs
(before/after)

    TOTAL      COUNT  MATCH   SLOWEST     AVERAGE   NAME               PATTERN

    0.043582   4117   100     0.000077    0.000011  goSingleDecl       \v(^\s*)@<=(import|var|const) [^(]
    0.004676   3619   100     0.000037    0.000001  goSingleDecl       \v^\s*\zs%(import|var|const)\ze [^(]
e.g.:

  var m = map[int]string{
        LevelInfo: "X",
  }

LevelInfo would get highlighted wrong
vim-dispatch parses every compiler and looks for strings
roughly matching: CompilerSet makeprg=<program>
It mentions in its help that simply making a comment
with such a string will also work. That's what I've done here.
Better capture for slightly changed 1.14 test -v output.
Otherwise it would apply outside of structs
Can't really get this right...
…ispatch

Make the compilers compatible with vim-dispatch.
* Allow *no* auto-download of tools (default is to auto-download)
* Allow to install tools in the default $GOBIN (default is to install
  tools in <plugin>/tools/bin
* Create command that forces download of all tools
@arp242 arp242 deleted the branch aignas:master June 26, 2025 14:58
@arp242 arp242 deleted the master branch June 26, 2025 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants