From: Richard Riley <rileyrgdev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacsclient over ssh
Date: Thu, 25 Jun 2009 14:47:05 +0200 [thread overview]
Message-ID: <h1vrkm$b5u$3@news.eternal-september.org> (raw)
In-Reply-To: mailman.1238.1245932253.2239.help-gnu-emacs@gnu.org
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?
>
> 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
>
next prev parent reply other threads:[~2009-06-25 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1165.1245793203.2239.help-gnu-emacs@gnu.org>
2009-06-23 22:09 ` emacsclient over ssh Richard Riley
2009-06-23 23:13 ` suvayu ali
[not found] ` <mailman.1178.1245818812.2239.help-gnu-emacs@gnu.org>
2009-06-24 10:40 ` Richard Riley
2009-06-24 7:49 ` Tim X
2009-06-24 8:32 ` Josef G. Bauer
2009-06-24 12:13 ` Anselm Helbig
2009-06-25 4:47 ` Harry Putnam
2009-06-25 7:28 ` tomas
2009-06-25 11:38 ` Harry Putnam
[not found] ` <mailman.1230.1245914729.2239.help-gnu-emacs@gnu.org>
2009-06-25 11:13 ` Richard Riley
2009-06-25 12:20 ` tomas
[not found] ` <mailman.1238.1245932253.2239.help-gnu-emacs@gnu.org>
2009-06-25 12:47 ` Richard Riley [this message]
2009-06-25 12:49 ` Richard Riley
2009-06-23 21:39 Harry Putnam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h1vrkm$b5u$3@news.eternal-september.org' \
--to=rileyrgdev@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).