Re: w32 does not have emacsclient/server

[Juanma Barranquero]

On 8/9/05, Stefan Monnier <address@hidden> wrote:

> I'd rather see "server-name" which could be a path to a unix socket (like
> now) or just a relative name of a unix socket (like now) or the name of
> a server to be found in ~/.emacs.servers.  I.e. if there is no unix socket
> of that name, lookup ~/.emacs.servers for TCP servers.

Another thing: that would mean having to decide whether you're
creating an AF_UNIX or AF_INET server, and if the former, connection
from some non-Unix emacsclients (like Windows) would be impossible. Is
that a bug or a feature?

I'm really not convinced than keeping both Unix sockets and TCP/IP
sockets is a good idea. I'm open to being convinced otherwise, though.

-- 
                    /L/e/k/t/u