Mercurial > vim
comparison src/eval.c @ 19085:fd1070ff696b v8.2.0103
patch 8.2.0103: using null object with execute() has strange effects
Commit: https://github.com/vim/vim/commit/e2a8f0773e91685843c062b1e48259712d5f2213
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Jan 8 19:32:18 2020 +0100
patch 8.2.0103: using null object with execute() has strange effects
Problem: Using null object with execute() has strange effects.
Solution: Give an error message ofr Job and Channel.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Wed, 08 Jan 2020 19:45:04 +0100 |
parents | 3b1f83fdaabc |
children | e3848b251a01 |
comparison
equal
deleted
inserted
replaced
19084:cd25e7f54344 | 19085:fd1070ff696b |
---|---|
5665 return buf; | 5665 return buf; |
5666 } | 5666 } |
5667 #endif | 5667 #endif |
5668 break; | 5668 break; |
5669 case VAR_UNKNOWN: | 5669 case VAR_UNKNOWN: |
5670 emsg(_("E908: using an invalid value as a String")); | 5670 emsg(_(e_inval_string)); |
5671 break; | 5671 break; |
5672 } | 5672 } |
5673 return NULL; | 5673 return NULL; |
5674 } | 5674 } |
5675 | 5675 |