From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stuart D. Herring" Newsgroups: gmane.emacs.devel Subject: Re: [EPeterson@mcdonaldbradley.com: Kill ring leak in winemacs macros] Date: Tue, 16 Aug 2005 09:31:39 -0700 (PDT) Message-ID: <41237.128.165.123.83.1124209899.squirrel@webmail.lanl.gov> 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> Reply-To: herring@lanl.gov NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1124210096 29444 80.91.229.2 (16 Aug 2005 16:34:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 16 Aug 2005 16:34:56 +0000 (UTC) Cc: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 16 18:34:46 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E54MF-0005S7-65 for ged-emacs-devel@m.gmane.org; Tue, 16 Aug 2005 18:32:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E54Pf-0008Kc-Ip for ged-emacs-devel@m.gmane.org; Tue, 16 Aug 2005 12:35:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E54PS-0008KX-Rc for emacs-devel@gnu.org; Tue, 16 Aug 2005 12:35:30 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E54PS-0008KL-CZ for emacs-devel@gnu.org; Tue, 16 Aug 2005 12:35:30 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E54PS-0008KI-9Y for emacs-devel@gnu.org; Tue, 16 Aug 2005 12:35:30 -0400 Original-Received: from [192.65.95.54] (helo=mailwasher-b.lanl.gov) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E54bM-0005Sz-2t; Tue, 16 Aug 2005 12:47:48 -0400 Original-Received: from mailrelay1.lanl.gov (mailrelay1.lanl.gov [128.165.4.101]) by mailwasher-b.lanl.gov (8.12.11/8.12.11/(ccn-5)) with ESMTP id j7GGVh6P032718; Tue, 16 Aug 2005 10:31:44 -0600 Original-Received: from webmail1.lanl.gov (webmail1.lanl.gov [128.165.4.106]) by mailrelay1.lanl.gov (8.12.11/8.12.11/(ccn-5)) with ESMTP id j7GGVd0H003441; Tue, 16 Aug 2005 10:31:39 -0600 Original-Received: from webmail1.lanl.gov (localhost.localdomain [127.0.0.1]) by webmail1.lanl.gov (8.12.11/8.12.11) with ESMTP id j7GGVdLm031528; Tue, 16 Aug 2005 10:31:39 -0600 Original-Received: (from apache@localhost) by webmail1.lanl.gov (8.12.11/8.12.11/Submit) id j7GGVdeR031526; Tue, 16 Aug 2005 09:31:39 -0700 X-Authentication-Warning: webmail1.lanl.gov: apache set sender to herring@lanl.gov using -f Original-Received: from 128.165.123.83 (SquirrelMail authenticated user 196434) by webmail.lanl.gov with HTTP; Tue, 16 Aug 2005 09:31:39 -0700 (PDT) In-Reply-To: <43020FDF.6060007@gnu.org> Original-To: emacs-devel@gnu.org User-Agent: SquirrelMail/1.4.4-2 X-Priority: 3 (Normal) Importance: Normal X-PMX-Version: 4.7.1.128075 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:42134 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:42134 > 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 [clipboard]? What kind of keyboard macro could communicate asynchronously with another program, via the clipboard or otherwise? Something like that would seem to require real Lisp anyway. Moreover, this whole change would be optional (customizable), so the user of any such macro could turn off that option (maybe even temporarily and within the macro to make it self-contained). So I don't think this change can hurt anything. ...I realize, reading the previous paragraph, that this answers the question of which implementation to pursue. The obvious value of a macro that temporarily enables (or disables) clipboard communication means that the customize option should be checked within the macro, not in execute-kbd-macro. One point, remains, though: Richard said he wanted the kill-ring re-synchronized with the external world at the end of a keyboard macro that desynched them; I guess that would have to go in execute-kbd-macro. But what should happen if both Emacs and the window system have new text at that point (where no ordering exists between them)? Davis Herring -- This product is sold by volume, not by mass. If it appears too dense or too sparse, it is because mass-energy conversion has occurred during shipping.