public inbox for
 help / color / mirror / Atom feed
From: Mark Purtill <>
To: <>
Subject: SourceNav with NTEmacs
Date: Thu, 09 Aug 2001 10:45:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <3190BC9FA8F6D3119508009027E5B33E4B7C39@MORSE>

Dalton, Barnaby writes:
 > Does anyone use sourcenav with ntemacs? I'm trying to get it working with
 > gnuclient. The first time I try to edit a file from sourcenav a new emacs
 > process is launched even if I have already started one via other means. This
 > second process starts with the *messages*
 > Server subprocess exited
 > connection failed: connection refused,, sn
 > >From then on sourcenav always uses this second process. Doesn anyone know
 > what is going on?
 > Gnuclient/serv is defnitely working ok as I have used it from windows
 > explorer/msdev for years.

	I had a similar problem under Linux.  When you set the editor
to gnuclient, SN recognizes that and does what it thinks is the right
thing, which seems to be to start a new emacs for you.  (Subsequent
calls would try to use gnuclient.)  In your case, it sounds like this
doesn't work because the server that gnuclient talks to has already
been started by your previous emacs.  Try writing a script with a name
different from gnuclient; I have one that looks something like this:

#! /bin/sh
export TMPDIR
gnuclient $*

You'll need the equivalent for NT, except probably not the TMPDIR
stuff.  (There's an additional problem on Linux that SN sets TEMPDIR,
which gnuclient uses to connect to the emacs; if the two processes
have different TMPDIRs, they can't connect, so I reset it.)  You might
try naming the progam both a name with "emacs" in the name and not and
see which works better for you.  (The behavior is different because,
again, SN is looking at the name and trying to be clever.)

^.-.^ Mark Purtill

      reply	other threads:[~2001-08-09 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08  6:24 Dalton, Barnaby
2001-08-09 10:45 ` Mark Purtill [this message]

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:

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

  git send-email \ \ \ \

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