From: Stefan Kangas <stefan@marxist.se>
To: Adolf Mathias <adolf.mathias@gmail.com>
Cc: 34014@debbugs.gnu.org
Subject: bug#34014: 25.2; binding down mouse event with modifier to mouse-drag-region does not work
Date: Sun, 16 Aug 2020 10:10:49 -0700 [thread overview]
Message-ID: <CADwFkmmOyrBzCFfvTWgsFZHbLEUFRP9uyWhFU4_bcJpaDG-16w@mail.gmail.com> (raw)
In-Reply-To: <CACHJYufZhkcSgzcSx8OatdRttJKVb92jSHEcA0nzaiyrYCr5_Q@mail.gmail.com>
Adolf Mathias <adolf.mathias@gmail.com> writes:
> No, it doesn't. With emacs -Q, mouse-1 then mouse-3 does the same as
> simply dragging out a region. Clicking mouse-3 at the same spot, the
> region gets killed, otherwise readjusted.
> With (setq mouse-drag-copy-region t), the region also gets copied to
> the kill ring, otherwise it just disappears.
>
> Assume the text cursor is at position A. I want the region from B to C
> copied to the text cursor position, and then continue editing right
> behind the copied text.
>
> 1. Workflow with mouse-stay-and-copy bound to S-mouse-1:
> press S-mouse-1 at B, release mouse-1 at C.
>
> 2. Workflow with mouse-copy-then-kill and (setq mouse-drag-copy-region t):
> click mouse-1 at B, click mouse-3 at C, click mouse-1 at A, hit Ctrl-Y.
>
> 3. Workflow with standard dragged region:
> drag out region from B to C. Hit Ctrl-W. Click mouse-1 at A. Hit Ctrl-Y.
>
> Workflow 1 saves me one or two mouse clicks and a keystroke and the
> navigation back to A. It is that navigation back to A that bothers me
> most - the dexterity issue, you know.
Thank you for the detailed explanation.
Perhaps the easiest would be to expand `mouse-drag-copy-region' et al.
to optionally support the behavior you are describing? I'm sure we
would consider a patch to Emacs along those lines.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-16 17:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 9:51 bug#34014: 25.2; binding down mouse event with modifier to mouse-drag-region does not work Adolf Mathias
2019-03-01 8:00 ` Eli Zaretskii
2020-08-13 12:02 ` Stefan Kangas
[not found] ` <CACHJYuftHtcJ_ixA0vKbRavKstkaR8fkBaZxyoO_N41Zq7Qy4w@mail.gmail.com>
2020-08-14 14:29 ` Stefan Kangas
2020-08-14 18:58 ` Adolf Mathias
2020-08-15 2:20 ` Stefan Kangas
2020-08-15 11:53 ` Adolf Mathias
2020-08-16 14:34 ` Stefan Kangas
2020-08-16 16:20 ` Adolf Mathias
2020-08-16 17:10 ` Stefan Kangas [this message]
2020-08-16 20:54 ` Adolf Mathias
2020-08-17 14:27 ` Stefan Kangas
[not found] ` <CACHJYue_KVWZ=wF-sa6nHCsAso0SDb0XSoXCRgW0teiR_Gt15Q@mail.gmail.com>
2020-08-18 13:26 ` Stefan Kangas
2020-08-18 15:07 ` Adolf Mathias
2020-08-18 15:32 ` Stefan Kangas
2020-08-15 12:07 ` Adolf Mathias
2020-08-16 21:00 ` bug#34014: Adolf Mathias
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=CADwFkmmOyrBzCFfvTWgsFZHbLEUFRP9uyWhFU4_bcJpaDG-16w@mail.gmail.com \
--to=stefan@marxist.se \
--cc=34014@debbugs.gnu.org \
--cc=adolf.mathias@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 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.