From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Smith_RS Newsgroups: gmane.emacs.help Subject: Annoying kill-ring behavior Date: Mon, 31 Mar 2014 15:06:00 -0700 (PDT) Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1396303836 2852 80.91.229.3 (31 Mar 2014 22:10:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 31 Mar 2014 22:10:36 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Apr 01 00:10:31 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WUkPT-0005TW-GL for geh-help-gnu-emacs@m.gmane.org; Tue, 01 Apr 2014 00:10:27 +0200 Original-Received: from localhost ([::1]:51616 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUkPS-0006yW-J8 for geh-help-gnu-emacs@m.gmane.org; Mon, 31 Mar 2014 18:10:26 -0400 X-Received: by 10.58.91.162 with SMTP id cf2mr9489297veb.17.1396303561113; Mon, 31 Mar 2014 15:06:01 -0700 (PDT) X-Received: by 10.140.109.98 with SMTP id k89mr192919qgf.11.1396303561089; Mon, 31 Mar 2014 15:06:01 -0700 (PDT) Original-Path: usenet.stanford.edu!hw13no10529723qab.1!news-out.google.com!du2ni19232qab.0!nntp.google.com!hw13no10529720qab.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=12.189.199.68; posting-account=FPshOQoAAABhQbXLwYlqquO5tX-UXyrO Original-NNTP-Posting-Host: 12.189.199.68 User-Agent: G2/1.0 Injection-Date: Mon, 31 Mar 2014 22:06:01 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:204623 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:96892 Archived-At: 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.