From: Phil Sainty <psainty@orcon.net.nz>
To: 58608@debbugs.gnu.org
Subject: bug#58608: 29.0.50; Nasty bug with pasting primary selection in term buffers
Date: Wed, 19 Oct 2022 12:10:10 +1300 [thread overview]
Message-ID: <fe2159e6e4577e1f5f171e19302da2e7@webmail.orcon.net.nz> (raw)
In-Reply-To: <4b9aa5bac2d1bfe5af7c246ae9648c87@webmail.orcon.net.nz>
On 2022-10-18 23:10, Phil Sainty wrote:
> 4. Using the mouse, select any small piece of text several
> lines above the bottom of the term buffer (e.g. double-
> click a word).
> 5. Move the mouse to the shell prompt at the end of the buffer
> and middle click to paste that selected text as input.
> 6. Without moving the mouse, middle click again at the same
> position.
In fact "Without moving the mouse" is irrelevant in step 6.
All that matters is where the mouse was when you middle-clicked
in step 5. All middle clicks subsequent to step 5 have the same
(bad) effect regardless of the mouse position, pasting the same
unintended selection each time.
I presume that having an *active* selection at step 5 makes the
difference.
More testing confirms that the initial middle click in step 5
updates the selection with the text between the start of the
active selection and the position of the middle click.
next prev parent reply other threads:[~2022-10-18 23:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 10:10 bug#58608: 29.0.50; Nasty bug with pasting primary selection in term buffers Phil Sainty
2022-10-18 23:10 ` Phil Sainty [this message]
2022-10-19 0:53 ` Phil Sainty
2022-10-19 1:19 ` Phil Sainty
2022-10-19 2:09 ` Phil Sainty
2022-10-19 3:22 ` Phil Sainty
2022-10-19 5:03 ` Phil Sainty
2022-10-19 11:05 ` Eli Zaretskii
2022-10-19 22:14 ` Phil Sainty
2022-10-20 5:36 ` Eli Zaretskii
2023-03-14 12:46 ` Phil Sainty
2023-03-14 14:28 ` Phil Sainty
2023-03-16 7:17 ` Eli Zaretskii
2023-03-26 12:45 ` Phil Sainty
2023-03-26 13:47 ` Eli Zaretskii
2023-03-26 13:48 ` 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=fe2159e6e4577e1f5f171e19302da2e7@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=58608@debbugs.gnu.org \
/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).