vim warning: CFPasteboardRef CFPasteboardCreate(CFAllocatorRef, CFStringRef) : failed to create global data

[basmac]

In 10.11.4 macports vim gives the following warning, which is annoying only. Apple version does not give the warning.

g5s1:~ bmcinnes$ vi run_Backup_g5s1
2016-04-29 08:32:32.269 vi[34105:18485399] CFPasteboardRef CFPasteboardCreate(CFAllocatorRef, CFStringRef) : failed to create global data
2016-04-29 08:32:32.274 vi[34105:18485399] CFPasteboardRef CFPasteboardCreate(CFAllocatorRef, CFStringRef) : failed to create global data
g5s1:~ bmcinnes$ /usr/bin/vi run_Backup_g5s1
g5s1:~ bmcinnes$ which vi
/opt/local/bin/vi
g5s1:~ bmcinnes$

[raimue (Rainer Müller)]

I do not have OS X 10.11 El Capitan to test this. Google has lots of hits for this message, many not related to vim. Also, the vim source code does not have any mention of a CFPasteboardCreate symbol, I only found references to NSPasteboard.

Are you logged in graphically or via SSH?

I best advice would be to try a reboot or logout/login to restart the pboard service.

[basmac]

I have tried restarts, reinstall of OS, to no avail. I am in iTerm2, ssh with or without -Y to another mac, all macs 10.11.4
With macports vi I get the warning, Apple vi no warnings.
Maybe its a macports ssh/vim issue.
Thanks for looking at the issue - its not urgent, just for macports information.
You can close it if you want to ?

[francwalter@…]

OH! I am happy to find this bugreport! I have this annoying warning too and didnt find the reason for long. The Macports Vim version is the problem! Now I know. On my MacBook with 10.11.5 the warning comes as user root and despite of any reboot since long. I asked in a forum about it: ​http://www.macuser.de/threads/el-capitan-fehlermeldung-nach-beenden-von-vim.736866/page-2 but never got a solution, didn't know that was vim-specific. And indeed, use I the /usr/bin/vim Mac-Version (not macports) the warning comes not. Will move to this then. It is 7.3 instead of the Macports 7.4, won't be that difference :)

[raimue (Rainer Müller)]

I cannot reproduce any such message with the current vim @8.0.0596 on macOS 10.12 Sierra. I tested both locally and over SSH. I have to assume this was fixed somehow or only affects OS X 10.11.