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 13:13:11 +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 1245930076 29730 80.91.229.12 (25 Jun 2009 11:41:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Jun 2009 11:41:16 +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 13:41:09 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 1MJnKG-00048O-FH for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Jun 2009 13:41:08 +0200 Original-Received: from localhost ([127.0.0.1]:57762 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJnKF-0000im-Se for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Jun 2009 07:41:07 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!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: 58 Original-X-Trace: news.eternal-september.org U2FsdGVkX19Epe6seT18/li0DI+9VphfoK7GfXPA/2krQ9HfArI1QfEq9EFPm1FHYb+Riew+adkviEGzpYTuZC5lIKGp0oExtTKmUjZn2mVO/I5epRabuVdBQ3Ef4I0l6fMCBoK9NHI= Original-X-Complaints-To: abuse@motzarella.org Original-NNTP-Posting-Date: Thu, 25 Jun 2009 11:13:09 +0000 (UTC) X-Auth-Sender: U2FsdGVkX1+TtFJ+ASKwJvCZZPzX0ve9NYVTQe5+dY6GaAmvHsiSYg== Cancel-Lock: sha1:AlTeruqRq3Ir2jde37Xl4mu1iLM= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Original-Xref: news.stanford.edu gnu.emacs.help:170278 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:65497 Archived-At: tomas@tuxteam.de writes: > On Wed, Jun 24, 2009 at 11:47:19PM -0500, Harry Putnam wrote: > > [...] > >> Well, like I mentioned in OP.. I want to be able to tap into a gnus >> session running on the remote...You can't do that with tramp [...] > >> Various other aggravations too. > > Have you thought of tunneling the emacs client <--> server connection > through SSH? > > Not tried yet, and I'm not sure whether there is'nt any better way -- > (gurus invited to chime-in ;-) but that is a rough sketch of how I would > proceed: > > (1) Start Emacs server on your server machine, tell it to listen on TCP: > emacs --daemon --eval '(setq server-use-tcp t)' > (of course, typically you wouldn't use --eval in the command line, > but rather put (setq ...) into some suitable startup file) > Now the Emacs daemon is running and accepting connections via tcp. > Maybe you can access it directly from your local network. If > security is enough, you might skip step (3). > > (2) Transfer the file ~/.emacs.d/server/server to your client machine. > It contains (among other things) a cookie which the client has to > present to the server to appease the dogs at its entrance. > > (3) Among those "other things" there is a server address and port > number. With some shell magic, create a shell command along the > lines of > ssh -Llocalhost::localhost: > where you choose and extract from the file > in (2) above > Note that this step is only strictly necessary if you don't want > to have your Emacs server listening in your home net (you'll have > to dissuade it from doing so by some other means, though). > > (4) Give your client in the client machine the server cookie from (2). > If you have done (3) and if and differ, > you might have to edit the cookie file: > emacsclient --server-file > > Of course, if you are more fluent in elisp, you might substitute the > shell magic above with sufficient elisp magic. It's just more magic. > > (5) Let us know whether that works ;-) > > Regards > -- tomás > > What does all that achieve that is different from connecting using emacsclient over standard ssh (with known_host/key allowing connection) and x forwarding?