On 18-Aug-2010 raf <r...@raf.org> wrote: > for me (from the original report), vim definitely looks > like the culprit. i'm using macosx-10.6.4, motif (from > macports) and the X11 that comes with macosx (and a recent > version of xquartz-2.5.2) and twm. given that fixed setup, > vim-7.3 can't copy/paste but vim-7.2.446 can. > > i'm just having another look at the behaviour which seems to > be: on starting gvim, you can copy from other windows and > paste into gvim's window multiple times. however, as soon as > you select any text in the gvim window it no longer sees any > text selections that have happened in other windows, nor do > other windows see any selections that have been made in > gvim. so as soon as you select text in gvim, it becomes > isolated from the system's primary selection and just > operates with its own local one. > > so it looks like this behaviour applies to linux and macosx > and to gtk, athena and motif but it obviously can't be > happening for everyone or it would never have survived this far. > > i hope this helps someone find the cause of the problem. > > cheers, > raf
OK, so for me pasting into Gvim is broken by the changeset which has the message "Fixes for time in clipboard request. Also fix ownership. (David Fries)". (Sorry for no changeset ID - I'm using a git clone of the Vim Mercurial repo, which gives me different commit IDs). What might be worth mentioning is even once using the primary selection becomes broken, it is still possible to read the clipboard. However, reading the clipboard takes awfully long - I tried pasting 3 lines, 100 bytes of text into Gvim and it took about 3 seconds to complete. -- Cheers, Lech -- 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
