unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* emacsclient not working anymore on Mac OS X
@ 2002-11-29 20:15 William McCallum
  2002-11-30 13:05 ` dme
  0 siblings, 1 reply; 6+ messages in thread
From: William McCallum @ 2002-11-29 20:15 UTC (permalink / raw)


Since upgrading to 10.2.2 and recompiling emacs from cvs (21.3.50), I 
find that emacclient no longer connects to a running carbon emacs.  For 
example

emacsclient --no-wait +100 file.tex
emacsclient: can't find socket; have you started the server?

This is despite the fact that the carbon emacs is running and the 
server has been started in my .emacs file with

(server-start)

Everything works fine with emacs 21.2.1 running under Xwindows


(520) 621 6697
http://www.math.arizona.edu/~wmc

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: emacsclient not working anymore on Mac OS X
  2002-11-29 20:15 William McCallum
@ 2002-11-30 13:05 ` dme
  0 siblings, 0 replies; 6+ messages in thread
From: dme @ 2002-11-30 13:05 UTC (permalink / raw)


* mccallumwilliam@qwest.net [2002-11-29 20:15:21]
> Since upgrading to 10.2.2 and recompiling emacs from cvs (21.3.50), I
> find that emacclient no longer connects to a running carbon emacs.
> For example
> 
> emacsclient --no-wait +100 file.tex
> emacsclient: can't find socket; have you started the server?

I'd guess that you are using the old fink version of emacsclient and
the new cvs version of emacsserver.  Emacsclient/server has been
modified to truncate hostnames at the first `.', which means that the
name of the unix domain socket changed.  If you have an old
emacsclient binary in your path (/sw/bin/emacsclient, for example) it
will not find the new socket.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* emacsclient not working anymore on Mac OS X
       [not found] <16429675@toto.iv>
@ 2002-11-30 21:43 ` Stephen Eglen
  2002-12-02 15:46   ` Richard Stallman
  0 siblings, 1 reply; 6+ messages in thread
From: Stephen Eglen @ 2002-11-30 21:43 UTC (permalink / raw)



 > emacsclient --no-wait +100 file.tex
 > emacsclient: can't find socket; have you started the server?

I'm afraid that I can't help answer this question, but it made me
think of the following:

Would it be a good idea for this error message to explain how to start
the server within Emacs?  You might think that because someone has
used emacsclient, they must know to do M-x server-start before hand.
However, in ESS (Emacs speaks statistics), emacsclient is used to
allow running statistical processes to use Emacs to edit various
objects.  So it it possible that an Emacs user may not yet know
about calling server-start.  Perhaps ESS should ensure (server-start)
is called, but regardless I think having an extra line in the error
might be helpful. e.g.:

 emacsclient: can't find socket; have you started the server?
 To start the server in emacs, type "M-x server-start".

Any objections to me checking this into lib-src/emacsclient.c?

Stephen

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: emacsclient not working anymore on Mac OS X
  2002-11-30 21:43 ` emacsclient not working anymore on Mac OS X Stephen Eglen
@ 2002-12-02 15:46   ` Richard Stallman
  2003-02-26  0:15     ` Dave Carlton
  0 siblings, 1 reply; 6+ messages in thread
From: Richard Stallman @ 2002-12-02 15:46 UTC (permalink / raw)
  Cc: emacs-devel

     emacsclient: can't find socket; have you started the server?
     To start the server in emacs, type "M-x server-start".

    Any objections to me checking this into lib-src/emacsclient.c?

That is a good idea.  Thanks for thinking of it,
and please do it.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: emacsclient not working anymore on Mac OS X
  2002-12-02 15:46   ` Richard Stallman
@ 2003-02-26  0:15     ` Dave Carlton
  2003-02-26 23:25       ` Richard Stallman
  0 siblings, 1 reply; 6+ messages in thread
From: Dave Carlton @ 2003-02-26  0:15 UTC (permalink / raw)
  Cc: emacs-devel

I notice you will also get this error message if you have executed sudo 
-s to become root. I presume the emacsclient is not capable of 
connecting to another users server?

On Monday, December 2, 2002, at 07:46 AM, Richard Stallman wrote:

>      emacsclient: can't find socket; have you started the server?
>      To start the server in emacs, type "M-x server-start".
>
>     Any objections to me checking this into lib-src/emacsclient.c?
>
> That is a good idea.  Thanks for thinking of it,
> and please do it.
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/emacs-devel
>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: emacsclient not working anymore on Mac OS X
  2003-02-26  0:15     ` Dave Carlton
@ 2003-02-26 23:25       ` Richard Stallman
  0 siblings, 0 replies; 6+ messages in thread
From: Richard Stallman @ 2003-02-26 23:25 UTC (permalink / raw)
  Cc: emacs-devel

    I notice you will also get this error message if you have executed sudo 
    -s to become root. I presume the emacsclient is not capable of 
    connecting to another users server?

That is probably correct.  I suppose there could be a feature to
specify the intended user name, for running emacsclient as root.
An envvar would be the convenient way, rather than a command option.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2003-02-26 23:25 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <16429675@toto.iv>
2002-11-30 21:43 ` emacsclient not working anymore on Mac OS X Stephen Eglen
2002-12-02 15:46   ` Richard Stallman
2003-02-26  0:15     ` Dave Carlton
2003-02-26 23:25       ` Richard Stallman
2002-11-29 20:15 William McCallum
2002-11-30 13:05 ` dme

Code repositories for project(s) associated with this public inbox

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

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