Saluton Benjamin & Bram :) First of all, sorry for the delay, but I've been busy as heck.
Second: Bram, looks like Chrome is putting HTML in the Desktop clipboard, but not in the X clipboard, see the message below, Benjamin has done an excellent research work. Benjamin R. Haskell <[email protected]> skribis: >> Perhaps Chrome puts HTML in the selection? > > Running Google Chrome 6.0.437.1 (Official Build 49781) VIM - Vi > IMproved 7.2 (2008 Aug 9, compiled Aug 22 2010 15:00:27) Included > patches: 1-442 > > Chrome does put HTML in the selection. But, not in the one that's > broken. > > I found this Chromium bug-report related to a clipboard problem: > http://code.google.com/p/chromium/issues/detail?id=34813 > > The actual problem doesn't look relevant, but there's a useful > clipboard/selection examining tool in one of the comments: > http://code.google.com/p/chromium/issues/detail?id=34813#c9 > Downloaded: gtk_clipboard_dump.cc Compiled: g++ $(pkg-config --cflags > --libs gtk+-2.0) -o ~/bin/gtk_clipboard_dump > ~/Download/gtk_clipboard_dump.cc > > Copying the David Gómez sample text in Chrome, and running > gtk_clipboard_dump yields: Mmm, revealing... I'm going to do the same with another browser so we can find what's the problem. Last resort will be gdbing Vim. Thanks A LOT for your help, for posting the code for the test tool and for all the information. Now I have a base to work. > [format: COMPOUND_TEXT / length: 12 / bits 8]: David Gómez > [format: STRING / length: 12 / bits 8]: David Gómez > [format: TEXT / length: 12 / bits 8]: David Gómez > [format: UTF8_STRING / length: 12 / bits 8]: David Gómez All those "length: 12" make me think they're all encoded with UTF-8 and not in latin1 (where length would be 11). > [format: text/plain / length: 12 / bits 8]: David Gómez Even this is encoded with UTF8 (I think...) > X clipboard [...] > [format: COMPOUND_TEXT / length: 11 / bits 8]: David Gómez > [format: TEXT / length: 11 / bits 8]: David Gómez > [format: STRING / length: 11 / bits 8]: David Gómez But these are encoded in latin1, and probably are the ones that Vim is using. If so, the problem is in Chrome, not in Vim. > Hope that's helpful, A lot, Ben, at least to me. Let's see if Bram sees something here that may be causing the problem. Otherwise I'll report the bug to the Chrome people. I think that Chrome uses GTK, and if so, it should be using GTK clipboard primitives. In that case, I'm afraid the problem may lie in the GTK libraries, but that's weird since no other GTK program shows the same behaviour :? -- Raúl "DervishD" Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net The revolution will not be televised -- 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
