Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tests: establish known quickfix buffer number in testscripts tests (#613
) Before a test script starts, the files from the txtar archive are extracted. Then govim (and gopls) are started. In some rare cases, gopls can end up calculating diagnostics before the testscript has started. Which means that it can be the case, because govim and Vim are already up and running, that the first buffer actually gets used for quickfix as opposed to, say, the first file we open. Instead below we copen then cclose in vimrc to reserve and establish a definite buffer number for the quickfix window. The quickfix buffer will always be buffer number 2 (because vim creates a buffer when opening, a buffer that is then used for the first file we open). Update various tests to reflect this change.
- Loading branch information
Showing
5 changed files
with
31 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters