From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Riley Newsgroups: gmane.emacs.help Subject: Re: emacsclient over ssh Date: Thu, 25 Jun 2009 14:49:35 +0200 Organization: aich tea tea pea dicky riley dot net Message-ID: References: <87r5x9g780.wl%anselm.helbig+news2009@googlemail.com> <87k530538o.fsf@newsguy.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1245937302 20689 80.91.229.12 (25 Jun 2009 13:41:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Jun 2009 13:41:42 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jun 25 15:41:35 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MJpCp-0004ZL-65 for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Jun 2009 15:41:35 +0200 Original-Received: from localhost ([127.0.0.1]:41275 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJpCo-000180-Ia for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Jun 2009 09:41:34 -0400 Original-Path: news.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!nx01.iad01.newshosting.com!newshosting.com!216.196.98.140.MISMATCH!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.straub-nv.de!feeder.motzarella.org!news.motzarella.org!eternal-september.org!news.motzarella.org!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 37 Original-X-Trace: news.eternal-september.org U2FsdGVkX19d/26PzreqXlcZ8oc0vrc6zqqZWGiYW7jBr/GRg6iSxMfc4tmxs2b/HBsU+vR+nl/nlkcBrRHRSSqkm13C9XV3rzoVR+zgGJn71Z0RpWkTt041X96TfIwtUx43iEd8TBY= Original-X-Complaints-To: abuse@motzarella.org Original-NNTP-Posting-Date: Thu, 25 Jun 2009 12:49:44 +0000 (UTC) X-Auth-Sender: U2FsdGVkX1+lV41++mny4S7TDbVomZBN3qLXVSsUngItm96fNSK84A== Cancel-Lock: sha1:CR4Ri7XOyLW1kJUetwov6YHkhfY= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (gnu/linux) Original-Xref: news.stanford.edu gnu.emacs.help:170287 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:65504 Archived-At: Richard Riley writes: > tomas@tuxteam.de writes: > >> On Thu, Jun 25, 2009 at 01:13:11PM +0200, Richard Riley wrote: >>> tomas@tuxteam.de writes: >> >> [...] >> >>> What does all that achieve that is different from connecting using >>> emacsclient over standard ssh (with known_host/key allowing connection) >>> and x forwarding? >> >> Following my sketch, you don't forward the X connection, but the emacs >> client <--> server connection. With X forwarding, the Emacs client >> (resp. the Emacs process) runs on the "server". > > Which is what you want. Since x forwarding is optimised for transfer I > would have thought? Ignore that. I see what you mean now. I dont fully understand the differences, but I see where you are going! > >> >> What prompted me to sketch this was the OP's requirement to connect to a >> running Gnus on the server. There I see the two alternatives mentioned above. >> >> No idea whether this buys you anything. It might be faster over a slow >> link. >> >> Regards >> -- tomás >> --