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

Previous Next

Package: emacs;

Reported by: Bob Nnamtrop <bobnnamtrop <at> gmail.com>

Date: Thu, 20 Oct 2011 16:20:02 UTC

Severity: normal

Done: Chong Yidong <cyd <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #53 received at 9810 <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Bob Nnamtrop <bobnnamtrop <at> gmail.com>
Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, 9810 <at> debbugs.gnu.org
Subject: Re: bug#9810: cw in viper mode clobbers clipboard
Date: Thu, 20 Oct 2011 23:03:34 +0200
On Thu, Oct 20, 2011 at 22:57, Bob Nnamtrop <bobnnamtrop <at> gmail.com> wrote:
> On Thu, Oct 20, 2011 at 12:46 PM, Stefan Monnier
> <monnier <at> iro.umontreal.ca> wrote:
>>> Right after you type 'cw' nothing in the buffer is erased. The word is
>>> hi-lighted but that is it. So it should not change any selection at
>>
>> That's what is supposed to happen now that select-active-regions
>> defaults to t.
>
> Playing around a bit more exposes more inconsistencies:
>
> -using the viper command R (viper-overwrite) hi-lights to the end of
> the line in a similar way as cw does to the end of the word but the
> primary selection is not clobbered. This is inconsistent to the
> behavior of cw (although better).

They actually work quite different. If you press ESC immediately after
R then nothing is changed in the buffer. However if you press escape
after cw then the word is still deleted.

So with respect to clipboard handling I think both are consistent and ok.

But maybe they do not behave the way vi does in this cases. (But that
is a totally different matter than this bug report.)




This bug report was last modified 13 years and 293 days ago.

Previous Next


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