E121 : Undefined variable: paste#paste_cmd on Vim 8.1 1-436 second launch

[Ni Va]

Hi,

I use this last built version of Vim.

VIM - Vi IMproved 8.1 (2018 May 18, compiled Sep 26 2018 13:46:15)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-436
Compiled by ni.va
Huge version with GUI.

Under Windows Seven 64 bits, on second launch of this Vim (deployed as standalone dir) from ~\AppData\Local\Temp, I encounter this warning :

Error detected while processing ~\AppData\Local\Temp\
Vim_x86\vim81\menu.vim:

line 163:
E121: Undefined variable: paste#paste_cmd
E15: Invalid expression: 'vnoremenu <script> &Edit.&Paste<Tab>"+gP^I' .
paste#paste_cmd['v']

When I test the same launching Vim from ~/desktop

Thank you for help

[Ken Takata]

Hi Ni,

I know you're creating your own Vim distribution. I suspect whether this is an
issue of your distribution.

Please let us know the following things, anytime when you report an issue:

* A step-by-step reproducible way with a minimal settings.
Using `vim --clean` is preferred.
Just saying "on second launch" is unclear.
* What you see, and what you expect.
(This time, this might be enough.)
* Which version of Vim (or gVim) and which version of OS are you using?
(This time, this might be enough.)
* Does the same thing happen with the official binary from www.vim.org or
the nightly builds from vim-win32-installer?

Regards,
Ken Takata

[Tony Mechelynck]

It looks to me like a case of out-of-date runtime files (but I could
be mistaken). Please check the last change dates of the following as
displayed near the top of each file (I'm listing the dates I see
there):

$VIMRUNTIME/menu.vim 2018 May 17
$VIMRUNTIME/autoload/paste.vim 2017 Aug 30

paste#paste_cmd should be a Dictionary with keys 'n' 'v' and 'i' each
corresponding to a String. Line 163 of menu.vim is here too the first
line where it is referenced.

Note that it is NOT recommended to source the vimrc in an already
running instance of Vim. The recommended way to make Vim take note of
a modified vimrc is to shut Vim down properly then restart it.


Best regards,
Tony.