Using a Vim that is built to be able to access X's PRIMARY and CLIPBOARD
selections (i.e., "* and "+), performing “:let &term=&term” causes Vim
to "forget" that it knows how to access those registers.
This is because set_termname() ends up calling clip_init(), which sets
owned = FALSE on both VimClipboard instances.
I'm not sure why changing &term should be modifying the state of the
clipboard at all, so the attached patch removes that bit of the code,
resolving the bug.
Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/term.c b/src/term.c
--- a/src/term.c
+++ b/src/term.c
@@ -1865,14 +1865,6 @@ set_termname(term)
p = (char_u *)"";
# ifdef FEAT_MOUSE_XTERM
-# ifdef FEAT_CLIPBOARD
-# ifdef FEAT_GUI
- if (!gui.in_use)
-# endif
-# ifndef FEAT_CYGWIN_WIN32_CLIPBOARD
- clip_init(FALSE);
-# endif
-# endif
if (use_xterm_like_mouse(term))
{
if (use_xterm_mouse())
