Your message dated Thu, 18 Jun 2009 01:01:36 -0400
with message-id <[email protected]>
has caused the report #531372,
regarding vim-gtk: misuses X cut buffer
to be marked as having been forwarded to the upstream software
author(s) Bram Moolenaar <[email protected]>
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
[patch] Use latin1 when manipulating CUT_BUFFER0
Thu, 18 Jun 2009 01:01:36 -0400
As described below (and confirmed in the ICCCM documentation), Vim
isn't correctly handling reading from/storing to CUT_BUFFER0. The
attached patch adapts the portions of Vim which manipulate CUT_BUFFER0
to convert text to latin1 before storing to and convert from latin when
reading from the cut buffer.
 - http://tronche.com/gui/x/icccm/sec-3.html#s-3
 - http://tronche.com/gui/x/icccm/sec-2.html#s-2.6.2
On Sun, May 31, 2009 at 11:10:21PM -0500, Jonathan Nieder wrote:
> 1. Open gvim and type some non-ASCII text such as "Ãtale".
> 2. Yank it (with just "yy", into the default register).
> 3. Exit.
> 4. Paste into a uxterm.
> xterm treats the text as Latin-1, and the word ÃÂtale appears. Similarly:
> 1. Open uxterm, type some non-ASCII text such as "Ãtale".
> 2. Select it with the mouse.
> 3. Unselect it.
> 4. Paste into gvim (with shift-insert or button-2).
> gvim treats the text as malformed UTF-8, and the text <e9>tale is
> inserted. On the other hand, text can be pasted from gvim to gvim
> without problems.
> This puzzled me (which program is right?) until I read the xterm
> manpage, which informs me
> But cut-buffers handle only ISO-8859-1 data (officially - some
> clients ignore the rules).
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]>
Description: Text Data
--- End Message ---