unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>, 27530@debbugs.gnu.org
Subject: bug#27530: patch to cut and copy secondary
Date: Thu, 29 Jun 2017 06:41:55 -0700 (PDT)	[thread overview]
Message-ID: <9cdc1ecc-d9b2-46fa-a044-fccc27ab1696@default> (raw)
In-Reply-To: <20170629.214304.1822535652145654069.tkk@misasa.okayama-u.ac.jp>

> I found secondary can be used as another region.

Good initiative.

(But another "selection", not another region.)

And a selection that is (obviously) not affected by the
cursor position.  It persists even as you move the cursor.
That's the main difference from the region (advantages,
disadvantages).

> Here I send a patch to cut and copy secondary as if region
> (when region does not exist).

FWIW, I suggested similar things to Emacs devel long ago.
I use the secondary selection a *lot*.

See https://www.emacswiki.org/emacs/second-sel.el,
https://www.emacswiki.org/emacs/SecondarySelection#second-sel.el

You might want to consider incorporating some or all of
what is there.  I and others have been using it since 2008.

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.

> +(defun mouse-secondary-exists-p ()
> +  "Return location of mouse-secondary-overlay when exists in current
> buffer."

Name probably shouldn't end in `-p' if the return value is
mainly not a Boolean.  Non-nil here means overlay limits.

> +(defun mouse-set-mark-and-point-from-secondary ()

Cf. `secondary-to-primary'.

> +(defun mouse-set-secondary-from-region ()

Cf. `primary-to-secondary'.

`second-sel.el' also gives the secondary selection its own
history, `secondary-selection-ring', analogous to `kill-ring'.

HTH.





  reply	other threads:[~2017-06-29 13:41 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 [this message]
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
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=9cdc1ecc-d9b2-46fa-a044-fccc27ab1696@default \
    --to=drew.adams@oracle.com \
    --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).