James McCoy wrote:
> 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.
Well, setting the 'term' option sort of means a reset of the terminal.
Why would you set the 'term' option while something is selected?
--
DENNIS: Look, strange women lying on their backs in ponds handing out
swords ... that's no basis for a system of government. Supreme
executive power derives from a mandate from the masses, not from some
farcical aquatic ceremony.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
