From: Eli Zaretskii <eliz@gnu.org>
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:58:53 +0200 [thread overview]
Message-ID: <83pqhrsipe.fsf@gnu.org> (raw)
In-Reply-To: <CAKV0tLOHBQ6B2=c1qz91zmhX8cREN66juaeEgQKqP8EfAVqZ1g@mail.gmail.com>
> Date: Thu, 20 Oct 2011 10:44:31 -0600
> From: Bob Nnamtrop <bobnnamtrop@gmail.com>
> Cc: 9810@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?
next prev parent reply other threads:[~2011-10-20 16:58 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
2011-10-20 16:58 ` Eli Zaretskii [this message]
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=83pqhrsipe.fsf@gnu.org \
--to=eliz@gnu.org \
--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).