unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
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 11:32:44 +0200	[thread overview]
Message-ID: <87lgltbidf.fsf@gmail.com> (raw)
In-Reply-To: <20170905.182537.2023575934474224469.tkk@misasa.okayama-u.ac.jp> (Tak Kunihiro's message of "Tue, 05 Sep 2017 18:25:37 +0900 (JST)")

Tak Kunihiro <tkk@misasa.okayama-u.ac.jp> writes:

>>> The function `mouse-exchange-point-and-mark-secondary' exchanges `mark
>>> and point' and secondary.  When there is neither primary nor
>>> secondary, it behaves as `exchange-point-and-mark'.  By doing this, no
>>> revision is necessary for functions that react to region.
>> 
>> This description seems to contradict the docstring:
>>>  
>>> +(defun mouse-exchange-point-and-mark-secondary (&optional arg)
>>> +  "Exchange the point and the mark, and the secondary selection.
>>> +When the mark is active, this exchanges the point and the mark
>>> +then creates the secondary selection from the primary selection.
>>> +When the mark is not active but the secondary selection exists,
>>> +this restores the primary selection from the secondary selection."
>>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> 
>> Could you explain in more detail how this functions? The behaviour
>> seems useful, but I don't understand exactly what it does just from
>> the docstring.
>
> The function exchanges point and mark.
> When there is region, this also creates secondary.
> When there is secondary, this converts secondary to primary in advance.
>

OK. So if I've understood correctly, the user can then use C-y to yank
the primary (which was the secondary before)?

Regards

Robert





  reply	other threads:[~2017-09-05  9:32 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 [this message]
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=87lgltbidf.fsf@gmail.com \
    --to=rpluim@gmail.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).