Skip to content

Conversation

@agriffis
Copy link
Contributor

Four problems that were preventing the vroom tests from running on
neovim:

Four problems that were preventing the vroom tests from running on
neovim:

- The vroom version was too old, see
  google/vroom#104

- The maktaba version was too old, see
  google/vim-maktaba#172. I considered
  constraining this to neovim but it applies to recent vim as well (the
  version of vim in travis/xenial is quite old) and the extra version
  checking seems pointless.

- The get-pip.py invocation was outdated.

- For some reason neovim pauses more often with "Hit ENTER" messages.
  Perhaps newer vim would too. In any case, increasing the cmdheight
  solves the problem without needing to sprinkle :silent everywhere.
Copy link
Contributor

@dbarnett dbarnett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

The neovim issue is google/vroom#83; they suggested a workaround of always sending ENTER when it might happen, but no good solution atm. Setting cmdheight is a nice trick, and might work on some of the others that were stuck.

@dbarnett dbarnett merged commit 7556c68 into google:master Jan 1, 2020
@agriffis agriffis deleted the fix/travis-vroom-neovim branch January 1, 2020 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants