From: Eli Zaretskii <eliz@gnu.org>
To: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: 27530@debbugs.gnu.org
Subject: bug#27530: patch to cut and copy secondary
Date: Tue, 05 Sep 2017 18:08:30 +0300 [thread overview]
Message-ID: <8360cx2nf5.fsf@gnu.org> (raw)
In-Reply-To: <20170905.121104.688310267504171014.tkk@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Tue, 05 Sep 2017 12:11:04 +0900 (JST))
> Date: Tue, 05 Sep 2017 12:11:04 +0900 (JST)
> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
> Cc: tkk@misasa.okayama-u.ac.jp
>
> I found the secondary selection is very useful. I sent a patch on
> June 2017 and Drew inferred importance of commands to utilize the
> secondary selection.
>
> > IMO, the first, and simplest, improvement to add to Emacs is
> > a way to create and yank the secondary selection using only
> > the keyboard, not the mouse. My guess is that the reason
> > more users do not use the secondary selection is that there
> > are no keyboard keybindings for it.
>
> I found that the exchange of primary and secondary can be implemented
> into C-x C-x as `mouse-exchange-point-and-mark-secondary'.
>
> (global-set-key [remap exchange-point-and-mark] 'mouse-exchange-point-and-mark-secondary)
Hmm... In Emacs 24, we have changed how selection works to conform
with other modern X applications, by having primary selection set only
via mouse gestures, whereas keyboard commands work with the clipboard.
Doesn't your proposal go in the opposite direction?
IOW, what is the logic of having keyboard commands set selections,
when all the rest of the X world does the exact opposite? Or did the
trend got reversed yet again?
In any case, a command whose name starts with "mouse-" should have the
"e" interactive spec, and should react to mouse gestures, not to
keyboard keys. I also don't like advising users to remap "C-x C-x" to
anything that smells a mouse.
Thanks.
next prev parent reply other threads:[~2017-09-05 15:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 12:43 bug#27530: patch to cut and copy secondary Tak Kunihiro
2017-06-29 13:41 ` Drew Adams
2017-07-01 0:45 ` Tak Kunihiro
2017-08-01 1:35 ` Tak Kunihiro
2017-09-05 3:11 ` Tak Kunihiro
2017-09-05 7:51 ` Robert Pluim
2017-09-05 9:25 ` Tak Kunihiro
2017-09-05 9:32 ` Robert Pluim
2017-09-05 12:22 ` Tak Kunihiro
2017-09-05 13:53 ` Drew Adams
2017-09-05 23:17 ` Tak Kunihiro
2017-09-06 0:29 ` Drew Adams
2017-09-05 15:08 ` Eli Zaretskii [this message]
2017-09-05 23:06 ` Tak Kunihiro
2017-09-06 2:33 ` Eli Zaretskii
2017-09-06 3:42 ` Tak Kunihiro
2017-09-06 16:04 ` Eli Zaretskii
2017-09-07 12:35 ` Tak Kunihiro
2017-09-07 19:11 ` Eli Zaretskii
2017-09-07 23:02 ` Tak Kunihiro
2017-09-08 8:27 ` Eli Zaretskii
2017-09-10 3:01 ` Tak Kunihiro
2017-09-11 2:03 ` Tak Kunihiro
2017-09-20 7:55 ` Eli Zaretskii
2017-09-20 12:39 ` Tak Kunihiro
2017-09-21 8:32 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8360cx2nf5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27530@debbugs.gnu.org \
--cc=tkk@misasa.okayama-u.ac.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.