Re: emacsclient can't connect to socket

[Stefan Monnier]

>     Since the socket is actually created in /tmp, I'm tempted to completely
>     get rid of the hostname there, so it'd just be /tmp/emacs1001/server,
>     so we'd get rid of the whole problem.
> 
>     Does anybody see a problem with it ?
>     Could /tmp reasonably be shared between several machines ?
> 
> I am sure there was originally a good reason for putting the FQDN in
> the socket name.  Formerly the sockets were made in your home
> directory; using the machine name was certainly necessary in that
> case.
> 
> Whether it is still necessary, I am not sure.

I've just installed a change that removes the hostname from the directory
in which the socket is placed.  This assumes that /tmp is not shared
between different hosts.
Also I've changed emacsclient.c so that if you specify an explicit but
relative socket name, it will look for it in the temp dir.  I.e. it behaves
as if the default socket name is just `server'.
We can then change `start-server' to take an optional arg that defaults to
"server" so we can have several emacs servers running on the same machine,
like one called "gnus", another called "server" (the default), another
called "testing", ...


        Stefan