Skip to content

Commit

Permalink
vim: Import v8.2.0796
Browse files Browse the repository at this point in the history
* 8.2.0796: MS-Windows: compiler can't handle C99 construct in libvterm
* 8.2.0795: libvterm code lags behind the upstream version
* 8.2.0794: libvterm code lags behind the upstream version
* 8.2.0793: MS-Windows: cannot build GUI with small features
* 8.2.0792: build failure with small features
* 8.2.0791: a second popup window with terminal causes trouble
* 8.2.0790: Vim9: list index not well tested
* 8.2.0789: Vim9: expression testing lost coverage using constants
  • Loading branch information
chrisbra committed May 18, 2020
1 parent b764f18 commit af9c3a0
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion gitlog.txt
Original file line number Diff line number Diff line change
@@ -1 +1 @@
* [8.2.0788](https://github.com/vim/vim/commit/deb17451edd65e2af1d155bce0886e856a716591): memory leak in libvterm\n* [8.2.0787](https://github.com/vim/vim/commit/a2e408f5981b4da64426c3bda98d837ea36469bf): libvterm code lags behind the upstream version\n* [8.2.0786](https://github.com/vim/vim/commit/0b39ec3c7dd41852fa6f0430b3f963c59d0b50d8): channel test is flaky on FreeBSD\n* [8.2.0785](https://github.com/vim/vim/commit/6fc3b59ee914a0d1710c8b037a0c592e0a7c34d4): libvterm code lags behind the upstream version\n* [8.2.0784](https://github.com/vim/vim/commit/94d729cbe8f0f788d9d7539f733cff395e73b228): libvterm code lags behind the upstream version\n* [8.2.0783](https://github.com/vim/vim/commit/c4c9f7e43e7229c78919a5618003ce8aac3e1785): libvterm code lags behind the upstream version\n* [8.2.0782](https://github.com/vim/vim/commit/df1643a6a7886b9363c2a98438e61cbe1c803d41): cannot build with Lua on MS-Windows\n* [8.2.0781](https://github.com/vim/vim/commit/9309eb2f28e6ee346c2a5deaa6f9c2b36578522e): compiler warning for not using value in Lua\n* [8.2.0780](https://github.com/vim/vim/commit/2d2970ea599e83acabee56be548a54a8e6b21007): libvterm code lags behind the upstream version\n* [8.2.0779](https://github.com/vim/vim/commit/f4e16ae041962555316a6953df30a45f4c45be6a): tmode\_T not used everywhere\n* [8.2.0778](https://github.com/vim/vim/commit/d4a5f40c0cc45fdfac01df0e408d557006eb0206): libvterm code lags behind the upstream version\n* [Update feature\_request.md](https://github.com/vim/vim/commit/ed37d9b3241abe7c302c7ac606df80037aecdb46)\n* [8.2.0777](https://github.com/vim/vim/commit/79ea680e6b1dd02035fdf8a5521927cf1f98c2ed): terminal test fails\n* [8.2.0776](https://github.com/vim/vim/commit/e178ba36546ec7805020280910306331f1ef4ed0): libvterm code lags behind the upstream version\n* [8.2.0775](https://github.com/vim/vim/commit/eb04f0893afe01faff272ef84c70d8cc16d8e80a): not easy to call a Vim function from Lua\n* [8.2.0774](https://github.com/vim/vim/commit/26e86445bf06ab7e7587dfdf75f33f7c70632b46): t\_TI and t\_TE are output when using 'visualbell'
* [8.2.0796](https://github.com/vim/vim/commit/37ebd42f16734838ab68be91da291c4ec8610f47): MS-Windows: compiler can't handle C99 construct in libvterm\n* [8.2.0795](https://github.com/vim/vim/commit/88d68de95da70d0f89a5246f58355d72e9c17db4): libvterm code lags behind the upstream version\n* [8.2.0794](https://github.com/vim/vim/commit/d098b824c10cc20dc55e18c22c4991f61826006e): libvterm code lags behind the upstream version\n* [8.2.0793](https://github.com/vim/vim/commit/1e1d2e89fa460328883bb09fb13a24e26ef1ab31): MS-Windows: cannot build GUI with small features\n* [8.2.0792](https://github.com/vim/vim/commit/c33b3216c8ceac84130d627b20cb7034e5f831e6): build failure with small features\n* [8.2.0791](https://github.com/vim/vim/commit/b5383b174b2436b556f76f14badb1c1f55d6d8f6): a second popup window with terminal causes trouble\n* [8.2.0790](https://github.com/vim/vim/commit/843700875e50c03c94245bef1b2de147b9b3b585): Vim9: list index not well tested\n* [8.2.0789](https://github.com/vim/vim/commit/66b3101672f7da32df2fd3962d7f14300e7a65f3): Vim9: expression testing lost coverage using constants

0 comments on commit af9c3a0

Please sign in to comment.