From owner-freebsd-current@FreeBSD.ORG Tue Oct 25 19:45:24 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D58B16A420 for ; Tue, 25 Oct 2005 19:45:24 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9585D43D4C for ; Tue, 25 Oct 2005 19:45:23 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9PJbjRE012819; Tue, 25 Oct 2005 13:37:46 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 25 Oct 2005 13:37:41 -0600 (MDT) Message-Id: <20051025.133741.105393650.imp@bsdimp.com> To: des@des.no From: "M. Warner Losh" In-Reply-To: <86mzkzkpvk.fsf@xps.des.no> References: <20051024132130.GW69015@bunrab.catwhisker.org> <86mzkzkpvk.fsf@xps.des.no> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 25 Oct 2005 13:37:46 -0600 (MDT) Cc: david@bunrab.catwhisker.org, current@freebsd.org Subject: Re: 6.0-RC1, X11 cut/paste between windows on different machines??!? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2005 19:45:24 -0000 In message: <86mzkzkpvk.fsf@xps.des.no> des@des.no (Dag-Erling Sm=F8rgrav) writes: : David Wolfskill writes: : > Symptoms... Sometimes (as mentioned above), the cut/paste works : > fine. Sometimes it doesn't. And in the latter case, what gets : > pasted into the target window is whatever had last been "cut" on : > the machine where the target window is running. And -- as an added= : > feature, I suppose -- it seems to be the norm (in the "non-working"= : > case) for the source window to be closed (and the process that had : > been running it to die). : = : man ssh, look for -Y. Or ForwardX11Trusted. Too bad ssh is stupid and old revisions die when they see configuration options they know nothing about :-( Warner