From: Phillip Lord <p.lord@russet.org.uk>
Subject: Re: emacs(client|server) vs. gnu(client|server)
Date: 17 Sep 2002 14:13:06 +0100 [thread overview]
Message-ID: <vflm60vjx9.fsf@rpc71.cs.man.ac.uk> (raw)
In-Reply-To: vd0y9a0hq4l.fsf@kogs31.informatik.uni-hamburg.de
>>>>> "Sven" == Sven Utcke <utcke+news@informatik.uni-hamburg.de> writes:
Sven> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai
Sven> =?iso-8859-15?q?Gro=DFjohann?=) writes:
>> Both started from the same base and then diverged. gnuclient can
>> contact an Emacs running on another host for editing files.
Sven> Talking about which: I normally sit in front of kogs31, and
Sven> have gnuclient set up in such a way that if I am logged into
Sven> another machine (kogs2, say) via ssh, if I edit a file there
Sven> an emacs frame pops up on kogs31.
Sven> So far so well. But yesterday I then moved bodily to kogs2,
Sven> and needed to edit something on the display of kogs2. I
Sven> _thought_ I would be able to use gnuclient to signal the emacs
Sven> on kogs31 to open a window on kogs2 to let me edit, but not
Sven> so. So, does this mean that the above can not be done, or
Sven> only that I am to dump to understand the manual?
gnuclient can do this I think, with the -h parameter, to specific the
hostname. But you have to be careful because gnuclient allows
execution of arbitrary lisp on the server emacs, which means arbitrary
processes on the server machine.
The easiest way to get this to work is just to stick "ssh kog31" in
front of the gnuclient call....
At least if I understand what you are asking correctly.
Cheers
Phil
next prev parent reply other threads:[~2002-09-17 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1031904732.3602.help-gnu-emacs@gnu.org>
2002-09-13 14:54 ` emacs(client|server) vs. gnu(client|server) Kai Großjohann
2002-09-17 10:22 ` Sven Utcke
2002-09-17 13:13 ` Phillip Lord [this message]
2002-09-18 9:13 ` Sven Utcke
2002-09-17 14:24 ` Kai Großjohann
2002-09-18 9:16 ` Sven Utcke
2002-09-20 13:42 ` Kai Großjohann
2002-09-23 13:00 ` Sven Utcke
2002-09-13 8:27 Luis O. Silva
2002-09-16 13:51 ` Alexander Koptelov
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=vflm60vjx9.fsf@rpc71.cs.man.ac.uk \
--to=p.lord@russet.org.uk \
/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).