unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 18:25:17 +0200	[thread overview]
Message-ID: <CANbX367DjfhyvpzDEEhXknNmWWxRAmpCcX9UoszYAgV4Gyff1A@mail.gmail.com> (raw)
In-Reply-To: <CAKV0tLOmAnB6no92Ci7bQBYvR5C7AnzXsmeKFjdwV66Tag4PQA@mail.gmail.com>

On Thu, Oct 20, 2011 at 18:18, Bob Nnamtrop <bobnnamtrop@gmail.com> wrote:
> As the title says, in viper command mode typing cw (ie change word)
> causes the emacs clipboard (not sure the proper name for it, but the
> thing I expect a middle mouse button to paste into the buffer) to get
> clobbered. This is a regression over all previous versions (actually I
> remember this bug occurring a long time ago and getting fixed so
> something must have broken it again). To replicate:
>
> emacs -Q
> M-x viper
> i (ie, go into insert mode)
> asdf hjkl (type a few words)
> <escape> (ie, go into command mode)
> click on the 'a' (or move there any way you want)
> double click to put 'asdf' into emacs clipboard (ie X11 clipboard,
> primary, whatever)
> click on the 'h' (or move there any way you want)
> cw (ie viper command to change word)j
> <middle mouse click> (to paste the clipboard, or yank or whatever
> emacs calls it :-)
> hjkl is pasted in
>
> But 'asdf' should have been pasted in. This also occurs with other
> commands like 'ct', etc. This is very annoying and I cannot imagine
> using the new version if this is not fixed.

I think the current behavior is the correct one. Why do you think it
is in error?





  reply	other threads:[~2011-10-20 16:25 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 [this message]
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
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=CANbX367DjfhyvpzDEEhXknNmWWxRAmpCcX9UoszYAgV4Gyff1A@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).