From: Smith_RS <rsmithpv@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Annoying kill-ring behavior
Date: Mon, 31 Mar 2014 15:06:00 -0700 (PDT) [thread overview]
Message-ID: <fc6b7de4-2c3d-430e-a6ef-e21ba2d062eb@googlegroups.com> (raw)
This will be my last question for a while. It's been a persistent niggle for a long time. I was just wondering why this happens and what level of hackery is required to make it go away.
SCENARIO #1
- mouse-1-down, move mouse over text, mouse-1-up, verify kill-ring modified correctly
- re-position mouse pointer over desired yank location in another frame
- notice that frame is not raised, do a mouse-1-down, mouse-1-up to raise the frame and set point at desired yank location
- mouse-2-down, mouse-2-up, observe correct yank behavior
SCENARIO #2
- mouse-1-down, move mouse over text, mouse-1-up, verify kill-ring modified correctly
- re-position mouse pointer over desired yank location in another frame
- notice that frame is not raised, do a mouse-1-down, a very small mouse-drag of just a few pixels, mouse-1-up to raise the frame
- mouse-2-down, mouse-2-up, observe that nothing is yanked, because there is now a zero-length string at the top of the kill-ring
Can someone clue me in as to how I avoid SCENARIO #2?
I want to know how to prevent empty entries from getting into the kill-ring, or remove them after the fact. There is obviously a click-vs-drag pixel threshold being set somewhere, but I can't see where that's exposed so I can modify it.
And I don't really understand why zero-length strings are allowed in the kill-ring at all.
Thanks.
next reply other threads:[~2014-03-31 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 22:06 Smith_RS [this message]
2014-03-31 22:45 ` Annoying kill-ring behavior Stefan Monnier
[not found] ` <mailman.18630.1396305973.10748.help-gnu-emacs@gnu.org>
2014-04-01 7:54 ` Smith_RS
2014-04-01 16:23 ` Smith_RS
2014-04-02 11:59 ` Stefan Monnier
[not found] ` <mailman.18813.1396529475.10748.help-gnu-emacs@gnu.org>
2014-04-03 16:52 ` Smith_RS
2014-04-03 21:59 ` Smith_RS
2014-04-04 4:34 ` Joost Kremers
2014-04-04 7:00 ` Smith_RS
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=fc6b7de4-2c3d-430e-a6ef-e21ba2d062eb@googlegroups.com \
--to=rsmithpv@gmail.com \
--cc=help-gnu-emacs@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.
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).