all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Hugh Holbrook <holbrook@aristanetworks.com>
Cc: tomas@tuxteam.de, emacs-devel@gnu.org
Subject: Re: patch for emacsclient to support GNU_NODE
Date: Sat, 27 Feb 2010 06:45:05 +0100	[thread overview]
Message-ID: <20100227054505.GA25866@tomas> (raw)
In-Reply-To: <640a924a1002261437k31bcb3b6tecb3bca67294c04f@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Feb 26, 2010 at 02:37:14PM -0800, Hugh Holbrook wrote:
> On Fri, Feb 26, 2010 at 6:26 AM, Davis Herring <herring@lanl.gov> wrote:
> >> Excuse my ignorance, but where could I look up what this is for?
> >
> > It just lets emacsclient send a directory name to Emacs that (on Emacs'
> > machine) provides remote access to emacsclient's machine, so that Emacs
> > can open files that emacsclient refers to it that are not reachable with
> > just the literal filename given.  (Apparently it has to be to the root of
> > that machine, since it's just prepended?)
> 
> Yes, precisely.  So for example, a file that is called /tmp/foobar by
> the emacsclient process might be reachable using NFS as
> /net/myhost/tmp/foobar on the host where emacs is running.  You would
> set GNU_NODE to /net/myhost in this case.

Thanks, David, Hugh. I'm now enlightened :-)

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFLiLFhBcgs9XrR2kYRAuSfAJ4qyU5GvcTspuhBco6yQ/o8V1EpYQCcCy0H
wcPh3RpNGSNGLt8d4ri5+nc=
=YCEV
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-02-27  5:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  6:58 patch for emacsclient to support GNU_NODE Hugh Holbrook
2010-02-26 14:01 ` tomas
2010-02-26 14:26   ` Davis Herring
2010-02-26 22:37     ` Hugh Holbrook
2010-02-26 22:57       ` Davis Herring
2010-02-27  5:45       ` tomas [this message]
2010-02-27 14:29       ` Stefan Monnier
2010-02-28  4:37         ` Hugh Holbrook

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100227054505.GA25866@tomas \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    --cc=holbrook@aristanetworks.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.