unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 06 Sep 2017 19:04:41 +0300	[thread overview]
Message-ID: <83o9qn24py.fsf@gnu.org> (raw)
In-Reply-To: <20170906.124252.919138792281853431.tkk@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Wed, 06 Sep 2017 12:42:52 +0900 (JST))

> Date: Wed, 06 Sep 2017 12:42:52 +0900 (JST)
> Cc: 27530@debbugs.gnu.org, tkk@misasa.okayama-u.ac.jp
> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
> 
> >>> 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?
> >>
> >>  I see.  I wonder if the direction lets the secondary selection
> >> react with region-reacting functions such for comment-dwim.
> >
> > I'm not sure I understand this comment.  Can you elaborate?
> 
> I often want to comment out text with mouse-secondary-overlay.
> 
> I meant if `mouse-secondary-overlay -> region' direction is not
> supported, text with mouse-secondary-overlay cannot be commented out
> until I select the text again as region.  I thought it is good to
> avoid redundant operation if possible.

If we want a function that will put region around secondary selection,
why not write such a function, and let users who want to code commands
that use this functionality do that?  IOW, why do we have to come up
with a command to do something which we aren't sure is a frequent use
case?





  reply	other threads:[~2017-09-06 16:04 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
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 [this message]
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

  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=83o9qn24py.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 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).