On Wed, Oct 1, 2014 at 2:47 PM, Christian Brabandt <cblists@256bit.org> wrote:
I'm not noticing clipboard corruption upon startup. In fact, other than explicit access of the "* register (for all operations, yanks, changes, deletes, pastes, etc.), the system clipboard doesn't enter into it.
On a whim, I cycled through all the values of 'clipboard', including empty, but nothing makes a difference.
Thank you, all!
Salman
-- 7.4.445 did fix a bug, that the clipboard was cleared when starting Vim.On Mi, 01 Okt 2014, Gary Johnson wrote:
> On 2014-10-01, Christian Brabandt wrote:
> > On Mi, 01 Okt 2014, Gary Johnson wrote:
> >
> I'm running 7.4.430 at work. I was previously running 7.4.389. I
> haven't had time this morning to do any testing of this. If you
> think these problems were fixed by patch 445, I can update my build
> to the latest and see what happens. Is there any value in my
> testing 7.4.430 first?
This was caused by an error in the original 7.4.396 patch (which fixes
the problem that accessing the clipboard could hang Vim when using batch
operations). But IIRC, once Vim started, the clipboard worked
(well, I couldn't test on Windows).
Best,
Christian
I'm not noticing clipboard corruption upon startup. In fact, other than explicit access of the "* register (for all operations, yanks, changes, deletes, pastes, etc.), the system clipboard doesn't enter into it.
On a whim, I cycled through all the values of 'clipboard', including empty, but nothing makes a difference.
Thank you, all!
Salman
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment