E353: Nothing in register " on startup.

[lindhobe]

In VIM 8.0.1213, I get the following error message any time I launch vim in an SSH session after middle-click pasting into that session.

E353: Nothing in register "

Additionally, the last character on the first line of whatever I'm editing is changed to the character 2. This didn't happen on VIM 8.0.1188, which was my previous build. Typing :reg reveals the following spurious registry entry:

". 2

I cannot figure out how to clear it. Details of my build are below:

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct 23 2017 08:33:05)
Included patches: 1-1213
Compiled by brian@machine12
Huge version without GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_old_static
+arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           +mouse_urxvt     -tcl
-balloon_eval    +folding         +mouse_xterm     +termguicolors
-browse          -footer          +multi_byte      +terminal
++builtin_terms  +fork()          +multi_lang      +terminfo
+byte_offset     -gettext         -mzscheme        +termresponse
+channel         -hangul_input    -netbeans_intg   +textobjects
+cindent         +iconv           +num64           +timers
-clientserver    +insert_expand   +packages        +title
-clipboard       +job             +path_extra      -toolbar
+cmdline_compl   +jumplist        -perl            +user_commands
+cmdline_hist    +keymap          +persistent_undo +vertsplit
+cmdline_info    +lambda          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       -python          +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             +rightleft       +windows
+diff            +menu            -ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
+emacs_tags      -mouseshape      +startuptime     -xpm
+eval            +mouse_dec       +statusline      -xsmp
+ex_extra        -mouse_gpm       -sun_workshop    -xterm_clipboard
+extra_search    -mouse_jsbterm   +syntax          -xterm_save
+farsi           +mouse_netterm   +tag_binary
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O3 -flto -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -O3 -flto -L/usr/local/lib -s -Wl,--as-needed -o vi        -lm -ltinfo -lnsl  -ldl

[chrisbra]

can you bisect the offending commit?

[lindhobe]

Well, that was my first git-bisect ever. I ran through it twice with different starting points to confirm:

65e4c4f6868882a380c319632a1728a5e7d274ad is the first bad commit
commit 65e4c4f6868882a380c319632a1728a5e7d274ad
Author: Bram Moolenaar <Bram@vim.org>
Date:   Sat Oct 14 23:24:25 2017 +0200

    patch 8.0.1194: actual fg and bg colors of terminal are unknown
    
    Problem:    Actual fg and bg colors of terminal are unknown.
    Solution:   Add t_RF.  Store response to t_RB and t_RF, use for terminal.

:040000 040000 2117979d82ccfcf982165802e256de837a5aeb35 a1afee90ce92e42a4c7e5416ece48ae419004ce3 M      runtime
:040000 040000 54fa07fa1e5cd5cdcc90e0eed0b3c38950bf67a6 b6625f40882e67b74fbe32d9c455a9f8191a6d03 M      src

Looking at the 8.0.1194 commit, I'll be darned if I can figure out why it's causing problems. Anyway, I'm going to revert to 8.0.1193 on my computer for the meantime.

[k-takata]

It looks like a termresponse problem and might be solved by #2126.
What does :echo v:termresponse show?
What terminal emulator are you using and which version?

[lindhobe]

I'm running XTerm 330. Environment variable TERM is "xterm". When I run ":echo v:termresponse" under either vim-8.0.1193 or vim-8.0.1213, I get the following:

[>41;330;0c

[lindhobe]

I'm deleting my previous comment about the bug being triggered by an if &t_Co > 2 || has("gui_running"), as it was erroneous. The bug still happens even after I've removed this line from my .vimrc. It doesn't happen consistently, and I got faked out by a few successful runs. My apologies for temporarily posting bad data.

[lindhobe]

Hmmm... Disabling terminal emulation seems to clear things up. However, I've discovered that adding --disable-terminal to the ./configure line doesn't actually disable the terminal emulator. That probably should be reported as a separate bug.

[pavlix]

I'm seeing the same issue. Vim just pastes random stuff from a previous session when started. But not always, just sometimes. I'm seeing this on latest openSUSE Tumbleweed.

vim-8.0.1428-2.1.x86_64

[pavlix]

Note: In my case on openSUSE Tumbleweed uninstalling the gvim package seems to help. Reinstalling it makes the issue show up again. There definitely seems to be a correlation in my case. Note that installing/uninstalling gvim alter the /etc/alternatives setting.

[k-takata]

I don't know which version of vim is used after you uninstall gvim, but I think that the termresponse feature is disabled on that version, because the problem is caused by the termresponse feature.
As I wrote in the previous comment, this should be fixed by #2126, but it is not merged yet.

[lacygoill]

For those of you who can reproduce, can you check whether 8.2.0936 helped in any way?

[tonymec]

<MiddleMouse> is supposed to read from register *, not register ". However, this may misfire if you have 'clipboard' set to autoselect and/or the a flag in 'guioptions' because if that is set, Vim will try to write its own register " into register *.

I often get Nothing in register + when putting from the clipboard. Usually trying again (i.e. just repeating the "+p "+P or :put + operation without touching the other application) gives the desired result.

Best regards,
Tony.