all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
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 09:29:38 -0500	[thread overview]
Message-ID: <jwvpr3qpxbg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <640a924a1002261437k31bcb3b6tecb3bca67294c04f@mail.gmail.com> (Hugh Holbrook's message of "Fri, 26 Feb 2010 14:37:14 -0800")

> 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.

> In my use case, I am invoking emacsclient from within a chrooted shell
> and using TCP to connect to an emacs process that is running on the
> same host, but outside the chroot.  Every file in the chroot is
> nameable in the root file system, but with a different path prefix.

> GNU_NODE_EXCLUDE is useful if some directory is mounted with the same
> path on both the client and server machine.  In my case, the home
> directory is special-cased and appears as /home/username to both the
> emacs and emacsclient process.

Could you point to some origin for this mechanism?
Googling only seems to point to this current thread and to some
gnuclient stuff.  Is gnuclient the only other program using such
a convention?


        Stefan




  parent reply	other threads:[~2010-02-27 14:29 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
2010-02-27 14:29       ` Stefan Monnier [this message]
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=jwvpr3qpxbg.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=holbrook@aristanetworks.com \
    --cc=tomas@tuxteam.de \
    /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.