From: Lennart Borgman <lennart.borgman@gmail.com>
To: Bob Nnamtrop <bobnnamtrop@gmail.com>
Cc: 9810@debbugs.gnu.org
Subject: bug#9810: cw in viper mode clobbers clipboard
Date: Thu, 20 Oct 2011 23:03:34 +0200 [thread overview]
Message-ID: <CANbX366Z3kDq5uCFZVAuwcSELF=vS4x=eozUu0Uw088kbsmHFA@mail.gmail.com> (raw)
In-Reply-To: <CAKV0tLOX5MmxJkpaPhHTm=x0z6m1wLQrbbp=6MoCbr7jyLwtaw@mail.gmail.com>
On Thu, Oct 20, 2011 at 22:57, Bob Nnamtrop <bobnnamtrop@gmail.com> wrote:
> On Thu, Oct 20, 2011 at 12:46 PM, Stefan Monnier
> <monnier@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.)
next prev parent reply other threads:[~2011-10-20 21:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 16:18 bug#9810: cw in viper mode clobbers clipboard Bob Nnamtrop
2011-10-20 16:25 ` Lennart Borgman
2011-10-20 16:44 ` Bob Nnamtrop
2011-10-20 16:48 ` Lennart Borgman
2011-10-20 16:57 ` Bob Nnamtrop
2011-10-20 18:46 ` Stefan Monnier
2011-10-20 20:28 ` Bob Nnamtrop
2011-10-20 20:32 ` Lennart Borgman
2011-10-20 21:31 ` Stefan Monnier
2011-10-20 22:12 ` Bob Nnamtrop
2011-10-20 22:38 ` Bob Nnamtrop
2011-10-21 3:06 ` Stefan Monnier
2011-10-21 3:05 ` Stefan Monnier
2011-10-29 5:37 ` Chong Yidong
2011-10-29 15:26 ` Bob Nnamtrop
2011-10-30 3:39 ` Chong Yidong
2011-10-20 20:57 ` Bob Nnamtrop
2011-10-20 21:03 ` Lennart Borgman [this message]
2011-10-20 16:58 ` Eli Zaretskii
2011-10-20 17:12 ` Bob Nnamtrop
2011-10-20 16:27 ` Eli Zaretskii
2011-10-20 16:48 ` Bob Nnamtrop
2011-10-20 16:58 ` Lennart Borgman
2011-10-20 17:09 ` Bob Nnamtrop
2011-10-20 17:16 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANbX366Z3kDq5uCFZVAuwcSELF=vS4x=eozUu0Uw088kbsmHFA@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=9810@debbugs.gnu.org \
--cc=bobnnamtrop@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).