From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: [EPeterson@mcdonaldbradley.com: Kill ring leak in winemacs macros] Date: Thu, 18 Aug 2005 22:15:59 +0100 Message-ID: References: <34161.128.165.123.83.1123097221.squirrel@webmail.lanl.gov> <42F1208D.1070307@student.lu.se> <34340.128.165.123.83.1123102769.squirrel@webmail.lanl.gov> <40280.128.165.123.83.1124204823.squirrel@webmail.lanl.gov> <43020FDF.6060007@gnu.org> <430211FD.5000507@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1124400442 11889 80.91.229.2 (18 Aug 2005 21:27:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 18 Aug 2005 21:27:22 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 18 23:27:18 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E5ruv-0002Um-9i for ged-emacs-devel@m.gmane.org; Thu, 18 Aug 2005 23:27:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E5ryS-0003tL-Ks for ged-emacs-devel@m.gmane.org; Thu, 18 Aug 2005 17:30:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E5ruK-0002kE-0t for emacs-devel@gnu.org; Thu, 18 Aug 2005 17:26:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E5ru9-0002eQ-OJ for emacs-devel@gnu.org; Thu, 18 Aug 2005 17:26:31 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E5ru7-0002bl-UZ for emacs-devel@gnu.org; Thu, 18 Aug 2005 17:26:27 -0400 Original-Received: from [194.106.33.237] (helo=outmail.freedom2surf.net) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1E5s1H-0005Ms-NE for emacs-devel@gnu.org; Thu, 18 Aug 2005 17:33:52 -0400 Original-Received: from wanchan.jasonrumney.net (i-83-67-23-108.freedom2surf.net [83.67.23.108]) by outmail.freedom2surf.net (8.12.10/8.12.10) with ESMTP id j7ILHGch021653; Thu, 18 Aug 2005 22:17:16 +0100 Original-Received: from TONKOTSU-RAMEN (tonkotsu-ramen.jasonrumney.net [10.0.0.28]) by wanchan.jasonrumney.net (Postfix) with ESMTP id 56C09DDD72; Thu, 18 Aug 2005 22:17:12 +0100 (BST) Original-To: Kevin Rodgers In-Reply-To: (Kevin Rodgers's message of "Thu, 18 Aug 2005 10:43:41 -0600") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (windows-nt) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:42242 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:42242 Kevin Rodgers writes: > Jason Rumney wrote: > > Jason Rumney wrote: > >> I'm not convinced this change is a good one. What if your macro > >> involves a call-process call to an external program that interacts > >> with Emacs via the keyboard? > > > > clipboard, of course, not keyboard. > > If the proposed new option's default preserves the current behavior, you > don't have to do anything. But if the default is to disable interaction > via the clipboard, then you'd have to customize the option before > executing the macro. I'm still not convinced this change is worth making now. On X, even with clipboard enabled, the actual copying to the clipboard is only performed if another application requests it. Andrew Innes suggested many years ago that the W32 clipboard should work the same way, but noone has picked up that job yet. I don't know which way Mac does it, but that can probably be modified to use delayed copying if it does not already. So we are talking about reducing the functionality of keyboard macros to get around a performance problem that does not exist on the most important platforms, and that we know can be fixed on others.