Skip to content

v8.2.1352

Compare
Choose a tag to compare
@chrisbra chrisbra released this 01 Aug 22:08

Github Downloads (by Release)
Nightly Vim Windows build snapshots (more information).

If you do not know what to use, use the 32bit installer (use the signed one, if available).

Signed releases will occasionally be provided on a best effort approach.

Note: Due to the expiration of the old certificate, a new certificate to sign the binaries has
been created and will be used starting with the next release after April 14th, 2020.
This may cause a SmartScreen warning by Windows because the certificate is new. Hopefully this
warning will vanish, once the certificate has been used more widely.
If you want to avoid this warning, you can use the latest release with the old certificate
v8.2.577.

Changes:

  • 8.2.1352: Vim9: no error for shadowing a script-local function
  • 8.2.1351: Vim9: no proper error if using namespace for nested function
  • 8.2.1350: Vim9: no test for error message when redefining function
  • 8.2.1349: Vim9: can define a function with the name of an import
  • 8.2.1348: build failure without the eval feature
  • 8.2.1347: cannot easily get the script ID
  • 8.2.1346: small build fails
  • 8.2.1345: Redraw error when using visual block and scroll
  • 8.2.1344: Vim9: No test for trying to redefine global function
  • 8.2.1343: Vim9: cannot find global function when using g:
  • 8.2.1342: Vim9: accidentally using "t" gives a confusing error
  • 8.2.1341: build failures
  • 8.2.1340: some tests fail on Cirrus CI and/or with FreeBSD
  • 8.2.1339: Vim9: assigning to global dict variable doesn't work
  • 8.2.1338: Vim9: assigning to script-local variable doesn't check type
  • 8.2.1337: Vim9: cannot use empty key in dict assignment
  • 8.2.1336: build failure on non-Unix systems
  • 8.2.1335: CTRL-C in the GUI doesn't interrupt
  • 8.2.1334: Github workflow timeout needs tuning
  • 8.2.1333: Vim9: memory leak when using nested global function

Files:

🔓 Unsigned Files:

Interface Informations

See the README for detail.