GNU bug report logs - #9810
cw in viper mode clobbers clipboard

Previous Next

Full log

View this message in rfc822 format

From: Bob Nnamtrop <bobnnamtrop <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: lennart.borgman <at> gmail.com, 9810 <at> debbugs.gnu.org
Subject: bug#9810: cw in viper mode clobbers clipboard
Date: Thu, 20 Oct 2011 11:12:36 -0600

On Thu, Oct 20, 2011 at 10:58 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> Date: Thu, 20 Oct 2011 10:44:31 -0600
>> From: Bob Nnamtrop <bobnnamtrop <at> gmail.com>
>> Cc: 9810 <at> debbugs.gnu.org
>>
>> just typing 'cw' should not cause either clipboard or
>> primary to be altered. The word is highlighted but that should be it,
>> it should not go into primary (or clipboard or any other selection).
>> The way it is now the common (for me) work-flow (put something into
>> primary, go somewhere else, use cw then <middel mouse> to change that
>> word) described above does not work anymore. The changes to primary
>> and clipboard described in NEWS have nothing to do with this (or
>> should not).
>
> Can you tell me which function does the cw command run?
>

Well, I do not really understand the viper code, but some searching
and I found this comment at line 1602 in viper-cmd.el

;; This function is called by various movement commands to execute a
;; destructive command on the region specified by the movement command.  For
;; instance, if the user types cw, then the command viper-forward-word will
;; call viper-execute-com to execute viper-exec-change, which eventually will
;; call viper-change to invoke the replace mode on the region.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.