On 03/05/11 11:35, guns wrote:
[...]
With regards to email in your mail client, I suspect that most people
receive email that is not politely hard-wrapped at 72 characters, and
possibly the response therein is even top-posted for convenience. If
this does not describe your mail, then I am quite
On Thu, May 5, 2011 at 7:25 AM, Bram Moolenaar b...@moolenaar.net wrote:
I would rather use the linewise selection only when the text ends in a
line break. I think in most situations the user can select the text
either with or without a terminating NL. At least in xterm you can.
I'm happy to
On 2011-05-03, Sung Pae wrote:
Gary, would you mind running your tests again with this patch? Yanking
multi-line selections from Firefox should be just fine, since it no
longer just looks at the last character to determine the motion type.
Sung Pae,
Thanks for the new patch. I reverted your
Upon closer inspection, I have the following observations about vim's
handling of foreign selections.
When pasting from the * or + register, vim requests a selection
from the system clipboard. If the selection is not in a vim
selection format:
- The mac, macosx, msdos, mswin, and qnx ports
On 03/05/11 09:59, Sung Pae wrote:
Upon closer inspection, I have the following observations about vim's
handling of foreign selections.
When pasting from the * or + register, vim requests a selection
from the system clipboard. If the selection is not in a vim
selection format:
- The
Well, what if I yank (in Firefox, say, or in Thunderbird) a multiline sentence
from the middle of a paragraph? As in the example below, I mean? With this
newfangled system, I won't be able to insert it in the middle of a different
paragraph in Vim, except by calling setreg('+', '', 'ac') to force
On May 3, 3:42 am, Tony Mechelynck antoine.mechely...@gmail.com
wrote:
Well, what if I yank (in Firefox, say, or in Thunderbird) a multiline
sentence from the middle of a paragraph? As in the example below, I
mean? With this newfangled system, I won't be able to insert it in the
middle of a
On Tue, May 3, 2011 at 3:58 AM, Ben Schmidt:
This perhaps allows the best of both worlds (once the people who, like
me, prefer characterwise clipboard pasting, put together some mappings
to do it that way).
I'd like to mention that there is another way to resolve this issue:
Instead of
On 2011-04-30, Sung Pae wrote:
On Sat, Apr 30, 2011 at 12:37 PM, Gary Johnson wrote:
Copying and pasting seems to be working fine now. 嚥�I don't
understand what problem this patch is supposed to fix. 嚥�If I knew
what to look for, I would apply and test it.
Some clarification then:
Hi Gary,
Thank you very much for testing the patch. Here is what I have found:
Test 1
* Start Firefox (3.5.3).
* Go to vim.sf.net.
* Triple-click the Vim 7.3 release announcement.
I can confirm that triple-clicking on a line in Firefox 4 on my Arch
Linux box does not
On 2011-05-02, Sung Pae wrote:
Hi Gary,
Thank you very much for testing the patch. Here is what I have found:
[...]
I will delve into this more deeply and try compiling with different
feature levels before re-submitting; I have a good idea about what is
the matter. I hope you will be
Sung Pae wrote:
Currently, when `putting' from the * and + registers, the register is
always pasted as MCHAR if it has been returned from the X clipboard.
However, vim convention implies that any string that ends in a \n or \r
should be expected to be behave like a linewise yank (see
On 2011-04-30, Bram Moolenaar wrote:
Sung Pae wrote:
Currently, when `putting' from the * and + registers, the register is
always pasted as MCHAR if it has been returned from the X clipboard.
However, vim convention implies that any string that ends in a \n or \r
should be expected
Gary Johnson wrote:
On 2011-04-30, Bram Moolenaar wrote:
Sung Pae wrote:
Currently, when `putting' from the * and + registers, the register is
always pasted as MCHAR if it has been returned from the X clipboard.
However, vim convention implies that any string that ends in a \n or \r
On Sat, Apr 30, 2011 at 12:37 PM, Gary Johnson garyj...@spocom.com
wrote:
Copying and pasting seems to be working fine now.  I don't
understand what problem this patch is supposed to fix.  If I knew
what to look for, I would apply and test it.
Some clarification then:
On a vim compiled
On 2011-04-30, Sung Pae wrote:
On Sat, Apr 30, 2011 at 12:37 PM, Gary Johnson wrote:
Copying and pasting seems to be working fine now. 嚥�I don't
understand what problem this patch is supposed to fix. 嚥�If I knew
what to look for, I would apply and test it.
Some clarification then:
On Sat, Apr 30, 2011 at 3:44 PM, Gary Johnson garyj...@spocom.com wrote:
Thank you for the thorough explanation. I won't be able to apply or
test your patch until Monday or Tuesday, but I'll do so then and let
you know how it works out.
I have a Windows XP machine at my desk and use
Hello,
Currently, when `putting' from the * and + registers, the register is
always pasted as MCHAR if it has been returned from the X clipboard.
However, vim convention implies that any string that ends in a \n or \r
should be expected to be behave like a linewise yank (see MAUTO).
Since it is
18 matches
Mail list logo
